DATEX II Profile
DATEX II allows exchange for several kinds of data via several Exchange Specific Platforms. Not all of those PSM's have necessarily to be implemented in every DATEX II system and not all data content need be implemented. Thus DATEX II allows the implementation of profiles. “Profiling” aims to define a customised subset of options offered by a standard for a particular need.
The profiling guide section of the portal gives an in depth description of the profiling methodology.
What is a Profile?
A DATEX II system is composed of different publications which can be delivered with different Exchange PSM's. Each DATEX II system builder chooses to implement the subset of couple publications - Functional Exchange Profile + Exchange Pattern(FEP+EP) implemented by an Exchange PSM based on his needs. This subset is called a « DATEX II profile ».
The need is to have profiles and options that allow DATEX II users to customize their implementations in order to provide more or less functionalities/facilities as necessary and not to be forced into implementing all the features. DATEX II allows every user to define a profile according to his own requirements whilst keeping interoperability on common parts (publications, operating modes) with other users.
What must the stakeholder choose?
Because different needs for different use cases of DATEX II may lead to the definition of different profiles, this step will require close stakeholders’ involvement to elicit their requirements. Moreover, profiling will require assessment of the cost/benefit trade-off, in particular of:
- standard features/services;
- implementation platforms; and
- level of service that must be achieved.
Stakeholders need to provide their own perspective which will influence the main choices to be made concerning:
- the list of publications to be exchanged,
- the Exchange Requirement to be fulfilled and Exchange Features to be implemented,
- and sometimes also specific technology PSM's, options.