Table of contents

1. Structure of the object info message
2. Process-related attributes

1. Structure of the object info message

The Object Info Message has a very good structure making it possible to pack almost the full dossier content into one message. It spares the send-out of redundant messages and can provide information to all involved agencies about the full dossier content. 

Structure of the OIM message sent by PCS:

• Message header:
  • Sender: 3178 (RNE)
  • Recipient: company code of the applicant/IM
• Identifier: CR ID
• ObjectInfoType
• CoordinatingIM 
• LeadRU
• TypeOfRequest
• ProcessType
• TypeOfInformation
• Train Information Extended:
  • Identifiers:
    • PlannedTransportIdentifiers (PTID): TR ID
    • RelatedPlannedTransportIdentifiers (RPTID): all object IDs of the dossier​​​​​​​
  • TrainInformation (TI)
  • PathInformationExtended (PIE):
    • PTID: all PR or PA IDs (depending on the phase) – Timetable updates use case: only the modified sub-paths; GetDossier use case: all the subpaths
    • Path Information: for each PR or PA ID listed in PTID of PIE
• Dossier-level Network-specific parameters (if applicable)

2. Process-related attributes

Some PCS and also in TAF TSI fields deliver important information about the request type, process type and the process step. Additionally, information about the leading or coordinating agencies in the dossier is also relevant therefore the Object Info Message structure includes the following elements (already mentioned above):

• TypeOfRequest: applicable basic planning process type (Path Study, Path Request, Path Modification)
• ProcessType: applicable business process type (e.g, New Path Request and allocation process for annual timetable) 
• TypeOfInformation: applicable process step to which the message refers to
• CoordinatingIM: Leading IM of the dossier
• LeadRU: Leading Applicant of the dossier