Standardised Solutions

Proposal Workshop: Cloud-to-Cloud Interface

Day: tbd
Venue: USA (exact location: tbd)

Notice: The meetings have been postponed due to participant's schedule conflicts. ASAM will survey the participants for the best appropriate date. Participants will receive a two-month notice of the next scheduled dates. We apologize for any inconvenience.

On August 24, the ASAM Office will host a Proposal Workshop to discuss, to agree upon, and to finalize a proposal for a potential standard.

On August 25, Cummins will host a project kick-off on the exact technical requirements with those who wish to actively participate in the ASAM Process.

A team consisting of representatives of Cummins, Geotab, RA Consulting, and Robert Bosch Engineering and Business Solutions have documented an initial concept for a standard. Now the ASAM community invites you to contribute to this initial framework.

Come, present your technical requests and requirements, and discuss the issues and potential solutions encountered when enabling communication between a telematics service providers server solution and manufacturer server solution. Your presented solutions and comments on the work to date will strengthen a future standard to be useful for all. We can make a presentation slot available for you at the meeting (first come, first serve) to present your requirements. Please indicate on the registration form if you would like to make a presentation.

Upon registering, the ASAM Office will send you the initial documentation developed for you to review. Feedback on this document is welcome before or during the workshop.

Which problem(s) will be addressed?

Vehicle OEMs and Tier 1 suppliers have increasing commercial reasons to securely maintain ECU software and configurations throughout the lifecycle of the vehicle at any time.  Additionally, data capture and use by the manufacturer is becoming a requirement for efficiency, for diagnostics, for prognostics, and for improved customer experience. The problem today is that each Telematics Service Provider and each Manufacturer have their own proprietary solution to transmit data from the Telematics Service Provider server solution to the Manufacturer server solution. The goal is to standardize this data transmission so that more time can be spent analyzing and putting the data to use – instead of focusing on establishing communication or aligning data from multiple sources.

The team is in discussion regarding the scope of this project. Come and determine if this project will be concerned with only a standard interface for bi-directional data transfer between the server solutions of the Telematic Service Provider and the manufacturer – or – also include transmission from the Telematics Device directly to the manufacturer server solution. 

The types of data and the formats of the data need to be discussed and agreed. The team has proposed for the first step that the data is only internal ECU and sensor data. But the industry should now state their opinion on a roadmap for this standard: what needs to be done in a step-wise approach to solve the problems of the manufacturers quickly?

What is the expected outcome of the workshop?

During the proposal workshop, the participants are given the opportunity to exchange their practical experiences, problems, requirements and potential solutions for a standardized cloud interface API to enable the secure, bi-directional transmission of data between the manufacturer’s server solution and the Telematics Service Provider’s server solution. The goal of the workshop is to come to a broad agreement on the technical approach, requirements and expected content of the upcoming standard. After the workshop, the project proposal will be written with the input of all workshop participants. This final proposal can be circulated for final agreement before the submission to the ASAM Technical Steering Committee for approval. 

Furthermore, based on the results of the Proposal Workshop, Cummins will host the first meeting of the project group. This day will focus on project planning / administrative tasks and technical discussions related o the foundation of the standard. For this meeting, ASAM membership is not required. Subsequent meetings will require all participants to be ASAM members.

Who should participate?

Technical experts and their immediate managers in the areas of telematics communication, security, cloud/server infrastructure, and ECU experts are welcome to participate at both days of the workshop and to actively contribute. You are encouraged to forward the invitation to the interested, experienced parties.

Goals for Standardization

  • An agreed API for the exchange of data between the server solution of the Telematics Service Provider and the manufacturer
  • An agreement if the exchange of data directly from the Telematics Device to manufacturer server solution is in scope or not
  • Methods or features for data protection
  • Data format definitions
  • A road map that defines a step-wise approach to scope and implement future use-cases and data types

Open Discussion Points

The current proposal is that the first version of the standard would define:

  • Transmission of vehicle data which is available from vehicle ECUs (i.e. faults, RPM, coolant temperature, etc.)
  • Transmission of sensory data which is available from the TSP device only (i.e. GPS, accelerometer)

Additional use cases that have been discussed, but have been delayed for future versions:

  • Use case 2: Execution of routines on vehicle ECUs
  • Use case 3: Driver messaging 
  • Use case 4: Diagnostics and assistance
  • Use case 5: OTA vehicle ECU config and updates

Come and let your voice be heard.            REGISTER HERE

ASAM International Conference


ASAM International Conference

AUTONOMOUS DRIVING - Big Testing and Big Data as the Next Challenge (06.-07. Dec. 2017, Dresden, Germany)
Learn more
ASAM Solutions Guide 2017


ASAM Solutions Guide 2017

A comprehensive guide to ASAM standards, solutions, members and ASAM compliant products.
Download now
Best Practice

About ASAM

Best Practice

Find out how companies are using ASAM standards.
Learn more