Towards a European Roadmap for Fostering OSLC Adoption in Systems Engineering Development? December 9, 2015 Frédéric Loiret KTH / OFFIS Frédéric Loiret – KTH / OFFIS An Example of Large European Project: CRYSTAL “Seamless Life-Cycle Collaboration for Safety-Critical Systems Engineering” } } } } } } 68 partners from 10 countries $87M total budget European key players from different industrial domains Large companies developing embedded systems act as technology users and use case providers Large tool providers, SMEs and researchers as technology providers 4 Industrial Sectors (Aerospace, Automotive, Rail, Healthcare) 2 Frédéric Loiret – KTH / OFFIS Agenda • Interoperability related activities in large European projects • Towards the establishment of a sustainable structure for interoperability specifications (in CP-SETIS) • Some technical challenges we are facing with OSLC • Some dissemination material from CRYSTAL • KTH contributions to the Lyo OSLC reference implementation 3 Frédéric Loiret – KTH / OFFIS Today’s situation in industrial companies Industrial Workflows • • Fragmented IT High maintenance costs Tool Layer Frédéric Loiret – KTH / OFFIS !! !! • High manual effort to handle data • Impact on quality and safety The CRYSTAL Vision Industrial Workflows Users get better ways of working Enable New Engineering Methods • Open Integration Platform Tool Layer Frédéric Loiret – KTH / OFFIS • Standardized Interoperability Specifications (IOS) Connect tools to expose & link data IOS History & Evolution } Pre-Project Phase (from 2010) ◦ Safe, iFEST, CESAR, MBAT projects Proof of concept, OSLC as one basis, Extensions to Testing & Analysis } Public Demonstrators CRYSTAL Project Phase (until mid 2016) ◦ Extension of IOS to additional concepts & standards ◦ Fostering adoption of IOS by Tool Vendors and Industrial End-Users } Proprietary Demonstrators Extended Public Demonstrators After Project Phase ◦ Coordination Action (H2020 CP-SETIS) ◦ new projects (ITEA3 ASSUME, ECSEL ENABLE-S3) Frédéric Loiret – KTH / OFFIS Industrial EndUser Application CRYSTAL High Level IOS Architecture Data Integration across Tools, Data Repositories and Engineering Phases e.g., Traceability across the whole product development lifecycle Interoperability Specification (IOS) Examples: • Heterogeneous co-simulation • Real-Time Data Measurement and Calibration • etc. <consists of> Non-Lifecycle IOS Examples: • IOS Variability Management • IOS Safety Management • etc. Lifecycle IOS <consists of> <consists of> NLC Domain OSLC Based Specification 1 à Follow the process advocated by OSLC for specifying domains CRYSTAL IOS Lifecycle Extension <adopts> Engineering Standard Examples: • FMI • ASAM-ODS • ISO26262 • AUTOSAR / EAST-ADL • ReqIF • STEP • etc. Frédéric Loiret – KTH / OFFIS 2 • OSLC Core specs <may define> 3 Bridges for Integration with Lifecycle IOS 7 Examples of “OSLC Domains”: • OSLC RM Spec, • OSLC QM Spec, • etc. Example from CRYSTAL: • Full-fledge traceability support between OSLC Requirements, Design Artifacts, and Simulation Results generated by FMI • Autosar to OSLC bridge • ReqIF to OSLC bridge Current Content of the CRYSTAL IOS • Lifecycle IOS • Adopted from OSLC • OSLC Core, CCM, TRS • OSLC RM, AM, QM, Asset, Change Request Domains • CRYSTAL extensions to existing Domains • RM, AM (extensive ones), QM • New Domains • Knowledge & KPIs Management • Formal Requirement Management • Verification & Validation • Variability Management • Safety & Risk Management • New Domains from other projects • Human Factor Modeling (from the HoliDes project) • AM extensions (from ASSUME/Scania) • Non-Lifecycle IOS • FMU/FMI standard for co-simulation • Bridges (Public release) • AUTOSAR / EAST-ADL to OSLC • OMG ReqIF to OSLC 8 Frédéric Loiret – KTH / OFFIS Context and current situation • Current situation is characterized by a wide variety of activities, which are only partly coordinated • Several follow-up projects building and extending the IOS • New European projects emerging that aim at interoperability solutions for development tools • Interoperability related projects are step-by-step converging towards a common definition of the IOS 9 Frédéric Loiret – KTH / OFFIS Challenges 1. Organizational & Strategical • A common vision and mission, shared by all major stakeholders, for supporting lifecycle data and tool interoperability for CPS Engineering has to be established Aligning the as yet only partially coordinated European IOS-related activities and paving the way for establishing the IOS as a major set of standards in CPS Engineering. • 2. Technical • • Coordination of IOS cross-project extensions (complementary & orthogonal concerns) A clear bridge has to be defined between the on-going definition of the IOS and other wide spread Interoperability and Engineering Standards commonly used by European developing organizations • related to “Data Exchange” besides “Data Integration” 10 Frédéric Loiret – KTH / OFFIS CP-SETIS – Coordination Action kick-started in 2015 Goals • Align all IOS related forces within Europe to support a common IOS Standardization Strategy, aiming at formal standardization process of the IOS • The definition and implementation of sustainable IOS Standardization Activities supporting both, formal standardization of ‘stable’ IOS versions as well as extensions of IOS, if possible within existing structures that survive the lifespan of single projects 11 Frédéric Loiret – KTH / OFFIS CP-SETIS WPs & Possible Implementation • Past Project CESAR • • • • • • • Past Project iFEST Past Project MBAT CRYSTAL EMC2 Defines IOS strategy WP2 Be focal point and point of Identification of Cross-Projects IOS contact for all IOS related Challenges activities Define stable IOS Versions for WG Standardization ARTEMIS-IA Evaluate results from Working Groups existing projects WP1 Organize cross-project Model of sustainable IOS workshops Standardization Activities Give recommendations to projects • Promotes Standards to tool Incubate new projects vendors and end users • Evaluate existing standards • Negotiates cooperation with standard WP0 organizations Management and • Create WGs in Standardization bodies Coordination • Assign IOS label to standards Future Project Future Project Projects develop proposals (specs) for IOS extensions / IOS modifications / new standards Tool User WP3 Fostering IOS Support and Industrial Acceptance Tool User WP6 Promotion & Dissemination WP5 Standardization SRA WP4 IOS Standardization Roadmap Tool Provider Tool Provider RO ASAM Calibration Data Management WG Network Configuration WG Frédéric Loiret – KTH / OFFIS OASIS Configuration Management WG Requirements Management WG OMG … … RO Partners Core Partners Associated Partners (initial list to be extended) Austrian Institute of Technology (AIT), Austria ABB, Sweden ARTEMIS-IA Industrial Association, Europe Airbus, France, Germany, UK AVL, Austria ASAM, Europe Royal Institute of Technology (KTH), Sweden Daimler, Germany OFFIS, Germany Volvo, Sweden SafeTRANS, Germany (coordinator) European Telecommunications Standards Institute (ETSI), Europe Siemens, Germany Thales, France à More are being invited to join 13 Frédéric Loiret – KTH / OFFIS Agenda • Interoperability related activities in large European projects • Towards the establishment of a sustainable structure for interoperability specifications (in CP-SETIS) • Some technical challenges we are facing with OSLC • Some dissemination material from CRYSTAL • KTH contributions to the Lyo OSLC reference implementation 14 Frédéric Loiret – KTH / OFFIS Some Technical Challenges of OSLC specs • Specification / Guidelines for handling Data Exchange scenarios • Via engineering standards • Via company-specific “OSLC domains” • Via basic “raw” file exchanges • The “Magic Triangle” • Version / Configuration / Variants • Authentication & Access Rights Management not standardized 15 Frédéric Loiret – KTH / OFFIS Towards a new distinction between normative and informative OSLC specs? Just a brainstorming! Already within the scope of OSLC/OASIS Normative Capabilities OSLC Core Linked-Data Platform for RDF, HTTP C.R.U.D. RESTful operations, OSLC-defined Resources, OSLC Core Resource types Not yet formally in the scope of OSLC/OASIS Notifications? Users Manag.? Access Control? Authentication? OSLC CCM Version & Configuration Management VM? Variability Management OSLC DUI & Resource Previews Delegated User Interface Dialogs VPM? Viewpoint Management ? OSLC Reporting Informative Capabilities OSLC Automation Support OSLC Asset Manag. OSLC Quality Manag. OSLC Product Definition OSLC Estimation & Measurement OSLC Arch. Manag. Detailed Arch. Manag. Formal Req. Manag. Human Factors Formal Analysis … etc … 16 Frédéric Loiret – KTH / OFFIS Knowledge Manag. Safety & Risk Manag. FMI/FMU Mapping Company-Specific Models … etc … Agenda • Interoperability related activities in large European projects • Towards the establishment of a sustainable structure for interoperability specifications (in CP-SETIS) • Some technical challenges we are facing with OSLC • Some dissemination material from CRYSTAL • Public Use Cases • Generic Engineering Methods • KTH contributions to the Lyo OSLC reference implementation 17 Frédéric Loiret – KTH / OFFIS Purpose of the CRYSTAL Public Use Cases • Describe typical engineering challenges with respect to (tool) interoperability for specific industrial sectors • In particular for Aerospace and Automotive • Perform prototyping of IOS concepts • Facilitate the presentation of CRYSTAL results in publications without facing IPR concerns • Documented Engineering Methods (or “Integration Scenarios”) and their mapping onto IOS concepts • Engineering Models available Andreas Mitschke – Airbus Group Frédéric Loiret – KTH / OFFIS 18 Example of the CRYSTAL Aerospace Public Use Case Definition of De-icing System for Regional Turboprop Aircraft Clustering of Engineering Methods System Design and Analysis related RTP related Analyze Requirements Set-up of SEE, including user rights Define Domain Model Extend for FMU Export Process Management Verify Design Against Requirements Heterogeneous Simulation Trade-Off Analysis Generate Fault-trees / TBD Add Safety Product Line Engineering Add Feature “Common Services” related Traceability/ Change Impact Analysis Search Data Test Support Andreas Mitschke – Airbus Group Frédéric Loiret – KTH / OFFIS Provide Specification Support collaborative working Maintain Consistency between multi-viewpoint models 19 Put all data under Configuration Control Versioning / Archiving Envisioned Prototype for Implementation De-Ice System Concepts Definition De-Ice System Functional Models De-Ice System Requirements Functional Models Requirements Database Connectors based on open standards Connectors based on open standards tors Connec pen on o based rds n sta da Physical behavior simulation database Conceptual Architecture Models Connectors based on open standards De-Ice System DATA Physical Behavior Models Traceability Links Application Lifecycle management C ba onn se ec sta d on tors nd op ard en s Communication via Secure Internet or Intranet Co bas nnec tors ed sta on op nda e rds n … and … andD/B many many more more DATA DATA Connectors based on open standards DATA Safety Analysis Database DATA Andreas Mitschke – Airbus Group Frédéric Loiret – KTH / OFFIS Connectors based on open standards Connectors based on open standards DATA Digital Mock-up DataBase 20 Concept Trade-off analysis D/B DATA rs cto n nne n ope o C o ed rd s bas tanda s DATA Product Lifecycle Management Developing IOS and generic Engineering Methods in CRYSTAL Describe Use cases IOS needs ß time Define engineering methods and artefacts exchanged gEMs Apply generalised engineering methods Consolidate engineering methods across Use cases Evaluate improved tool Validate Engineering Method Use of system engineering environment Sytze Kalisvaart – TNO Frédéric Loiret – KTH / OFFIS 21 Collect IOS candidates Define IOS architecture Create Interoperability specification Create IOS tool adapters CRYSTAL Generalised Engineering Methods • How to use IOS for a typical work process? • • • • Sample generalised Engineering Methods show how to map to IOS Cross-domain engineering steps and engineering functions Categorised according to ISO 15288 Based on Engineering methods collected in Use cases • Current gEMs being developed in CRYSTAL • • • • • • Tests coverage of requirements Simulation management Version & configuration management Safety management Certification (draft) Drafts: Variability Management / ReqIF-OSLC / Trade-off Analysis Sytze Kalisvaart – TNO Frédéric Loiret – KTH / OFFIS 22 Agenda • Interoperability related activities in large European projects • Towards the establishment of a sustainable structure for interoperability specifications (in CP-SETIS) • Some technical challenges we are facing with OSLC • Some dissemination material from CRYSTAL • KTH contributions to the Lyo OSLC reference implementation 23 Frédéric Loiret – KTH / OFFIS OSLC Reference Implementation / Community Building • Building up momentum around Lyo should be fostered! Vocabulary based on Linked Data - An Eclipse Graphical User Interface • KTH contributions so far 07/12/15 17:55 • OSLC4J code generators (part of Lyo) • Modeling support for Linked Data Variability (sc_var) Software (sc_sw) hierarchy: String [hasSubComponent] min: String 1 family: String max: String SoftwareComponent releaseDate: String step: String dcterms:subject: String dcterms:description: XMLLiteral hierarchy: String generation: String version: String Reads/Owns: CalibrationPara... allowedRange: Range associatesWith: RtdbVariable value: Integer [Reads/Owns] 1 owns: RtdbVariable unit: String 1 [hasSoftwareComponent] hasSubComponent: SoftwareComponent [owns] hasSoftwareComponent: SoftwareComponent family: String releaseDate: String generation: String version: String Range CalibrationParameter ECUSoftware OSLC EMF Meta Model allowedValues: KeyValuePair 1 1 [Reads/Owns] [owns] Local: allowedRange dcterms:subject: String scc:dataType: String 1 min: String max: String step: String Local: allowedValues 1 [has_interface] RtdbVariable 0..* KeyValuePair dcterms:subject: String dcterms:description: XMLLiteralLocal: allowedValues dcterms:subject: String 0..* dcterms:description: XMLLiteral scc:dataType: String value: Integer unit: String [has_interface] 1 Communication (sc_com) [has_io_port] Dublin Core (dcterms) 1 1 CommonID subject: String [associatesWith] dcterms:identifier: String Local: hasID session: String isOperationalData: Boolean 1 isFreezeFrame: Boolean Diagnostic Communication Interface type: String identifier: String description: XMLLiteral 1 communication interface dcterms:identifier: String segment: String [associatesWith] [has_message] Message [is_gatewayed] 1 1 [uses_port] Automatic Generation dcterms:subject: String priority: String sourceAdress: String: String destinationAddress: String: String period: String timeout: String type: String Scania Core (scc) has_message: Message dataType: String is_gatewayed: communication interface has_signal: Signal 1 1 RDF (rdf) [has_signal] 1 Io_port type: Resource Signal dcterms:subject: String type: String pin_type: String direction: String dcterms:subject: String bit_start: String bit_length: String offset: String factor: String [associates_with] 1 Generated OSLC4J Front-Ends hasID: CommonID uses_port: Io_port associates_with: Io_port 24 Frédéric Loiret – KTH / OFFIS has_interface: communication interface has_interface: Diagnostic Communication Interface has_io_port: Io_port type: String bit_start: String sourceAdress: String: String segment: String bit_length: String destinationAddre ss: String: String session: String pin_type: String offset: String period: String isOperationalDat a: Boolean direction: String factor: String timeout: String isFreezeFrame: Boolean priority: String file:///Users/floiret/Documents/Recherche/Projets/IOS_ECA/meetings/2015_12_09-OSLC_Summit_OMG/material/pics/SpecificationDiagram.svg Page 1 of 1 Thanks for your attention! CRYSTAL website http://www.crystal-artemis.eu CP-SETIS website (under construction) http://cp-setis.eu CRYSTAL IOS V2 & Public Use Case Deliverables (publicly released) http://www.crystal-artemis.eu/deliverables.html Lyo/KTH Code Generators https://wiki.eclipse.org/Lyo/AdaptorCodeGeneratorWorkshop 25 Frédéric Loiret – KTH / OFFIS