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 307 records · Page 17

YAM- A Framework for Rapid Software Development

YAM is a software development framework with tools for facilitating the rapid development and integration of software in a concurrent software development environment. YAM provides solutions for thorny development challenges associated with software reuse, managing multiple software configurations, the development of software product-lines, multiple platform development and build management. YAM uses release-early, release-often development cycles to allow developers to incrementally integrate their changes into the system on a continual basis. YAM facilitates the creation and merging of branches to support the isolated development of immature software to avoid impacting the stability of the development effort. YAM uses modules and packages to organize and share software across multiple software products. It uses the concepts of link and work modules to reduce sandbox setup times even when the code-base is large. One side-benefit is the enforcement of a strong module-level encapsulation of a module s functionality and interface. This increases design transparency, system stability as well as software reuse. YAM is in use by several mid-size software development teams including ones developing mission-critical software.

simulations↗

ATM Technology Demonstration-1 Phase II Boeing Configurable Graphical Display (CGD) Software Design Description

This Software Description Document (SDD) captures the design for developing the Flight Interval Management (FIM) system Configurable Graphics Display (CGD) software. Specifically this SDD describes aspects of the Boeing CGD software and the surrounding context and interfaces. It does not describe the Honeywell components of the CGD system. The SDD provides the system overview, architectural design, and detailed design with all the necessary information to implement the Boeing components of the CGD software and integrate them into the CGD subsystem within the larger FIM system. Overall system and CGD system-level requirements are derived from the CGD SRS (in turn derived from the Boeing System Requirements Design Document (SRDD)). Display and look-and-feel requirements are derived from Human Machine Interface (HMI) design documents and working group recommendations. This Boeing CGD SDD is required to support the upcoming Critical Design Review (CDR).

Wilber, George F.↗

Nickel-cadmium Battery Cell Reversal from Resistive Network Effects

During the individual cell short-down procedures often used for storing or reconditioning nickel-cadmium (Ni-Cd) batteries, it is possible for significant reversal of the lowest capacity cells to occur. The reversal is caused by the finite resistance of the common current-carrying leads in the resistive network that is generally used during short-down. A model is developed to evaluate the extent of such a reversal in any specific battery, and the model is verified by means of data from the short-down of a f-cell, 3.5-Ah battery. Computer simulations of short-down on a variety of battery configurations indicate the desirability of controlling capacity imbalances arising from cell configuration and battery management, limiting variability in the short-down resistors, minimizing lead resistances, and optimizing lead configurations.

Zimmerman, A. H.↗

Human System Risk Management for Space Flight

This brief abstract reviews the development of the current day approach to human system risk management for space flight and the development of the critical components of this process over the past few years. The human system risk management process now provides a comprehensive assessment of each human system risk by design reference mission (DRM) and is evaluated not only for mission success but also for long‐term health impacts for the astronauts. The discipline of bioastronautics is the study of the biological and medical effects of space flight on humans. In 1997, the Space Life Sciences Directorate (SLSD) initiated the Bioastronautics Roadmap (Roadmap) as the "Critical Path Roadmap", and in 1998 participation in the roadmap was expanded to include the National Space Biomedical Research Institute (NSBRI) and the external community. A total of 55 risks and 250 questions were identified and prioritized and in 2000, the Roadmap was base-lined and put under configuration control. The Roadmap took into account several major advisory committee reviews including the Institute of Medicine (IOM) "Safe Passage: Astronaut care for Exploration Missions", 2001. Subsequently, three collaborating organizations at NASA HQ (Chief Health and Medical Officer, Office of Space Flight and Office of Biological & Physical Research), published the Bioastronautics Strategy in 2003, that identified the human as a "critical subsystem of space flight" and noted that "tolerance limits and safe operating bands must be established" to enable human space flight. These offices also requested a review by the IOM of the Roadmap and that review was published in October 2005 as "A Risk Reduction Strategy for Human Exploration of Space: A Review of NASA's Bioastronautics Roadmap", that noted several strengths and weaknesses of the Roadmap and made several recommendations. In parallel with the development of the Roadmap, the Office of the Chief Health and Medical Officer (OCHMO) began a process in 2004 of evaluating the tolerance limits and safe operating bands called for in the Bioastronautics Strategy. Over the next several years, the concept of the "operating bands" were turned into Space Flight Human System Standards (SFHSS), developed by the technical resources of the SLSD at the NASA Johnson Space Center (JSC). These standards were developed and reviewed at the SLSD and then presented to the OCHMO for acceptance. The first set of standards was published in 2007 as the NASA‐STD‐3001, Volume 1, Crew Health that elaborated standards for several physiological areas such as cardiovascular, musculoskeletal, radiation exposure and nutrition. Volume 2, Human Factors, Habitability and Human Health was published in 2011, along with development guidance in the Human Integration Design Handbook (HIDH). Taken together, the SFHSS Volumes 1 and 2, and the HIDH replaced the NASA‐STD‐3000 with new standards and revisions of the older document. Three other changes were also taking place that facilitated the development of the human system risk management approach. In 2005, the life sciences research and development portfolio underwent a comprehensive review through the Exploration Systems Architecture Study (ESAS) that resulted in the reformulation of the Bioastronautics Program into Human Research Program (HRP) that was focused on appropriate mitigation results for high priority human health risks. The baseline HRP budget was established in August 2005. In addition, the OCHMO formulated the Health and Medical Technical Authority (HMTA) in 2006 that established the position of the Chief Medical Officer (CMO) at the NASA JSC along with other key technical disciplines, and the OCHMO became the responsible office for the SFHSS as noted above. The final change was the establishment in 2008 of the Human System Risk Board (HSRB), chaired by the CMO with representation from the HRP, SLSD management and technical experts. The HSRB then began to review all human system risks, established a comprehensive risk management and configuration management plan and data sharing policy. These major developments of standards, the HRP, the HMTA and a forum for review of human system risks (HSRB) facilitated the integration of human research, medical operations, systems engineering and many other disciplines in the comprehensive review of human system risks. The HSRB began a comprehensive review of all potential inflight medical conditions and events and over the course of several reviews consolidated the number of human system risks to 30 where the greatest emphasis is placed for investing program dollars for risk mitigation. The HSRB considers all available evidence from human research, medical operations and occupational surveillance in assessing the risks for appropriate mitigation and future work. All applicable DRMs (low earth orbit 6 and 12 months, deep space sortie for 30 days and 1 year, a one year lunar mission, and a planetary mission for 3 years) are considered as human system risks are modified by the hazards associated with space flight such as microgravity, exposure to radiation, distance from the earth, isolation and a closed environment. Each risk has a summary assessment representing the state of knowledge/evidence base for that risk, the available risk mitigations, traceability to the SFHSS and program requirements, and future work required. These data then can drive coordinated budgets across the HRP, the International Space Station, Crew Health and Safety and Advanced Exploration System budgets. These risk assessments were completed for 6 DRMs in December of 2014 and serve as the baseline for which subsequent research and technology development and crew health care portfolios can be assessed. The HSRB will review each risk at least annually and especially when new information is available that must be considered for effective risk mitigation. The current status of each risk can be reported to program management for operations, budget reviews and general oversight of the human system risk management program.

Davis, Jeffrey↗

Attitude control/momentum management of the Space Station Freedom for large angle torque-equilibrium-attitude configurations

An attitude-control and momentum-management (ACMM) system for the Space Station in a large-angle torque-equilibrium-attitude (TEA) configuration is developed analytically and demonstrated by means of numerical simulations. The equations of motion for a rigid-body Space Station model are outlined; linearized equations for an arbitrary TEA (resulting from misalignment of control and body axes) are derived; the general requirements for an ACMM are summarized; and a pole-placement linear-quadratic regulator solution based on scheduled gains is proposed. Results are presented in graphs for (1) simulations based on configuration MB3 (showing the importance of accounting for the cross-inertia terms in the TEA estimate) and (2) simulations of a stepwise change from configuration MB3 to the 'assembly complete' stage over 130 orbits (indicating that the present ACCM scheme maintains sufficient control over slowly varying Space Station dynamics).

Parlos, Alexander G.↗

Dynamic Airspace Configuration

In air traffic management systems, airspace is partitioned into regions in part to distribute the tasks associated with managing air traffic among different systems and people. These regions, as well as the systems and people allocated to each, are changed dynamically so that air traffic can be safely and efficiently managed. It is expected that new air traffic control systems will enable greater flexibility in how airspace is partitioned and how resources are allocated to airspace regions. In this talk, I will begin by providing an overview of some previous work and open questions in Dynamic Airspace Configuration research, which is concerned with how to partition airspace and assign resources to regions of airspace. For example, I will introduce airspace partitioning algorithms based on clustering, integer programming optimization, and computational geometry. I will conclude by discussing the development of a tablet-based tool that is intended to help air traffic controller supervisors configure airspace and controllers in current operations.

airspace↗

Evaluation of Early Ground Control Station Configurations for Interacting with a UAS Traffic Management (UTM) System

The purpose of this paper is to report on a human factors evaluation of ground control station design concepts for interacting with an unmanned traffic management system. The data collected for this paper comes from recent field tests for NASA's Unmanned Traffic Management (UTM) project, and covers the following topics; workload, situation awareness, as well as flight crew communication, coordination, and procedures. The goal of this evaluation was to determine if the various software implementations for interacting with the UTM system can be described and classified into design concepts to provide guidance for the development of future UTM interfaces. We begin with a brief description of NASA's UTM project, followed by a description of the test range configuration related to a second development phase. We identified (post hoc) two classes in which the ground control stations could be grouped. This grouping was based on level of display integration. The analysis was exploratory and informal. It was conducted to compare ground stations across those two classes and against the aforementioned topics. Herein, we discuss the results.

unmanned traffic management↗

Jitter Controller Software

Sinusoidal jitter is produced by simply modulating a clock frequency sinusoidally with a given frequency and amplitude. But this can be expressed as phase jitter, frequency jitter, or cycle-to-cycle jitter, rms or peak, absolute units, or normalized to the base clock frequency. Jitter using other waveforms requires calculating and downloading these waveforms to an arbitrary waveform generator, and helping the user manage relationships among phase jitter crest factor, frequency jitter crest factor, and cycle-to-cycle jitter (CCJ) crest factor. Software was developed for managing these relationships, automatically configuring the generator, and saving test results documentation. Tighter management of clock jitter and jitter sensitivity is required by new codes that further extend the already high performance of space communication links, completely correcting symbol error rates higher than 10 percent, and therefore typically requiring demodulation and symbol synchronization hardware to operating at signal-to-noise ratios of less than one. To accomplish this, greater demands are also made on transmitter performance, and measurement techniques are needed to confirm performance. It was discovered early that sinusoidal jitter can be stepped on a grid such that one can connect points by constant phase jitter, constant frequency jitter, or constant cycle-cycle jitter. The tool automates adherence to a grid while also allowing adjustments off-grid. Also, the jitter can be set by the user on any dimension and the others are calculated. The calculations are all recorded, allowing the data to be rapidly plotted or re-plotted against different interpretations just by changing pointers to columns. A key advantage is taking data on a carefully controlled grid, which allowed a single data set to be post-analyzed many different ways. Another innovation was building a software tool to provide very tight coupling between the generator and the recorded data product, and the operator's worksheet. Together, these allowed the operator to sweep the jitter stimulus quickly along any of three dimensions and focus on the response of the system under test (response was jitter transfer ratio, or performance degradation to the symbol or codeword error rate). Additionally, managing multi-tone and noise waveforms automated a tedious manual process, and provided almost instantaneous decision- making control over test flow. The code was written in LabVIEW, and calls Agilent instrument drivers to write to the generator hardware.

Lansdowne, Chatwin↗

Systems and Methods for Determining Inertial Navigation System Faults

An inertial navigation system (INS) includes a primary inertial navigation system (INS) unit configured to receive accelerometer measurements from an accelerometer and angular velocity measurements from a gyroscope. The primary INS unit is further configured to receive global navigation satellite system (GNSS) signals from a GNSS sensor and to determine a first set of kinematic state vectors based on the accelerometer measurements, the angular velocity measurements, and the GNSS signals. The INS further includes a secondary INS unit configured to receive the accelerometer measurements and the angular velocity measurements and to determine a second set of kinematic state vectors of the vehicle based on the accelerometer measurements and the angular velocity measurements. A health management system is configured to compare the first set of kinematic state vectors and the second set of kinematic state vectors to determine faults associated with the accelerometer or the gyroscope based on the comparison.

Bharadwaj, Raj Mohan↗

A Study of Future Communications Concepts and Technologies for the National Airspace System-Part III

The National Aeronautics and Space Administration (NASA) Glenn Research Center (GRC) is investigating current and anticipated wireless communications concepts and technologies that the National Airspace System (NAS) may need in the next 50 years. NASA has awarded three NASA Research Announcements (NAR) studies with the objective to determine the most promising candidate technologies for air-to-air and air-to-ground data exchange and analyze their suitability in a post-NextGen NAS environment. This paper will present progress made in the studies and describe the communications challenges and opportunities that have been identified as part of the study. NASA's NextGen Concepts and Technology Development (CTD) Project integrates solutions for a safe, efficient and high-capacity airspace system through joint research efforts and partnerships with other government agencies. The CTD Project is one of two within NASA's Airspace Systems Program and is managed by the NASA Ames Research Center. Research within the CTD Project is in support the 2011 NASA Strategic Plan Sub-Goal 4.1: Develop innovative solutions and advanced technologies, through a balanced research portfolio, to improve current and future air transportation. The focus of CTD is on developing capabilities in traffic flow management, dynamic airspace configuration, separation assurance, super density operations and airport surface operations. Important to its research is the development of human/automation information requirements and decisionmaking guidelines for human-human and human-machine airportal decision-making. Airborne separation, oceanic intrail climb/descent and interval management applications depend on location and intent information of surrounding aircraft. ADS-B has been proposed to provide the information exchange, but other candidates such as satellite-based receivers, broadband or airborne internet, and cellular communications are possible candidate's.

Navigation↗

A feedback linearization approach to spacecraft control using momentum exchange devices

Recent developments in the area of nonlinear control theory have shown how coordiante changes in the state and input spaces can be used with nonlinear feedback to transform certain nonlinear ordinary differential equations into equivalent linear equations. These feedback linearization techniques are applied to resolve two problems arising in the control of spacecraft equipped with control moment gyroscopes (CMGs). The first application involves the computation of rate commands for the gimbals that rotate the individual gyroscopes to produce commanded torques on the spacecraft. The second application is to the long-term management of stored momentum in the system of control moment gyroscopes using environmental torques acting on the vehicle. An approach to distributing control effort among a group of redundant actuators is described that uses feedback linearization techniques to parameterize sets of controls which influence a specified subsystem in a desired way. The approach is adapted for use in spacecraft control with double-gimballed gyroscopes to produce an algorithm that avoids problematic gimbal configurations by approximating sets of gimbal rates that drive CMG rotors into desirable configurations. The momentum management problem is stated as a trajectory optimization problem with a nonlinear dynamical constraint. Feedback linearization and collocation are used to transform this problem into an unconstrainted nonlinear program. The approach to trajectory optimization is fast and robust. A number of examples are presented showing applications to the proposed NASA space station.

Dzielski, John Edward↗

System Oriented Runway Management: A Research Update

The runway configuration used by an airport has significant implications with respect to its capacity and ability to effectively manage surface and airborne traffic. Aircraft operators rely on runway configuration information because it can significantly affect an airline's operations and planning of their resources. Current practices in runway management are limited by a relatively short time horizon for reliable weather information and little assistance from automation. Wind velocity is the primary consideration when selecting a runway configuration; however when winds are below a defined threshold, discretion may be used to determine the configuration. Other considerations relevant to runway configuration selection include airport operator constraints, weather conditions (other than winds) traffic demand, user preferences, surface congestion, and navigational system outages. The future offers an increasingly complex landscape for the runway management process. Concepts and technologies that hold the potential for capacity and efficiency increases for both operations on the airport surface and in terminal and enroute airspace are currently under investigation. Complementary advances in runway management are required if capacity and efficiency increases in those areas are to be realized. The System Oriented Runway Management (SORM) concept has been developed to address this critical part of the traffic flow process. The SORM concept was developed to address all aspects of runway management for airports of varying sizes and to accommodate a myriad of traffic mixes. SORM, to date, addresses the single airport environment; however, the longer term vision is to incorporate capabilities for multiple airport (Metroplex) operations as well as to accommodate advances in capabilities resulting from ongoing research. This paper provides an update of research supporting the SORM concept including the following: a concept of overview, results of a TRCM simulation, single airport and Metroplex modeling effort and a benefits assessment.

Lohr, Gary W.↗

Configuring the Orion Guidance, Navigation, and Control Flight Software for Automated Sequencing

The Orion Crew Exploration Vehicle is being designed with greater automation capabilities than any other crewed spacecraft in NASA s history. The Guidance, Navigation, and Control (GN&C) flight software architecture is designed to provide a flexible and evolvable framework that accommodates increasing levels of automation over time. Within the GN&C flight software, a data-driven approach is used to configure software. This approach allows data reconfiguration and updates to automated sequences without requiring recompilation of the software. Because of the great dependency of the automation and the flight software on the configuration data, the data management is a vital component of the processes for software certification, mission design, and flight operations. To enable the automated sequencing and data configuration of the GN&C subsystem on Orion, a desktop database configuration tool has been developed. The database tool allows the specification of the GN&C activity sequences, the automated transitions in the software, and the corresponding parameter reconfigurations. These aspects of the GN&C automation on Orion are all coordinated via data management, and the database tool provides the ability to test the automation capabilities during the development of the GN&C software. In addition to providing the infrastructure to manage the GN&C automation, the database tool has been designed with capabilities to import and export artifacts for simulation analysis and documentation purposes. Furthermore, the database configuration tool, currently used to manage simulation data, is envisioned to evolve into a mission planning tool for generating and testing GN&C software sequences and configurations. A key enabler of the GN&C automation design, the database tool allows both the creation and maintenance of the data artifacts, as well as serving the critical role of helping to manage, visualize, and understand the data-driven parameters both during software development and throughout the life of the Orion project.

Odegard, Ryan G.↗

Spaceborne computer executive routine functional design specification. Volume 2: Computer executive design for space station/base

The computer executive functional system design concepts derived from study of the Space Station/Base are presented. Information Management System hardware configuration as directly influencing the executive design is reviewed. The hardware configuration and generic executive design requirements are considered in detail in a previous report (System Configuration and Executive Requirements Specifications for Reusable Shuttle and Space Station/Base, 9/25/70). This report defines basic system primitives and delineates processes and process control. Supervisor states are considered for describing basic multiprogramming and multiprocessing systems. A high-level computer executive including control of scheduling, allocation of resources, system interactions, and real-time supervisory functions is defined. The description is oriented to provide a baseline for a functional simulation of the computer executive system.

Kennedy, J. R.↗

Highly reliable processor system for space application.

Description of a redundant processor organization which can be implemented with off-the-shelf processors for fault-tolerant operation. Reconfiguration can be performed automatically in a transientless manner. To support this system configuration and redundancy management concept, an operating system referred to as a synchronous executive has been designed. This system is directed at real-time closed-loop space applications where minimum response time, no degradation of software solution, and system simplicity are of importance. The system is based on a multicomputer organization with each machine solving the same problem based on a common set of inputs. Processor status is fed to a higher-level device which selects a controlling processor for controlling outputs and monitoring computers for fault detection.

Tsou, H. S. E.↗

Space shuttle/food system study. Volume 2, Appendix G: Ground support system analysis. Appendix H: Galley functional details analysis

The capabilities for preflight feeding of flight personnel and the supply and control of the space shuttle flight food system were investigated to determine ground support requirements; and the functional details of an onboard food system galley are shown in photographic mockups. The elements which were identified as necessary to the efficient accomplishment of ground support functions include the following: (1) administration; (2) dietetics; (3) analytical laboratories; (4) flight food warehouse; (5) stowage module assembly area; (6) launch site module storage area; (7) alert crew restaurant and disperse crew galleys; (8) ground food warehouse; (9) manufacturing facilities; (10) transport; and (11) computer support. Each element is discussed according to the design criteria of minimum cost, maximum flexibility, reliability, and efficiency consistent with space shuttle requirements. The galley mockup overview illustrates the initial operation configuration, food stowage locations, meal assembly and serving trays, meal preparation configuration, serving, trash management, and the logistics of handling and cleanup equipment.

Source record↗

Final definition and preliminary design study for the initial atmospheric cloud physics laboratory, a Spacelab mission payload

The following areas related to the final definition and preliminary design study of the initial atmospheric cloud physics laboratory (ACPL) were covered: (1) proposal organization, personnel, schedule, and project management, (2) proposed configurations, (3) study objectives, (4) ACPL experiment program listing and description, (5) mission/flight flexibility and modularity/commonality, (6) study plan, and (7) description of following tasks: requirement analysis and definition task flow, systems analysis and trade studies, subsystem analysis and trade studies, specifications and interface control documents, preliminary design task flow, work breakdown structure, programmatic analysis and planning, and project costs. Finally, an overview of the scientific requirements was presented.

Source record↗