After the finalization of the migration to the new identifiers, the new identifiers have to be mandatory in the message exchange. References for further reading (mandatory for implementation of the new identifiers!) The following documents are necessary to be used : TrainID OTN Framework (Annex 8.1) – TrainID Variant Framework (Annex 8.2) – TrainID Update Link Framework (Annex 8.3) – TrainID Case Reference Framework (Annex 8.4) – TrainID Object Info Framework (Annex 8.5) – TrainID UML (Annex 8.8) – TrainID WG10 Handbook (Annex 8.9): The baseline from 2011 endorsed by TAF – TSI RU/IM Cluster With these documents, the details about the procedures of handling of the new identifiers and their relation with legacy identifiers (such as OTN) is provided. UML is given as the Enterprise Architect” model as well as the full HTML “Sparx website-capable material (Annex 8.8).
After the finalization of the migration to the new identifiers, the new identifiers have to be mandatory in the message exchange. References for further reading (mandatory for implementation of the new identifiers!) The following documents are necessary to be used : TrainID – OTN Framework (Annex 8.1) TrainID – Variant Framework (Annex 8.2) TrainID – Update Link Framework (Annex 8.3) TrainID – Case Reference Framework (Annex 8.4) TrainID – Object Info Framework (Annex 8.5) TrainID – UML (Annex 8.8) TrainID – WG10 Handbook (Annex 8.9): The baseline from 2011 endorsed by TAF TSI RU/IM Cluster With these documents, the details about the procedures of handling of the new identifiers and their relation with legacy identifiers (such as OTN) is provided. UML is given as the “Sparx Enterprise Architect” model as well as the full HTML website-capable material (Annex 8.8).
20151018_TAP_TAF_RU_IM_Sector-Handbook_v2.1.1_1.0-clear.docx