PowerPointPrsentation

1
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
2
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
3
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)
Foundation as so called E-Leiter Arbeitskreis,
a common working group, MSR is organized at
within the strategy circle 4, electric/electronics
.
The goal was development of cost reduction
potentials by cooperation in non competitive
areas and the use of synergy potentials in a
common project
4
MSR
History 2 Who are MSR?
BMW AG
DaimlerChrysler AG
Porsche AG
Volkswagen AG
http//www.msr-wg.de
VDO A. Schindling AG
Hella KG
Robert Bosch GmbH
Siemens AG
MSR stands for Manufacturer Supplier Relationship
5
MSR
History 3 Phases of MSR and MEDOC
MEDOC engineering documentation
pilot
combination formal and informel data
preparation for the mass market
analysis
SGML Phase
XML Phase
1990
1995
today
2000
6
MSR
Organisation MSR
planning steering E-Leiter report strategie ro
le of supervisory board
MSR project committee
project management budget planning objective
control release committee report
AG MEDOC engineering documentation
AG MEGMA model exchange
AG MEPRO process synchonisation
7
MSR
Roadmap ASAM merger
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
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
8
MSR
Presentation of MEDOC
MSR stands for Manufacturer Supplier Relationship
9
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 Implementatio
n 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)
objectives
benefits
10
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 MS
RREP
11
MSR-MEDOC
Organisation MEDOC
project management budget planning objective
control release MSR committee report
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
12
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
13
MSR-MEDOC
Positioning in the level model for structured
content
14
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
  lets 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

15
MSR-MEDOC
Expectations from MSR for an ASAM e.V. merger

• stable organisation
• international members
• quick decision processes
• international members

organisation

• focus on embedded-systems development not only
  for vehicles
• market penetration by integration of the tool
  suppliers
• transparent business processes

strategy

• common XML architectur for ASAM and MSR
  information models
• further development of the released methods

content

• long term goal planning
• stable financing basis

persistence
16
MSR-MEDOC
desirable scenario, MSR integration into ASAM on
the human basis
ASAM
Big Demonstrator II
team
MSR
common planing and steering
17
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)
18
MSR-MEDOC
Example 1 implementation MSRSYS
PREPROCESSING
AUTHORING
PUBLISHING
REPOSITORY
requirement specification
XML based output from other legacy system
versioning
the web
XML extentions for MS Office
configuration formating publishing
applications
native XML editing tool
19
MSR-MEDOC
Example SW development process using MSRSW
element
process step information
root element for overall structur
20
MSR-MEDOC
Using the overall structure in a
process orientated tool environment
functional requirements
specification, design, implementation
analysis
calibration
process step
e.g. ASCET-SD
e.g. UML
e.g. INCA,
e.g. editor
tooling
export
export
export
export
standardized Information model
EDM PDM
Content management aggregation integration
configuration
21
documentation with MSRSW example case tool
ASCET-SD (1)
MSR-MEDOC
22
documentation with MSRSW example case tool
ASCET-SD (2)
MSR-MEDOC
Sample sequence of the exported MSRSW structur
23
documentation with MSRSW example formater
postprocessing
MSR-MEDOC
24
MSR-MEDOC
coupling of TDMs using MSRCC example engine
control unit SW development
Bosch/K3
BMW
classical SW develop- ment environment
classical SW develop- ment environment

• MSRCC
• (CONTAINER-CATALOG )
• Exchange of
• source code
• configuration
• documentation

ASCET-SD
ASCET-SD
Continuus CM
Clearcase CM
eDoc (MSRSW)
ARCUS
PDM (car structur), ERP
PDM, ERP
25
MSR
Strategic proposal
MEDOC
application interest group
MEDOC in ASAM
planning development release of DTDs
common projects starting with former MSR
partners Goal process realisation with MSR
methods
feedback from realization
26
MSR
Presentation of MEGMA
MSR stands for Manufacturer Supplier Relationship
27
MSR-MEGMA
Organisation
BMW AG
DaimlerChrysler AG
Porsche AG
Volkswagen AG
VDO A. Schindling AG
Hella KG
Robert Bosch GmbH
Siemens AG
28
MSR-MEGMA
History
Integration of Toolsuppliers
Concentration on Block Library
DemoExample
Block LibrarySpecification
Analysis of Model Exchange
Tool FeaturesAnalysis
11/1997
12/1998
12/2000
12/1999
today
29
MSR-MEGMA
Goals

• Model based function specification and
  development.
• Standardization of modelling
• Enhancement of Modelling Tools
• Interfacing for Specificationand Documentation
• Model Exchange between Tools

Function Model
Implementation Information
Outputs
Inputs
Vehicle System Model
30
MSR-MEGMA
Technical Focus Model Exchange
MEGMA goal Conversion Process for Standardized
Block Library
31
MSR-MEGMA
Integration of Tool Suppliers
MATLAB SIMULINK
ASCET-SD
ECU
Today new Integration of dSpace for Targetlink
Codegeneration
32
MSR-MEGMA
MSR Automotive Block Library Benefits
The MSR Automotive Block Library

• 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.

33
MSR-MEGMA
Demo Example Engine Idle Control
34
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)
35
MSR-MEGMA
MEGMA-MEDOC-ASAM
Standards for the automotive systems development
process
Development Process
Model Based Development MEGMA
Testing
Specification
Development Documentation MEDOC
Implementation
ASAM Testing Standards
36
MSR-MEGMA/MEDOC
MEGMA as Manufacturer - Supplier Linkage
Process MEGMA/MEDOC (idealized)
Automotive Manufacturer
MSR MEGMA/MEDOC Model and Documentation Exchange
Supplier
MSR stands for Manufacturer Supplier
Relationship
37
Outlook Interface MEGMA-Model - Documentation
MSR-MEGMA/MEDOC
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)!
MEGMA Library Model
38
MSR-MEGMA/MEDOC
Outlook Manufacturer - Supplier Model Exchange
Supplier
Manufacturer
Matlab/SIMULINK
ASCET-SD
CM
CM
MSRSW
MSRSW
PDM (Fahrzeugstruktur), ERP
PDM, ERP
39
MSR-MEGMA
Next Steps to Go
Short Term

• 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
40
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