ASAM Standards International Perspective – A Report

ASAM Standards International Perspective – A Report

Author : Puran Parekh Board of Directors – ASAM e.V.

26th October 2011 Novi, USA

2

VISION

to create a development and testing world where devices can be freely inter-connected and data can be seamlessly exchanged…….

3

CAT StandardsHelp Companies take the  individual test rig data to department level/ enterprise level testing and validation process, without affecting the core functionality of the test rig, by leveraging device, data format and the analysis tool independence

4

Current CAT StandardsASAM ACI: (Automatic Calibration Interface)Defines interfaces between automation and optimization components which evaluate an optimized setof parameters for control systems.

ASAM CEA: (Components for Evaluation and Analysis)defines a component interface and the necessary basic functionality for the creation of project-specific overall applications from modular measured data evaluation and analysis tools

ASAM GDI: (Generic Device Interface)Defines interfaces to measurement devices and intelligent subsystems as well as a syntax for ageneric description of their capabilities.

ASAM ODS: (Open Data Service)Defines a generic data model (for universal interpretation of data), interfaces (for model management, data storage and data retrieval), and a data exchange syntax and format

5

Automotive Electronics(AE)

Help companies in implementing enterprise wide collaborative engineering and diagnostic functionality by leveraging standardized way of communication and data exchangeabilty beween various stakeholders

6

AE – MCD Structure

7

AE Process Support

8

TO SUPPORT ENTERPRISE PROCESS

ASAM STANDARDS

9

INTERNATIONAL PERSPECTIVE

ASAM Standards

10

Today, ASAM e.V. …counts more than 120 companies from Europe, North-America, and Asia, including most of the big international OEMs.

11

ASAM – International Image

ASAM ODS – De facto….Extensive uses of AE Standards but visibility is

Missing

12

ASAM ODS: Use casesSearch OnlyAnalysis OnlyAbove + Support for Macro Level Work FlowAbove + Support for Micro level process of EngineerFrom test bed to test field to Enterprise level scalability

13

ASAM ODS – Few MythsOff the shelf solutions , Wrong assumptions – ODS can solve all the problemsATF is a fixed file formatImportance of MIME types… Why needed and so important?Parameter Set for different domain For Example NVH / Crank angle?Application Model – What is it???Supplier have to integrate ODS into their product and they will require more knowledgeODS project is complete if we just import the data into ODS and access it from any analysis softwareAny Supplier say “I AM ODS COMPLIANT” Supplier’s data model can be used as it is for Enterprise Level deploymentMDM is off the shelf solutions:-> Is it the right Approach??ODS is too complex and some time slow….ASAM ODS is a database

14

Some Open Questions?Missing background as how the standard is evolved over a period to such a detailed level which can be appreciated (Without the understanding of the background the standard looks complicated)Supplier view of standardLack of trained people , companiesLocal suppliers have practically very less or no knowledgeHow to integrate local suppliers in Process supported by ASAM standardsCultural issues

15

FACTSASAM provides base standards which can be extended using Application elements , and these elements can be populated using infrastructure approachMain Focus :Structured organization of engineering data from different domains Most of supplier have implemented domain specific interfaces into their product

16

Why ODS project fails?Supplier is made responsible for complete projectNo Co-ordination between End user, IT and SuppliersMost of the time focus is on data storage and not on usage Lack of infrastructure approachUnderestimate complexity in the beginning

17

ChallengesChange in paradigm / mindsetChanges in Analysis tools functionalityProcess centric ApproachTesting – Dynamic / Continuously evolving in nature…..

18

For SuccessInfrastructure approachStandardization of naming conventions / testing process / Micro processInvolvement of Engineering team, IT, Tool Supplier and integrator at the beginningTop down / Bottom up approachBe careful about supplier specific solutions…. (They are very specific to their own product)

19

Expectations from ASAM Use of multi domain data Example , Engine NVH and Crank angle data , ECU dataData exchangeability between CAE and CATImprovement in existing standards to cater to new requirementsISO26262 – can AE and CAT collaborate to manage test results

20

AE Area – Internatioanl usagesMost of the AE standards are used extensively Specially MCD standards(1(XCP),2(ODX/A2L),3C/3D)Expectation – Improvement in MCD-3MC areaOverlapping areas in CAT and AE (Specially Automatic calibration process)

21

To benefit from ASAM platform effectivelyCommunity driven ApproachOpen and transparent cultureProcess Ownership

Questions????Thank you!!