0% found this document useful (0 votes)
40 views26 pages

2020 System of Systems Engineering Collaborators-Digital Engineering Toolchain

Uploaded by

hgc1953
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
40 views26 pages

2020 System of Systems Engineering Collaborators-Digital Engineering Toolchain

Uploaded by

hgc1953
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 26

SoSECIE Webinar

Welcome to the
2020 System of Systems Engineering Collaborators
Information Exchange (SoSECIE)

We will start at 11AM Eastern Time


Skype Meeting +1 (703) 983-2020, 46013573#
You can download today’s presentation from the SoSECIE Website:
https://mitre.tahoe.appsembler.com/blog
To add/remove yourself from the email list or suggest a future topic or
speaker, send an email to [email protected]
NDIA System of Systems SE Committee
• Mission
• To provide a forum where government, industry, and academia can share
lessons learned, promote best practices, address issues, and advocate
systems engineering for Systems of Systems (SoS)
• To identify successful strategies for applying systems engineering principles
to systems engineering of SoS
• Operating Practices
• Face to face and virtual SoS Committee meetings are held in conjunction
with NDIA SE Division meetings that occur in February, April, June, and
August

NDIA SE Division SoS Committee Industry Chairs:


Mr. Rick Poel, Boeing
Ms. Jennie Horne, Raytheon
OSD Liaison:
Dr. Judith Dahmann, MITRE
Simple Rules of Engagement

• I have muted all participant lines for this introduction and the
briefing.
• If you need to contact me during the briefing, send me an e-mail at
[email protected].
• Download the presentation so you can follow along on your own
• We will hold all questions until the end:
• I will start with questions submitted online via the CHAT window in Skype.
• I will then take questions via telephone; State your name, organization, and
question clearly.
• If a question requires more discussion, the speaker(s) contact info is
in the brief.
Disclaimer

• MITRE and the NDIA makes no claims, promises or guarantees


about the accuracy, completeness or adequacy of the contents of
this presentation and expressly disclaims liability for errors and
omissions in its contents.
• No warranty of any kind, implied, expressed or statutory,
including but not limited to the warranties of non-infringement of
third party rights, title, merchantability, fitness for a particular
purpose and freedom from computer virus, is given with respect
to the contents of this presentation or its hyperlinks to other
Internet resources.
• Reference in any presentation to any specific commercial
products, processes, or services, or the use of any trade, firm or
corporation name is for the information and convenience of the
participants and subscribers, and does not constitute
endorsement, recommendation, or favoring of any individual
company, agency, or organizational entity.
2020-2021 System of Systems Engineering
Collaborators Information Exchange Webinars
Sponsored by MITRE and NDIA SE Division

June 2, 2020
SERC: Methods to Evaluate Cost/Technical Risk and Opportunity
Thomas McDermott and Cody Fleming

June 16, 2020


Challenges for Systems of Systems / Mission Engineering in a Space Acquisition Environment
Lt Col Benjamin Bennett

June 30, 2020


Mission Engineering Playbook
Dr. Judith Dahmann

July 28, 2020


Addressing Mission Engineering from a Lead Systems Integration Perspective
Dr. Warren Vaneman

More coming soon!


|6|

Digital Engineering Toolchain


Aleksandra Markina-Khusid, PhD
Ryan Jacobs, PhD
Jeff Vodov
Greg Quinn

May 19, 2020

© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
|7|

Purpose
OSD Digital Engineering Strategy (June 2018)

Sponsors are implementing OSD strategy


MITRE is employing modern DE practices to meet sponsor objectives
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
|8|

MITRE Digital Engineering Toolchain Vision

MITRE employs a digital engineering


environment that connects people,
processes, tools and data across an
end-to-end digital enterprise

Key Assumptions:
▪ Multi-disciplinary teams are required to address sponsor needs
– SMEs use specialized tools of their domains
▪ Data needs to be exchanged among SMEs’ tools repeatedly on a given project
▪ Data needs to be “served up” in a format usable in the SME’s environment
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
|9|

MITRE Approach To DE Capability Development

Provide Online
Access to Support
Tools in the Sponsor
Toolchain Projects

Integrate Into
Digital Peer Review
Engineering & Share
Toolchain

Identify, Catalog
& Share Reusable
Methods, Processes Identify and
and Tools address Gaps
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 10 |

MITRE Digital Engineering Environment

SE and SW Technology

Systems Model,
Engineering Simulation,
Analytics &
Experimentation
Cyber CALDERA
Operations
and Effects
Electronic
Systems &
Technology
Acquisition &
Mgt Sciences
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1. SW Engineering
| 11 |

Lines of Effort

Drives Requirements Reusable Infrastructure


Partner Projects
Multi- SysML SysML
Technical disciplinary Plugins Profiles
Products Collaboration
Scalable Data
Supports MVC Products Transforms

Drives Requirements Drives Requirements

Supports SME UX Facilitates Implementation of


Productization (UX)
Online
Training
Workflow

Accessible
Information

© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 12 |

Reusable Infrastructure
| 13 |

DE Toolchain Technical Requirements


The Digital Engineering Toolchain shall…
1. Use data from supported authoring tool(s) via a recognized industry standard
2. Manage links between resources across tools
3. Notify users of changes in data artifacts that are relevant to them
4. Transform model data across domain-specific notations to translate key information
5. Update data via a recognized standard – to be consumed by supported authoring tool(s)
6. Support authoring reports on information to address different stakeholder concerns, organizing them in
accessible reporting dashboards
7. Support maintaining a baseline configuration for information (as well as variant configurations)
8. Support analyzing information with reasoners and analysis tools using published query end points and APIs
9. Assign access permissions
10.Use a common terminology standard for tools that are within the same domain
11.Support new tools and new types of tools (Extensibility)
12.Support new versions of tools without requiring changes to DE Toolchain (Maintainability)
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 14 |

Enabling Technologies for the DE Toolchain

Traceability Across Digital Artifacts

Curates, integrates, configuration


Application Lifecyle Management

Analyzes information, generates


Product Life-cycle Management

Host Model in Neutral Format

measures precise differences

Supports design reviews and


Acquires information from

federated information and


Verifies the consistency of

Notifies impacted users of


Source Code Management

Ontology Development
Model Transformation

Visualization of Model

Integrates MagicDraw
Integrates Rhapsody

engineering changes
Plug-in Extensibility
Model Management

system forensics
authoring tools
API Accessible

manages

reports
Intercax Syndeia q s s s q q q q q s w
OASIS OSLC q w q s q q q q q w w w
SECollab s q s q q q q q s s w w s
MDWorkbench q s s q q
Sodius MDAccess q q q q
Inter-Op q q q q
Model Development Kit (MDK) q q
NASA JPL - OpenMBEE Model Management System q s s q q q q q
View Editor q q q q q q
TeamWork Cloud q q q q q q s
No Magic Cameo Collaborator q q q q q s q
Rhapsody Model Manager q q q s q s s q q q q q q
IBM Rational Team Concert q s s q q q q q q q
Rational Engineering Lifecycle Manager q s s q q s s q q q q q
DARPA STITCHES w w w w w
NASA JPL OpenCaesar q q q q w q q q q q
ModelBus ModelBus q q q q
SKAYL PHENOM w q
Modelica Functional Mock-Up Interface (FMI) q q s s q
Maple SOFT MAPLE MBSE q q q q s
JAMA Software JAMA Connect s s q w w
GITHUB q q q q s
GIT GITLAB q q q q s s
JIRA q
Source: R. Cloutier, “2019 JPL MBSE Workshop Survey Results,” Presented at the Atlassian Bitbucket q s
NASA JPL MBSE Symposium, 2019. Microsoft Team Foundation Server q s s q
The Eclipse Foundation Eclipse IDE q q q q
Siemens Teamcenter s s q q q q
Dassault Systemes 3DEXPERIENCE ENOVIA s s q q q
Tom Sawyer Perspectives q q q q q w w

No existing technology to rule them all. Approach is to understand the


workflow among SMEs and identify the right composition of technologies to
facilitate repeated data exchanges among tools.
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 15 |

DE Toolchain Technology Matrix

Up an

Su
Legend

Ex ain mm gn tio ura ds


Us

da sfo

pp

te tai
Tr
e

M a co ss rm nfig oar
te
Does Not Do

ns na on t cce via ion


Us
da

or ain
da m m No we ing

ib bi er ss
e
t a tai ep au
ta
w

M su

M
Modified To Accomplish

ta

ili lit
fr

na n b or tho ma
an p

ty
in de y u
om

ly
s

ag po

:n : n nol rm PI
Does to an Extent

to l d se

zi ase ing ing s

ew ew og is
e L rte

A fo
ng lin D
su at rs our
o
q Does Really Well

y
in d a

pp a a of

to ve y s ion
in e c as ool

i
R
ks

In gra s of ls
ol
or cro ch es

In typ of t d
t

te te
s a sio and s
A
if
be tho

m Pe n A
te

te

gr s too
nd ns ar
i
d ss d nge
t

a
t

at Rh ls
r
u

o hb

es ap
en

M so
e oo
re ool
r

ag d
t
s

a s

ic y
a
t

Dr
s
t
c

in

aw
s

s
$ Commercial Intercax Syndeia s s s s s s w q q q
Open-Source OASIS Eclipse Lyo with OSLC s w w w s w w q s q q q
$ Commercial Sodius Willert SECollab with OSLC q q w w w q s s q q q s q q
Open-Source NASA JPL OpenMBEE s w w q s s q s s q
$$ Commercial Dassault - No Magic Cameo TWC / Collaborator / DataHub q q q s w q s q q
$$ Commercial IBM Jazz ELM with OSLC q q q w s q q q q q q s q
$ Commercial Maple SOFT MAPLE MBSE q s s s s q q
Government DARPA STITCHES w w w w w w w w w w w w
Open-Source NASA JPL OpenCaesar s s q s s q w q
$$ Commercial ModelBus ModelBus with OSLC q q s s q q
$$$ Commercial SKAYL PHENOM s q s
Open-Source The Eclipse Foundation Eclipse Model Framework (EMF) w w w w w w w w q q q q
$$ Commercial Siemens Teamcenter with OSLC q s q q q q q s q s s s
$$ Commercial Dassault Systemes 3DEXPERIENCE ENOVIA s s q q q q q q s s
$ Commercial Tom Sawyer Perspectives q q q s s q
$ Commercial Northwoods Software Go JS s
$$$ Commercial Phoenix Integration ModelCenter q q q q q
$$ Commercial Mentor Graphics Context SDM with OSLC q q q q q q q q
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 16 |

Open Services for Lifecycle Collaboration (OSLC) –


Functional

▪ OASIS Standard (since 2013)


▪ Establish links between
resources in different lifecycle
tools from within those tools
▪ Use resources in one tool to
affect resources in another tool
(e.g. transformation)
▪ Add new types of tools (domains)
▪ Switch versions of tools
▪ Switch tool used for a domain

© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 17 |

Open Services for Lifecycle Collaboration (OSLC) –


Architectural
▪ Domain defines vocabulary (resources) for
each type of tool.
▪ OSLC Core provides cross-domain services
– Resource Description Framework (RDF) for
syntax:
Subject Predicate Object
Resource Property Value
Book “author” “Bob”

– Tracked Resource Sets (TRS) for event-based


▪ Linked Data Platform (LDP)
– HTTP as the application protocol (not
tunneled)
– RESTful services
– Linking data across tools via URLs
– No copying of data
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 18 |

OSLC and Tool Interoperability

Goal of OSLC is tool interoperability which requires the following:

Interoperability
Requirement (IR) Description How OLSC Meets Requirement
1 Physical Network connectivity between tools TCP/IP
2a Application – Specification of how data will be transferred over REST (HTTP+URLs)
Protocol physical connectivity
2b.1 Application – Data Basic syntax used to represent the data sent via the XML
syntax protocol
2b.2 Application – Data Schema used to define how the data is structured RDF
structure within the syntax
2b.3 Application – Data Meaning of all data elements OSLC Resource Shapes in OSLC
semantic Specifications
3 Business Process Overall process that tools are used to support (tools Delegated User Interfaces and Resource
can be orchestrated or choreographed) Previews but mostly process-dependent
Reference: Mihindukulasooriya, N., Garca-Castro, R., and Esteban-Gutierrez, M.: Linked Data Platform as a novel approach for Enterprise
Application Integration. Center for Open Middleware, Ontology Engineering Group (2013)
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 19 |

Examples of Digital Engineering


Workflows on Projects
| 20 |

A Public Sector Program Example:


Technology Insertion into a Human-Centric Process
Goals:
• Build a framework for reasoning about technology insertion into an
architecture supporting a human-centric process.
• Understand the impact of technology choices and process design on
customer experience.
• Key measures of effectiveness include queue lengths and wait times.

© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 21 |

A Public Sector Program Example:


Multi-Disciplinary Digital Engineering Environment
Technical Approach:
▪ Capture tradespace parameterization in architecture model
▪ Generate run matrix for operational simulation from SysML model
▪ Use MATLAB for preliminary data exploration and analysis
▪ Built interactive dashboard for visualization of results
Dashboard for Key
Decision Makers
• Query, Visualize, Review

Operational
Analysis

Tradespace
Model Analysis
Architecture &
transform
Design
engine
• Incremental,
iterative MS&A Cost and Effort
process Analysis
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 22 |

Architecture - Operational Analysis Workflow


Architecture SME Step 2, Architect runs
Operations Researcher
the Tradespace plugin Step 3, OR SME
Step 1, Architect Modeling tool to generate valid is notified of
Analysis Tool
makes updates to designs csv change by email Step 5,
Biometrics model Extendsim
produces
Step 4, OR results csv
SME runs the
Valid Designs simulation

Integrated Model Environment

Step 9, Visualize
Step 8, Operational
results
SMEs provide Step 6, Systems
feedback and iterate Analyst runs
analysis and
visualizes results
Step 7, Review
changes to model
Operations SME with Operational
Systems Analyst
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
SMEs
| 23 |

A DoD Program Example: Eliminate Stovepipes

• Development Stovepipes ▪ Programmatic and Technical


sides not connected

Requirements Design AoA Cost Estimation

© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 24 |

A DoD Program Example:


Multi-Disciplinary Digital Engineering Environment
Technical Approach:
▪ Link Architecture & Design to other relevant disciplines (Cyber, SWAP-C, Cost) via a scalable model transform
▪ Perform synchronization of data based on user notifications
▪ Perform Impact Analysis; Query and Review without having to open an Authoring tool
Dashboard for Key
Decision Makers
• Query, Visualize, Review

Requirements
Analysis
Cyber Analysis
Traceability
via Rhapsody
Gateway

Model SWAP-C Analysis


Architecture &
transform
Design
engine
• Impact Analysis
• Check & synch on Cost and Effort
data updates Analysis
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 25 |

Architecture - Cost Analysis Workflow


Authoring Tool Work Breakdown Structure (WBS)
Step 1, Step 2,
Architect Architect Step 2.1,
makes saves a Step 3, Cost
WBS
updates… OR new model SME is notified
updated via a
identifies a baseline of change
model
GRA
transform
component to
analyze Integrated Model Environment

Architecture SME Cost SME


Step 5,
Step 6, Architect
Cost SME
is notified of Step 4, Cost
saves a
updated cost SME updates
new
estimate and the analysis
baseline
accepts change
to model
Analysis Tool
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.
| 26 |

Lessons Learned
▪ No existing tool addresses all DE integration and interoperability
challenges
– Commercial/open source tools provide indicators on where industry is going
▪ Need to utilize existing standards as much as possible
– Custom solutions are often difficult to deploy and productize in sponsor
environments
▪ DE adoption will only be possible if users can work in their
disciplinary tools
– Need to integrate existing engineering workflows and make it easier for
users to do their day-to-day job
▪ DE is challenging to implement technically and programmatically
– Incremental use case driven progress can help with technical scalability and
required stakeholder buy-in
© 2020 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 19-03071-1.

You might also like