SEARCH · Engineering Papers

Results for “Reliability and Integrity Management”

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 289 records · Page 16

All sources NASA NTRS DOE OSTI

NASA NTRS1998

Towards a Theory for Integration of Mathematical Verification and Empirical Testing

From the viewpoint of a project manager responsible for the V&V (verification and validation) of a software system, mathematical verification techniques provide a possibly useful orthogonal dimension to otherwise standard empirical testing. However, the value they add to an empirical testing regime both in terms of coverage and in fault detection has been difficult to quantify. Furthermore, potential cost savings from replacing testing with mathematical verification techniques cannot be realized until the tradeoffs and synergies can be formulated. Integration of formal verification with empirical testing is also difficult because the idealized view of mathematical verification providing a correctness proof with total coverage is unrealistic and does not reflect the limitations imposed by computational complexity of mathematical techniques. This paper first describes a framework based on software reliability and formalized fault models for a theory of software design fault detection - and hence the utility of various tools for debugging. It then describes a utility model for integrating mathematical and empirical techniques with respect to fault detection and coverage analysis. It then considers the optimal combination of black-box testing, white-box (structural) testing, and formal methods in V&V of a software system. Using case studies from NASA software systems, it then demonstrates how this utility model can be used in practice.

Lowry, Michael↗

NASA NTRS1990

IDEF5 Ontology Description Capture Method: Concept Paper

The results of research towards an ontology capture method referred to as IDEF5 are presented. Viewed simply as the study of what exists in a domain, ontology is an activity that can be understood to be at work across the full range of human inquiry prompted by the persistent effort to understand the world in which it has found itself - and which it has helped to shape. In the contest of information management, ontology is the task of extracting the structure of a given engineering, manufacturing, business, or logistical domain and storing it in an usable representational medium. A key to effective integration is a system ontology that can be accessed and modified across domains and which captures common features of the overall system relevant to the goals of the disparate domains. If the focus is on information integration, then the strongest motivation for ontology comes from the need to support data sharing and function interoperability. In the correct architecture, an enterprise ontology base would allow th e construction of an integrated environment in which legacy systems appear to be open architecture integrated resources. If the focus is on system/software development, then support for the rapid acquisition of reliable systems is perhaps the strongest motivation for ontology. Finally, ontological analysis was demonstrated to be an effective first step in the construction of robust knowledge based systems.

Menzel, Christopher P.↗

NASA NTRS2005

Smart Sensors' Role in Integrated System Health Management

During the last decade, there has been a major effort in the aerospace industry to reduce the cost per pond of payload and become competitive in the international market. Competition from Europe, Japan, and China has reduced this cost to almost a third from 1990 to 2000. This cost has leveled in recent years to an average price of around $12,000/pound of payload. One of NASA's goals is to promote the development of technologies to reduce this cost by a factor of 10 or more Exploration of space, specially manned exploration missions, involves very complex launch and flight vehicles, associated ground support systems, and extensive human support during all phases of the mission. When considering the Space Shuttle Program, we can see that vehicle and ground support systems' processing, operation, and maintenance represent a large percentage of the program cost and time. Reducing operating, processing and maintenance costs will greatly reduce the cost of Exploration programs. The Integrated System Health Management (ISHM) concept is one of the technologies that will help reduce these operating, processing and maintenance costs. ISHM is an integrated health monitoring system applicable to both flight and ground systems. It automatically and autonomously acquires information from sensors and actuators and processes that information using the ISHM-embedded knowledge. As a result, it establishes the health of the system based on the acquired information and its prior knowledge. When this concept is fully implemented, ISHM systems shall be able to perform failure prediction and remediation before actual hard failures occurs, preventing its costly consequences. Data sources, sensors, and their associated data acquisition systems, constitute the foundation of the system. A smart sensing architecture is required to support the acquisition of reliable, high quality data, required by the ISHM. A thorough definition of the smart sensor architectures, their embedded diagnostic agents, and communication protocols need to be established and standardized to allow the embedding and exchange of health information among sensors and ISHM. This workshop is aimed to foster the exchange of ideas and lessons learned between government, industry and academia to aid in the establishment of ISHM (and smart sensors) standards and guidelines as well as to identify present technology gaps that will have to be overcome to successfully achieve this goal.

Perotti, Jose M.↗

NASA NTRS2018

The Second European Service Module (ESM-2) Evolutions, Production and Challenges

This paper presents an overview of the Second European Service Module (ESM-2), the second in a series of European Service Modules produced as part of the Barter agreement between NASA and ESA for the Orion Program. The European Industrial consortium is led by the ESA prime contractor Airbus Defence and Space in Bremen. ESA and Airbus signed the ESM-2 contract on 16 February 2017, for this key element of the Orion Exploration Mission 2 (EM-2). EM-2 is the first crewed mission for Orion and will take astronauts farther into the solar system than humanity has ever travelled. EM-2 will also be a historic mission for Europe, as the ESM-2 will be the first European spacecraft to be part of a human transportation system carrying humans beyond low Earth orbit. ESM-2 is mainly a recurring production following ESM-1. Nevertheless, there are a number of important changes being implemented, for example, to incorporate upgrades to further enhance safety and reliability. The challenging delivery schedule for ESM-2 has driven the need to commence manufacturing prior to completion of the qualification on ESM-1. In addition, some requirement deviations and non-compliances approved for ESM-1 have resulted in modifications for ESM-2. In order to manage the competing constraints effectively, the ESM-2 Team has put in place a number of novel approaches to manage schedule, risk, and technical changes. Airbus has set up multi-functional teams according to an approach known as "Major Spacecraft Deliveries" consisting of quality assurance, engineering and procurement. The risk of starting manufacturing prior to qualification is managed through a special risk share agreement. This agreement necessitates rigorous risk reviews across the board for all manufacturing, assembly, integration and test milestones. The ESM-2 changes are managed by Configuration Management, but Airbus has also introduced the Technical Baseline Matrix to provide a transparent top-level overview of the changes from ESM-1 to ESM-2. The tool provides the basis for ESM-2 design and development needs, decisions, as well as the input for the Orion EM-2 Critical Design Review (CDR). The main technical evolutions, status of the production and the novel management approaches for ESM-2 are presented and discussed in the paper.

Orion European Service Module Programme↗

NASA NTRS1991

Formulation of a strategy for monitoring control integrity in critical digital control systems

Advanced aircraft will require flight critical computer systems for stability augmentation as well as guidance and control that must perform reliably in adverse, as well as nominal, operating environments. Digital system upset is a functional error mode that can occur in electromagnetically harsh environments, involves no component damage, can occur simultaneously in all channels of a redundant control computer, and is software dependent. A strategy is presented for dynamic upset detection to be used in the evaluation of critical digital controllers during the design and/or validation phases of development. Critical controllers must be able to be used in adverse environments that result from disturbances caused by an electromagnetic source such as lightning, high intensity radiated field (HIRF), and nuclear electromagnetic pulses (NEMP). The upset detection strategy presented provides dynamic monitoring of a given control computer for degraded functional integrity that can result from redundancy management errors and control command calculation error that could occur in an electromagnetically harsh operating environment. The use is discussed of Kalman filtering, data fusion, and decision theory in monitoring a given digital controller for control calculation errors, redundancy management errors, and control effectiveness.

Belcastro, Celeste M.↗

NASA NTRS1997

Case Study of an Object-Oriented System: EOSDIS

Mission to Planet Earth (MTPE) is a long-term NASA research mission to study the processes leading to global climate change. The Earth Observing System (EOS) is a NASA campaign of satellite observatories that are a major component of MTPE. The EOS Data and Information System (EOSDIS) is another component of MTPE that will provide the Earth science community with easy, affordable, and reliable access to Earth science data. EOSDIS is a distributed system, with major facilities at six Distributed Active Archive Centers (DAACS) located throughout the United States. The EOSDIS software architecture is being designed to receive, process, and archive several terabytes of science data on a daily basis. Thousands of science users and perhaps several hundred thousands of non-science users are expected to access the system. While there are many segments in EOSDIS (e.g., flight operations, network) this case study discusses the development of the science data processing segment (SDPS). We briefly review the architecture of the system, the goals of the SDPS, and the development progress to date. This study highlights key software development challenges, experiences integrating COTS, and the difficulties of managing a complex system development effort.

Behnke, Jeanne↗

NASA NTRS1991

Transportation technology program: Strategic plan

The purpose of this report is to define the technology program required to meet the transportation technology needs for current and future civil space missions. It is a part of an integrated plan, prepared by NASA in part in response to the Augustine Committee recommendations, to describe and advocate expanded and more aggressive efforts in the development of advanced space technologies. This expanded program will provide a technology basis for future space missions to which the U.S. aspires, and will help to regain technology leadership for the U.S. on a broader front. The six aspects of this integrated program/plan deal with focused technologies to support space sciences, exploration, transportation, platforms, and operations as well as provide a Research and Technology Base Program. This volume describes the technologies needed to support transportation systems, e.g., technologies needed for upgrades to current transportation systems and to provide reliable and efficient transportation for future space missions. The Office of Aeronautics, Exploration, and Technology (OAET) solicited technology needs from the major agency technology users and the aerospace industry community and formed a transportation technology team (appendix A) to develop a technology program to respond to those needs related to transportation technologies. This report addresses the results of that team activity. It is a strategic plan intended for use as a planning document rather than as a project management tool. It is anticipated that this document will be primarily utilized by research & technology (R&T) management at the various NASA Centers as well as by officials at NASA Headquarters and by industry in planning their corporate Independent Research and Development (IR&D) investments.

Source record↗

NASA NTRSDate not supplied

Developing Concepts of Operations Using Multi-Step Tool Techniques With Large Language Models

The National Aeronautics and Space Administration (NASA) Air Mobility Pathfinders (AMP) project is developing and evaluating concepts of operations (ConOps) for safe, secure, and scalable Urban Air Mobility (UAM) operations. The AMP project’s Operational Concepts, Architecture, and Requirements Integration (OCARI) Team is using a Model Based System Engineering (MBSE) approach for integration, interoperability, and traceability of Advanced Air Mobility (AAM) ecosystems centered around urban air taxi services. The team’s goal is to define structures and behaviors needed for system feasibility, readiness, and interoperability, establish a UAM knowledge base, and trace and validate assumptions and requirements relevant to AAM. NASA Langley Research Center (LaRC) is spearheading an innovative digital engineering approach to integrate, communicate, and facilitate the research of multi-modal transportation systems. The Knowledge-based Digital Platform (KbDP) is a concept being developed that ties the workflows of Project Managers (PM), Principal Investigators (PI), and System Engineers together across organizational boundaries. It does so through the management of an information database defined by mathematical, data science, and system engineering principles. Machine Learning (ML) algorithms play a key role in this concept by extracting meaningful knowledge from relational and graph databases, document repositories, and system artifacts, which the human user leverages to greatly improve the efficiency and effectiveness of their research. Recent advancements in the field of Large Language Models (LLMs), specifically models trained for tool use, such as Command-R , now allow for the reliable implementation of single-step and multi-step tool-centric systems. These techniques provide the LLM with a set of tools, in our case Python functions, that can be called on to answer a much wider range of questions compared to LLMs implemented using a traditional single-source or Retrieval Augmented Generation (RAG) approach. Through this method, the LLM can pull information from multiple data sources, such as relational or graph databases, document repositories, application programming interfaces (APIs), and SysML artifacts depending on the user’s question. The LLM can also output the information in a variety of different formats, using output generation tools, such as CSV, UML, or SysML artifacts. Additionally, tools can be assigned roles and can work together to provide answers to queries in an “agent” like approach, similar to that implemented by Microsoft’s AutoGen framework where different agents can converse with each other to accomplish tasks. Previously, our team developed a chatbot system with “agent like” functionality in the form of different “modes” the user could select from a user interface (UI), this architecture can be seen on the left in figure 1. Three different modes were implemented, the first mode allowed the LLM to utilize the structures and algorithms within a graph database to trace UAM requirements. The second mode gave the LLM access to a vector search capable of providing relevant information from thousands of document pages related to UAM ConOps and requirements. The third mode served as a general assistant where users could enter open-ended questions and custom prompts to utilize the LLM for different use-cases. This system improved the process surrounding generating and analyzing information related to UAM requirements, however, the implementation provided a clunky user experience. Users were required to know what mode to select within the UI in advance before entering their question to the selected tool. Moreover, the different tools were isolated from each other, they lacked bidirectional links that would allow for tools to collaborate to generate better responses. Our team is working on a new architecture, seen on the right in the below figure, with the goal to address many of the UX shortcomings of our original system while improving the accuracy and depth of responses from the LLM. This new system will automatically select the appropriate tool to use based off the user’s question. Each tool will be capable of calling on any of the other tools available to the LLM, resulting in a collaborative pipeline where tools can pass data between other tools until enough data is received to generate an answer to the user’s question. Using a locally deployed, open-source, LLM, the NASA OCARI team, in collaboration with Collins Aerospace, will implement a prototype application that will bridge knowledge across multiple sources to assist System Engineers (SEs) with requirements discovery and tracing, research question and use case identification, and assumption validation. Such a system will also allow SEs to more easily, and intuitively, explore the AAM ecosystem, ultimately improving the efficiency and effectiveness of the SE's research and decision-making processes surrounding ConOps development and validation. In this session, our team will provide a video demonstration of our new prototype architecture in action. We will also present an overview of our prototype system architecture and talk about its advantages over traditional LLM deployments along with how those advantages can provide additional value to the field of System Engineering.

systems engineering↗

NASA NTRSDate not supplied

Summary of Technical Interchange Meetings (TIMs) Designed to Enable Earth Independent Medical Operations (EIMO)

The Exploration Medical Capability Element (ExMC) in NASA’s Human Research Program hosted a series of TIMs in 2023-2024 designed to stimulate discussion around specific topics with the goal of enabling EIMO. In context of the thematic constituent elements of EIMO, namely pre-mission planning, acute/emergent/prolonged medical decision making, supply/resource management and task load management, subject matter experts from industry, academia and government (NASA and other Agencies) provided valuable and actionable guidance and recommendations. Earth-based medical experts will remain indispensable for pre-mission planning, however, management of acute/emergent medical contingencies will require a gradual transition of medical care and decision making from terrestrial to space-based assets to enable support of astronaut health and performance and reduce overall mission risk. Key to achieving these enhancements is providing an integrated data system platform capable of utilizing multiple data streams in concert with a variety of on-board databases and passive monitoring of video and wearable sensors to enable a multi-modal, agentic AI-based clinical decision support system (CDSS) to support crew medical officer (CMO) medical decision-making. The EIMO series of TIMs (I-V) have proven to be instructive and portend a significant paradigm shift will be necessary to maintain crew health and performance on exploration class missions. Importantly, since the expected paradigm shift will be significantly different from the methods of operation that have been employed for the majority of missions from the inception of human spaceflight to date, any proposed methods must be deployed in the setting of ongoing operations early and be “tested, reviewed and practiced” while reliable back-up is available to facilitate an Enterprise-wide level of comfort and acceptance. Serious constraints on data transmission coupled with a large and expanding universe of on-board medical informatics data streams will necessitate implementation of a CDSS to supplant the current reliance on support provided by ground-based SMEs. Establishment of trust in the system by CMO/crew and the ground-based medical support team will be essential. Co-development of a CDSS with industry partners will assure that state of the art tools can be employed, and industry efficiencies can be leveraged. Training regimens, materials and tools must evolve to be responsive (just-in-time training) and facilitate autonomous execution of procedures. Proficiency metrics should be established and be based on validated competencies or milestones as opposed to a prescribed number of training hours. Training should be prioritized for broad, translatable skills that have universal application across a variety of medical conditions. Repetition was deemed to be the key to achieving proficiency and emphasis should lie in procedural training which is known to extinguish more rapidly than diagnostic skills. Advanced tools, e.g., extended reality, can provide more realistic and effective training. Use of advanced probabilistic risk assessment tools will be essential to optimize the medical system capability while carefully balancing risk relative to mass/power/volume limitations. Importance of factoring use-life of medical supplies and maintaining awareness of redundancy and opportunity to re-purpose under off nominal situations was emphasized. Consideration of adopting optimized performance standards vs. “good-enough” performance thresholds is warranted. The use of legacy systems as opposed to creating new systems may be preferable. Managing task load and associated cognitive load will be essential to maintain operational safety and behavioral health. ExMC aspires to create a shared EIMO paradigm and strategic vision for advancing medical system design through novel technologies, training, protocols, and support capabilities, built upon the spirit of successful strategies and innovations over the past six decades of space medicine operations.

Jay Lemery↗

NASA NTRS1989

Microcomputer based controller for the Langley 0.3-meter Transonic Cryogenic Tunnel

Flow control of the Langley 0.3-meter Transonic Cryogenic Tunnel (TCT) is a multivariable nonlinear control problem. Globally stable control laws were generated to hold tunnel conditions in the presence of geometrical disturbances in the test section and precisely control the tunnel states for small and large set point changes. The control laws are mechanized as four inner control loops for tunnel pressure, temperature, fan speed, and liquid nitrogen supply pressure, and two outer loops for Mach number and Reynolds number. These integrated control laws have been mechanized on a 16-bit microcomputer working on DOS. This document details the model of the 0.3-m TCT, control laws, microcomputer realization, and its performance. The tunnel closed loop responses to small and large set point changes were presented. The controller incorporates safe thermal management of the tunnel cooldown based on thermal restrictions. The controller was shown to provide control of temperature to + or - 0.2K, pressure to + or - 0.07 psia, and Mach number to + or - 0.002 of a given set point during aerodynamic data acquisition in the presence of intrusive geometrical changes like flexwall movement, angle-of-attack changes, and drag rake traverse. The controller also provides a new feature of Reynolds number control. The controller provides a safe, reliable, and economical control of the 0.3-m TCT.

Balakrishna, S.↗

NASA NTRS1999

Lockheed Martin Skunk Works Single Stage to Orbit/Reusable Launch Vehicle

Lockheed Martin Skunk Works has compiled an Annual Performance Report of the X-33/RLV Program. This report consists of individual reports from all industry team members, as well as NASA team centers. This portion of the report is comprised of a status report of Lockheed Martin's contribution to the program. The following is a summary of the Lockheed Martin Centers involved and work reviewed under their portion of the agreement: (1) Lockheed Martin Skunk Works - Vehicle Development, Operations Development, X-33 and RLV Systems Engineering, Manufacturing, Ground Operations, Reliability, Maintainability/Testability, Supportability, & Special Analysis Team, and X-33 Flight Assurance; (2) Lockheed Martin Technical Operations - Launch Support Systems, Ground Support Equipment, Flight Test Operations, and RLV Operations Development Support; (3) Lockheed Martin Space Operations - TAEM and A/L Guidance and Flight Control Design, Evaluation of Vehicle Configuration, TAEM and A/L Dispersion Analysis, Modeling and Simulations, Frequency Domain Analysis, Verification and Validation Activities, and Ancillary Support; (4) Lockheed Martin Astronautics-Denver - Systems Engineering, X-33 Development; (5) Sanders - A Lockheed Martin Company - Vehicle Health Management Subsystem Progress, GSS Progress; and (6) Lockheed Martin Michoud Space Systems - X-33 Liquid Oxygen (LOX) Tank, Key Challenges, Lessons Learned, X-33/RLV Composite Technology, Reusable Cyrogenic Insulation (RCI) and Vehicle Health Monitoring, Main Propulsion Systems (MPS), Structural Testing, X-33 System Integration and Analysis, and Cyrogenic Systems Operations.

Source record↗

NASA NTRS2017

Considerations for an Integrated UAS CNS Architecture

The National Aeronautics and Space Administration (NASA) Glenn Research Center (GRC) is investigating revolutionary and advanced universal, reliable, always available, cyber secure and affordable Communication, Navigation, Surveillance (CNS) options for all altitudes of UAS operations. In Spring 2015, NASA issued a Call for Proposals under NASA Research Announcements (NRA) NNH15ZEA001N, Amendment 7 Subtopic 2.4. Boeing was selected to conduct a study with the objective to determine the most promising candidate technologies for Unmanned Air Systems (UAS) air-to-air and air-to-ground data exchange and analyze their suitability in a post-NextGen NAS environment. The overall objectives are to develop UAS CNS requirements and then develop architectures that satisfy the requirements for UAS in both controlled and uncontrolled air space. This contract is funded under NASAs Aeronautics Research Mission Directorates (ARMD) Aviation Operations and Safety Program (AOSP) Safe Autonomous Systems Operations (SASO) project and proposes technologies for the Unmanned Air Systems Traffic Management (UTM) service.There is a need for accommodating large-scale populations of Unmanned Air Systems (UAS) in the national air space. Scale obviously impacts capacity planning for Communication, Navitation, and Surveillance (CNS) technologies. For example, can wireless communications data links provide the necessary capacity for accommodating millions of small UASs (sUAS) nationwide? Does the communications network provide sufficient Internet Protocol (IP) address space to allow air traffic control to securely address both UAS teams as a whole as well as individual UAS within each team? Can navigation and surveillance approaches assure safe route planning and safe separation of vehicles even in crowded skies?Our objective is to identify revolutionary and advanced CNS alternatives supporting UASs operating at all altitudes and in all airspace while accurately navigating in the absence of navigational aids. These CNS alternatives must be reliable, redundant, always available, cyber-secure, and affordable for all types of vehicles including small UAS to large transport category aircraft. The approach will identify CNS technology candidates that can meet the needs of the range of UAS missions to specific air traffic management applications where they will be most beneficial and cost effective.

Templin, Fred L.↗

NASA NTRS2017

Considerations for an Integrated UAS CNS Architecture

The National Aeronautics and Space Administration (NASA) Glenn Research Center (GRC) is investigating revolutionary and advanced universal, reliable, always available, cyber secure and affordable Communication, Navigation, Surveillance (CNS) options for all altitudes of UAS operations. In Spring 2015, NASA issued a Call for Proposals under NASA Research Announcements (NRA) NNH15ZEA001N, Amendment 7 Subtopic 2.4. Boeing was selected to conduct a study with the objective to determine the most promising candidate technologies for Unmanned Air Systems (UAS) air-to-air and air-to-ground data exchange and analyze their suitability in a post-NextGen NAS environment. The overall objectives are to develop UAS CNS requirements and then develop architectures that satisfy the requirements for UAS in both controlled and uncontrolled air space. This contract is funded under NASAs Aeronautics Research Mission Directorates (ARMD) Aviation Operations and Safety Program (AOSP) Safe Autonomous Systems Operations (SASO) project and proposes technologies for the Unmanned Air Systems Traffic Management (UTM) service.There is a need for accommodating large-scale populations of Unmanned Air Systems (UAS) in the national air space. Scale obviously impacts capacity planning for Communication, Navigation, and Surveillance (CNS) technologies. For example, can wireless communications data links provide the necessary capacity for accommodating millions of small UASs (sUAS) nationwide? Does the communications network provide sufficient Internet Protocol (IP) address space to allow air traffic control to securely address both UAS teams as a whole as well as individual UAS within each team? Can navigation and surveillance approaches assure safe route planning and safe separation of vehicles even in crowded skies?Our objective is to identify revolutionary and advanced CNS alternatives supporting UASs operating at all altitudes and in all airspace while accurately navigating in the absence of navigational aids. These CNS alternatives must be reliable, redundant, always available, cyber-secure, and affordable for all types of vehicles including small UAS to large transport category aircraft. The approach will identify CNS technology candidates that can meet the needs of the range of UAS missions to specific air traffic management applications where they will be most beneficial and cost effective.

Templin, Fred L.↗

NASA NTRS1993

On-board B-ISDN fast packet switching architectures. Phase 2: Development. Proof-of-concept architecture definition report

For the next-generation packet switched communications satellite system with onboard processing and spot-beam operation, a reliable onboard fast packet switch is essential to route packets from different uplink beams to different downlink beams. The rapid emergence of point-to-point services such as video distribution, and the large demand for video conference, distributed data processing, and network management makes the multicast function essential to a fast packet switch (FPS). The satellite's inherent broadcast features gives the satellite network an advantage over the terrestrial network in providing multicast services. This report evaluates alternate multicast FPS architectures for onboard baseband switching applications and selects a candidate for subsequent breadboard development. Architecture evaluation and selection will be based on the study performed in phase 1, 'Onboard B-ISDN Fast Packet Switching Architectures', and other switch architectures which have become commercially available as large scale integration (LSI) devices.

Shyy, Dong-Jye↗

NASA NTRS2000

NPSS on NASA's IPG: Using CORBA and Globus to Coordinate Multidisciplinary Aeroscience Applications

Within NASA's High Performance Computing and Communication (HPCC) program, the NASA Glenn Research Center is developing an environment for the analysis/design of aircraft engines called the Numerical Propulsion System Simulation (NPSS). The vision for NPSS is to create a "numerical test cell" enabling full engine simulations overnight on cost-effective computing platforms. To this end, NPSS integrates multiple disciplines such as aerodynamics, structures, and heat transfer and supports "numerical zooming" between O-dimensional to 1-, 2-, and 3-dimensional component engine codes. In order to facilitate the timely and cost-effective capture of complex physical processes, NPSS uses object-oriented technologies such as C++ objects to encapsulate individual engine components and CORBA ORBs for object communication and deployment across heterogeneous computing platforms. Recently, the HPCC program has initiated a concept called the Information Power Grid (IPG), a virtual computing environment that integrates computers and other resources at different sites. IPG implements a range of Grid services such as resource discovery, scheduling, security, instrumentation, and data access, many of which are provided by the Globus toolkit. IPG facilities have the potential to benefit NPSS considerably. For example, NPSS should in principle be able to use Grid services to discover dynamically and then co-schedule the resources required for a particular engine simulation, rather than relying on manual placement of ORBs as at present. Grid services can also be used to initiate simulation components on parallel computers (MPPs) and to address inter-site security issues that currently hinder the coupling of components across multiple sites. These considerations led NASA Glenn and Globus project personnel to formulate a collaborative project designed to evaluate whether and how benefits such as those just listed can be achieved in practice. This project involves firstly development of the basic techniques required to achieve co-existence of commodity object technologies and Grid technologies; and secondly the evaluation of these techniques in the context of NPSS-oriented challenge problems. The work on basic techniques seeks to understand how "commodity" technologies (CORBA, DCOM, Excel, etc.) can be used in concert with specialized "Grid" technologies (for security, MPP scheduling, etc.). In principle, this coordinated use should be straightforward because of the Globus and IPG philosophy of providing low-level Grid mechanisms that can be used to implement a wide variety of application-level programming models. (Globus technologies have previously been used to implement Grid-enabled message-passing libraries, collaborative environments, and parameter study tools, among others.) Results obtained to date are encouraging: we have successfully demonstrated a CORBA to Globus resource manager gateway that allows the use of CORBA RPCs to control submission and execution of programs on workstations and MPPs; a gateway from the CORBA Trader service to the Grid information service; and a preliminary integration of CORBA and Grid security mechanisms. The two challenge problems that we consider are the following: 1) Desktop-controlled parameter study. Here, an Excel spreadsheet is used to define and control a CFD parameter study, via a CORBA interface to a high throughput broker that runs individual cases on different IPG resources. 2) Aviation safety. Here, about 100 near real time jobs running NPSS need to be submitted, run and data returned in near real time. Evaluation will address such issues as time to port, execution time, potential scalability of simulation, and reliability of resources. The full paper will present the following information: 1. A detailed analysis of the requirements that NPSS applications place on IPG. 2. A description of the techniques used to meet these requirements via the coordinated use of CORBA and Globus. 3. A description of results obtained to date in the first two challenge problems.

Lopez, Isaac↗

NASA NTRS1993

Integrated risk management

The purpose of this report is to first present a basis or foundation for the building of an integrated risk management plan and them to present the plan. The integration referred to is across both the temporal and the hierarchical dimensions. Complexity, consequence, and credibility seem to be driving the need for the consideration of risk. Reduction of personal bias and reproducibility of the decision making process seem to be driving the consideration of a formal risk plan. While risk can be used as either a selection tool or a control tool, this paper concentrates on the selection usage. Risk relies on stated purpose. The tightness of the definition of purpose and success is directly reflected in the definition and control of risk. Much of a risk management plan could be designed by the answers to the questions of why, what, who, when, and where. However, any plan must provide the following information about a threat or risk: likelihood, consequence, predictability, reliability, and reproducibility. While the environment at NASA is seen as warm, but not hot, for the introduction of a risk program, some encouragement is seen if the following problems are addressed: no champion, no commitment of resource, confused definitions, lack of direction and focus, a hard sell, NASA culture, many choices of assessment methods, and cost. The plan is designed to follow the normal method of doing work and is structured to follow either the work break down structure or a functional structure very well. The parts of the plan include: defining purpose and success, initial threat assessment, initial risk assessment, reconciling threats and parameters, putting part of the information down and factoring the information back into the decision process as it comes back up, and developing inferences. Two major suggestions are presented. One is to build an office of risk management to be used as a resource by managers in doing the risk process. Another is to form a pilot program to try out the details in the plan and modify the method where needed.

Hunsucker, J. L.↗

NASA NTRSDate not supplied

Transitioning a Flexible and Scalable Satellite Ground Station Observation Network (GSON) Framework to an Operational Environment

Obtaining accurate and timely satellite observations is of paramount importance in fields like disaster management, weather diagnoses/forecasting, and Earth Sciences remote sensing. Stored mission data (SMD), from low Earth orbiting (LEO) satellite sensors, provides important observations for these fields and applications, however data access to SMD can be delayed from one and half hours to three hours from the time the observations were made. This data latency poses a significant impact on data product optimal use. We developed a Ground Station Observation Network (GSON) that utilizes commercial ground station as a service (GSaaS) providers to acquire low latency direct broadcast (DB) data from AQUA, SNPP, and JPSS-1 satellites using antennas located in strategic locations around the world. We will discuss techniques to improve the deployment efficiency and code reliability and quality of the GSON framework. Topics include right-sizing and containerization of the code to facilitate integration and adaptation with continuous delivery (CD) pipeline, locating non-code assets in referenceable repositories separated from code, adaptation of pipelines as code and simplification of CD, intersecting with code quality tests and checks as part of the pipeline execution and deployment, and establishing distributed repositories, registries, and system identities in a way that mitigates compromise to the CD pipeline. These techniques enable deployment of processing systems that are both highly specific but also dynamically modifiable. This new class of system allows for a flexible and scalable deployment while avoiding the “black box” issues that can plague large system deployments.

cluster↗

NASA NTRSDate not supplied

Rapid Spacecraft Payload Development: In-Orbit Demonstration of Flight Software Reuse, Scalability, and Dependability

As space mission design trends towards shared, multi-mission platforms and high-performance onboard computing architectures, the number of spacecraft launched into operation is also steadily rising. Through ridesharing, spacecraft miniaturization, and other cost-reduction measures, the barriers to space are lowering, resulting in compounded growth in the amount of flight software being deployed. To meet the needs of both the growing quantity and evolving nature of spacecraft, flight software design must accordingly adapt to support more efficient development, solutions to computational resource-sharing, and software reusability. This paper focuses on a software payload demonstrating several core technologies that improve the state-of-the-art in these identified areas. Launched into low-earth orbit in January 2022, our software payload was conceived, designed, and delivered in a span of merely two months. It was developed on top of the NASA core Flight System (cFS) framework and the Distributed Spacecraft Autonomy (DSA) Comm cFS application, which translates cFS software bus messages across a Data Distribution Service (DDS) network. The flight software, packaged in Linux container images, was deployed as one of 18 flight applications managed through the Unibap SpaceCloud Framework. The applications were run on a Unibap iX5-102 radiation-tolerant payload computer, hosted on the D-Orbit SCV-004 spacecraft as part of an ESA-sponsored in-orbit technology test. Our payload, referred to as the DSA D-Orbit software, demonstrates the reusability of the DSA Comm app in a substantially different context and purpose as its original mission. Comm’s original design goal was to reliably distribute messages between spacecraft swarms of arbitrary size and dynamic network topology. However, we leverage this same functionality to introduce redundancy and opportunistic parallel data processing in the context of a representative onboard image processing workload. This adaptive mission architecture was enabled in part by the SpaceCloud Framework’s use of container virtualization as the payload integration interface. By using a base container image with common high-level language runtimes and libraries, we were able to rapidly design, develop, and validate our image processing application without many of the technological barriers common to flight software development. We present details the goals, approach, results, and lessons learned through this technology demonstration experiment and contextualize those observations against present and future challenges in spacecraft software development.

computer programming↗