Systems Engineering Standards landscape - Elysium · Systems Engineering Standards landscape Jay...

Global Product Data Interoperability Summit | 2015

BOEING is a trademark of Boeing Management Company

Copyright © 2015 Boeing. All rights reserved.

Copyright © 2014 Northrop Grumman Corporation. All rights reserved.

GPDIS_2015.ppt | 1




GPDIS_2015.ppt | 1

Systems Engineering

Standards landscape

Jay GanguliBoeing





GPDIS_2015.ppt | 2

Agenda

• Context & approach

• The dimensions of analysis

• The sources of information• SEBok, NSF, INCOSE 2025 SE Vision

• Overlap of some standards.

• Implications of some current directions• FutureSTEP, MoSSEC, AP209

• Future influencers..disruptors..• BigData- Distributed Graph databases, InMemory computing

• Research via NSF Systems Engineering grants.





GPDIS_2015.ppt | 3

• The problem…

• Initial discussion at PDES Inc.• PDES Sytems Engineering team

• Landscape….needs to show multidimensional data.

• Implementation techniques …OSLC…REST, Linked Data

• Product Life Cycle

• SysML, AADL, MoSSEC, AP233, ReqIF, FMI, Modelica………etc

• Standards bodies…PDES..INCOSE, OASIS, ProSTEP..OMG

• How choosing one path…restricts/ opens up other options

• Consultancy with Industry Subject Matter Experts• Sandy Friedenthal- “Father of SysML”

• Axel Reichwein - Koneksys

• Nigel Shaw – Eurostep

• Garry Roedler- Lockheed Martin Fellow, INCOSE Fellow and Founder Recipient;

Context & Approach

SysML

AP233

OSLC

PLCS

AP242

AP209

MoSSECAADL

XML

WSDL

REST

WADL

SOAP

Linked

Data

PLCS

Lib

HTTP

ReqIF





GPDIS_2015.ppt | 4

A Review of Systems Engineering Standards and Processes (2008)

by Guey-shin Chang , Horng-linn Perng , Jer-nan Juang

Dimension - Evolution over time





GPDIS_2015.ppt | 5

2025- Sys Engg Vision -INCOSE–

S.Friedenthal et al..

Dimension: The Use Case





GPDIS_2015.ppt | 6

2025- Sys Engg Vision -INCOSE–S.Friedenthal et al..

Dimension: The Stakeholder view





GPDIS_2015.ppt | 7

Dimension : The SE Bok





GPDIS_2015.ppt | 8

Dimension : Layered Standards

Figure 1.9 – from Sandy’s Book





GPDIS_2015.ppt | 9

Standards and their Product life cycle scope.

SOURCE: Analysis of PLM Standards for US Army- NIST

Dimension : Standards influencing each other





GPDIS_2015.ppt | 10

2025- Sys Engg Vision-INCOSE –S.Friedenthal et al..

Dimension : Theoretical foundations of Systems EngineeringThe INCOSE Vision





GPDIS_2015.ppt | 11

NSF – Theoretical Framework for SysEng – Paredis

Dimension : Theoretical foundations of Systems EngineeringNational Science Foundation –Systems Science





GPDIS_2015.ppt | 12


Dimension : Complexity…and its roots





GPDIS_2015.ppt | 13

Dimension : Consortia / Business priorities and drivers





GPDIS_2015.ppt | 14

Used with permission from Garry Roedler, LM Fellow / Engineering Outreach Program Manager

INCOSE Fellow and Founder Recipient; IEEE Golden Core

.





GPDIS_2015.ppt | 15

Growing collaboration

Used with permission from Garry Roedler, LM Fellow / Engineering Outreach Program Manager

INCOSE Fellow and Founder Recipient; IEEE Golden Core

.





GPDIS_2015.ppt | 16

Dimension : Churn in STEP





GPDIS_2015.ppt | 17

Dimension : Churn in STEP….Requirements domain





GPDIS_2015.ppt | 18

STEP AP209 & MoSSEC

Used with permission from Nigel Shaw, Director EuroSTEP





GPDIS_2015.ppt | 19

STEP AP209 & MoSSEC






GPDIS_2015.ppt | 20

AP209 & MoSSEC






GPDIS_2015.ppt | 21

Challenges for distributed systems engineering : MoSSEC

Collaboration Services

Remain Compliant with existing

Standards (e.g. AP233, AP239, AP242)

• Distributed Infrastructure • Secure Collaboration for:

– Locations

– Organisations

– Software Platforms

• Distributed Processes• Multitude of Modelling and

Simulation tools

• Simulation driven design changes

traced and under PLM control

• Distributed Data• Modelling and Simulation data

• V-cycle meta-data – (who what when where how why etc)

• Efficient sharing,

synchronisation and integration





GPDIS_2015.ppt | 22

Collaboration vs Modelling & Simulation Data

• Modelling and Simulation data • Managed in the PLM/M&S systems

• Exchanged with technical standards

• Collaborative SE context data • Managed by MoSSEC Compliant Tools

• Exchanged with MoSSEC services

• Together they enable the distributed dataset

Technical standards:

e.g. AP242, AP209MoSSEC





GPDIS_2015.ppt | 23

MoSSEC & AP233, and PLCS





GPDIS_2015.ppt | 24

Evolution of “interoperability” in the Product Data space (STEP context)

The primary driver for interoperability in the STEP world was aimed at building new APs faster.





GPDIS_2015.ppt | 25

STEP main High Level capabilities

STEP Future Architecture Workshop - 29-30 June 2015

- Toulouse

25

STEP on the Lifecycle





GPDIS_2015.ppt | 26

26

Multi-layered information models..based on Standards –

Replicating the PLCS experience

STEP Future Architecture Workshop - 29-30 June 2015

- Toulouse





GPDIS_2015.ppt | 27

FutureSTEP..recent developments





GPDIS_2015.ppt | 28

FutureSTEP..recent developments





GPDIS_2015.ppt | 29

Dimensions- what does a Pragmatic user need?

• Scope of standards• Ease of adoption by vendors + users + developers

• Vendors attends standards mtgs…• Existing tool support• Existing adoption• Alignment with technical trends – Linked data. Is the std

compatible with linked data, communication protocol• Documentation quality, accessible, examples to get started• Stds :

• Std ways to access info: AP233, SysML, AADL, FMI, Modelica, Simulink,

• Std protocol: OSLC is domain independent..• Quantify the complexity…the number of relationships• Assess the impact..is it in a domain used by 90% of engineers.• W3C: Dublin Core, RDFontologies,

Courtesy : Axel Reichwein - Koneksys





GPDIS_2015.ppt | 30

OSLC

http://www.w3.org/DesignIssues/LinkedData.html





GPDIS_2015.ppt | 31

OSLC & STEP… possible patterns of interaction





GPDIS_2015.ppt | 32

OSLC & SysML experience

Courtesy : Axel Reichwein, Koneksys





GPDIS_2015.ppt | 33

OSLC Tool Interoperability






GPDIS_2015.ppt | 34

OSLC Resource and Resource Shapes






GPDIS_2015.ppt | 35

One way to think of the landscape





GPDIS_2015.ppt | 36

CongaConfiguration Optimisation of Next Generation Aircraft

The Positive influence of Consortia Projects: UK’s CONGA:

PLCS/MoSSEC/OSLC

“. The solution was to create BDA requirement objects on the

collaboration hub and embed the link to the DOORS requirement inside.

Using the link to the delegated UI it was possible for existing consumers

of BDA resources to access the requirements in DOORS without having

to develop their own OSLC consumer adapters. “

“

The aim was to identify

how requirements in OSLC

could be made available to

other partners.

The other tools in the tool

net were already BDA

compliant and so a re-work

to OSLC consumers

wasn’t desirable . “

( Source: OSLC Community Update – OSLC with PLCS and MoSSEC ( June 10,2015

)





GPDIS_2015.ppt | 37


The need to Collaborate..





GPDIS_2015.ppt | 38

People…





GPDIS_2015.ppt | 39

• Standards Lead At INCOSE( Ken Zemrowski) & Sandy Friedenthal

working on 2 near term task

• Focus on developing a domain specific SE vision for automotive

• INCOSE will encourage other domains to do something similar.

• NSF – Theoretical Framework for SysEng engagement. The

standards roadmap is critical here too.

• INCOSE engagement with standards bodies like PDES, OASIS- OSLC

• ‘MBSE for OSLC ‘working group is working with OSLC. (Mark

Sampson and Sandy F – Co-Chairs)

• ‘Tools Interop WG’ is also collaboration on standards .

• INCOSE’s new strategy ‘Accelerate the Transformation to a MB

Discipline’ has a ‘Technical objective that requires engagement with other

standards bodies.

• MBSE wiki would be a good place to show links to other standards

working groups

People…. INCOSE & PDES

http://www.omgwiki.org/MBSE/doku.php#affiliated_incose_groups





GPDIS_2015.ppt | 40

• ALM-PLM working group leaders invited to

FutureSTEP sessions• Axel Reichwein to present OSLC view at PLCS meet.

• Importance of Standardizing Interaction patterns and

Webservices

• Linked Data…Resource Shapes..

• Could provide early clues on Interoperability needs for

STEP.

People ..FutureSTEP and OSLC-ALM-PLM

http://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0CAcQjRxqFQoTCJrBrvC6-scCFUo3iAoda5EFRQ&url=http://freshdev4.com/strategylab/are-you-too-busy-read-this/&bvm=bv.102537793,bs.1,d.aWw&psig=AFQjCNGS8KZAVon2dBeeOq3PKDer1Y8YiA&ust=1442455298173522

http://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0CAcQjRxqFQoTCJrBrvC6-scCFUo3iAoda5EFRQ&url=http://freshdev4.com/strategylab/are-you-too-busy-read-this/&bvm=bv.102537793,bs.1,d.aWw&psig=AFQjCNGS8KZAVon2dBeeOq3PKDer1Y8YiA&ust=1442455298173522





GPDIS_2015.ppt | 41

OSLC Community Update ( June 10,2015 )





GPDIS_2015.ppt | 42

ProSTEP and OSLC





GPDIS_2015.ppt | 43

BACKUP





GPDIS_2015.ppt | 44

Analysis results

• Performance

• Preferred

architectures

Architecture instances

• Applications

• Platforms

• Features

• Properties, flows

Transformation: SysML to/from AADL

44

uc [Package] FVL_Platform [Data Correlation Use Case Diagram]

Data Correlation System Boundary

Acquire SourceTracks

Acquire PlatformPosition

Publish CorrelatedTracks

Correlate TrackData

Initialize andShutdown

SA_Data_MgrDCFM

Health_Monitor_Mgr

sd [Package] FVL_Platform [Data Correlation seq]

Acquire Source Tracks

Ref

Acquire Platform Position

Ref

Publish Correlated Tracks

Ref

loop

Acquire Source Tracks

Ref

Acquire Platform Position

Ref

Publish Correlated Tracks

Ref

loop

FVL_SystemContext.hmm

FVL_SystemContext.dcfm

Uninitialized

Uninitialized

Initialized

Publish Tracks

shutdown

initialize

DrainSourceTrackQueue

applyCorrelationAlgorithm

FVL_SystemContext.sdm

dcfm1

sdm_Correlated_Track_ID

sdm_CorrelatedTrack

sdm_SourceTrack

hmm_PlatformId

sdm_PlatformPosition

sdm_PlatformId

sdm1

dcfm_Correlated_Track_ID

dcfm_CorrelatedTrack

dcfm_SourceTrack

dcfm_PlatformPosition

dcfm_PlatformId

hmm1

dcfm_PlatformId

SysML (Rhapsody)

AADL Profile

• Ensures consistency between the system model and domain models

• AADL profile enables import of SysML elements into AADL model.

AADL (OSATE)

Systems Engineering Standards landscape - Elysium · Systems Engineering Standards landscape Jay...

Documents

Transcript of Systems Engineering Standards landscape - Elysium · Systems Engineering Standards landscape Jay...