MoSSEC. A standard for sharing Modelling and Simulation information in a collaborative Systems Engineering Context. MoSSEC

Transcription

1 MoSSEC Adrian Murton Airbus Operations Ltd MoSSEC A standard for sharing Modelling and Simulation information in a collaborative Systems Engineering Context

2 Agenda Why do I need MoSSEC? What is MoSSEC? MoSSEC in use What is the status of MoSSEC? Summary Page 2

3 Agenda Why do I need MoSSEC? What is MoSSEC? MoSSEC in use What is the status of MoSSEC? Summary Page 3

4 Lifecycle of System of Interest Sequential Development Concept Design Integration & Production Utilization Qualification Support Disposal V-Cycle Layers System Layer Sub System Layer Implementation Layer Requirement Definition Concept. and. Design V&V Requirement Definition Concept. and. Design Validation Verificati on V&V Qualification Integration & Test Qualification Integration & Test Implementation Maturity Iterative Page 4

5 Lifecycle of System of Interest Sequential Development Concept Design Production Utilization Integration & Qualification Support Disposal Layers V-Cycle To develop highly complex systems also Requireme Validation Qualificati nt System Layer Definition Concept Verificati. and V&V on Integrati using. different platforms on & Design Test Requireme Qualificati in different Definition locations. on Sub System Layer Concept. and V&V Integration. & Test Implementation Layer Design Implementation involves multiple partners Maturity Iterative Page 5

6 Challenges for distributed systems engineering 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 M&S M&S Tool M&S Tool M&S Tool Tool M&S M&S Tool M&S Tool M&S Tool Tool M&S M&S Tool M&S Tool M&S Tool Tool Distributed Data Modelling and Simulation data V-cycle meta-data (who what when where how why etc) Efficient sharing, synchronisation and integration Page 6 Collaboration Context Data Technical Data Collaboration Context Data Technical Data Remain Compliant with existing Standards (e.g. AP233, AP239, AP242)

7 Challenges for distributed systems engineering 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 M&S M&S Tool M&S Tool M&S Tool Tool M&S M&S Tool M&S Tool M&S Tool Tool M&S M&S Tool M&S Tool M&S Tool Tool Distributed Data Modelling and Simulation data V-cycle meta-data (who what when where how why etc) Efficient sharing, synchronisation and integration Page 7 Collaboration Context Data Technical Data Collaboration Context Data Technical Data Distributed SE challenges are applicable to in-house organisations

8 Collaboration vs Modelling & Simulation Data Modelling and Simulation data Managed in the PLM/M&S systems Exchanged with technical standards Together they enable the distributed dataset Collaborative SE context data Managed by MoSSEC Compliant Tools Exchanged with MoSSEC standard Page 8

9 Agenda Why do I need MoSSEC? What is MoSSEC? MoSSEC in use What is the status of MoSSEC? Summary Page 9

10 MoSSEC: a common approach based on standards MoSSEC provides a common approach for: Structuring the Distributed Dataset Structuring the Information Services for Dataset Management MoSSEC is built on ISO standards AP2xx AP239 Exposed As Structured By Defined By MoSSEC Business Object Model Page 10 Model Based mapping 3D Geom RM PDM etc New STEP Architecture

11 MoSSEC Business Object Model coverage Contracts Access rights Security classification Organizations Persons Expectations, Needs and Goals, Value Creation Strategy Networks Models Key Values Requirements and Approvals Assumptions and Justifications Quality Gates and Reports Templates Methods Libraries Templates Objectives Variables Objects are: Business Level Domain neutral Connections, Components Breakdowns Studies Objectives Concepts Page 11

12 Edition 1 Scope MoSSEC Presentation to NAFEMS SDMWG MoSSEC Technical Aspects: Technical Content - Proposed Scope of V1 Contracts Access rights Security classification Organizations Persons Expectations, Needs and Goals, Value Creation Strategy Studies Models Requirements/Quality Security & Trust Networks Models Key Values Templates Methods Libraries Architectures & Interfaces + supporting objects from other rows Connections, Components Breakdowns Requirements and Approvals Assumptions and Justifications Quality Gates and Reports Templates Objectives Variables Page 12

13 MoSSEC Business Object Model defined with SysML Summary View Detailed Block Diagrams AP242 etc AP239 MoSSEC Business Object Model Model Based mapping 3D Geom RM PDM etc Page 13

14 MoSSEC Unique Combination of Features Links Modelling and Simulation to the Systems Engineering Context Uses objects at a business level Efficiently shares context information Uses web services defined using the business object specification Builds on existing standards Uses New STEP Architecture mapping to AP239 and the Core Technical Capabilities Exploits AP239 usages such as Long Term Archiving. Page 14

15 Agenda Why do I need MoSSEC? What is MoSSEC? MoSSEC in use What is the status of MoSSEC? Summary Page 15

16 TeamCenter 3DExperience MoSSEC in Use: An example from TOICA What will you see? A study has already been structured and specified in the Architect s Cockpit The study objects required for Thermal analysis are sent to the TeamCenter platform with clear context, mapped to TC objects. The thermal analysis is performed and study results are attached to TC structure and sent to DS platform for the Architect to assess. Video sequence: 12 May 2016 Collaboration Results 16

17 Agenda Why do I need MoSSEC? What is MoSSEC? MoSSEC in use What is the status of MoSSEC? Summary Page 17

18 MoSSEC project - participants Project Co-chairs: Adrian Murton (Airbus Operations Ltd) Greg Pollari (Rockwell Collins) Industrial: Airbus Group, Boeing, Rockwell Collins, Honeywell, GKN Aerospace, BAE Systems Vendors: Dassault Systèmes, Eurostep, MSC Software, Siemens PLM Software Page 18

19 MoSSEC Preparatory Phase Kick-Off Meeting Jan MoSSEC Proposal Stage activities Bi-weekly phone calls Creation of MoSSEC websites (Public) private.mossec.org (Private) Preliminary Work Item submitted May 24 th 2016 International Workshop (June Toulouse) New Work Item and White Paper submitted October 4 th 2016 International ballot launched October 14 th 2016 Approval of New Work Item achieved December 9 th 2016 Page 19

20 MoSSEC White Paper (associated with New Work Item) MoSSEC Business Aspects Overview of business context Synthesis of business requirements Business use case example MoSSEC Technical Aspects Definition of technical content Development principles Interdependencies with related standards MoSSEC Project and Risk Management Deliverables Financial aspects Scheduling Page 20

21 MoSSEC: Further information MoSSEC public website Overview Resources News Links MoSSEC private website To be added to the members list contact: Page 21

22 Agenda Why do I need MoSSEC? What is MoSSEC? MoSSEC in use What is the status of MoSSEC? Summary Page 22

23 MoSSEC: Modelling and Simulation information in a collaborative Systems Engineering Context A proposed ISO standard: To improve decision making for complex products. For sharing the systems engineering context (Who, What,Where, When, How, Why) of modelling and simulation data between Internal teams/domains and Extended Enterprise Supported by industrial partners (e.g. Airbus, Rockwell Collins, Boeing, BAE Systems) and vendors (e.g. Eurostep, Dassault Systèmes, MSC Software, Siemens) Status: A first definition used extensively on EU research projects ISO New Work Item approved December 2016 Page 23

24 Page 24