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 325 records · Page 18

Improving Abundance Estimates of Spring–Summer Snake River Chinook Salmon for Fisheries Management

Abstract The Columbia River basin is home to a run of spring–summer Chinook Salmon Oncorhynchus tshawytscha that returns to the Snake River drainage of Idaho, Oregon, and Washington in the Pacific Northwest. Historically, the run was one of the more productive throughout the Columbia River basin. However, Snake River spring–summer Chinook Salmon have experienced declines in abundance due to overfishing, habitat degradation, and dams. Several stocks are listed as threatened under the U.S. Endangered Species Act and are supported by mitigation hatcheries funded by Idaho Power Company, the Lower Snake River Compensation Plan, and the Bonneville Power Administration. To maximize tribal and state harvest of returning hatchery adults, minimize impacts on wild fish, and ensure that enough hatchery fish return to meet broodstock needs, careful fisheries management is required. Since 2008, managers have used hatchery adults, PIT-tagged as juveniles and detected at Lower Granite Dam, to generate adult abundance estimates. In season, these estimates inform state and tribal harvest shares and ensure that broodstock needs are met. Postseason, they provide smolt-to-adult survival and return rates. Since 2012, parentage-based tagging (PBT) has provided an alternative method to estimate stock- and age-specific returns at Lower Granite Dam, since returning hatchery adults sampled at Lower Granite Dam can be assigned to their parents. We compared stock-specific abundance estimates between PIT- and PBT-derived methodologies for return years 2016–2019. Across all years, PIT tag estimates accounted for 65% of the PBT-based estimates at Lower Granite Dam across all age-groups and release sites combined. This underrepresentation across all groups equated to 49,833 fish that were not accounted for in PIT tag abundance estimates. It is clear that PBT-based estimates should aide in-season harvest management and postseason run reconstruction to avoid the known bias of estimates from PIT tags, especially during years of low returns when increased accuracy is critical.

Coykendall, D. Katharine (ORCID:0000000211482397)↗

Future space transportation requirements for the management of orbital debris

Launch vehicle upper stages continue to contribute to future orbital debris scenarios whenever they undergo explosive propulsion system failures, as well as by remaining on orbit as potential collision targets for smaller orbiting bodies. No active measures have been instituted to date in order to remove nonfunctional satellites or spent rocket stages from earth orbit; they are nevertheless conceivable, and classifiable as (1) orbital-maneuvering retrieval; (2) self-disposal; and (3) propulsive deorbit or atmospheric drag augmentation. Illustrative cases and parametric assessments of these methods' feasibility and cost are presented.

Petro, Andrew J.↗

Work Package 5: Contingency Management. Mission Planning Requirements Document: Preliminary Version. Revision A

The purpose of this document is to identify the general flight/mission planning requirements for same-day file-and-fly access to the NAS for both civil and military High-Altitude Long Endurance (HALE) Unmanned Aircraft System (UAS). Currently the scope of this document is limited to Step 1, operations above flight level 43,000 feet (FL430). This document describes the current applicable mission planning requirements and procedures for both manned and unmanned aircraft and addresses HALE UAS flight planning considerations in the future National Airspace System (NAS). It also discusses the unique performance and operational capabilities of HALE UAS associated with the Access 5 Project, presents some of the projected performance characteristics and conceptual missions for future systems, and provides detailed analysis of the recommended mission planning elements for operating HALE UAS in the NAS.

Source record↗

Risk-Informed Decision Making: Application to Technology Development Alternative Selection

NASA NPR 8000.4A, Agency Risk Management Procedural Requirements, defines risk management in terms of two complementary processes: Risk-informed Decision Making (RIDM) and Continuous Risk Management (CRM). The RIDM process is used to inform decision making by emphasizing proper use of risk analysis to make decisions that impact all mission execution domains (e.g., safety, technical, cost, and schedule) for program/projects and mission support organizations. The RIDM process supports the selection of an alternative prior to program commitment. The CRM process is used to manage risk associated with the implementation of the selected alternative. The two processes work together to foster proactive risk management at NASA. The Office of Safety and Mission Assurance at NASA Headquarters has developed a technical handbook to provide guidance for implementing the RIDM process in the context of NASA risk management and systems engineering. This paper summarizes the key concepts and procedures of the RIDM process as presented in the handbook, and also illustrates how the RIDM process can be applied to the selection of technology investments as NASA's new technology development programs are initiated.

Dezfuli, Homayoon↗

Hazard and Operability Study for the Ammonia Fuel Systems at the National Transportation Research Center

Oak Ridge National Laboratory’s (ORNL’s) Buildings and Transportation Science Division (BTSD) plans to operate research engines fueled by ammonia in two engine test cells at the National Transportation Research Center (NTRC). A scientific need has recently emerged to evaluate the suitability of liquid anhydrous ammonia as a low-lifecycle-carbon fuel source for difficult-to-electrify transportation sectors, including the marine sector. Therefore, BTSD plans to install an ammonia storage and delivery system to 2360 HVC engine research labs L125 (Cell 3) and L111 (Cell 7) capable of delivering 35 and 75 lb/h, respectively. These laboratories are specifically designed to allow for engine and fuels research and development, and they have existing safety systems for mitigating risks associated with toxics and flammables. Anhydrous ammonia is toxic and flammable, and the system will use relatively large quantities compared with standard gas bottles. Ammonia is one of the most widely produced chemicals in the world, and the hazards associated with toxicity and flammability are well understood. Ammonia storage for use in engine research at NTRC is anticipated to take the form of an ammonia tank with capacity of 1,000 water gallons; this quantity will remain below the threshold quantity of 10,000 lb (~2,000 gal) used both by the US Environmental Protection Agency for reporting under the Emergency Planning and Community Right to Know Act and for Risk Management Program requirements, and also by the US Occupational Safety and Health Administration for Process Safety Management requirements. ORNL’s Environmental Protection Services Division was also consulted to verify that the quantities of ammonia anticipated to be used would be in compliance with environmental regulations. The Environmental Protection Services Division staff confirmed that the anticipated quantities fall below ORNL’s permit thresholds. However, because of the hazards associated with anhydrous ammonia, the quantities to be used, and the limited experience with similar quantities of ammonia at ORNL, BTSD decided to perform a hazard and operability (HazOp) study on the ammonia storage and delivery system.

33 ADVANCED PROPULSION SYSTEMS↗

Descoping

Explore the source record for details and available documents.

requirements interaction management requirements e↗

Assessment of Quality Management for Transport Packages Not Requiring Authority Design Approval - 18194

The majority of transports of radioactive materials are carried out in packages which don't need a package design approval of a competent authority. Low active radioactive materials are transported in such kind of packages e.g. in the medical and pharmaceutical industry and in the nuclear industry as well. In Germany the decision to phase out nuclear energy leads to a strong demand for packages to transport low and middle active radioactive waste due to the dismantling and decommissioning of nuclear power plants. According to IAEA regulations the 'non-competent authority approved package types' are the excepted packages and the industrial packages of Type IP-1, IP-2 and IP-3 and of Type A. For the packages of Type IP-2, IP-3 and Type A an assessment by the German competent authority is required for the quality management for the design, manufacture, testing, documentation, use, maintenance and inspection. In general a compliance audit of the manufacturer of the packaging is required during this assessment procedure. Their regulatory level in the IAEA regulations is not comparable with the regulatory density for packages requiring competent authority design approval. The countries apply different approaches within the assessment of the quality assurance measures in the management system as well as in the quality assurance program of a special package design. To use the package or packaging in a safe manner and in compliance with the regulations a management system for each phase of the life of the package or packaging is necessary. In order to help manufactures, which measurements and documents are needed for the assessment procedure, BAM developed a guideline. The guideline BAM-GGR 016 [5] describes the needed quality management for the design, manufacture, testing, documentation, use, maintenance and inspection of a packaging and the package. The poster to be presented will explain the different requirements of the quality assurance measures and give examples. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Using SCOR as a Supply Chain Management Framework for Government Agency Contract Requirements

Enterprise Supply Chain Management consists of: Specifying suppliers to support inter-program and inter-agency efforts. Optimizing inventory levels and locations throughout the supply chain. Executing corrective actions to improve quality and lead time issues throughout the supply chain. Processing reported data to calculate and make visible supply chain performance (provide information for decisions and actions). Ensuring the right hardware and information is provided at the right time and in the right place. Monitoring the industrial base while developing, producing, operating and retiring a system. Seeing performance deep in the supply chain that could indicate issues affecting system availability and readiness.

Paxton, Joe↗

The OpenSE Cookbook: A Practical, Recipe Based Collection of Patterns, Procedures, and Best Practices for Executable Systems Engineering for the Thirty Meter Telescope

The OpenSE Cookbook is an open-sourced collection of patterns, procedures, and best practices targeted for systems engineers who seek guidance on applying model-based and executable systems engineering (MBSE) using SysML. Its content has emerged from the system level modeling effort on the European Framework Program 6 (FP6) and the Thirty Meter Telescope (TMT). The TMT MBSE approach applied the Executable Systems Engineering Method (ESEM) and the open-source Engineering Environment (OpenMBEE) to specify, analyze, and verify requirements of TMT’s Alignment and Phasing System (APS) and the Narrow Field Infrared Adaptive Optics System (NFIRAOS). In these applications, implicit dependencies are made explicit in a formal model through the use of ESEM, OpenMBEE, and SysML modeling constructs. The value proposition for applying this MBSE approach was to establish precise requirements and fine-grained traceability to system designs, and to verify key requirements beginning early in development. The integration of ESEM and the OpenMBEE tooling infrastructure (providing linked-data and web-operability) is a significant added value for the MBSE approach. The APS is responsible for the overall pre-adaptive optics wavefront quality, using starlight to measure wavefront errors and align the TMT optics. In the formally integrated and executable SysML model, simulations are performed to analyze the impact of changed requirements and verify specified constraints for various operational scenarios. The APS team used several modeling patterns to capture information such as the requirements, the operational scenarios, involved subsystems and their interaction points, the estimated or required time durations, and the mass and power consumption. Adaptive optics systems are designed to sense real-time atmospheric turbulence and correct the telescope’s optical beam to remove its effect. The system model for the adaptive optics operational modes was developed to capture sequence behaviors and operational scenarios to run Monte-Carlo simulations for verifying acquisition time, observing efficiency, and operational behavior requirements. The model is particularly useful for investigating the effect of parallelization, identifying interface issues, and re-ordering sequence acquisition tasks. A former version of the Cookbook (which is now updated to MBSE challenges, goals, and lessons learned) included modeling guidelines and conventions for all system aspects, hierarchy levels, and views, which were developed during for the Active Phasing Experiment (APE), an opto-mechatronical system technology demonstrator for the Extremely Large Telescope (ELT). The Cookbook utilizes the above mentioned system models as real-world case-studies to demonstrate and document the applications of the recipes, providing also instructional examples and addressing the available tooling support. The Cookbook is accompanied by a number of SysML models and aodel libraries which facilitate model authoring and maintenance. The Cookbook covers the different aspects of Systems Engineering such as management of Requirements, Design (behavior and structure), Interfaces, Interdisciplinary Integration, Analysis, Trade Studies, and Technical Resources. This paper presents the background, motivation, architecture, and highlights some key content of the Cookbook. For example, interface management, error budget management, requirements verification, Monte Carlo driven analysis, and timing analysis of operational scenarios. The paper discusses how the capabilities of OpenMBEE contributed significantly to the adoption of executable systems engineering.

Brower, Eric↗

Shuttle GPS R/PA evaluation analysis and performance tradeoff study

Primary responsibility was understanding and analyzing the various GPS receiver functions as they relate to the shuttle environment. These receiver functions included acquisition properties of the sequential detector, acquisition and tracking properties of the various receiver phase locked loops, and the techniques of sequential receiver operation. In addition to these areas, support was provided in the areas of oscillator stability requirements, antenna management, and navigation filter requirements, including preposition aiding.

Booth, R. W. D.↗

Mission Operations Report (MOR) for the Solar, Anomalous, and Magnetosphere Particle Explorer (SAMPEX)

MISSION OPERATIONS REPORTS are published for use by NASA senior management, as required by NASA Headquarters Management Instruction HQMI 8610. lC, effective November 26, 1991. The purpose of these reports is to provide a documentation system that represents an internal discipline to establish critical discriminators selected in advance to measure mission accomplishment, provide a formal written assessment of mission accomplishment, and provide an accountability of technical achievement. Prelaunch reports are prepared and issued for each flight project just prior to launch. Following launch, updating (Post Launch) reports are issued to provide mission status and progress in meeting mission objectives. Primary distribution of these reports is intended for personnel having program/project management responsibilities.

Source record↗