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.

SourceResearch connectionFrom yearThrough year

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

At least 73 records · Page 4

All sources NASA NTRS DOE OSTI

NASA NTRS2004

A Recipe for Streamlining Mission Management

This paper describes a project's design and implementation for streamlining mission management with knowledge capture processes across multiple organizations of a NASA directorate. Thc project's focus is on standardizing processes and reports; enabling secure information access and case of maintenance; automating and tracking appropriate workflow rules through process mapping; and infusing new technologies. This paper will describe a small team's experiences using XML technologies through an enhanced vendor suite of applications integrated on Windows-based platforms called the Wallops Integrated Scheduling and Document Management System (WISDMS). This paper describes our results using this system in a variety of endeavors, including providing range project scheduling and resource management for a Range and Mission Management Office; implementing an automated Customer Feedback system for a directorate; streamlining mission status reporting across a directorate; and initiating a document management, configuration management and portal access system for a Range Safety Office's programs. The end result is a reduction of the knowledge gap through better integration and distribution of information, improved process performance, automated metric gathering, and quicker identification of problem areas and issues. However, the real proof of the pudding comes through overcoming the user's reluctance to replace familiar, seasoned processes with new technology ingredients blended with automated procedures in an untested recipe. This paper shares some of the team's observations that led to better implementation techniques, as well as an IS0 9001 Best Practices citation. This project has provided a unique opportunity to advance NASA's competency in new technologies, as well as to strategically implement them within an organizational structure, while wetting the appetite for continued improvements in mission management.

Mitchell, Andrew E.↗

NASA NTRS2006

Integrated Modeling Environment

The Integrated Modeling Environment (IME) is a software system that establishes a centralized Web-based interface for integrating people (who may be geographically dispersed), processes, and data involved in a common engineering project. The IME includes software tools for life-cycle management, configuration management, visualization, and collaboration.

Mosier, Gary↗

NASA NTRS2011

SOFIA Program SE and I Lessons Learned

Once a "Troubled Project" threatened with cancellation, the Stratospheric Observatory for Infrared Astronomy (SOFIA) Program has overcome many difficult challenges and recently achieved its first light images. To achieve success, SOFIA had to overcome significant deficiencies in fundamental Systems Engineering identified during a major Program restructuring. This presentation will summarize the lessons learn in Systems Engineering on the SOFIA Program. After the Program was reformulated, an initial assessment of Systems Engineering established the scope of the problem and helped to set a list of priorities that needed to be work. A revised Systems Engineering Management Plan (SEMP) was written to address the new Program structure and requirements established in the approved NPR7123.1A. An important result of the "Technical Planning" effort was the decision by the Program and Technical Leadership team to re-phasing the lifecycle into increments. The reformed SOFIA Program Office had to quickly develop and establish several new System Engineering core processes including; Requirements Management, Risk Management, Configuration Management and Data Management. Implementing these processes had to consider the physical and cultural diversity of the SOFIA Program team which includes two Projects spanning two NASA Centers, a major German partnership, and sub-contractors located across the United States and Europe. The SOFIA Program experience represents a creative approach to doing "System Engineering in the middle" while a Program is well established. Many challenges were identified and overcome. The SOFIA example demonstrates it is never too late to benefit from fixing deficiencies in the System Engineering processes.

Ray, Ronald J.↗

NASA NTRS1983

Configuration Analysis Tool

Configuration Analysis Tool (CAT), is information storage and report generation system for aid of configuration management activities. Configuration management is discipline composed of many techniques selected to track and direct evolution of complex systems. CAT is interactive program that accepts, organizes and stores information pertinent to specific phases of project.

Merwarth, P. D.↗

NASA NTRS1974

Earth Observatory Satellite system definition study. Report no. 3: Design/cost tradeoff studies. Appendix D: EOS configuration design data. Part 2: Data management system configuration

The Earth Observatory Satellite (EOS) data management system (DMS) is discussed. The DMS is composed of several subsystems or system elements which have basic purposes and are connected together so that the DMS can support the EOS program by providing the following: (1) payload data acquisition and recording, (2) data processing and product generation, (3) spacecraft and processing management and control, and (4) data user services. The configuration and purposes of the primary or high-data rate system and the secondary or local user system are explained. Diagrams of the systems are provided to support the systems analysis.

Source record↗

NASA NTRS1972

Advanced Software Techniques for Data Management Systems. Volume 2: Space Shuttle Flight Executive System: Functional Design

A functional design of software executive system for the space shuttle avionics computer is presented. Three primary functions of the executive are emphasized in the design: task management, I/O management, and configuration management. The executive system organization is based on the applications software and configuration requirements established during the Phase B definition of the Space Shuttle program. Although the primary features of the executive system architecture were derived from Phase B requirements, it was specified for implementation with the IBM 4 Pi EP aerospace computer and is expected to be incorporated into a breadboard data management computer system at NASA Manned Spacecraft Center's Information system division. The executive system was structured for internal operation on the IBM 4 Pi EP system with its external configuration and applications software assumed to the characteristic of the centralized quad-redundant avionics systems defined in Phase B.

Pepe, J. T.↗

NASA NTRS2014

Functional Analysis for an Integrated Capability of Arrival/Departure/Surface Management with Tactical Runway Management

The runway is a critical resource of any air transport system. It is used for arrivals, departures, and for taxiing aircraft and is universally acknowledged as a constraining factor to capacity for both surface and airspace operations. It follows that investigation of the effective use of runways, both in terms of selection and assignment as well as the timing and sequencing of the traffic is paramount to the efficient traffic flows. Both the German Aerospace Center (DLR) and NASA have developed concepts and tools to improve atomic aspects of coordinated arrival/departure/surface management operations and runway configuration management. In December 2012, NASA entered into a Collaborative Agreement with DLR. Four collaborative work areas were identified, one of which is called "Runway Management." As part of collaborative research in the "Runway Management" area, which is conducted with the DLR Institute of Flight Guidance, located in Braunschweig, the goal is to develop an integrated system comprised of the three DLR tools - arrival, departure, and surface management (collectively referred to as A/D/S-MAN) - and NASA's tactical runway configuration management (TRCM) tool. To achieve this goal, it is critical to prepare a concept of operations (ConOps) detailing how the NASA runway management and DLR arrival, departure, and surface management tools will function together to the benefit of each. To assist with the preparation of the ConOps, the integrated NASA and DLR tools are assessed through a functional analysis method described in this report. The report first provides the highlevel operational environments for air traffic management (ATM) in Germany and in the U.S., and the descriptions of the DLR's A/D/S-MAN and NASA's TRCM tools at the level of details necessary to compliment the purpose of the study. Functional analyses of each tool and a completed functional analysis of an integrated system design are presented next in the report. Future efforts to fully develop the ConOps will include: developing scenarios to fully test environmental, procedural, and data availability assumptions; executing the analysis by a walk-through of the integrated system using these scenarios; defining the appropriate role of operators in terms of their monitoring requirements and decision authority; executing the analysis by a walk-through of the integrated system with operator involvement; characterizing the environmental, system data requirements, and operator role assumptions for the ConOps.

Phojanamongkolkij, Nipa↗

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 NTRS1979

Data base management system configuration specification

The functional requirements and the configuration of the data base management system are described. Techniques and technology which will enable more efficient and timely transfer of useful data from the sensor to the user, extraction of information by the user, and exchange of information among the users are demonstrated.

Neiers, J. W.↗

NASA NTRS1977

Survey of piloting factors in V/STOL aircraft with implications for flight control system design

Flight control system design factors involved for pilot workload relief are identified. Major contributors to pilot workload include configuration management and control and aircraft stability and response qualities. A digital fly by wire stability augmentation, configuration management, and configuration control system is suggested for reduction of pilot workload during takeoff, hovering, and approach.

Ringland, R. F.↗

NASA NTRS1970

Onboard data management

Configurations and functions of onboard data processing for space shuttles

Poupard, R. E.↗

NASA NTRS2017

Digital Model-Based Engineering: Expectations, Prerequisites, and Challenges of Infusion

Digital model-based engineering (DMbE) is the use of digital artifacts, digital environments, and digital tools in the performance of engineering functions. DMbE is intended to allow an organization to progress from documentation-based engineering methods to digital methods that may provide greater flexibility, agility, and efficiency. The term 'DMbE' was developed as part of an effort by the Model-Based Systems Engineering (MBSE) Infusion Task team to identify what government organizations might expect in the course of moving to or infusing MBSE into their organizations. The Task team was established by the Interagency Working Group on Engineering Complex Systems, an informal collaboration among government systems engineering organizations. This Technical Memorandum (TM) discusses the work of the MBSE Infusion Task team to date. The Task team identified prerequisites, expectations, initial challenges, and recommendations for areas of study to pursue, as well as examples of efforts already in progress. The team identified the following five expectations associated with DMbE infusion, discussed further in this TM: (1) Informed decision making through increased transparency, and greater insight. (2) Enhanced communication. (3) Increased understanding for greater flexibility/adaptability in design. (4) Increased confidence that the capability will perform as expected. (5) Increased efficiency. The team identified the following seven challenges an organization might encounter when looking to infuse DMbE: (1) Assessing value added to the organization. Not all DMbE practices will be applicable to every situation in every organization, and not all implementations will have positive results. (2) Overcoming organizational and cultural hurdles. (3) Adopting contractual practices and technical data management. (4) Redefining configuration management. The DMbE environment changes the range of configuration information to be managed to include performance and design models, database objects, as well as more traditional book-form objects and formats. (5) Developing information technology (IT) infrastructure. Approaches to implementing critical, enabling IT infrastructure capabilities must be flexible, reconfigurable, and updatable. (6) Ensuring security of the single source of truth (7) Potential overreliance on quantitative data over qualitative data. Executable/ computational models and simulations generally incorporate and generate quantitative vice qualitative data. The Task team also developed several recommendations for government, academia, and industry, as discussed in this TM. The Task team recommends continuing beyond this initial work to further develop the means of implementing DMbE and to look for opportunities to collaborate and share best practices.

Hale, J. P.↗

NASA NTRS2012

Multiplexer/Demultiplexer Loading Tool (MDMLT)

The purpose of the MDMLT is to improve the reliability and speed of loading multiplexers/demultiplexers (MDMs) in the Software Development and Integration Laboratory (SDIL) by automating the configuration management (CM) of the loads in the MDMs, automating the loading procedure, and providing the capability to load multiple or all MDMs concurrently. This loading may be accomplished in parallel, or single MDMs (remote). The MDMLT is a Web-based tool that is capable of loading the entire International Space Station (ISS) MDM configuration in parallel. It is able to load Flight Equivalent Units (FEUs), enhanced, standard, and prototype MDMs as well as both EEPROM (Electrically Erasable Programmable Read-Only Memory) and SSMMU (Solid State Mass Memory Unit) (MASS Memory). This software has extensive configuration management to track loading history, and the performance improvement means of loading the entire ISS MDM configuration of 49 MDMs in approximately 30 minutes, as opposed to 36 hours, which is what it took previously utilizing the flight method of S-Band uplink. The laptop version recently added to the MDMLT suite allows remote lab loading with the CM of information entered into a common database when it is reconnected to the network. This allows the program to reconfigure the test rigs quickly between shifts, allowing the lab to support a variety of onboard configurations during a single day, based on upcoming or current missions. The MDMLT Computer Software Configuration Item (CSCI) supports a Web-based command and control interface to the user. An interface to the SDIL File Transfer Protocol (FTP) server is supported to import Integrated Flight Loads (IFLs) and Internal Product Release Notes (IPRNs) into the database. An interface to the Monitor and Control System (MCS) is supported to control the power state, and to enable or disable the debug port of the MDMs to be loaded. Two direct interfaces to the MDM are supported: a serial interface (debug port) to receive MDM memory dump data and the calculated checksum, and the Small Computer System Interface (SCSI) to transfer load files to MDMs with hard disks. File transfer from the MDM Loading Tool to EEPROM within the MDM is performed via the MILSTD- 1553 bus, making use of the Real- Time Input/Output Processors (RTIOP) when using the rig-based MDMLT, and via a bus box when using the laptop MDMLT. The bus box is a cost-effective alternative to PC-1553 cards for the laptop. It is noted that this system can be modified and adapted to any avionic laboratory for spacecraft computer loading, ship avionics, or aircraft avionics where multiple configurations and strong configuration management of software/firmware loads are required.

Brewer, Lenox Allen↗

NASA NTRS1999

Lightning Mapper Sensor Lens Assembly S.O. 5459: Project Management Plan

Kaiser Electro-Optics, Inc. (KEO) has developed this Project Management Plan for the Lightning Mapper Sensor (LMS) program. KEO has integrated a team of experts in a structured program management organization to meet the needs of the LMS program. The project plan discusses KEO's approach to critical program elements including Program Management, Quality Assurance, Configuration Management, and Schedule.

Zeidler, Janet↗

NASA NTRS1974

Apollo experience report: Flight-control data needs, terminal display devices, and ground system configuration requirements

The development of flight-control facilities for the Apollo program is reviewed from the viewpoint of the user organization. These facilities are treated in three categories: data systems, ground-based display and control systems, and configuration management. The effects of certain Apollo program factors on the selection, sizing, and configuration management of these systems are discussed. Recommendations are made regarding improvement of the systems and the reduction of system sensitivity to the program factors.

Hoover, R. A.↗

NASA NTRSDate not supplied

Initial Analysis of Digitally Enabled Cooperative Operations in Class D Terminal Airspace

The primary contribution of this paper is an initial analysis of integrating digitally enabled cooperative operations (or digital operations for short) with Visual Flight Rules (VFR) and Instrument Flight Rules (IFR) operations in the terminal airspace around a Class D airport, specifically around Fort Worth Alliance airport (KAFW). Enabled by connected digital technologies and automated information exchange, digital operations as envisioned would utilize cooperative practices and operator-responsible separation to ensure safety. In the present study, three conflict management configurations for digital operations were analyzed: 1) centralized with a single instance of a conflict management service to model a scenario with only one fleet operator conducting digital operations or all fleet operators utilizing the same service, 2) federated with two different instances to model a scenario with two different fleet operators conducting digital operations, and 3) fully distributed with a different instance for each digital operation. In simulations in which recorded tracks for VFR and IFR operations were played back and digital operations were modeled that would nominally arrive at KAFW once every 20 minutes (given no conflict resolution maneuvers), there were one or fewer losses of separation (LOS) across the three conflict management configurations. The same result was seen in simulations in which digital operations would nominally arrive at KAFW once every 10 minutes. However, in simulations in which digital operations would nominally arrive at KAFW once every 5 minutes, the number of LOS ranged between six and ten. This highlights the need for follow-on research to investigate the extent to which additional capabilities for digital operations, such as complexity management and/or flow organization, may be needed.

digitally enabled cooperative operations, digital ↗

NASA NTRSDate not supplied

Initial Analysis of Digitally Enabled Cooperative Operations in Class D Terminal Airspace

digitally enabled cooperative operations↗

NASA NTRS2001

Configuration and Data Management Process and the System Safety Professional

This article presents a discussion of the configuration management (CM) and the Data Management (DM) functions and provides a perspective of the importance of configuration and data management processes to the success of system safety activities. The article addresses the basic requirements of configuration and data management generally based on NASA configuration and data management policies and practices, although the concepts are likely to represent processes of any public or private organization's well-designed configuration and data management program.

Shivers, Charles Herbert↗