Search NASA⌕ Search

SEARCH · Search NASA

Results for “requirement 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
DOE OSTI2024

A Framework to Assess Advanced Reactor Spent Fuel Management Facility Deployment

Advanced nuclear reactors offer various operational advantages over existing light water reactors but could produce types of spent nuclear fuel (SNF) with a wide variety of forms and characteristics depending on how many different concepts are deployed. Each advanced reactor SNF type potentially poses unique management challenges. New planning efforts will be necessary to anticipate how the management requirements of advanced reactor SNF will affect the deployment of an integrated waste management system. This paper applies a framework of high-level facility deployment milestones to a generic SNF management system, reviewing them together with the advanced reactor SNF characteristics and management requirements. This allows for the investigation of factors that influence facility and system deployment, and ultimately, the identification of challenges facing the deployment of different kinds of SNF management facilities. Here, the back end of the once-through fuel cycle is examined for four advanced reactor system technology types: sodium-cooled fast reactors, high-temperature gas-cooled reactors, liquid-fuel molten salt reactors, and lead-cooled fast reactors. It is observed that milestones earlier in the facility deployment process (e.g., siting and facility design) are more impacted by the uniqueness of advanced reactor SNF characteristics than others (e.g., construction and testing). Ultimately, none of the differences are seen as fundamentally disqualifying in a technical sense; however, they should be considered early, potentially as part of reactor design, to avoid issues in the future.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
NASA NTRS1978

CAD/CAM data management needs, requirements and options

The requirements for a data management system in support of technical or scientific applications and possible courses of action were reviewed. Specific requirements were evolved while working towards higher level integration impacting all phases of the current design process and through examination of commercially marketed systems and related data base research. Arguments are proposed for varied approaches in implementing data base systems ranging from no action necessary to immediate procurement of an existing data base management system.

Lopatka, R. S.↗
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↗
DOE OSTI2024

Hydrodynamic Test Requirements Process Improvements

Hydrodynamic testing at Los Alamos National Laboratory would benefit from a process improvement for the requirements process. Cameo was used as a digital solution for requirements management to allow Lead Engineers to track requirements more effectively. This was identified as a process improvement throughout this Capstone project. This report includes a project proposal, business case, literature review, methodology, project plan, data analysis, decision-making report, financial analysis report, discussion, and conclusion. Initially, this project focused on figuring out a solution for the hydrotest requirement process improvements. The scope narrowed to focus on the use of Cameo for requirement capture and management. During this Capstone, four tests had digital models produced for requirements management in Cameo. The initial model was the baseline, with core requirements used across the tests. Commonalities in tests were used and the core requirements allowed for process efficiencies. In the data analysis, it was seen that overall, the implementation of using Cameo for requirements resulted in a decreasing trend for both schedule and normalized cost. Tests have different complexity levels which is also a factor in how long the requirements process will take. Additional data is needed to continue analyzing process improvements. Through decisionmaking and financial analysis, the recommendation was to use Cameo for requirements process improvement. Multiple experts provided feedback for requirements that were then captured within models. Numerous tangible and intangible benefits were identified with this process improvement. For return on investment, the metric of success was schedule reduction, which was overall seen. Four tests were analyzed, so future analysis will be needed. There is also not a great financial risk because the main cost would be purchasing more licenses. Individuals must generate requirements whether using this software or not. Overall, training is needed to help improve the skillsets of Lead Engineers but is already being supported on a regular frequency. A desktop guide was started associated with explaining the process, however, it is a work in progress. The team plans on adding additional information in the digital models to help status when requirements are met using verification methods and artifacts. From working on this project an improved understanding of Cameo and requirements was the result. There are future opportunities to extend the usage for requirements management and progress will continue after this project.

99 GENERAL AND MISCELLANEOUS↗
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.↗
DOE OSTI2022

Controller Requirements for Managing Community Microgrids

Microgrid control systems are central to the functioning of a microgrid. They are responsible for managing distributed energy resources (DER) in both grid-connected and islanded modes of operation. Although microgrids are being developed and deployed by many utilities, several questions are being raised about the control system that manages them. This document provides the detailed list of requirements for a feeder-level microgrid controller to manage various islanded and grid-connected use cases. Functionally, the use cases include control scenarios that require the controller to maintain energy balance, prevent constraint violations, manage switching equipment, manage grid-forming (GFM) and grid-following (GFL) DER, manage critical/non-critical loads, and coordinate with peer systems to operate joined island areas. In addition to detailed requirements, the document includes interface and performance metrics for functional evaluation. These requirements can be applied to utility-managed microgrid controllers that exclusively manage utility-owned equipment; requirements also apply to third-party managed microgrid controllers that coordinate with the utility- and customer-owned equipment. The document can also be used by technology developers and project developers in industry to specify desired control strategies and performance characteristics for community microgrid controllers.

24 POWER TRANSMISSION AND DISTRIBUTION↗
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.↗