Search NASA⌕ Search

SEARCH · Search NASA

Results for “Systems Engineering and Program Integration”

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 1,063 records · Page 59

SE and I system testability: The key to space system FDIR and verification testing

The key to implementing self-diagnosing design is a systems engineering task focused on design for testability concurrent with design for functionality. The design for testability process described here is the product of several years of DOD study and experience. Its application to the space station has begun on Work Package II under NASA and McDonnell direction. Other work package teams are being briefed by Harris Corporation with the hope of convincing them to embrace the process. For the purpose of this discussion the term testability is used to describe the systems engineering process by which designers can assure themselves and their reviewers that their designs are TESTABLE, that is they will support the downstream process of determining their functionality. Due to the complexity and density of present-day state-of-the-art designs, such as pipeline processors and high-speed integrated circuit technology, testability feature design is a critical requirement of the functional design process. A systematic approach to Space systems test and checkout as well as fault detection fault isolation reconfiguration (FDFIR) will minimize operational costs and maximize operational efficiency. An effective design for the testability program must be implemented by all contractors to insure meeting this objective. The process is well understood and technology is here to support it.

Barry, Thomas↗

Application of computational fluid dynamics to the design of the film cooled STME subscale nozzle for the National Launch System

The status of computational fluid dynamics (CFD) calculations for the Space Transportation Main Engine (STME) film/dump cooled nozzle design is presented, with an emphasis on the timely impact of CFD on the design of the sub-scale nozzle coolant system. The following aspects of the sub-scale coolant delivery system were analyzed with CFD: 1) a design trade study of a mechanical flow splitting device for uniform distribution of the subsonic cavity flow, 2) a design trade study of the subsonic cavity lip to achieve film integrity, and 3) an analysis of the primary flow interaction with the core/secondary coolant streams. All design calculations were performed with the Generalized Aerodynamic Simulation Program (GASP), a 3-D, multi-block, generalized Navier-Stokes code capable of solving with frozen, finite-rate or equilibrium chemical kinetics. The initial design of the subsonic cavity flow used square posts to distribute the sonic orifice jets into a uniform flow. Calculations for this design indicated that an unacceptable mal-distribution of film occurred. Design modifications involving curved and slotted posts were computed in an effort to uniformly distribute the secondary coolant flow. Analysis of these configurations showed that although the flowfield improved in uniformity, it was still unacceptable, especially at higher feed pressures. Results from these studies were then incorporated into a design that resulted in the insertion of a porous metal ring into the subsonic cavity. Subsequent water flow model studies showed that this concept was successful in uniformly distributing flow exiting the cavity. In addition to the design of the subsonic cavity, CFD was also used to analyze the secondary coolant lip and the primary flow interaction with the core/secondary coolant streams. A series of calculations were first performed to modify the subsonic cavity lip contour. The flow over the modified lip was then computed simultaneously with the primary injectors to determine the impact of the subsonic coolant stream on the primary slot jets. Pressure, temperature, velocity, and coolant mass fraction contours are presented for these configurations. Information is given in viewgraph form.

Garrett, Joseph L.↗

Achieving the Proper Balance Between Crew and Public Safety

A paramount objective of all human-rated launch and reentry vehicle developers is to ensure that the risks to both the crew onboard and the public are minimized within reasonable cost, schedule, and technical constraints. Past experience has shown that proper attention to range safety requirements necessary to ensure public safety must be given early in the design phase to avoid additional operational complexities or threats to the safety of people onboard, and the design engineers must give these requirements the same consideration as crew safety requirements. For human spaceflight, the primary purpose and operational concept for any flight safety system is to protect the public while maximizing the likelihood of crew survival. This paper will outline the policy considerations, technical issues, and operational impacts regarding launch and reentry vehicle failure scenarios where crew and public safety are intertwined and thus addressed optimally in an integrated manner. An overview of existing range and crew safety policy requirements will be presented. Application of these requirements and lessons learned from both the Space Shuttle and Constellation Programs will also be discussed. Using these past programs as examples, the paper will detail operational, design, and analysis approaches to mitigate and balance the risks to people onboard and in the public. Manned vehicle perspectives from the Federal Aviation Administration (FAA) and Air Force organizations that oversee public safety will be summarized as well. Finally, the paper will emphasize the need to factor policy, operational, and analysis considerations into the early design trades of new vehicles to help ensure that both crew and public safety are maximized to the greatest extent possible.

Gowan, John↗

Kedalion: NASA's Adaptable and Agile Hardware/Software Integration and Test Lab

NASA fs Kedalion engineering analysis lab at Johnson Space Center is on the forefront of validating and using many contemporary avionics hardware/software development and integration techniques, which represent new paradigms to heritage NASA culture. Kedalion has validated many of the Orion hardware/software engineering techniques borrowed from the adjacent commercial aircraft avionics solution space, with the intention to build upon such techniques to better align with today fs aerospace market. Using agile techniques, commercial products, early rapid prototyping, in-house expertise and tools, and customer collaboration, Kedalion has demonstrated that cost effective contemporary paradigms hold the promise to serve future NASA endeavors within a diverse range of system domains. Kedalion provides a readily adaptable solution for medium/large scale integration projects. The Kedalion lab is currently serving as an in-line resource for the project and the Multipurpose Crew Vehicle (MPCV) program.

Mangieri, Mark L.↗

Overview of the Development and Testing of the Heatshield for Extreme Entry Environment Technology (HEEET) TPS

Over the last 5 years, the Heatshield for Extreme Entry Environment Technology (HEEET) project has been working to mature a 3-D Woven Thermal Protection System (TPS) to Technical Readiness Level (TRL) 6 to support future NASA missions to destinations such as Venus and Saturn. A key aspect of the project has been the development of the manufacturing and integration processes/procedures necessary to build a heat shield utilizing the HEEET 3D-woven material. This has culminated in the building of a 1-meter diameter Engineering Test Unit (ETU) representative of what would be used for a Saturn probe. The present talk provides an overview of recent testing of NASA's Heatshield for Extreme Entry Environment Technology (HEEET) 3D Woven TPS. Under the current program, the ETU has been subjected to Thermal and Mechanical loads typical of deep space mission to Saturn. Thermal testing of HEEET coupons has performance up to 4,500 watts per centimeter squared at 5 atmospheres stagnation pressure and successful shear performance up to 3000 pascals at 1,650 watts per centimeter squared at 2.6 atmospheres pressure.

HEEET↗

Human Capabilities Assessments for Autonomous Missions: A Multi-Team Research Effort to Reduce Risk in the Human-System Integration Architecture for Future Deep-Space Missions

In future exploration missions beyond low earth-orbit, crew will have to execute complex operations and respond to off-nominal events, without real-time support from Mission Control. It is anticipated that increased reliance on automated systems, including human-centric vehicle and information architecture, will need to be designed to support the crew; increased risk to performance, health, and safety may occur if these are not implemented appropriately. The Human Factors and Behavioral Performance Element (HFBP) in the NASA Human Research Program supports research to characterize and mitigate such human health and performance risks, including the Risk of Adverse Outcome Due to Inadequate Human Systems Integration Architecture (HSIA). The HSIA risk addresses the integration of onboard capability and the crew roles and responsibilities necessary to enable the crew to respond effectively and efficiently in the increasingly autonomous mission operations environment. In 2017, HFBP released the “Human Capabilities Assessments for Autonomous Missions” (HCAAM) research topic to address HSIA related questions. HCAAM is a major NASA research effort that has assembled a multidisciplinary team from seven institutions to work closely with design and engineering efforts on research towards developing and refining human performance standards, guidelines and automation tools. The scientific focus is on quantitative assessment of human capabilities relevant to future deep-space missions during which earth/spacecraft communication is so delayed and intermittent that the crew must be able to function autonomously. The integrated strategy of the HCAAM project characterizes human capabilities and limitations related to potential performance decrements during long duration exploration mission spaceflight as relevant to both routine and complex task performance; defines system characteristics that reduce the likelihood or impact of potential decrements in human performance capabilities; performs integrated assessment of intelligent system responses within the context of an operational environment with relevant NASA tools, systems, and data structures in order to determine positive or negative interactions and validate recommended approaches; and proposes specific updates to existing standards and guidelines for inclusion in NASA handbooks for the design of future spacecraft intelligent systems that provide crew performance assessment/feedback, and to also serve as decision-support aids for the onboard crew (i.e., NASA-STD-3001, and NASA/SP-Human Integration Design Handbook (HIDH)). The scientific research vectors being addressed by the seven HCAAM teams include: - crew task performance (accuracy, efficiency) (crew + automation) - crew performance (accuracy, efficiency) - crew Situation Awareness - procedure design and multi-modal enhancement - concurrent tasking (mixed manual + some level of autonomy) - task handover - crew self-planning and time-lining - task design - trust in automation, real-time calibration - human multi-sensory feedback and guidance - human trust in on-board software-based intelligent assistants - virtual assistants The presentation will highlight plans and progress made in each of these research areas as well as the methods by which surrogate astronaut crews in the NASA JSC HERA spaceflight analog facility will function as human test subjects for all of the HCAAM research projects.

HCAAM VNSCOR↗

NASA’s Identified Risks of Adverse Outcomes Due to Inadequate Human Systems Integration Architecture in Human Spaceflight

The NASA Human System Risk Board (HSRB) has the overall responsibility for tracking the evolution of the top ~30 human system risks that it has identified to be associated with human spaceflight. As part of this process, the Board is charged with maintaining a consistent, integrated process to mitigate those risks, and developing evidence-based risk posture recommendations. One of the identified risks is due to inadequate human systems integration architecture (HSIA) and a driving factor of this risk is that given decreasing real-time ground support for execution of complex operations during future exploration missions, there is a possibility of adverse performance outcomes including that crew are unable to adequately respond to unanticipated critical malfunctions or detect safety critical procedural errors. The HSRB uses Directed Acyclic Graphs (DAGs) as a communication tool for describing how astronaut exposure to spaceflight hazards leads to meaningful mission-level health and performance outcomes and as the basis for understanding intermediate causal relationships between risk contributing factors and countermeasures that link hazards to outcomes. The HSIA risk DAG will be presented and described. Historically, critical malfunctions requiring Crew/MCC management occurred at a rate of 1.7 times per year for ISS averaged over the lifetime and 3-4 times per year in the burn in phase for the vehicle. These averages do not include EVA data, which greatly increases the incident rate. Prior experience from the Apollo program showed 10/11 crewed missions experienced significant anomalies where crew relied heavily on MCC expertise in real-time. These failure patterns are in line with those observed in other complex engineered systems (e.g., oil rigs, launch systems, commercial aviation, etc.) It is likely that general malfunction and error rates are > 10% for short duration missions (<30 days), based on past and current spaceflight operations data. Likelihood of adverse outcomes has the potential to increase as crew conduct work with new, complex systems and with less ground support. For Low Earth Orbit missions and Lunar missions less than 30 days, assuming minimal comm delays, disruptions and bandwidth limitations, malfunctions and errors can affect mission objectives and crew health but may be mitigated by ground support. For Lunar missions greater than 30 days and any potential Mars mission malfunctions and errors can have Loss of Crew and Loss of Mission consequences due to reduced ground support (communication delays, constraints and blackouts) for more complex operations, as well as reduced resupply and evacuation options.

Daniel M Buckland↗

Core Stage TVC Systems Engineering Challenges in Reusing Heritage Hardware

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Two actuators are used to move each engine in two planes perpendicular to one another (i.e., pitch and yaw). The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Core Auxiliary Power Unit (CAPU) is derived from the Orbiter Auxiliary Power Unit (APU). The Orbiter and Solid Rocket Booster APU turbines are powered by hot gas produced by catalyzed hydrazine decomposition. On the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. While direct reuse or slight modification of existing hardware may seem to be a triple-win for a program in cost, schedule, and technical risk mitigation, those benefits can only be realized when its degree of application in a new system is carefully and thoughtfully managed. The heritage hardware reuse should be prescribed within the heritage design capability and reuse environments must lie within the envelope of heritage qualification testing. Despite the significant test and flight experience of the Shuttle heritage hardware components, successful integration with the newly designed CS TVC components and incorporation into the stage design proved to be a challenge which required re-qualification of the heritage hardware as well as thorough integrated testing to support flight certification. Examples of the challenges that were overcome include: re-qualifying heritage hardware to survive new shock and vibration environments, certifying performance of extensively modified heritage hardware, regenerating design insight due to lack of available heritage vendor data, showing compliance to modern structural design standards, translation of heritage requirements for analog avionics to modern digital avionics, and interfacing heritage mechanical hardware with newly designed avionics. This paper is the second installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. This paper will discuss several engineering challenges encountered during the development process for SLS CS TVC and how they were successfully overcome to reach flight readiness.

Thrust Vector Control↗

Space Launch System: Core Stage Thrust Vector Control Systems Engineering Challenges in Reusing Heritage Hardware

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Two actuators are used to move each engine in two planes perpendicular to one another (i.e., pitch and yaw). The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Core Auxiliary Power Unit (CAPU) is derived from the Orbiter Auxiliary Power Unit (APU). The Orbiter and Solid Rocket Booster APU turbines are powered by hot gas produced by catalyzed hydrazine decomposition. On the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. While direct reuse or slight modification of existing hardware may seem to be a triple-win for a program in cost, schedule, and technical risk mitigation, those benefits can only be realized when its degree of application in a new system is carefully and thoughtfully managed. The heritage hardware reuse should be prescribed within the heritage design capability and reuse environments must lie within the envelope of heritage qualification testing. Despite the significant test and flight experience of the Shuttle heritage hardware components, successful integration with the newly designed CS TVC components and incorporation into the stage design proved to be a challenge which required re-qualification of the heritage hardware as well as thorough integrated testing to support flight certification. Examples of the challenges that were overcome include: re-qualifying heritage hardware to survive new shock and vibration environments, certifying performance of extensively modified heritage hardware, regenerating design insight due to lack of available heritage vendor data, showing compliance to modern structural design standards, translation of heritage requirements for analog avionics to modern digital avionics, and interfacing heritage mechanical hardware with newly designed avionics. This paper is the second installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. This paper will discuss several engineering challenges encountered during the development process for SLS CS TVC and how they were successfully overcome to reach flight readiness.

Thrust Vector Control↗

The Application of a Boundary Integral Equation Method to the Prediction of Ducted Fan Engine Noise

The prediction of ducted fan engine noise using a boundary integral equation method (BIEM) is considered. Governing equations for the BIEM are based on linearized acoustics and describe the scattering of incident sound by a thin, finite-length cylindrical duct in the presence of a uniform axial inflow. A classical boundary value problem (BVP) is derived that includes an axisymmetric, locally reacting liner on the duct interior. Using potential theory, the BVP is recast as a system of hypersingular boundary integral equations with subsidiary conditions. We describe the integral equation derivation and solution procedure in detail. The development of the computationally efficient ducted fan noise prediction program TBIEM3D, which implements the BIEM, and its utility in conducting parametric noise reduction studies are discussed. Unlike prediction methods based on spinning mode eigenfunction expansions, the BIEM does not require the decomposition of the interior acoustic field into its radial and axial components which, for the liner case, avoids the solution of a difficult complex eigenvalue problem. Numerical spectral studies are presented to illustrate the nexus between the eigenfunction expansion representation and BIEM results. We demonstrate BIEM liner capability by examining radiation patterns for several cases of practical interest.

Dunn, M. H.↗

Learning Lessons from the X-37 Project

The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite's White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with and turnaround maintenance performed. The fight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development. NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This recent partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of the X-37 effort, the team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff research and development and provides valuable experience to implement the exploration vision.

Turner, Susan↗

Ares I-X Flight Test - The Future Begins Here

In less than two years, the National Aeronautics and Space Administration (NASA) will launch the Ares I-X mission. This will be the first flight of the Ares I crew launch vehicle, which, together with the Ares V cargo launch vehicle, will eventually send humans to the Moon, Mars, and beyond. As the countdown to this first Ares mission continues, personnel from across the Ares I-X Mission Management Office (MMO) are finalizing designs and fabricating vehicle hardware for an April 2009 launch. This paper will discuss the hardware and programmatic progress of the Ares I-X mission. Like the Apollo program, the Ares launch vehicles will rely upon extensive ground, flight, and orbital testing before sending the Orion crew exploration vehicle into space with humans on board. The first flight of Ares I, designated Ares I-X, will be a suborbital development flight test. Ares I-X gives NASA its first opportunity to gather critical data about the flight dynamics of the integrated launch vehicle stack; understand how to control its roll during flight; better characterize the severe stage separation environments that the upper stage engine will experience during future operational flights; and demonstrate the first stage recovery system. NASA also will begin modifying the launch infrastructure and fine-tuning ground and mission operations, as the agency makes the transition from the Space Shuttle to the Ares/Orion system.

Davis, Stephan R.↗

CECE: A Deep Throttling Demonstrator Cryogenic Engine for NASA's Lunar Lander

As one of the first technology development programs awarded under NASA's Vision for Space Exploration, the Pratt & Whitney Rocketdyne (PWR) Deep Throttling, Common Extensible Cryogenic Engine (CECE) program was selected by NASA in November 2004 to begin technology development and demonstration toward a deep throttling, cryogenic Lunar Lander engine for use across multiple human and robotic lunar exploration mission segments with extensibility to Mars. The CECE program leverages the maturity and previous investment of a flight-proven hydrogen/oxygen expander cycle engine, the RL10, to develop and demonstrate an unprecedented combination of reliability, safety, durability, throttlability, and restart capabilities in a high-energy, cryogenic engine. NASA Marshall Space Flight Center and NASA Glenn Research Center personnel were integral design and analysis team members throughout the requirements assessment, propellant studies and the deep throttling demonstrator elements of the program. The testbed selected for the initial deep throttling demonstration phase of this program was a minimally modified RL10 engine, allowing for maximum current production engine commonality and extensibility with minimum program cost. In just nine months from technical program start, CECE Demonstrator No. 1 engine testing in April/May 2006 at PWR's E06 test stand successfully demonstrated in excess of 10:1 throttling of the hydrogen/oxygen expander cycle engine. This test provided an early demonstration of a viable, enabling cryogenic propulsion concept with invaluable system-level technology data acquisition toward design and development risk mitigation for both the subsequent CECE Demonstrator No. 2 program and to the future Lunar Lander Design, Development, Test and Evaluation effort.

Giuliano, Victor J.↗

High Voltage Hall Accelerator Propulsion System Development for NASA Science Missions

NASA Science Mission Directorates In-Space Propulsion Technology Program is sponsoring the development of a 3.8 kW-class engineering development unit Hall thruster for implementation in NASA science and exploration missions. NASA Glenn Research Center and Aerojet are developing a high fidelity high voltage Hall accelerator (HiVHAc) thruster that can achieve specific impulse magnitudes greater than 2,700 seconds and xenon throughput capability in excess of 300 kilograms. Performance, plume mappings, thermal characterization, and vibration tests of the HiVHAc engineering development unit thruster have been performed. In addition, the HiVHAc project is also pursuing the development of a power processing unit (PPU) and xenon feed system (XFS) for integration with the HiVHAc engineering development unit thruster. Colorado Power Electronics and NASA Glenn Research Center have tested a brassboard PPU for more than 1,500 hours in a vacuum environment, and a new brassboard and engineering model PPU units are under development. VACCO Industries developed a xenon flow control module which has undergone qualification testing and will be integrated with the HiVHAc thruster extended duration tests. Finally, recent mission studies have shown that the HiVHAc propulsion system has sufficient performance for four Discovery- and two New Frontiers-class NASA design reference missions.

Kamhawi, Hani↗

The OpenSE Cookbook: A Practical, Recipe Based Collection of Patterns, Procedures, and Best Practices for Executable Systems Engineering for the Thirty Meter Telescope

The OpenSE Cookbook is an open-sourced collection of patterns, procedures, and best practices targeted for systems engineers who seek guidance on applying model-based and executable systems engineering (MBSE) using SysML. Its content has emerged from the system level modeling effort on the European Framework Program 6 (FP6) and the Thirty Meter Telescope (TMT). The TMT MBSE approach applied the Executable Systems Engineering Method (ESEM) and the open-source Engineering Environment (OpenMBEE) to specify, analyze, and verify requirements of TMT’s Alignment and Phasing System (APS) and the Narrow Field Infrared Adaptive Optics System (NFIRAOS). In these applications, implicit dependencies are made explicit in a formal model through the use of ESEM, OpenMBEE, and SysML modeling constructs. The value proposition for applying this MBSE approach was to establish precise requirements and fine-grained traceability to system designs, and to verify key requirements beginning early in development. The integration of ESEM and the OpenMBEE tooling infrastructure (providing linked-data and web-operability) is a significant added value for the MBSE approach. The APS is responsible for the overall pre-adaptive optics wavefront quality, using starlight to measure wavefront errors and align the TMT optics. In the formally integrated and executable SysML model, simulations are performed to analyze the impact of changed requirements and verify specified constraints for various operational scenarios. The APS team used several modeling patterns to capture information such as the requirements, the operational scenarios, involved subsystems and their interaction points, the estimated or required time durations, and the mass and power consumption. Adaptive optics systems are designed to sense real-time atmospheric turbulence and correct the telescope’s optical beam to remove its effect. The system model for the adaptive optics operational modes was developed to capture sequence behaviors and operational scenarios to run Monte-Carlo simulations for verifying acquisition time, observing efficiency, and operational behavior requirements. The model is particularly useful for investigating the effect of parallelization, identifying interface issues, and re-ordering sequence acquisition tasks. A former version of the Cookbook (which is now updated to MBSE challenges, goals, and lessons learned) included modeling guidelines and conventions for all system aspects, hierarchy levels, and views, which were developed during for the Active Phasing Experiment (APE), an opto-mechatronical system technology demonstrator for the Extremely Large Telescope (ELT). The Cookbook utilizes the above mentioned system models as real-world case-studies to demonstrate and document the applications of the recipes, providing also instructional examples and addressing the available tooling support. The Cookbook is accompanied by a number of SysML models and aodel libraries which facilitate model authoring and maintenance. The Cookbook covers the different aspects of Systems Engineering such as management of Requirements, Design (behavior and structure), Interfaces, Interdisciplinary Integration, Analysis, Trade Studies, and Technical Resources. This paper presents the background, motivation, architecture, and highlights some key content of the Cookbook. For example, interface management, error budget management, requirements verification, Monte Carlo driven analysis, and timing analysis of operational scenarios. The paper discusses how the capabilities of OpenMBEE contributed significantly to the adoption of executable systems engineering.

Brower, Eric↗

Observing System Simulations for the AOS Mission

The Earth System Observatory (ESO) is NASA’s response to the recommendations of the 2017 Earth Sciences Decadal Survey conducted by the US National Academy of Sciences, Engineering and Medicine. The ESO is being conceived as a set of fully integrated missions addressing 4 main Earth science focus areas including aerosols, clouds, convection and precipitation (jointly re-ferred to as AOS, the Atmosphere Observing System). ESO ground breaking observations will provide critical measurements to address societally relevant problems in climate change, natural hazard mitiga-tion, fighting forest fires, and improving real-time agricultural processes. A critical element of the AOS observing strategy is to make extensive use of new passive and active sen-sors as well as of the so-called Program-of-Record (PoR), complemented by a fully integrated sub-orbital component. In order to achieve maximum benefit, all these observations need to be integrated into comprehensive observing and modeling/data assimilation systems. Such an approach requires compre-hensive model-data synthesis capabilities that needs to be conceived in conjunction with the space-based and suborbital components of AOS. In this presentation we will summarize the major science goals of AOS including cloud feedbacks, at-mospheric convection, emphasizing aerosol processes and aerosol radiative effects, and the synergistic aspects of clouds-precipitation-aerosol interactions. We will describe examples of the observing system simulation capabilities being developed for AOS, including global storm resolving nature runs, detailed instrument and retrieval simulators, as well as fast retrieval emulators for instrumenting climate models. This simulation environment, being developed under NASA’s open-source science initiative, will permit us to explore how AOS data will be used across space and time to better initialize forecasts and train modeling systems, and to infuse models and data assimilation systems with AOS data, well before launch.

Arlindo da Silva↗

Learning Lessons from the X-37 Project

The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite s White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with landing and turnaround maintenance performed. The Flight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development (R&D). NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of this effort, the X-37 team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff R&D and provides valuable experience to implement the Vision for Space Exploration.

Turner, Susan↗

Modeling in the State Flow Environment to Support Launch Vehicle Verification Testing for Mission and Fault Management Algorithms in the NASA Space Launch System

Analysis methods and testing processes are essential activities in the engineering development and verification of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS). Central to mission success is reliable verification of the Mission and Fault Management (M&FM) algorithms for the SLS launch vehicle (LV) flight software. This is particularly difficult because M&FM algorithms integrate and operate LV subsystems, which consist of diverse forms of hardware and software themselves, with equally diverse integration from the engineering disciplines of LV subsystems. M&FM operation of SLS requires a changing mix of LV automation. During pre-launch the LV is primarily operated by the Kennedy Space Center (KSC) Ground Systems Development and Operations (GSDO) organization with some LV automation of time-critical functions, and much more autonomous LV operations during ascent that have crucial interactions with the Orion crew capsule, its astronauts, and with mission controllers at the Johnson Space Center. M&FM algorithms must perform all nominal mission commanding via the flight computer to control LV states from pre-launch through disposal and also address failure conditions by initiating autonomous or commanded aborts (crew capsule escape from the failing LV), redundancy management of failing subsystems and components, and safing actions to reduce or prevent threats to ground systems and crew. To address the criticality of the verification testing of these algorithms, the NASA M&FM team has utilized the State Flow environment6 (SFE) with its existing Vehicle Management End-to-End Testbed (VMET) platform which also hosts vendor-supplied physics-based LV subsystem models. The human-derived M&FM algorithms are designed and vetted in Integrated Development Teams composed of design and development disciplines such as Systems Engineering, Flight Software (FSW), Safety and Mission Assurance (S&MA) and major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GN&C), Thrust Vector Control (TVC), liquid engines, and the astronaut crew office. Since the algorithms are realized using model-based engineering (MBE) methods from a hybrid of the Unified Modeling Language (UML) and Systems Modeling Language (SysML), SFE methods are a natural fit to provide an in depth analysis of the interactive behavior of these algorithms with the SLS LV subsystem models. For this, the M&FM algorithms and the SLS LV subsystem models are modeled using constructs provided by Matlab which also enables modeling of the accompanying interfaces providing greater flexibility for integrated testing and analysis, which helps forecast expected behavior in forward VMET integrated testing activities. In VMET, the M&FM algorithms are prototyped and implemented using the same C++ programming language and similar state machine architectural concepts used by the FSW group. Due to the interactive complexity of the algorithms, VMET testing thus far has verified all the individual M&FM subsystem algorithms with select subsystem vendor models but is steadily progressing to assessing the interactive behavior of these algorithms with LV subsystems, as represented by subsystem models. The novel SFE applications has proven to be useful for quick look analysis into early integrated system behavior and assessment of the M&FM algorithms with the modeled LV subsystems. This early MBE analysis generates vital insight into the integrated system behaviors, algorithm sensitivities, design issues, and has aided in the debugging of the M&FM algorithms well before full testing can begin in more expensive, higher fidelity but more arduous environments such as VMET, FSW testing, and the Systems Integration Lab7 (SIL). SFE has exhibited both expected and unexpected behaviors in nominal and off nominal test cases prior to full VMET testing. In many findings, these behavioral characteristics were used to correct the M&FM algorithms, enable better test coverage, and develop more effective test cases for each of the LV subsystems. This has improved the fidelity of testing and planning for the next generation of M&FM algorithms as the SLS program evolves from non-crewed to crewed flight, impacting subsystem configurations and the M&FM algorithms that control them. SFE analysis has improved robustness and reliability of the M&FM algorithms by revealing implementation errors and documentation inconsistencies. It is also improving planning efficiency for future VMET testing of the M&FM algorithms hosted in the LV flight computers, further reducing risk for the SLS launch infrastructure, the SLS LV, and most importantly the crew.

Trevino, Luis↗