Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Requirements 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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2009

From Research to Flight: Surviving the TRL Valley of Death for Robotic and Human Space Exploration

There must be a plan or opportunities for flight validation: a) To reduce the bottleneck of new technologies at the TRL Valley of Death; b) To allow frequent infusion of new technologies into flight missions. Risk must be tolerated for new technology flight experiments. Risk must also be accepted on early-adopting missions to enable new capabilities. Fundamental research is critical to taking the next giant leap in the scientific exploration of space. Technology push is often required to meet current mission requirements. Technology management requires more than issuing NRAs and overseeing contracts.

Johnson, Les↗
NASA NTRS2009

From Research to Flight: Surviving the TRL Valley of Death for Robotic and Human Exploration

Fundamental research is critical to taking the next giant leap in the scientific exploration of space. NASA should be pushing the envelope and asking "what if?" .. Technology push enables new capabilities. When NASA began, everything was enabling. .. Technology pull is often required to meet current mission requirements. Technology management requires more than issuing NRAs and overseeing contracts. Continuous assessment, peer review, and system systems studies are vital to credible TRL advancement. A strategy for taking technology R&D to new heights will lead to discoveries at far-reaching destinations..

Johnson, Les↗
NASA NTRS2019

Requirements Development and Management on the Psyche Project

In January 2017, Psyche was one of two mission concepts selected by NASA for flight as part of the 14th Discovery mission competition. The project has been staffing up and maturing the spacecraft, instrument and mission system baseline designs on the path towards a 2022 launch. During much of 2018, the Project has been executing the lifecycle stage called Phase B, “Preliminary Design and Technology Completion,” one key element of which is the development and management of requirements at various levels. In the case of the Psyche project, this process has been particularly unique for several reasons. The project utilizes a Solar Electric Propulsion (SEP) Chassis from Space Systems Loral (SSL), a high volume manufacturer of commercial geostationary (GEO) telecom spacecraft based on the 1300 satellite bus. While SSL has an extensive, well-vetted set of requirements based on their very successful Earth-orbiting product line, translating that heritage to a deep space science mission required special care. In addition to the differences associated with the deep space environment and longer communication times, new interfaces had to be incorporated. While a substantial portion of the Flight System consists of the SEP Chassis, there were several new interfaces within various subsystems between SSL components and those provided by JPL and other contractors. Managing these interfaces through requirements at a relatively higher level than normally seen on internal or external builds proved challenging. Finally, the Psyche spacecraft plans to host the flight terminal of the Deep Space Optical Communications (DSOC) technology demonstration, which is itself a separate project with its own requirements that must be flowed down and managed. This paper will present an overview of the requirement development and management process for the Psyche project. It will discuss in detail the various challenges summarized above, the methods and decisions chosen to address them, and evaluate their overall effectiveness at this stage in the project.

Elkins-Tanton, Linda T.↗
NASA NTRS1979

Development of Integrated Programs for Aerospace-vehicle design (IPAD): Integrated information processing requirements

The engineering-specified requirements for integrated information processing by means of the Integrated Programs for Aerospace-Vehicle Design (IPAD) system are presented. A data model is described and is based on the design process of a typical aerospace vehicle. General data management requirements are specified for data storage, retrieval, generation, communication, and maintenance. Information management requirements are specified for a two-component data model. In the general portion, data sets are managed as entities, and in the specific portion, data elements and the relationships between elements are managed by the system, allowing user access to individual elements for the purpose of query. Computer program management requirements are specified for support of a computer program library, control of computer programs, and installation of computer programs into IPAD.

Southall, J. W.↗
NASA NTRS1972

Crew interface specifications preparation for in-flight maintenance and stowage functions

The findings and data products developed during the Phase 2 crew interface specification study are presented. Five new NASA general specifications were prepared: operations location coding system for crew interfaces; loose equipment and stowage management requirements; loose equipment and stowage data base information requirements; spacecraft loose equipment stowage drawing requirements; and inflight stowage management data requirements. Additional data was developed defining inflight maintenance processes and related data concepts for inflight troubleshooting, remove/repair/replace and scheduled maintenance activities. The process of maintenance task and equipment definition during spacecraft design and development was also defined and related data concepts were identified for futher development into formal NASA specifications during future follow-on study phases of the contract.

Parker, F. W.↗
NASA NTRS2008

Record Management and Design Reuse

Government mandated records management requirements apply to retention and long term archival of a wide variety of records. Part of the attention is on permanent accession and retention by the U.S. National Archives and Records Administration (NARA) but interim requirements for storage by the source agency are included. As government agencies and the Department of Defense move toward implementations, additional goals often include saving design data for reuse. This paper briefly reviews the government records management requirements then investigates candidate meanings of 'reuse' and proposes an enhanced design records retention approach. The recommended strategy that emerges is, for a given program or product family, to invest in rich and readily re-executable preservation of design artifacts for one or two subsequent generations, then downgrade the data in utility through conversions, ultimately reaching the NARA minimum standard for permanent historical-interest archives.

permanent accession↗
NASA NTRS1989

Cryogenic fluid management technology requirements for the Space Transfer Vehicle

An in-house study was performed to design a cryogenic Space Transfer Vehicle (STV) for the late 1990s that can evolve with the demanding mission requirements of the manned exploration initiatives. An assessment of cryogenic fluid management technology issues associated with the STV was performed to identify technology gaps and propose advanced development activities.

Cramer, John M.↗
NASA NTRS1991

EMASS (trademark): An expandable solution for NASA space data storage needs

The data acquisition, distribution, processing, and archiving requirements of NASA and other U.S. Government data centers present significant data management challenges that must be met in the 1990's. The Earth Observing System (EOS) project alone is expected to generate daily data volumes greater than 2 Terabytes (2 x 10(exp 12) Bytes). As the scientific community makes use of this data, their work will result in larger, increasingly complex data sets to be further exploited and managed. The challenge for data storage systems is to satisfy the initial data management requirements with cost effective solutions that provide for planned growth. The expendable architecture of the E-Systems Modular Automated Storage System (EMASS(TM)), a mass storage system which is designed to support NASA's data capture, storage, distribution, and management requirements into the 21st century is described.

Peterson, Anthony L.↗
NASA NTRS1992

EMASS (tm): An expandable solution for NASA space data storage needs

The data acquisition, distribution, processing, and archiving requirements of NASA and other U.S. Government data centers present significant data management challenges that must be met in the 1990's. The Earth Observing System (EOS) project alone is expected to generate daily data volumes greater than 2 Terabytes (2(10)(exp 12) Bytes). As the scientific community makes use of this data their work product will result in larger, increasingly complex data sets to be further exploited and managed. The challenge for data storage systems is to satisfy the initial data management requirements with cost effective solutions that provide for planned growth. This paper describes the expandable architecture of the E-Systems Modular Automated Storage System (EMASS (TM)), a mass storage system which is designed to support NASA's data capture, storage, distribution, and management requirements into the 21st century.

Peterson, Anthony L.↗
NASA NTRS2012

Vehicle Health Management Communications Requirements for AeroMACS

As the development of standards for the aeronautical mobile airport communications system (AeroMACS) progresses, the process of identifying and quantifying appropriate uses for the system is progressing. In addition to defining important elements of AeroMACS standards, indentifying the systems uses impacts AeroMACS bandwidth requirements. Although an initial 59 MHz spectrum allocation for AeroMACS was established in 2007, the allocation may be inadequate; studies have indicated that 100 MHz or more of spectrum may be required to support airport surface communications. Hence additional spectrum allocations have been proposed. Vehicle health management (VHM) systems, which can produce large volumes of vehicle health data, were not considered in the original bandwidth requirements analyses, and are therefore of interest in supporting proposals for additional AeroMACS spectrum. VHM systems are an emerging development in air vehicle safety, and preliminary estimates of the amount of data that will be produced and transmitted off an aircraft, both in flight and on the ground, have been prepared based on estimates of data produced by on-board vehicle health sensors and initial concepts of data processing approaches. This allowed an initial estimate of VHM data transmission requirements for the airport surface. More recently, vehicle-level systems designed to process and analyze VHM data and draw conclusions on the current state of vehicle health have been undergoing testing and evaluation. These systems make use of vehicle system data that is mostly different from VHM data considered previously for airport surface transmission, and produce processed system outputs that will be also need to be archived, thus generating additional data load for AeroMACS. This paper provides an analysis of airport surface data transmission requirements resulting from the vehicle level reasoning systems, within the context of overall VHM data requirements.

Kerczewski, Robert J.↗
NASA NTRS1995

Advanced transportation system studies. Technical area 2: Heavy lift launch vehicle development: Technical Results - Volume 2

Sections 10 to 13 of the Advanced Transportation System Studies final report are included in this volume. Section 10 contains a copy of an executive summary that was prepared by Lockheed Space Operations Company (LSOC) to document their support to the TA-2 contract during the first-year period of performance of the contract, May 1992 through May 1993. LSOC participated on the TA-2 contract as part of the concurrent engineering launch system definition team, and provided outstanding heavy lift launch vehicle (HLLV) ground operations requirements and concept assessments for Lockheed Missiles and Space Company (LMSC) through an intercompany work transfer as well as providing specific HLLV ground operations assessments at the direction of NASA KSC through KSC funding that was routed to the TA-2 contract. Section 11 contains a copy of a vehicle-independent, launch system health management requirements assessment. The purpose of the assessment was to define both health management requirements and the associated interfaces between a generic advanced transportation system launch vehicle and all related elements of the entire transportation system, including the ground segment. Section 12 presents the major TA-2 presentations provided to summarize the significant results and conclusions that were developed over the course of the contract. Finally, Section 13 presents the design and assessment report on the first lunar outpost heavy lift launch vehicle.

Source record↗
NASA NTRS2005

Step 1: Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Contingency Management

This document involves definition of technology interface requirements for Contingency Management. This was performed through a review of Contingency Management-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Contingency Management Work Package were considered. Beginning with HSI high-level functional requirements for Contingency Management, and Contingency Management technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of system failures and associated contingency procedures, and (2) the control capability needed by the pilot to obtain system status and procedure information. Fundamentally, these requirements provide the candidate Contingency Management technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Contingency Management operations and functions should interface with the pilot to provide the necessary Contingency Management functionality to the UA-pilot system. Requirements and guidelines for Contingency Management are partitioned into four categories: (1) Health and Status and (2) Contingency Management. Each requirement is stated and is supported with a rationale and associated reference(s).

Source record↗
NASA NTRS2005

Influence of Planetary Protection Guidelines on Waste Management Operations

Newly outlined missions in the Space Exploration Initiative include extended human habitation on Mars. During these missions, large amounts of waste materials will be generated in solid, liquid and gaseous form. Returning these wastes to Earth will be extremely costly, and will therefore likely remain on Mars. Untreated, these wastes are a reservoir of live/dead organisms and molecules considered to be "biomarkers" i.e., indicators of life). If released to the planetary surface, these materials can potentially confound exobiology experiments and disrupt Martian ecology indefinitely (if existent). Waste management systems must therefore be specifically designed to control release of problematic materials both during the active phase of the mission, and for any specified post-mission duration. To effectively develop waste management requirements for Mars missions, planetary protection guidelines must first be established. While previous policies for Apollo lunar missions exist, it is anticipated that the increased probability of finding evidence of life on Mars, as well as the lengthy mission durations will initially lead to more conservative planetary protection measures. To facilitate the development of overall requirements for both waste management and planetary protection for future missions, a workshop was conducted to identify how these two areas interface, and to establish a preliminary set of planetary protection guidelines that address waste management operations. This paper provides background regarding past and current planetary protection and waste management issues, and their interactions. A summary of the recommended planetary protection guidelines, anticipated ramifications and research needs for waste management system design for both forward (Mars) and backward (Earth) contamination is also provided.

Hogan, John A.↗
NASA NTRS2007

Earth Observations to Assess Impact of Hurricane Katrina on John C. Stennis Space Center

The peril from hurricanes to Space Operations Centers is real and is forecast to continue; Katrina, Rita, and Wilma of 2005 and Charley, Frances, Ivan, and Jeanne of 2004 are sufficient motivation for NASA to develop a multi-Center plan for preparedness and response. As was demonstrated at SSC (Stennis Space Center) in response to Hurricane Katrina, NASA Centers are efficiently activated as local command centers, playing host to Federal and State agencies and first responders to coordinate and provide evacuation, relocation, response, and recovery activities. Remote sensing decision support provides critical insight for managing NASA infrastructure and for assisting Center decision makers. Managers require geospatial information to manage the federal city. Immediately following Katrina, SSC s power and network connections were disabled, hardware was inoperative, technical staff was displaced and/or out of contact, and graphical decision support tools were non-existent or less than fully effective. Despite this circumstance, SSC EOC (Emergency Operations Center) implemented response operations to assess damage and to activate recovery plans. To assist Center Managers, the NASA ASP (Applied Sciences Program) made its archive of high-resolution data over the site available. In the weeks and months after the immediate crisis, NASA supplemented this data with high-resolution, post-Katrina imagery over SSC and much of the affected coastal areas. Much of the high-resolution imagery was made available through the Department of Defense Clear View contract and was distributed through U.S. Geological Survey Center for Earth Resources Observation and Science "Hurricane Katrina Disaster Response" Web site. By integrating multiple image data types with other information sources, ASP applied an all-source solutions approach to develop decision support tools that enabled managers to respond to critical issues, such as expedient access to infrastructure and deployment of resources, provision of temporary shelter, logistical control of critical supplies, and the mobilization and coordination of assets from ground crews to aircraft/airspace management. Furthermore, ASP developed information products that illustrate risks to SSC's infrastructure from surge, inundation, and flood. Current plans include developing wind-risk prototype products for refinement and adoption into EOC plans.

Graham, William D.↗
DOE OSTI2024

LSE-61: Rubin Observatory Data Management System (DMS) Requirements

This document contains the top-level requirements for the Data Management subsystem of the LSST, when combined with the Data Management-related requirements in the LSST System Requirements (LSR, LSE-29) and Observatory System Specifications (OSS, LSE-30).

79 ASTRONOMY AND ASTROPHYSICS↗
NASA NTRSDate not supplied

Implementing an Objectives-Driven, Risk-Informed, and Case-Assured Approach to Safety and Mission Success at NASA

NASA is developing a “Standard for Assurance of Space Flight Safety and Mission Success” that implements an objectives-driven, risk-informed, and case-assured approach to safety and mission success (S&MS) for NASA space flight programs and projects. The standard aligns with the philosophy of risk leadership that has recently been established in NASA policy to assure acceptable levels of flight crew safety and mission success risk. It is consistent with existing NASA risk management requirements and is compatible with NASA program management and systems engineering requirements. The methodology described in the standard is presented in terms of an S&MS assurance framework that is designed to allow substantial flexibility in the specific means by which programs and projects achieve acceptable mission S&MS risk. Such flexibility is necessary to accommodate the increasingly broad range of acquisition strategies employed by NASA, including commercial transportation services, as well as to accommodate the increasingly rapid evolution of space flight-related technologies and practices. A key feature of the S&MS assurance framework is the specification of S&MS success criteria for each life-cycle review (LCR). The S&MS assurance case is structured around these criteria, the satisfaction of which indicates that the program/project is adhering to the S&MS risk posture. This enables the evolving S&MS assurance case to be used as a fundamental program/project submittal at each LCR, where its inherent structure of argument, supported by evidence, directly supports the evaluation of the program/project with respect to the S&MS success criteria, and by extension, the S&MS risk posture. As such, the S&MS assurance case is integral to program/project systems engineering, risk management, and S&MS oversight activities, and provides the principal basis for S&MS risk acceptance by the Decision Authority throughout the program/project life cycle.

Risk Posture↗