2001-03-21 page 1 v1.4 © 2001 msr msr agenda structure history, mission, organisation of the msr...

2001-03-21 V1.4© 2001 MSR

MSRAgenda 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

2001-03-21 V1.4© 2001 MSR

MSRProceeding proposed by MSR for a ‚merger‘

Agree on a ‚merger‘ as a common goal

Set up a Common Task forceto plan the merger regardingGoals, organisation, finances

Etablisha regularly Communicationbetween MSR and ASAM

Agree on the ‚final decision process‘ in both organisations

2001-03-21 V1.4© 2001 MSR

Foundation as so called ‚E-Leiter Arbeitskreis‘, a common working group, MSR is organized at within the strategy circle 4, electric/electronics.

MSRHistory 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

2001-03-21 V1.4© 2001 MSR

MSRHistory 2: Who are MSR?

VDO A.Schindling AG

Porsche AGVolkswagen AG

DaimlerChryslerAG

Robert BoschGmbH

Hella KG

Siemens AG

BMW AG

http://www.msr-wg.de

MSR stands for Manufacturer Supplier Relationship

2001-03-21 V1.4© 2001 MSR

MSRHistory 3: Phases of MSR and MEDOC

1990 1995 today

analysis

2000

databasephase

SGMLPhase

XMLPhase

phase 2

MEDOCMEGMAMEPRO

engineering documentationmodel exchangeprocess synchonisation

project phase 95-012 sub-projects

phase 1

project phase 90-952 sub-projects

MEDOCMESA

engineering documentationsimulation interface

MEDOC engineering documentation

pilotcombination

formal and informeldata

preparation forthe mass market

2001-03-21 V1.4© 2001 MSR

MSROrganisation MSR

MSR project committee

AG MEDOCengineering

documentation

AG MEGMAmodel

exchange

AG MEPROprocess

synchonisation

planning & steering‚E-Leiter‘ report

strategierole of „supervisory board “

project managementbudget planningobjective control

releasecommittee report

2001-03-21 V1.4© 2001 MSR

MSRRoadmap 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

2001-03-21 V1.4© 2001 MSR

MSRPresentation of MEDOC


MEDOC

MEDOC stands for MSR engineering data objects and contents

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCMEDOC MSR engineering documentation

seemless, continuous and consistently structured productdocumention for electric/electronic components and systemsover their whole lifecycle e.g. for requirements specification

Implementation platform and tool independant

Exchange of information between car manufacturer and supplierwithout data conversion

Integration in heterogenious IT environments (PDM/TDM)

support of views (e.g. requirements specification vs. Functionalspecification)

structural unification, but no access mechanisms

document comprehensive mechanisms (reference concepts)

benefits:

objectives:

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCResults

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

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCOrganisation MEDOC

steering groupAG MEDOC

AK MSRSW

AG DTDAG implementation

& environment

AK MSRNET

AK MSRSYS

AK MSRDIA

AK MSRREP

AK MSRCC

AK MSRFMEA

common structural basisDTD strategy

CoC for implemention‚Think tank‘

modelling ofDTDs

project managementbudget planningobjective control

releaseMSR committee report

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCMEDOC MSR development documentation

considered process (simplified):

car manufacturer

supplier / simultaneous engineering partner

MSR MEDOC data exchange e.g. requirement specs, documentation, C-code

MEDOC stands for MSR engineering data objects and contents

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCPositioning in the level model for structured content

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCMEDOC : 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

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCExpectations 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 methodscontent

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCdesirable scenario, MSR integration into ASAM on the human basis

Big Demonstrator II

ASAM

MSR

team

commonplaning and steering

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCExamples and practical demonstration

- selected short examples for the use of

a) MSRSYS electric component designb) MSRSW ECU SW specificationc) MSRCC SW module exchange

- practical demonstration of an authoring system for electric components using the MEDOC MSRSYS structure (BMW project eCIS)

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCExample 1: implementation MSRSYS

configurationformatingpublishing

native XML editing tool

XML extentions for MS Office

XML based output from other legacy system

requirementspecification

the web

applications

PREPROCESSING AUTHORING PUBLISHINGREPOSITORY

versioning

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCExample SW development process using MSRSW

element

process stepinformation

root elementfor overallstructur

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCUsing the overall structure in a processorientated tool environment

e.g. ASCET-SDe.g. UML

analysis specification,design,

implementation

calibration

e.g. INCA,

functionalrequirements

Content management : aggregation integration configuration

e.g. editor

MS

RS

W

EDMPDM

processstep

tooling

standardizedInformationmodel

export export export export

MS

RS

W

MS

RS

W

MS

RS

W

2001-03-21 V1.4© 2001 MSR

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

2001-03-21 V1.4© 2001 MSR

MSR-MEDOC

Sample sequence of the exported MSRSW structur

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

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCdocumentation with MSRSW example formater postprocessing

2001-03-21 V1.4© 2001 MSR

MSR-MEDOCcoupling of TDMs using MSRCC example engine control unit SW development

classical SW develop-ment environment

ASCET-SD

eDoc (MSRSW)

Co

nti

nu

us

CM

Cle

arca

se

CM

ASCET-SD

ARCUS

BMW Bosch/K3

MSRCC(CONTAINER-CATALOG )

Exchange of- source code- configuration

- documentation

classical SW develop-ment environment

PDM (car structur), ERPPDM (car structur), ERP PDM, ERPPDM, ERP

2001-03-21 V1.4© 2001 MSR

MSRStrategic proposal

planningdevelopment

releaseof DTDs

common projects startingwith ‚former‘ MSR partnersGoal: process realisation

with MSR methods

MEDOC in ASAM ‚application interest group‘

feedback from realization

MEDOC

2001-03-21 V1.4© 2001 MSR

MSRPresentation of MEGMA


MEGMA

MEGMA stands for MSR engineering graphic model exchange

2001-03-21 V1.4© 2001 MSR

MSR-MEGMAOrganisation

VDO A.Schindling AG

Porsche AGVolkswagen AG

DaimlerChryslerAG

Robert BoschGmbH

Hella KG

Siemens AG

BMW AG

2001-03-21 V1.4© 2001 MSR

11/1997 12/1998 today12/200012/1999

Block LibraryKick-off

Block LibrarySpecification

Analysis of Model Exchange

Tool FeaturesAnalysis

Integration ofToolsuppliers

Concentration onBlock Library

MSR-MEGMAHistory

DemoExample

2001-03-21 V1.4© 2001 MSR

Inp

uts

Ou

tpu

ts

Function

Model

ImplementationInformation

Vehicle System Model

MSR-MEGMAGoals

Model based function specification and development.

Standardization of modelling Enhancement of

Modelling Tools Interfacing for Specification

and Documentation Model Exchange

between Tools

2001-03-21 V1.4© 2001 MSR

MSR-MEGMATechnical Focus: Model Exchange

StandardizedBlock Library

Model-FileTool-1

Model-FileTool-2

Tool-1 Tool-2

Converter

StandardizedsierteModel Description

Co-Simulation

C-Code

Autocode/Code-Integration

Export/Import

MEGMA goal:Conversion Process forStandardized Block Library

2001-03-21 V1.4© 2001 MSR

ASCET-SD

ECU

MATLABSIMULINK

MSR-MEGMAIntegration of Tool Suppliers

Today new: Integration of dSpace for Targetlink Codegeneration

2001-03-21 V1.4© 2001 MSR

MSR-MEGMAMSR 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

2001-03-21 V1.4© 2001 MSR

MSR-MEGMAResult: 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)

2001-03-21 V1.4© 2001 MSR

MSR-MEGMAMEGMA-MEDOC-ASAM

Model Based DevelopmentMEGMA

Development DocumentationMEDOC

ASAM Testing Standards

Development Process

Standards for the automotive systems development process

Sp

ecification

Tes

tin

g

Implementation

2001-03-21 V1.4© 2001 MSR

MSR-MEGMA/MEDOCMEGMA as Manufacturer - Supplier Linkage

Process MEGMA/MEDOC (idealized):

Automotive Manufacturer

Supplier

MSR MEGMA/MEDOC Model and Documentation Exchange

MSR stands for: „Manufacturer Supplier Relationship“

2001-03-21 V1.4© 2001 MSR

MSR-MEGMA/MEDOCOutlook: Interface MEGMA-Model - Documentation

MEGMA Library Model

The MEGMA Automotive Block Library standardizes modeling and can bein future enhanced with respect to implementation information for automatic linkage with structured documentation (MSRSW.DTD and ASAP2)!

2001-03-21 V1.4© 2001 MSR

MSR-MEGMA/MEDOCOutlook: Manufacturer - Supplier Model Exchange

Matlab/SIMULINK

MSRSW

CM

CM ASCET-SD

MSRSW

Manufacturer Supplier

PDM (Fahrzeugstruktur), ERPPDM (Fahrzeugstruktur), ERP PDM, ERPPDM, ERP

2001-03-21 V1.4© 2001 MSR 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.

LongTerm

ShortTerm

2001-03-21 V1.4© 2001 MSR

MSRProceeding proposed by MSR for a ‚merger‘

Agree on a ‚merger‘ as a common goal

Set up a Common Task forceto plan the merger regardingGoals, organisation, finances

Etablisha regularly Communicationbetween MSR and ASAM

Agree on the ‚final decision process‘ in both organisations

2001-03-21 page 1 v1.4 © 2001 msr msr agenda structure history, mission, organisation of the msr...

Documents