SEARCH · Search NASA

Results for “process and scheduling”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 145 records · Page 8

All sources NASA NTRS DOE OSTI

NASA NTRS1986

Run-time implementation issues for real-time embedded Ada

A motivating factor in the development of Ada as the department of defense standard language was the high cost of embedded system software development. It was with embedded system requirements in mind that many of the features of the language were incorporated. Yet it is the designers of embedded systems that seem to comprise the majority of the Ada community dissatisfied with the language. There are a variety of reasons for this dissatisfaction, but many seem to be related in some way to the Ada run-time support system. Some of the areas in which the inconsistencies were found to have the greatest impact on performance from the standpoint of real-time systems are presented. In particular, a large part of the duties of the tasking supervisor are subject to the design decisions of the implementer. These include scheduling, rendezvous, delay processing, and task activation and termination. Some of the more general issues presented include time and space efficiencies, generic expansions, memory management, pragmas, and tracing features. As validated compilers become available for bare computer targets, it is important for a designer to be aware that, at least for many real-time issues, all validated Ada compilers are not created equal.

Maule, Ruth A.↗

NASA NTRS1995

Planning as a Precursor to Scheduling for Space Station Payload Operations

Contemporary schedulers attempt to solve the problem of best fitting a set of activities into an available timeframe while still satisfying the necessary constraints. This approach produces results which are optimized for the region of time the scheduler is able to process, satisfying the near term goals of the operation. In general the scheduler is not able to reason about the activities which precede or follow the window into which it is inputs to scheduling so that the intermediate placing activities. This creates a problem for operations which are composed of many activities spanning long durations (which exceed the scheduler's reasoning horizon) such as the continuous operations environment for payload operations on the Space Station. Not only must the near term scheduling objectives be met, but somehow the results of near term scheduling must be made to support the attainment of long term goals.

Howell, Eric↗

NASA NTRS2001

Web-Based Distributed Simulation of Aeronautical Propulsion System

An application was developed to allow users to run and view the Numerical Propulsion System Simulation (NPSS) engine simulations from web browsers. Simulations were performed on multiple INFORMATION POWER GRID (IPG) test beds. The Common Object Request Broker Architecture (CORBA) was used for brokering data exchange among machines and IPG/Globus for job scheduling and remote process invocation. Web server scripting was performed by JavaServer Pages (JSP). This application has proven to be an effective and efficient way to couple heterogeneous distributed components.

Zheng, Desheng↗

NASA NTRS1999

Scientific Programming Using Java and C: A Remote Sensing Example

This paper presents results of a project to port code for processing remotely sensed data from the UNIX environment to Windows. Factors considered during this process include time schedule, cost, resource availability, reuse of existing code, rapid interface development, ease of integration, and platform independence. The approach selected for this project used both Java and C. By using Java for the graphical user interface and C for the domain model, the strengths of both languages were utilized and the resulting code can easily be ported to other platforms. The advantages of this approach are discussed in this paper.

Prados, Donald↗

NASA NTRS2008

Increasing the Cost-efficiency of the DSN

JPL has operated the Deep Space Network (DSN) on behalf of NASA since the 1960's. Over the last two decades, the DSN budget has generally declined in real-year dollars while the aging assets required more attention, and the missions became more complex. As a result, the budget has been increasingly consumed by Operations and Maintenance (O and M), significantly reducing the funding wedge available for technology investment and for enhancing the DSN capability and capacity. Responding to this budget squeeze, the DSN launched an effort to improve the cost-efficiency of the O and M. In this paper we: Analyze the components of O&M. We note for example that, for the DSN, less than 20% of the staff engage in the traditional human-in-front-a-console role, so any effort to increase the cost efficiency must go beyond reducing the number of "Real-time operators." Explain the underlying organizational and cultural structures. Any cost-efficiency activities changes either accept, or carefully modify these structures. For example, the DSN O&M is based on the concept that there are three nearly identical antenna complexes separated by approximately 1200 in latitude and that each antenna complex is operated by a different contractor (driven by international agreements). Explore planned changes in the customer interface, e.g. web-based automated scheduling, and the processes required for a transition. Changes have to be evaluated in the larger end-to-end context, e.g. do the changes provide a net cost-efficiency for the DSN and the missions, or do they merely shift cost from the DSN to the missions. Consider possible significant changes in real-time pass management, e.g. full-remoting of operations, and lights-dim operations, while maintaining (or improving) the performance metrics of the DSN. Investigate how procedural and administrative changes could increase cost-efficiency, in conjunction with changes in the customer interfaces and real-time pass management. Examples would be handling of inter-governmental agreements, improved sharing of resources with other agencies, and better use of commercial (rather than government) resources

Deep Space Network (DSN)↗

NASA NTRS2010

JSC Wireless Sensor Network Update

Sensor nodes composed of three basic components... radio module: COTS radio module implementing standardized WSN protocol; treated as WSN modem by main board main board: contains application processor (TI MSP430 microcontroller), memory, power supply; responsible for sensor data acquisition, pre-processing, and task scheduling; re-used in every application with growing library of embedded C code sensor card: contains application-specific sensors, data conditioning hardware, and any advanced hardware not built into main board (DSPs, faster A/D, etc.); requires (re-) development for each application.

Wagner, Robert↗

NASA NTRS2011

Ground Processing Affordability for Space Vehicles

Launch vehicles and most of their payloads spend the majority of their time on the ground. The cost of ground operations is very high. So, why so often is so little attention given to ground processing during development? The current global space industry and economic environment are driving more need for efficiencies to save time and money. Affordability and sustainability are more important now than ever. We can not continue to treat space vehicles as mere science projects. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability which are not available for ELV's (Expendable Launch Vehicles). More human-rated vehicles are being developed, with the retirement of the Space Shuttles, and for a new global space race, yet these cost more than the many unmanned vehicles of today. We can learn many lessons on affordability from RLV's. DFO (Design for Operations) considers ground operations during design, development, and manufacturing-before the first flight. This is often minimized for space vehicles, but is very important. Vehicles are designed for launch and mission operations. You will not be able to do it again if it is too slow or costly to get there. Many times, technology changes faster than space products such that what is launched includes outdated features, thus reducing competitiveness. Ground operations must be considered for the full product Lifecycle, from concept to retirement. Once manufactured, launch vehicles along with their payloads and launch systems require a long path of processing before launch. Initial assembly and testing always discover problems to address. A solid integration program is essential to minimize these impacts, as was seen in the Constellation Ares I-X test rocket. For RLV's, landing/recovery and post-flight turnaround activities are performed. Multi-use vehicles require reconfiguration. MRO (Maintenance, Repair, and Overhaul) must be well-planned--- even for the unplanned problems. Defect limits and standard repairs need to be in-place as well as easily added. Many routine inspections and maintenance can be like an aircraft overhaul. Modifications and technology upgrades should be expected. Another factor affecting ground operations efficiency is trending. It is essential for RLV's, and also useful for ELV's which fly the same or similar models again. Good data analysis of technical and processing performance will determine fixes and improvements needed for safety, design, and future processing. Collecting such data on new or low-frequency vehicles is a challenge. Lessons can be learned from the Space Shuttle, or even the Concorde aircraft. For all of the above topics, efficient business systems must be established for comprehensive program management and good throughput. Drawings, specifications, and manuals for an entire launch vehicle are often in different formats from multiple vendors, plus they have proprietary constraints. Nonetheless, the integration team must ensure that all data needed is compatible and visible to each appropriate team member. Ground processing systems for scheduling, tracking, problem resolution, etc. must be well laid-out. The balance between COTS (commercial off the shelf) and custom software is difficult. Multiple customers, vendors, launch sites, and landing sites add to the complexity of efficient IT (Information Technology) tools.

Ingalls, John↗

NASA NTRS2013

Mission Data System Java Edition Version 7

The Mission Data System framework defines closed-loop control system abstractions from State Analysis including interfaces for state variables, goals, estimators, and controllers that can be adapted to implement a goal-oriented control system. The framework further provides an execution environment that includes a goal scheduler, execution engine, and fault monitor that support the expression of goal network activity plans. Using these frameworks, adapters can build a goal-oriented control system where activity coordination is verified before execution begins (plan time), and continually during execution. Plan failures including violations of safety constraints expressed in the plan can be handled through automatic re-planning. This version optimizes a number of key interfaces and features to minimize dependencies, performance overhead, and improve reliability. Fault diagnosis and real-time projection capabilities are incorporated. This version enhances earlier versions primarily through optimizations and quality improvements that raise the technology readiness level. Goals explicitly constrain system states over explicit time intervals to eliminate ambiguity about intent, as compared to command-oriented control that only implies persistent intent until another command is sent. A goal network scheduling and verification process ensures that all goals in the plan are achievable before starting execution. Goal failures at runtime can be detected (including predicted failures) and handled by adapted response logic. Responses can include plan repairs (try an alternate tactic to achieve the same goal), goal shedding, ignoring the fault, cancelling the plan, or safing the system.

Reinholtz, William K.↗

NASA NTRS2015

Metallography of Battery Resistance Spot Welds

Li-ion cells provide an energy dense solution for systems that require rechargeable electrical power. However, these cells can undergo thermal runaway, the point at which the cell becomes thermally unstable and results in hot gas, flame, electrolyte leakage, and in some cases explosion. The heat and fire associated with this type of event is generally violent and can subsequently cause damage to the surrounding system or present a dangerous risk to the personnel nearby. The space flight environment is especially sensitive to risks particularly when it involves potential for fire within the habitable volume of the International Space Station (ISS). In larger battery packs such as Robonaut 2 (R2), numerous Li-ion cells are placed in parallel-series configurations to obtain the required stack voltage and desired run-time or to meet specific power requirements. This raises a second and less obvious concern for batteries that undergo certification for space flight use: the joining quality at the resistance spot weld of battery cells to component wires/leads and battery tabs, bus bars or other electronic components and assemblies. Resistance spot welds undergo materials evaluation, visual inspection, conductivity (resistivity) testing, destructive peel testing, and metallurgical examination in accordance with applicable NASA Process Specifications. Welded components are cross-sectioned to ensure they are free of cracks or voids open to any exterior surface. Pore and voids contained within the weld zone but not open to an exterior surface, and are not determined to have sharp notch like characteristics, shall be acceptable. Depending on requirements, some battery cells are constructed of aluminum canisters while others are constructed of steel. Process specific weld schedules must be developed and certified for each possible joining combination. The aluminum canisters' positive terminals were particularly difficult to weld due to a bi-metal strip that comes ultrasonically pre-welded by the manufacturer. This was further complicated as the maximum electrode force was limited to low-electrode force to prevent deflection of the aluminum can during welding. Other Li-ion cells are comprised of smaller diameter cylindrical steel canisters which are inherently capable of handling greater force from the electrodes. Allowing higher-electrode forces aids greatly in insuring a consistent resistance network for the weld. Overall lessons learned: developing good jigs is critical to insure the parts and electrodes are planer to one another and the location of the weld sites remains accurate and repeatable; maintaining strict control over materials is critical--materials must be of a specific hardness and chemical composition to insure that a weld schedule is repeatable; accuracy of the die used to stamp the projections is critical and worth the investment; and proper seasoning of the electrodes is critical to producing consistent welds--once the electrodes have been properly seasoned, cleaning/dressing should be avoided until it is absolutely necessary.

Martinez, J. E.↗

NASA NTRS2015

NASA's Space Launch System Program Update

Hardware and software for the world's most powerful launch vehicle for exploration is being welded, assembled, and tested today in high bays, clean rooms and test stands across the United States. NASA's Space Launch System (SLS) continued to make significant progress in 2014 with more planned for 2015, including firing tests of both main propulsion elements and the program Critical Design Review (CDR). Developed with the goals of safety, affordability, and sustainability, SLS will still deliver unmatched capability for human and robotic exploration. The initial Block 1 configuration will deliver more than 70 metric tons of payload to low Earth orbit (LEO). The evolved Block 2 design will deliver some 130 metric tons to LEO. Both designs offer enormous opportunity and flexibility for larger payloads, simplifying payload design as well as ground and on-orbit operations, shortening interplanetary transit times, and decreasing overall mission risk. Over the past year, every vehicle element has manufactured or tested hardware. An RS-25 liquid propellant engine was hotfire-tested at NASA's Stennis Space Center, Miss. for the first time since 2009 exercising and validating the new engine controller, the renovated A-1 test stand, and the test teams. Four RS-25s will power the SLS core stage. A qualification five-segment solid rocket motor incorporating several design, material, and process changes was scheduled to be test-fired in March at the prime contractor's facility in Utah. The booster also successfully completed its Critical Design Review (CDR) validating the planned design. All six major manufacturing tools for the core stage are in place at the Michoud Assembly Facility in Louisiana, and have been used to build numerous pieces of confidence, qualification, and even flight hardware, including barrel sections, domes and rings used to assemble the world's largest rocket stage. SLS Systems Engineering accomplished several key tasks including vehicle avionics software and hardware build and testing, scale model acoustic and base heating tests. Construction of the Interim Cryogenic Propulsion Stage (ICPS) began. Advanced development provided a look into the future of SLS. Shell buckling knockdown factor testing refined decades-old design margins that added thousands of pounds to rocket payloads. Adaptive manufacturing and structured light scanning development promised to cut the cost and time associated with manufacturing and testing. This paper will provide an overview of the progress made over the past year and provide a glimpse of 2015 milestones and beyond on the way to the first launch in 2018.

May, Todd↗

NASA NTRS2015

NASA's Space Launch System Program Update

May, Todd↗

NASA NTRS2018

Engineering Elegant Systems: Postulates, Principles, and Hypotheses of Systems Engineering

Definition: System Engineering is the engineering discipline which integrates the system functions, system environment, and the engineering disciplines necessary to produce and/or operate an elegant system; Elegant System - A system that is robust in application, fully meeting specified and adumbrated intent, is well structured, and is graceful in operation. Primary Focus: System Design and Integration: Identify system couplings and interactions; Identify system uncertainties and sensitivities; Identify emergent properties; Manage the effectiveness of the system. Engineering Discipline Integration: Manage flow of information for system development and/or operations; Maintain system activities within budget and schedule. Supporting Activities: Process application and execution.

Watson, Michael D.↗

NASA NTRS2018

A Flexible Control Center Architecture for Support of Diverse Spaceflight Missions

The Ames Multi-Mission Operations Center (MMOC) enables and supports flight and science operations for Ames' spaceflight missions. The MMOC is composed of the facilities, networks, information technology equipment, software, and system administration services needed by flight projects to effectively and efficiently perform all mission functions, including planning, scheduling, command, telemetry processing, and science analysis. The MMOC's ready-to-use services reduce start-up time, shorten procurement and provisioning and allow mission planning efforts to focus more on science and less on infrastructure. The architecture of the MMOC was designed from the start for flexibility, so that it can readily support multiple missions of greatly varying size and complexity while simultaneously keeping costs low.

Differding, Joan C.↗

NASA NTRS2020

Dynamic IT Security Database and Analytics for Launch Control Systems Software

During the Summer 2020 session, I worked with intern Destani S. Van Arsdalen of EGS Software. Together, we co-created a tool to aid the dynamic investigation, updated over time,of the security compliance of LCS COTS and open source software. We originally planned touse spreadsheet software for management and analysis, but through this exploratoryproject, chose to use Python and JSON after receiving feedback on our project’s current anddesired capabilities at that time.At first, the project was solely designed to help on-board new COTS software, based on aquestionnaire that could be filled out for each software package. This, combined with usingthe spreadsheet application’s web-query capabilities to fetch information from the NVD,allowed presentation and analytics cells to automatically populate as elements of themanually-filled questionnaire changed. While this system was promising, we decided tochange technologies for a few reasons. In the spreadsheet, single cells could not hold complexdata like arrays and objects. The automatic population of cells and dynamic updates made itdifficult to manage and add new features. And finally, it had limited extensibility sinceadding new software required significant understanding of how both the spreadsheet wasconstructed, and the more obscure, proprietary scripting languages packaged with it.The pivot to a standard computer science database language of JSON, aided by thescripting capabilities of Python, greatly helped to improve the project’s functionality. First,and most importantly, the script’s import and analysis of database data is easilyreproducible. Additional data analysis can be modularly added without requiringmodification of the script and is capable of routine scheduling. The revised process can besplit into three parts. First, the conversion of LCS asset and software documentation into theJSON hierarchical database format. Second, the merging of this database with the NVD,forming a new data structure, using CPEs of the CVE object as a linking element betweenthem. And third, the automatically performed analytics and analysis of the combined data,in a modular and extensible format, to produce better informed business decisions. The outputted graphs, for example, are automatically generated by the Python script inconnection with the combined database. This allows updated graphs and any analytics to be re-rendered automatically following updates to the LCS’s initial asset documentation. Afinal report can then be programmatically and easily constructed from these sources to allow fully reproducible metrics for heavily evidenced risk management decisions.

it↗

NASA NTRS2020

The XRISM Science Data Center: Optimizing the Scientific Return from a Unique X-ray Observatory

The X-Ray Imaging and Spectroscopy Mission, XRISM, is currently scheduled to launch in 2022 with the objective of building on the brief, but significant, successes of the ASTRO-H (Hitomi) mission in solving outstanding astrophysical questions using high resolution X-ray spectroscopy. The XRISM Science Operations Team (SOT) consists of the JAXA-led Science Operations Center (SOC) and NASA-led Science Data Center (SDC), which work together to optimize the scientific output from the Resolve high-resolution spectrometer and the Xtend wide-field imager through planning and scheduling of observations, processing and distribution of data, development and distribution of software tools and the calibration database (CaldB), support of ground and in-flight calibration, and support of XRISM users in their scientific investigations of the energetic universe. Here, we summarize the roles and responsibilities of the SDC and its current status and future plans. The Resolve instrument poses particular challenges due to its unprecedented combination of high spectral resolution and throughput, broad spectral coverage, and relatively small field-of-view and large pixel-size. We highlight those challenges and how they are being met.

XRISM↗

NASA NTRSDate not supplied

Vapor Growth of ZnSe-based Compound Semiconductors in Low Gravity environment on International Space Station

Six low-gravity experiments of crystal growth of ZnSe-based compound semiconductors by physical vapor transport (PVT) are scheduled to be processed inside Low Gradient Furnace (LGF) on Materials Science Research Rack (MSRR) in Material Science Laboratory (MSL) on International Space Station (ISS) starting from February 27th, 2023. The flight samples consist of three unseeded growths of ZnSe, Cr-doped ZnSe and ZnSeTe as well as growth of ZnSe on top of three single crystal ZnSe seeds with orientation of (100), (110) and (111). The main scientific objective of the flight experiments is to establish the effects of gravity-driven fluid flows on Earth to (i) the non-uniform incorporation of impurities and defects and (ii) the deviation from stoichiometry observed in the grown crystals caused by growth interface fluctuations and evolution as the results of buoyancy-driven convection and irregular fluid-flows. The investigation will also evaluate the effects of gravity on the PVT process by examining (i) the growth kinetics on various seed orientations, (ii) the dopant segregation and distribution in the Cr doped ZnSe, and (iii) the compositional segregation and distribution in the ternary ZnSeTe crystal grown by PVT. Additionally, from X-ray diffraction/topography and by measuring the density and distribution of various crystalline defects it will assess the self-induced strain effects developed during processing at elevated temperatures caused by the weight of the crystals. During the ground-based preparations, the following tasks have been accomplished: • Establish the thermodynamic properties of the ZnSe binary and related ternary systems by measuring the partial pressures of the vapor phase coexisting with the condensed phases and perform phase diagram calculations for comparison. • Evaluate the effects of gravity-driven convection in the growth process by performing experiments under various vapor transport orientations relative to gravity vector, i.e., horizontal, vertically stabilized and destabilized configurations. • Establish a quantitative correlation between growth parameters and the characteristics and properties of the grown crystals by characterizing the crystals using a variety of techniques. • Evaluate the fundamentals of the current theories on vapor transport and crystal growth kinetics by performing in-situ and real-time monitoring techniques during growth. • Develop a one-dimensional diffusion limited theory of mass transport and two- and three-dimensional numerical simulations of both mass transport and heat transfer and thus establish the microgravity requirements for the flight experiments and to predict the characteristics of the grown crystals such as the solid-vapor interface shapes… etc. and establish a fundamental understanding of the crystal growth process from the comparison with experimental results.

ZnSe↗

NASA NTRSDate not supplied

NASA Space Communications and Navigation: One Network Evolution

The NASA Space Communications and Navigation (SCaN) Program is responsible for providing the essential connectivity to robotic and human space explorers. The missions relying on SCaN range from suborbital and balloon missions to those traveling beyond the edge of the solar system. The demands for communications and navigation services enabled by SCaN (and its affiliated partners) are projected to increase and outpace the current network capacity. At the same time, the Agency finds itself surrounded by a burgeoning commercial space marketplace, technological advancement, and other government agencies that share common interests in space resiliency, robustness, and performance. As a result, SCaN has begun pivoting toward commercial services and collaborating with partners to close capacity and capability gaps. Given these growing demands of the Agency there is increasing need for multi-network solutions. Future mission concepts will rely on both government and commercial capabilities, both Near Space Network capacity and Deep Space Network capacity. Integrating these diverse support services together from a technical, programmatic and implementation standpoint will be key to meet the growing needs of the future. To accomplish this, a more substantive shift is required, and SCaN is reshaping itself to be a customer-centric, service-oriented, high-performance leader in the space communications community. This paper outlines the SCaN One Team, One Mission, One Network approach, and provides a vision for future mission community experience that includes streamlined mission commitment interfaces and clear processes, dynamic network scheduling and load balancing, and higher efficiency data transport and delivery through the integration of cloud infrastructure and services.

Near Space Network↗

NASA NTRS1994

Galileo mission planning for Low Gain Antenna based operations

The Galileo mission operations concept is undergoing substantial redesign, necessitated by the deployment failure of the High Gain Antenna, while the spacecraft is on its way to Jupiter. The new design applies state-of-the-art technology and processes to increase the telemetry rate available through the Low Gain Antenna and to increase the information density of the telemetry. This paper describes the mission planning process being developed as part of this redesign. Principal topics include a brief description of the new mission concept and anticipated science return (these have been covered more extensively in earlier papers), identification of key drivers on the mission planning process, a description of the process and its implementation schedule, a discussion of the application of automated mission planning tool to the process, and a status report on mission planning work to date. Galileo enhancements include extensive reprogramming of on-board computers and substantial hard ware and software upgrades for the Deep Space Network (DSN). The principal mode of operation will be onboard recording of science data followed by extended playback periods. A variety of techniques will be used to compress and edit the data both before recording and during playback. A highly-compressed real-time science data stream will also be important. The telemetry rate will be increased using advanced coding techniques and advanced receivers. Galileo mission planning for orbital operations now involves partitioning of several scarce resources. Particularly difficult are division of the telemetry among the many users (eleven instruments, radio science, engineering monitoring, and navigation) and allocation of space on the tape recorder at each of the ten satellite encounters. The planning process is complicated by uncertainty in forecast performance of the DSN modifications and the non-deterministic nature of the new data compression schemes. Key mission planning steps include quantifying resource or capabilities to be allocated, prioritizing science observations and estimating resource needs for each, working inter-and intra-orbit trades of these resources among the Project elements, and planning real-time science activity. The first major mission planning activity, a high level, orbit-by-orbit allocation of resources among science objectives, has already been completed; and results are illustrated in the paper. To make efficient use of limited resources, Galileo mission planning will rely on automated mission planning tools capable of dealing with interactions among time-varying downlink capability, real-time science and engineering data transmission, and playback of recorded data. A new generic mission planning tool is being adapted for this purpose.

Gershman, R.↗