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 109 records · Page 6

NASA Space Flight Program and Project Management Handbook

This handbook is the companion document to NPR 7120.5F, NASA Space Flight Program and Project Management Requirements. It represents the accumulation of knowledge on managing program and projects derived from NASA’s human, robotic, and scientific missions. It incorporates the “corporate knowledge” for existing and future NASA space flight programs and projects, including NASA’s Artemis missions to establish a sustainable human presence on the Moon through collaboration with commercial and international partners, NASA’s James Webb Space Telescope (JWST) mission, and NASA’s robotic missions on Mars. The practices discussed have evolved as a function of NASA’s core values of safety, integrity, teamwork, excellence, and inclusion, and may also prove a resource for other agencies, the private sector, and academia. The knowledge gained from the Agency’s victories and defeats, including the checks and balances and initiatives to better control cost and risk, provides a foundation for continuing an exciting and healthy space program. This handbook provides implementation guidance for NPR 7120.5F and includes the changes and updates to key procedural requirements in NPR 7120.5F since NPR 7120.5E. The goal of the NPR requirements is to ensure programs and projects are developed and successfully executed in the most cost-effective and efficient manner possible. This handbook provides context, rationale, and explanation to facilitate the application of requirements and to pass on some of the hard-won best practices and lessons learned.

Tracy L Osborne↗

An Overview of Project Planning for Hot-Isostatic Pressure Treatment of High-Level Waste Calcine for the Idaho Cleanup Project - 12289

The Calcine Disposition Project is responsible for retrieval, treatment by hot-isostatic pressure, packaging, and disposal of highly radioactive calcine stored at the Idaho Nuclear Technology and Engineering Center at the Idaho National Laboratory Site in southeast Idaho. In the 2009 Amended Record of Decision: Idaho High-Level Waste and Facilities Disposition Final Environmental Impact Statement the Department of Energy documented the selection of hot-isostatic pressure as the technology to treat the calcine. The Record of Decision specifies that the treatment results in a volume-reduced, monolithic waste form suitable for transport outside of Idaho by a target date of December 31, 2035. That target date is specified in the 1995 Idaho Settlement Agreement to treat and prepare the calcine for transport out of Idaho in exchange for allowing storage of Navy spent nuclear fuel at the INL Site. The project is completing the design of the calcine-treatment process and facility to comply with Record of Decision, Settlement Agreement, Idaho Department of Environmental Quality, and Department of Energy requirements. A systems engineering approach is being used to define the project mission and requirements, manage risks, and establish the safety basis for decision making in compliance with DOE O 413.3B, 'Program and Project Management for the Acquisition of Capital Assets'. The approach draws heavily on 'design-for-quality' tools to systematically add quality, predict design reliability, and manage variation in the earliest possible stages of design when it is most efficient. Use of these tools provides a standardized basis for interfacing systems to interact across system boundaries and promotes system integration on a facility-wide basis. A mass and energy model was developed to assist in the design of process equipment, determine material-flow parameters, and estimate process emissions. Data generated from failure modes and effects analysis and reliability, availability, maintainability, and inspectability analysis were incorporated into a time and motion model to validate and verify the capability to complete treatment of the calcine within the required schedule. The Calcine Disposition Project systems engineering approach, including use of industry-proven design-for-quality tools and quantitative assessment techniques, has strengthened the project's design capability to meet its intended mission in a safe, cost-effective, and timely manner. Use of these tools has been particularly helpful to the project in early design planning to manage variation; improve requirements and high-consequence risk management; and more effectively apply alternative, interface, failure mode, RAMI, and time and motion analyses at the earliest possible stages of design when their application is most efficient and cost effective. The project is using these tools to design and develop HIP treatment of highly radioactive calcine to produce a volume-reduced, monolithic waste form with immobilization of hazardous and radioactive constituents. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Documentation pckage for the RFID temperature monitoring system (Of Model 9977 packages at NTS).

The technical basis for extending the Model 9977 shipping package periodic maintenance beyond the one-year interval to a maximum of five years is based on the performance of the O-ring seals and the environmental conditions. The DOE Packaging Certification Program (PCP) has tasked Argonne National Laboratory to develop a Radio-Frequency Identification (RFID) temperature monitoring system for use by the facility personnel at DAF/NTS. The RFID temperature monitoring system, depicted in the figure below, consists of the Mk-1 RFId tags, a reader, and a control computer mounted on a mobile platform that can operate as a stand-alone system, or it can be connected to the local IT network. As part of the Conditions of Approval of the CoC, the user must complete the prescribed training to become qualified and be certified for operation of the RFID temperature monitoring system. The training course will be administered by Argonne National Laboratory on behalf of the Headquarters Certifying Official. This is a complete documentation package for the RFID temperature monitoring system of the Model 9977 packagings at NTS. The documentation package will be used for training and certification. The table of contents are: Acceptance Testing Procedure of MK-1 RFID Tags for DOE/EM Nuclear Materials Management Applications; Acceptance Testing Result of MK-1 RFID Tags for DOE/EM Nuclear Materials Management Applications; Performance Test of the Single Bolt Seal Sensor for the Model 9977 Packaging; Calibration of Built-in Thermistors in RFID Tags for Nevada Test Site; Results of Calibration of Built-in Thermistors in RFID Tags; Results of Thermal Calibration of Second Batch of MK-I RFID Tags; Procedure for Installing and Removing MK-1 RFID Tag on Model 9977 Drum; User Guide for RFID Reader and Software for Temperature Monitoring of Model 9977 Drums at NTS; Software Quality Assurance Plan (SQAP) for the ARG-US System; Quality Category for the RFID Temperature Monitoring System; The Documentation Package for the RFID Temperature Monitoring System; Software Test Plan and Results for ARG-US OnSite; Configuration Management Plan (CMP) for the ARG-US System; Requirements Management Plan for the ARG-US System; and Design Management Plan for ARG-US.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

An approach to improve management visibility within the procurement and financial group at Goldstone

Improvements in the operational efficiency of the data management systems at the Goldstone Deep Space Communications Complex (GDSCC) are discussed. This addresses the existing procurement and financial management data system at GDSCC, identifies management requirements for better visibility, describes a proposed computerized data management system, summarizes results to data, and identifies plans for future development.

Maiocco, F. R.↗

Data management for Computer-Aided Engineering (CAE)

Analysis of data flow through the design and manufacturing processes has established specific information management requirements and identified unique problems. The application of data management technology to the engineering/manufacturing environment addresses these problems. An overview of the IPAD prototype data base management system, representing a partial solution to these problems, is presented here.

Bryant, W. A.↗

Using expert systems to implement a semantic data model of a large mass storage system

The successful development of large volume data storage systems will depend not only on the ability of the designers to store data, but on the ability to manage such data once it is in the system. The hypothesis is that mass storage data management can only be implemented successfully based on highly intelligent meta data management services. There now exists a proposed mass store system standard proposed by the IEEE that addresses many of the issues related to the storage of large volumes of data, however, the model does not consider a major technical issue, namely the high level management of stored data. However, if the model were expanded to include the semantics and pragmatics of the data domain using a Semantic Data Model (SDM) concept, the result would be data that is expressive of the Intelligent Information Fusion (IIF) concept and also organized and classified in context to its use and purpose. The results are presented of a demonstration prototype SDM implemented using the expert system development tool NEXPERT OBJECT. In the prototype, a simple instance of a SDM was created to support a hypothetical application for the Earth Observing System, Data Information System (EOSDIS). The massive amounts of data that EOSDIS will manage requires the definition and design of a powerful information management system in order to support even the most basic needs of the project. The application domain is characterized by a semantic like network that represents the data content and the relationships between the data based on user views and the more generalized domain architectural view of the information world. The data in the domain are represented by objects that define classes, types and instances of the data. In addition, data properties are selectively inherited between parent and daughter relationships in the domain. Based on the SDM a simple information system design is developed from the low level data storage media, through record management and meta data management to the user interface.

Roelofs, Larry H.↗

Closed Loop Requirements and Analysis Management

Effective systems engineering involves the use of analysis in the derivation of requirements and verification of designs against those requirements. The initial development of requirements often depends on analysis for the technical definition of specific aspects of a product. Following the allocation of system-level requirements to a product's components, the closure of those requirements often involves analytical approaches to verify that the requirement criteria have been satisfied. Meanwhile, changes that occur in between these two processes need to be managed in order to achieve a closed-loop requirement derivation/verification process. Herein are presented concepts for employing emerging Team center capabilities to jointly manage requirements and analysis data such that analytical techniques are utilized to effectively derive and allocate requirements, analyses are consulted and updated during the change evaluation processes, and analyses are leveraged during the design verification process. Recommendations on concept validation case studies are also discussed.

Lamoreaux, Michael↗

NASA Standing Review Board Handbook

This handbook provides guidance based on best practices for the planning, preparation, review, reporting, and closeout of Standing Review Board (SRB) activities. Revision C updates the Revision B version of the SRB Handbook published in 2016 to incorporate updates to NASA Procedural Requirements (NPR) 7120.5F, NASA Space Flight Program and Project Management Requirements. These updates include: - Changing the Dissenting Opinion process to the Formal Dissent process, which retains the current process augmented with an expedited escalation path. - Updates to requirements for establishing an Agency Baseline Commitment (ABC) and for performing Joint Cost and Schedule Confidence Level (JCL) analyses for tightly coupled programs. - Additional requirements for performing a JCL analysis for single-project programs and projects over $1B Life-Cycle Cost (LCC). - Use of initial capability cost estimates instead of LCC estimates in specific, identified instances for single-project programs and projects that plan continuing operations and production, including integration of capability upgrades, with an unspecified Phase E end point. These single-project programs and projects define an initial capability during Phase A and develop an initial capability cost that establishes the ABC at Key Decision Point (KDP) C. Initial capability is the first operational mission flight (or as defined in the KDP B Review Plan) and is documented in the KDP B Decision Memorandum. Initial capability cost includes operations cost for the initial capability. The Phase E cost estimate for continuing operations and production is established separately as part of the Operational Readiness Review (ORR) and KDP E for the 5 years after initial capability and subsequently updated and documented annually for the next 5-year period. Upgrades during Phase E that meet the Agency criteria for a major project for external reporting are treated as projects for the purposes of establishing their own development ABC outside the Phase E cost estimate. The Phase E cost estimate is updated to include production and operations costs associated with these upgrades. Development, production, and operations costs of other (i.e., non-major) upgrades are included in the Phase E cost estimate. (See NPR 7120.5, Sections 2.4.1.5 and 2.4.1.6 and the NASA Space Flight Program and Project Management Handbook (PM Handbook), Section 5.5.4 for additional information.) The scope of the SRB’s assessment with respect to initial capability, Phase E cost estimate, and major upgrades for these single-project programs and projects is defined in the Terms of Reference (ToR).

Kevin Michael Gilligan↗

Best practice data life cycle approaches for the life sciences

Throughout history, the life sciences have been revolutionised by technological advances; in our era this is manifested by advances in instrumentation for data generation, and consequently researchers now routinely handle large amounts of heterogeneous data in digital formats. The simultaneous transitions towards biology as a data science and towards a ‘life cycle’ view of research data pose new challenges. Researchers face a bewildering landscape of data management requirements, recommendations and regulations, without necessarily being able to access data management training or possessing a clear understanding of practical approaches that can assist in data management in their particular research domain. Here we provide an overview of best practice data life cycle approaches for researchers in the life sciences/bioinformatics space with a particular focus on ‘omics’ datasets and computer-based data processing and analysis. We discuss the different stages of the data life cycle and provide practical suggestions for useful tools and resources to improve data management practices.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

Talent Acquisition in Scientific and Engineering Disciplines: A Case Study of National Laboratory (TASED) [Thesis]

Identifying the hindrances to performing effective talent acquisition within the science, technology, engineering, and mathematics field is an important topic for technical hiring managers. Top candidates have multiple options during highly competitive market conditions requiring managers to look for unique solutions which diverge from competition. Prior to this study there has been very little research considering national laboratory research and development challenges from a technical hiring manager’s talent acquisition perspective. Utilizing a unique combination of national laboratory multi-organization survey, pilot study, Human Resource (HR) tracking data and trust based business strategy to enhance partnering this research finds hiring managers can leverage out of the box techniques to improve internal processes while developing industry support to target highly qualified individuals. This methodology could be utilized by technical hiring managers across federal national laboratory enterprise to effectively capture next generation staff and leadership talent who align with their organization professionally as well as social culture.

99 GENERAL AND MISCELLANEOUS↗

New developments in RTR fuel recycling

As most utilities in the world, Research and Test Reactors (RTR) operators are currently facing two challenges regarding the fuel, in order to comply with local safety and waste management requirements as well as global non-proliferation obligation: - How to manage used fuel today, and - How fuel design changes that are currently under development will influence used fuel management. AREVA-La-Hague plant has a large experience in used fuel recycling, including traditional RTR fuel (UAl). Based on that experience and deep knowledge of RTR fuel manufacturing, AREVA is currently examining possible options to cope with both challenges. This paper describes the current experience of AREVA-La-Hague in UAl used fuels recycling and its plan to propose recycling for various types of fuels such as U{sub 3}Si{sub 2} fuel or UMo fuel on an industrial scale. (authors)

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

The total Earth Resources System of the 1980's: A view of the future

The study was organized to address the total earth resources system in the broadest sense: distinguishing characteristics of the resources form the input, and information from user models forms the output. The effort began with a treatment of resource management requirements which traced information needs back to budgets, laws, and charters. These requirements were used to structure a 1980's scenario and to define thirty broad resource management missions (or applications) which could be confidently expected to be carried out by the future system. A classical systems approach was followed to assess the current state-of-the-art, structure system requirements, and to define the necessary platforms, sensors, and ground system architecture. The study of two resource management missions in additional detail was conducted to illuminate problems of transition from R&D to operational systems. The space shuttle's role in the system received special attention and a mission able to be served by an early flight was defined.

Cheeseman, C. E.↗

Guidance and Recommendations for Streamlining Reporting for Federal Energy and Water Efficiency Projects

Federal agencies are required to report on their progress in meeting various energy and water management requirements. These reporting requirements encompass energy and water projects at federal facilities, including projects that are alternatively financed, e.g., conducted through energy savings performance contracts (ESPCs) or utility energy service contracts (UESCs). The purpose of this guidance is to provide recommendations to streamline federal agency reporting. The guidance recommends the use of eProject Builder (ePB), a project development and archiving tool for energy projects. ePB carries additional value in its simplification of federal agency reporting by dovetailing with the Federal Energy Management Program’s (FEMP’s) EISA 432 Compliance Tracking System (CTS).

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Issues in NASA program and project management

This volume is the eighth in an ongoing series addressing current topics and lessons learned in NASA program and project management. Articles in this volume cover the following topics: (1) power sources for the Galileo and Ulysses Missions; (2) managing requirements; (3) program control of the Tropical Rainfall Measuring Mission; (4) project management method; (5) career development for project managers; and (6) resources for NASA managers.

Hoffman, Edward J.↗

SOFIA Program SE and I Lessons Learned

Once a "Troubled Project" threatened with cancellation, the Stratospheric Observatory for Infrared Astronomy (SOFIA) Program has overcome many difficult challenges and recently achieved its first light images. To achieve success, SOFIA had to overcome significant deficiencies in fundamental Systems Engineering identified during a major Program restructuring. This presentation will summarize the lessons learn in Systems Engineering on the SOFIA Program. After the Program was reformulated, an initial assessment of Systems Engineering established the scope of the problem and helped to set a list of priorities that needed to be work. A revised Systems Engineering Management Plan (SEMP) was written to address the new Program structure and requirements established in the approved NPR7123.1A. An important result of the "Technical Planning" effort was the decision by the Program and Technical Leadership team to re-phasing the lifecycle into increments. The reformed SOFIA Program Office had to quickly develop and establish several new System Engineering core processes including; Requirements Management, Risk Management, Configuration Management and Data Management. Implementing these processes had to consider the physical and cultural diversity of the SOFIA Program team which includes two Projects spanning two NASA Centers, a major German partnership, and sub-contractors located across the United States and Europe. The SOFIA Program experience represents a creative approach to doing "System Engineering in the middle" while a Program is well established. Many challenges were identified and overcome. The SOFIA example demonstrates it is never too late to benefit from fixing deficiencies in the System Engineering processes.

Ray, Ronald J.↗

Functional Requirements for Onboard Management of Space Shuttle Consumables

This report documents the results of the study "Functional Requirements for Onboard Management of Space Shuttle Consumables." The study was conducted for the Mission Planning and Analysis Division of the NASA Lyndon B. Johnson Space Center, Houston, Texas, between 3 July 1972 and 16 November 1973. The overall study program objective was two-fold. The first objective was to define a generalized consumable management concept which is applicable to advanced spacecraft. The second objective was to develop a specific consumables management concept for the Space Shuttle vehicle and to generate the functional requirements for the onboard portion of that concept. Consumables management is the process of controlling or influencing the usage of expendable materials involved in vehicle subsystem operation. The report consists of two volumes. Volume I presents a description of the study activities related to general approaches for developing consumable management, concepts for advanced spacecraft applications, and functional requirements for a Shuttle consumables management concept. Volume II presents a detailed description of the onboard consumables management concept proposed for use on the Space Shuttle.

Graf, P. J.↗

Lessons Learned With Risk Management: A Systems Engineer's Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

Lessons Learned With Risk Management: A Systems Engineer’s Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗