aam ecosystem working group mbse approach

AAM ECOSYSTEM WORKING GROUP

MBSE APPROACH

Sami Rodriguez

October 20th, 2020

OUTLINE

• AAM MBSE Model Introduction

• UAM Enterprise Architecture

• AAM Reference Framework

• Model Capabilities & Key Highlights

• Research Test Model

2

AAM MBSE MODEL STRUCTURE

3

UAM

Vehicle Airspace Community

• Initial Prototype built out in MagicDraw

• Model breakdown Identified through current documentation along with Models of Models

Methodology (MoM)

• AAM Model’s based on the Unified Architectural Framework (UAF) and SysML

– Enterprise Model is built using UAF

– System Architecture is built using SysML

Decomposed Concept of Operations into System

of Systems for MBSE Implementation

AAM MBSE MODEL STRUCTURE

• Deliver the NASA CC through the creation of several MBSE Models:

– UAM Enterprise Model:

• Represents the collection of various models

• Collectively represents all the necessary

Requirements, Use Cases, Scenarios,

Standards, Documents needed to

successfully deliver the CC

– FAA Regulatory Model: Model that identifies the applicable

FAA Regulations, Advisory Circulars, Standards, etc.

– Research Test Model: Model that assures AAM safety and accelerate scalability

through modeling of integrated demonstrations of candidate operational concepts

and scenarios

4

OUTLINE






5

ENTERPRISE ARCHITECTURE

• System Breakdown from HL

Architecture to the Vehicle, Airspace,

and Community

• Interfaces from the vehicle to the

airspace exist between the Vehicle,

PSU, and SDSP

• Process repeated with subsystems,

sub-subsystems, etc. until a

satisfactory and sufficient depth has

been achieved

• Develop and mature the Requirements,

Behaviors, etc. for each System Model

6

UAF

SysML

• System Architecture is the strategic organization of the functional elements of the system,

laid out to enable the roles, relationships, dependencies, and interfaces between elements

to be clearly defined and understood

• System Architecture has:

– Structure: logical representations that the details of the overall hierarchy through system

decomposition

– Interfaces: system boundaries that are used for interactions with other systems and elements

– Behaviors: represent the functions that each system or subsystem provides in order to accomplish

the functional requirements associated with it

SYSTEM ARCHITECTURES

7

FAA REGULATIONS MODEL

• Captured relevant FAA regulations as UAF Standard

Element

• Model Structure is based around relevant FARS and

Advisory Circulars

• Each Element has hyperlinks to its online location

• Database for the relevant Regulations

• Similar contract will be used for applicable Standards

8

FAA REGULATIONS MODEL CONT.

• Decomposed

Regulations into

Requirements

• Created Constraint

Blocks that help

perform parametric

analysis to ensure an

Airplane meets the

standard requirements

• In this case, an

Airplane Category

must be verified, and

Aircraft Performance

Levels must be defined

9

OUTLINE






10

• Digital model of the AAM System

• Represents the Enterprise Architecture & aligns with the MoM methodology

• Internal Elements are artifacts that provide the environment to organize and analyze

content that satisfies the CC

• Prototype model for public interaction in 2021

AAM REFERENCE FRAMEWORK

11

OUTLINE






12

IN-MODEL GLOSSARY

13

INTRA METRO AIR SHUTTLE MISSION

14

Characteristic Characteristic Details

Vehicle TypeVTOL aircraft designed for low noise, low operating cost, rapid

turnaround, and passenger comfort and convenience

Number of Passengers

3 to 9

− 3 passengers as minimum size consistent with current

transportation− 9 as breakpoint in Part 135 regulations

Takeoff and Landing

Locations

Only designated takeoff and landing areas

10s of takeoff and landing areas per metro area

Service ProviderPrivate undertaking, local transportation authority, or public-private

partnership

Scheduling Largely scheduled, but also semi-scheduled variations

Locations of FlightInclude ability to fly up to multiple thousand feet AGL (autonomous

aircraft will no longer be limited to flight below 400 ft. AGL)

Trip Distance 10s of miles

Density of Operations100s of vehicles per metro area

10s of vehicles flying simultaneously

Diversity of Vehicle

Types and Procedures

Moderate

~5 different vehicle types

Piloted, semi-autonomous, and remotely piloted operations

ATM Paradigm

Small numbers of federated, qualified ATM service providers

Multiple number of supplementary data service providers

Weather-tolerant operations

Level of AutomationSemi-autonomous or remotely piloted operations

PropulsionElectric, limited endurance (urban)

*source: UAM Passenger-carrying OpsCon v12.2

Intra-Metro Air Shuttle Overview

INTRA METRO AIR SHUTTLE MISSION

15

REQUIREMENT ANALYSIS

16

• Requirements are realized into the model as elements with ID,

Name, and Text (shall statement)

• Use “Satisfy” relationship for a model element to satisfy a

requirement, e.g. vehicle to the Vehicle Operations

requirement

• Model elements referenced within the text, e.g. Metropolitan

Area in the Vehicle Operations requirement, will be connected

to the requirement with a “trace” relationship

COLLABORATION

17

REPORT GENERATION

18

OUTLINE






19

RESEARCH TEST MODEL STRUCTURE

20

• Model Structure is based around AAM Scenarios and MTEs

– National Campaign is our primary use case

• Series Emphasis on Operational Scenarios, and remaining flexible to industry

needs

– NC-DT assesses the readiness of external ranges and partners to collect

comprehensive data in support of NC-1

– NC-1 scenarios will move participants

closer to operations by baselining operational

expectations & identifying gaps in AAM

– NC-2-4, and associated developmental

testing, will progressively mature advanced

UAM vehicle configurations and automation

research

MTES

21

• Mission Task Elements (MTEs) can be considered as fundamental building

blocks to identify the relationship between aircraft performance and flight

characteristics and means of demonstrating compliance, and evaluating the

robustness and operational readiness of vehicle designs

RESEARCH TEST REQUIREMENTS

22

• MTEs and Scenarios need to Satisfy Research Test Requirements

BACKUP

23

ENTERPRISE ARCHITECTING

• Initial Process:

– Start the model by defining the purpose of

the system being created

– Capture the overall Vision of UAM

– Continue by creating the requirements for

the UAM Resource Architecture

• Resource Architecture is a UAF element

used to denote a model of the Architecture,

composed of systems that traces to the

overarching Vision

24

ENTERPRISE ARCHITECTURE

25

• System Breakdown from HL Level

Architecture to the Vehicle, Airspace, and

Community

• Develop and mature the Requirements for

each System found within the UAM

Architecture

• Continue by elaborating on the next tier’s

requirements to define the prime systems to

be created with the interfaces between them

MTES

26

GRAND CHALLENGE SCENARIO

27

AAM NATIONAL CAMPAIGN (NC) SERIES

28

Goal

1. Accelerate Certification and Approval

2. Develop Flight Procedure Guidelines

3. Evaluate the CNS Trade-Space

4. Demonstrate an Airspace Operations

Management (AOM) Architecture

5. Characterize Community Concerns

Objectives

Assure AAM safety and accelerate scalability through integrated demonstrations of

candidate operational concepts and scenarios.

AAM MBSE MODEL INTRODUCTION

• Model Based Systems Engineering (MBSE) is the “utilization of dynamic models to

complete standard systems engineering tasks in order to visually represent system

functionality and hierarchy”

• MBSE can be used for:

– Reusability of system elements

– Improved Communication

– Centralized information database

– Increased ability to manage system complexity

– Scalable to the Problem

• The AAM Project was selected to be a pilot program for MBSE

– Specifically, creating a UAM Enterprise Architecture

• MagicDraw was used to develop the initial Enterprise Architecture

29

WHY IS THE NASA USING MBSE?

30

NASA Goal: To enable the AAM Mission Critical Commitment by capturing, organizing, tracing, analyzing and

validating representative UAM system architectures and requirements

Objectives:

• Develop a centralized information database accessible by the AAM Ecosystem

• Improve ability to manage a very large and highly complex set of system concepts, architectures

& reqmts

• Build a comprehensive representative UAM Enterprise Architecture structure

• Capture the necessary data and requirements that define the UAM System Architecture

• Validate the UAM System Architecture using research and test data

• Identify gaps in existing standards, regulations and policies

• Improve Communications and interoperability across the AAM Ecosystem

• Enable reusability of system elements that can be leveraged by other NASA Projects and

external Stakeholders

• Enable scalable solutions to the problem

Critical Commitment:

Based on validated operational concepts, simulations, analyses, and results from National

Campaign demonstrations, the AAM Mission will deliver aircraft, airspace, and infrastructure

system and architecture requirements to enable sustainable and scalable medium density

advanced air mobility operations