Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “model based systems engineering (MBSE)”

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 181 records · Page 10

Automated Generation of Fault Management Artifacts from a Simple System Model

Our understanding of off-nominal behavior - failure modes and fault propagation - in complex systems is often based purely on engineering intuition; specific cases are assessed in an ad hoc fashion as a (fallible) fault management engineer sees fit. This work is an attempt to provide a more rigorous approach to this understanding and assessment by automating the creation of a fault management artifact, the Failure Modes and Effects Analysis (FMEA) through querying a representation of the system in a SysML model. This work builds off the previous development of an off-nominal behavior model for the upcoming Soil Moisture Active-Passive (SMAP) mission at the Jet Propulsion Laboratory. We further developed the previous system model to more fully incorporate the ideas of State Analysis, and it was restructured in an organizational hierarchy that models the system as layers of control systems while also incorporating the concept of "design authority". We present software that was developed to traverse the elements and relationships in this model to automatically construct an FMEA spreadsheet. We further discuss extending this model to automatically generate other typical fault management artifacts, such as Fault Trees, to efficiently portray system behavior, and depend less on the intuition of fault management engineers to ensure complete examination of off-nominal behavior.

Spinup and Orient↗

A Model-Based Approach to Engineering Behavior of Complex Aerospace Systems

One of the most challenging yet poorly defined aspects of engineering a complex aerospace system is behavior engineering, including definition, specification, design, implementation, and verification and validation of the system's behaviors. This is especially true for behaviors of highly autonomous and intelligent systems. Behavior engineering is more of an art than a science. As a process it is generally ad-hoc, poorly specified, and inconsistently applied from one project to the next. It uses largely informal representations, and results in system behavior being documented in a wide variety of disparate documents. To address this problem, JPL has undertaken a pilot project to apply its institutional capabilities in Model-Based Systems Engineering to the challenge of specifying complex spacecraft system behavior. This paper describes the results of the work in progress on this project. In particular, we discuss our approach to modeling spacecraft behavior including 1) requirements and design flowdown from system-level to subsystem-level, 2) patterns for behavior decomposition, 3) allocation of behaviors to physical elements in the system, and 4) patterns for capturing V&V activities associated with behavioral requirements. We provide examples of interesting behavior specification patterns, and discuss findings from the pilot project.

SysML↗

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↗

Architectural Modeling and Analysis for Safety Engineering

Model-based development tools are increasingly being used for system-level development of safety-critical systems. Architectural and behavioral models provide important information that can be leveraged to improve the system safety analysis process. Model-based design artifacts produced in early stage development activities can be used to perform system safety analysis, reducing costs and providing accurate results throughout the system life-cycle. In this report we describe an extension to the Architecture Analysis and Design Language (AADL) that supports modeling of system behavior under failure conditions. This Safety Annex enables the independent modeling of component failures and allows safety engineers to weave various types of fault behavior into the nominal system model. The accompanying tool support uses model checking to propagate errors from their source to their effect on safety properties without the need to add separate propagation specifications. The tool also captures all minimal set of fault combinations that can cause violation of the safety properties, that can be compared to qualitative and quantitative objectives as part of the safety assessment process. We describe the Safety Annex, illustrate its use with a representative example, and discuss and demonstrate the tool support enabling an analyst to investigate the system behavior under failure conditions.

FTA↗

NASA’s Secured Airspace for Urban Air Mobility (UAM)

The Urban Air Mobility (UAM) architecture is leveraged from the Unmanned Traffic Management (UTM) concept of operations. Within the UAM environment, UAM operators work collaboratively to manage aerial vehicles in the urban environment. Providers of Services for UAM (PSU), UAM operators, and Supplemental Data Service Providers (SDSP) provide services to support flight operations within that environment. As a recognized need, various views of UAM flight information are provided to the public and public safety entities. To accomplish this, among other goals, the Federal Aviation Administration (FAA) can coordinate flight information between the FAA controlled National Airspace System (NAS) and the UAM environments through the FAA-Industry Data Exchange Protocol (FIDXP). This concept of UAM proposes to develop short-range, point-to-point transportation systems in metropolitan areas using vertical take-off and landing (VTOL) or short take-off and landing (STOL) aircraft to overcome increasing surface congestion. To garner the support of UAM and to realize its potential, an assurance of cybersecurity is critical for public acceptance. Understanding the various components communicating with one-another cybersecurity, like in other industries, has come to the forefront highlighting the need to protect these networks and systems from cyberattacks. With the planned growth and reach of UAM systems, it’s clear that the associated data exchange and service interactions will be at risk due to numerous types of cybersecurity attacks. Consequently, as these threats evolve, the UAM cybersecurity capabilities must adapt to these changes as well. While learning is always the goal, the overall intent of this workshop is to make recommendations on the following: (1) how future UAM environments can be protected against cyber-attacks, and (2) what mechanisms should be put in place to detect attacks against UAM environments.

UAM↗

Gap Analysis of UAS Manuals and Hazards

Emerging aviation includes the use of small Unmanned Aerial Systems (UAS) in novel operations. The manufacture and operation of these small UAS are not as regulated as today’s commercial operation, and their widespread use introduces new risks and hazards to the general public. Today, there are case-by-case approvals for sUAS operations, particularly for emergency response operations in which the potential benefits to use of sUAS is perceived to outweigh potential risks. We analyze operational approvals, procedures, and concepts of operation to identify and categorize the risks and hazards that applicants and approvers are already considering, and also identify barriers and mitigations that the operators have already put in place. This analysis may help lead to routine checklists that standardize safety analysis and lead to more routine operations.

grounded theory↗

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↗

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↗

A Model-Based Framework for NASA Science Mission Formulation

This paper details an effort to implement NASA systems engineering standards and practices using a Digital System Model (DSM), which we also refer to as the system architecture model (SAM). Creating a SAM at the beginning of a design effort helps systems engineer identify errors, inconsistencies, and miscommunications as early as possible. Such issues can then be resolved before it becomes costly and requires significant rework to do so. A pre-formulation SAM also enables advanced trade studies at the earliest stage of concept development. This results in “win-wins” where architecture changes can reduce cost without decreasing effectiveness, or increase effectiveness without increasing cost. SAMs also streamline the creation of project documentation and facilitate superior dialogue between science, engineering, and management stakeholders. Common artifacts such as Master Equipment Lists (MELs), Science Traceability Matrices (STMs), and Mission Traceability Matrices (MTMs), can be automatically maintained through requirements and structural models in the SAM. Key performance parameters (and changes to them) can be tied to simulations in the SAM, allowing far more rapid and extensive trade space exploration. As will be shown in this work, these advantages have been realized for the first time in an actual NASA Goddard Space Flight Center (GSFC) pre-phase A and phase A concept study. Modelbased design tools have been developed in a general, modular manner to maximize reuse on future programs. Focus is placed on structural and requirements architecture modeling. Data is ingested into the SAM from existing discipline model outputs (e.g. MS Excel spreadsheets) and used to update a SysML structural model. A mission requirements model is created within the SAM, containing mission specific as well as standard GSFC mission requirements. With the linked requirements model and structural model, automated compliance checking will be performed as mission parameters evolve without the need for discipline engineers to work directly with the SAM in SysML.

MBSE↗

ENABLING ARCHITECTURE TRADES AND DESIGN EXPLORATION FOR NUCLEAR ELECTRIC PROPULSION

Recent renewed interest in Nuclear Electric Propulsion (NEP) at NASA has driven the need for design space exploration and analysis of alternative architectures to evaluate performance and feasibility of NEP concepts. It has been over a decade since NASA last invested in Nuclear Electric Propulsion development efforts, and the landscape has shifted in both mission objectives and technology readiness levels. This also means that many of the engineering analyses and design frameworks tailored to NEP date back to the Jupiter Icy Moons Orbiter (JIMO) days of the early 2000s. Thus, a need was identified for updating and modernizing the modeling and simulation toolsets for NEP. This paper will detail the development efforts in the Marshall Space Flight Center’s Advanced Concepts Office, with a particular focus on the development of the NEP stage of the NEP-Chem vehicle. The paper will cover the various models used, and their current development status, as well as provide an overview of the integrated vehicle model and plans for further development.

Nuclear↗