CRYSTAL. Seamless Life-Cycle Collaboration for Safety-Critical Systems Engineering. Dr. Christian El Salloum AVL List GmbH

Transcription

1 CRYSTAL Seamless Life-Cycle Collaboration for Safety-Critical Systems Engineering Dr. Christian El Salloum AVL List GmbH ARTEMIS-JU Joint project Undertaking

2 Today s situation at industrial companies Industrial Workflows! Fragmented IT High maintenance costs!!! High manual effort to handle data Impact on quality and safety Tool Layer

3 The tool-integration problem Point-to-point Integrations don t scale Monocultures lock you in Maintenance, management, and change costs go up over time Ongoing and unexpected costs drain resources Creating new integrations is unpredictable Past choices restrict present action and future vision

4 The CRYSTAL Vision Industrial Workflows Enable New Engineering Methods Users get better ways of working Open Integration Platform Standardized Interoperability Specification Connect tools to expose & link data Tool Layer

5 CRYSTAL has the critical mass to generate impact 68 partners from 10 countries 82M budget European key players (competitors) from different industrial domains Large companies developing embedded systems act as technology users and case providers Large tool providers, SMEs and researchers as technology providers

6 CRYSTAL TECHNICAL APPROACH Standardize tool interaction, but not a tool s capabilities! Apply the Interoperability Specification (IOS) as the central standard Build on existing standards whenever reasonable

7 Integration Technologies: Syncing vs. Linking

8 BOM UUT OPTION A: SYNCING DATA BETWEEN TOOLS Example: Synchronize Unit Under Test (UUT) description in a Test Management system with Bill of Material (BOM) in a PLM system PLM System Test Management automatic syncing via mapping table November 19th, 2015

9 SYNCING PROS & CONS Benefits The user has all his data in its favorite tool No significant disruption in his workflow and user experience Specialized sync tools exist on the market Manage synchronization and conflict resolution in a transparent way Sync tool vendors takes care that all adaptors are kept up-to-date Challenges Data redundancy Who should be the master? Duplication of tool functionalities Often a consequence of data redundancy November 19th, 2015

10 OPTION B: LINKED DATA (WITH OSLC) OPEN SERVICES FOR LIFE CYCLE COLLABORATION Architecture of the Web Linked Data Automation Monitoring Standard Interfaces Just Enough integration November 19th, 2015

11 OSLC STANDARDIZED INTERFACES Communication Layer HTTP Syntax Layer RDF/XML Semantic Layer OSLC Core OSLC Domains November 19th, 2015

12 Web Services Web Services TRANSITION FROM SYNC TO LINK ALM EXAMPLE (POINT-TO-POINT) PLM MCAD Configura tions ECAD Parts Options & Variants ECRs SW Config ALM Req SW Config Test Releases Variant Specs Defects SW Changes Web Services Java API Mechanical Engineer Configuration Manager Variability Manager IIS (Web Services) MBSE Reusable Assets Simulations Req Variation Points COM API Operational Models Component Models System Models Requirements Engineer System Architect Test Manage r November 19th, 2015

13 TRANSITION FROM SYNC TO LINK ALM EXAMPLE (OSLC) Configurable OSLC Resources HTML RDF+ XML JSON PLM MCAD Configura tions ECAD Parts Options& Variants ECRs OSLC Connec tor ECR Part Opti on OSLC Connec tor ChR SWC Req ALM SW Changes SW Config Test Releases Req Defects Requirements Engineer Test Manage r MBSE Reusable Assets Variation Points Operational Models System Models Variability Manager Simulations Component Models System Architect November 19th, 2015

14 OSLC Benefits & Challenges Benefits Open standard & tool vendor agnostic No redundant data since data is not copied but linked Provides Delegated User Interface Generate views from one tool in the GUI of another tool Challenges Link consistency has to be maintained over time Base line management over distributed data stores has to be solved Flexible license model required OSLC has still to become a widely industrially accepted standard November 19th, 2015

15 Customer Requirement IOS as a multi standard Automotive Example (Public Use Case) Requirement Test Case System Requirement System specification Functional Safety Requirement Safety Goal Functional safety concept AVL VeVaT/Magic Simulation results ReqIF File import OSLC Data Mapping Parameter mapping AVL Model.Connect Virtual Integration platform

16 Project Outcomes CRYSTAL Interoperability Specification (IOS) Open specification Enables seamless integration of tools and full traceability across the product life cycle CRYSTAL IOS compliant Implementations Engineering Tools SDKs for developing IOS adaptors Tools for specifying and instantiating a System Engineering Environment (platform builder) CRYSTAL Use-Cases as reference scenarios Demonstrators with high level of maturity

17 Lessons Learned & Road to Success Build on a technically sound foundation CRYSTAL is based on successful principles like the Linked Data principles defined by the W3C (World Wide Web Consortium) Reach a critical mass CRYSTAL motivated a large group of stakeholders to make initial investments in the technology (AIPP and external stakeholders) Ensure openness & stability CRYSTAL actively supported the creation of eco-systems that creates and govern open standards (e.g. OSLC, FMI, ASAM ) based on the developed specifications Facilitate uptake by new stakeholders CRYSTAL provides tools to ease the adoption of the technology CRYSTAL provides reference solutions (demonstrators) CRYSTAL builds up an developer community

18 Conclusion & Market Innovation Reduced system development costs due to smart integration of tools Increased flexibility for OEMs Avoidance of vendor-lock-in New market opportunities for tool providers Facilitate innovation and market entry Great opportunities for SMEs Ensure Europe s leading edge position in development of safety-critical cyber-physical systems

19 Thank you for your attention! Technical Coordination: Dr. Christian El Salloum (AVL List GmbH) Adminstrative Coordination: Annemarie Hamedler (AVL List GmbH)