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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
DOE OSTI2025

Artificial Intelligence and Digital Engineering as Enablers for Systems Engineering in the Energy Sector

Systems engineering is of utmost importance for the success of high-cost, high-complexity megaprojects, which are common in the energy sector. However, the traditional document-centric systems engineering approach tends to be labor-intensive and time-consuming, which has inhibited its full adoption despite proven metrics on its return on investment. However, with the modern approach of digital engineering and technological advancements in artificial intelligence (AI) technologies, the barriers to systems engineering adoption can finally be broken. This paper goes through the systems engineering V-model for lifecycle management and assesses the current state of implementation of digital engineering (especially, mod-el-based systems engineering, digital twins, and digital threads) and AI for each step. It was observed that a combination of digital engineering and AI is being used across different industries to accelerate and optimize systems engineering processes such as concept development, requirements management, architecture definition, system development, verification and validation, operations, and maintenance. Specifically in the energy sector, AI-augmented digital engineering has shown initial potential in accelerated development and deployment, performance optimization, anomaly detection, predictive maintenance, and configuration management. However, challenges remain in integrating DE and AI into an end-to-end system lifecycle management ecosystem safely and reliably. Addressing these challenges and continuously developing impactful tools will enable fast, efficient, and high-frequency deployment of power generation capabilities to keep up with the world?s energy demands and build energy security.

42 - ENGINEERING↗
NASA NTRSDate not supplied

Using Systems Engineering to Develop an Integrated Crew Health and Performance System to Mitigate Risk for Human Exploration Missions

New space exploration missions are currently being designed to take humanity beyond low Earth orbit (LEO) to cis-lunar space, the lunar surface, and eventually to Mars. These missions carry increased risks due to a number of factors, including distance from Earth, exposure to deep space hazards, reduced capacity and ability to resupply and evacuate, and increased communication delays. As distance from Earth grows and mission length increases, a growing proportion of mission risk can be attributed to the “human system.” Almost twenty years ago, the Institute of Medicine in the United States recommended the early and complete integration of the human system into the spacecraft and mission design process to mitigate this increased risk inherent in exploration missions. Exploration missions will require increasing levels of crew self-sufficiency that will challenge the current operational paradigms established in LEO. Enabling progressive Earth independence requires management of the increasingly complex interactions among spacecraft systems and integration of all the data and functions that affect human health and performance into one coordinated system –the Crew Health and Performance (CHP) system. This system is a critical spacecraft system that is analogous to other systems such as propulsion, guidance and navigation, or avionics. Design and integration of the CHP system requires the evidence-based merger of typically disparate disciplines such as medicine, human factors, and life support system design, using systems engineering (SE) practices. SE provides traceability of spacecraft requirements and enables reliable and repeatable trade space analysis of the many competing options for hardware and software to be included in the mission architecture. The approach described here enables spacecraft and mission designers to align the scope of a CHP system with mission specific requirements, decrease risk to the crew, and increase the probability of mission success.

Kerry McGuire↗
NASA NTRS1976

Computer-aided design and computer science technology

A description is presented of computer-aided design requirements and the resulting computer science advances needed to support aerospace design. The aerospace design environment is examined, taking into account problems of data handling and aspects of computer hardware and software. The interactive terminal is normally the primary interface between the computer system and the engineering designer. Attention is given to user aids, interactive design, interactive computations, the characteristics of design information, data management requirements, hardware advancements, and computer science developments.

Fulton, R. E.↗
NASA NTRS2001

The Acquisition Process as a Vehicle for Enabling Knowledge Management in the Lifecycle of Complex Federal Systems

This white paper explores how to increase the success and operation of critical, complex, national systems by effectively capturing knowledge management requirements within the federal acquisition process. Although we focus on aerospace flight systems, the principles outlined within may have a general applicability to other critical federal systems as well. Fundamental design deficiencies in federal, mission-critical systems have contributed to recent, highly visible system failures, such as the V-22 Osprey and the Delta rocket family. These failures indicate that the current mechanisms for knowledge management and risk management are inadequate to meet the challenges imposed by the rising complexity of critical systems. Failures of aerospace system operations and vehicles may have been prevented or lessened through utilization of better knowledge management and information management techniques.

Stewart, Helen↗
NASA NTRS2013

Configuration Management at NASA

NASA programs are characterized by complexity, harsh environments and the fact that we usually have one chance to get it right. Programs last decades and need to accept new hardware and technology as it is developed. We have multiple suppliers and international partners Our challenges are many, our costs are high and our failures are highly visible. CM systems need to be scalable, adaptable to new technology and span the life cycle of the program (30+ years). Multiple Systems, Contractors and Countries added major levels of complexity to the ISS program and CM/DM and Requirements management systems center dot CM Systems need to be designed for long design life center dot Space Station Design started in 1984 center dot Assembly Complete in 2012 center dot Systems were developed on a task basis without an overall system perspective center dot Technology moves faster than a large project office, try to make sure you have a system that can adapt

Doreswamy, Rajiv↗
NASA NTRS2015

The Use of UML for Software Requirements Expression and Management

It is common practice to write English-language "shall" statements to embody detailed software requirements in aerospace software applications. This paper explores the use of the UML language as a replacement for the English language for this purpose. Among the advantages offered by the Unified Modeling Language (UML) is a high degree of clarity and precision in the expression of domain concepts as well as architecture and design. Can this quality of UML be exploited for the definition of software requirements? While expressing logical behavior, interface characteristics, timeliness constraints, and other constraints on software using UML is commonly done and relatively straight-forward, achieving the additional aspects of the expression and management of software requirements that stakeholders expect, especially traceability, is far less so. These other characteristics, concerned with auditing and quality control, include the ability to trace a requirement to a parent requirement (which may well be an English "shall" statement), to trace a requirement to verification activities or scenarios which verify that requirement, and to trace a requirement to elements of the software design which implement that requirement. UML Use Cases, designed for capturing requirements, have not always been satisfactory. Some applications of them simply use the Use Case model element as a repository for English requirement statements. Other applications of Use Cases, in which Use Cases are incorporated into behavioral diagrams that successfully communicate the behaviors and constraints required of the software, do indeed take advantage of UML's clarity, but not in ways that support the traceability features mentioned above. Our approach uses the Stereotype construct of UML to precisely identify elements of UML constructs, especially behaviors such as State Machines and Activities, as requirements, and also to achieve the necessary mapping capabilities. We describe this approach in the context of a space-based software application currently under development at the Jet Propulsion Laboratory.

model-based engineering↗
NASA NTRS2020

Evolution of the Preliminary Fault Management Architecture and Design for the Psyche Mission

The Psyche Mission presents the first opportunity toexplore the largest metal asteroid in the solar system, (16)Psyche, which is believed to be the exposed core of a largerplanetesimal that was stripped of its rocky mantle throughmultiple collisions during early solar system formation. Themission was selected in January 2017 for a 2022 launch as partof NASA’s Discovery Program and is uniquely enabled by theintegration of a Solar Electric Propulsion (SEP) Chassisdelivered by Maxar Space Solutions with JPL’s core deepspace avionics, flight software, and fault managementarchitectures. One of the key design tasks is the development ofa fault management system capable of being responsive to theunique elements of the combined JPL and Maxar spacecraftarchitecture. This new design leverages the strengths of eachorganization, with Maxar delivering its well-proven highvoltage power bus and low-thrust electric propulsionsubsystem from its GEO communications satellite product line,and JPL delivering its deep space mission expertise and thehardware and software most critical to deep space missiondesign. The development of a robust low-thrust mission andthe integration of design philosophies and hardware from twoorganizations is not without its challenges though.A key challenge in the development of the Psyche faultmanagement architecture and design is in the integration ofdesign philosophies and hardware from JPL and Maxar. Atthe architecture level, Maxar GEO communications satellitesare developed under the premise of highly responsive groundin the loop for the resolution of anomalies, and theimplementation takes a fail-operational approach to minimizedown time for its customers. In contrast, a deep space missionmust be able to maintain safety with long periods of groundcommunication outage. Additionally, with no time-criticalevents after launch, the Psyche spacecraft will generally failsafe in the presence of anomalous conditions; specialconsideration is being given to this approach, however, tominimize the loss of electric propulsion thrust time, which iscritical to low-thrust missions. At the hardware level, thedetailed definition of interfaces between JPL and Maxarhardware presents a unique challenge in the development andflowdown of fault management requirements, the developmentand implementation of fault monitors and responses, and thedevelopment and verification of fault containment boundaries.This paper describes the evolution of the Psyche faultmanagement architecture and design from the concept studyinto the preliminary design phase, with a focus on the uniquechallenges associated with flying GEO communicationssatellite hardware in deep space, implementing a robust lowthrust mission, and the integration of design philosophies andhardware from JPL and Maxar. Details regarding how thesechallenges are addressed in the fault management design inorder to maximize heritage, leverage the strengths of eachorganization, and minimize risk across the design are alsodiscussed.

Marsh, Danielle↗
DOE OSTI2026

Metadata Standards for the NSE: Extended Field Standards

This standard presents a set of optional metadata fields for managed digital objects within the Nuclear Security Enterprise (NSE) and provides a deeper look at data representation in metadata by looking at the representation of 1) Records Management required metadata, and 2) common representations of technical/scientific data. Metadata standardization is a critical enabler for effectively sharing data, documents, and other digital objects between NSE sites, and for tracing the digital thread at the object level. Standardization is necessary for both schemas and vocabularies, meaning that both field standards and value standards must be specified. This document serves as a complementary field standard, recommending an optional set of fields that should be uniformly built for all managed digital objects within the NSE. This document specifically focuses on extending the shared discovery layer defined in the first white paper by introducing additional descriptive and data representation fields that improve cross-site search and interpretation.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗
NASA NTRS1973

Functional requirements for onboard management of space shuttle consumables, volume 1

A study was conducted to determine the functional requirements for onboard management of space shuttle consumables. A generalized consumable management concept was developed for application to advanced spacecraft. The subsystems and related consumables selected for inclusion in the consumables management system are: (1) propulsion, (2) power generation, and (3) environmental and life support.

Graf, P. J.↗
NASA NTRS1974

Life sciences payload definition and integration study. Volume 2: Requirements, design, and planning studies for the carry-on laboratories

The task phase concerned with the requirements, design, and planning studies for the carry-on laboratory (COL) began with a definition of biomedical research areas and candidate research equipment, and then went on to develop conceptual layouts for COL which were each evaluated in order to arrive at a final conceptual design. Each step in this design/evaluation process concerned itself with man/systems integration research and hardware, and life support and protective systems research and equipment selection. COL integration studies were also conducted and include attention to electrical power and data management requirements, operational considerations, and shuttle/Spacelab interface specifications. A COL program schedule was compiled, and a cost analysis was finalized which takes into account work breakdown, annual funding, and cost reduction guidelines.

Source record↗
NASA NTRS2017

Ecological Forecasting Project Management with Examples

Once scientists publish results of their projects and studies, all too often they end up on the shelf and are not otherwise used. The NASA Earth Science Division established its Applied Sciences Program (ASP) to apply research findings to help solve and manage real-world problems and needs. ASP-funded projects generally produce decision support systems for operational applications which are expected to last beyond the end of the NASA funding. Because of NASAs unique perspective of looking down on the Earth from space, ASP studies involve the use of remotely sensed information consisting of satellite data and imagery as well as information from sub-orbital platforms. ASP regularly solicits Earth science proposals that address one or more focus areas; disasters mitigation, ecological forecasting, health and air quality, and water resources. Reporting requirements for ASP-funded projects are different from those typical for research grants from NASA and other granting agencies, requiring management approaches different from other programs. This presentation will address the foregoing in some detail and give examples of three ASP-funded ecological forecasting projects that include: 1) the detection and survey of chimpanzee habitat in Africa from space, 2) harmful algal blooms (HABs) in the California Current System affecting aquaculture facilities and marine mammal populations, and 3) a call for the public to identify North America wildlife in Wisconsin using trail camera photos. Contact information to propose to ASP solicitations for those PIs interested is also provided.

Management↗
NASA NTRS2011

Collaboration Portals for NASA's Airborne Field Campaigns

The University of Alabama in Huntsville (UAH), in collaboration with the Global Hydrology Resource Center, a NASA Earth Science Data Center, has provided information management for a number of NASA Airborne Field campaigns, both hurricane science investigations and satellite instrument validation. Effective field campaign management requires communication and coordination tools, including utilities for personnel to upload and share flight plans, weather forecasts, a variety of mission reports, preliminary science data, and personal photos. Beginning with the Genesis and Rapid Intensification Processes (GRIP) hurricane field campaign in 2010, we have provided these capabilities via a Drupal-based collaboration portal. This portal was reused and modified for the Midlatitude Continental Convective Clouds Experiment (MC3E), part of the Global Precipitation Measurement mission ground validation program. An end goal of these development efforts is the creation of a Drupal profile for field campaign management. This presentation will discuss experiences with Drupal in developing and using these collaboration portals. Topics will include Drupal modules used, advantages and disadvantages of working with Drupal in this context, and how the science teams used the portals in comparison with other communication and collaboration tools.

Conover, Helen↗
DOE OSTI2025

Challenges in Continuous In-Field Critical Current Testing of High-Temperature Superconducting Tapes: Thermal and Mechanical Perspectives

High-temperature superconductors (HTS) are essential for ultra-high-field applications requiring exceptional current-carrying capacity under extreme conditions. However, systematic characterization of critical current in long-length conductors remains challenging due to complex thermal, electromag netic, and mechanical interactions during continuous testing. This study reports the development of a continuous in-field magnetization testing system for position-dependent critical current measurement in HTS tapes at 20 K under 7.5 T fields applied normal to the tape plane, enabling identification of performance-limiting regions that could compromise magnet stability. Here, the system addresses two fundamental challenges inherent to cryogenic reel to-reel testing. First, thermal management requires continuous cooling of a moving conductor to 20 K, achieved through liquid nitrogen precooling combined with a 100 W@20 K Gifford McMahon cryocooler. Second, screening currents in high fields generate Lorentz forces that induce twisting, bowing, and potential delamination. To mitigate these risks, we propose mechanical reinforcement and active current density suppression strategies. Numerical simulations using the stream function formulation reveal four primary failure modes: frictional heating at guide interfaces, unstable equilibria causing deformation, transverse current-induced stresses at guide transitions, and unsupported forces in vertical spans. Our mitigation strategies include PTFE coated guides to minimize friction, spring-loaded stabilization mechanisms to maintain tape alignment, controlled pre-heating using the liquid nitrogen thermal jacket to suppress critical current at stress points, and optimized guide positioning to minimize force accumulation. The experimental system is nearing completion, with testing planned to commence within two months. Preliminary validation at 65 K under 0.5 T demonstrates strong correlation between simulation-predicted mechanical instabilities and observed critical current variations during conductor tran sitions through the measurement region. These findings establish a robust foundation for quality assurance protocols essential to next-generation superconducting magnet applications.

Chen, Siwei [Princeton Plasma Physics Laboratory (↗
NASA NTRS2006

Advancing the practice of systems engineering at JPL

In FY 2004, JPL launched an initiative to improve the way it practices systems engineering. The Lab's senior management formed the Systems Engineering Advancement (SEA) Project in order to "significantly advance the practice and organizational capabilities of systems engineering at JPL on flight projects and ground support tasks." The scope of the SEA Project includes the systems engineering work performed in all three dimensions of a program, project, or task: 1. the full life-cycle, i.e., concept through end of operations 2. the full depth, i.e., Program, Project, System, Subsystem, Element (SE Levels 1 to 5) 3. the full technical scope, e.g., the flight, ground and launch systems, avionics, power, propulsion, telecommunications, thermal, etc. The initial focus of their efforts defined the following basic systems engineering functions at JPL: systems architecture, requirements management, interface definition, technical resource management, system design and analysis, system verification and validation, risk management, technical peer reviews, design process management and systems engineering task management, They also developed a list of highly valued personal behaviors of systems engineers, and are working to inculcate those behaviors into members of their systems engineering community. The SEA Project is developing products, services, and training to support managers and practitioners throughout the entire system lifecycle. As these are developed, each one needs to be systematically deployed. Hence, the SEA Project developed a deployment process that includes four aspects: infrastructure and operations, communication and outreach, education and training, and consulting support. In addition, the SEA Project has taken a proactive approach to organizational change management and customer relationship management - both concepts and approaches not usually invoked in an engineering environment. This paper'3 describes JPL's approach to advancing the practice of systems engineering at the Lab. It describes the general approach used and how they addressed the three key aspects of change: people, process and technology. It highlights a list of highly valued personal behaviors of systems engineers, discusses the various products, services and training that were developed, describes the deployment approach used, and concludes with several lessons learned.

process improvement↗
NASA NTRS2023

Trades, Architecture, and Design of the Joint Augmented Reality Visual Informatics (Joint AR) Product

Future expeditions will enable exploration and study of the planetary surfaces of the Moon and Mars by performing extravehicular activity (EVA) operations. Present-day International Space Station (ISS) EVA operations require an intricate and tight choreography of crew, space suits, tools, systems, and flight teams to plan, train, and execute with limited advanced informatics. Additionally, EVA operations, aside from the Apollo Lunar surface missions, have predominately focused on maintenance and construction tasks where success criteria are clearly measurable. However, future exploration missions expect to enable crew to carry out scientific objectives in increasingly Earth-independent ways. In this paper, the Joint Augmented Reality Visual Informatics System (Joint AR) characterizes the design space for developing a modular augmented reality (AR) device for a spacesuit form factor that can support crew decision-making for EVA. This paper highlights the project’s experience with a product-focused management style and use-case centered systems engineering approach to iteratively design, build, and test. The Joint AR product features were defined via trade studies and market analysis of previous EVA display efforts, various AR components such as optics, commercial AR systems, light engines, data interfaces, graphics engine software and analog test beds. We outline the defining architectural design decisions, including safety criticality considerations, suit mounting interfaces, computer architectures, and partnership contracting mechanisms. The outcomes of these studies, architecture decisions, and management requirements result in a recommended design which is the Joint AR product. We discuss the evolution, development of these system components, and what work remains. We hope to share a unified understanding of various design decisions and how they impact the future of crew members’ access to data during Lunar and Martian EVAs. This ongoing effort can enable a community-wide discovery process toward realizing necessary AR features and capabilities for future missions.

Augmented Reality↗
NASA NTRS1998

Computational Model of Human and System Dynamics in Free Flight: Studies in Distributed Control Technologies

This paper presents a set of studies in full mission simulation and the development of a predictive computational model of human performance in control of complex airspace operations. NASA and the FAA have initiated programs of research and development to provide flight crew, airline operations and air traffic managers with automation aids to increase capacity in en route and terminal area to support the goals of safe, flexible, predictable and efficient operations. In support of these developments, we present a computational model to aid design that includes representation of multiple cognitive agents (both human operators and intelligent aiding systems). The demands of air traffic management require representation of many intelligent agents sharing world-models, coordinating action/intention, and scheduling goals and actions in a potentially unpredictable world of operations. The operator-model structure includes attention functions, action priority, and situation assessment. The cognitive model has been expanded to include working memory operations including retrieval from long-term store, and interference. The operator's activity structures have been developed to provide for anticipation (knowledge of the intention and action of remote operators), and to respond to failures of the system and other operators in the system in situation-specific paradigms. System stability and operator actions can be predicted by using the model. The model's predictive accuracy was verified using the full-mission simulation data of commercial flight deck operations with advanced air traffic management techniques.

Corker, Kevin M.↗
NASA NTRS2011

Reducing NPR 7120.5D to Practice: Transitioning from Design Reviews to the SIR Hardware Review

The Gravity Recovery And Interior Laboratory (GRAIL) mission was the first Jet Propulsion Laboratory (JPL) project initiated under NASA's revised rules for space flight project management, NPR 7120.5D, "NASA Space Flight Program and Project Management Requirements." NASA selected GRAIL through a competitive Announcement of Opportunity process and funded its Phase B Preliminary Design effort. The team's first major milestone was a JPL institutional milestone, the Project Mission System Review (PMSR), which proved an excellent tune-up for the end-of-Phase-B NASA life-cycle review, the Preliminary Design Review (PDR). Building on JPL experience on the Prometheus and Juno projects, the team successfully organized for and conducted these reviews on an aggressive schedule. For the Project Critical Design Review (CDR), lessons learned from the PDR and updated Standing Review Board (SRB) practices from the Agency were factored into the review preparation effort. Additionally, the review was held at the Principal Investigator's institution, the Massachusetts Institute of Technology, rather than at the project management center (JPL), which necessitated additional cross-country coordination steps. The PMSR, PDR, and CDR were design reviews and largely paper-oriented. For the System Integration Review (SIR), the project needed to transition to a hardware review and deal with paper in a very different manner. While many of the practices employed for the design reviews were modified and retained (e.g., review preparation team, gate products management, pre-reviews, SRB coordination), the review agenda, presentation style, and slide templates were significantly changed. A key success factor concerned the handling of project open paper, which was succinctly and effectively communicated to the SRB in presentations.This paper provides a brief overview of the GRAIL mission and its project management challenges, provides a detailed description of project SIR preparation and execution activities, including positive and negative lessons learned and identifies recommendations for future NASA (and non- NASA) project teams.

NPR 7120.5D↗
DOE OSTI2026

Understanding Electric Vehicle Range and Charging Needs: Interactions Between Ambient Temperature, Commute Patterns, and State-of-Charge Usage

Electric vehicle (EV) performance can vary substantially under real-world operating conditions, particularly due to ambient temperature effects on energy consumption, battery behavior, and thermal management requirements. This study quantifies how weather conditions, daily driving patterns, and State-of-Charge (SOC) usage strategies jointly influence EV driving range, charging frequency, and overall energy efficiency. A detailed and experimentally validated Autonomie vehicle model is developed, integrating a powertrain, a mono-zonal cabin model, and a battery electro-thermal model. Three battery sizes (200-, 300-, and 400-mile homologated ranges) are assessed across five commute profiles (20–200 miles) and six ambient temperatures (−18 °C to 50 °C), including scenarios with and without preconditioning. Results show that extreme temperatures could significantly decrease the maximum achievable range by up to 55% in cold conditions (−18 °C) and 40% in hot conditions (50 °C), relative to moderate conditions. Larger battery packs retain a greater fraction of their nominal range under thermal stress, while smaller packs experience sharper relative penalties due to the higher contribution of thermal loads to total energy demand. The analysis further demonstrates that limiting operation to partial SOC windows (e.g., 80–20%), a common real-world practice, significantly reduces achievable range and increases charging frequency, particularly in cold weather. Thermal preconditioning while plugged in is shown to mitigate these effects for short trips, reducing energy consumption by up to 31% in hot conditions and 7% in cold conditions. The findings demonstrate how climate, SOC usage behavior, and thermal management jointly shape the practical driving capability of EVs, highlighting the importance of efficient thermal management and realistic user charging strategies for ensuring reliable EV operation across diverse climatic scenarios.

33 ADVANCED PROPULSION SYSTEMS↗