Search NASA⌕ Search

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

Software Manages Documentation in a Large Test Facility

The 3MCS computer program assists and instrumentation engineer in performing the 3 essential functions of design, documentation, and configuration management of measurement and control systems in a large test facility. Services provided by 3MCS are acceptance of input from multiple engineers and technicians working at multiple locations;standardization of drawings;automated cross-referencing; identification of errors;listing of components and resources; downloading of test settings; and provision of information to customers.

Gurneck, Joseph M.↗
NASA NTRS2009

Policy-Based Management Natural Language Parser

The Policy-Based Management Natural Language Parser (PBEM) is a rules-based approach to enterprise management that can be used to automate certain management tasks. This parser simplifies the management of a given endeavor by establishing policies to deal with situations that are likely to occur. Policies are operating rules that can be referred to as a means of maintaining order, security, consistency, or other ways of successfully furthering a goal or mission. PBEM provides a way of managing configuration of network elements, applications, and processes via a set of high-level rules or business policies rather than managing individual elements, thus switching the control to a higher level. This software allows unique management rules (or commands) to be specified and applied to a cross-section of the Global Information Grid (GIG). This software embodies a parser that is capable of recognizing and understanding conversational English. Because all possible dialect variants cannot be anticipated, a unique capability was developed that parses passed on conversation intent rather than the exact way the words are used. This software can increase productivity by enabling a user to converse with the system in conversational English to define network policies. PBEM can be used in both manned and unmanned science-gathering programs. Because policy statements can be domain-independent, this software can be applied equally to a wide variety of applications.

James, Mark↗
NASA NTRS1974

Space shuttle configuration accounting functional design specification

An analysis is presented of the requirements for an on-line automated system which must be capable of tracking the status of requirements and engineering changes and of providing accurate and timely records. The functional design specification provides the definition, description, and character length of the required data elements and the interrelationship of data elements to adequately track, display, and report the status of active configuration changes. As changes to the space shuttle program levels II and III configuration are proposed, evaluated, and dispositioned, it is the function of the configuration management office to maintain records regarding changes to the baseline and to track and report the status of those changes. The configuration accounting system will consist of a combination of computers, computer terminals, software, and procedures, all of which are designed to store, retrieve, display, and process information required to track proposed and proved engineering changes to maintain baseline documentation of the space shuttle program levels II and III.

Source record↗
NASA NTRS1980

The Build System - Integration and management of large software avionic systems

The Build System comprises the software tools and procedures creating the flight memory load for the Space Shuttle Backup Flight System. The system has six functions: (1) configuration management, which insures that the memory load contains the proper modules, all clearly marked; (2) source translation, which translates the source code into a relocatable machine code; (3) module integration, which combines and assigns memory locations to all the object modules produced in source translation; (4) static code analysis, which verifies the integration process; (5) deliverables generation, which yields release documentation and deliverable items; and (6) release maintenance, which controls all system patches subsequent to release. Further developments will include more automation in the producing of patches from source-code updates and system requirements for tracking.

Mayer, J. T. B.↗
NASA NTRSDate not supplied

Tracking Critical Thermal Metrics throughout the Life Cycle of a Large Observatory Thermal Model

Observatory thermal models for large, complex missions, such as the Wide Field InfraRed Survey Telescope (WFIRST) mission, produce an immense amount of data to be processed. Configuration management of the model throughout the project life cycle has mainly focused on which versions of the subsystem models form the current observatory level configuration. However, the results produced by the model are not nearly as well tracked and traceable. Given the various states of design maturity for each of the components in the WFIRST design, an updated component model is nearly ready to be integrated at the next higher level of assembly about every month or two. With each subsystem model delivery, the observatory model needs to remove the old component, integrate the new one, execute the model, and inspect the results. Usually, this inspection focuses primarily on the newly integrated component. Recently, a Metric Tracking Spreadsheet was developed to help provide a “big picture” view of the entire observatory highlighting key parameters critical to mission performance. This spreadsheet helps track impacts on subsystems by updates of other subsystems that were not intuitively obvious. Metrics tracked include: absorbed environmental loading (to determine effectiveness of sunshield), temperatures of critical avionics, electrical dissipations, heater power predictions, stability of critical optics, parasitic heat leaks in cryogenic region, high level heat flows between elements, and model run time. Producing this data for the same operational configuration with each model update has helped produce a trail of data to evaluate the impact of model updates. While the metrics selected are specific for WFIRST, other large, complex observatories could be well served to establish their own metrics early in the project life cycle to track to quickly assess the impact of any subsystem on other subsystems or the overall system itself.

Thermal Desktop↗
NASA NTRSDate not supplied

Run Time Improvement Efforts for the Roman Space Telescope Thermal Analysis

"Observatory thermal models for large, complex missions, such as the Wide Field InfraRed Survey Telescope (WFIRST) mission, produce an immense amount of data to be processed. Configuration management of the model throughout the project life cycle has mainly focused on which versions of the subsystem models form the current observatory level configuration. However, the results produced by the model are not nearly as well The Roman Space Telescope (RST), formerly known as the Wide Field InfraRed Survey Telescope, is the next great astrophysics observatory mission to follow the James Webb Space Telescope with a planned launch in 2026. As a large scale, flagship mission for NASA with challenging wave front error stability requirements, a single model approach for both thermal discipline analysis and thermo-optical distortion analysis has been used since the early days of the project. In alleviating the need to maintain two separate models for different analysis types, it imposes run time penalties on the thermal analysis with a large model with significant radiation heat exchange. Throughout the lifecycle of the project, the component models have steadily grown in size, resulting in a continuous growth of the overall observatory model with each update and consequently a considerable increase in the model run time. While ongoing efforts to reduce run time are continuously investigated, previous efforts had primarily focused on timestep size and total simulation time to reach quasi-equilibrium. More recently, studies were performed on the total number of radiation couplings (radks) included in the model, which has a nearly linear impact on run time, but increases exponentially with node count. As standard practice for spacecraft analysis, small radks were excluded from the temperature solution based on the assumption that their interchange/view factors have a negligible impact on heat flow. Four approaches were investigated to reduce the model run time while minimizing the impact on accuracy: (1) the Equivalent Radiation Network node, (2) Progressive Radk Inclusion as solution proceeds, (3) Targeted Radk Filtering for critical/non critical areas, and lastly (4) Representation of culled radks with Backloads. Furthermore, the investigation of model run time also revealed that cold cases took noticeably longer to run than hot cases; the root computational inefficiencies were explored along with the computation penalty of linearization of the external radks and recalculation of temperature dependent linear couplings at each timestep. This paper outlines the details of each of the above approaches and their impact on run time and model accuracy.

Thermal Analysis↗
NASA NTRSDate not supplied

Run Time Improvement Efforts for the Roman Space Telescope Thermal Analysis

Observatory thermal models for large, complex missions, such as the Wide Field InfraRed Survey Telescope (WFIRST) mission, produce an immense amount of data to be processed. Configuration management of the model throughout the project life cycle has mainly focused on which versions of the subsystem models form the current observatory level configuration. However, the results produced by the model are not nearly as well The Roman Space Telescope (RST), formerly known as the Wide Field InfraRed Survey Telescope, is the next great astrophysics observatory mission to follow the James Webb Space Telescope with a planned launch in 2026. As a large scale, flagship mission for NASA with challenging wave front error stability requirements, a single model approach for both thermal discipline analysis and thermo-optical distortion analysis has been used since the early days of the project. In alleviating the need to maintain two separate models for different analysis types, it imposes run time penalties on the thermal analysis with a large model with significant radiation heat exchange. Throughout the lifecycle of the project, the component models have steadily grown in size, resulting in a continuous growth of the overall observatory model with each update and consequently a considerable increase in the model run time. While ongoing efforts to reduce run time are continuously investigated, previous efforts had primarily focused on timestep size and total simulation time to reach quasi-equilibrium. More recently, studies were performed on the total number of radiation couplings (radks) included in the model, which has a nearly linear impact on run time, but increases exponentially with node count. As standard practice for spacecraft analysis, small radks were excluded from the temperature solution based on the assumption that their interchange/view factors have a negligible impact on heat flow. Four approaches were investigated to reduce the model run time while minimizing the impact on accuracy: (1) the Equivalent Radiation Network node, (2) Progressive Radk Inclusion as solution proceeds, (3) Targeted Radk Filtering for critical/non critical areas, and lastly (4) Representation of culled radks with Backloads. Furthermore, the investigation of model run time also revealed that cold cases took noticeably longer to run than hot cases; the root computational inefficiencies were explored along with the computation penalty of linearization of the external radks and recalculation of temperature dependent linear couplings at each timestep. This paper outlines the details of each of the above approaches and their impact on run time and model accuracy.

Thermal Analysis↗
NASA NTRS1991

Using NetMaster to manage IBM networks

After defining a network and conveying its importance to support the activities at the JSC, the need for network management based on the size and complexity of the IBM SNA network at JSC is demonstrated. Network Management consists of being aware of component status and the ability to control resources to meet the availability and service needs of users. The concerns of the user are addressed as well as those of the staff responsible for managing the network. It is explained how NetMaster (a network management system for managing SNA networks) is used to enhance reliability and maximize service to SNA network users through automated procedures. The following areas are discussed: customization, problem and configuration management, and system measurement applications of NetMaster. Also, several examples are given that demonstrate NetMaster's ability to manage and control the network, integrate various product functions, as well as provide useful management information.

Ginsburg, Guss↗
NASA NTRS2007

Design and Data Management System

The Design and Data Management System (DDMS) was developed to automate the NASA Engineering Order (EO) and Engineering Change Request (ECR) processes at the Propulsion Test Facilities at Stennis Space Center for efficient and effective Configuration Management (CM). Prior to the development of DDMS, the CM system was a manual, paper-based system that required an EO or ECR submitter to walk the changes through the acceptance process to obtain necessary approval signatures. This approval process could take up to two weeks, and was subject to a variety of human errors. The process also requires that the CM office make copies and distribute them to the Configuration Control Board members for review prior to meetings. At any point, there was a potential for an error or loss of the change records, meaning the configuration of record was not accurate. The new Web-based DDMS eliminates unnecessary copies, reduces the time needed to distribute the paperwork, reduces time to gain the necessary signatures, and prevents the variety of errors inherent in the previous manual system. After implementation of the DDMS, all EOs and ECRs can be automatically checked prior to submittal to ensure that the documentation is complete and accurate. Much of the configuration information can be documented in the DDMS through pull-down forms to ensure consistent entries by the engineers and technicians in the field. The software also can electronically route the documents through the signature process to obtain the necessary approvals needed for work authorization. The workflow of the system allows for backups and timestamps that determine the correct routing and completion of all required authorizations in a more timely manner, as well as assuring the quality and accuracy of the configuration documents.

Messer, Elizabeth↗
NASA NTRS1996

[Formian 2 and a Formian Function for Processing Polyhedric Configurations]

The work began in October 1994 with the following objectives: (1) to produce an improved version of the programming language Formian; and (2) to create a means for computer aided handling of polyhedric configurations including the geodesic forms of all kinds. A new version of Formian, referred to as Formian 2, is being implemented to operate in the Windows 95 environment. It is an ideal tool for configuration management in a convenient and user-friendly manner. The second objective was achieved by creating a standard Formian function that allows convenient handling of all types of polyhedric configurations. In particular, the focus of attention is on polyhedric configurations that are of importance in architectural and structural engineering fields. The natural medium for processing of polyhedric configurations is a programming language that incorporates the concepts of 'formex algebra'. Formian is such a programming language in which the processing of polyhedric configurations can be carried out using the standard elements of the language. A description of this function is included in a chapter for a book entitled 'Beyond the Cube: the Architecture of space Frames and Polyhedra'. A copy of this chapter is appended.

Nooshin, H.↗
NASA NTRS1987

SAGA: A project to automate the management of software production systems

The Software Automation, Generation and Administration (SAGA) project is investigating the design and construction of practical software engineering environments for developing and maintaining aerospace systems and applications software. The research includes the practical organization of the software lifecycle, configuration management, software requirements specifications, executable specifications, design methodologies, programming, verification, validation and testing, version control, maintenance, the reuse of software, software libraries, documentation, and automated management.

Campbell, Roy H.↗
NASA NTRSDate not supplied

Optimization of Airport Runway Configuration with Forecast-Augmented Offline Reinforcement Learning

Runway configuration Management (RCM) governs the optimal utilization of runways based on variables such as traffic and meteorological conditions, making it a daunting task in air traffic management due to its dependency on volatile operational and environmental factors. This paper improves upon our previous work [1] on using offline model-free reinforcement learning for creating a Runway Configuration Assistance (RCA) decision-support tool. A novel integration of forecast data from LAMP (Localized Aviation Model Output Statistics Program) and TAF (Terminal Area Forecast) is introduced, enhancing the tool’s accuracy and also its adaptability to quick wind changes. The performance is evaluated using two major US airports, Charlotte Douglas International Airport (CLT) and Denver International Airport (DEN). To counter scalability issues presented by the addition of discrete forecast variables, we transitioned to a continuous state space model, ensuring scalability and inclusion of longer forecast data. The results of our experiments reflect significant improvements in the RCA tool’s prediction accuracy.

Sumanth Nethi↗
NASA NTRS1999

Reinventing The Design Process: Teams and Models

The future of space mission designing will be dramatically different from the past. Formerly, performance-driven paradigms emphasized data return with cost and schedule being secondary issues. Now and in the future, costs are capped and schedules fixed-these two variables must be treated as independent in the design process. Accordingly, JPL has redesigned its design process. At the conceptual level, design times have been reduced by properly defining the required design depth, improving the linkages between tools, and managing team dynamics. In implementation-phase design, system requirements will be held in crosscutting models, linked to subsystem design tools through a central database that captures the design and supplies needed configuration management and control. Mission goals will then be captured in timelining software that drives the models, testing their capability to execute the goals. Metrics are used to measure and control both processes and to ensure that design parameters converge through the design process within schedule constraints. This methodology manages margins controlled by acceptable risk levels. Thus, teams can evolve risk tolerance (and cost) as they would any engineering parameter. This new approach allows more design freedom for a longer time, which tends to encourage revolutionary and unexpected improvements in design.

Wall, Stephen D.↗
NASA NTRS2004

Value-added Data Services at the Goddard Earth Sciences Data and Information Services Center

The NASA Goddard Earth Sciences Data and Information Services Center (GES DISC), in addition to serving the Earth Science community as one of the major Distributed Active Archives Centers (DAACs), provides much more than just data. Among the value-added services available to general users are subsetting data spatially and/or by parameter, online analysis (to avoid downloading unnecessarily all the data), and assistance in obtaining data from other centers. Services available to data producers and high-volume users include consulting on building new products with standard formats and metadata and construction of data management systems. A particularly useful service is data processing at the DISC (i.e., close to the input data) with the users algorithm. This can take a number of different forms: as a configuration-managed algorithm within the main processing stream; as a stand-alone program next to the on-line data storage; as build-it-yourself code within the Near-Archive Data Mining (NADM) system; or as an on-the-fly analysis with simple algorithms embedded into the web-based tools. Partnerships between the GES DISC and scientists, both producers and users, allow the scientists to concentrate on science, while the GES DISC handles the data management, e.g., formats, integration, and data processing. The existing data management infrastructure at the GES DISC supports a wide spectrum of options: from simple data support to sophisticated on-line analysis tools, producing economies of scale and rapid time-to-deploy. At the same time, such partnerships allow the GES DISC to serve the user community more efficiently and to better prioritize on-line holdings. Several examples of successful partnerships are described in the presentation.

Leptoukh, Gregory G.↗
NASA NTRS2010

Managing Complex Space Missions Like the James Webb Space Telescope

Program Management Summary; Organizational structure is established. Roles and responsibilities are well defined: a) All major contracts are in place. b) All foreign partners are in place, operating under signed Memoranda of Understanding (MOUs). c) Partners include GSFC, NGST, Ball, ITT, ATK, STScI, ESA, CSA, UAz, LM, JPL, MSFC, ARC, JSC, etc. All enabling technologies are at Technical Readiness Level-6. Earned Value Management is being applied to all major contracts consistent with Agency guidance. Schedules are baselined and the project critical path is understood/managed. Budget with reserves established. Liens and threats system in use. Formal Configuration Management (CM) processes are in place. Project-level schedules are maintained within the CM system. Formal Risk Management processes are in place. Requirements are stable and flowed down. Project metrics are established and tracked monthly: a) Includes technical as well as cost and schedule metrics. b) Changes as well as trends are reported each month.

Sabelhaus, Phil↗
NASA NTRS1994

ControlShell: A real-time software framework

The ControlShell system is a programming environment that enables the development and implementation of complex real-time software. It includes many building tools for complex systems, such as a graphical finite state machine (FSM) tool to provide strategic control. ControlShell has a component-based design, providing interface definitions and mechanisms for building real-time code modules along with providing basic data management. Some of the system-building tools incorporated in ControlShell are a graphical data flow editor, a component data requirement editor, and a state-machine editor. It also includes a distributed data flow package, an execution configuration manager, a matrix package, and an object database and dynamic binding facility. This paper presents an overview of ControlShell's architecture and examines the functions of several of its tools.

Schneider, Stanley A.↗
NASA NTRS2003

Integration and Test of Shuttle Small Payloads

Recommended approaches for space shuttle small payload integration and test (I&T) are presented. The paper is intended for consideration by developers of shuttle small payloads, including I&T managers, project managers, and system engineers. Examples and lessons learned are presented based on the extensive history of NASA's Hitchhiker project. All aspects of I&T are presented, including: (1) I&T team responsibilities, coordination, and communication; (2) Flight hardware handling practices; (3) Documentation and configuration management; (4) I&T considerations for payload development; (5) I&T at the development facility; (6) Prelaunch operations, transfer, orbiter integration and interface testing; (7) Postflight operations. This paper is of special interest to those payload projects that have small budgets and few resources: that is, the truly faster, cheaper, better projects. All shuttle small payload developers are strongly encouraged to apply these guidelines during I&T planning and ground operations to take full advantage of today's limited resources and to help ensure mission success.

Wright, Michael R.↗