Pathfinder Orange Book for Version 2.2.4 - RNE

More documents

Recommendations

Info

Pathfinder Orange Book Version 2.2.4Agreeing catalogue pathsCatalogue paths retains “Path Elaboration” status until all participating IM’s have stated theiragreement. The leading IM (= requester = initiator) can release the paths. This release processenters the catalogue path in the path catalogue. The participating IM’s can transfer their pathsections into the Dossier manually or by means of Integration Platform (web service“updateDossier”, see [3]).It must be repeated here that a national path can be assigned to more than one Dossier. Inaddition, a path can consist of more than one path element, each with its own number/identifier.This means that national catalogue path elements can be combined into international cataloguepath corridors even during the agreement phase.3.4.3 Updating catalogue paths3.4.3.1 General updatingA path in the path catalogue can be changed just like a path in the agreement process. The IMmaking the change is responsible for ensuring that a catalogue path corridor still retains itsintended connections. All participating IM’s are notified of the change in a similar way to theprocedure in the agreement phase (the Dossier appears in the “Inbox“).If, following a change, an IM withdraws his agreement to a corridor the path still remains in thecatalogue, because this non-agreed path can still be requested by an RU for a sub-section.Approval for a catalogue path corridor is withdrawn by the IM giving his national path element thestatusRed = not agreed Not accepted3.4.3.2 Updating the availability of dynamic catalogue pathsThe availability of a dynamic catalogue path is shown using the dates in service function ofPathfinder. This means that a path can be marked by the IM as reserved or not reserved forspecific dates in service. These dates in service can be updated using the dates in service importfunction of the Pathfinder Integration Platform. The dates in service can be changed manually orthey can be updated in the dossier via Integration Platfrom (web service “updateDossier”, see [3]).3.4.4 Searching for catalogue paths3.4.4.1 In the requested timetableThe existing search function is used to search for catalogue paths. In the “Open” and“Harmonization” phases, an RU can use the search function within the “RU’s requested timetable”for a particular stop. The search can be further restricted by using the existing search fields. Thearrival and departure times are also added as search fields. (See also: 10.6.27. “Find cataloguepaths” symbol (RU’s only) )If the RU selects a catalogue path for transfer, then the “IM timetable” from the stop from which thesearch function was called up is entered as the requested timetable for the RU. The requestedtimetable is then extended by the stops of the catalogue path. The Dossier number of thecatalogue path is entered in the comments field for the stops as a reference for the IM. All otherparameters of the catalogue path are transferred to the corresponding data fields.The RU can edit the complete timetable. Any number of catalogue paths can be transferred into arequested timetable.3.4.4.2 In the normal search functionAll IM’s can use the normal search function to search for catalogue paths. The Dossier type“Catalogue” and train type “Catalogue path“ must be selected and the search restricted by usingother parameters if necessary.3.4.4.3 Printing catalogue pathsLike all other paths, catalogue paths can be printed. This is done via a PDF file, which the user canthen download from the central system on to his workstation and print out.3.4.5 Requesting / ordering catalogue pathsThe procedure for requesting and ordering catalogue paths is just the same as for individuallyagreed paths. The RU selects the catalogue path in the requested timetable and adds to it asrequired.December 2010 Page 34 of 133
Pathfinder Orange Book Version 2.2.4Any number of catalogue paths can be linked together within a requested timetable. For example,several catalogue path elements can be combined into one catalogue path corridor. However, theparticipating IM’s must check whether the elements they have combined are in fact available.The Dossier is then sent by the leading RU to the IM as a request. An IM can tell from the Dossierreference in the comments relating to the stops that this request is based on a catalogue path.In the start-up phase of Pathfinder, the dates in service for a dynamic catalogue path in particularwill not always be updated in real time and immediately. It should therefore be remembered thateven though catalogue paths may be identified as being available, they may in fact not be availablefor allocation.An RU can use a catalogue path as an “Path Elaboration example”, i.e. once the catalogue pathdata has been transferred into their requested timetable they can adapt it to suit their individualneeds. If the parameters of a catalogue path are adapted by an RU after transfer, it is up to the IMwho is approached to decide whether to use the catalogue path or to construct their own.A catalogue path that has been ordered and allocated (reserved) can be identified in the pathcatalogue as reserved, by transferring the reserved dates in service to Pathfinder via the PathfinderIntegration Platform. That is to say, the national planning system must send the catalogue path toPathfinder with a modified key for the dates in service. Alternatively the dates in service for whichthe catalogue path has been reserved can also be entered manually in Pathfinder.3.4.6 Period of validity of catalogue pathsCatalogue paths are linked to one particular timetable period. When that timetable period expires,the catalogue paths are stored in the archive.3.4.7 Deleting catalogue pathsThe IM responsible for a catalogue path, generally the “provider” or initiator, can delete a cataloguepath Dossier. Any other participating IM’s will be notified via their Inbox. Another IM who is involvedcannot delete the catalogue path, but can withdraw his consent for his particular section. The pathstill remains stored in the path catalogue.December 2010 Page 35 of 133
Page 1 and 2: Pathfinder Orange Book Version 2.2
Page 33: Pathfinder Orange Book Version 2.2
Page 85 and 86:
Pathfinder Orange Book Version 2.2
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133:
show all

Pathfinder Orange Book for Version 2.2.4 - RNE

Create successful ePaper yourself

Delete template?

Save as template?