Home » railML newsgroups » railml.timetable » Attribute processStatus to be declared deprecated for <train>, <trainPart> and <trainGroup>
Re: [railML2] Re: Documentation of attribute "pathStatus" and proposal for new value "offered" [message #2495 is a reply to message #2461] Thu, 16 July 2020 16:20 Go to previous messageGo to previous message
Stefan Jugelt is currently offline  Stefan Jugelt
Messages: 3
Registered: May 2014
Junior Member
Dear all,

the TAF TSI (see https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv% 3AOJ.L_.2014.356.01.0438.01.ENG) contains a legal binding process description of the short term path request.

For the TAF TSI the following messages for a path request exists:

1. PathRequestMessage (RU --> IM)
2. ReceiptConfirmationMessage (IM --> RU)
3. PathDetailsMessage (IM --> RU)
4. PathConfirmedMessage (RU --> IM)
5. PathDetailsRefusedMessage (RU --> IM)
6. PathNotAvailableMessage (IM --> RU)
7. PathCanceledMessage

The messages are exchanged between the railway undertaking and the infrastructure manager in the order above. Some of the messages are optional, such as PathDetailsRefusedMessage.

The messages above may contain an additional element "TypeOfInformation", carrying supplementary information about the status of the path. The following values are allowed:

01 harmonisation - in process
02 harmonisation - accepted
03 harmonisation - rejected
04 harmonisation - completed
05 path study request
06 pre-arranged path/reserve capacity
07 create offer
08 coordination update
09 draft offer
10 draft alternative offer
11 observation - in process
12 observation - complete
13 preparation of final offer - in process
14 preparation of final offer - accepted
15 preparation of final offer - rejected
16 final offer
17 final offer - accepted
18 alternative offer accepted
19 pre-accepted offer
20 Final Offer rejected
21 no alternative available
22 booked
23 - preparation of draft alternative offer is in progress
24 - Preparation of draft offer - accepted
25 offer/final offer rejected (without revision)
26 alternative offer rejected (without revision)
27 offer/final offer rejected (revision required)
28 alternative offer rejected (revision required)
31 Close Dossier
30 Create Dossier
40 Fully Assembled Path (FAP, constructed path)
41 Final Offer rejected
42 Preparation of draft offer accepted
43 Preparation of draft offer rejected
44 Draft offer rejected
45 - Draft no alternative available
50 activate path (utilisation notification)
51 deactivate path (utilisation notification)
52 confirmation of utilisation notification
53 Path and train cancelled

More information about the is available in the sector handbook: http://taf-jsg.info/?page_id=280

Kind regards,

Stefan Jugelt
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Meaning and usage of @shuntingTime
Next Topic: Extension suggestion for alternativeSectionTT
Goto Forum:
  


Current Time: Sun May 05 00:58:22 CEST 2024