9/3/2019

1

DE, v2, and 2.0:A Discussion of All (SE) Things Model-Based and DigitalDavid Long

President, Vitech Corporation

Former President and Fellow, INCOSE

david.long@vitechcorp.com

Copyright © 2019 by Vitech.

Connecting People, Disciplines, and Insights:Essential Context for Systems Engineering

Systems engineering focuses on ensuring the pieces

work together to achieve the objectives of the whole.Systems Engineering Body of Knowledge (SEBoK) 2

Investors

Architects

Designers

Engineers

Builders / Programmers

Inspectors

Operators

Users

Image credit:US Department of Transportation

9/3/2019

2

3

CONCEPT DEVELOPMENT

Classical Engineering in a Complicated World

REQUIRED

R1

R2.2

R1.1

R2.3

R2

R2.1

R1.2

R3

R4.2

R4.1

R

R4

R5

BEHAVIOR

F1

F2.2

F3.1

F2

F2.1

F3.2

F3

F4.2

F4.1

F

F4

F5

F3.3

F6

F6.2

F6.1

L1.2

L3.1

L1

L1.1

L3.2

L3

F4.2

F4.1

L

L4

F5

L3.3

L2

STRUCTURE

Systems Challenges in Today’s World:Exceeding the Capabilities of Traditional (S)E

4

SE Vision 2025. Copyright © 2014 by INCOSE. All rights reserved.

Complexity exceeding

the bounds of

traditional siloed

approaches

Image credit: Alisa Farr for Letter27. farrimages.com

9/3/2019

3

5

MBSE 1.0: A Well-Intentioned – but flawed – Approach

Seeing the Bigger Picture:What MBSE Should Be All About

6

• Making system descriptive and analytical models explicit, coherent, and consistent• Evolution from low-fidelity representations in documents to higher-fidelity, richer

representations

• Improved granularity of knowledge capture for management, analysis, and learning

• One architectural model connecting multiple analytical models

• Leveraging models for communication and analysis

• Developing an “authoritative source of truth” for system design and specification

• Ensuring consistent design and specification (when done well)

• Providing an explicit system model to engineering teams

An evolution – not revolution – in thinking and approach…An evolution that offers transformative results

9/3/2019

4

Seeing MBSE in the Greater ContextDigital Engineering, v2, MBE, and a manifesto

7NDIA Model-Based Engineering

Final Report, February 2011

A New Digital Engineering Strategy(June 2018)

8

9/3/2019

5

A Muddy Sidebar:Models, MBSE, and Digital Engineering

9

Model: a graphical, mathematical (symbolic), physical, or verbal representation or simplified version of a concept, phenomenon, relationship, structure, system, or an aspect of the real world.

www.businessdictionary.com

Model: a physical, mathematical, or otherwise logical representation of a system, entity, phenomenon, or process.

DoD5000.59-M 1998

Model-based systems engineering (MBSE) is the formalized application of modeling 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, September, 2007

Digital Engineering: an integrated digital approach that uses authoritative sources of systems' data and models as a continuum across disciplines to support lifecycle activities from concept through disposal.

ODASD-SE, 2017

A Notable Shift for SysML:The Vision for SysML v2

10

• Increase adoption and effectiveness of MBSE by enhancing• Precision and expressiveness of the language

• Consistency and integration among language concepts

• Interoperability with other engineering models and tools

• Usability by model developers and consumers

• Key elements• New metamodel that is not constrained by UML

• Robust visualizations based upon flexible view and viewpoint specification and execution

• Standardized API to Access the Model

• Proposed timeline• Initial submission Jun 2020; final Jun 2021

Credit Sandy Friedenthal, 2019 INCOSE International Workshop

9/3/2019

6

Transforming Engineering: A New Manifesto

11

Transforming the Engineering Enterprise through MBSE 2.0

12

9/3/2019

7

Exceeding the Capabilities of Traditional (S)E: Capturing Knowledge, Responding to Change

13Image credit: Alisa Farr for Letter27. farrimages.com

System scale

Mission complexity

Technical complexity

Project team complexity

Dynamic complexity

Transforming from Siloed Engineering (MBSE 1.0)

14

CONCEPT DEVELOPMENT

REQUIRED

R1

R2.2

R1.1

R2.3

R2

R2.1

R1.2

R3

R4.2

R4.1

R

R4

R5

BEHAVIOR

F1

F2.2

F3.1

F2

F2.1

F3.2

F3

F4.2

F4.1

F

F4

F5

F3.3

F6

F6.2

F6.1

L1.2

L3.1

L1

L1.1

L3.2

L3

F4.2

F4.1

L

L4

F5

L3.3

L2

STRUCTURE

9/3/2019

8

REQUIRED BEHAVIOR STRUCTURE AS DESIGNED AS BUILTAS ORDERED AS DELIVERED AS SERVICED

CONCEPT DEVELOPMENT PRODUCTIONUTILIZATION &

SUPPORT

RETIR

E

Functioning in an interdependent environment requires that every team possess a holistic understanding of the interaction between all the moving parts.

Team of Teams, 2015

to Concurrent Engineering of Systems (MBSE 2.0)

which Resets the Equation for MBSE

16

Engineering of Systems / Digital Thread / Digital Twin / Digital Engineering

requires

Concurrency

requires

Concurrent MBSE / MBSE 2.0

is maximized by

Re-engineering the Engineering Enterprise

built upon

A Holistic Systems Perspective

9/3/2019

9

Understanding Concurrency and Concurrent MBSE

17

MBSE 2.0(aka Concurrent MBSE)

concurrent MBSE(the ability for a team of systems engineers

to work on their systems model in parallel)

concurrent MBSE(the ability for a systems team to effectively

engage all members and stakeholders)

concurrent MBSE(the ability to effectively engage detailed

design within the Engineering of Systems

framework while eliminating the air gap)

Identifying the Keystone: The Systems Metamodel as the Foundation for the Engineering Enterprise

18

…more than diagrams

…more than a data dictionary

…more than capture

…more than specification

…more than the system of interest

9/3/2019

10

Identifying the Keystone: The Systems Metamodel as the Foundation for the Engineering Enterprise

19

Moving the Focus from Engineering Artifacts to Engineering Systems

20

9/3/2019

11

Power at the Enterprise Level: Shared Understanding, Program Cycle Disruption, Course Correction

Customer

Chief Engineer

Hardware

Software

Safety

Reliability, Availability,Maintainability

Manufacturability

SecurityTest

Logistics

Maintenance

Operations

Environmental

Training & Personnel

Publications

Program Mgt.

Configuration Management

Systems Engineering Team

22

9/3/2019

12

Power at the Systems Level:Ensuring Consistency in Behavior and Structure

23

What does my component do?

Power at the Systems Level:Ensuring Consistency in Behavior and Structure

24

What does my component talk to?

9/3/2019

13

Power at the Systems Level:Ensuring Consistency in Behavior and Structure

25

Power in Connecting Design:Dynamic Technical Data Packages with Context

26

• Interface definitions

• Incoming and outgoing signals

• Required functionality

• Design constraints

• Associated requirements

• Test requirements

• Physical and behavioral context

• Rationale and design history

• Analytical dependencies

• Multidimensional traceability

9/3/2019

14

Achieving Seamless Analytical Simulation:Systems Engineering with Rigor

27

Connecting from Strategy through to Requirements

28

Operational SystemStrategic

System Architecture

UserNeeds

Subsystem Requirements

Concept of Operations

Stakeholder & System

Requirements

Purpose & Priorities

Credit: Spencer Tech

9/3/2019

15

Enhancing Enterprise Performance through MBSE 2.0

29

Connecting architecture and analysis

Moving from custom built to composability Leveraging patterns and architecture

Aligning through an “Authoritative Source of Truth”

Moving from Challenges to Success: Engineering Systems in the Age of Complexity

30

Advancing your organization’s

digital transformation1. Look across the silos

2. Define the as-is and to-be for scope,

context, and capabilities

3. Implement a semantically rich systems

metamodel

4. Begin the journey for your engineering

enterprise

Knowledge retention and organizational

learning enabled by a proven metamodel

. . . increasing effectiveness, reuse, and

return on investment.

Insight into interactions and dependencies,

both direct and indirect . . . equipping the

team to respond effectively in the face of

complexity and reduce mission risk.

Shared understanding of problem and

solution across the team . . . resulting in

resilient architectures and elegant

solutions informed by the wisdom of

multiple viewpoints.

Authoritative source of truth reflecting both

design and rationale . . . accelerating

programs and reducing costs by effective

thru-life knowledge management.

9/3/2019

16

Questions

David Long, ESEP

President

2270 Kraft Drive

Suite 1600

Blacksburg, VA 24060

USA

+1.540.951.3322 x107

www.vitechcorp.com

david.long@vitechcorp.com

@thinkse

31