Code allocation

Codes are divided into three categories: • A for functional codes that have no impact on the message exchange. It represents functional information that is sent through the messages for functional use within the business processes (e.g. planning of a short term train) • B for process codes that have a relevance for the way applications deal with the message (e.g. the status of the message new, update, delete) • C for external codes that are used within the business processes but are controlled by different domains (e.g. Retail, UN Codes) that have their own governance processes. A reference to the controlling body is given. Processes for the maintenance of codes • Category A: • These codes are maintained within the domain of RUs, IMs and SMs. Any involved stakeholder (e.g. RU, IM, AB) can put the request for a change (new, alteration, deletion) to the technical services management group in the governance entity. The entity can consult relevant expert working groups on the need of that change within 2 months. The entity attributes a code value and informs the Supervisory Board. The entity publishes the code soon after. • Category B: • These codes are maintained within the domain. Any involved stakeholder (RU, IM, AB) can put the request for a change (new, alteration, deletion) to the technical services management group which has to consult relevant expert working groups on the need of that change within 2 months notice. The working group can reject, ask for clarifications and give a recommendation, eventually following an impact analysis. If approved, a migration strategy has to be developed as well. On recommendation of the working groups the service management group attributes a code value and recommends approval from the Supervisory Board. The entity publishes the code and the migration plan soon after that confirmation. The code can be used according to that migration plan or bilateral agreements. • Category C -> see respective controlling body. The entity publishes these codes as well for information as soon as they are known. A delay notice until the use of these codes can be agreed. The ERA TAF and/or TAP CCM WP will be informed on the changes of the codes.