naval information warfare center atlantic...a mission engineer perspective showing how a modeling...

NIWC Atlantic is part of the Naval Research & Development Establishment (NR&DE)

Naval Information Warfare

Center Atlantic

Digital Engineering & Model-Based Systems Engineering

Statement A: Approved for Public Release. Distribution is unlimited (28 March 2019).

Charleston Defense Contractors Association

50th Small Business &Industry Outreach Initiative

2 April 2019

David Smoak, SSTMNIWC Atlantic

SSTM for SoS Engineering

2

Why Model-Based Systems Engineering?


3

• Specifications

• Interface requirements

• System design

• Analysis & Trade-off

• Test plans

Moving from document-centric to model-centric

AirplaneATC Pilot

Request to proceed

Authorize

Power-up

Initiate power-up

Direct taxiway

Report Status

Executed cmds

Initiate Taxi

Future

Towards MBSE: A Practice in Transition

Reprinted from INCOSE Model-Based Systems Engineering Workshop, February 2010

Traditional


4

What MBSE is All AboutModels as a by-product of Systems Engineering

▼ Evolution from low-fidelity representations in documents to higher fidelity, richer representations

▼ Leveraging models for communication and analysis

▼ Developing a “authoritative source of truth” for system design and specification

▼ Ensuring consistent design and specification

▼ Providing an explicit system model to engineering teams

Today: Standalone models related through documents

Future: Shared system model with multiple views and connected

to discipline models

Reference: MBSE 101 by Elyse Fosse

“Systems Engineering focuses on ensuring the pieces work together to achieve the objectives of the whole.”

Reference: Systems Engineering Body of Knowledge (SEBoK)

MBSE Definition (from INCOSE/DAU):

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.


http://www.sebokwiki.org/

5

DoD Digital Engineering Strategy: 5 GoalsReleased June 2018


6

Navy SE Transformation Framework

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 ReviewsData Standards

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


7

Integ

rated Test

Veh

icle #1

Design & Manufacture Release

Integ

ration

Even

ts

Move rapidly to mfg. Substantiation and

insight via modeling environment

Element 4

SET Framework – 4 Elements

CDD

* 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

Re-balance as required

Mechanical Design Models

Electrical Design Models

Software Design Models

Testing Methods & Models

Analysis Tools

Single Source of Truth

Instantiate System Spec in

a model

Mission Effectiveness optimizationElement 1

Element 2Element 3

Instantiate and validate design

in models

Right-size CDD –very few KPPs, all

tied to mission effectives

MDAO*/SET-BASED DESIGN


8

SPAWAR Model-Based Systems EngineeringKey to Navy Systems Engineering Transformation

▼SPAWAR MBSE:

Formalized use of a common model to support a data driven systems engineering lifecycle

Can be used to support acquisition and budgetary decisions while ensuring interoperable designs and capabilities throughout the SPAWAR Enterprise

Common Data is the Key!

Key Components of Policy:

▼ Governance

▼ Roles & Responsibilities

▼ Process

▼ Data and tools

▼ Workforce development

Sig

ned

by

CO

MS

PA

WA

R

16 M

ay 2

018

▼Why do we need a common MBSE approach across the SPAWAR Enterprise?

Provides a consistent approach for developing and sharing engineering information across interrelated efforts

Improves product quality, reduces cycle time, enables re-use and resource efficiency once implemented

All SPAWAR organizations will “develop, maintain and use digital models for SE and SoSE activities”

Enables Digital Thread

SPAWARINST 5401.6,

MBSE Policy


https://wiki.spawar.navy.mil/confluence/display/HQ/HQ+Instructions?preview=/4327001/246848633/SPAWARINST 5401.6 508 Compliant.pdf

9

MBSE Vision


10

Model-Based Systems Engineering 2019 PLAN

MBSE is an approach that uses digital models as an integral part of the engineering technical baseline throughout

the acquisition lifecycle. As part of the Navy’s Systems Engineering Transformation effort Naval Information Warfare

Center (NIWC) Atlantic has established an MBSE Strategic Plan to build a capable workforce, collaborate with DoD

and Industry, communicate and implement an MBSE environment, which includes common Methodology, Tools,

Language, Standards and Ontology within the Command.

David Smoak, SSTM

System of Systems

Engineering

[email protected]

(843) 218-4544

WORKFORCE DEV. STRAT.

This strategy is utilized to publish a CDM,

establish training across the workforce

leveraging both internal and external

resources, provide a Community of

Interest to support organizational

expectations for implementation

GUIDEBOOK

The Guidebook describes the

MBSE-related best practices,

digital environment strategy,

business rules and resources

and is made available to NIWC

Atlantic IPTs as a reference for

structuring MBSE execution

MEASUREMENT PLAN

The Model Measurement Plan

establishes the guidance for how we

measure the publishing/consumption

of models, how projects are mapped

to the missions they support, which

programs are adopting practices,

and other measures of success.

SE

P 2

018

OC

T 2

019

MA

R 2

020

COMMS STRATEGY

The MBSE Communications

Strategy outlines the key avenues

for distributing information that

will enable the maturation and

cultural growth of the NIWC

ATLANTIC MBSE workforce.

OC

T 2

018

3

KEY MILESTONES

GOALS

METRICS

12

3

Improve fidelity of

communications across the

product lifecycle

Better deliver and sustain

operational capabilities

through model use and reuse

Develop and mature MBSE

capability and capacity

The MBSE Innovation Strategy outlines

the utilization of innovation dollars to

enhance workforce development,

facilities recapitalization (IME), and

technology transition (pilots/projects)

enabling the goals of the MBSE

technical growth area.

INNOVATION

STRATEGY

OC

T 2

018

1

MODELING BASELINE

The Model Practice Baseline

represents where NIWC Atlantic

stands today in terms of our

modeling practices, tools,

standards, sharing, storage and

capability development.

NO

V 2

018

Qualifications: OCSMP

5 0 0

Level 1 Level 3 Level 4

0

Level 2

3

COI Members

and MBSE

Practitioners

21

2

2

1

133

3

SysML Trained

with tool access

5 21

FY18 FY19

350 (O)

Successful

Pilots

0 3

FY18 FY19

3

13 (O)


11

PLANNING & CUSTOMER

REQUIREMENTS

SYSTEM REQUIREMENTS &

DESIGN

BUILD / INTEGRATE

TESTPRODUCTION & DEPLOYMENT

SUSTAINMENT• N2CS OA Phase 1• Mission Analysis EURAFSWA MOC

• USEUCOM OA Modeling• DWO Undersea Prototype• WCB/ICP 9• PEO EIS

• N2C2 3D Modeling• USEUCOM Building 2301 Renovation C4I Design

• 3d M&S CAD Lab• MC3: MBSE Implementation

• ATC Reality Capture

• Building Information Modeling - SIPH

• PMW 790 Shore Planning Activity

• C6F CM Phase 1• C5F CM Phase 1 & 2• Component Enterprise

Data Center

Digital Model

Physical System

ModelModel

Model

Model Model

Digital Twin

Low Fidelity Model High Fidelity Model

Element 4Element 1 Element 2 Element 3

19 pilot projects aligning through out the

Digital Thread

Digital Thread: Pilot Alignment

• Engineering Transformation: Live Data Advanced ANSYS Finite Element Analysis


12

MBSE Success StoryIW Mission Alignment Process

▼ Integrated modeling environment prototype managing the allocation of mission-level requirements to systems in a System of Systems

A Mission Engineer perspective showing how a modeling environment can help dynamically manage requirements across programs of record

Could be utilized for a Program/Project-level perspective and Platform-level perspective

▼ Highlighted two system capabilities within a mission

thread Integrated modeling environment facilitates the assessment of

conditions and excursions

Requirements management challenge goes up exponentially

Blue MOEs are a function of multiple interacting mission

threads, making asset and capability trades difficult to manage

without an optimization engine

▼ IW capabilities are complex and require mission-level

modeling to decompose The IW domain includes sensors, networks, battle management

aids, electronic warfare capabilities, routers, etc…

The dependencies between these capabilities and how they

contribute to mission requirements are complex

ModelCenter

Mission Engineer Perspective - SUW mission-

level requirements decomposed via SysML

Sensor System Engineer –

physics level model of sensor

attributes versus collection

requirements

Geolocation System Engineer

– physics level model of

geolocation algorithm versus

accuracy and latency

requirementsLinkages between physics level models and

mission requirements with trade-space analysis

Successfully prototyped a mission model with linkages to physics level models


13

MBSE Success StoryC&OC Model-Based Systems Engineering (MBSE)


Vision

Utilize a holistic MBSE approach in order to develop and

implement engineering products that are based upon Mission

Architectures and Analyses that detail end-to-end mission

requirements, regardless of domain, in support of understanding

and improving the range of military Operations.

Concept of Operations• Start with Operational Analysis to derive

operational requirements in order to match with

system capabilities

• Create digital linkages between requirements-

>SysML models->Digital Models

• Create holistic models of shore platforms to

include all installed systems and environmental

characteristics

• Focused on the holistic environment vice

individual systems and system capabilities

Drafted and Implementing NIWC Atlantic MBSE Approach

14

Analyze and Characterize the

Systems

• Size, Weight, and Power

• System and SoS Interfaces

(Electrical, Mechanical,

Software, Networking)

• Human Systems Integration

• Operating Environment

• RF (Antenna Propagation, Co-

Site)

Aggregate the Characteristics

into Requirements Language

Each weatherproof & ballistic

protected roof wiring pass-through

point will be capable of allowing up

to 15ea cables to pass, each of up

to ½ in diameter.

Engineer, Model and

Simulate the System

• Develop Prototype interfaces

to increase systems

modularity; and reduce

mechanical and electrical/RF

interference

• Build 3D Models (Creo,

Solidworks)

• Simulate (ANSYS Mechanical

and HFSS RF Simulation)

Rapidly Prototype

3D Printed Bracket

NIWC Atlantic is utilizing a Model-Based Systems Engineering

(MBSE) approach to enable robust requirements development

and management, new interface development, rapid

prototyping, and verification and validation of systems to

ensure timely fielding of needed capabilities.

Dynamic Trade Space

Allocation

• Allocate system components

to requirements

• Compare Multiple Options

(e.g. SWaP Analysis)

• Identify components where

requirements can be coupled

without adversely affecting

system performance (reduce

SWaP)

• Identify requirements that

must be de-coupled to enable

proper system operation (e.g.

radio and jammer)

Successful implementation of an MBSE Approach

MBSE Approach to Tactical Vehicle System Development

Requirements to Rapid Prototyping


15

MBSE Technical Exchange Series


16

Technical Discussion

▼ Technical Exchange – 21 May 2019

▼ How are you preparing for Digital Engineering Transformation?

Digital Engineering Ecosystem:

− Processes

− Integrated Tools & application

− Data sharing and integration

− Ontologies

− ETC…

Workforce Development

Acceptance of models and transfer of models vice traditional documents as CDRLs


naval information warfare center atlantic...a mission engineer perspective showing how a modeling...

Documents