Results for “Configuration Management” — Page 22

NASA NTRS1983

A case study of a system engineered for control by humans

Alternatives to the traditional concepts for real time health and safety operations were examined. The pitfalls of the conventional contingency planning for health and safety are highlighted. The Solar Maximum Mission (SMM) contingency planning and operations provides the evolution from the conventional people intensive health and safety operation, toward a night watchman mode of operations. The SMM spacecraft health and safety operations were budget constrained to the point that one operator was responsible for the health and safety of the entire spacecraft one week after launch. The spacecraft was a protoflight with brand new subsystem configurations, software and procedures. To manage the risks associated with this one man SMM health and safety operation, the real time contingency planning and operations centered around unambiguously identifying a system level problem, and reactively safing components susceptible to unrecoverable damage. The methodology applied to both analyzing and implementing this approach of SMM is shown.

Rothenberg, J.↗

NASA NTRS1988

A Methodology for Multiple Rule System Integration and Resolution Within a Singular Knowledge Base

Expert Systems which support knowledge representation by qualitative modeling techniques experience problems, when called upon to support integrated views embodying description and explanation, especially when other factors such as multiple causality, competing rule model resolution, and multiple uses of knowledge representation are included. A series of prototypes are being developed to demonstrate the feasibility of automating the process of systems engineering, design and configuration, and diagnosis and fault management. A study involves not only a generic knowledge representation; it must also support multiple views at varying levels of description and interaction between physical elements, systems, and subsystems. Moreover, it will involve models of description and explanation for each level. This multiple model feature requires the development of control methods between rule systems and heuristics on a meta-level for each expert system involved in an integrated and larger class of expert system. The broadest possible category of interacting expert systems is described along with a general methodology for the knowledge representation and control of mutually exclusive rule systems.

Kautzmann, Frank N., III↗

NASA NTRS1988

The fast encryption package

The organization of some tools to help improve passwork security at a UNIX-based site is described along with how to install and use them. These tools and their associated library enable a site to force users to pick reasonably safe passwords (safe being site configurable) and to enable site management to try to crack existing passworks. The library contains various versions of a very fast implementation of the Data Encryption Standard and of the one-way encryption functions used to encryp the password.

Bishop, Matt↗

NASA NTRS1988

Orbital Maneuvering Vehicle space station communications design

The authors present an Orbital Maneuvering Vehicle space station communications systems design approach which is intended to satisfy the stringent link requirements. The operational scenario, system configuration, signal design, antenna system management, and link performance analysis are discussed in detail. It is shown that the return link can transmit up to 21.6 Mb/s and maintain at least a 3-dB link margin through proper power and antenna management control at a maximum distance of 37 km. It is suggested that the proposed system, which is compatible with the space station multiple-access system, can be a model for other space station interoperating elements or users to save the development cost and reduce the technical and schedule risks.

Arndt, D.↗

NASA NTRS1990

Proposed definition of the term en route in en route aircraft noise

The problem of en route aircraft noise was examined in a formal, dedicated, setting. Whereas the general meaning of the term en route might be intuitively understood, it is suggested that a precise formal definition of the term en route would be opportune from the outset, especially since the scientific and technical investigation of the problem of noise immissions on the ground from aircraft in flight away from the airspace of an airport may conceivably lead to administrative, regulatory, and legal consequences that would mandatorily require a precise definition of the term en route. Five flight segments, with their differing airframe configurations, engine thrusts, and airspeed management, should form the basis for the differential consideration of the noise immissions perceived on the ground underneath or near the defined segments of the flightpath in en route flight, from the end of the initial climb from an airport after takeoff until the final approach to an airport.

Garbell, Maurice A.↗

NASA NTRS1991

An Historical Perspective of the NERVA Nuclear Rocket Engine Technology Program

Nuclear rocket research and development was initiated in the United States in 1955 and is still being pursued to a limited extent. The major technology emphasis occurred in the decade of the 1960s and was primarily associated with the Rover/NERVA Program where the technology for a nuclear rocket engine system for space application was developed and demonstrated. The NERVA (Nuclear Engine for Rocket Vehicle Application) technology developed twenty years ago provides a comprehensive and viable propulsion technology base that can be applied and will prove to be valuable for application to the NASA Space Exploration Initiative (SEI). This paper, which is historical in scope, provides an overview of the conduct of the NERVA Engine Program, its organization and management, development philosophy, the engine configuration, and significant accomplishments.

Robbins, W. H.↗

NASA NTRS1991

An historical perspective of the NERVA nuclear rocket engine technology program

Nuclear rocket research and development was initiated in the United States in 1955 and is still being pursued to a limited extent. The major technology emphasis occurred in the decade of the 1960s and was primarily associated with the Rover/NERVA Program where the technology for a nuclear rocket engine system for space application was developed and demonstrated. The NERVA (Nuclear Engine for Rocket Vehicle Application) technology developed twenty years ago provides a comprehensive and viable propulsion technology base that can be applied and will prove to be valuable for application to the NASA Space Exploration Initiative (SEI). This paper, which is historical in scope, provides an overview of the conduct of the NERVA Engine Program, its organization and management, development philosophy, the engine configuration, and significant accomplishments.

Robbins, W. H.↗

NASA NTRS1993

Columbus system support for telescience operations

With the given constraints of the space environment, the telescience concept aims at providing a space mission user with optimum flexibility and responsiveness for spaceborne investigations. The concept includes automated system management functions, which allocate and monitor planned resources and time windows, within which the investigator can perform his science interactively responding 'on-line' to experimental data. During the telescience operation, the user is given the capability to send telecommands to the payload from the User Home Base with transparency to the rest of the system. Any violation of the 'booked' time and resources will be detected by the system and reported back to the user for appropriate action. Ultimately, the system will react to maintain the integrity of the system and its payload. Upon completion of the telescience session, the system management function reverses the system configuration and deallocates resources automatically.

Lytton, David W.↗

NASA NTRS2003

Toward a Dynamically Reconfigurable Computing and Communication System for Small Spacecraft

Future science missions will require the use of multiple spacecraft with multiple sensor nodes autonomously responding and adapting to a dynamically changing space environment. The acquisition of random scientific events will require rapidly changing network topologies, distributed processing power, and a dynamic resource management strategy. Optimum utilization and configuration of spacecraft communications and navigation resources will be critical in meeting the demand of these stringent mission requirements. There are two important trends to follow with respect to NASA's (National Aeronautics and Space Administration) future scientific missions: the use of multiple satellite systems and the development of an integrated space communications network. Reconfigurable computing and communication systems may enable versatile adaptation of a spacecraft system's resources by dynamic allocation of the processor hardware to perform new operations or to maintain functionality due to malfunctions or hardware faults. Advancements in FPGA (Field Programmable Gate Array) technology make it possible to incorporate major communication and network functionalities in FPGA chips and provide the basis for a dynamically reconfigurable communication system. Advantages of higher computation speeds and accuracy are envisioned with tremendous hardware flexibility to ensure maximum survivability of future science mission spacecraft. This paper discusses the requirements, enabling technologies, and challenges associated with dynamically reconfigurable space communications systems.

Kifle, Muli↗

NASA NTRS2003

Multi-Disciplinary Analysis for Future Launch Systems Using NASA's Advanced Engineering Environment (AEE)

A new engineering environment constructed for the purposes of analyzing and designing Reusable Launch Vehicles (RLVs) is presented. The new environment has been developed to allow NASA to perform independent analysis and design of emerging RLV architectures and technologies. The new Advanced Engineering Environment (AEE) is both collaborative and distributed. It facilitates integration of the analyses by both vehicle performance disciplines and life-cycle disciplines. Current performance disciplines supported include: weights and sizing, aerodynamics, trajectories, propulsion, structural loads, and CAD-based geometries. Current life-cycle disciplines supported include: DDT&E cost, production costs, operations costs, flight rates, safety and reliability, and system economics. Involving six NASA centers (ARC, LaRC, MSFC, KSC, GRC and JSC), AEE has been tailored to serve as a web-accessed agency-wide source for all of NASA's future launch vehicle systems engineering functions. Thus, it is configured to facilitate (a) data management, (b) automated tool/process integration and execution, and (c) data visualization and presentation. The core components of the integrated framework are a customized PTC Windchill product data management server, a set of RLV analysis and design tools integrated using Phoenix Integration's Model Center, and an XML-based data capture and transfer protocol. The AEE system has seen production use during the Initial Architecture and Technology Review for the NASA 2nd Generation RLV program, and it continues to undergo development and enhancements in support of its current main customer, the NASA Next Generation Launch Technology (NGLT) program.

Monell, D.↗

NASA NTRS2005

Microsystem Cooler Concept Developed and Being Fabricated

A patented microsystem cooler concept has been developed by the NASA Glenn Research Center. It incorporates diaphragm actuators to produce the Stirling refrigeration cycle within a planar configuration compatible with the thermal management of electronics, sensors, optical and radiofrequency systems, microarrays, and other microsystems. The microsystem cooler is most suited to volume-limited applications that require cooling below the ambient or sink temperature. Johns Hopkins University Applied Physics Laboratory is conducting development testing and fabrication of a prototype under a grant from Glenn.

Moran, Matthew E.↗

NASA NTRS2010

Identification and Characterization of Key Human Performance Issues and Research in the Next Generation Air Transportation System (NextGen)

This report identifies key human-performance-related issues associated with Next Generation Air Transportation System (NextGen) research in the NASA NextGen-Airspace Project. Four Research Focus Areas (RFAs) in the NextGen-Airspace Project - namely Separation Assurance (SA), Airspace Super Density Operations (ASDO), Traffic Flow Management (TFM), and Dynamic Airspace Configuration (DAC) - were examined closely. In the course of the research, it was determined that the identified human performance issues needed to be analyzed in the context of NextGen operations rather than through basic human factors research. The main gaps in human factors research in NextGen were found in the need for accurate identification of key human-systems related issues within the context of specific NextGen concepts and better design of the operational requirements for those concepts. By focusing on human-system related issues for individual concepts, key human performance issues for the four RFAs were identified and described in this report. In addition, mixed equipage airspace with components of two RFAs were characterized to illustrate potential human performance issues that arise from the integration of multiple concepts.

Lee, Paul U.↗

NASA NTRS2017

Methods and Apparatus for Deployable Swirl Vanes

An aircraft control structure for drag management includes a nozzle structure configured to exhaust a swirling fluid stream. A plurality of swirl vanes are positioned within the nozzle structure, and an actuation subsystem is configured to cause the plurality of swirl vanes to move from a deployed state to a non-deployed state. In the non-deployed state, the plurality of swirl vanes are substantially flush with the inner surface of the nozzle structure. In the deployed state, the plurality of swirl vanes produce the swirling fluid stream.

Shah, Parthiv N.↗

NASA NTRSDate not supplied

Human Thermal Assessment of Traverse and Geology Task Iterations During Simulated Lunar Extravehicular Activity

Spacewalks or extravehicular activities (EVA) in microgravity are mentally and physically demanding. Current microgravity EVAs are predominantly focused on upper body tasks on engineered surfaces; however, the introduction of gravity means that crew members during future lunar EVAs will be required to perform tasks that generate full body workloads such as navigating natural lunar terrain while conducting geological sampling. To date, only 12 people have walked on the surface of the Moon resulting in limited knowledge of suited thermal regulation under lunar-relevant physical workloads. To address this gap, a study is underway to focus on spacesuit operations with simulated lunar EVA workloads. This study presents methodology for collecting standard thermal measures during suit testing. In this pilot study, two suited subjects underwent simulated lunar EVAs using the NASA Active Response Gravity Offload System (ARGOS) to simulate the effects of partial gravity. Each lunar EVA, lasting three to five hours, included various metabolically demanding EVA tasks. Subjects donned the NASA Mark III (MK III) space suit and were offloaded to 1/6th G (lunar gravity). A subset task circuit from one of these simulations replicated an EVA traverse to a lunar crater, taking a geological sample, and returning to base. The suited subject walked one 1500 m (0% grade) and three 500 m traverses at three different grades (10, 20, 30%). Between each traverse, subjects performed geology sampling tasks (0 and 10% grade). Thermal measurements included core and skin temperature, liquid cooling garment (LCG) inlet and outlet temperature, and spacesuit gas inlet and outlet temperature and humidity. Compared to baseline core temperature (S1 = 37.07±0.32 °C, S2 = 37.27±0.01 °C) and mean skin temperature (S1 = 32.38±0.34 °C, S2 = 33.62±0.03 °C), after a 1500 m traverse, each suited subject showed an increased core temperature (S1 = 37.23±0.12 °C, S2 = 37.41±0.11°C) and decreased mean skin temperature (S1 = 32.16±0.17 °C, S2 = 31.53±1.15 °C) at a delta LCG temperature (S1 = 1.86±0.24 °C, S2 = 2.20±0.76 °C) and delta suit humidity (S1 = 9.66±1.49 %, S2 = 11.50±1.58 %). Core temperature continued to increase from compounding traverse and geology tasks (S1 = 38.04±0.03 °C, S2 = 38.1±0.02 °C) accompanied by an increase in delta LCG temperature (S1 = 2.24±0.13 °C, S2 = 2.67±0.12 °C) and delta suit humidity (S1 = 28±2.42 %, S2 = 31±2.13 %). Conversely, as the circuit progressed, mean skin temperature continued to decrease due to sustained LCG heat rejection (S1 = 30.08±0.15 °C, S2 = 30.28±0.07 °C). During the simulated EVA circuit core temperature increased to elevated values and remained elevated as heat was retained while mean skin temperature decreased due to peripheral heat offloaded to the LCG. The thermal measures collected during this study provided critical heat loading dynamics during lunar EVA tasks. Including core and skin temperatures along with suited thermal measures provides a standard data collection scheme for human thermal metrics during EVA task management. Data collected in this configuration can be used to build future lunar EVA task circuits and human thermal predictions.

Bradley Hoffmann↗

NASA NTRS1984

The representation of manipulable solid objects in a relational database

This project is concerned with the interface between database management and solid geometric modeling. The desirability of integrating computer-aided design, manufacture, testing, and management into a coherent system is by now well recognized. One proposed configuration for such a system uses a relational database management system as the central focus; the various other functions are linked through their use of a common data repesentation in the data manager, rather than communicating pairwise to integrate a geometric modeling capability with a generic relational data managemet system in such a way that well-formed questions can be posed and answered about the performance of the system as a whole. One necessary feature of any such system is simplification for purposes of anaysis; this and system performance considerations meant that a paramount goal therefore was that of unity and simplicity of the data structures used.

Bahler, D.↗

NASA NTRS2018

An “EPIIC” Vision to Evolve Project Integration, Innovation, and Collaboration with Broad Impact for How NASA Executes Complex Projects

Evolving Project Integration, Innovation, and Collaboration (EPIIC) is a vision defined to transform the way projects manage information to support real-time decisions, capture best practices and lessons learned, perform assessments, and manage risk across a portfolio of projects. The foundational project management needs for data and information will be revolutionized through innovations on how we manage and access that data, implement configuration control, and certify compliance. The embedded intelligence of new interactive data interfaces integrate technical and programmatic data such that near real time analytics can be accomplished to more efficiently and accurately complete systems engineering and project management tasks. The system-wide data analytics that are integrated into customized data interfaces allows the growing team of engineers and managers required to develop and implement major NASA missions the ability to access authoritative source(s) of system information while greatly reducing the labor required to complete system assessments. This would allow, for example, much of what is accomplished in a scheduled design review to take place as needed, between any team members, at any time. An intelligent data interface that rigorously integrates systems engineering and project management information in near real time can provide substantially greater insight for systems engineers, project managers, and the large diverse teams required to complete a complex project. System engineers, programmatic personnel (those who focus on cost, schedule, and risk), the technical engineering disciplines, and project management can realize immediate benefit from the shared vision described herein. Implementation of the vision also enables significant improvements in the performance of the engineered system being developed.

Moreland, Robert J.↗

NASA NTRS2022

Making or Breaking a Rover: System Engineering Parameters On-Board the Mars 2020 Perseverance Rover

On February 18, 2021, Perseverance, NASA’s Jet Propulsion Laboratory’s (JPL’s) Mars 2020 Rover, successfully landed on Mars with all systems nominal, despite the risk surrounding the over 200,000 internal flight parameters that had to be properly configured. The Perseverance team defines these parameters as software variables that are configurable, commandable and retrievable from Earth. In 2015, the Mars 2020 project leaders focused on improving systems engineering of parameters based on their experiences from parameter management on previous Mars rovers (Curiosity, Opportunity, Spirit, and Pathfinder) and parameter failures of past missions, such as the mission-ending parameter of the Mars Climate Orbiter. The new rigorous development process allowed for efficient certification and effective implementation of the parameters, allowing the rover to approach and land on the red planet (the most challenging phase of the mission) with zero parameter issues. Although successful, the Perseverance team learned many lessons for how to better manage parameters for the continued surface operations of the Mars 2020 mission and future missions. This paper will discuss eight parameter-management topics for the Perseverance Mission. The first is parameter definition: how we define parameters on our mission, where they are physically located on the vehicle, and why we have so many of them. The second topic is the updated parameter flight software module from Curiosity, including details on the 99% reduction in parameter commands, new bulk configuration capabilities, and improved parameter traceability. The third topic is parameter selection for different mission phases; this includes improving and tweaking our preferred parameter settings until they become certification candidates and managing parameter configurations based on test venue throughout the mission life cycle. The fourth topic is our flight certification process; this includes certification of flight values for four different epochs in the mission: Launch, Entry Decent and Landing (EDL) - 6days, Landing + 5 Sols (Martian Days, still on Cruise Flight Software), and once are on Surface Flight Software (FSW). The fifth topic covers in-flight command implementation, along with details on testing, validation, and verification of those commands. In the sixth section, we will explain our use of open-source management tools, including how we used GitHub for version control and management approvals. The seventh topic will describe the ground tools used in operations, including capabilities of the in-house built tool called Parasol. The eighth and final topic will dig into lessons learned for improving parameter management in the future of this mission and others.

Roth, Brian↗

NASA NTRS2022

Making or Breaking a Rover- Systems Engineering Parameters On-Board the Mars 2020 Perseverance Rover

On February 18, 2021, Perseverance, NASA’s Jet Propulsion Laboratory’s (JPL’s) Mars 2020 Rover, successfully landed on Mars with all systems nominal, despite the risk surrounding the over 200,000 internal flight parameters that had to be properly configured. The Perseverance team defines these parameters as software variables that are configurable, commandable and retrievable from Earth. In 2015, the Mars 2020 project leaders focused on improving systems engineering of parameters based on their experiences from parameter management on previous Mars rovers (Curiosity, Opportunity, Spirit, and Pathfinder) and parameter failures of past missions, such as the mission-ending parameter of the Mars Climate Orbiter. The new rigorous development process allowed for efficient certification and effective implementation of the parameters, allowing the rover to approach and land on the red planet (the most challenging phase of the mission) with zero parameter issues. Although successful, the Perseverance team learned many lessons for how to better manage parameters for the continued surface operations of the Mars 2020 mission and future missions. This paper will discuss eight parameter-management topics for the Perseverance Mission. The first is parameter definition: how we define parameters on our mission, where they are physically located on the vehicle, and why we have so many of them. The second topic is the updated parameter flight software module from Curiosity, including details on the 99% reduction in parameter commands, new bulk configuration capabilities, and improved parameter traceability. The third topic is parameter selection for different mission phases; this includes improving and tweaking our preferred parameter settings until they become certification candidates and managing parameter configurations based on test venue throughout the mission life cycle. The fourth topic is our flight certification process; this includes certification of flight values for four different epochs in the mission: Launch, Entry Decent and Landing (EDL) - 6days, Landing + 5 Sols (Martian Days, still on Cruise Flight Software), and once are on Surface Flight Software (FSW). The fifth topic covers in-flight command implementation, along with details on testing, validation, and verification of those commands. In the sixth section, we will explain our use of open-source management tools, including how we used GitHub for version control and management approvals. The seventh topic will describe the ground tools used in operations, including capabilities of the in-house built tool called Parasol. The eighth and final topic will dig into lessons learned for improving parameter management in the future of this mission and others.

Roth, Brian↗