SEARCH · Search NASA

Results for “Systems Engineering environments”

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 469 records · Page 26

All sources NASA NTRS DOE OSTI

NASA NTRS1959

Experimental Altitude Performance of JP-4 Fuel and Liquid-Oxygen Rocket Engine with an Area Ratio of 48

The performance for four altitudes (sea-level, 51,000, 65,000, and 70,000 ft) of a rocket engine having a nozzle area ratio of 48.39 and using JP-4 fuel and liquid oxygen as a propellant was evaluated experimentally by use of a 1000-pound-thrust engine operating at a chamber pressure of 600 pounds per square inch absolute. The altitude environment was obtained by a rocket-ejector system which utilized the rocket exhaust gases as the pumping fluid of the ejector. Also, an engine having a nozzle area ratio of 5.49 designed for sea level was tested at sea-level conditions. The following table lists values from faired experimental curves at an oxidant-fuel ratio of 2.3 for various approximate altitudes.

Fortini, Anthony↗

NASA NTRSDate not supplied

Going beyond reliability to robustness and resilience in space systems

The words reliability, robustness, and resilience, are often used interchangeably to describe tough and dependable systems but the distinctions between them suggest how to design more serviceable space systems. Reliability is simply the quality of consistently performing well. A system that dependably meets its design requirements in the specified environments is reliable. The designers may not consider themselves responsible for failures under unanticipated conditions. Robustness is the capability of performing without failure under a wide range of conditions, which can go beyond the expected range to include possible off-nominal conditions. Resilience is the ability to recover from or adapt to damaging events, such as failures, accidents, external disruptions, and repurposing. Such changes are usually unanticipated. They often invalidate the usual operating assumptions and cause system failure. Reliability, robustness, and resilience describe dependable performance under increasingly difficult conditions, first the specified environment, then a wider possible environment, and finally unanticipated damaging events. These three are increasingly desirable and increasingly difficult to achieve. Engineering for resilience would design systems that can ignore or repair failures, survive accidents, and recover from disruptions. Increasing the resilience of space systems, the ability to perform after unanticipated events, would greatly increase space crew safety. Improving reliability and robustness can be done by dealing with known sources of problems, but improving resilience requires implementing a general approach to reducing the impact of unknown future events. Two contrasting approaches are reducing system complexity and adding supervisory control. The need for resilience has been claimed for decades but little has been accomplished. Systems designers assume that they understand requirements, technologies, designs, architectures, integration, testing, operations, and environments. The potential problems of changes, failures, accidents, unknown environments, and unknown unknowns are ignored. Systems designers are typically overconfident and ignore the need for robustness and resilience.

Harry W Jones↗

NASA NTRS1997

Application of NASA's Advanced Life Support Technologies in Polar Regions

The problems of obtaining adequate pure drinking water and disposing of liquid and solid waste in the U.S Arctic, a region where virtually all water is frozen solid for much of the year, has led to unsanitary solutions. Sanitation and a safe water supply are particularly problems in rural villages. These villages are without running water and use plastic buckets for toilets. The outbreak of diseases is believed to be partially attributable to exposure to human waste and lack of sanitation. Villages with the most frequent outbreaks of disease are those in which running water is difficult to obtain. Waste is emptied into open lagoons, rivers, or onto the sea coast. It does not degrade rapidly and in addition to affecting human health, can be harmful to the fragile ecology of the Arctic and the indigenous wildlife and fish populations. Current practices for waste management and sanitation pose serious human hazards as well as threaten the environment. NASA's unique knowledge of water/wastewater treatment systems for extreme environments, identified in the Congressional Office of Technology Assessment report entitled An Alaskan Challenge: Native Villagt Sanitation, may offer practical solutions addressing the issues of safe drinking water and effective sanitation practices in rural villages. NASA's advanced life support technologies are being combined with Arctic science and engineering knowledge to address the unique needs of the remote communities of Alaska through the Advanced Life Systems for Extreme Environments (ALSEE) project. ALSEE is a collaborative effort involving the NASA, the State of Alaska, the University of Alaska, the North Slope Borough of Alaska, Ilisagvik College in Barrow and the National Science Foundation (NSF). The focus is a major issue in the State of Alaska and other areas of the Circumpolar North; the health and welfare of its people, their lives and the subsistence lifestyle in remote communities, economic opportunity, and care for the environment. As advanced technologies are transferred to the commercial sector the ALSEE project Offers the potential for development of new industries in Alaska to supply the products to support remote communities of the globe.

Bubenheim, David L.↗

NASA NTRS1986

Applying Ada to Beech Starship avionics

As Ada solidified in its development, it became evident that it offered advantages for avionics systems because of it support for modern software engineering principles and real time applications. An Ada programming support environment was developed for two major avionics subsystems in the Beech Starship. The two subsystems include electronic flight instrument displays and the flight management computer system. Both of these systems use multiple Intel 80186 microprocessors. The flight management computer provides flight planning, navigation displays, primary flight display of checklists and other pilot advisory information. Together these systems represent nearly 80,000 lines of Ada source code and to date approximately 30 man years of effort. The Beech Starship avionics systems are in flight testing.

Funk, David W.↗

NASA NTRS2005

Managed Development Environment Successes for MSFC's VIPA Team

This paper outlines the best practices of the Vehicle Design Team for VIPA. The functions of the VIPA Vehicle Design (VVD) discipline team are to maintain the controlled reference geometry and provide linked, simplified geometry for each of the other discipline analyses. The core of the VVD work, and the approach for VVD s first task of controlling the reference geometry, involves systems engineering, top-down, layout-based CAD modeling within a Product Data Manager (PDM) development environment. The top- down approach allows for simple control of very large, integrated assemblies and greatly enhances the ability to generate trade configurations and reuse data. The second VVD task, model simplification for analysis, is handled within the managed environment through application of the master model concept. In this approach, there is a single controlling, or master, product definition dataset. Connected to this master model are reference datasets with live geometric and expression links. The referenced models can be for drawings, manufacturing, visualization, embedded analysis, or analysis simplification. A discussion of web based interaction, including visualization, between the design and other disciplines is included. Demonstrated examples are cited, including the Space Launch Initiative development cycle, the Saturn V systems integration and verification cycle, an Orbital Space Plane study, and NASA Exploration Office studies of Shuttle derived and clean sheet launch vehicles. The VIPA Team has brought an immense amount of detailed data to bear on program issues. A central piece of that success has been the Managed Development Environment and the VVD Team approach to modeling.

Finckenor, Jeff↗

NASA NTRS2013

Adoption of Test Driven Development and Continuous Integration for the Development of the Trick Simulation Toolkit

This paper describes the adoption of a Test Driven Development approach and a Continuous Integration System in the development of the Trick Simulation Toolkit, a generic simulation development environment for creating high fidelity training and engineering simulations at the NASA/Johnson Space Center and many other NASA facilities. It describes what was learned and the significant benefits seen, such as fast, thorough, and clear test feedback every time code is checked-in to the code repository. It also describes a system that encourages development of code that is much more flexible, maintainable, and reliable. The Trick Simulation Toolkit development environment provides a common architecture for user-defined simulations. Trick builds executable simulations using user-supplied simulation-definition files (S_define) and user supplied "model code". For each Trick-based simulation, Trick automatically provides job scheduling, checkpoint / restore, data-recording, interactive variable manipulation (variable server), and an input-processor. Also included are tools for plotting recorded data and various other supporting tools and libraries. Trick is written in C/C++ and Java and supports both Linux and MacOSX. Prior to adopting this new development approach, Trick testing consisted primarily of running a few large simulations, with the hope that their complexity and scale would exercise most of Trick's code and expose any recently introduced bugs. Unsurprising, this approach yielded inconsistent results. It was obvious that a more systematic, thorough approach was required. After seeing examples of some Java-based projects that used the JUnit test framework, similar test frameworks for C and C++ were sought. Several were found, all clearly inspired by JUnit. Googletest, a freely available Open source testing framework, was selected as the most appropriate and capable. The new approach was implemented while rewriting the Trick memory management component, to eliminate a fundamental design flaw. The benefits became obvious almost immediately, not just in the correctness of the individual functions and classes but also in the correctness and flexibility being added to the overall design. Creating code to be testable, and testing as it was created resulted not only in better working code, but also in better-organized, flexible, and readable (i.e., articulate) code. This was, in essence the Test-driven development (TDD) methodology created by Kent Beck. Seeing the benefits of Test Driven Development, other Trick components were refactored to make them more testable and tests were designed and implemented for them.

Penn, John M.↗

NASA NTRS2012

The Direction of Fluid Dynamics for Liquid Propulsion at NASA Marshall Space Flight Center

Marshall Space Flight Center (MSFC) is the National Aeronautics and Space Administration (NASA)-designated center for the development of space launch systems. MSFC is particularly known for propulsion system development. Many engineering skills and technical disciplines are needed to accomplish this mission. This presentation will focus on the work of the Fluid Dynamics Branch (ER42). ER42 resides in the Propulsion Systems Department at MSFC. The branch is responsible for all aspects of the discipline of fluid dynamics applied to propulsion or propulsion-induced loads and environments. This work begins with design trades and parametric studies, and continues through development, risk assessment, anomaly investigation and resolution, and failure investigations. Applications include the propellant delivery system including the main propulsion system (MPS) and turbomachinery; combustion devices for liquid engines and solid rocket motors; coupled systems; and launch environments. An advantage of the branch is that it is neither analysis nor test centric, but discipline centric. Fluid dynamics assessments are made by analysis, from lumped parameter modeling through unsteady computational fluid dynamics (CFD); testing, which can be cold flow or hot fire; or a combination of analysis and testing. Integration of all discipline methods into one branch enables efficient and accurate support to the projects. To accomplish this work, the branch currently employs approximately fifty engineers divided into four teams -- Propellant Delivery CFD, Combustion Driven Flows CFD, Unsteady and Experimental Flows, and Acoustics and Stability. This discussion will highlight some of the work performed in the branch and the direction in which the branch is headed.

Griffin, Lisa W.↗

NASA NTRS1988

From 2001 to 1994: Political environment and the design of NASA's Space Station system

The U.S. civilian space station, a hope of numerous NASA engineers since before the agency was founded in 1958 and promoted by NASA as the country's 'next logical step' into space, provides an excellent case study of the way public-sector research and development agencies continuously redefine new technologies in the absence of the market discipline that governs private-sector technological development. The number of space station design studies conducted since 1959, both internally by NASA or contracted by the agency to the aerospace industry, easily exceeds a hundred. Because of this, three clearly distinguishable examples are selected from the almost thirty-year history of space station design in NASA. Together these examples illustrate the difficulty of defining a new technological system in the public sector as that system becomes increasingly subject, for its development, to the vagaries of federal research and development politics.

Fries, Sylvia Doughty↗

NASA NTRS1984

Control system testing

A three stage process of ground testing of the Space Telescope Pointing Control System is used for verification prior to on-orbit operation. First, development tests are conducted in a laboratory environment using flight/engineering model control sensor and actuators configured with an engineering model of the flight computer and data management system breadboards. These development tests validate the results of computer simulations predicting control system performance. Integration tests bring together flight system elements and software interfaced to a software simulation of vehicle dynamics to confirm closed loop performance. The final ground test phase, flight systems testing, is conducted on the fully assembled Space Telescope, verifies interfaces with the Fine Guidance Sensors and includes a thermal vacuum testing period. During the final test phase, the Point Control System is exercised with the dynamics simulator running in real time.

Whittler, W. H.↗

NASA NTRS2008

Communication Needs Assessment for Distributed Turbine Engine Control

Control system architecture is a major contributor to future propulsion engine performance enhancement and life cycle cost reduction. The control system architecture can be a means to effect net weight reduction in future engine systems, provide a streamlined approach to system design and implementation, and enable new opportunities for performance optimization and increased awareness about system health. The transition from a centralized, point-to-point analog control topology to a modular, networked, distributed system is paramount to extracting these system improvements. However, distributed engine control systems are only possible through the successful design and implementation of a suitable communication system. In a networked system, understanding the data flow between control elements is a fundamental requirement for specifying the communication architecture which, itself, is dependent on the functional capability of electronics in the engine environment. This paper presents an assessment of the communication needs for distributed control using strawman designs and relates how system design decisions relate to overall goals as we progress from the baseline centralized architecture, through partially distributed and fully distributed control systems.

Culley, Dennis E.↗

NASA NTRSDate not supplied

NASA Aeronautics Research Mission Directorate System Security Engineering Approaches

System security engineering (SSE) is a set of formal engineering methods and is considered a subset of systems engineering. It is a relatively new development in systems engineering with the initial NIST (National Institute of Standards) standard published in November of 2016 with updates in 2018, and 2022. The guiding principles in our methodology are based in NIST Special Publication 800-160 Vol. 1 “Systems Security Engineering: Considerations For A Multidisciplinary Approach In The Engineering Of Trustworthy Secure Systems” and integrate methodologies from common IT (Information Technology) threat modeling approaches utilizing MBSE (Model-Based Systems Engineering). The presentation will discuss how our teams utilize SSE and MBSE (Model-Based Systems Engineering) to develop secure architectures for systems under development in our NASA aeronautics research environment. This includes the activities to develop Protection Needs (PN) that, in turn result in security requirements in the design context and policies for the future state operational context for system protection. The process of applying SSE to analyze project architectures and ConOps (Concept of Operations) is intended to ensure the transferred research is both secure and securable in a “real-world” setting.

Systems Security Engineering↗

NASA NTRS2018

Failure Analysis and Products in a Model-Based Environment

The work presented in this paper describes an approach, including a methodology and tools, which allows system engineers to capture failure-related information in a model and generate automatically key failure analysis products: the Failure Modes, Effects and Criticality Analysis (FMECA) and the Fault Tree Analysis (FTA). The work has been developed by Tietronix Software, Inc. and the NASA’s Jet Propulsion Laboratory (JPL), and the resulting auto-generated artifacts shown in this paper demonstrate the ability to obtain powerful reliability and fault management products in a model-based environment.

Castet, Jean-Francois↗

NASA NTRS1989

Preliminary base heating environments for a generalized ALS LO2/LH2 launch vehicle, appendix 1 and 2

A secondary objective of contract NAS8-39141 is to provide base heating assessments, as required, to support Advanced Launch System (ALS) preliminary launch vehicle and propulsion system design studies. The ALS propulsion systems integration working group meeting (No. 3) recently completed in San Diego, California, focused attention on the need for base heating environment determination to provide preliminary requirements for LO2/LH2 propulsion systems currently being considered for ALS. We were requested to provide these environments for a range of possible propellant mixture and nozzle area ratios. Base heating environments can only be determined as a function of altitude when the engine operating conditions and vehicle base region geometry (engine arrangement) are known. If time dependent environments are needed to assess thermal loads, a trajectory must also be provided. These parameters are not fixed at this time since the ALS configurations and propulsion operating conditions are varied and continue to be studied by Phase B contractors. Therefore, for this study, a generalized LO2/LH2 system was selected along with a vehicle configuration consisting of a seven-engine booster and a three-engine core. MSFC provided guidance for the selection. We also selected a limited number of body points on the booster and core vehicles and engines for the environment estimates. Environments at these locations are representative of maximum heating conditions in the base region and are provided as a function of altitude only. Guidelines and assumptions for this assessment, methodology for determining the environments, and preliminary results are provided in this technical note. Refinements in the environments will be provided as the ALS design matures.

Bender, Robert L.↗

NASA NTRS2012

Space Environments and Spacecraft Effects Organization Concept

The National Aeronautics and Space Administration (NASA) is embarking on a course to expand human presence beyond Low Earth Orbit (LEO) while also expanding its mission to explore the solar system. Destinations such as Near Earth Asteroids (NEA), Mars and its moons, and the outer planets are but a few of the mission targets. Each new destination presents an opportunity to increase our knowledge of the solar system and the unique environments for each mission target. NASA has multiple technical and science discipline areas specializing in specific space environments disciplines that will help serve to enable these missions. To complement these existing discipline areas, a concept is presented focusing on the development of a space environments and spacecraft effects (SENSE) organization. This SENSE organization includes disciplines such as space climate, space weather, natural and induced space environments, effects on spacecraft materials and systems and the transition of research information into application. This space environment and spacecraft effects organization will be composed of Technical Working Groups (TWG). These technical working groups will survey customers and users, generate products, and provide knowledge supporting four functional areas: design environments, engineering effects, operational support, and programmatic support. The four functional areas align with phases in the program mission lifecycle and are briefly described below. Design environments are used primarily in the mission concept and design phases of a program. Engineering effects focuses on the material, component, sub-system and system-level selection and the testing to verify design and operational performance. Operational support provides products based on real time or near real time space weather to mission operators to aid in real time and near-term decision-making. The programmatic support function maintains an interface with the numerous programs within NASA, other federal government agencies, and the commercial sector to ensure that communications are well established and the needs of the programs are being met. The programmatic support function also includes working in coordination with the program in anomaly resolution and generation of lessons learned documentation. The goal of this space environment and spacecraft effects organization is to develop decision-making tools and engineering products to support all mission phases from mission concept through operations by focusing on transitioning research to application. Products generated by this space environments and effects application are suitable for use in anomaly investigations. This paper will describe the scope of the TWGs and their relationship to the functional areas, and discuss an organizational structure for this space environments and spacecraft effects organization.

Edwards, David L.↗

NASA NTRS2001

Power Quality and Reliability Project

One area where universities and industry can link is in the area of power systems reliability and quality - key concepts in the commercial, industrial and public sector engineering environments. Prairie View A&M University (PVAMU) has established a collaborative relationship with the University of'Texas at Arlington (UTA), NASA/Johnson Space Center (JSC), and EP&C Engineering and Technology Group (EP&C) a small disadvantage business that specializes in power quality and engineering services. The primary goal of this collaboration is to facilitate the development and implementation of a Strategic Integrated power/Systems Reliability and Curriculum Enhancement Program. The objectives of first phase of this work are: (a) to develop a course in power quality and reliability, (b) to use the campus of Prairie View A&M University as a laboratory for the study of systems reliability and quality issues, (c) to provide students with NASA/EPC shadowing and Internship experience. In this work, a course, titled "Reliability Analysis of Electrical Facilities" was developed and taught for two semesters. About thirty seven has benefited directly from this course. A laboratory accompanying the course was also developed. Four facilities at Prairie View A&M University were surveyed. Some tests that were performed are (i) earth-ground testing, (ii) voltage, amperage and harmonics of various panels in the buildings, (iii) checking the wire sizes to see if they were the right size for the load that they were carrying, (iv) vibration tests to test the status of the engines or chillers and water pumps, (v) infrared testing to the test arcing or misfiring of electrical or mechanical systems.

Attia, John O.↗

NASA NTRS1994

Open system environments

An open system is defined as a system that implements open specifications for interfaces, services, and supporting formats to enable properly engineered applications software to be ported with minimal changes across a wide range of systems; and to interact with users in a style which facilitates user portability. Based on that definition, a reference model for an open system environment is presented.

Schulz, Fritz↗

NASA NTRSDate not supplied

Going Beyond Reliability to Robustness and Resilience in Space Life Support Systems

The words reliability, robustness, and resilience are often used interchangeably to describe tough and dependable systems but the distinctions between them suggest how to design more serviceable space systems. Reliability is simply the quality of consistently performing well. A system that dependably meets its design requirements in the specified environment is reliable. The designers may not consider themselves responsible for failures under unanticipated conditions. Robustness is the capability of performing without failure under a wide range of conditions, which can go beyond the expected range to include possible off-nominal conditions. Resilience is the ability to recover from or adapt to unanticipated damaging events, such as failures, accidents, external disruptions, and repurposing. Such changes can invalidate the usual operating assumptions and cause system failure. Reliability, robustness, and resilience describe dependable performance under increasingly difficult conditions, first the specified environment, then a wider possible environment, and finally unanticipated damaging conditions. These three qualities are increasingly desirable and increasingly difficult to achieve. Engineering for resilience would design systems that can ignore or repair failures, survive accidents, and recover from unanticipated disruptions. Increasing the resilience of space systems would greatly increase space crew safety. Improving reliability and robustness requires dealing with known problems, but improving resilience requires implementing a general approach to reducing the impact of unknown future events. The need for robustness and resilience has been stated for decades but little has been done. Systems designers often assume that they understand everything they need to know. The potential failures caused by changes, failures, accidents, unknown environments, and unknown unknowns can be ignored. Such overconfidence can lead to neglect of reliability, robustness, and resilience.

Harry W. Jones↗

NASA NTRSDate not supplied

Going Beyond Reliability to Robustness and Resilience in Space Life Support Systems

Harry W. Jones↗