Search NASASearch

SEARCH · Search NASA

Results for “Configuration 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.

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

At least 91 records · Page 5

Making automated computer program documentation a feature of total system design

It is pointed out that in large-scale computer software systems, program documents are too often fraught with errors, out of date, poorly written, and sometimes nonexistent in whole or in part. The means are described by which many of these typical system documentation problems were overcome in a large and dynamic software project. A systems approach was employed which encompassed such items as: (1) configuration management; (2) standards and conventions; (3) collection of program information into central data banks; (4) interaction among executive, compiler, central data banks, and configuration management; and (5) automatic documentation. A complete description of the overall system is given.

Wolf, A. W.

SSC Engineering Analysis

A package for the automation of the Engineering Analysis (EA) process at the Stennis Space Center has been customized. It provides the ability to assign and track analysis tasks electronically, and electronically route a task for approval. It now provides a mechanism to keep these analyses under configuration management. It also allows the analysis to be stored and linked to the engineering data that is needed to perform the analysis (drawings, etc.). PTC s (Parametric Technology Corp o ration) Windchill product was customized to allow the EA to be created, routed, and maintained under configuration management. Using Infoengine Tasks, JSP (JavaServer Pages), Javascript, a user interface was created within the Windchill product that allows users to create EAs. Not only does this interface allow users to create and track EAs, but it plugs directly into the out-ofthe- box ability to associate these analyses with other relevant engineering data such as drawings. Also, using the Windchill workflow tool, the Design and Data Management System (DDMS) team created an electronic routing process based on the manual/informal approval process. The team also added the ability for users to notify and track notifications to individuals about the EA. Prior to the Engineering Analysis creation, there was no electronic way of creating and tracking these analyses. There was also a feature that was added that would allow users to track/log e-mail notifications of the EA.

Ryan, Harry

Predicting Airport Runway Configurations for Decision-Support Using Supervised Learning

One of the most challenging tasks for air traffic controllers is runway configuration management (RCM). It deals with the optimal selection of runways to operate on (for arrivals and departures) based on traffic, surface wind speed, wind direction, other environmental variables, noise constraints, and several other airport-specific factors. It affects the efficiency of the National Airspace System (NAS) and both surface and airspace operations can benefit from better understanding future runway configurations. In this paper, we present a comprehensive implementation of predictive models for runway configuration estimation from large volumes of historical data. Specifically, operational data from two full years (2018 and 2019) is collected, analyzed, and fused together to build the data product used in this work. The data set differs from prior work in the field in terms of its scope, resolution, and variety of factors collected and considered. Meteorological data is collected from two different sources – current weather conditions from METAR (Meteorological Terminal Aviation Routine Weather Report) and forecast weather conditions from Localized Aviation MOS Program (LAMP). Operational data from the Federal Aviation Administration (FAA) Aviation System Performance Metrics (ASPM) related to scheduled and actual number of arrivals and departures, average taxi times, etc. are collected. NASA’s Sherlock Data Warehouse is used to identify critical information such as go-arounds, and other events that might impact RCM decision-making. All data is collected and aggregated over 15-minute intervals throughout the two years. This provides a resolution like the timescales that might be necessary for runway configuration management decision-making. A variety of supervised learning algorithms are tested including Support Vector Machine, Random Forest, Gradient Boosting, etc. including tuning of the model hyperparameters. The modeling process is applied and presented on two representative U.S. airports – Charlotte Douglas International Airport (KCLT) and Denver International Airport (KDEN). The two airports present different levels of complexity in terms of the total number of configurations used and provide a balanced perspective on the generalizability of the developed approach to other airports in the NAS. Initial results are promising (F1 score of 0.91 at KCLT and 0.83 at KDEN) for data in the test set. The final paper will contain a comprehensive comparison between different models and model building strategies as well as further refined results. Most important predictors for each airport will be identified along with a discussion and recommendations on adapting the framework to other scenarios.

Tejas G Puranik

Digital Archive Issues from the Perspective of an Earth Science Data Producer

Contents include the following: Introduction. A Producer Perspective on Earth Science Data. Data Producers as Members of a Scientific Community. Some Unique Characteristics of Scientific Data. Spatial and Temporal Sampling for Earth (or Space) Science Data. The Influence of the Data Production System Architecture. The Spatial and Temporal Structures Underlying Earth Science Data. Earth Science Data File (or Relation) Schemas. Data Producer Configuration Management Complexities. The Topology of Earth Science Data Inventories. Some Thoughts on the User Perspective. Science Data User Communities. Spatial and Temporal Structure Needs of Different Users. User Spatial Objects. Data Search Services. Inventory Search. Parameter (Keyword) Search. Metadata Searches. Documentation Search. Secondary Index Search. Print Technology and Hypertext. Inter-Data Collection Configuration Management Issues. An Archive View. Producer Data Ingest and Production. User Data Searching and Distribution. Subsetting and Supersetting. Semantic Requirements for Data Interchange. Tentative Conclusions. An Object Oriented View of Archive Information Evolution. Scientific Data Archival Issues. A Perspective on the Future of Digital Archives for Scientific Data. References Index for this paper.

Barkstrom, Bruce R.

Directed Acyclic Graph Guidance Documentation

For over a decade, the National Aeronautics and Space Administration (NASA) has tracked and configuration-managed approximately 30 risks to astronaut health and performance that occur before, during and after spaceflight. The Human System Risk Board (HSRB), a Health and Medical Technical Authority (HMTA) Board at NASA Johnson Space Center, is the entity responsible for identifying, assessing, analyzing, and monitoring the official understanding of the risk or risk posture for each of the Human System Risks and determining – based on evaluation of the available evidence – when that risk posture changes. The ultimate purpose of tracking and researching these risks is to find ways to reduce the risk that astronaut crews face during spaceflight. Historically, research, development and operations relevant to one risk have been conducted in isolation from other risks; these individual risk ‘silos’ enabled initial characterization of each specific risk. In spaceflight however, the impact of exposure to risk for astronaut crews is cumulative, and not independent of exposures or other risks, as all the adverse effects of the spaceflight environment begin at launch, continue throughout the duration of the mission and in some cases across the lifetime of the crews. In January of 2020, the HSRB at NASA embarked on a pilot project designed to assess the potential value of causal diagramming as a tool to facilitate understanding these cumulative and interdependent effects as applied within Human System Risk management. This process uses directed acyclic graphs as a means of formalizing a shared mental model of the causal flow of risk among Risk Board stakeholders. Initially this model was to improve communication among those stakeholders, but the potential value exceeds communication alone. Formalization of the process for creating these causal diagrams will enable the creation of a composite risk network that is vetted by members of the NASA community and configuration managed. The causal diagrams are formulated as directed acyclic graphs (DAGs) to function as a type of knowledge graph for reference for the board and its stakeholders. This document outlines the pilot process, the standardized approaches, and guidance for risk custodian teams when creating and updating DAGs as a part of the NASA Human System Risk Management process.

Risk

Spaceflight Ground Support Equipment Reliability & System Safety Data

Presented were Reliability Analysis, consisting primarily of Failure Modes and Effects Analysis (FMEA), and System Safety Analysis, consisting of Preliminary Hazards Analysis (PHA), performed to ensure that the CoNNeCT (Communications, Navigation, and Networking re- Configurable Testbed) Flight System was safely and reliably operated during its Assembly, Integration and Test (AI&T) phase. A tailored approach to the NASA Ground Support Equipment (GSE) standard, NASA-STD-5005C, involving the application of the appropriate Requirements, S&MA discipline expertise, and a Configuration Management system (to retain a record of the analysis and documentation) were presented. Presented were System Block Diagrams of selected GSE and the corresponding FMEA, as well as the PHAs. Also discussed are the specific examples of the FMEAs and PHAs being used during the AI&T phase to drive modifications to the GSE (via "redlining" of test procedures, and the placement of warning stickers to protect the flight hardware) before being interfaced to the Flight System. These modifications were necessary because failure modes and hazards were identified during the analysis that had not been properly mitigated. Strict Configuration Management was applied to changes (whether due to upgrades or expired calibrations) in the GSE by revisiting the FMEAs and PHAs to reflect the latest System Block Diagrams and Bill Of Material. The CoNNeCT flight system has been successfully assembled, integrated, tested, and shipped to the launch site without incident. This demonstrates that the steps taken to safeguard the flight system when it was interfaced to the various GSE were successful.

Fernandez, Rene

Directed Acyclic Graphs: A Tool for Understanding the NASA Human Spaceflight System Risks - Human System Risk Board

For over a decade, the National Aeronautics and Space Administration (NASA) has tracked and configuration-managed approximately 30 risks to astronaut health and performance that occur before, during and after spaceflight. The Human System Risk Board (HSRB), a Health and Medical Technical Authority (HMTA) Board at NASA Johnson Space Center, is the entity responsible for identifying, assessing, analyzing, and monitoring the official understanding of the risk or risk posture for each of the Human System Risks and determining – based on evaluation of the available evidence – when that risk posture changes. The ultimate purpose of tracking and researching these risks is to find ways to reduce the risk that astronaut crews face during spaceflight. Historically, research, development and operations relevant to one risk have been conducted in isolation from other risks; these individual risk ‘silos’ enabled initial characterization of each specific risk. In spaceflight however, the impact of exposure to risk for astronaut crews is cumulative, and not independent of exposures or other risks, as all the adverse effects of the spaceflight environment begin at launch, continue throughout the duration of the mission and in some cases across the lifetime of the crews. In January of 2020, the HSRB at NASA embarked on a pilot project designed to assess the potential value of causal diagramming as a tool to facilitate understanding of these cumulative and interdependent effects as applied within Human System Risk management. This process uses directed acyclic graphs as a means of formalizing a shared mental model of the causal flow of risk among Risk Board stakeholders. Initially this model was to improve communication among those stakeholders, but the potential value exceeds communication alone. The causal diagrams are formulated as directed acyclic graphs (DAGs) to function as a type of knowledge graph for reference for the board and its stakeholders. This document is a sister document to NASA/TM 20220006812 Directed Acyclic Graph Guidance Documentation (1). In that document, the basic guidance for creating and standardizing directed acyclic graphs as tools for cross-risk analysis is provided. This document contains the initial configuration managed DAGs that were created as a result of applying those principles. These initial versions were accepted by the HSRB in January of 2022. Each of the Human System Risks are represented by a DAG that has been reviewed by the larger Human Health and Performance community at NASA including life scientists, physical scientists, physicians, nurses, pharmacists, exercise specialists and more. These results show the starting point for Human System Risk DAGs as shared mental models and communication aids across the boundaries of the various expertise needed to understand and mitigate the human risks in spaceflight. Because they are a starting point, each of these DAGs can be expected to change over time as new or refined evidence becomes available. The process for updating these DAGs can be found in the JSC-66705 Human System Risk Management Plan (2) that is publicly available on the NASA Technical Reports Server.

Erik L. Antonsen

Guidance and Control Software Project Data - Volume 1: Planning Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.

Hayhurst, Kelly J.

Performance monitor system functional simulator, environmental data, orbiter 101(HFT)

Information concerning the environment component of the space shuttle performance monitor system simulator (PMSS) and those subsystems operational on the shuttle orbiter 101 used for horizontal flight test (HFT) is provided, along with detailed data for the shuttle performance monitor system (PMS) whose software requirements evolve from three basic PMS functions: (1) fault detection and annunciation; (2) subsystem measurement management; and (3) subsystem configuration management. Information relative to the design and operation of Orbiter systems for HFT is also presented, and the functional paths are identified to the lowest level at which the crew can control the system functions. Measurement requirements are given which are necessary to adequately monitor the health status of the system. PMS process requirements, relative to the measurements which are necessary for fault detection and annunciation of a failed functional path, consist of measurement characteristics, tolerance limits, precondition tests, and correlation measurements.

Parker, F. W.

Management approach recommendations. Earth Observatory Satellite system definition study (EOS)

Management analyses and tradeoffs were performed to determine the most cost effective management approach for the Earth Observatory Satellite (EOS) Phase C/D. The basic objectives of the management approach are identified. Some of the subjects considered are as follows: (1) contract startup phase, (2) project management control system, (3) configuration management, (4) quality control and reliability engineering requirements, and (5) the parts procurement program.

Source record

Comparative thermal analysis of alternate Cryogenic Fluid Management Experiment (CFME) configurations

The Cryogenic Fluid Management Experiment (CFME) was analyzed to assess the feasibility and advisability of deleting the vapor cooled shield (VCS) from the baseline CFME insulation and pressure control system. Two alternate concepts of CFME insulation and pressure control, neither of which incorporated the VCS, were investigated. The first concept employed a thermodynamic vent system (TVS) to throttle the flow through an internal wall mounted heat exchanger (HX) within the pressure vessel to decrease boiloff and pressure rise rate, while the second concept utilized a TVS without an internal heat exchanger. Only the first concept was viable. Its performance was assessed for a seven day mission and found to be satisfactory. It was also concluded that VCS development costs would be greater than for an internal HX installation. Based upon the above comparisons, the HX was recommended as a replacement for the VCS.

Merino, F.

Mission Control Center (MCC) System Specification for the Shuttle Orbital Flight Test (OFT) Timeframe

System specifications to be used by the mission control center (MCC) for the shuttle orbital flight test (OFT) time frame were described. The three support systems discussed are the communication interface system (CIS), the data computation complex (DCC), and the display and control system (DCS), all of which may interfere with, and share processing facilities with other applications processing supporting current MCC programs. The MCC shall provide centralized control of the space shuttle OFT from launch through orbital flight, entry, and landing until the Orbiter comes to a stop on the runway. This control shall include the functions of vehicle management in the area of hardware configuration (verification), flight planning, communication and instrumentation configuration management, trajectory, software and consumables, payloads management, flight safety, and verification of test conditions/environment.

Source record

SQL-RAMS

SQL-RAMS (where "SQL" signifies Structured Query Language and "RAMS" signifies Rocketdyne Automated Management System) is a successor to the legacy version of RAMS a computer program used to manage all work, nonconformance, corrective action, and configuration management on rocket engines and ground support equipment at Stennis Space Center. The legacy version resided in the FileMaker Pro software system and was constructed in modules that could act as stand-alone programs. There was little or no integration among modules. Because of limitations on file-management capabilities in FileMaker Pro, and because of difficulty of integration of FileMaker Pro with other software systems for exchange of data using such industry standards as SQL, the legacy version of RAMS proved to be limited, and working to circumvent its limitations too time-consuming. In contrast, SQL-RAMS is an integrated SQL-server-based program that supports all data-exchange software industry standards. Whereas in the legacy version, it was necessary to access individual modules to gain insight to a particular work-status documents, SQL-RAMS provides access through a single-screen presentation of core modules. In addition, SQL-RAMS enable rapid and efficient filtering of displayed statuses by predefined categories and test numbers. SQL-RAMS is rich in functionality and encompasses significant improvements over the legacy system. It provides users the ability to perform many tasks which in the past required administrator intervention. Additionally many of the design limitations have been corrected allowing for a robust application that is user centric.

Alfaro, Victor O.

SQL-RAMS

SQL-RAMS (where "SQL" signifies Structured Query Language and "RAMS" signifies Rocketdyne Automated Management System) is a successor to the legacy version of RAMS -- a computer program used to manage all work, nonconformance, corrective action, and configuration management on rocket engines and ground support equipment at Stennis Space Center. The legacy version resided in the File-Maker Pro software system and was constructed in modules that could act as standalone programs. There was little or no integration among modules. Because of limitations on file-management capabilities in FileMaker Pro, and because of difficulty of integration of FileMaker Pro with other software systems for exchange of data using such industry standards as SQL, the legacy version of RAMS proved to be limited, and working to circumvent its limitations too time-consuming. In contrast, SQL-RAMS is an integrated SQL-server-based program that supports all data-exchange software industry standards. Whereas in the legacy version, it was necessary to access individual modules to gain insight into a particular workstatus document, SQL-RAMS provides access through a single-screen presentation of core modules. In addition, SQL-RAMS enables rapid and efficient filtering of displayed statuses by predefined categories and test numbers. SQL-RAMS is rich in functionality and encompasses significant improvements over the legacy system. It provides users the ability to perform many tasks, which in the past required administrator intervention. Additionally, many of the design limitations have been corrected, allowing for a robust application that is user centric.

Alfaro, Victor O.

SCDM in a Distributed Environment

The Software Configuration Management (SCM) of the Space Launch Initiative (SLI) Advanced Engineering Environment (AEE) products is performed in a distributed environment-meaning the activities performed during the project lifecycle are across numerous NASA Centers, facilities, organizations, colleges and industry. SCM is the glue that holds the project and products together-especially in a distributed environment. It identifies, controls, accounts, and verified the details of the products; the schedule of activities; the assigned responsibilities; and the required resources, including staff, tools, and computer facilities. Data/document management (DM) captures and conveys the SCM and project efforts. SCM and DM are integrally linked; hence, Software Configuration and Data Management (SCDM). This paper discusses one team's challenges in implementing SCDM in a distributed environment. The distributed nature of the project introduces new opportunities for moving SCDM to the next level of usefulness in today's high-tech development arena. The lessons learned from the implementation of distributed SCDM in support of the SLI AEE Project provide valuable information for future implementations of SCM and DM.

Crowley, Sandra L.

TPSAS-NF1676L-12441-DND

The increasing presence of airport surface surveillance technologies has spawned a strong interest in airport surface traffic management research; the vast majority has assumed that the airport’s runway configuration is known and constant. Tactical Runway Configuration Management (TRCM), one component of NASA’s System Oriented Runway Management concept, plans the airport configuration to optimize traffic efficiency for the forecast weather, traffic, and other factors. While planning runway configuration can provide benefit and is required by other automation concepts, larger benefits are possible by planning other airport configuration decisions, such as runway assignment policies, that are currently made manually by controllers. A laboratory prototype of the TRCM algorithm which selects optimal airport configuration schedules has been implemented and studied within a simulation environment. The presentation will describe simulation results for several airports, under various weather and traffic conditions. The sequence of airport configurations recommended by TRCM result in significantly less delay than the airport configurations that were actually used by controllers, illustrating both the potential benefit from airport configuration optimization and the ability of TRCM to provide effective airport configuration schedules. The application to several, distinct airports demonstrates the approach is capable of handling the differences between airports with a common algorithm, while providing decision support that respects the current procedures at those airports. Consequently, TRCM is able to be deployed to any airport within the current National Airspace System. The TRCM algorithmic approach is also extensible to future operational scenarios. NASA is in the process of transferring the initial TRCM technology to the FAA. Future research will extend the concept and algorithm to provide coordinated plans for metroplex airports and study NextGen applications.

Stephen Atkins

TPSAS-NF1676L-12263-DND

The increasing presence of airport surface surveillance technologies has spawned a strong interest in airport surface traffic management research; the vast majority has assumed that the airport’s runway configuration is known and constant. Tactical Runway Configuration Management (TRCM), one component of NASA’s System Oriented Runway Management concept, plans the airport configuration to optimize traffic efficiency for the forecast weather, traffic, and other factors. While planning runway configuration can provide benefit and is required by other automation concepts, larger benefits are possible by planning other airport configuration decisions, such as runway assignment policies, that are currently made manually by controllers. A laboratory prototype of the TRCM algorithm which selects optimal airport configuration schedules has been implemented and studied within a simulation environment. The presentation will describe simulation results for several airports, under various weather and traffic conditions. The sequence of airport configurations recommended by TRCM result in significantly less delay than the airport configurations that were actually used by controllers, illustrating both the potential benefit from airport configuration optimization and the ability of TRCM to provide effective airport configuration schedules. The application to several, distinct airports demonstrates the approach is capable of handling the differences between airports with a common algorithm, while providing decision support that respects the current procedures at those airports. Consequently, TRCM is able to be deployed to any airport within the current National Airspace System. The TRCM algorithmic approach is also extensible to future operational scenarios. NASA is in the process of transferring the initial TRCM technology to the FAA. Future research will extend the concept and algorithm to provide coordinated plans for metroplex airports and study NextGen applications.

Stephen Atkins