Insights from Large Scale Model Based Systems Engineering ...elysiuminc.com/gpdis/2016/Tuesday-Presentations/Boeing-Mark... · Why is Model Based Systems Engineering Important at

BOEING is a trademark of Boeing Management Company

Copyright © 2016 Boeing. All rights reserved.

Copyright © 2014 Northrop Grumman Corporation. All rights reserved.

GPDIS_2016.ppt | 1

Insights from Large Scale

Model Based Systems

Engineering at Boeing

John Herrold and Mark Williams

Sept 25, 2016

Global Product Data Interoperability Summit | 2016




GPDIS_2016.ppt | 2

Customers and customer support in 150 countries

Total revenue in 2012: $81.7 billion

70 percent of commercial airplane revenue from customers outside the

United States

Manufacturing, service & technology partnerships with companies

around the world

Contracts with 22,000 suppliers and partners globally

Research, design & technology-development centers & programs

in multiple countries

More than 170,000 Boeing employees in 50 states and 70 countries

Boeing at a Glance





GPDIS_2016.ppt | 3

A Sample of Diverse Boeing Products





GPDIS_2016.ppt | 4

Presentation Credits

• Original presentation from:

26th Annual INCOSE International Symposium

Edinburgh, UK July 18-21, 2016

www.incose.org/symp2016

• Created by:

Robert Malone, Brittany Friedland,

John Herrold and Daniel Fogarty

The Boeing Company





GPDIS_2016.ppt | 5

1. Why is Model Based Systems Engineering Important

at Boeing?

2. What Benefit Does Boeing Derive from System

Architecture Modeling?

3. What Insight Has Boeing Gained from Large Scale

System Architecture Modeling?

4. What Support Does Boeing Require from Standards

Associations, Industry and Academia?

5. Conclusion

AGENDA





GPDIS_2016.ppt | 6

Why is Model Based Systems (MBSE)

Engineering Important at Boeing?





GPDIS_2016.ppt | 7

1. System Architecture Model

- which feed and interact with -

2. Analytic Models

3. Verification Models

MBSE Comprises More Than One Type of Model

(John C. Watson, INCOSE IW 2012 MBSE Workshop, Systems Modeling)





GPDIS_2016.ppt | 8


1. System Architecture Models

• Used to capture the system’s behavior, structure,

constraints, interfaces and requirements

• Repository-based to define product entities and their

inter-relationships

• A vehicle to define the needed analysis task including

the task’s goals, imposed constraints, and assumptions

(John C. Watson, INCOSE IW 2012 MBSE Workshop, Systems Modeling)





GPDIS_2016.ppt | 9

1. System Architecture Models

Address three major data management challenges:

• Bounding expanding data management effort

resulting from integration of complex systems

• Coordination of data management activities

within a global supplier base

• Schedule and cost risk imposed by the above






GPDIS_2016.ppt | 10

Evolution of Aerospace Systems Integration

Transmitting

LRU

Receiving

LRU

Receiving

LRU

Receiving

LRU

Receiving

LRU

Receiving

LRU

Point-to-point, 1 way

A429 Network

Up

to 2

9 D

rops

LRU

Broadcast, multiplex

LRU

LRU

LRU

LRU

Routed, multiplex

A629 Network

Integrated Modular Architecture

(IMA)

A664 Network

Interface reconciliation, bandwidth, timing,

latency analysis straightforward

Broadcasts single, 32-bit words

Transmitter owns the buses LRUs share the buses

Transmissions must be scheduled

Transmissions brokered by AIMS

AIMS


Transmissions routed through switches

Transmissions brokered by CCS

Broadcasts up to 31 wordstrings

containing up to 256 20-bit words

Broadcasts frames up to 1472 bytes,

comprising 32-bit words

CAN

LRU

RDC

Switch

CCS

429

LRU

RDC

Switch

Req

uire

men

t

Bud

gets

Latency, timing, etc

requirements parsed into

budgets and managed

Req

uire

men

t

Bud

gets

Protocol

Conversion

Signal

Routing

RDCRDC

1,2,3

1 2 3

Computation

at source

Signal

Gateway

Central

Computing



budgets and managed

Central

Computing

Benefits of IMA:

• Performance

• Weight Reduction

• System Stability

Acronyms

AIMS - Airplane Information Management System CCS - Common Core System LRU - Line Replaceable Unit

CAN - Controller Area Network IMA - Integrated Modular Architecture RDC - Remote Data Concentrator





GPDIS_2016.ppt | 11

Evolution of Aerospace Systems Integration

Transmitting

LRU

Receiving

LRU

Receiving

LRU

Receiving

LRU

Receiving

LRU

Receiving

LRU

Point-to-point, 1 way

A429 Network

Up

to 2

9 D

rops

LRU

Broadcast, multiplex

LRU

LRU

LRU

LRU

Routed, multiplex

A629 Network

Integrated Modular Architecture

(IMA)

A664 Network

Interface reconciliation, bandwidth, timing,

latency analysis straightforward

Broadcasts single, 32-bit words

Transmitter owns the buses LRUs share the buses


Transmissions brokered by AIMS

AIMS


Transmissions routed through switches

Transmissions brokered by CCS

Broadcasts up to 31 wordstrings

containing up to 256 20-bit words

Broadcasts frames up to 1472 bytes,

comprising 32-bit words

CAN

LRU

RDC

Switch

CCS

429

LRU

RDC

Switch

Req

uire

men

t

Bud

gets



budgets and managed

Req

uire

men

t

Bud

gets

Protocol

Conversion

Signal

Routing

RDCRDC

1,2,3

1 2 3

Computation

at source

Signal

Gateway

Central

Computing



budgets and managed

Central

Computing

Acronyms

AIMS - Airplane Information Management System CCS - Common Core System LRU - Line Replaceable Unit

CAN - Controller Area Network IMA - Integrated Modular Architecture RDC - Remote Data Concentrator

• Amenable to peer-to-

peer negotiations

• Somewhat

manageable in

documents, although

cumbersome

• Peer-to-peer

negotiations

impossible

• Management in

documents

untenable, modeling

necessary





GPDIS_2016.ppt | 12

CAN

LRU

RDC

Switch

CCS

Common

Motor Start

Controller

RDC

Switch

A664

Analog

CAN

A664

A664

A664

Hydraulic

Pump

Control Unit

Hydraulic

Pump

Engage

Switch

Hydraulic

Pump

Engage

Indicator

Light

Analog

Analog

Overhead Panel

Hydraulic

Pump

Engage

Switch

Hydraulic

Pump

Engage

Indicator

Light

Overhead Panel

Flight Deck

Control

Panel

Hosted

Function

Hydraulics

Interface

Hosted

Function

A653

A653

A653

Analog

A653

A664

Analog

A664

A653

A653

A664

A664

CANAnalog

Legacy ArchitectureIMA (A664)

Architecture

Supplier #1

Supplier #2

Supplier #2

Supplier #3

Supplier #4

Supplier #1

Supplier #6

Supplier #5

Supplier #4

Supplier #3

Analog

CAN

A664

A653

Multiple protocol conversions

unmanageable in documents,

modeling necessary

Illustrative Example of Digital Networks Evolution





GPDIS_2016.ppt | 13

CAN

LRU

RDC

Switch

CCS

Common

Motor Start

Controller

RDC

Switch

A664

Analog

CAN

A664

A664

A664

Hydraulic

Pump

Control Unit

Hydraulic

Pump

Engage

Switch

Hydraulic

Pump

Engage

Indicator

Light

Analog

Analog

Overhead Panel

Hydraulic

Pump

Engage

Switch

Hydraulic

Pump

Engage

Indicator

Light

Overhead Panel

Flight Deck

Control

Panel

Hosted

Function

Hydraulics

Interface

Hosted

Function

A653

A653

A653

Analog

A653

A664

Analog

A664

A653

A653

A664

A664

CANAnalog

Legacy ArchitectureIMA (A664)

Architecture

Supplier #1

Supplier #2

Supplier #2

Supplier #3

Supplier #4

Supplier #1

Supplier #6

Supplier #5

Supplier #4

Supplier #3


Data from globally distributed

suppliers unmanageable in

documents, modeling necessary

Supplier

#2

Supplier

#3

Supplier

#4





GPDIS_2016.ppt | 14

What Benefit Does Boeing Derive from

System Architecture Modeling?





GPDIS_2016.ppt | 15

A Simple Integrated System Architecture Model

What Has to

be Done

How Well

How it

is Done





GPDIS_2016.ppt | 16


Do the functions

and requirements

included in the

specification

completely and

accurately

specify the

logical

architecture

model?





GPDIS_2016.ppt | 17


Do the individual

specifications,

especially regarding

interfaces, conflict

with each other?





GPDIS_2016.ppt | 18

Avoid Test Errors Through Early System Architecture Models

Functional In

tegra

tion A

naly

sis

Num

ber

of

Inte

rface C

hanges

$

£

€

¥

$ $ $ $ $

£ £ £ £ £

€ € € € €

¥ ¥ ¥ ¥ ¥

Interface

Changes





GPDIS_2016.ppt | 19

What Insight has Boeing Gained from

Large Scale System Architecture

Modeling?





GPDIS_2016.ppt | 20

Large Scale, Highly Integrated Systems : Large, Highly Integrated Models

Functions ~2,300

Functional Data Flows ~10,000

Equipment Installations ~5,000

Data Parameters Processed by Installed

Equipment

~1,000,000

Electrical Connections Between Installed

Equipment

~9,000

Objects in Model ~ 50,000,000

(~ 3 relationships

(links) per 1

object)

Typical Digital Networks System Architecture Model Data Volume (Tens of GBytes)

~1,000

modelers Insig

hts





GPDIS_2016.ppt | 21


Effective Modeling Requires Multiple Model Views

• Diagramming view impractical to create and view 50,000,000

objects and relationships

o Time required to populate diagrams unacceptable

o Number and size of diagrams untenable

• Diagramming view impractical to analyze 50,000,000 objects and

relationships for integrity

o Human analysis of drawings too slow and error prone

• Modeling tasks shift from structure (diagrams) to detail and

analysis (querying) as model matures and grows.

• Need several model views to efficiently populate and review data:

o Spreadsheet Views

o Document Views

o etc





GPDIS_2016.ppt | 22

• Extensibility of the Modeling Environment is Essentialo Higher fidelity models allow more precise analysis

Precise analysis captures specific design problems/errors early

o Higher fidelity models require more detailed underlying data models

o Boeing digital avionics data model comprises several dozen object

types, several hundred relationship types, several thousand object attributes

• Import/Export Utilities Are Critical

• The Dataset Is The Modelo Artifacts are views of the model

o Model sharing is dataset sharing

Other Modeling Insights





GPDIS_2016.ppt | 23

Other Modeling Insights

• A Standard Modeling Notation does not Achieve Data

Integrity

o A standard data model constrained by rules achieves integrity

• Model Analysis Utilities Are Critical (Query Engine)o Detecting modeling errors reduces schedule and cost risk

o Takes longer to produce data in a database than in standard

desktop applications (point of contention among users)

o Payoff is the ability to analyze integrated model data for

completeness and correctness

o Well formed set of model analysis queries allow people not

involved in system design nor model development to detect

thousands of modeling errors daily





GPDIS_2016.ppt | 24

What Support Does Boeing Require from

Standards Associations, Industry and

Academia?





GPDIS_2016.ppt | 25

Support from Standards Associations, Industry and Academia

Standards Associationso Standard MBSE data models, and accompanying

composition/aggregation/construction rules

o Data exchange and schema standards

• Boeing participating in INCOSE WGs

• Boeing support for Standard Body WGs (Oasis, OMG, ISO)

• Potential Boeing MBSE data model paper at IS 2017

or Boeing trade study paper at IS 2017





GPDIS_2016.ppt | 26


Industry

A suite of tools based on a robust, flexible hub that

provides multiple data creation and manipulation views,

with data exchange utilities

• persistent, robust database that allows hundreds of users to modify the

models simultaneously and globally

• extensible data model that can be easily constrained by a rule set

• extensible API to support customized data creation and manipulation

utilities

• rich, natural language query engine

• industry standard import/export utility





GPDIS_2016.ppt | 27


Academia

oArchitects: MBSE tool and process architecting

established as a component of MBSE course

curricula

Use case, process and task, data model, business rule

development

oPractitioners: Modeling principles taught as part of

MBSE curricula, before the use of any particular

modeling tool or language

Develop skills in extracting data and relationships from documents

Develop skills in effectively organizing data in terms of objects,

relationships, attributes





GPDIS_2016.ppt | 28

Conclusion





GPDIS_2016.ppt | 29

• System architecture models indispensable at Boeing

• High fidelity modeling allows Boeing to accelerate

development schedules

• Large model datasets bring data management

challenges

• For large scale system architecture modeling, MBSE

community should pursue:o standard data models and modeling rule sets

o robust, capable tools; and,

o education for tool and process architects and modeling

practitioners

Conclusion





GPDIS_2016.ppt | 30

Questions

Documents

Insights from Large Scale Model Based Systems Engineering ...elysiuminc.com/gpdis/2016/Tuesday-Presentations/Boeing-Mark... · Why is Model Based Systems Engineering Important at