Model-Based Systems Engineering Symposium 2014 Canberra, Australia Managing Complexity (Risk) using Model Based Engineering Approaches on the SEA 4000 AWD Program 27-28 October 2014 Steve Saunders FIEAust CPEng
Agenda Introduction Dichotomy Between MBCD and MBSE Complexity 101 SEA4000 Air Warfare Destroyer Prelude SEA 4000 Lessons Dynamic Tension: Enterprise vs Engineering Needs SEA 4000 Strategy Using MBCD Using MBSE Risk Viewpoint Integration Conclusions Questions Page 2
Prelude Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it. - Perlis Complexity Cognition Risk Reduction Page 3
Introduction Most Modern Systems Developments in Domain are Massively Complex Complexity as such that the Human Mind cannot analyse Must employ techniques to manage complexity Model Based approaches must enable this SEA 4000 Air Warfare Destroyer Program used as a case study But before we start, what is MBE, MBCD, MBSE?? Page 4
Dichotomy Between MBCD and MBSE Concept Definition Enterprise Viewpoints Enterprise and Business Understanding in abstracted views Program Committed Costs driven by few Key Parameters & Relationships Technical Viewpoints Engineering Profession Trained in facts/laws - Details Systems Engineering Page 5
Complexity 101 SEI/NDIA Report CMU/SEI-2012-SR-009 Complexity Proportional to Challenge and Risk of Requirements Error Page 6
Complexity 101 Defense Acquisition University 1993 Total Ownership Cost Errors in Requirements Total Ownership Cost highly Sensitive to Errors in Requirements Page 7
SEA4000 Air Warfare Destroyer Prelude Delivering one of the world s most capable multipurpose warships The AWD Alliance, responsible for delivering three world-class warships to the RAN. The Hobart Class destroyers will be the most capable surface combatants ever operated by the RAN, able to assume a leading command and control role with ADF and coalition forces. As Mission Systems Integrator Raytheon Australia is: Developing the Hobart class combat system architecture; Developing the Hobart class combat system design; Developing the integrated support systems; Integrating non-aegis elements of the combat system; and Providing project management and systems engineering services. Page 8
SEA 4000 LESSONS Photos Courtesy AWD Alliance 9
Dynamic Tension: Enterprise Level vs Engineering Level Key Stakeholders need big picture concepts Use of appropriate viewpoints of the data Considerations of required visualisations Considerations for current (Build phase) and through-life (Support phase) Think from the Stakeholder s point of view, not the modeler's Engineers trained to capture accurate data Accurate data compounds complexity problem Use of appropriate MBE tools to ensure consistency and accuracy of the data set MBE tools encourage capture of detail How can we Meet Stakeholder Needs but Preserve Data Accuracy? Page 10
Dynamic Tension: Enterprise Level vs Engineering Level Compliance Viewpoint Present Data for Intended Audience Many, Many Views Required Model Representation of AWD System Page 11
Dynamic Tension: Enterprise Level vs Engineering Level MBSE Model Accurate, Consistent, Engineering Notations Visualisation Layers Adapted for Enterprise Stakeholders Page 12
AWSS 10 VSR 10-01 IFF 10-02 HSR 10-03 SSRS 10-04 EO/IRST 10-05 AWS 20 C&D 20-01 ADS 20-02 WCS 20-03 ACTS 20-04 ORTS 20-05 SPYCP 20-06 CSSE 20-07 LSE 20-08 ACI 20-09 AWWS 30 VLS 30-01 GWS 30-02 SSMS 30-03 FCS 30-04 VSRD 40 VSRAD 40-01 VSRSD 40-02 FP 40-03 Not Used 40-04 USW 50 USWC 50-01 HMS 50-02 VDS 50-03 AWSS 10 VSR 10-01 IFF 10-02 HSR 10-03 SSRS 10-04 EO/IRST 10-05 AWS 20 Interface Level C&D 20-01 2 2 0 To Be Defined - Waiting on Product Selection ADS 20-02 2 2 2 2 2 1 Human In The Loop - Procedural WCS 20-03 2 2 2 Existing Interface (No Changes) ACTS 20-04 2 2 2 2 2 3 Simple Gateway Conversion Between OTS Components ORTS 20-05 2 2 2 2 2 2 4 Minor Change to either/both ends to Interafce SPYCP 20-06 2 2 2 2 2 5 Complex Gateway Conversion Between OTS Components CSSE 20-07 6 New Interface to FMS or Complex Product Interface Change LSE 20-08 7 Future Integration ACI 20-09 AWWS 30 VLS 30-01 2 GWS 30-02 2 4 2 2 2 SSMS 30-03 6 7 FCS 30-04 2 2 VSRD 40 VSRAD 40-01 2 VSRSD 40-02 2 FP 40-03 Not Used 40-04 USW 50 USWC 50-01 HMS 50-02 2 VDS 50-03 0 OTST 50-04 1 TDS 50-05 7 DDS 50-06 UCS 50-07 MOAS 50-08 EWS 60 EWC 60-01 MW ES 60-02 2 2 2 2 0 SMW ES 60-03 0 CML 60-04 0 MW EA 60-05 0 0 NULKA 60-06 0 ASMWD 60-07 7 CIS 70 RF 70-01 INTCOM 70-02 2 2 7 7 0 0 CIS MGMT 70-03 0 0 CEC 70-04 2 2 DLINK 70-05 2 2 0 0 0 AVS 80 HOP 80-01 HLA 80-02 NAV 90 IBS 90-01 4 2 2 0 INS 90-02 2 2 0 2 2 4 4 2 2 4 0 2 2 4 4 0 NAVSEN 90-03 0 SMM A0 SMMS A0-01 1 4 0 0 0 SMMC A0-02 0 OBTS B0 OBT CONT B0-01 2 2 2 0 OBT SIM B0-02 OBT STIM B0-03 ATI C0 ATIFW C0-01 3 3 3 3 3 7 0 4 0 ASWCS C0-02 0 2 0 EWSCS C0-03 0 2 0 EXT XX-XX 0 0 0 0 0 OTST 50-04 TDS 50-05 DDS 50-06 UCS 50-07 MOAS 50-08 EWS 60 EWC 60-01 MW ES 60-02 SMW ES 60-03 CML 60-04 MW EA 60-05 NULKA 60-06 ASMWD 60-07 CIS 70 RF 70-01 INTCOM 70-02 CIS MGMT 70-03 CEC 70-04 DLINK 70-05 AVS 80 HOP 80-01 HLA 80-02 NAV 90 IBS 90-01 INS 90-02 NAVSEN 90-03 SMM A0 SMMS A0-01 SMMC A0-02 OBTS B0 OBT CONT B0-01 OBT SIM B0-02 OBT STIM B0-03 ATI C0 ATIFW C0-01 ASWCS C0-02 EWSCS C0-03 EXT XX-XX Integration of Visualisations 1. Direct Viewpoints into the Model e.g OV-5b 2. Model data directly populates Visualisation (VISIO and EXCEL) e.g. SV-3 3. No Tool Integration; Architect abstracts concepts e.g. OV-1 Page 13
SEA 4000 Phase 2 MBSE dd Page 14
SEA 4000 Phase 2 Using MBCD dd Page 15
SEA 4000 Phase 2 and MBSE dd Stakeholder Collaboration With Consideration for Full Life-Cycle / Evolution Paths Output is Balanced Requirements! Fit to COTS Systems Architecting Common Risk Focus (All Aspects) System Development From Best For Program Specification Page 16
Examples from AWD MBCD Operational Vignettes Risk Hybrid model SysML Notation SysML (for OV-5b, SV-5a, SV-4) augmented by VISIO, Excel, Powerpoint Visualisations Concept Visualisations Recognises Concept Stakeholders Needs Non-Integrated Views Managed by System Architect Page 17
Examples from AWD MBSE Majority within MBSE Environment SysML, though some Visualisations Remain Visualisations cover SysML Notation Interface Risk Profile, Technology Forecasts, Test Sequencing, Certification Boundary, Security Viewpoints etc. Non-Integrated Views Managed by System Architect Supporting Visualisations Page 18
Risk Viewpoint Integration Risk Minimisation is a Common Denominator Compliance Risk Technology Readiness Risk Regulatory Risk Integration Risk Sustainment Risk Security Risk Certification Risk Cost Risk Etc Focus Team on Risk Vector Mitigation as a Common Goal Page 19
Conclusions Modern Systems are COMPLEX Surpasses Human Cognitive Ability MBE must enable SIMPLIFICATION and Addition of DETAIL Simplification is HARD, the results are PROFOUND MBCD tools must support RAPID architectural EXPERIMENTS Engineers like DETAIL, keep a reign on them! Current MBE Tools Unable to provide all viewpoints needed Know what to model and what not Think of the Output not the Model Focus Team on Risk Vector Mitigation as a Common Goal It is all about a BALANCE, Appropriate Viewpoints on the Data Set and RISK VECTOR MITIGATION Page 20
Managing Complexity (Risk) using Model Based Engineering Approaches on the SEA 4000 AWD Program Questions? Steve Saunders Raytheon Australia Page 21
Acronyms ADF Australian Defence Force AWD Air Warfare Destroyer (SEA 4000) CDG Capability Development Group COTS Commercial Off-the-Shelf DoDAF Department of Defense Architecture Framework MBCD Model Based Concept Design MBE Model Based Engineering MBSE Model Based Systems Engineering OMG Object Management Group OV-5b DoDAF Operational Activity Model RAN Royal Australian Navy SV-4 DoDAF System Functionality Description SV-5a DoDAF Operational Activity to System Function Traceability Matrix SysML OMG Systems Modeling Language Page 22
About the Author Steve Saunders is an Engineering Fellow of Engineers Australia and for Raytheon Australia. He received his Bachelor of Electrical Engineering, from the University of Technology Sydney (UTS) with first class Honours in 1990. He has worked with Rockwell International, Boeing Australia and now Raytheon Australia on Australian Defence projects in various Systems Engineering Management, Requirements Development, Architecture, Design and Test roles. He is an OMG recognised Raytheon certified architect having completed the Raytheon Certified Architect Program in 2005. Steve has been involved in the Royal Australian Navy s Air Warfare Destroyer Program since 2005 as the Combat System Chief Architect working in phase 2 of the Program to establish the Combat System architecture. He is now the AWD Combat System Chief Engineer and Combat System design authority. Page 23