msr tr MSR goes ASAM en

Slide1: 

MSR Agenda structure History, Mission, Organisation of the MSR Consortium Proceeding proposed by MSR for a ‚merger‘ Organisation of the MSR MEDOC Goals, scope and lessons learned of MEDOC Expectations of MEDOC for an ASAM e.V. merger Use cases for MSRSYS, MSRSW, MSRCC A short demo of a MSRSYS implementation at BMW History, scope, organisation and results of MEGMA Examples, Outlook and next steps to go MSR MEDOC MEGMA

Slide2: 

MSR Proceeding proposed by MSR for a ‚merger‘ Agree on a ‚merger‘ as a common goal Set up a Common Task force to plan the merger regarding Goals, organisation, finances Etablish a regularly Communication between MSR and ASAM Agree on the ‚final decision process‘ in both organisations

Slide3: 

Foundation as so called ‚E-Leiter Arbeitskreis‘, a common working group, MSR is organized at within the strategy circle 4, electric/electronics. MSR History 1: Where it all started We have the year 1990 ..... An initiative of the top manager of the development (E-Leiter) of the german car makers (Audi, BMW, DC, Porsche, VW): The goal was development of cost reduction potentials by cooperation in non competitive areas and the use of synergy potentials in a common project

Slide4: 

MSR History 2: Who are MSR? VDO A. Schindling AG Porsche AG Volkswagen AG DaimlerChrysler AG Robert Bosch GmbH Hella KG Siemens AG BMW AG http://www.msr-wg.de MSR stands for Manufacturer Supplier Relationship

Slide5: 

MSR History 3: Phases of MSR and MEDOC 1990 1995 today analysis 2000 SGML Phase XML Phase MEDOC engineering documentation pilot combination formal and informel data preparation for the mass market

Slide6: 

MSR Organisation MSR MSR project committee AG MEDOC engineering documentation AG MEGMA model exchange AG MEPRO process synchonisation planning & steering ‚E-Leiter‘ report strategie role of „supervisory board “ project management budget planning objective control release committee report

Slide7: 

MSR Roadmap ASAM merger 4./5.7.00 21.11.00 12.12.00 6.2.01 8.3.01 21.3.01 22.3.01 3.4.01 17.4.01 24.4.01 MSR Workshop MSR Consortium MEDOC SC MEDOC SC MSR Consortium MSR & ASAM MB meeting ASAM management board MEDOC SC ASAM membership meeting MSR Consortium Need for a change MEDOC assigned to plan an ASAM merger Concepts for the merger First draft for set of MEDOC slides OK for slides, review criteria for merger First ‚real‘ contact with ASAM MB ASAM MB decides first reactions to ASAM decisions approval by ASAM members MSR reviews the ASAM results

Slide8: 

MSR Presentation of MEDOC MSR stands for Manufacturer Supplier Relationship

Slide9: 

MSR-MEDOC MEDOC MSR engineering documentation seemless, continuous and consistently structured product documention for electric/electronic components and systems over their whole lifecycle e.g. for requirements specification Implementation platform and tool independant Exchange of information between car manufacturer and supplier without data conversion Integration in heterogenious IT environments (PDM/TDM) support of views (e.g. requirements specification vs. Functional specification) structural unification, but no access mechanisms document comprehensive mechanisms (reference concepts) benefits: objectives:

Slide10: 

MSR-MEDOC Results developed structures (DTDs) processed domains electric HW-system and components ECU software functions system network diagnosis specification failure mode and effect analysis container for code, SW-configuration and their documentation based on SW-Modules general documentation and change management structure MSRSYS MSRSW MSRNET MSRDIA MSRFMEA MSRCC MSRREP

Slide11: 

MSR-MEDOC Organisation MEDOC steering group AG MEDOC AK MSRSW AG DTD AG implementation & environment AK MSRNET AK MSRSYS AK MSRDIA AK MSRREP AK MSRCC AK MSRFMEA common structural basis DTD strategy CoC for implemention ‚Think tank‘ modelling of DTDs project management budget planning objective control release MSR committee report

Slide12: 

MSR-MEDOC MEDOC MSR development documentation considered process (simplified): MSR MEDOC data exchange e.g. requirement specs, documentation, C-code MEDOC stands for MSR engineering data objects and contents

Slide13: 

MSR-MEDOC Positioning in the level model for structured content

Slide14: 

MSR-MEDOC MEDOC : lessons learned POSITIVE business model determines to act in different roles (e.g. as architect, mason, resident) impulsive power by use of technology within (car-) series projects voluntary liaison that means voluntariness of attendance AND bound by contract small is beautiful torch relay: not all partners are in all times in a leading role by the use in series project, solidarity in the group as a compensative power basic mental attitude is ‚open minded‘ not ‚let‘s fight‘ formal, document based (MSRREP / SGML) change management process NEGATIVE low market penetration focused on technology (still) too weak feedback from widely implementations individuel rollout processes within the partner companies lack of integration of the tool suppliers

Slide15: 

MSR-MEDOC Expectations from MSR for an ASAM e.V. merger organisation strategy persistence stable organisation international members quick decision processes international members focus on embedded-systems development not only for vehicles market penetration by integration of the tool suppliers transparent business processes long term goal planning stable financing basis common XML architectur for ASAM and MSR information models further development of the released methods content

Slide16: 

MSR-MEDOC desirable scenario, MSR integration into ASAM on the human basis Big Demonstrator II ASAM MSR team common planing and steering

Slide17: 

MSR-MEDOC Examples and practical demonstration - selected short examples for the use of a) MSRSYS electric component design b) MSRSW ECU SW specification c) MSRCC SW module exchange - practical demonstration of an authoring system for electric components using the MEDOC MSRSYS structure (BMW project eCIS)

Slide18: 

MSR-MEDOC Example 1: implementation MSRSYS configuration formating publishing native XML editing tool XML extentions for MS Office XML based output from other legacy system requirement specification the web applications PREPROCESSING AUTHORING PUBLISHING REPOSITORY versioning

Slide19: 

MSR-MEDOC Example SW development process using MSRSW element process step information root element for overall structur

Slide20: 

MSR-MEDOC Using the overall structure in a process orientated tool environment e.g. ASCET-SD e.g. UML analysis specification, design, implementation calibration e.g. INCA, functional requirements Content management : aggregation integration configuration e.g. editor EDM PDM process step tooling standardized Information model export export export export

documentation with MSRSW example case tool ASCET-SD (1): 

MSR-MEDOC documentation with MSRSW example case tool ASCET-SD (1)

documentation with MSRSW example case tool ASCET-SD (2): 

MSR-MEDOC Sample sequence of the exported MSRSW structur documentation with MSRSW example case tool ASCET-SD (2)

documentation with MSRSW example formater postprocessing: 

MSR-MEDOC documentation with MSRSW example formater postprocessing

Slide24: 

MSR-MEDOC coupling of TDMs using MSRCC example engine control unit SW development classical SW develop- ment environment ASCET-SD eDoc (MSRSW) Continuus CM Clearcase CM ASCET-SD ARCUS BMW Bosch/K3 MSRCC (CONTAINER- CATALOG ) Exchange of source code configuration documentation classical SW develop- ment environment

Slide25: 

MSR Strategic proposal planning development release of DTDs common projects starting with ‚former‘ MSR partners Goal: process realisation with MSR methods MEDOC in ASAM ‚application interest group‘ feedback from realization MEDOC

Slide26: 

MSR Presentation of MEGMA MSR stands for Manufacturer Supplier Relationship

Slide27: 

MSR-MEGMA Organisation VDO A. Schindling AG Porsche AG Volkswagen AG DaimlerChrysler AG Robert Bosch GmbH Hella KG Siemens AG BMW AG

Slide28: 

11/1997 12/1998 today 12/2000 12/1999 Block Library Specification Analysis of Model Exchange Tool Features Analysis Integration of Toolsuppliers Concentration on Block Library MSR-MEGMA History Demo Example

Slide29: 

Inputs Outputs Function Model Implementation Information Vehicle System Model MSR-MEGMA Goals Model based function specification and development. Standardization of modelling Enhancement of Modelling Tools Interfacing for Specification and Documentation Model Exchange between Tools

Slide30: 

MSR-MEGMA Technical Focus: Model Exchange MEGMA goal: Conversion Process for Standardized Block Library

Slide31: 

ASCET-SD ECU MATLAB SIMULINK MSR-MEGMA Integration of Tool Suppliers Today new: Integration of dSpace for Targetlink Codegeneration

Slide32: 

MSR-MEGMA MSR Automotive Block Library Benefits Standardizes model based function development. Furnishes a full set of blocks for discrete modelling. Provides blocks with identically verified behaviour. Results in homogenous models in structure, hierarchy and function. Improves the reuse of models. Improves documentation and requirements engineering process. (i.e. automatic content for MSRSW.DTD) Provides the basics for additional guidelines for autocode. Is the foundation for possible future automatic model exchange. The MSR Automotive Block Library

Slide33: 

MSR-MEGMA Demo Example: Engine Idle Control

Slide34: 

MSR-MEGMA Result: MSR Block Library Specification Arithmetic (5) Logic (4) Comparisons (7) Mathematic Functions (11) Counter/Timer (10) Delay/Memory (6/2) Nonlinear (8) Integrators (2) Low/Highpass (5) Parameter and Constants (8) Miscellaneous (12)

Slide35: 

MSR-MEGMA MEGMA-MEDOC-ASAM Model Based Development MEGMA Development Documentation MEDOC ASAM Testing Standards Development Process Standards for the automotive systems development process Specification Testing Implementation

Slide36: 

MSR-MEGMA/MEDOC MEGMA as Manufacturer - Supplier Linkage Process MEGMA/MEDOC (idealized): Automotive Manufacturer Supplier MSR MEGMA/MEDOC Model and Documentation Exchange MSR stands for: „Manufacturer Supplier Relationship“

Outlook: Interface MEGMA-Model - Documentation: 

MSR-MEGMA/MEDOC Outlook: Interface MEGMA-Model - Documentation MEGMA Library Model The MEGMA Automotive Block Library standardizes modeling and can be in future enhanced with respect to implementation information for automatic linkage with structured documentation (MSRSW.DTD and ASAP2)!

Slide38: 

MSR-MEGMA/MEDOC Outlook: Manufacturer - Supplier Model Exchange Matlab/SIMULINK MSRSW CM CM ASCET-SD MSRSW Manufacturer Supplier

Slide39: 

MSR-MEGMA Next Steps to Go Bring the MSR automotive block library from paper to work. Set defacto standard for model based function devolopment. Develop a demonstrator system. Finish test specification and (automatic) test procedures. Integrate tool suppliers in further development. Support the implementation of tool suppliers. Provide verification testing and MSR/ASAM certification of the tool specific implementations. Establish defacto Standard. Continue development of the automotive block library - new features are multirate blocks, code generation and state charts. Establish a formal certification procedure. Long Term Short Term

Slide40: 

MSR Proceeding proposed by MSR for a ‚merger‘ Agree on a ‚merger‘ as a common goal Set up a Common Task force to plan the merger regarding Goals, organisation, finances Etablish a regularly Communication between MSR and ASAM Agree on the ‚final decision process‘ in both organisations