Data.CONNECT™ - Data.CONNECT™ - Content
Connect your existing data
Data.CONNECTTM is a technology stack that provides simple, task-oriented data access by linking different data sinks and sources.
In the course of the development of a vehicle, huge quantities of data are generated. In order to be best-in-class, it is important to get the most out of this data treasure. Especially the linkage of the data brings the decisive advance in knowledge. However, this potential is frequently not used because the data are very specific - not only with regard to the representation of data models but also with regard to data format, navigation possibilities, data access or presentation of results and KPIs.
How can the simulation models, test result data, calibration parameter data, parts lists or cost calculations be linked if they were stored in different specific data sinks?
The AVL Solution
Data.CONNECT™ is a technology stack that connects system and component data from different sources to provide simple, task-oriented data access. An intelligent data connection layer links the various "worlds" via a central virtual link repository. Physically, the data can remain in the original database.
This allows to link data from different sources.Thus, it is possible to e.g. determine which dataset has been created with which calibration parameters and can then be linked to a certain bill of material and cost calculation. These results can be connected to specific drive test configurations.
The Added Value
- You can implement new applications to analyze development results
- Dependencies can be traced across different data sources
- Better understand decisions during individual optimization loops
- Gain many new insights into your vehicle development process
Who can tell me with certainty which datasets are flashed in this hybrid vehicle?
When engine calibrators hand over their datasets to their clients, they will state, “engineering targets achieved under normal conditions”. The transmission calibrators say the same thing. The battery control unit teams ditto. Do they mean that all calibration datasets have been tested on their own, as stand-alone calibrations, or together as a system in a hybrid vehicle?