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 73 records · Page 4

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.↗

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↗

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.↗

Tethys: The Marine and Hydrokinetic Technology Environmental Impacts Knowledge Management System -- Requirements Specification -- Version 1.0

The marine and hydrokinetic (MHK) environmental impacts knowledge management system (KMS), dubbed Tethys after the mythical Greek goddess of the seas, is being developed for the U.S. Department of Energy (DOE) Office of Energy Efficiency and Renewable Energy Wind and Hydropower Technologies Program (WHTP) by Pacific Northwest National Laboratory (PNNL). This requirements specification establishes the essential capabilities required of Tethys and clarifies for WHTP and the Tethys development team the results that must be achieved by the system.

54 ENVIRONMENTAL SCIENCES↗

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.↗

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↗

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.↗

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.↗

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.↗

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.↗

Lands with Wilderness Characteristics, Resource Management Plan Constraints, and Land Exchanges: Cross-Jurisdictional Management and Impacts on Unconventional Fuel Development in Utah's Uinta Basin

Utah is rich in oil shale and oil sands resources. Chief among the challenges facing prospective unconventional fuel developers is the ability to access these resources. Access is heavily dependent upon land ownership and applicable management requirements. Understanding constraints on resource access and the prospect of consolidating resource holdings across a fragmented management landscape is critical to understanding the role Utah’s unconventional fuel resources may play in our nation’s energy policy. This Topical Report explains the historic roots of the “crazy quilt” of western land ownership, how current controversies over management of federal public land with wilderness character could impact access to unconventional fuels resources, and how land exchanges could improve management efficiency. Upon admission to the Union, the State of Utah received the right to title to more than one-ninth of all land within the newly formed state. This land is held in trust to support public schools and institutions, and is managed to generate revenue for trust beneficiaries. State trust lands are scattered across the state in mostly discontinuous 640-acre parcels, many of which are surrounded by federal land and too small to develop on their own. Where state trust lands are developable but surrounded by federal land, federal land management objectives can complicate state trust land development. The difficulty generating revenue from state trust lands can frustrate state and local government officials as well as citizens advocating for economic development. Likewise, the prospect of industrial development of inholdings within prized conservation landscapes creates management challenges for federal agencies. One major tension involves whether certain federal public lands possess wilderness character, and if so, whether management of those lands should emphasize wilderness values over other uses. On December 22, 2010, Secretary of the Interior Ken Salazar issued Secretarial Order 3310, Protecting Wilderness Characteristics on Lands Managed by the Bureau of Land Management. Supporters argue that the Order merely provides guidance regarding implementation of existing legal obligations without creating new rights or duties. Opponents describe Order 3310 as subverting congressional authority to designate Wilderness Areas and as closing millions of acres of public lands to energy development and commodity production. While opponents succeeded in temporarily defunding the Order’s implementation and forcing the Bureau of Land Management (BLM) to adopt a more collaborative approach, the fundamental questions remain: Which federal public lands possess wilderness characteristics and how should those lands be managed? The closely related question is: How might management of such resources impact unconventional fuel development within Utah? These questions remain pressing independent of the Order because the BLM, which manages the majority of federal land in Utah, is statutorily obligated to maintain an up-to-date inventory of federal public lands and the resources they contain, including lands with wilderness characteristics. The BLM is also legally obligated to develop and periodically update land use plans, relying on information obtained in its public lands inventory. The BLM cannot sidestep these hard choices, and failure to consider wilderness characteristics during the planning process will derail the planning effort. Based on an analysis of the most recent inventory data, lands with wilderness characteristics — whether already subject to mandatory protection under the Wilderness Act, subject to discretionary protections as part of BLM Resource Management Plan revisions, or potentially subject to new protections under Order 3310 — are unlikely to profoundly impact oil shale development within Utah’s Uinta Basin. Lands with wilderness characteristics are likely to v have a greater impact on oil sands resources, particularly those resources found in the southern part of the state. Management requirements independent of lands with wilderness characteristics far overshadow the challenges posed by wilderness issues. Wilderness character issues aside, a need to improve management integration remains. In researching past efforts to manage across the fragmented landscape we found that unilateral actions have been deeply divisive and engendered distrust among those impacted by the action. This distrust can linger for decades. Collaborative efforts, whether intended to protect lands, foster development, or do both, can represent an attractive alternative to unilateral action. Such collaborative efforts are more likely to succeed when they respond to strong incentives to act, evidence widespread involvement and support, and benefit from a committed champion. Projects are all but certain to fail where participants overreach or one of these elements is missing. For more than three decades, the state and federal government have cooperatively pursued land exchanges in order to “block up” isolated state trust lands and eliminate inholdings. These efforts can advance both conservation and development objectives, and are generally conducted in conjunction with efforts to protect extraordinary federal lands. Congress recognized the value of such exchanges and, as part of the Energy Policy Act of 2005, directed the Department of the Interior to pursue land exchanges as a means of facilitating environmentally responsible oil shale and oil sands recovery. But land exchanges are not without their challenges. Federal law requires equalizing the value of the lands and resources to be exchanged, and various means of equalizing value have been attempted. More flexible approaches have a higher likelihood of success, but are often criticized as resulting in an economic windfall for one party. Today challenges associated with appraisal and valuation stand as the most significant obstacles in the way of large-scale exchanges. Greater reliance on revenue sharing provisions that prevent an economic windfall to one party and avoid challenges inherent in valuing oil shale and oil sands resources may mark a promising path forward. The success or failure of these efforts could profoundly impact both the prospect of unconventional fuel development and wilderness character protection.

04 OIL SHALES AND TAR SANDS↗

Nuclear analysis generic requirements for fusion applications of radiation shielding - 25639

Radiation shielding engineering and associated nuclear analysis plays an important role in design, operation, maintenance and decommissioning of nuclear fusion devices. Requirements adopted in current analyses are investigated versus basic principles of requirement management and verification and validation aspects. An assessment is proposed to derive applicable product and process requirements from safety principles and transversal function requirements. V and V aspects are extended to cover input and output data. It is concluded that beyond the progress on computational capabilities and technical quality of fusion neutronics shielding analysis, there is the need to develop the underlying procedures and requirement management to satisfy configuration management, quality assurance and safety demonstration needs. (authors)

61 RADIATION PROTECTION AND DOSIMETRY↗

Water Management Successes at the DoE's Environmental Management Waste Management Facility - 19194

URS-CH2M Oak Ridge LLC (UCOR) manages the cleanup of the 2,200-acre East Tennessee Technology Park (ETTP) for its client, the U.S. Department of Energy (DOE), in Oak Ridge, Tennessee. The ETTP site was contaminated with radioactive, hazardous and industrial wastes generated by more than 40 years of national defense and energy missions. Stormwater management is a critical activity at the DoE's Oak Ridge Reservation Environmental Management Waste Management Facility (EMWMF) due to the high average rainfall and the consequences if inadequately managed. EMWMF is located in East Tennessee with an average rainfall of 54.25 inches/year. EMWMF has implemented a successful, multipart strategy to maximize the margin of safety, reduce the volume of stormwater requiring management, and otherwise minimize operational impacts from large volumes of landfill water. The strategy consists of: - Pre-planning and preparation; - Landfill storm water prevention; - Inventory minimization; - Accelerated storm water removal. Since implementation of this aggressive water management strategy in 2017, EMWMF has reduced the volume of leachate requiring management by approximately 27%. This reduction increased the safety and compliance for the EMWMF, while at the same time, reduced costs. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

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↗

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↗

Systematic Literature Review: How is Model-Based Systems Engineering Justified?

The genesis for this systematic literature review was to search for industry case studies that could inform a decision of whether or not to support the change process, investment, training, and tools needed to implement an MBSE approach across the engineering enterprise. The question asked was, how the change from a document - based systems engineering approach (DBSE) to a model-based systems engineering approach (MBSE) is justified? The methodology employed for this systematic literature review was to conduct a document search of electronically published case studies by authors from the defense, space, and complex systems product engineering industries. The 67 case studies without metrics mainly attributed success to completeness, consistency, and communication of requirements. The 21 case studies with metrics on cost and schedule primarily attributed success to the ability of an MBSE approach to improve defect prevention strategies. The primary conclusion is that there is a significant advantage to project performance by applying an MBSE approach. An MBSE approach made the engineering processes on a complex system development effort more efficient by improving requirements completeness, consistency, and communication. These were seen in engineering processes involved in requirements management, concept exploration, design reuse, test and qualification, Verification and Validation, and margins analyses. An MBSE approach was most effective at improving defect prevention strategies. The approach was found to enhance the capability to find defects early in the system development life cycle (SDLC), when they could be fixed with less impact and prevented rework in later phases, thus mitigating risks to cost, schedule, and mission. However, if a program only employed an MBSE approach for requirements management, advantages from finding defects early could not be leveraged in later phases, where the savings in cost and schedule from rework prevention is realized. Significant performance success was achieved when the systems engineer (SE) held a leadership role over engineering process es. A number of the case studies addressed a general lack of skilled MBSE engineers as a major hindrance to implementing an MBSE approach successfully.

42 ENGINEERING↗

National Rotor Testbed Requirements. Draft

This document serves both as a guide and a record for requirements management associated with design of retrofit rotors for the Sandia SWiFT turbines. The rotors will support a long-term experimental campaign. Data gathered during the campaign will support formal verification and validation of complex flow numerical models for prediction of metrics deemed important for wind energy plant efficiency. These integrated projects involve multiple years of effort, dozens of engineers and collaborators, and dozens of stakeholders in the form of the research community, National Lab staff, and DOE staff. Creating of formal, written requirements will ensure flow-down of activities from high-level goals, aid communication, and enable clear verification of activities. A custom requirements schema is created and described. Commercial requirements management software —IBM Rational DOORS—is used to organize the information and ensure traceability. This document serves as a record of the process as well as a record of the exported, detailed contents of the DOORS database.

17 WIND ENERGY↗