Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Model-based”

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 1,171 records · Page 65
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

State Machine Modeling of the Space Launch System Solid Rocket Boosters

The Space Launch System is a Shuttle-derived heavy-lift vehicle currently in development to serve as NASA's premiere launch vehicle for space exploration. The Space Launch System is a multistage rocket with two Solid Rocket Boosters and multiple payloads, including the Multi-Purpose Crew Vehicle. Planned Space Launch System destinations include near-Earth asteroids, the Moon, Mars, and Lagrange points. The Space Launch System is a complex system with many subsystems, requiring considerable systems engineering and integration. To this end, state machine analysis offers a method to support engineering and operational e orts, identify and avert undesirable or potentially hazardous system states, and evaluate system requirements. Finite State Machines model a system as a finite number of states, with transitions between states controlled by state-based and event-based logic. State machines are a useful tool for understanding complex system behaviors and evaluating "what-if" scenarios. This work contributes to a state machine model of the Space Launch System developed at NASA Ames Research Center. The Space Launch System Solid Rocket Booster avionics and ignition subsystems are modeled using MATLAB/Stateflow software. This model is integrated into a larger model of Space Launch System avionics used for verification and validation of Space Launch System operating procedures and design requirements. This includes testing both nominal and o -nominal system states and command sequences.

model-based systems engineering↗
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 NTRS2018

NASA Electronic Parts and Packaging (NEPP) Program: Resources for SmallSats on EEE Parts

From the outside looking in, the NEPP program supports NASA's traditional approach to providing electrical, electronic, and electromechanical (EEE) assurance for space missions. Standards (military and commercial) for EEE parts are based on risk averse methodologies, drive higher costs and schedules, and, in general, provide devices that significantly lag behind commercial devices in performance aspects (speed, power efficiency, etc...). This is NOT the model most small missions realistically can use. However, when you look behind the curtain, NEPP has been considering the risk trade space for small missions for over five years and has consistently provided resources that the small mission regime would find useful. In this paper, we provide a brief overview of these resources as well as NEPP's current research/development efforts that are relevant. While we'll primarily discuss radiation assurance related issues such as data availability and usage, assurances processes for not only the radiation effects side, but also the EEE parts reliability will be touched upon.

Electrical↗
NASA NTRS2014

LADEE Multi-Domain Simulation

The Lunar Atmosphere Dust Environment Explorer (LADEE) was a small explorer class spacecraft that was launched on Sept 7, 2013 and that was de-orbited and successfully impacted the Moons surface on April 17, 2014 after completing all of the mission objectives. The low-cost rapidly prototyped hardware design used for the spacecraft was extend to the development of the software base. To achieve this goal, a Model Based Design approach was utilized to develop the onboard flight software, and out of this development a model based multipurpose simulator was created of the LADEE spacecraft and its mission environment. This simulator extended the traditional function of propagating the vehicle's kinematic and rotational states and included the electrical and thermal states propagation. Traditionally, these domains are handled by domain specific high fidelity simulations that use the states histories from other domains as input. By reducing the fidelity and abstracting the relevant features being monitored and controlled by the flight software, it was possible to model the coupling across these domains resulting in more accurate overall system behavior. A faster than real-time workstation (WSIM) version of the LADEE simulator was used to develop and test the software control algorithms in the Simulink environment. To maximize the performance of the simulation, modeling knobs were introduced to reduce the resolution of the some of the domains models when the effects of that domain were not significant for the scope of that simulation. The automatic code generation feature in Simulink was used to port the simulation to several real-time environments to support Processor-in-the-Loop (PIL) and Hardware-in-the-Loop (HIL) testing, verification and validation. The real-time environment required that the design of each of the domain models be deterministic as possible in the time required to perform all of the calculations to update its states. The simulation interface was designed to be compatible with the command interface employed by the LADEE mission operation team. The WSIM, PIL, and HIL simulators thus used a common interface and thus were used for flight software testing, for mission operations personnel training (nominal and off-nominal operations) prior to the mission and to perform command sequence verification during the mission. This presentation will look at the modeling strategies used to create a common interface to the simulator and to model and couple multiple domains within the simulation, the results of those strategies, and the lessons learned.

Multi-Domain↗
NASA NTRS2022

A Systems Model for System-Wide Safety Safety Demonstrator (SD-1): Wildfire Response Operations

The aim of this internship-based project was to contribute to the ongoing development of a systems model for System-Wide Safety’s first Technical Challenge 5 (TC5) series Safety Demonstrator (SD-1), which will be a demonstration of an In-Time Aviation Safety Management System (IASMS) in emerging wildfire response operations. Using Models-Based Systems Engineering (MBSE) principles to develop the model, I organized and traced previously collected stakeholder needs from the Spring 2022 NASA System-Wide Safety Wildland Firefighting Operations Virtual Workshop (https://nari.arc.nasa.gov/sws-wildfire) to system elements, creating connections which can be used in the future by the project engineers to identify and address requirements gaps throughout the system design process. I also identified and modeled preliminary use case scenarios for aerial assets in the demonstrator and, building on previously produced preliminary high-level models of the 8 SD-1 Services, Functions, and Capabilities (SFCs) and their IASMS data flows, worked to model the Real-Time Risk Assessment (RTRA) tool as an implementation of Risk Assessment and Management that can take in multiple sets of data monitored by SFCs. Project deliverables include stakeholder requirements tables and matrices and systems model diagrams produced with MagicDraw software in the SysML Systems Modeling Language, with eventual plans to connect model diagrams to a Department of Defense Operational Viewpoint (OV-1) graphic, a high-level operational concept graphic that will be used to visualize the SD-1 scenarioin a future phase. The system model serves to provide a common understanding of the scope of and activities necessary for the completion of SD-1,and traces how stakeholder needs are to be addressed.

model-based systems engineering↗
NASA NTRSDate not supplied

From the Knowledge-based Digital Platform (KbDP) Concept for Advanced Air Mobility Research to a Preliminary Prototype

Advanced Air Mobility (AAM) encompasses a range of innovative operational and technological changes to aviation (electric aircraft, increasingly automated aircraft, increasingly automated airspace operations, etc.) that are transforming aviation’s role in everyday movement of people and goods. There are multiple associated concepts and use cases for AAM, all interrelated, including small Unmanned Aircraft System (UAS) Traffic Management (UTM), Upper-Class E Traffic Management (ETM), Extensible Traffic Management (xTM), Regional Air Mobility (RAM), and Urban Air Mobility (UAM). These AAM operations must integrate with traditional Air Traffic Management (ATM) operations, as well as non-aviation modes of transportation and logistics. National Aeronautics and Space Administration (NASA) is spearheading an innovative digital engineering approach to integrate, communicate, and facilitate the research of multi-modal transportation systems. The Knowledge-based Digital Platform (KbDP) is a concept being developed that ties the workflows of Project Managers (PM), Principal Investigators (PI), and System Engineers together across organizational boundaries. It does so through the management of an information database defined by mathematical, data science, and system engineering principles. Machine Learning (ML) algorithms play a key role in this concept by extracting meaningful knowledge from the information database, which the human user leverages to greatly improve the efficiency and effectiveness of their research. Expected benefits of this concept include improved technology transfers from research to production, improved research portfolio investments, and research outcomes that are more integrated with all aspects of the multi-modal transportation problem. The preliminary KbDP prototype has been realized using UAM as a pathfinder use case and developed by a team of system engineer, software developer, data scientist, and interns.

Systems Engineering↗
NASA NTRSDate not supplied

Overview of the Subscale RAVEN Flight Controls and Modeling Testbed

The Research Aircraft for eVTOL Enabling TechNologies (RAVEN) Subscale Wind-Tunnel and Flight Test (SWFT) model is a subscale aircraft built for flight dynamics and controls research demonstrated in wind-tunnel and flight-test experiments. The intent of this paper is to provide a summary of past, current, and future efforts being pursued by the RAVEN-SWFT project. Initially, vehicle development guidelines were crafted by a multidisciplinary team to ensure that the RAVEN-SWFT vehicle was well suited for research in multiple areas, including aero-propulsive modeling, flight controls, and autonomy, among others. The vehicle has been used to obtain extensive wind-tunnel data, enabling aero-propulsive model development across the transition flight envelope and validation of computational tools. The vehicle will be used to conduct flight testing in order to evaluate modeling strategies and flight control logic. The RAVEN-SWFT model also serves as a risk reduction activity for a conceptual, full-scale vehicle in the 1000-lb class. The next steps in the project are to successfully demonstrate free flight in hover, transition, forward flight, and the reverse thereof, utilizing custom control laws integrated onto the RAVEN-SWFT avionics hardware. The project intends to publicize all of the geometry, data, and methods in future reports.

eVTOL↗
NASA NTRSDate not supplied

Modeling NASA’s Procedural Requirement Processes - Implications for Digital Future

The National Aeronautics and Space Administration (NASA) has an ongoing Digital Transformation effort and to leverage and showcase the power of Digital Transformation, an effort is underway to develop an integrated, datacentric, model representing NASA’s key process requirements. The task was divided into three phases: As Is modeling, Analysis, and To Be Planning. As part of this effort, a team has completed the first Phase I of the modeling task and is nearing completion of the second phase. This effort will capture the key elements as requirements, responsibilities, allocations, roles, products, and associated lifecycle elements. The scope of modeling included NASA’s NPR 7120.5 (Project and Program Management), NPR 7123.1 (Systems Engineering) and NPRs 8705.2 (Risk classification for Robotic Missions) and 8705.4 (Human-Rating Requirements for Space Missions). This paper will summarize the approach, scope, parsing patterns applied, metamodel, and associated workflows for the As-Is modeling. It will also summarize the results and insights gleaned during that phase, including the review process. These insights have informed the analysis and will be discussed. The analysis modeling phase will also be summarized including how the stakeholders were engaged, how the common elements were handled and dispositioned, and will also describe some of the plans for the future of NASA NPDs and NPRs.

Systems Engineering↗
NASA NTRSDate not supplied

Defining A Modelling Language to Support Functional Hazard Assessment

Functional Hazard Assessment (FHA) is a key early-stage engineering process that supports the incorporation of safety in design by identifying the high-level functional hazards the system may encounter. While many FHA-like methodologies have been proposed in the design engineering literature, many of these methodologies have had difficulty becoming accepted industry practice. Industry standards, on the other hand, either provide too little recommendation on how to represent the function of the system to perform FHA, or rely on existing design artefacts which insufficiently support the goals of the process. This paper presents some of the problems with current modeling languages (both proposed and used) for FHA which limit the scope, expressiveness, flexibility, and precision of the analysis. It then outlines desirable principles an FHA-supporting analysis language should embody, and introduces the Functional Reasoning Design Language (FRDL), a formal modeling language for describing the functional elements of a system and their interactions, which aims to satisfy these principles. To demonstrate the use of this language, the modeling and hazard analysis of a disaster response drone is presented. While this case study is limited in scope, it highlights how FRDL can represent system function while reducing the ambiguity present in typical FHA-supporting functional modeling languages

Hazard Assessment↗
NASA NTRSDate not supplied

Modeling NASA’s Procedural Requirement Processes – Implications for a Digital Future

The National Aeronautics and Space Administration (NASA) has an ongoing Digital Transformation effort and to leverage and showcase the power of Digital Transformation, an effort is underway to develop an integrated, datacentric, model representing NASA’s key process requirements. The task was divided into three phases: As Is modeling, Analysis, and To Be Planning. As part of this effort, a team has completed the first Phase I of the modeling task and is nearing completion of the second phase. This effort will capture the key elements as requirements, responsibilities, allocations, roles, products, and associated lifecycle elements. The scope of modeling included NASA’s NPR 7120.5 (Project and Program Management), NPR 7123.1 (Systems Engineering) and NPRs 8705.2 (Risk classification for Robotic Missions) and 8705.4 (Human-Rating Requirements for Space Missions).

NPR↗
DOE OSTI2025

Digital Safety Analysis for Small Modular Nuclear Reactors (SMRs)

A Documented Safety Analysis (DSA) is a Department of Energy (DOE) construct that defines the extent to which a nuclear facility can be operated safely. It includes a description of hazards, safe boundaries, and hazard controls. The authors assert that a Digital Safety Analysis (DgSA) is far superior to a legacy DSA for several reasons: • The underling database is structured such that it is possible to perform a comprehensive design review and safety analysis by iterating systematically across a hierarchy of linked objects versus a redundant and spotty review by entities of various abilities under unknown resource and schedule constraints. • The analysis of a new design can discover elements that are similar to elements in previous designs. The discovery of similarities is made possible by using the same structure for the underlying database for each new DgSA. The “prior learning” from previous designs is then applied automatically to new designs. • Outputs from the DgSA are from a single source to ensure consistency among various views of the same information. After the DgSA is released, the continued use of a single source implements a configuration management program to ensure consistency between the design basis, the design, the built system, and system procedures. • The development of the DgSA is agile in that any change in a linked object triggers an analysis of impacts on other linked objects and updates of linked objects are made accordingly. After the DgSA is released, the continued maintenance of these links and objects automates the “unreviewed safety question” process.

22 - GENERAL STUDIES OF NUCLEAR REACTORS↗
DOE OSTI2025

Digital Safety Analysis for Small Modular Nuclear Reactors (SMRs)

The licensing process for any nuclear installation generally requires the review and approval of numerous documents by a regulatory body. Alternate approaches are needed where similar nuclear installations are planned to be built and operated at multiple sites around the world. Such is the case for the deployment of small modular nuclear reactors (SMRs) under development by multiple enterprises in multiple countries. As a use case for this paper, the authors propose an alternative to the Documented Safety Analysis (DSA) required by the United States Department of Energy (DOE) for the licensing of its nuclear installations. The DSA is a DOE construct that requires the review and approval of numerous documents. It includes an in-depth description of hazards, safe boundaries, and hazard controls.

Microreactors↗
DOE OSTI2025

Artificial Intelligence and Digital Engineering as Enablers for System 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↗