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 !! !! • High manual • Fragmented IT effort to handle • High data maintenance • Impact on quality costs and safety Tool Layer Frédéric Loiret – KTH / OFFIS
The CRYSTAL Vision Industrial Workflows Users get better ways of Enable New Engineering working Methods • Standardized Interoperability Specifications Open (IOS) Integration Platform • Connect tools to expose & link data Tool Layer Frédéric Loiret – KTH / OFFIS
IOS History & Evolution } Pre-Project Phase (from 2010) Proprietary Demonstrators ◦ 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 Extended Public ◦ Fostering adoption of IOS by Tool Vendors and Industrial End-Users Demonstrators } After Project Phase ◦ Coordination Action (H2020 CP-SETIS) Industrial End- ◦ new projects (ITEA3 ASSUME, ECSEL ENABLE-S3) User Application Frédéric Loiret – KTH / OFFIS
CRYSTAL High Level IOS Architecture Data Integration across Tools, Data Repositories and Engineering Phases Interoperability Specification Examples: e.g., Traceability across the whole product (IOS) • Heterogeneous co-simulation development lifecycle • Real-Time Data Measurement and Calibration <consists of> • etc. Examples: • IOS Variability Management • IOS Safety Management • etc. Non-Lifecycle IOS Lifecycle IOS à Follow the process advocated by à <consists of> <consists of> OSLC for specifying domains 1 NLC Domain OSLC Based CRYSTAL IOS Lifecycle Specification Extension <adopts> 2 • OSLC Core specs Engineering <may define> Standard Examples of “OSLC 3 Domains”: • OSLC RM Spec, Bridges for • OSLC QM Spec, Integration with Examples: • etc. Lifecycle IOS • FMI • ASAM-ODS • ISO26262 Example from CRYSTAL: • AUTOSAR / EAST-ADL • Full-fledge traceability support between • ReqIF OSLC Requirements, Design Artifacts, and • STEP Simulation Results generated by FMI • etc. • Autosar to OSLC bridge • ReqIF to OSLC bridge 7 Frédéric Loiret – KTH / OFFIS
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 • Projects develop proposals (specs) Past Past Past Future Future CRYSTAL Project Project Project EMC2 for IOS extensions / Project Project CESAR iFEST MBAT IOS modifications / new standards • Defines IOS strategy Tool User WP2 • Be focal point and point of Identification of Cross-Projects IOS contact for all IOS related Challenges activities • Define stable IOS Versions WP3 Tool User for WG Standardization ARTEMIS-IA Fostering IOS Support • Evaluate results from Working Groups and Industrial Acceptance existing projects WP1 • Organize cross-project WP6 Model of sustainable IOS workshops Promotion & Dissemination Standardization Activities • Give recommendations to WP5 Tool Provider projects • Promotes Standards to tool Standardization SRA • Incubate new projects vendors and end users • Evaluate existing standards • Negotiates cooperation with standard WP4 WP0 organizations Tool Provider IOS Standardization Roadmap Management and • Create WGs in Standardization bodies Coordination • Assign IOS label to standards RO ASAM OASIS OMG Calibration Data Network Configuration Requirements RO Management Configuration Management Management … … WG WG WG WG Frédéric Loiret – KTH / OFFIS
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 Not yet formally in the scope of OSLC/OASIS OSLC/OASIS OSLC Core Linked-Data Platform for RDF, Notifications? Users Manag.? HTTP C.R.U.D. RESTful operations, OSLC-defined Resources, Access Control? Authentication? OSLC Core Resource types Normative Capabilities OSLC CCM VM? Version & Configuration Management Variability Management OSLC DUI & Resource Previews VPM? Delegated User Interface Dialogs Viewpoint Management ? OSLC Product Knowledge Detailed Arch. OSLC Reporting Definition Manag. Manag. OSLC Automation OSLC Estimation Safety & Risk Formal Req. Support & Measurement Manag. Manag. Informative OSLC Asset OSLC Arch. Human Factors Formal Analysis Capabilities Manag. Manag. OSLC Quality … etc … FMI/FMU Mapping Manag. Company-Specific Models … etc … 16 Frédéric Loiret – KTH / OFFIS
Recommend
More recommend
