Search NASASearch

SEARCH · Search NASA

Results for “system engineering program”

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.

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

At least 163 records · Page 9

Implementing an Objectives-Driven, Risk-Informed, and Case-Assured Approach to Safety and Mission Success at NASA

NASA is developing a “Standard for Assurance of Space Flight Safety and Mission Success” that implements an objectives-driven, risk-informed, and case-assured approach to safety and mission success (S&MS) for NASA space flight programs and projects. The standard aligns with the philosophy of risk leadership that has recently been established in NASA policy to assure acceptable levels of flight crew safety and mission success risk. It is consistent with existing NASA risk management requirements and is compatible with NASA program management and systems engineering requirements. The methodology described in the standard is presented in terms of an S&MS assurance framework that is designed to allow substantial flexibility in the specific means by which programs and projects achieve acceptable mission S&MS risk. Such flexibility is necessary to accommodate the increasingly broad range of acquisition strategies employed by NASA, including commercial transportation services, as well as to accommodate the increasingly rapid evolution of space flight-related technologies and practices. A key feature of the S&MS assurance framework is the specification of S&MS success criteria for each life-cycle review (LCR). The S&MS assurance case is structured around these criteria, the satisfaction of which indicates that the program/project is adhering to the S&MS risk posture. This enables the evolving S&MS assurance case to be used as a fundamental program/project submittal at each LCR, where its inherent structure of argument, supported by evidence, directly supports the evaluation of the program/project with respect to the S&MS success criteria, and by extension, the S&MS risk posture. As such, the S&MS assurance case is integral to program/project systems engineering, risk management, and S&MS oversight activities, and provides the principal basis for S&MS risk acceptance by the Decision Authority throughout the program/project life cycle.

Risk Posture

Performance of a Checkerboard Liner With Uncertain Impedances

The current fleet of large commercial aircraft has successfully achieved FAA noise certifications because of, in part, the successful application of uniform passive duct liner treatments to control engine system noise. One goal of NASA's engine system noise reduction program is to develop technologies to improve the sound absorbing properties of duct liner treatments so that they remain effective in modern turbo fan engines. One such technology being studied is checkerboard or periodic axially and circumferentially segmented liners. A preliminary assessment of the potential of this technology was conducted by applying uncertainties associated with manufacturing, installation, source structure, and tonal frequency to a liner developed using deterministic design methods and generating a measure of improvement with respect to a uniform liner subjected to the same uncertainties. Deterministic design and analysis of the candidate checkerboard liner showed that it obtains a 1.5 dB per duct aspect ratio improvement in liner attenuation over a similarly designed uniform liner. When uncertainties in liner impedances, source structure, and frequency are considered, the performance of the checkerboard liner drops off dramatically. The final results of this paper show that the candidate checkerboard liner has a less than 25 percent chance of outperforming the uniform liner when moderate levels of uncertainty are considered. It is important to note that this study did not include the effects of mean flow on liner performance and, more important to note, that as a gradient based optimization process was used to design the checkerboard liner, it is almost certain that a global optimal design was not found for the candidate checkerboard liner. Had it been possible to find a better deterministically performing checkerboard liner, the probability that this candidate liner would outperform the uniform liner would certainly have been higher.

Robinson, J. H.

Explanation Constraint Programming for Model-based Diagnosis of Engineered Systems

We can expect to see an increase in the deployment of unmanned air and land vehicles for autonomous exploration of space. In order to maintain autonomous control of such systems, it is essential to track the current state of the system. When the system includes safety-critical components, failures or faults in the system must be diagnosed as quickly as possible, and their effects compensated for so that control and safety are maintained under a variety of fault conditions. The Livingstone fault diagnosis and recovery kernel and its temporal extension L2 are examples of model-based reasoning engines for health management. Livingstone has been shown to be effective, it is in demand, and it is being further developed. It was part of the successful Remote Agent demonstration on Deep Space One in 1999. It has been and is being utilized by several projects involving groups from various NASA centers, including the In Situ Propellant Production (ISPP) simulation at Kennedy Space Center, the X-34 and X-37 experimental reusable launch vehicle missions, Techsat-21, and advanced life support projects. Model-based and consistency-based diagnostic systems like Livingstone work only with discrete and finite domain models. When quantitative and continuous behaviors are involved, these are abstracted to discrete form using some mapping. This mapping from the quantitative domain to the qualitative domain is sometimes very involved and requires the design of highly sophisticated and complex monitors. We propose a diagnostic methodology that deals directly with quantitative models and behaviors, thereby mitigating the need for these sophisticated mappings. Our work brings together ideas from model-based diagnosis systems like Livingstone and concurrent constraint programming concepts. The system uses explanations derived from the propagation of quantitative constraints to generate conflicts. Fast conflict generation algorithms are used to generate and maintain multiple candidates whose consistency can be tracked across multiple time steps.

Narasimhan, Sriram

1964 publications

NASA program technical notes on materials, propulsion systems, spacecraft, and engineering development

ENGINEERING DEVELOPMENT

New 5 Kilowatt Free-piston Stirling Space Convertor Developments

The NASA Vision for Exploration of the moon may someday require a nuclear reactor coupled with a free-piston Stirling convertor at a power level of 30-40 kW. In the 1990s, Mechanical Technology Inc. s Stirling Engine Systems Division (some of whose Stirling personnel are now at Foster-Miller, Inc.) developed a 25 kW free piston Stirling Space Power Demonstrator Engine under the SP-100 program. This system consisted of two 12.5 kW engines connected at their hot ends and mounted in tandem to cancel vibration. Recently, NASA and DoE have been developing dual 55 W and 80 W Stirling convertor systems for potential use with radioisotope heat sources. Total test times of all convertors in this effort exceed 120,000 hours. Recently, NASA began a new project with Auburn University to develop a 5 kW, single convertor for potential use in a lunar surface reactor power system. Goals of this development program include a specific power in excess of 140 W/kg at the convertor level, lifetime in excess of five years and a control system that will safely manage the convertors in case of an emergency. Auburn University awarded a subcontract to Foster-Miller, Inc. to undertake development of the 5 kW Stirling Convertor Assembly. The characteristics of the design along with progress in developing the system will be described.

Brandhorst, Henry W., Jr.

Safety inputs to development program plans

Safety engineers integration into overall system through basic development programs, involving management, manufacturing, testing and integrated logistic support

Ball, L. W.

System Engineering on the Use for Ares I,V - the Simpler, the Better

The Ares I and Ares V Vehicles will utilize the J-2X rocket engine developed for NASA by the Pratt & Whitney Rocketdyne Company. The J-2X is an improved higher power version of the original J-2 engine used during the Apollo program. With higher power and updated requirements for safety and performance, the J-2X becomes a new engine using state-of-the-art design methodology, materials and manufacturing processes. The implementation of Systems Engineering (SE) principles enables the rapid J-2X development program to remain aligned with the ARES I and V vehicle programs, Meeting the aggressive development schedule is a challenge. Coordinating the best expertise thai NASA and PWR have to offer requires effectively utilizing resources at multiple sites. This presents formidable communication challenges. SE allows honest and open discussions of issues and problems. This simple idea is often overlooked in large and complex SE programs. Regular and effective meetings linking SE objectives to component designs are used to voice differences of opinions with customer and contractor in attendance so that the best mutual decisions can be made on the shortest possible schedule. Regular technical interchange meetings on secure program wide computer networks and CM processes are effective,in the "Controlled Change" process that exemplifies good SE. Good communication is a key effective SE implementation. The System of Systems approach is the vision of the Orion program which facilitates the establishment of dynamic SE processes at all levels including the engine. SE enables requirements evolution by facilitating organizational and process agility. Flow down and distribution of requirements is controlled by Allocation Reports which breakdown numerical design objectives (weight, reliability, etc.) into quanta goals for each component area. Linked databases of design and verification requirements helps eliminate redundancy and potential mistakes inherent m separated systems. Another tool, the Architecture Design Description, is being used to control J-2X system architecture and effectively communicate configuration changes to those involved in the design process. But the proof is in successful program accomplishment. The SE is the methodology being used to meet the challenge of completing J-2X engine certification 2 years ahead of any engine program ever developed at PWR. The Ares I SE system of systems has delivered according to expectations thus far. All major design reviews (SRR. PDR, CDR) have been successfully conducted to satisfy overall program objectives using SE as the basis for accomplishment. The paper describes SE tools and techniques utilized to achieve this success.

Kelly, William

Sustainable, Reliable Mission-Systems Architecture

A mission-systems architecture, based on a highly modular infrastructure utilizing: open-standards hardware and software interfaces as the enabling technology is essential for affordable and sustainable space exploration programs. This mission-systems architecture requires (a) robust communication between heterogeneous system, (b) high reliability, (c) minimal mission-to-mission reconfiguration, (d) affordable development, system integration, and verification of systems, and (e) minimal sustaining engineering. This paper proposes such an architecture. Lessons learned from the Space Shuttle program and Earthbound complex engineered system are applied to define the model. Technology projections reaching out 5 years are mde to refine model details.

O'Neil, Graham

Sustainable, Reliable Mission-Systems Architecture

A mission-systems architecture, based on a highly modular infrastructure utilizing open-standards hardware and software interfaces as the enabling technology is essential for affordable md sustainable space exploration programs. This mission-systems architecture requires (8) robust communication between heterogeneous systems, (b) high reliability, (c) minimal mission-to-mission reconfiguration, (d) affordable development, system integration, end verification of systems, and (e) minimal sustaining engineering. This paper proposes such an architecture. Lessons learned from the Space Shuttle program and Earthbound complex engineered systems are applied to define the model. Technology projections reaching out 5 years are made to refine model details.

O'Neil, Graham

Integrating Engineering Data Systems for NASA Spaceflight Projects

NASA has a large range of custom-built and commercial data systems to support spaceflight programs. Some of the systems are re-used by many programs and projects over time. Management and systems engineering processes require integration of data across many of these systems, a difficult problem given the widely diverse nature of system interfaces and data models. This paper describes an ongoing project to use a central data model with a web services architecture to support the integration and access of linked data across engineering functions for multiple NASA programs. The work involves the implementation of a web service-based middleware system called Data Aggregator to bring together data from a variety of systems to support space exploration. Data Aggregator includes a central data model registry for storing and managing links between the data in disparate systems. Initially developed for NASA's Constellation Program needs, Data Aggregator is currently being repurposed to support the International Space Station Program and new NASA projects with processes that involve significant aggregating and linking of data. This change in user needs led to development of a more streamlined data model registry for Data Aggregator in order to simplify adding new project application data as well as standardization of the Data Aggregator query syntax to facilitate cross-application querying by client applications. This paper documents the approach from a set of stand-alone engineering systems from which data are manually retrieved and integrated, to a web of engineering data systems from which the latest data are automatically retrieved and more quickly and accurately integrated. This paper includes the lessons learned through these efforts, including the design and development of a service-oriented architecture and the evolution of the data model registry approaches as the effort continues to evolve and adapt to support multiple NASA programs and priorities.

Carvalho, Robert E.

Minority University System Engineering: A Small Satellite Design Experience Held at the Jet Propulsion Laboratory During the Summer of 1996

The University of Texas at El Paso (UTEP) in conjunction with the Jet Propulsion Laboratory (JPL), North Carolina A&T and California State University of Los Angeles participated during the summer of 1996 in a prototype program known as Minority University Systems Engineering (MUSE). The program consisted of a ten week internship at JPL for students and professors of the three universities. The purpose of MUSE as set forth in the MUSE program review August 5, 1996 was for the participants to gain experience in the following areas: 1) Gain experience in a multi-disciplinary project; 2) Gain experience working in a culturally diverse atmosphere; 3) Provide field experience for students to reinforce book learning; and 4) Streamline the design process in two areas: make it more financially feasible; and make it faster.

Ordaz, Miguel Angel

Space Program Advocacy Can Distort Project Management and Damage Systems Engineering

Over-optimistic project advocacy often causes exaggerated performance claims and underestimated costs and schedules. This can distort project management and damage systems engineering. NASA projects such as the space shuttle and Hubble are extreme examples. NASA's spectacular success in the Apollo moon landings seems to have produced overconfidence and carelessness, but also to have gained tolerance for unrealistic claims and forgiveness when they were proven wrong. Apollo risk analysis predicted many astronaut fatalities. This was believed but was potentially damaging to the Apollo program, so risk analysis was discontinued. The moon landings beat bad odds because Apollo obsessively reduced risk. Its success seemed to confirm that risk analysis was unreasonably pessimistic and that risk could be overcome by good engineering. This understanding caused risk to be increased during space shuttle engineering and led to an unnecessarily dangerous approach. The shuttle design placed a fragile spacecraft next to the fuel tanks and failed to provide crew escape or launch abort. These design decisions directly caused the Challenger and Columbia tragedies. After Challenger, risk analysis was re-established. The current rocket and capsule design does consider risk and the result strongly resembles Apollo. Apollo advocacy led NASA to abandon risk analysis and this was ultimate cause of the Shuttle tragedies. Excessive advocacy that distorts risk, cost, and schedule could be prevented in an ideal organization that used systems engineering to make rational and fair decisions. However, most real organizations accommodate human and group needs using informal methods often described as "the system." Humans have biases, use innate decision making heuristics, instinctively rely on "gut feel," and establish deviant groups through groupthink. Expecting organizations to become totally rational is impractical, but specific problems such as neglecting risk and underestimating cost and schedule can be directly challenged with some hope of success.

Jones, Harry W.

A database for propagation models

The NASA Propagation Program supports academic research that models various propagation phenomena in the space research frequency bands. NASA supports such research via school and institutions prominent in the field. The products of such efforts are particularly useful for researchers in the field of propagation phenomena and telecommunications systems engineers. The systems engineer usually needs a few propagation parameter values for a system design. Published literature on the subject, such as the Cunsultative Committee for International Radio (CCIR) publications, may help somewhat, but often times, the parameter values given in such publications use a particular set of conditions which may not quite include the requirements of the system design. The systems engineer must resort to programming the propagation phenomena model of interest and to obtain the parameter values to be used in the project. Furthermore, the researcher in the propagation field must then program the propagation models either to substantiate the model or to generate a new model. The researcher or the systems engineer must either be a skillful computer programmer or hire a programmer, which of course increases the cost of the effort. An increase in cost due to the inevitable programming effort may seem particularly inappropriate if the data generated by the experiment is to be used to substantiate the already well-established models, or a slight variation thereof. To help researchers and the systems engineers, it was recommended by the participants of NASA Propagation Experimenters (NAPEX) 15 held in London, Ontario, Canada on 28-29 June 1991, that propagation software should be constructed which will contain models and prediction methods of most propagation phenomenon. Moreover, the software should be flexible enough for the user to make slight changes to the models without expending a substantial effort in programming.

Kantak, Anil V.

Water recovery and management test support modeling for Space Station Freedom

The water-recovery and management (WRM) subsystem proposed for the Space Station Freedom program is outlined, and its computerized modeling and simulation based on a Computer Aided System Engineering and Analysis (CASE/A) program are discussed. A WRM test model consisting of a pretreated urine processing (TIMES), hygiene water processing (RO), RO brine processing using TIMES, and hygiene water storage is presented. Attention is drawn to such end-user equipment characteristics as the shower, dishwasher, clotheswasher, urine-collection facility, and handwash. The transient behavior of pretreated-urine, RO waste-hygiene, and RO brine tanks is assessed, as well as the total input/output to or from the system. The model is considered to be beneficial for pretest analytical predictions as a program cost-saving feature.

Mohamadinejad, Habib

Shuttle mission simulator requirements report, volume 1, revision A

The tasks are defined required to design, develop produce, and field support a shuttle mission simulator for training crew members and ground support personnel. The requirements for program management, control, systems engineering, design and development are discussed along with the design and construction standards, software design, control and display, communication and tracking, and systems integration.

Burke, J. F.