systems engineering transformation industry day

Systems Engineering Transformation

Industry Day 8 March 2018

Southern Maryland Higher Education Center

44219 Airport Road

California, Maryland

Bldg. 2 - Center Hall

NAVAIR Public Release 2018-194. Distribution Statement A – “Approved for public release; distribution is unlimited”

Presented To:

Presented By:

Outpacing the Competition: A Systems Engineering Challenge

8 March 2018

Systems Engineering Transformation Industry Day

VADM Paul Grosklags, Commander, NAVAIR

Distribution Statement A:

Approved for public release; distribution unlimited PR# 2017-928

Life Has Been Good!

3



Competition is Back

4

Framing the Challenge



Sea Lanes Remain the Lifeblood of Our Economy

90% of global trade by volume / 70% of global trade by value 98% of telecoms traffic

6



Changing Environment

7

Sources: Janes / RAND / US-China Commission

Advanced Fighter/ Strike

Aircraft (3rd/4th Generation)

Advanced Attack

Submarines

Short Range

Ballistic Missiles

Advanced ASCM Capable

Surface Combatants (DD/FF)

1999



Advanced Fighter/ Strike

Aircraft (3rd/4th Generation)

Advanced Attack

Submarines

Short Range

Ballistic Missiles

0

30

60

90

120

1999 2001 2003 2005 2007 2009 2011 2013

PRC Military Spending (Official Figures)

Spending in Billions (US)

Aircraft Carrier

Changing Environment

*2014 Budget Increased 12.2%

Sources: Janes / RAND / US-China Commission

1999

2015

Advanced ASCM Capable

Surface Combatants (DD/FF)

8

9 Distribution Statement A:


USN and PLA(N) Capability Fielding Trends

Fielding

Initial Estimate

Observed/Expected

DF-21D Anti-Ship Ballistic Missile

J-15 Carrier Based Strike Fighter

Cooperative Engagement Capability

Hypersonics YJ-12/18 Anti-Ship Cruise Missile

LUYANG III

Anti-Satellite Capability

Type 055 Cruiser

9

Initial Operational

Capability

POM-08

FY-17

Naval Integrated Fire Control -Counter Air

Joint Strike Fighter (F-35)

Standard Missile - 6 High Altitude Anti-Submarine Warfare Weapon

Next Generation Jammer

Air and Missile Defense Radar

CG(X) Maritime Strike

Tomahawk

We’re Slower!

USN Warfighting Advantage has Steadily Eroded



NAVAIR Response

Commander’s Intent – Remains Unchanged

• Increase Speed of New Capabilities to Fleet • Increase Readiness

Strategic Initiatives – Focus on Speed

• Capabilities Based Acquisition – Rapid delivery of integrated capabilities

• Sustainment Vision 2020 – Predictive, integrated sustainment operations

• Digital Business Operations – Integrated business systems “apps” at the desktop

10

Accelerating delivery of fully integrated capabilities which are designed,

developed, and sustained in a Model Based Digital Environment



FOR INTERNAL USE ONLY – DO NOT DISTRIBUTE

Why Are We Here Today?

• REALLY want / need your input

• NAVAIR cannot successfully do this

without all of you(+)

• Success will drive / require a different

relationship between gov’t and industry

– Business “arrangements” will change . . . will

require true partnerships . . .

11

Our biggest challenges will not be technology and tools,

they will be cultural and business related

SE Transformation - “Shaping our Future…”


Integrated Warfare Analysis

establishes CONEMPS

and Effects-Chains

CONEMPS and Effects Chains

are modeled at the System of

Systems (SoS) level

SYSTEM MODEL

Capability Based Acquisition - Outpacing the Threat Digital Thread enables rapid delivery of Integrated Capabilities

Constructive Virtual Live

LVC-based training maximizes Fleet

proficiency

System models form

“Constructive” basis for LVC

M&S environment

Enabling Capabilities-Based T&E

SoS MODEL

Systems are developed in a

Model-Based environment

(SE Transformation) Digital Linkage

13 NAVAIR Public Release 2017-370. Distribution Statement A – “Approved for public release; distribution is unlimited”

Industry-Government Partnership

• SET applies to Government and Industry

– Commercial cycle time is a function of development and

production activities

– DoD cycle times add the activities associated with Government

oversight responsibilities

– Both must be addressed to achieve the necessary reduction

• Government must reassess its role in the acquisition process and the

methods for executing that role

1. Criteria for gov’t involvement/oversight (not every decision)

2. If involved, must be on developer’s timeline

3. Must bring value to the decision – not just positional authority

• Industry must fully leverage advances in HPC-enabled models and

participate in establishing a collaborative, integrated digital

environment which enables continuous interaction


The Elements of SE Transformation


System Specification as a Model

16

A system model is an

interconnected set of model

elements that represent key

system aspects including

structure, behavior,

requirements, and parametrics

In SET, the System Spec

(Performance Spec) would be

instantiated in a model (using

SysML). It will be developed in

a collaborative workspace by a

cross-functional team. The

model will then be placed on the

development contract vice a

paper spec


System Model – As An Integration Framework

17

External

Requirements

System

Document &

Specification

Mechanical

Design

Models

Electrical

Design

Models

Software

Design

Models

Testing

Methods &

Models

System Framework for Design

Viewpoint

Traceability

Rationale Analysis

Needs

Performance

Estimates

System Model The system model is

linked “upstream” to

mission effectiveness

models and

CONEMPS, and

“downstream” to

decomposed and

allocated sub-system

requirements and

associated designs. It

is also linked to

verification tools (FEM,

CFD) which validate it’s

fidelity and utility for

intended purpose

The system model flows down, and is interconnected with the

subsystem requirements and emerging designs. These design are

instantiated in different models based on their governing physics

(stress/strain, fluids, electro-magnetic, etc.)


Human

Readable

Revie

w A

rtif

ac

ts

Single Source of Truth

18

Machine

Readable

An

aly

sis

To

ols

SYSTEM MODEL

• Ability to interrogate the design

information and extract data into

the format necessary for the

given task o Leverages formalism

o Transformation rules are reusable

o Provides machine and human

readable formats

• Leverage the model by reviewing

the model itself

• Stakeholders focus on the views

of the system model that

address their concerns

Single-Source-of-Truth

Repository

(Gov’t/Prime)

Table

View

Diagram

View

Graph

View

XML

View

RDF

View

The entire set of models and

tools is held in a single

repository and becomes the

Single-Source-of-Truth for the

duration of system development


Putting It Together in a New Framework


SET Framework 4 Elements

20

CDD

Inte

gra

ted

Te

st

Ve

hic

le #

1

Design & Manufacture Release

MDAO*/SET-BASED DESIGN

Inte

gra

tion

Eve

nts

* Multi-Disciplinary Analysis & Optimization

• Elimination of paper CDRL artifacts and

large-scale design reviews

• Continuous insight/oversight via digital

collaborative environment and

interaction with the Single Source of

Truth

Mechanical Design Models

Electrical Design Models

Software Design Models

Testing Methods & Models

Analysis Tools

Instantiate and

validate design

in models

Move rapidly to mfg.

Substantiation and

insight via modeling

environment

Re-balance as

required

Single Source of Truth Instantiate

System Spec in

a model

Mission

Effectiveness

optimization

V6.0

Right-size CDD –

very few KPPs, all

tied to mission

effectives

Element 1

Element 2

Element 3

Element 4


How SET Can Reduce Development Cycle Time

1. Right-size CDD

– Narrow top of the requirements pyramid

– Off-load requirements to other elements of SoS and via TTPs (CONOPS)

– KPPs must be tied to mission effectiveness, Ao or Cost

2. Eliminate or reduce SETR events

3. Eliminate/reduce CDRLs

4. MDAO enabled by HPC and multi-physics computational tools

allows rapid optimization and design trades

5. Quality improvement at all levels – reduced rework due to

requirements and design defects

6. Continual use of mission effectiveness modeling in design trade –

reduce technical churn going after 100% compliance when 80% will

satisfy mission

7. Allow asynchronous design and manufacture release decisions –

Gov’t involved real-time via IDE in production release decisions

8. Early T&E focused on model validation – allow models to do heavy

lifting

21 21 NAVAIR Public Release 2017-370. Distribution Statement A – “Approved for public release; distribution is unlimited”

How NAVAIR is Executing SET


SET Framework 5 Functional Areas

23

V11.3

Training Content

Development

Coaching &

Mentoring

Workshops

Training Delivery

KEY AREAS OF

RESEARCH:

• Model Integration

• Model Integrity

• Ontology

• MDAO

• Multi-Physics

Modeling

• Model Visualization

• Roadmap &

Implementation

Contract

Language

Tech Data / Acq.

Artifacts

SET Research

Team Integrated Modeling

Environment Team

Policy, Contract &

Legal Team

Outreach

Acquisition Policy

Initial Training

Workforce &

Culture Team

Model

Visualization

Data, Process,

Knowledge Ref.

Model

Decision

Framework

IT Infrastructure

Modeling

Methodology

Model Repository

SSOT

Modeling Tool-Set

Skill/Performance

Model

Instructions, SWP

& Guides

Source Selection

SE Process Model

“as-is / “to-be”

Process &

Methods Team

V&V Process

IP/Proprietary

Data

Requirements

Policy

System Modeling

(Spec)

Gov’t/Prime

Collaboration

System Model

Technical

Domain

Virtual Reviews Data Standards

Recruiting

Deployment

Strategy &

Planning

Increment

Deployment

SET Enterprise

Deployment

Infusion & Pilots

Surrogate

Experiment

Email: [email protected]

NAVAIR MBSE Community of Practice:

https://community.apan.org/wg/navair-

set/navair-mbse-community-of-practice/

Lessons Learned

& Metrics

Acquisition Sys.

Ref. Model

Gov’t

Collaboration Ctr.

Gov’t/Prime

Collaboration Ctr.

Dev. Modeling

Methodology

CBA Links


Execution Framework

24

Functional Areas

Wo

rkfo

rce &

Cu

lture

Inte

gra

ted

Mo

delin

g

En

viro

nm

en

t

Pro

cesses /

Meth

od

s

Po

licy, C

on

tracts

&

Leg

al

Tech

nic

al R

esearc

h

Each Element requires work in the 5 Functional Areas in order to reach “Full Maturity”

Increment 1

Increment 2

Increment 3


Pilots – MANGL, MCAS, NACES, NGAD Eng

Experiment – Surrogate System

SET Capability

Development

SET “Roll-out” Strategy

SE Transformation Research (by the SERC)

SET Capability

Development

SET Operation & Maintenance (SEDIC/4.1)

Research State-of-the=art

Research

Literature

Pilot – MQ-25A

Pilot – V-22 COD “Virtual” Technical Reviews

Pilots – FVL, Triton Training Device

Research

Collaboration

Increment 1 Increment 2 Increment 3

Lessons

Learned

Lessons

Learned

Lessons

Learned

NAVAIR Enterprise Deployment

Develo

pm

en

t &

Im

ple

me

nta

tio

n

Infu

sio

n &

De

plo

ym

en

t

SET RESEARCH • Model Integration

• Model Integrity

• Implementation Methods

• Roadmap

TOOLS – Licenses,

Sustainment, etc..

• Collaboration Center , IT,

CM, SW Releases, etc..

• Process Documentation -

instruction, SWP, SSP,

Guides

TRAINING • Help Desk

INTEGRATED MODELING

ENVIRONMENT(IME) • Modelling Methodology

• Modelling Tool-set

• Modelling Language

• Model Repository

• Collaboration Center

PILOTS &

DEMONSTRATIONS • Collaborative Environment

• Technical Review

Framework (e.g. MDAO)

• System Model

• Engineering Data in Models

SET Cap.

Dev.

SET Capability

Development

V7.0


Surrogate Pilot focus on Execution of SET Framework

Surrogate Pilot

Integrated Modeling Environment

for real-time Collaboration in

Authoritative Source of Truth


SET Schedule

27

O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S

POAM & Detailed Sch Inc 1

Training Development V1

Codification of Process Codification of Process

SET Research (SERC)

Modeling Methodology Research

Modeling Integration/Integrity Research

Institutionalization Research

Policy, Legal &

Contracts

Contract Language V1 Contract Language V2

SETR/CDRL to Models SETR/CDRL to Models

Process &

Methodology

Incremental Development of Modeling Methodology & Ontology

Collaboration & Tech Review V1 Collaboration & Tech Review V2

Development of Reference, Domain, Product, Analysis and V&V Models

Workforce &

Culture

Training Strategy and Planning Training Development V2

Initial Training Training V1 Training V2 (ongoing)

Dev Modeling CoP Website

SET Website

Communication and Outreach

ToolSets

SSOT Repository V1 SSOT Repository V2 SSOT Repository V3

Collaboration Center V1 Collaboration Center V2

SET Milestones

Modeling &

Collaboration

Environment

IT Infrastructure IT Infrastructure

ToolSet Eval Initial ToolSet

v11.0FY17 FY18 FY19

Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4Q3

FY20

Q1 Q2 Q3 Q4Q1 Q2


28

0800 - 0830 Sign In

0830 - 0840 Welcome, Opening Remarks Mr. Dave Cohen, SES, Director

Systems Engineering Department

0840 - 0900 NAVAIR Leadership Remarks VADM Paul Grosklags, Commander,

Naval Air Systems Command

0900 - 0945 SET Overview Mr. Dave Cohen

0945 - 1000 Agenda & Ground Rules Leslie Thomas, SET Operations

1000 - 1030 Break

SET Functional Area Briefs

1030 - 1100 Workforce & Culture Bob Steinbach

1100 - 1130 Integrated Modeling Environment David Fields

1130 - 1200 Process & Methods Fran Chamberlain / Don Polakovics

1200 - 1330 Lunch

1330 - 1400 Policy, Contracts & Legal Nathaniel Norwood

1400 - 1500 Research & Surrogate Experiment Mark Blackburn

1500 - 1600 Q&A

Systems Engineering Transformation (SET)

Industry Day Agenda


Ground Rules

All attendees must sign-in

Please silence cell phones and pagers

No audio or visual recordings are permitted

This is an Informational Briefing only

Meeting is Unclassified.

As stated in the Feb 15, 2018 FedBizOps, SET RFI & Industry Day update, due to schedule constraints, One-on-One Discussions will no longer be held. Please disregard any information pertaining to One-on-One Discussions within the RFI.

No Verbal Questions Will be Entertained During the Briefing


Questions and Answers

• Submit questions in writing on 3x5 cards provided at the sign-in table and then placing them in the Questions Box. Questions may be submitted during any break.

• After today’s meeting, any follow-on questions should be submitted in writing by e-mail to [email protected]. Please start the subject of the email with "SET Industry Day Follow-On Questions".

• All follow-on questions must be submitted to the Government by March 14, 2018 09:00 EST.

• All questions and Government answers will be posted on the FedBizOpps website (www.fbo.gov).


Disclaimer

NAVAIR has not made a commitment to procure any of the items discussed and release of this RFI should not be construed as a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned. Reminder: Any information provided to the Government as a result of this RFI may be used either directly or indirectly to modify and develop NAVAIR acquisition processes and/or policies.

The information shared today reflects current Government intentions and is subject to change based on a variety of circumstances, including internal and external comments.

31

Workforce and Culture

32

Workforce Trained in

Model Based Collaboration

Developed Cadre of Skilled

Modelers

Full Modeling

Methodology Training

Workforce Trained in

Model based Technical Reviews

SET Deployment

Website

APAN SET Cross

Functional Collaboration

Acquisition Workforce

Understands and Values

MBSE

Program Start-up

Workshops

Skills Performance

Model

MBSE CoP

Frequently Asked

Questions

(FAQs)

Integrated Full

Spectrum SE Training


SET Functional Areas

33

V11.3

Training Content

Development

Coaching &

Mentoring

Workshops

Training Delivery

KEY AREAS OF

RESEARCH:


• Model Integrity

• Ontology

• MDAO

• Multi-Physics

Modeling


• Roadmap &

Implementation

Contract

Language

Tech Data / Acq.

Artifacts

SET Research


Environment Team

Policy, Contract &

Legal Team

Outreach

Acquisition Policy

Initial Training

Workforce &

Culture Team

Model

Visualization

Data, Process,

Knowledge Ref.

Model

Decision

Framework

IT Infrastructure

Modeling

Methodology

Model Repository

SSOT

Modeling Tool-Set

Skill/Performance

Model

Instructions, SWP

& Guides

Source Selection

SE Process Model


Process &

Methods Team

V&V Process

IP/Proprietary

Data

Requirements

Policy

System Modeling

(Spec)

Gov’t/Prime

Collaboration

System Model

Technical

Domain


Recruiting

Deployment

Strategy &

Planning

Increment

Deployment

SET Enterprise

Deployment

Infusion & Pilots

Surrogate

Experiment





Lessons Learned

& Metrics

Acquisition Sys.

Ref. Model

Gov’t

Collaboration Ctr.

Gov’t/Prime

Collaboration Ctr.

Dev. Modeling

Methodology

CBA Links


Workforce and Culture

Training - End State

Cadre Skilled

Modelers

DoD Training

Curriculum Basic SysML

Intermediate SysML

Advanced SysML

Integrated Full

Spectrum SE

Training

Workforce

Transformed to

Value Model

Based Methods

Start up

Workshops Element 1/2

Element 3/4


Workforce & Culture

Training - Increment 1

Training Courses

35

Architecture and Systems Engineering:

Models and Methods to Manage Complex

Systems

• Four Course Professional Certificate Program

• 17 Weeks On-line

• 190 Employees Completed/Enrolled

Essentials for Understanding SysML Models/

Hands-On Essentials for Creating SysML

Models

• One Week On-site (20/class)

• Language & Tool Training

• 83 Employees Trained

Advanced SysML • One Week On-site/ 8 Week Distance Learning

• Advanced Language & Tool Training

• 17 Employees Trained

Online SysML Language Training • 30 – 40 Hour Online Course

• Self Paced/ On-Demand

• In Process of Contracting Effort


Workforce & Culture

Training - Increment 1 cont.

Coaching/Mentoring

36

Dr. Mark Blackburn, Stevens Institute of Technology

Dr. Russell Peak, Georgia Institute of Technology

Dr. Kristin Giammarco, Naval Postgraduate School

Sandy Friedenthal – MBSE Industry Leader /

Independent Consultant / Author

Dr. Donna Rhodes, Massachusetts Institute of Technology


Workforce & Culture

Outreach & Communications

Multi-media

– SET Video – On YouTube

– SET Podcast – Mr. Dave Cohen, SES , Dir., Systems Engineering

Digital Collaboration

– Internal

• SET MyTeam.NAVAIR Collaboration Website

• SET All Partners Access Network (APAN) Collaboration Community

– External

• MBSE Community-of-Practice (CoP) APAN Collaboration Community

• SET Implementation Website (coming soon)

Collaboration/Outreach

– VADM Grosklags - NDIA Keynote, Sea, Air, Space Brief

– OSD, Army, Air Force, ASN, CNO, SYSCOM, and Industry

– Digital Engineering WG (OSD); SERC Research (Army);

– DWO Tasking (CNO); SEWG (SYSCOM)

– SESG SYSCOM Collaboration Event

– Briefs to PEOs, PMAs, Technical Competencies

– Monthly SET Working Sessions


Workforce & Culture

Digital Collaboration

38

Create an account:

apan.org

Search for:

NAVAIR

https://community.apan.org/wg/navair-set/navair-mbse-community-of-practice/



39

Working both

Classified and

Unclassified Environment

Model Transformation

Government Access to Prime Data

Enterprise Tool Suite

(NMCI/Shared Licenses)

CM-Controlled Repository

Government Collaboration

Center

Detailed Methodology

Single Source of

Truth

System Model Data Accessible

IT Infrastructure

for Model Collaboration

& Development

Enterprise Modeling

Guidance & Data

Standards

MDAO



40

V11.3

Training Content

Development

Coaching &

Mentoring

Workshops

Training Delivery

KEY AREAS OF

RESEARCH:


• Model Integrity

• Ontology

• MDAO

• Multi-Physics

Modeling


• Roadmap &

Implementation

Contract

Language

Tech Data / Acq.

Artifacts

SET Research


Environment Team

Policy, Contract &

Legal Team

Outreach

Acquisition Policy

Initial Training

Workforce &

Culture Team

Model

Visualization

Data, Process,

Knowledge Ref.

Model

Decision

Framework

IT Infrastructure

Modeling

Methodology

Model Repository

SSOT

Modeling Tool-Set

Skill/Performance

Model

Instructions, SWP

& Guides

Source Selection

SE Process Model


Process &

Methods Team

V&V Process

IP/Proprietary

Data

Requirements

Policy

System Modeling

(Spec)

Gov’t/Prime

Collaboration

System Model

Technical

Domain


Recruiting

Deployment

Strategy &

Planning

Increment

Deployment

SET Enterprise

Deployment

Infusion & Pilots

Surrogate

Experiment





Lessons Learned

& Metrics

Acquisition Sys.

Ref. Model

Gov’t

Collaboration Ctr.

Gov’t/Prime

Collaboration Ctr.

Dev. Modeling

Methodology

CBA Links


SET Integrated Modeling Environment Overview (IME)

VTL / DOCGEN


Enterprise Business

Process

A modeling capability, not just a tool…

A Combination of Methodology, Language, and Tools…

Knowledge

Management

Capability

Analysis

Design

Methods

Systems

Engineering

MDAO

Reference Models

Process Models

Knowledge Models Model Libraries Enterprise Interfaces

Scripts/Plugins

Reporting Templates

System Model

Mechanical

Design

Models

Electrical

Design

Models

Software

Design

Models

Testing

Methods &

Models

Tools & Infrastructure Skilled People Support

Requirements Elicitation

Requirements Justification

Requirements Analysis

Requirements Traceability

Risk Management

Configuration Management

Acquisition Docs:

System

Specifications

Documentation and

other reports

Ca

pa

bilit

y N

ee

ds


IME MBSE Tool Trade Study

Initial Cut Criteria

38 COTS Tools Evaluated for

•SysML

•DoDAF

•UAF

•Project Access

•Configuration Management

•CAC/PKI Support

•Requirements Management

•Simulation & Parametrics

In-Depth Analysis

Down Selected to 3 Tools

• Cameo System Modeler (NoMagic)

• Rational Rhapsody (IBM)

• Enterprise Architect (Sparx Systems)

Each Tool ‘s Capabilities Evaluated

• Detailed Analysis on Initial Cut Criteria

• Additional Analysis on Import/Export, Support, Cost, etc.

42

Supported

SysML DoDAF UAF Project Access Access Control Project CMServer PKI

Support

Native

Requirements

Editor

DOORS

Integration

Simulatio

n

Cameo Enterprise Architecture Architect 18.X No Magic 32 2 1 2 1 1 2 1 2 2 1

Cameo Enterprise Architecture Enterprise 18.X No Magic 32 2 1 2 1 1 2 1 2 2 1

Cameo Enterprise Architecture Standard 18.X No Magic 32 2 1 2 1 1 2 1 2 2 1

Enterprise Architect Systems Engineering 13.0 Sparx 32 2 1 2 1 1 2 1 2 2 1

Enterprise Architect Ultimate 13.0 Sparx 32 2 1 2 1 1 2 1 2 2 1

Cameo System Modeler Architect 18.X No Magic 32 2 1 2 1 1 2 1 2 2 1

Cameo System Modeler Enterprise 18.X No Magic 32 2 1 2 1 1 2 1 2 2 1

Rhapsody Architect for Software 8.X IBM 16 2 1 2 1 1 2 1 2 1 1

Rhapsody Architect for Systems Engineers 8.X IBM 16 2 1 2 1 1 2 1 2 1 1

Rhapsody Designer for System Engineers 8.X IBM 16 2 1 2 1 1 2 1 2 1 1

Rhapsody Developer 8.X IBM 16 2 1 2 1 1 2 1 2 1 1

Innoslate 3.8 Innsolate 0 2 0 1 1 1 2 1 2 1 1

CORE Spectrum 9 Vitech 0 2 1 0 1 1 2 1 2 1 1

GENESYS 4.1 Vitech 0 2 1 0 1 1 2 1 2 1 1

Integrity Modeler 8.3 PTC 0 2 0 2 1 1 2 1 2 1 1

Enterprise Architect Business & Software

Engineering13.0 Sparx 0 1 1 1 1 1 0 1 2 1 1

Enterprise Architect Corporate 13.0 Sparx 0 1 1 1 1 1 0 1 2 1 1

Magic Draw Architect 18.X No Magic 0 0 1 2 1 1 2 1 0 1 1

Magic Draw Enterprise 18.X No Magic 0 0 1 2 1 1 2 1 0 1 1

Magic Draw Professional 18.X No Magic 0 0 1 2 1 1 2 1 0 1 1

MagicDraw Standard 18.X No Magic 0 0 1 2 1 1 2 1 0 1 1

Modelio SA - SysML 3.6.1 ModelioSoft 0 2 0 0 1 1 2 0 2 1 1

MagicDraw Personal 18.X No Magic 0 0 1 2 0 0 2 1 0 1 1

Enterprise Architect Desktop 13.0 Sparx 0 1 1 0 0 0 0 1 2 1 1

Enterprise Architect Professional 13.0 Sparx 0 1 1 0 0 0 0 1 2 1 1

Visual Paradigm Enterprise 14.1 Visual Paradigm 0 2 0 0 1 1 0 0 2 0 1

Visual Paradigm Professional 14.1 Visual Paradigm 0 2 0 0 1 1 0 0 2 0 1

Atego Modeler 8.1 Atego 0 2 1 0 0 0 0 0 1 1 1

Astah SysML 1.4 Astah 0 2 0 0 0 0 2 0 0 0 1

Papyrus 2.0.2 Eclipse Foundation 0 2 0 0 0 0 1 0 0 1 1

Rational Software Architect 9.5 IBM 0 0 0 0 0 1 2 0 0 1 1

Visual Paradigm Modeler 14.1 Visual Paradigm 0 2 0 0 1 1 0 0 0 0 1

Visual Paradigm Standard 14.1 Visual Paradigm 0 2 0 0 1 1 0 0 0 0 1

Software Ideas Modeler 10 Software Ideas 0 2 0 0 0 0 0 0 0 0 1

SysML Designer 3.0 Obeo Network 0 2 0 0 0 0 0 0 0 0 1

Visual Paradigm Community 14.1 Visual Paradigm 0 2 0 0 0 0 0 0 0 0 1

Cradle 7.3 3SL 0 2 0 2 1 1 2 1 2 1 1

Scade Suite N/A Esterel Technologies 0 2 0 0 0 0 0 0 1 1 1

Initial Criteria

Features

Tool Version Vendor Score

Framework Server Based Respository


IME Legacy Model Transformation

43

NoMagic SysML/UPDM Model

UPIA

UML RSA

Provides NAVAIR programs and projects the

capability to convert legacy UML/UPIA

models into SysML/UPDM models for using

in Cameo System Modeler

Currently available for Unclassified models

(Classified capability in development)



Initial Modeling Environment (Unclassified)

Industry Leading Modeling Tools…

NMCI Software Distribution…

MBSE Tool

Trade Study

Legacy Model Transformation

Government Collaboration Center Plan

Preliminary Modeling Tool Suite

Cameo System Modeler

NMCI Floating Licenses

Acquisition System

Reference Model

Configuration Controlled Repository

44

Virtual Technical Reviews

Teamwork Cloud

Collaborative Integrated Systems Engineering Environment (ISEE)


IME Initial Repository

NoMagic Teamwork

Cloud Server

Single Source of Truth Repository

• Configuration Management

• Branch/Fork/Merge

Multiple Modeler/Stakeholder Access

• Role Based Permissions

• Concurrent Modeling Efforts

Secure and Accessible

• NMCI eDMZ Hosted

• CAC/PKI Authentication

• NMCI Floating License Server

45

Development Environment

• Citrix/NMCI Based

• Using for Process/Method Beta Tests

Production Environment

• NMCI eDMZ Hosted

• Server Builds & IT Approvals in Process


Initial Acquisition System Reference Model

AS

RM

• Initial Reference Models Based on SET Pilots

• Rotary Wing <- currently in alpha stage

• Carrier Based UAV <- start development in the next couple months

• Foundation for Many SET Activities

• Training

• Methodology

• Competency Buy-In

• MBSE Testbed

• Provides Top-to-Bottom view of NAVAIR System Models


Gov’t Collaboration Center Plan

Collaborative Space

Reviews & Development

Computing Environment

Multi Level Security

Tool Access

47

Initial Plan Includes

• Stakeholder Requirements

• Possible existing spaces to use as

prototype

• Early draft cost and schedule


Spec Document from Model

Requirements are Created & Managed in the System Model

Custom Reports allow for Products (Spec, ICD, etc.) to be Generated from Model

Results in PDF, Word, Excel, etc.

Initial Report for MQ-25 Control System

Performance Specification (CSPS)

• Requirements imported from DOORS

• Report pulls out requirements, headers,

images, and front matter

• Working to add additional data not captured

in DOORS (CSCI allocation, traces to

Operational Architecture, etc.)

SET Working on a Requirement

Management Standardize Structure

• Allows all programs/projects to use the

same reports

• Provides easier CM

• Better traceability


Process & Methods

49

Gov’t / Prime Collaboration

Model Methodology

Process Model –

“As-is” / To-be”

System Modeling

(Spec)

Model-Centric Source

Selection

V&V Process

System Model –

Technical Domain

Surrogate

Instructions, SWP, & Guides

Virtual SETRs

Integrated Full

Spectrum SE Training



50

V11.3

Training Content

Development

Coaching &

Mentoring

Workshops

Training Delivery

KEY AREAS OF

RESEARCH:


• Model Integrity

• Ontology

• MDAO

• Multi-Physics

Modeling


• Roadmap &

Implementation

Contract

Language

Tech Data / Acq.

Artifacts

SET Research


Environment Team

Policy, Contract &

Legal Team

Outreach

Acquisition Policy

Initial Training

Workforce &

Culture Team

Model

Visualization

Data, Process,

Knowledge Ref.

Model

Decision

Framework

IT Infrastructure

Modeling

Methodology

Model Repository

SSOT

Modeling Tool-Set

Skill/Performance

Model

Instructions, SWP

& Guides

Source Selection

SE Process Model


Process &

Methods Team

V&V Process

IP/Proprietary

Data

Requirements

Policy

System Modeling

(Spec)

Gov’t/Prime

Collaboration

System Model

Technical

Domain


Recruiting

Deployment

Strategy &

Planning

Increment

Deployment

SET Enterprise

Deployment

Infusion & Pilots

Surrogate

Experiment





Lessons Learned

& Metrics

Acquisition Sys.

Ref. Model

Gov’t

Collaboration Ctr.

Gov’t/Prime

Collaboration Ctr.

Dev. Modeling

Methodology

CBA Links


Process & Methods Overview

• SET Element 1 & 2 (Pre-contract award)

– Establish model-based links between Mission Capability

(MTB/ ICTB /CDD) and System Capability (program of record)

– Develop process for creating an Acquisition System Model

(model-based spec) that can be used in an RFP

– Leverage Object Oriented Systems Engineering Method (OOSEM)

for adoption – OMG Standard

– Connections Between Methods, ASRM, Pilots and Training

– Develop Model-Centric Source Selection and V & V Processes

• SET Element 3 & 4 (Post-contract award)

– Establish Technical Domain processes and methods for applying system engineering

models to reduce system design, development and verification cost, while increasing

system effectiveness.

– Establish process and methods for using systems models and authoritative electronic

data to streamline technical reviews and data reporting (CDRL) requirements.

51

“….formalizing the application of models to support system requirements, design,

analysis, verification and validation activities beginning in the conceptual design

phase and continuing throughout development and later life cycle phases.” INCOSE

SE Vision 2020


Human

Readable

Revie

w A

rtif

ac

ts

Model-Centric Collaboration/Review – End-state

52

Machine

Readable

An

aly

sis

To

ols

SYSTEM MODEL

• Ability to interrogate the design

information and extract data into

the format necessary for the

given task o Leverages formalism

o Transformation rules are reusable

o Provides machine and human

readable formats

• Leverage the model by reviewing

the model itself

• Stakeholders focus on the views

of the system model that

address their concerns

Single-Source-of-Truth

Repository – (IDE - Gov’t/Prime)

Table

View

Diagram

View

Graph

View

XML

View

RDF

View

The entire set of models and

tools is held in a single

repository and becomes the

Single-Source-of-Truth for the

duration of system development


SET Integrated Modeling Environment (IME) Conceptual View – End State

VTL / DOCGEN


Enterprise Business

Process

A modeling capability, not just a tool…

A Combination of Methodology, Language, and Tools…

Knowledge

Management

Capability

Analysis

Design

Methods

Systems

Engineering

MDAO

Reference Models

Process Models

Knowledge Models Model Libraries Enterprise Interfaces

Scripts/Plugins

Reporting Templates

System Model

Mechanical

Design

Models

Electrical

Design

Models

Software

Design

Models

Testing

Methods &

Models

Tools & Infrastructure Skilled People Support

Requirements Elicitation

Requirements Justification


Requirements Traceability

Risk Management

Configuration Management

Acquisition Docs:

System

Specifications

Documentation and

other reports

Ca

pa

bilit

y N

ee

ds


System Model – As An Integration Framework

54

External

Requirements

System

Document &

Specification

Mechanical

Design

Models

Electrical

Design

Models

Software

Design

Models

Testing

Methods &

Models

System Framework for Design

Viewpoint

Traceability

Rationale

Analysis

Needs

Performance

Estimates

System Model The system model is

linked “upstream” to

mission effectiveness

models and

CONEMPS, and

“downstream” to

decomposed and

allocated sub-system

requirements and

associated designs. It

is also linked to

verification tools (FEM,

CFD) which validate it’s

fidelity and utility for

intended purpose

The system model flows down, and is interconnected with the

subsystem requirements and emerging designs. These design are

instantiated in different models based on their governing physics

(stress/strain, fluids, electro-magnetic, etc.)

54

SME Technical

Information


55

Conceptual Design System Model

JCIDS

CDD

DODAF

Mission Analysis

Process and Methods

• AIR-4.0M applies system modeling to

rapidly converge to optimum

conceptual design solution

• AIR-4.1 performs Requirements

Analysis at the System Model

• Technical Competencies generate

portions of System Model or provide

model compatible input

Element 1 - End State Process & Methods


Element 1


56

Process and Methods • System Specification in a model;

Specifications produced directly

from the Initial System Model to RFP

• Technical Competencies generate

portions of System Model or provide

model compatible input

Element 2 - End State Process & Methods

System

Spec

CDD

Source

Selection

Documents

Technical Requirements

Element 1 Initial

System Model Input

Initial System Model

+

Requirements Engineering

(System-Level)

Transition from Requirements Management

to Requirements Engineering

Element 2


57

Model Centric Source Selection – Vision

Source Selection Process

MCE Gov’t RFP & Baseline System Models

Released to Industry

MCE Contractor Proposal & Proposed System Models

Technical Evaluation

Leveraging System Model Parametrics

Model Centric Engineering (MCE) RFP Package: MCE Government RFP & System Models

System Models

System Models System Models

SSA Source Selection Decision

System Models

Initial Focus areas


Establish Model Based Links Mission and System Models

58

POR System Model Refines ICF

Representation of System

System

Capability and Operational

ICF System Model Elements

POR System Model

ICF System Model

Current – “Illustration” Quality Technical

Information


OOSEM and ASRM to Develop Initial System Model

(Spec)

59

POR System Model

• Kick-Off Workshop to Set Up Model

• Use ICF/ICTB Products When Available.

• If Not Available, Develop Abbreviated Set

for POR

OOSEM Activities for Specify and Design System

ASRM

ASRM - Acquisition Reference System Model

OOSEM – Object Oriented SE Methodology


Element 3 - End-State

Process and Methods (Technical Domain)

60

Element 2

System Model

(Kr Specific)

Element 3

System Model

(Kr Specific)

Integrated Development

Environment (IDE)

CDRL’s

Discrete

SETR

Events

CAD & Co-Simulation Gov.-Kr Collaboration

Through IDE

Element 3

Process and Methods End State

• Competencies use System Model to

define, simulate, validate and verify

system compliance and interfaces

• Government and industry employ

model data as alternative to CDRL’s.

• Near continuous stakeholder

awareness significantly reduces cost

and scope of milestone reviews

• Integrated Model Based V&V


Element 4

System Model

(Kr Specific)

CAD & Reference

Data

Element 4 - End-State

Process and Methods (Technical Domain)

61

Element 3

System Model

(Kr Specific)

CAD & Co-Simulation

Reference Data

for System Level

V&V

Element 4

Individual Aircraft

Digital Twin

Process and Methods End State

• Competencies use System Model to

define, simulate, validate and verify

system compliance and interfaces

• Government and industry employ

model data as alternative to CDRL’s.

• Near continuous stakeholder

awareness significantly reduces cost

and scope of milestone reviews

• Model based system V & V


Verification and Validation

Physical Design and

Architecture

Detailed Specifications

Performance Specifications

Stakeholder Needs

System

SYSTEM VALIDATION

MODEL VALIDATION

DESIGN VERIFICATION

RQMTS VALIDATION

DESIGN VALIDATION

SYSTEM VERIFICATION

PCA DESIGN

VALIDATION

RQMTS VALIDATION

RQMTS VALIDATION

RQMTS VALIDATION

RQMTS VERIFICATION

DESIGN VALIDATION

DESIGN VERIFICATION

Logical and Domain

Architecture

Pre-CONTRACT: NAVAIR DOMINATED

Post-CONTRACT: CONTRACTOR DOMINATED

RQMTS VERIFICATION

MODEL ENVIRONMENT

MODEL VERIFICATION

RQMTS VALIDATION

• V&V Framework defines the many V&V activities in an MBSE environment

• V&V activities are defined for each step and between steps in the SE core process

• V&V activities are performed:

- Utilizing system model

- Performed on system model

- Performed through system modeling


Verification

• Verification activities in an MBSE environment: – Requirements Verification

• Ensuring the system requirements meets the process of requirements engineering

– Design Verification • Ensuring the system design meets the requirements of the

design process

– System Verification • Ensuring the system as designed and as built meets

specified requirements

– Model Verification • Ensuring the system model meets its intended requirements

and intended purpose


Validation

• Validation activities in an MBSE

environment:

– Requirements Validation

• Ensuring the requirements accurately reflect the

stakeholder’s needs

– Design Validation

• Ensuring the design reflects the stakeholder’s needs

– System Validation

• Ensuring the system as specified, designed and built meets

the stakeholder’s needs

– Model Validation

• Ensuring the system model is an accurate representation of

the real world from the perspective of it’s intended use


Instructions, SWPs, & Guides Overview

Develop instructions, Standard Work Packages (SWPs) and

guides to accurately capture, formalize, and implement the

NAVAIR MBSE process for system development, test and

sustainment over the entire life-cycle in support of a successful

systems engineering transformation at NAVAIR

– Explore model-based delivery of process guidance

– Develop SWP(s) needed to apply system modeling to the SE

process for life-cycle support

– Coordinate MBSE SWPs across NAVAIR competencies to ensure

consistent message and alignment

– Develop guides, templates, and/or examples to support the

process of defining the system specification in a model

– Generate a NAVAIR MBSE Instruction


Policy, Contracts, and Legal

66

Contract Language

Acquisition Policy

Model-Centric Source

Selection

Requirements Policy

Technical Data /

Acquisition Artifacts

IP / Proprietary

Data



67

V11.3

Training Content

Development

Coaching &

Mentoring

Workshops

Training Delivery

KEY AREAS OF

RESEARCH:


• Model Integrity

• Ontology

• MDAO

• Multi-Physics

Modeling


• Roadmap &

Implementation

Contract

Language

Tech Data / Acq.

Artifacts

SET Research


Environment Team

Policy, Contract &

Legal Team

Outreach

Acquisition Policy

Initial Training

Workforce &

Culture Team

Model

Visualization

Data, Process,

Knowledge Ref.

Model

Decision

Framework

IT Infrastructure

Modeling

Methodology

Model Repository

SSOT

Modeling Tool-Set

Skill/Performance

Model

Instructions, SWP

& Guides

Source Selection

SE Process Model


Process &

Methods Team

V&V Process

IP/Proprietary

Data

Requirements

Policy

System Modeling

(Spec)

Gov’t/Prime

Collaboration

System Model

Technical

Domain


Recruiting

Deployment

Strategy &

Planning

Increment

Deployment

SET Enterprise

Deployment

Infusion & Pilots

Surrogate

Experiment





Lessons Learned

& Metrics

Acquisition Sys.

Ref. Model

Gov’t

Collaboration Ctr.

Gov’t/Prime

Collaboration Ctr.

Dev. Modeling

Methodology

CBA Links


68

Model Centric Source Selection – Vision

Source Selection Process

MCE Gov’t RFP & Baseline System Models

Released to Industry

MCE Contractor Proposal & Proposed System Models

Technical Evaluation

Leveraging System Model Parametrics

Model Centric Engineering (MCE) RFP Package: MCE Government RFP & System Models

System Models

System Models System Models

SSA Source Selection Decision

System Models

Initial Focus areas


SET Increment 1 Deliverables


SET Functional Areasv9.1

Initial Training - GaTech

SysML 101/102; MIT MBSE

Initial Core of Trained

ModelersMentoring & Coaching Workshop - Start-up

Initial Competency Model

- Skills/Performance

SET Website - MyTeam;

APAN FAQs - Modeling

MBSE Video (long)

MBSE Video (short)

SET Socialization - Internal

& External

SET Performance

Objective - SE Workforce

Initial Modeling

Environment - IT (Unclass)

Initial Modeling ToolSet -

MagicDraw; TeamWork

Cloud; Collaborator

Initial Acquisition System

Reference Model

Legacy Model

Transformation (UML to

SysML)

Specification Document

Generation from System

Model

Trade Study - MBSE ToolsInitial Configuration

Controlled Repository

Standalone Classified Lab

Pilot

Initial Government

Collaboration Center Plan

Initial System Model -

Process Guide/Model

Initial Requirements

Analysis - Process GuideMethodology - (Initial)

Model-centric Technical

Review

Initial Definition of Model-

Centric Source Selection

Process

Virtual SETR - Web-based

(Collaborative ISEE)Model-Centric V&V

POLICYPolicy, Contracts & Legal

Contract Language - IDE

Contract Language -

Model-centric

Collaboration

Contract Language -

Model Data Sharing (IP)

Contract Language -

Model-centric Technical

Review

Research - Model

Integration/IntegritySurrogate Plan

Surrogate SysML Model

(UAV)Surrogate Kick-off Use Cases

RESEARCHTechnical Research

SET INCREMENT 1 DELIVERABLES

PEOPLEWorkforce & Culture

TOOLSIntegrated Modeling

Environment

PROCESSProcess & Methods

SET End-State: Policy, Contracts and Legal

70

SET Framework Element 1

(Mission Capability)


(System Requirements)


(System Architecture & Design)


(System Implementation and V&V)

Services Acceptance of

Minimizing KPPs

Contract Language for

Model-Centric Collaboration

Policy for Collaboration and

Delivery of IP and Proprietary

Data

Collaboration with Industry –

Shared Info (pre-contract)

Contract Language for

Model-based Data and Model

Delivery

DoD Adopting SoS

Acquisition Methodologies

JCIDS Policy

Acquisition Policy

SET End-State (Dec 31, 2020)

Policy for Collaboration and

Delivery of IP and Proprietary

Data


71

MCE Systems Engineering Language for Collaboration Across the Contractual Boundary

POLICY

Policy,

Contracts &

Legal

Contract Language

IDE

Contract

Language –

Model Centric

Collaboration

Contracting

Language-

Model Data

Sharing

Contract Language

– Model Centric

Technical Review

Contract Language

– Delivery of IP and

Proprietary Data

Technical

Requirements

for MBSE X X X X

System Model

(SM) Delivery X X

SM Industry

Standards

Compliance X X X

Architecture

Centric SM X X X

SM Enterprise

Architecture

Conformance X X X

Verification

and Validation

Support X X X


72

POLICY

Policy,

Contracts &

Legal

Contract Language

IDE

Contract

Language –

Model Centric

Collaboration

Contracting

Language-

Model Data

Sharing

Contract Language

– Model Centric

Technical Review

Contract Language

– Delivery of IP and

Proprietary Data

Physical Item

Flow Type

Interfaces X X X

Collaboration

– Pre-

Milestone B X X X

SM Design &

Development

Methodology X X

SM Analysis

X X X X

SM Technical

Reviews X X X X

Government

Ownership of

the Technical

Baseline

X X X X

MCE Systems Engineering Language for Collaboration Across the Contractual Boundary


73

Policy, Contracts, and Legal - Status & Language Examples

Current Status & Language Examples:

Leveraged conferences and networking with Industry to identify and compile

additional contracts language:

– Queried other Government Agencies for MCE Contract Language

– Held discussions with Contracts and Reference model experts

– Identified additional MBE-related content that can be integrated into a larger Contracts

based documents (RFP, SOW’s, PBWS, etc.) to support model-based approaches

Overall Engineering process: The contractor shall implement a model-based engineering

approach in accordance with ISO/IEC/IEEE 15288:2015 Systems and Software Engineering –

System Life Cycle Processes and ISO 10303-242 (STEP AP 242) Managed Model-Based 3D

Engineering resulting in digital representations of program and technical data being used to

support all phases of systems development in accordance with the program office’s systems

engineering plan (SEP)……..

…

Integrated Data Environment: The contractor shall implement an Integrated Data

Environment (IDE) which shall be the single source for all programmatic, technical,

sustainment, and other data produced by the contractor under this SOW. The Contractor shall

maintain documents and data in electronic readable, unprotected, searchable, and captured in

the development environments original format in accordance with ISO/IEC 26555:2015 -

Software and systems engineering -- Tools and methods for product line technical management

and ISO 10303-209:2014 (STEP AP 209) – Multidisciplinary Analysis and Design…….


74

Language Examples:

Requirements Analysis Tasks: The Contractor shall manage requirements traces from

program office provided operational, systems, sustainment, testing, and other requirements to

Contractor specifications, ICDs, subsystem specifications, and component level (hardware,

software, and firmware) specifications using <<insert name>> requirements software or the

contractors chosen requirements management software to ensure functional and interface

requirements are implemented in the design, including COTS and NDI used in support of

production. The requirements model database, including requirements object descriptions and

requirements object relationships, forms the primary tasks deliverable (CDRL XX). The

requirements tool shall encompass the essential processes and capabilities identified in

ISO/IEC TR 24766:2009 - Information technology -- Systems and software engineering -- Guide

for requirements engineering tool capabilities………

…

Architectural Design Tasks: The contractor shall develop architectural models using Systems

Modeling Language (SysML) v1.5 in accordance with ISO/IEC 19514:2017, Information

technology -- Object management group systems modeling language (OMG SysML®)". The

contractor’s shall use the <<insert name>> or Computer Aided Systems Engineering (CASE)

software used to develop the architectural model must exchange model-source data in

accordance with ISO 10303-233 (STEP AP233) Systems Engineering and Design. While the

contractor will produce both model data and graphical representations of this data using the

SysML standard, model data, not the graphical representation, will be the configuration

managed item……...



75

Language Examples:

Analysis Tasks: The contractor will produce systems analysis sufficient to verify that

architectural and solution designs implement requirements including but not limited to Key

Performance Requirements (KPPs), Measures of Effectiveness (MoEs) and Measures of

Performance (MoPs.) This analysis may include simulations, statistical analysis, or other

methods required to provide the objective evidence required to support technical reviews and

acquisition decision making as defined by the program office SEP and contractors SEMP.

Sufficiency shall be determined by the program office in consultation with the contractor.

The Contractor shall use <<insert name>> or commercially available analysis tools and

industry-standard data management protocols which support data exchange through the IDE….

…

Sustainment Tasks: The contractor shall implement a Platform Logistics Management (PLM)

approach through the IDE which provides for data interoperability as defined by ISO

14306:2017 - Industrial automation systems and integration -- JT file format specification for 3D

visualization. The PLM system shall maintain configuration managed data concerning the as-

build design solution, including, as-built drawings, specifications, parts/data lists, wiring lists,

application lists, software designs, computer software code (executable/operating/source code),

software/firmware development tools, firmware, algorithms and modeling, associated software

operating manuals and software/algorithm documentation, Quality Assurance (QA) provisions,

special inspection equipment/designs, special tooling/designs, work instructions, build

procedures and processes, and special packaging instructions…….



76

Language Examples:

Solution Design Tasks: The Contractor shall provide digital copies of engineering modification

orders, modification instructions, modification drawings, and processes altering Commercial Off-

the-Shelf (COTS) equipment through the IDE. Digital technical design packages (TDP) shall

include as-built drawings, specifications, parts/data lists, wiring lists, application lists, software

designs, computer software code (executable/operating/source code), software/firmware

development tools, firmware, algorithms and modeling, associated software operating manuals

and software/algorithm documentation, Quality Assurance (QA) provisions, special inspection

equipment/designs, special tooling/designs, work instructions, build procedures and processes,

and special packaging instructions…….

…

Cyber Security: The Contractor shall provide a comprehensive Cybersecurity design that

implements the applicable baseline Cybersecurity controls from: DoD Instruction 8500.01 –

Cybersecurity, National Institute of Standards and Technology (NIST) Special Publication (SP)

800-53 - Security and Privacy Controls for Federal Information Systems and Organizations,

Committee for National Security Systems Instruction (CNSSI) 1253 - Security Categorization

and Control Selection For National Security Systems as defined in the System Security Plan

(SSP). The Contractor shall ensure that Cybersecurity boundaries (e.g., crypto boundary,

authorization boundary, classification boundary) are clearly and consistently identified in system

models, documents and drawings…..



77

Current Status:

34+ Contract Language Paragraphs identified and documented to

date:

– Additional Paragraphs covering

• Verification & Validation

• Model Based Simulation and Support

• System Model Analysis

• Tool-Independent & Tool-Proprietary Formats

• Model-Based System Design Specifications (Model-Based SDS)

• Collaboration

• System Model Technical Reviews

• IP/Proprietary Data

Training Materials:

– Developing Initial Draft of Training Materials for Policy, Contract & Legal

functional area



78

Policy, Contracts, and Legal – Desired Feedback from Industry

Contract language & feedback regarding :

• MCE Statements of Work

• MCE approaches to applying MBSE

• MCE approach to eliminating CDRLs, providing all system knowledge

via system models

• MCE approach to Government & Contractor Collaboration in a IDE

• MCE Technical Reviews in a IDE

• MCE approach for managing IP & Data Rights in an IDE both Pre-

Contract Award and After Contract Award

• MCE approach for capturing and printing all document based system

artifacts from the System Model


Research - Surrogate

79

MDAO

Modeling Methodologies

Model Ontology

Model Integrity

Multi-Physics Modeling

Integrated Modeling

Environment

Model Integration



V11.3

Training Content

Development

Coaching &

Mentoring

Workshops

Training Delivery

KEY AREAS OF

RESEARCH:


• Model Integrity

• Ontology

• MDAO

• Multi-Physics

Modeling


• Roadmap &

Implementation

Contract

Language

Tech Data / Acq.

Artifacts

SET Research


Environment Team

Policy, Contract &

Legal Team

Outreach

Acquisition Policy

Initial Training

Workforce &

Culture Team

Model

Visualization

Data, Process,

Knowledge Ref.

Model

Decision

Framework

IT Infrastructure

Modeling

Methodology

Model Repository

SSOT

Modeling Tool-Set

Skill/Performance

Model

Instructions, SWP

& Guides

Source Selection

SE Process Model


Process &

Methods Team

V&V Process

IP/Proprietary

Data

Requirements

Policy

System Modeling

(Spec)

Gov’t/Prime

Collaboration

System Model

Technical

Domain


Recruiting

Deployment

Strategy &

Planning

Increment

Deployment

SET Enterprise

Deployment

Infusion & Pilots

Surrogate

Experiment

Lessons Learned

& Metrics

Acquisition Sys.

Ref. Model

Gov’t

Collaboration Ctr.

Gov’t/Prime

Collaboration Ctr.

Dev. Modeling

Methodology

CBA Links

80






Semantic Web Technologies

Multidisciplinary Design,

Analysis and Optimization

MDAO

Modeling Methodologies


SET Research Topics - SERC

Digital System Model:

Single Source of Truth

(Authoritative Source

of Truth)

MDAO

Workflow

Enforces Modeling Methods

Underlying technologies

for reasoning about completeness

and consistency Across

Domains in modeling

tool agnostic way Guides proper usage to ensure

Model Integrity (trust in model

results) for decision making

Provides optimization analysis

Across Domains

to support KPP

and alternatives trades

at mission, system,

& subsystem levels


Graphical CONOPS Scenario for Skyzer UAV Mission


Surrogate Pilot Overview

• Mission: Collaboration between Government and Industry in

Model-based Acquisition under SET Framework

• Goal: Execute SET Framework to Assess, Refine, and

Understand a New Paradigm for Collaboration in Authoritative

Source of Truth (AST)

• Objectives (non exhaustive):

– Formalize experiment to answer questions about executing SET

framework using Surrogate Contractor (SC)

– ”Government team” creates mission, system (& other) models,

“generates specification/RFP,” & provides acquisition models to SC as

Government Furnished Information (GFI)

– SC refines GFI reflects corrections/innovations with physical allocation

views with multi-physics-based Initial Balanced Design

– Simulate continuous virtual reviews and derive new objective measures

for assessing maturing design in AST

– Demonstrate visualizations for real-time collaboration in AST

– Demonstrate and document methods applied

– Investigate challenging areas and research topics in series of pilots


Proposal for Design

Models must be able

to demonstrate aspects

for Produce-ability

Decisions

involving Multi-physics

Status: Use Cases for Surrogate Pilot and

Experimental System (Skyzer)

84

Surrogate

Pilot Use

Cases (UC)

Mission

Model UC

System

Model UC Project Plan

UC

Contractor(s)

System

Model(s) UC

Contractor

Design

Model UC

Source

Section UC

RFI RFP

GFI GFI

Skyzer is Experimental System using Authoritative Source of Truth (AST)

Objectives to Assess SE Framework

Collaboration

in Authoritative

Source of Truth UC

How we Collaborate in AST

Mission Models

System Models

Based on Standards

Proposal

Extends

GFI


Identify Experimental Objectives for Use Cases



Surrogate Pilot


for real-time Collaboration in


86

OpenMBEE


Elements of Authoritative Source of Truth


Government-side of Authoritative Source of Truth

(AST) for Surrogate Pilot

Use Cases for Collaboration Environment and


View Editor*

Model

Management

System (MMS*)

Teamwork

Cloud

Cameo

Collaborator

Integration and

Interoperability

Framework**

Internal Stakeholders • Stevens/SERC

• Engility

• Georgia Tech

• NAVAIR SMEs

• ?

No Magic

Clients with

MDK/DocGen*

(all team members)

Surrogate Contractor • Altair

• ?

External “Monitors” • DoD

• Other Services

• Industry

• Non-SERC

collaborator

?

1

1) Collaboration environment with role-based access for all stakeholders

2) Was/Is analysis from View Editor to track all changes in models

3) Determine roles for Surrogate Contractor (SC) to make entries through

View Editor or possibly MMS in AST to link to SC-side of AST

4) Provide roles so that External Monitoring Organizations can view what’s

happening, and

5) Provide means for External Monitoring Organizations to create “own” sub-

repository so that different organizations can make/link comments that

are either public or private to any stakeholders

6) How do we link ontologies to MMS for semantic reasoning about methods

and tool interoperability across domains (**SERC research)

3

4

5

6

2





Analysis Tools


*OpenMBEE


Mission Model Specification Complies with

Integrated Capability Framework

89

Integrated

Capability

Framework


Use OpenMBEE

Model Development Kit/DocGen

View and Viewpoint Hierarchy

Model Management System

View Editor

Visualization in

View Editor


Formalized Experiment in Integrated Models

1. The Surrogate Project/Planning Model

– Captures evolving set of objectives to be demonstrated, assessed and

refined related to SET Framework Execution

2. The Project Planning Model for Skyzer

3. Surrogate Mission Model for Skyzer

4. Surrogate System Model for Skyzer

5. Surrogate Acquisition Model Skyzer

6. View and Viewpoints for DocGen and other Libraries

7. Surrogate Contractor Design Models

AND

• Creating Authoritative Source of Truth between ”Government Team” and

Industry Surrogate Contractors



CDD

Inte

gra

ted

Te

st

Ve

hic

le #

1

Design & Manufacture Release

MDAO*/SET-BASED DESIGN

Inte

gra

tion

Eve

nts

* Multi-Disciplinary Analysis & Optimization

• Elimination of paper CDRL artifacts and

large-scale design reviews

• Continuous insight/oversight via digital

collaborative environment and

interaction with the Single Source of

Truth





Analysis Tools

Instantiate and

validate design

in models

Move rapidly to mfg.

Substantiation and

insight via modeling

environment

Re-balance as

required

Single Source of Truth Instantiate

System Spec in

a model

Mission

Effectiveness

optimization

V5.0

92

Right-size CDD –

very few KPPs, all

tied to mission

effectives

INSIGHT/OVERSIGHT

Element 1

Element 2 Element 3 Element 4


Formalizing the Use of Models… Creating a Digital Thread…

93

Operational Models Other Business Models

Personnel, support, training, etc.

User Capability Model

System Model

Sub-System 1

Model

Sub-System 2

Model

Sub-System n

Model

Component 1

Model

Component 2

Model

Component n

Model

Wa

rfig

hte

r

Ac

qu

ire

r

Pri

me

Co

ntr

ac

tor

Su

b C

on

tra

cto

rs

Acquisition

Agreement

Main

Contract

Sub

Contracts

SoS

Level

System

Level

Sub-System

Level

Functional Baseline

Allocated Baseline

Initial System Model

Final System Model

System Model is

Authoritative

Requirements Source

(e.g. Gov’t Specification)


Formalized Surrogate Pilot Plan as Model Using

NASA/JPL Ontology Modeling Method


Objectives and Questions in Surrogate Pilot Model

95

These will be traced to

model elements that

will be used to satisfy

these objectives.


Methods for Partition of Work and Modularization


Modeling Enterprise and Model for

Systems Engineering Transformation Pilot


View Editor on Skyzer RFI Mission Model (1/2)


View Editor on Skyzer RFI Mission Model (2/2)


Use NASA/JPL Ontologies


Mission Objectives Characterize Needed

”Experiments” To Assess SET Framework Concept


Surrogate Status

• Updates being posted to APAN continuously

• Surrogate kickoff completed 12/7/2017

• Weekly meetings with Team and Surrogate Contractor

• Conducted a Request for Information (RFI) to provide a SysML

model for Surrogate Contractor to analyze

– Responses that were based on a SysML adaptation demonstrated that

model provided information to understand existing design quickly

• Working RFI for Skyzer (Surrogate Experiment Mission/System)

– Need to ensure that producability decision includes multi-physics design

– Skyzer RFI released February 1, 2018

– Mock Industry Day February 9, 2018

– Post-mock Industry Day meeting Feb 16, 2018 discussed change in

approach

– RFI response due February 28, 2018

• RFP to be issued based on RFI responses

• Element 4 for Phase I targeted for September 2018


Where Are We:

Increment 1 and Elements 1 & 2

103

Functional Areas

Wo

rkfo

rce &

Cu

lture

Inte

gra

ted

Mo

delin

g

En

viro

nm

en

t

Pro

cesses /

Meth

od

s

Po

licy, C

on

tracts

&

Leg

al

Tech

nic

al R

esearc

h

Each Element requires work in the 5 Functional Areas in order to reach “Full Maturity”

Increment 1

Increment 2

Increment 3


We are here

104

Q&A Session
