Objectives for the further development of TecDoc data exchange structures
More flexible for new content
In the vast majority of cases, new content results in a change in the data exchange format with today’s exchange structures. This applies in particular to the reference data and, in particular, to the link targets. New classes of vehicles or vehicle components – for example for electromobility applications – can only be integrated into the databases “passenger cars” and “commercial vehicles” with non-transparent “tricks”. We aim to be able to provide such extensions in the future without the need to adapt the format. The new 3.0 information model provides a generic basis for this.
In this sense, this format change is intended to make further future format changes unnecessary.
Faster development of new target markets
With a new – largely generic approach – for the integration of new markets (in terms of vehicle classes and components), the option for a faster implementation is also increasing, as this does not require any technical adjustments on the interfaces of the partners involved.
The extension of TecDoc data exchange to other areas of application can therefore be faster and less cost-intensive.
Expansion to include logistics information
In addition to catalogue information, the transfer of data for applications in the areas of transport and storage (logistics in the broader sense) should also be able to be provided in the future. In addition to product characteristics (packaging, weights, dimensions), so-called packaging hierarchies also play an important role here. This should enable further user groups to use TecDoc data, for example by providing information about transport packaging or hazardous materials.
For this purpose, the TecDoc data structures are extended by the corresponding components, as this information cannot be adequately represented in the current structures.
Improved data quality
The new data exchange structures should also have part of the set of rules integrated into the structure. This applies above all to the characteristics expected and permitted for the products. In this way, we would also like to structurally promote the reliability of the content already mentioned in the section “Data quality and validations”.
Automation is an important factor, especially in the logistics process environment. This can only be achieved with 100% reliable data.
You will find the documentation in the subfolder “extras” of your data package in the file 3.0_Documents.7z
The basic design principles and structures of the new model are explained in this documentation. In addition, we have already informed about this at various international data user meetings and the last two data supply meetings in Berlin (2015 and 2016). Further information events will follow. Please take advantage of this opportunity.
This document describes in detail the migration of data from the format TAF 2.4 into the structures based on the information model 3.0.
Please note that the documents are in English only. A translation into German will only take place after the completion and only for the documentation of the information model.
The further implementation of the new data model and the solutions and services based on it should be based on the following principles:
1) Step-by-step optimization of design and documentation
You can also find the documentation (format description) in the customer area at www.tecalliance.net
We will carry out a continuous update, which is documented in a version history at the beginning of the document.
We will make editorial adjustments largely without comment. Significant adjustments to the structures will be communicated to you as part of regular communication.
2) Sketch of a step-by-step rollout
The focus is on the implementation of the objectives mentioned at the outset and the gradual and comprehensible supplementation/replacement of existing structures for all users. This process will be spread over several years and will not require a “big-bang” scenario.
3) Step-by-step provision of data in ever better quality levels
Data is provided in the three quality levels alpha/beta/productive. You will find reference data (linking targets) in alpha quality as part of your data package.