Enterprise Systems-of-Systems Model for Digital Thread ...mitre... · 4/30/2019 · Identify Data Sets to Parameterize ―What are the measurement areas ... Loper M., Ed., Modeling

SoSECIE Webinar - April 30, 2019

Enterprise Systems-of-Systems Model for Digital Thread Enabled Acquisition

Sponsor: DASD(SE)

ByTom McDermott (Stevens)

Molly Nadolski (Ga Tech), Paul Collopy (UAH), Chris Paredis (GT/Clemson)SoSECIE Webinar Series

April 30, 2019

www.sercuarc.org

SoSECIE Webinar - April 30, 2019 2

Agenda

• Introduction

• Methodology: Multi-level Sociotechnical Modeling & Enterprise Systems Analysis

• Systemigrams

• Outcomes & Next Steps

SERC Project RT-182

Digital Thread Enabled

Acquisition


Background


SERC Project RT-182 Digital Thread Enabled Acquisition

This research was conducted to evaluate the impacts of DE on current DoD acquisition enterprise processes. The following questions guided the research:

• What changes are likely to emerge from the transition to DE processes, methods, and tools?

• What are the enablers and barriers to such innovation in the DoD acquisition enterprise?

• What stakeholders will be affected and how will they likely embrace or oppose change?

• How might stakeholders be incentivized to embrace innovation and how will this be measured?

• What are the leading and long-term indicators of change?

• How might the value of such changes be predicted and measured?


Read Our Report


Agenda

SERC Project RT-182


Acquisition

• Introduction


• Systemigrams



Enterprise SoS Process

Graphic: W. Rouse & M. Pennock, Complex Enterprise Systems,

5th Annual SERC Sponsor Research Review February 25, 2014

Descriptive

Models

Graphic: smumn.edu/facpages/~dbucknam/rat_cartoon.jpg


Full Process & Project Scope

1. Context Analysis

2. Central Questions of Interest

3. Identify System Structure & Phenomena

― Background Research

― Interviews

4. Visualize Relationships

― Systemigram Narratives & Diagrams

5. Identify Areas of Exploration

― Innovation System Analysis

― Key stakeholders

― Critical enablers & barriers to change

6. Identify Data Sets to Parameterize

― What are the measurement areas that will drive change?

― What measures are collected versus what should be collected

2. Agree on Central Questions of Interest

3. Identify System Structure & Phenomena

4. Visualize Relationships

5. Identify Areas of Exploration

6. Identify Data Sets to Parameterize

7. Identify Relevant Computational

Models

Agree on Context & Boundaries

Conceptualize Models and abstractions

Develop Narratives &

Diagrams

Develop Data Models

Integrate Computational

Models

Test/ Verify

Rouse, W.B, Modeling and Visualization of Complex Systems and Enterprises, Wiley, 2015.

Loper M., Ed., Modeling and Simulation in the Systems Engineering Lifecycle, Springer, 2015.

1. View the System as a Multi-Layer

Enterprise

Framework: Facilitation: Model Design:


1. The problem

situation:

unstructured

7. Action to

improve the

problem

situation

6. Feasible,

desirable

changes

2. The problem

situation:

expressed

5. Dramatization

and Dialogue

3. Structured

text

4a. Formal

system

concept

4. Systemigram(s)

Design

4b. Other

systems

thinking

Real world

Systems thinking

Stakeholder

Interviews

Design Workshop,

Actors &

Enablers

Stakeholder

Reconciliation,

Measures of

Change

Central

Questions of

Interest

Innovation

System

Development

A qualitative stakeholder-driven process to produce quantitative goals

In Practice: Enterprise Systemigrams


SoS Perspectives


Stakeholder Interviews & Research

• 15 Project Visits Completed, 25 People Interviewed

―DASD/SE

―Aerospace Corp

―JHU APL

―SAF/AQ

―Army PM-Aviation

―Army Future Vertical Lift Program Office

―Ground-Based Strategic Deterrent Program Office

―SPAWAR San Diego

―TARDEC

―J8 JCIDS office

―DOT&E

―NASA-Langley

―NASA-Marshall

―JPL

• Also:

―~50 documents reviewed

―6 facilitated meetings with DASD/SE team


Interview Process

Resources

Human Resources and Training Opportunities: Trained people who can put science, technology, and innovation to work for problem solving

Technological Resources: Tools and the knowledge to use them

Institutional and Infrastructure Resources: Organizations or functions that provide the structure and collective knowledge needed to innovate

Collaboration & Communication Resources:Connections among parts of the system that diffuse knowledge and enable learning

Knowledge Resources: Information embedded in research, indigenous knowledge, intellectual property, etc.

The Present: What cannot be sustained in the future we seek

The Future: What characteristics of the system we aspire to create

The Transformation: The zone of innovation, signals of the future in the present

Actors


Storytelling and Narrative

Individual Narratives& Statements

Meaningful Course of Action

AnecdoteDatabase

storytelling and mapping tools to describe the future as a conceptual model


Context Analysis (Selected Phrases)

Enabling Environment Key Actors & Resources Interactions/Activities Outcomes/Outputs

Do

mai

n

• Operational Context –

increasing complexity

• DoD DE Strategy

• Manufacturing 4.0 drivers

• Global innovation in DE

• Curate models across domains, fidelity,

phases and the lifecycle

• Goal 1: Formalize the development,

integration and use of models to

inform enterprise and program

decision making

• Map the realm of the possible with

warfighter needs

Inst

itu

tio

ns • Develop, mature, and

use IT infrastructures

• Define and govern

authoritative source of

truth

• INCOSE and other

professional organizations

• Digital program documents

• Enterprise owns the ontology and data

layer for analytical approaches

• Libraries of reusable models

• Pay once for data, reuse everywhere

• Goal 2: Provide an enduring

authoritative source of truth (AST)

• Goal 4: Establish a supporting

infrastructure and environment

Pro

cess

es

• Lexicon, taxonomies,

ontologies

• Paperless system and

technical information

• Communities: Standards,

guides

• Communicators/

matchmakers

• Model governance/version

control mgmt.

• Better informed Decision

makers

• Digital twin that injects data back into

the models

• System data accessible from a single

portal

• Eliminate human process of finding and

using data

• Everything needed is on desktop, what’s

been done before is there to reuse

• Goal 3: Incorporate technical

innovations to improve the

engineering practice

• opportunities that can be gained from

deeper information in the AST

• make the process more efficient and

reduce rework

• capture and maintain lessons learned

Pe

op

le

• Comfort with

technology

• Usability of DE

methods & tools

• Organizational and

cultural resistance

• Learning systems that

adapt to individual

abilities

• Leadership & messaging

• Older vs younger workforce

• Human capital - skills

• A-Teams & B/C-Teams -

performance

• Enhance collaboration

• Humans can focus on creative work and

machines can take care of mundane

tasks

• Understand incremental value of all

trades, done dynamically

• Goal 5: Transform Culture and

Workforce

• easier to ingest new processes and

incorporate acquisition expertise into

the tools

• make the B-team and C-team players

perform more at the A-Team level


DE Transformation Systemigrams


Agenda

• Introduction


• Systemigram; Authoritative Source of Truth


SERC Project RT-182


Acquisition

Digital Models

Contractor

Owned

Government

Owned

Program Office Staff

Developers

Procurement

Program Managers

System

Complexity

Configuration

Management

Design

Escapes/

Defects

IT Savvy Workforce

More flexible

More distributed

System

Engineering

Standards

Actors

Domain

Structure

Processes/

Resources

Legend

System

Characteristics

Connectedness

Safety

Reliability

Security

Size

Weapon System

Acquisition

Sustainment

Production

Development

Concept

drives

Increasing

Is too great to be

understood by

individual

Authoritative Source of Truth

DoD Policy Domain Specific

Federated Data Set

Weapon

Systems

Other

Programs

Constituent

Systems

Which are

dependent

on

provide

Government

Program/

Enterprises

To provide

Systems-of-

Systems

Analysis

Needs

access

to

Authoritative

Source of Truth

Central Data

Repository

Model Libraries

Common Data

Baselines

(like FMECA)

Trust

Interoperability

Tech Data

Procurement

Test

Data

Enables

AI-enabled Big

Data Tools

Central Data Storage

Cloud Server

Single Portal

Computing

System

Extracted

from

Ontology &

Data Standards

Data & Model

Evolution

Data & Model

Availability

Instantly

on the

Scale and

Complexity

Version

Control

Endurance

Warfighter

Realm of

the Possible

Innovation

Agility

Competition

Finding &

Using Data

By better

managing

To Eliminate/

Reduce/

Control

Govern

Use

Define

Provide

Everything is

on the

Desktop when

Needed

Knowledge

Translation

Create

Buy-in

System

Updates

Is a feature

of today’s

To set

Which

governs

Needing a

Driving

strategy

from the

Leads to

inability to

sustain

Is a good

starting

place for

Has existing

Who

produce

Resides in

Makes

up the

Working for

Deciding

Initial

Source of

To

develop

Feed a Validated by

Hire an

Future

Systems

Engineers

for

Responsible for

Help manage

Must manage the Of the

Must ensureOf the

For the

For the

ofenabling

Built &

used by

defines

supports

for

of

Between

Manage

Improving

Critical to

enabling

spurs

need

Managing

the

Strategy

System

Complexity

Configuration

Management

Actors

Domain

Structure

Processes/

Resources

Legend

Increasing


DoD Policy

Government

Program/

Enterprises

To provide

Authoritative

Source of Truth

Central Data

Repository

Model Libraries

Common Data

Baselines

(like FMECA)

Provide

To set

Which

governs

Driving

strategy

from the

Leads to

inability to

sustain

Strategy

System

Complexity

Actors

Domain

Structure

Processes/

Resources

Legend

Increasing


Authoritative

Source of Truth

Central Data

Repository

Model Libraries

Common Data

Baselines

(like FMECA)

System

Characteristics

Connectedness

Safety

Reliability

Security

Size

Weapon System

Acquisition

Sustainment

Production

Development

Concept

drives

Weapon

Systems

Other

Programs

Constituent

Systems

Which are

dependent

on

provide

Systems-of-

Systems

Analysis

Needs

access

to

Define

Is a feature

of today’s

Needing a

Initial

Source of

To

develop

Strategy


Developers

Procurement

Program Managers

Is too great to be

understood by

individual

Working for

System

Complexity

Design

Escapes/

Defects

Actors

Domain

Structure

Processes/

Resources

Legend

Increasing


Authoritative

Source of Truth

Central Data

Repository

Model Libraries

Common Data

Baselines

(like FMECA)


Cloud Server

Single Portal

Computing

System

Finding &

Using Data

By better

managing

To Eliminate/

Reduce/

Control

Everything is

on the

Desktop when

Needed

Resides in

for

System

Characteristics

Connectedness

Safety

Reliability

Security

Size

drives

Strategy

Standards

Is a good

starting

place for

Has existing

Digital Models

Contractor

Owned

Government

Owned


Developers

Procurement

Program Managers

System

Complexity

Configuration

Management

Design

Escapes/

Defects

Actors

Domain

Structure

Processes/

Resources

Legend

Increasing

Is too great to be

understood by

individual


Domain Specific

Federated Data Set

Government

Program/

Enterprises

Authoritative

Source of Truth

Central Data

Repository

Model Libraries

Common Data

Baselines

(like FMECA)

Tech Data

Procurement

Test

Data


Cloud Server

Single Portal

Computing

System

Extracted

from

Data & Model

Availability

Instantly

on the

Finding &

Using Data

To Eliminate/

Reduce/

Control

Everything is

on the

Desktop when

Needed

Create

Buy-in

Which

governs

Driving

strategy

from the

Leads to

inability to

sustainWho

produce

Resides in

Makes

up the

Deciding

Feed a Validated by

for

of

Strategy

Critical to

AI-enabled Big

Data Tools

Help manage

Digital Models

Contractor

Owned

Government

Owned

Design

Escapes/

Defects

Actors

Domain

Structure

Processes/

Resources

Legend


Test

Data


Cloud Server

Single Portal

Computing

System

Extracted

from

Finding &

Using Data

To Eliminate/

Reduce/

Control

Everything is

on the

Desktop when

Needed

Validated by

for

Strategy

Trust

Enables

Warfighter

Agility

Use

Knowledge

Translation

Future

Systems

Engineers

For the

Built &

used by

supports

for

Between

Improving

Digital Models

Contractor

Owned

Government

Owned

Actors

Domain

Structure

Processes/

Resources

Legend


Strategy

Knowledge

Translation

Future

Systems

Engineers

Built &

used by

supports

for


Cloud Server

Single Portal

Computing

System

Data & Model

Evolution

Version

Control

Govern

of

Manage

IT Savvy Workforce

More flexible

More distributed

System

Engineering

Government

Program/

Enterprises

Hire an

Must manage the Of the

Must ensureOf the

Scale and

Complexity

Endurance


Agenda

• Introduction


• Context Background: DE Transformation

• Systemigram; Workforce and Culture


SERC Project RT-182


Acquisition

Program Office

Workforce

Procurement

Engineering

Program

Manageme

nt

Prod./

Quality

Assurance

Business/

Financial

Management

Test &

Eval

Actors

Domain

Structure

Processes/

Resources

Legend

Workforce and Culture

Is no silver

bullet for good

Must be

about

uses

Seeing

increasing

Has

mature

Do not

Have

the

Performed

by

Less

receptive touses

Frustrated

with lack

of

cause

s

More

receptive to

Link together

Broaden

perspectives

with

Provide

Limits

delegation to

Driving

transition to

Requiring

reprioritizatio

n of the

To

do

Driving

change in

of

Ability

to

model

across

Systems

Engineering

System

Complexity

Disciplinary

Roles

Aging

Workforce

Experienced

Engineers

Younger

Engineers

Digital

ModelsAttritio

n

Digital

Engineering

Knowledge

Transfer

Pace of

Adoptio

n

MBSE

Program

Collaboration

“Heroes”

Engineering

Workforce

Software

Engineering

System

Engineerin

g

Manufacturing

Hardware

Engineering

Test &

Eval

Hav

e the

Leads

to

Concern

Will lead

to more

technica

l

Struggle

with formal

cross-

disciplinary

Rely too

much on


Cloud

Server

Single Portal

Computing

System

Communication

With

stakeholders

Across roles

Across

disciplines

Leadership

Creat

e

Buy-

in

Will

reduce

Messaging

Reduce

risk

Communicate

better

Do the same

things faster

Create better

informed

requirements

Make better

informed

decisions

Ability to assert

completeness

More work

flexibility

Strategic

vector/

Commander’s

intent

Must provide

Needed

to

Finding &

Using Data

to

Everything is

on the

Desktop when

Needed

for

Transform

Workforce

and

Culture

Must

incentivize

Digital

Collaboration

PlatformsLack formal

Digital Tools

Support

collaboration

Different uses

of similar tools

Customize user

experience

Provide effective

visualization

DE Initiatives

Innovation

spaces &

projects

Communities of

Practice/

Interest

Guidebook

Chapter on

MBSE

Shared

knowledge/

Authoritative

Source of Truth

Must

produc

eTo create

the

necessar

y

Mus

t

Wit

h

Must

support

investmen

t in

uses

Must

invest

in

an

d

Bridge the

modelers to

acquirers gap

Will

help

Leading

to

improved

on

Must

persist

to

Needed to

More

“A”

Players

into

Will

be set

by

Agility

Improving

Tool

Vendors

Program Office

Workforce

Procurement

Engineering

Program

Manageme

nt

Prod./

Quality

Assurance

Business/

Financial

Management

Test &

Eval

Actors

Domain

Structure

Processes/

Resources

Legend


Is no silver

bullet for good

Must be

about

uses

Seeing

increasing

Has

mature

Do not

Have

the

uses

Driving

change in

Ability

to

model

across

Systems

Engineering

System

Complexity

Disciplinary

Roles

MBSE

Engineering

Workforce

Software

Engineering

System

Engineerin

g

Manufacturing

Hardware

Engineering

Test &

Eval

Hav

e the

Communication

With

stakeholders

Across roles

Across

disciplines

Actors

Domain

Structure

Processes/

Resources

Legend


Is no silver

bullet for good

Must be

about

uses

Seeing

increasing

Has

mature

Performed

by

Less

receptive touses

Frustrated

with lack

of

cause

s

More

receptive to

Link together

Broaden

perspectives

with

Provide

Limits

delegation to

Driving

transition to

of

Ability

to

model

across

Systems

Engineering

System

Complexity

Disciplinary

Roles

Aging

Workforce

Experienced

Engineers

Younger

Engineers

Digital

ModelsAttritio

n

Digital

Engineering

Knowledge

Transfer

Pace of

Adoptio

n

MBSE

“Heroes”

Leads

to

Concern

Rely too

much on

Will

reduce

To create

the

necessar

y

Actors

Domain

Structure

Processes/

Resources

Legend

Workforce and CultureMust be

about

Seeing

increasing

Frustrated

with lack

of

cause

sDriving

transition to

of

Systems

Engineering

System

ComplexityAttritio

n

Digital

Engineering

Pace of

Adoptio

n

Leadership

Creat

e

Buy-

in

Will

reduce

Messaging

Reduce

risk

Communicate

better

Do the same

things faster

Create better

informed

requirements

Make better

informed

decisions

Ability to assert

completeness

More work

flexibility

Strategic

vector/

Commander’s

intent

Must provide

Needed

to

Finding &

Using Data

to

Everything is

on the

Desktop when

Needed

for

Transform

Workforce

and

Culture

Must

incentivize

Digital

Collaboration

Platforms

DE Initiatives

Innovation

spaces &

projects

Communities of

Practice/

Interest

Guidebook

Chapter on

MBSE

Shared

knowledge/

Authoritative

Source of Truth

Must

produc

e

Mus

t

Wit

h

Must

support

investmen

t in

Must

persist

to

Needed to

More

“A”

Players

into

Will

be set

by

Agility

Improving

Tool

Vendors

Younger

Engineers

of


Cloud

Server

Single Portal

Computing

System

Digital

Collaboration

Platforms

Digital Tools

Support

collaboration

Different uses

of similar tools

Customize user

experience

Provide effective

visualization

To create

the

necessaryuses

and

on

Tool

Vendors


Workforce & Culture

• Most stakeholders and experts do agree there is a cultural change at

play

• Divergence in perspective in regards to what this might look like

• Change in the “old guard” to “new guard”, whether or not there are

workforce capabilities and the “talent” will look like

• Substantial workforce shift: new tools which bring in digital natives and

will be a merger of new technology and existing experience

• Are there capabilities and resources to address the changes?

• Tensions between the old and new guard

• Evolution of Systems Engineering and System Modeling roles & methods

• Digital collaboration and access to truth data is a key enabler

• Commitment of leadership is essential

• Investment, common messaging, safe places to experiment

• What innovations will drive the future DE desktop environment?


Agenda

• Introduction



• Systemigram; Inform Enterprise and Program Decision Making


SERC Project RT-182


Acquisition

Actors

Domain

Structure

Processes/

Resources

Legend

Inform Enterprise and Program Decision Making

Government Model

Concerns

Appropriate

abstractions

Enterprise

Architecture

Define context

Right fidelity

Vendor Model

Concerns

Better

understand IF’s

Support the

Digital Twin

Inject context &

return design

Pull the digital

thread

Model

Development

& Curation

Standards

Development

Make Systems

Engineering

more Efficient

Decision

making

Digital Model

for Human

Understanding

Lessons

Learned

Authoritative

Source of Truth

Digital Data

Models

Simulation

Early Stage

Program

Development

Increase

effort in

SME

knowledgeFeeds

into

for

Acquisition

Cost savings

Initially little

Model

Developers

Systems

Engineering

for

Communication

Media

To output

Decision

Makersfor

Models

form

Patterns

Digital

Requirements

define

CDD

To produce the Immediate

knowledge

of

Operational

Planning &

Force Structure

Satisfy

Capabilities, not

Requirements

Design to

System

Development

Process

Of the

Quality

Control

More time for

Good Cross-

Program

Functional Models

A living

Digital Twin

Digital

program

history

Simulate

Operations

at Scale

Different Models

representing same

capabilities at

different scales

Digital

Thread

More Robust

AoAs

needs

And process

to get to

With

continuity

through

Prototyping

Metadata

to

Domain

specific models

Ontologies

Capability

Assessment

Starts the

Link to

Feed

into Support

Milestone A

Milestone B

capturing

Systems Engineering

Behaviors

Rethink

Configuration

Management

Integrate Robust

SE Process

Avoid Box-

Checking

Eliminate

Checklists

Acquisition

Behaviors

Being a better

Customer

Creating better

Proposals

Simulate before

Spending

inform

Produces a

Model Management

Concerns

Workflows

Modeling SW

Interoperability

Model security

Model sharing

Program Manager

Concerns

Cost savings

Design escapes

Design changes

System level trades &

analyses

capturing

For future

To Eliminate/

Reduce/

Control

Actors

Domain

Structure

Processes/

Resources

Legend


Model

Development

& Curation

Authoritative

Source of Truth

Digital Data

Models

Simulation

SME

knowledgeFeeds

into

Different Models

representing same

capabilities at

different scales

Metadata

Domain

specific models

Ontologies

Actors

Domain

Structure

Processes/

Resources

Legend


Decision

making

Digital Model

for Human

Understanding

Systems

Engineering

for

Communication

Media

To output

Decision

Makersfor

Systems Engineering

Behaviors

Rethink

Configuration

Management

Integrate Robust

SE Process

Avoid Box-

Checking

Eliminate

Checklists

Acquisition

Behaviors

Being a better

Customer

Creating better

Proposals

Simulate before

Spending

Produces a

Actors

Domain

Structure

Processes/

Resources

Legend


Government Model

Concerns

Appropriate

abstractions

Enterprise

Architecture

Define context

Right fidelity

Make Systems

Engineering

more Efficient

Authoritative

Source of Truth

Digital Data

Models

Simulation

SME

knowledgeFeeds

into

for

Digital

Requirements

define

CDD

To produce the

Operational

Planning &

Force Structure

Satisfy

Capabilities, not

Requirements

Design to

System

Development

Process

Of the

Quality

Control

More time for

Good Cross-

Program

Functional Models

A living

Digital Twin

Digital

program

history

More Robust

AoAs

needs

And process

to get to

With

continuity

through

Capability

Assessment

Starts the

Link to

Feed

into Support

Milestone A

Milestone B

capturing


Agenda

• Introduction



• Systemigram; Other Insights


SERC Project RT-182


Acquisition

Actors

Domain

Structure

Processes/

Resources

Legend

Technical Innovations to Improve Engineering Practice

Superior weapons

systems

Effective technical

innovation

Engineering

decision

making

Data Technologies

Machine Learning

Data Analytics

IoT

Ontology

Engineering

Superior Modeling

Capabilities

Authoritative

Source of TruthData Repositories

Materials DB

Weather DBSE Modeling

languages

Formal/

Unambiguous

Intuitive

Layered

Uncertainty

Characterization

Validation

Quantification

Calibration

Knowledge

Repositories

Structured

Unstructured

HPC

Infrastructure

Energy

Efficient

Scalable

Simulation

Algorithms

Human-in-the-loop

Multidisciplinary

Real-Time

Modelers

Decision

Makers

Language

Architects

SMEs

Communities

of Practice

Visualization

Capabilities

VR/AR

Data Viz

Tradespace

Superior

Reasoning/Inference

Capabilities

Superior

Interpretation

Capabilities

Superior System

Creation/Definition

Capabilities

requires

Superior

Communication

Capabilities

maintain

advantage over

Agile

Adversary

drives

need for

enables

Acquisition

Stakeholders

Supply Chain

Program Office

Contractors

System

Complexity

results in

requires

achieve

through

Federated

Model Repository

implemented in

supported by

useexpress

knowledge

to generate

use

More

Comprehensive

Models

Digital Twin

achieve

through

incorporated in

form

generate

serve as

input to

serve as

input to

Digital Collaboration

achieve

through

Generate

data for

performs

performsperforms

informs

Exploration

Capabilities

Tradespace

Exploration

Optimization

performs

provides

insight to

The Cloud

Model Checking

Formal

Verification

Reasoning

Algorithms

Consistency

& Completeness

Checking

makes SE

more efficient

enables

Assuring

mission

success

Agile

Scalable

Superior

Engineering

Capabilities

Cost effective

Implemented in

achieve

through

supports

Models

form

Patterns

Simulate at

Scale

scales with

supports

Enables

Enables

Feeds

Available

on

Foster

Support

Manage

Facing

Replace

with

Need to Move

Beyond

Digital Engineering Infrastructure

Tomorrow’s

Digital Engineering

Today’s

Infrastructure

Comprehensive,

Effective

Configuration

Management

Focus on

Manual Processes

Finding Data

60 days to

get data off

test range

Using Data

DE Capability

MBSE Tools

MBSE language

Processes

Building

Manage Data

Buy Data

from

Others

Search for

Relevant

Data

Automated

Data

Extraction

Real Time

Quick Look

High Fidelity Models

Living Digital Twin

Threats

Libraries of

Information

Different

Levels

Current Resources

MS Office Tools

Data Repositories like

the Wild West

Configuration

Management

Integrated

Tools

Complete

Package

Databases

Outcomes

Upcoming

Systems

Greater Scale

Greater

Complexity

Systems of

Systems

Must

Eliminate

ManagingNeed

Necessitates

Need Policy

forUsing IT to

Transition

to

Spec Doc Writers

Actors

Domain

Structure

Processes/

Resources

Legend

Transition

System Level

Trades and

Analysis

To

Parametric

Tools

Enables

Enables

Manage

Rigorous

Systems

Engineering

Enable

Return to

Leads to

The Cloud

Available

on

Available on

Collaboration

across Disciplines

and Locations

Interoperable

Interconnected

System Development

___ in the Loop

Training

Augmented

Reality Simulation

Operations

Enables

Focus on


Digital Information Exchange

Presented at inaugural DEIXWGmeeting, INCOSE IS 2017

Change the nature of AoAsChange how

we curate data and models

Change what Systems

Engineers do

Change Reqs

process


Agenda

• Introduction


• Systemigrams


SERC Project RT-182


Acquisition


Outcomes and Next Steps

• Created holistic model of DoD Acquisition Enterprise change as DE is gradually adopted

• Good agreement across stakeholders on the nature of the strategy

• Descriptive modeling process reveals scope of change

• Testing insights in multiple forums using Systemigrams

• Base models informing other activities:

―Digital Engineering Working Group (DEWG)

―Digital Engineering Information Exchange Working Group (DEIXWG)


Next Phase – DE Metrics

• Theme: “A Program Office Guide to Successful DE Transition”

• Work with several DoD program offices, contractors, and tool providers

• Identify measures of success, anddefine multi-level measurement models

―Near- and long-term change indicators

• Identify potential innovation game-changers

―Define enablers and barriers to innovation

―Define cross-sector innovation opportunities


Future Research Needs

• Model Curation and Certitude. Must develop a rigorous approach to verify, validate, and accredit the models that are incorporated into the Authoritative Source of Truth, particularly quality and range of valid use.

• Metadata standards for the Authoritative Source of Truth. Extend SET work on ontologies and metadata/metamodel libraries and tools.

• Human Capital. This will be a significant shift in the workplace, leading to an “IT/Data Savvy” workforce. Training programs must evolve with the strategy.

• Bringing in the first and last phases. Need to engage and define how the capabilities assessment and development, operational, and test functions adopt and benefit from DE.

• Evolution of Benefits of DE. A sustained program that encourages exploring the art of the possible and understanding of the unique use cases that will evolve should be pursued.

SoSECIE Webinar - April 30, 2019

Questions?

Thank you!

Documents

Enterprise Systems-of-Systems Model for Digital Thread ...mitre... · 4/30/2019 · Identify Data Sets to Parameterize ―What are the measurement areas ... Loper M., Ed., Modeling