PCS PROCESS GUIDELINES 2016
For path requests for the running timetable 2015
and the annual timetable 2016
Version: 1.2 / 3 March 2015
Updates
Every alteration in this document is reported in the following list of alterations
Nr.
Date
New (item, content)
0.1
9.1.2015
Opening of the file
0.2
12.1.2015 Update of deadlines and milestones
0.3
15.1.2015 Chapter “NEW PCS FUNCTIONS (PCS Release 4.3)” updated
1.1
23.1.2015 Index update
1.2
3.3.2015
Corrections
RailNetEurope
Oelzeltgasse 3/8
AT-1030 Vienna
Phone: +43 1 907 62 72 00
Fax: +43 1 907 62 72 90
Notes
PCS Process Guidelines 2016
mailbox@rne.eu
www.rne.eu
Content
1.
2.
3.
4.
5.
SET-UP OF PCS ............................................................................................................. 4
INTRODUCTION ............................................................................................................. 4
NEW PCS FUNCTIONS (PCS Release 4.3) .................................................................... 5
1) Search and Report ............................................................................................................... 5
2)
Pre-constructed Product search ........................................................................................... 5
3)
Template Manager ............................................................................................................... 6
4)
COBRA ................................................................................................................................ 6
5)
Manage Dossier ................................................................................................................... 7
6)
Multiple frequency trains....................................................................................................... 8
7)
Flex PaP .............................................................................................................................. 8
8)
Network PaP ........................................................................................................................ 9
9)
PaP Management............................................................................................................... 10
PCS PROCESS ............................................................................................................. 10
OPEN A DOSSIER ........................................................................................................ 10
1) Reference Point.................................................................................................................. 11
2)
Calendar and Offset ........................................................................................................... 11
3)
Common parameters .......................................................................................................... 11
4)
RU-IM pairs ........................................................................................................................ 11
5)
Partial and full harmonisation ............................................................................................. 11
6.
PATH CONSULTING / FEASIBILITY STUDY ................................................................ 13
7.
PATH REQUEST ........................................................................................................... 14
8.
PATH ELABORATION ................................................................................................... 14
9.
DRAFT TIMETABLE / PATH OFFER ............................................................................. 14
10. OBSERVATIONS / ACCEPTANCE ............................................................................... 14
11. POST-PROCESSING .................................................................................................... 15
12. FINAL OFFER ............................................................................................................... 15
13. ACTIVE TIMETABLE ..................................................................................................... 16
14. PATH MODIFICATION / PATH ALTERATION ............................................................... 16
1) Path Modification ................................................................................................................... 16
2) Path Alteration ....................................................................................................................... 18
15.
16.
17.
18.
19.
20.
PARTIAL OFFERS ........................................................................................................ 20
DEADLINES & MILESTONES (fully harmonised process) ............................................. 24
PCS REFERENCE HANDBOOK ................................................................................... 26
NATIONAL PATH REQUESTS ...................................................................................... 26
SUPPORT ..................................................................................................................... 27
REMARK ....................................................................................................................... 27
2
PCS Process Guidelines 2016
3
PCS Process Guidelines 2016
1. SET-UP OF PCS
Applicants can use PCS for all timetable phases. The date of submission of a path request to the
Infrastructure Managers/Allocation Bodies (IMs/ABs) and the requested timetable period will
decide if it is a path request placed in time for the next annual timetable, a late path request or an
ad-hoc path request.
Preparation of next annual timetable
Path
request
s for
Preparation of running timetable
Late path requests
for next annual TT



After deadline X-8
Until X-2
Paths are planned
on the basis of
leftover capacity
Path requests for the running timetable


New service that start in the running
timetable (X to X+12)
‘First come – First served’
2. INTRODUCTION
RailNetEurope (RNE) and its members will do their best to promote the use of PCS by companies
applying for train paths (hereafter: applicants).
Path requests will be accepted via PCS and answers will be communicated through PCS either in
addition to, or in replacement of, the traditional answering process already in use within the
national organisations.
The RNE Joint Office shall help applicants by providing them with functional and technical
information (e.g. training, e-learning, providing access to PCS, interfaces, processes, guidelines).
The use of PCS has to be made available to any applicant by any IMs/ABs for ad-hoc path
requests for the running timetable 2015 and requests for the 2016 annual timetable. The process
calendar for the timetable 2016 has been approved by RNE members and is valid both for
passenger and freight path applications.
PCS guidelines are applicable under the rules described in the RNE process handbooks for path
allocation (documents are available on RNE website: www.rne.eu). These guidelines describe the
main steps regarding international path requests which have to be fulfilled by applicants (either
applicants or authorized applicants) requesting a path involving several IMs/ABs and by IMs/ABs
itself.
4
PCS Process Guidelines 2016
3. NEW PCS FUNCTIONS (PCS Release 4.3)
With PCS release 4.3 new functions were implemented in PCS regarding
1)
2)
3)
4)
5)
6)
7)
8)
9)
Search and Report
Pre-constructed Product search
Template Manager
COBRA
Manage Dossier
Multiple frequency trains
Flex PaP
Network PaP
PaP Management
1) Search and Report
In case of dossier export, if the chosen format is PDF or Excel, then the user is able to select
the relevant part of the dossier to export:
» Dossier Information
» Applicants (RUs) section
» Infrastructure managers section
» Calendar
For each dossier report (Dossier Organizer, Dossier Register, Dossier Archiver and Dossier
Statistics) PCS will generate a summary sheet that contains the following information:
» Search criteria (for all report types, render the dossier search form as close to the UI)
» Number of dossiers found through the search
» Number of dossiers present in the report
2) Pre-constructed Product search
Each place where the RFCs are available as a filter, the numbers of the corridors were replaced
with the names of them such as:
» C01→Rhine-Alpine
» C02→North Sea-Mediterranean
» C03→Scandinavian-Mediterranean (but just from 2015, disabled)
» C04→Atlantic
» C05→Baltic-Adriatic (but just from 2015, now disabled)
» C06→Mediterranean
» C07→Orient/East-Med
» C08→North Sea-Baltic (but just from 2015, now disabled)
» C09→CS (Czech-Slovak)
It became possible to choose PaPs and insert to dossier during the Create New Dossier Wizard
and also possible to save the PaP search mask as a template for further application.
5
PCS Process Guidelines 2016
3) Template Manager
The Administration menu was extended with a new part “Template Manager”. The users are
able to maintain every kind of templates of their own that is available in PCS.
The possible templates are the following (please note that their availability is according to the
agency type):
» Common dossier parameters
» Dossier level parameters
» National IM parameters
» PaP search mask
» Parameter set code
4) COBRA
During the RNE technical meeting it is common that there are bilateral meetings between
neighbouring IMs to harmonize border times. To facilitate that workload the use of excel files is
still common. However the files that are used are often in a different format and layout,
depending to the IM that creates them and so two IMs still harmonize with different files, making
the work process even more complicated and not error-free.
Idea of the concept
The concept of Cobra is to support the border point harmonization for international trains.
However not every international train is part of PCS, but part of the Excel file. That is why a new
entity was created in PCS for Cobra which is called “Request”.
Request means a national path created by the IM based on his received national path requests
where he can add train parameters, calendar, border time and the neighbouring IM.
Therefore the Cobra menu has two parts from the aspect of border point type:
» PCS Border Points: contains the border (handover) points that are recognized automatically
by PCS based on the dossiers in the system.
» Non PCS Border Points: contains the requests created by the IMs.
Functions of the concept
» Dedicated page for handover points with special search functions
» PCS recognizes automatically the handover points (path sections)
» Possibility to harmonize only border times and indicate harmonization status with dedicated
acceptance indicators
» Possibility to create trains (requests) in PCS without existing dossier
» Possibility to merge requests
Concept works according to the following rules
» PCS Border Point is harmonized only if both neighbour IM set green (accepted) for their
acceptance indicators
» Non PCS Border Points harmonized only if the requests are merged together
» Every modification in the Cobra page on a PCS Border Point would result the same
modification in the dossier
» Cobra function is available only for IMs
» Border point harmonization is optional for the time being
Further improvements
6
PCS Process Guidelines 2016
»
»
Non PCS Border Point workflow should be improved according to process related reasons
Visibility and usability improvements are necessary (serious change can be expected only
with PCS Next Generation)
5) Manage Dossier
A couple new functions were introduced in order to help the user to be able to create a dossier
faster and promoting from one phase to another also be easier.
Helper functions related to RFC products
» Search for PaPs from Create New Dossier Wizard
» Insert all selected catalogues from the basket to the dossier in one step
» Edit inserted catalogues
» Request not available days in one step (see as Combined PaP/Tailor-made solution)
Combined PaP/Tailor-made solution
Last year when RUs were working with PaPs it happened several times that they had to create
a separated dossier for some days, because one PaP was not available on a day and using
PaPs in subsidiary timetables was not possible too.
Idea of concept
Based on the analysis and the experiences we defined the business case where the customer
requests the path by using PaP which does not cover all days of traffic for the train needed by
the customer.
We differ here between 3 cases:
» RU/Applicant requests the PaP (optionally with feeder/outflow path too), but indicates more
days of traffic than the PaPs contains
» RU/Applicant requests the PaP (optionally with feeder/outflow path too), but C-OSS cannot
offer all the days from the PaP – some specific days (e.g. one day in the timetable year)
» RU/Applicant requests the PaP (optionally with feeder/outflow path too), but the IM has
indicated on specific PaP sections that the availability is restricted according to maintenance
works
PCS then should guide the user through the process and help him to create subsidiary
timetables for the not available days.
Functions of the concept
In case the RU/Applicant would like to request a running day for a PaP which is originally not
covered by the PaP, PCS will offer the possibility to solve the situation with subsidiary timetables.
A new button will be enabled on the bottom of the calendar view called “Create Subsidiary TT
for the not available days”.
After the using the new functionality PCS will show a preview (Subsidiary overview) to the user
about the planned subsidiary structure and user can confirm that.
Concept works according to the following rules
» New concept is working only with Fix PaPs
» The generated subsidiaries are managed by PCS that is why the RU cannot adjust the
timetable where the PaP supposes to be there
» RUs can create and edit subsidiary timetables on the feeder/outflow sections
» In case of not available days IM has to offer timetable for subsidiary timetables where the
PaP is not available. Changing of acceptance indicator is also necessary
7
PCS Process Guidelines 2016
Further improvements
» In the future (probably with Major Release 2015) the feature will be extended to the Flex
PaPs as well
Make Observation
During the Observation phase the RUs would use the pre-defined Observation reasons for their
comment. Currently only pre-defined (by the PCS User Group) reasons are available in the list,
but it is planned that IMs should create the reason types as they do it for the National Parameters
too.
RUs can start working with the feature in Observation phase with clicking on a new button under
the comment field in the Dossier header “Make Observation”.
The new process of the Observation is the following:
1. At first the RU needs to select the IM involved by the observation (multi-choice)
2. Then the RU select the part of the dossier involved by the observation (dossier, main path
id or subsidiary path id), select the Section involved (all the section or particular section)
3. The RU preselects observations type (multi choice possible) previously setting in National
Parameters by each IM.
For instance:
o 01 Route not correct
o 02 Timetable not correct
o 03 Lack of date
o 04 Date not asked
o 05 Train parameter not in accordance with the request
o 06 Timetable not harmonized
o 07 Another reason
4. Set observation checkbox, if the comment is a “justified objection”
5. Then appears a field close to the observation type selected in order to enable the RU to
write its observation (free text)
6. The information should appears when triggering a report
After making the observation it will appear in a comment field for the time being, but in the future
with PCS Next Generation special notifications will be generated.
6) Multiple frequency trains
In the former PCS version it was possible only to copy a train once as a frequency train with
the flexibility to shift in departure time (+/-) and day shift (+/-). After the Major Release 2014 it
became possible to create several dossiers based on a parent dossier in one step using the
frequency train type as a composite relation.
7) Flex PaP
With PCS version 4.3 there is a new pre-constructed product available in the system, which is
called Flex PaP. In PCS Flex PaPs are always differentiated with blue colour from other
products.
Idea of concept
A Flex PaP is a semi-finalised path product with the following, most relevant characteristics:
8
PCS Process Guidelines 2016
»
»
»
»
»
Handover times at network borders are fix (and harmonised between IMs) and have to be
published
Origin, destination and intermediate locations of a PaP/PaP section: Possibility – but no
requirement – for IMs to communicate the times for its own locations (e.g. including stopping
or passage times)
Indication of standard journey times and parameters for each corridor section
IMs may limit the maximum number of stops and total stopping time per section or for the
entire network
X-8 to X-5 (path offer): Path planning by the IM can be done with a focus on optimal capacity
usage but respecting the agreed border times with the neighbour IMs
Functions of the concept
» Flex PaPs in PCS are represented with a new dossier type “Flex PaP”
» Flex PaPs can be created via PaP Importer and PaP Manager
» Possibility to change optional times at first and last path section
» Possibility to delete first/last path section, if it is not a Protected Border
» Possibility to change or delete optional times at intermediate Flex points
» Possibility to add new path sections for additional “intermediate locations” with times,
parameters, activities, calendars
» Possibility to add feeder/outflow sections
» Possibility to defining Flex PaP constraints (Standard journey time, Max number of stops,
Total stopping time)
Concept works according to the following rules
» Protected Border points and times are read only and mandatory
» Origin time/Destination time is mandatory, if operation point is reference point of the Flex
PaP dossier
» Intermediate Flex points (existing in respective Flex PaP) cannot be deleted
Further improvements
» In the future (probably with Major Release 2015) the feature will be adopted to the Combined
PaP/Tailor-made solution
8) Network PaP
“Network PaPs (in short “NetPaPs)” are PaPs designated to foster the optimal use of
infrastructure capacity and address the needs for capacity in specific geographical relations or
of market segments with special requirements in train path characteristics. They may be offered
on a single RFC or on two or more connected RFCs. “Network PaPs” consist of contiguous PaP
sections linked together and are identified by a special ID or marker in PaP catalogues and IT
tools.
Network PaP is not a new a product, it is only a layer created by RFCs for the PaPs that can
contain several PaPs (Fix or Flex).
9
PCS Process Guidelines 2016
9) PaP Management
Last year the only way to create PaPs in PCS was to use the Faul-Tolerant Excel Importer.
However creation of RFC Excel file for PCS Import takes a lot of manual effort for C-OSS and
for IM users. They either don’t have the complete RFC data when needed and they need to
change/adjust the data after the import.
In order to reduce the manual labour needed by the involved parties a new functionality is
provided by PCS: PaP Management. It is a wizard that provides the following capabilities:
» Bulk Editing (for creation, editing and deletion of PaP sections)
» Support of managing of both Fix and Flex PaPs
» Origin – Destination pairs editor
» Train parameter validation rules editor (per corridor/timetable period)
» Distances between PaP section editor (available as a separate function as well)
» Parameter set code editor (available as a separate function as well)
4. PCS PROCESS
Process steps for feasibility studies and path requests (placed on time and late requests) for the
next annual timetable and for the running timetable (ad-hoc requests) are unified:
Feasibility studies:
Annual timetable
(placed on time):
Annual timetable
(Late path
requests):
Running timetable
(ad-hoc requests):
5. OPEN A DOSSIER
The leading applicant may open a new dossier at any time of the year. It is of course also possible
to start a path request with an old or existing dossier from a previous timetable period. This is
possible by using the button ‘copy the dossier’ in the section ‘control’ (index ‘details’), or ‘Carry
forward’ function in ‘Search and Reports’ index. This means that the applicant is going to work with
a copy of the original file.
10
PCS Process Guidelines 2016
PCS function according to TAF-TSI requirements
1) Reference Point
In the RU-requested timetable, the selection of a reference point for planning is
mandatory! The reference point is a single point on the requested path, chosen by the
leading RU (leading applicant), which serves for specifying the direction of planning: forward
planning, planning from the middle, and backward planning. More precisely, the reference
point can be (and in the most cases it will be) the first point on the path, it can be a middle
point on the path (e.g. a border crossing) or it can be the last point on the path (e.g. a harbour
– the arrival time at the harbour should be synchronized with the departure time of a ship).
In contrast with the RU-requested timetable, in the IM timetable the reference point is set by
each IM, and, per default, is the first point of the particular network.
2) Calendar and Offset
For the reference point, the calendar is mandatory! Users have to set the calendar for this
operation point, and it will serve as reference calendar. On all other operation points of the
path, the offset in days will be automatically calculated by the system upon the given arrival
/ departure times. The system automatically recognises the midnight crossover.
Nevertheless, users are kindly asked to check the offset values given by the system and
make any necessary corrections.
3) Common parameters
For each operation point on the path (both RU-requested timetable as well as IM timetable), the input of train parameters (such as train weight, train length, locomotive type,
maximum speed and activity type) is mandatory! Mandatory fields are marked with a red
star (*) in the parameter input form.
4) RU-IM pairs
The system automatically sets the RU-IM pairs: all operation points are registered by the
different IMs. When an RU is chosen as the agency in charge of a particular operation point,
the system will make a pair of the RU and IM. This allows for better control of which IM the
RU will have to contact regarding its request (this feature is especially interesting for RU
companies with an open access to several IM networks).
5) Partial and full harmonisation
The system supports fully harmonised and partially harmonised Ad-Hoc (Short-Term)
Path Requests. Partially-harmonised requests are the requests which are issued even if not
all lights of the participating companies are set to green during the harmonisation. After
issuing the request, every RU-IM pair can have their own process layer, i.e. it can happen
that one RU-IM pair already has a dossier in the ‘Active Timetable’ and the neighbouring RUIM pair is still in the Path Elaboration phase. This approach speeds up the process for
requests issued at short notice.
After filling in the relevant data, the dossier can be moved to the Harmonisation phase. During this
period, involved applicants fill in their data and harmonise their requests. There is one part for the
harmonisation of path-related issues and a separate part for production-related issues (e.g. train
information, train composition, requested connections, through coaches).
11
PCS Process Guidelines 2016
If no support (consultation) at all is needed from the IMs/ABs, the leading applicant may switch the
dossier with all applicants light on green directly to  Path Request.
In case the applicants wish to receive a detailed feasibility study result, or simply consult the
IMs/ABs, the dossier must be moved to  Path Consulting Conference.
Operation points
Several users (applicants and IMs/ABs) will finalise their interface with PCS within the coming
months. In order to be able to transfer the data, some prerequisites are necessary. One of them
concerns the available operation points. Here are some hints regarding the choice of the correct
operation point:
 Column Type: ‘I’ = Infrastructure has to appear in this column for the relevant operation point
 Column Agency name: the name of the IM/AB in charge of this operation point has to be
listed
 Border/handover stations: these stations should be listed twice, firstly with the code/agency
name of the IM/AB in charge of the last path section until this point, secondly with the code
of the IM/AB in charge of the next path section. As some IMs/ABs accept PCS as formal path
request and allocation tool, the requested path section plays a major role. In order to bring a
path request placed in PCS in line with legal requirements, it is suggested to add the network
border operation points as well – even in cases where the train is not stopping there.
 Regarding automatic offset setting at the operation points, the special treatment of time
editing for border points / interchange stations has to be considered: it is recommended to
attribute only the arrival time to the incoming operation point on the border (belonging to the
first IM), and to attribute only the departure time to the outgoing operation point (belonging
to the second IM). By using this approach, the system will be able to set the appropriate
offset value in days for the border / interchange points.
Remark: if an error message occurs at an operation point entry in the timetable, the operation point
selection has to be opened and one of the proposed operation points has to be selected.
IM-specific parameters
For the same reason as with operation points – i.e. due to the increasing use of PCS requests in the
company systems of IMs/ABs – the train parameters for the line sections of the particular IM/AB
have to be entered. The correct input of train parameters in the requested timetable enables more
efficient path construction by IMs/ABs following the request via PCS. Therefore, the possibility to
input the IM-specific train parameters at the operation point level in the requested timetable is
provided and has to be used by authorised applicants. IM-specific parameters are configured or
updated in the PCS system by IMs/ABs at a certain period of the year for the next timetable period
(usually in October for the second but next timetable period).
The new functionality has been provided since PCS 3.0: IMs can specify a conditional field in the
IM-specific parameter list and conditional value. Hence, if the corresponding parameter value is
chosen by the applicant, the rest of the mandatory IM parameters can be ignored. For example, if
the parameter value indicates that the request has already been issued at the national level, then
the applicant does not have to fill in the same mandatory parameters twice for the national IM-specific
sections.
12
PCS Process Guidelines 2016
In the release PCS 4.0, for the requests for TT 2015, the dossier level IM specific parameters are
intensively used. These parameters are used for the information that is important on the request
level and not on the path section level, such as “customer number”. The IMs have the possibility to
use these parameters also as the conditional parameters. The manual for parameter configuration
for IMs can be found in the document “PCS IM Parameters Configuration Manual”.
The new features provided in the release PCS 4.0 for the usage and editing of the parameters can
be found in the document “PCS 4.0 - Quick Reference for Parameter Editing”.
6. PATH CONSULTING / FEASIBILITY STUDY
Feasibility studies make a significant contribution to the efficiency of the path allocation process for
the annual timetable and for ad-hoc paths. They allow applicants’ service plans to be checked for
feasibility and, as necessary, taken through further iterations.
After the dossier has been moved to Path Consulting, the conference mode will be activated
automatically, which allows applicants and IMs/ABs to share information and give advice on the
consistency of the request. This mode may be used for example during path consultation meetings
between applicants and IMs/ABs. IMs/ABs may give remarks in general on the path in question.
Afterwards the dossier may be moved back to Harmonisation either by the leading applicant or by
the coordinating IM/AB. The dossier is moved back also to Harmonisation in case there is insufficient
information.
If a detailed feasibility study with a concrete timetable is needed, the leading applicant has to submit
the Feasibility Study Request. IMs/ABs will conduct path studies and will try to give answers to path
feasibility study requests as soon as possible and in time, so that applicants may benefit from these
results either as a preparation for their regular meetings and information ex-change or for
immediately placing a path request. This procedure applies to feasibility studies for path requests
placed until Mid-January for the next annual timetable and for path requests for the running timetable.
Submissions to feasibility study requests for the annual timetable placed until Mid-January will be
switched directly to Path Study Elaboration Conference. If IMs/ABs intend to examine some possible
path solutions without involving the applicants too early, the coordinating IM/AB might switch off the
conference mode. The dossier will be moved back to conference mode automatically at the latest 8
days after the switch off. In case the negotiations between IMs/ABs have not been concluded within
these 8 days, the coordinating IM/AB may switch off the conference mode again. Nevertheless, the
leading applicant has always the possibility to withdraw the feasibility study request.
In this phase of the process (Feasibility Study Elaboration), the applicant can only access an archive
version of the dossier. In passenger traffic, the train composition may be changed by the applicant
at any time, as long as it has no influence on the characteristics of the path. In freight traffic, train
composition changes (e.g. weight, length or gauge (profile)) may require a new path study due to
the necessity of cancelling the ongoing study.
When studies by all IMs/ABs have been finalized and the dossier has been updated according to the
status of the request, the coordinating IM/AB releases the Feasibility Study Response. The leading
applicant can only accept an acknowledgement of the Feasibility Study Result in the dossier
(Acknowledge Feasibility Study). If doing so, it is moved to the Harmonisation mode. It might happen
that, for one reason or another, an IM/AB is not able to make a feasibility study (e.g. line closure). In
this case the light for this IM/AB will be red.
If the result of the feasibility study does not suit the requirements of the applicants, they may either
request a new feasibility study after having adapted the parameters for example (only if there is
enough time left), or they may place the request with their original requirements (copy RU timetable).
13
PCS Process Guidelines 2016
7. PATH REQUEST
If applicants wish to request the studied paths, the dossier status must be changed by the leading
applicant by using the button ‘Replace requested timetables by IM timetables’.
The leading applicant must ensure that all participants agree with the request. This process is
controlled by making sure that all path-related ‘lights’ are green. Unless all lights are green it will not
be possible to switch the path request to the next stage.
Requests for the running timetable 2015 will be classified by the system as ad-hoc path request and
will be handled by the IMs/ABs on the base of ‘first in – first served’ in case of a path conflict.
Requests for the annual timetable 2016 placed at the latest on 13th April 2015 will be handled as
path requests placed on time. If a request is handed over to the IMs/ABs between 14th April and 12
October 2015, the system will classify it automatically as late path request.
It is always possible for the leading applicant to withdraw a path request.
8. PATH ELABORATION
After having checked the consistency of the application, the coordinating IM/AB changes the dossier
status from Path Request to Path Elaboration mode. This action allows all IMs/ABs to work on the
design of the draft timetable. During this phase no dossier may be modified by any applicant and no
applicant may see the working area of the IMs/ABs (IMs timetable) until the coordinating IM/AB
switches the dossier either to the  Draft Timetable phase for path requests placed on time or to 
Path offer (late request offer and ad-hoc request offer).
9. DRAFT TIMETABLE / PATH OFFER
Path requests placed on time until the 2nd Monday in April: all agreed and harmonised dossiers with
all green lights from IMs/ABs will be switched automatically at internationally agreed deadline from
Path Elaboration to Draft Timetable.
Please note that dossiers with yellow lights, i.e. dossiers with path conflicts unsolved in due time,
will not be switched automatically. Due to the “Partial offer” function there will be no conference mode
in Observations as long as the “Partial offer” function is active. Please see chapter 14 for details of
the “Partial offer” function.
Late path requests: the coordinating IM/AB will switch manually agreed and harmonised dossiers
with all green lights from IMs/ABs from Path Elaboration to Late Request (path) Offer.
Ad-hoc path requests: dossiers with all IM/AB lights on green will be switched automatically (every
night at 23:00 h) to Ad-hoc Request (path) Offer.
All lights of the applicants will be changed to blue when shifting the dossier in  Observations or 
Acceptance.
10. OBSERVATIONS / ACCEPTANCE
Path requests placed on time until the 2nd Monday in April: Applicants may make Observations
regarding the proposed draft timetable in the available field. After these steps no observation can be
14
PCS Process Guidelines 2016
made anymore. Afterwards the dossier will be switched to  Post-Processing by the leading
applicant manually or automatically on the defined deadline.
Late and ad-hoc path requests: Applicants’ acceptance should be given within 5 working days for
late path requests and 72 hours for ad-hoc path requests after receipt of the path offer. If the
applicants do not have any remarks regarding the path offer, the leading applicant may switch the
dossier directly to  Active Timetable in order to speed up the process. By doing so, all involved
applicants consider the path offer as  Final offer which they all accept. As a consequence, two
phases – Observations and Final offer – will be skipped. It has to be mentioned that the system does
not take any automatic actions related to the time limits; the 5 days and/or 72 hours should serve as
an organisational proposal.
In case the path offer does not correspond with the expectation of the applicants, the leading
applicant may make remarks. This dossier will be switched to  Post-Processing. This is possible
only if applicants’ lights are at least green, yellow or red.
If an applicant puts the light on ‘red’, they should indicate their reason for the need to adapt the path
offer.
11. POST-PROCESSING
IMs/ABs prepare the final answers to the customers. In this phase, IMs/ABs may optimise the train
path. Once all IMs/ABs have finished their final adjustments, the dossier for Path requests placed
on time until the 2nd Monday in April is moved either manually or automatically to the  Final offer
mode by the coordinating IM/AB.
In case an IM/AB is not in a position to submit a final offer for the annual timetable, it is considered
as a Path rejection. The system will then forward a pdf file of the relevant PCS dossier to the
appropriate Regulatory Body on behalf of the responsible IM/AB. This procedure is based on an
agreement between the European Commission and the European Regulatory Bodies on the one
side, and RNE and its members on the other side.
If in a dossier not all IMs/ABs lights are on green on time (e.g. due to still unsolved conflicts), national
regulations for submitting a final offer will be applied.
Late & Ad-hoc path requests: the system checks regularly the status of the acceptance indicators of
the dossiers in this phase and transfers those dossiers every night at 23:00 h to  Final offer, where
all IMs/ABs light are on green.
12. FINAL OFFER
Path requests placed on time until the 2nd Monday in April: all involved applicants accept the final
offer within 5 working days by setting all lights on green. Late and ad-hoc path requests: if a dossier
is moved from path acceptance directly to  Active Timetable, the Final offer is just a milestone. If
the dossier has been moved from Post-Processing directly to this phase, all involved applicants
accept the Final offer within the deadlines mentioned in Sector 9 by setting all lights on green. In
order to keep the dossier ‘alive’ after the path construction and once the final offer has been
accepted, all dossiers for all processes with all applicants’ lights on green will be switched either
manually or automatically (the system checks regularly (every night) the status of the acceptance
indicators of the dossiers at 23:00) in the next phase  Active Timetable (see also Sector 13).
15
PCS Process Guidelines 2016
13. ACTIVE TIMETABLE
In this phase, applicants and IMs/ABs may use the dossier for adjustments or modifications of
various elements (e.g. changes in rolling stock or path due to short-notice maintenance work).
14. PATH MODIFICATION / PATH ALTERATION
Based on TAF/TAP-TSI requirements, two new functions for changing dossiers in “Active Timetable”
were added to PCS since PCS Release 3.1:


Path Modification for changes triggered by RUs and
Path Alteration for changes triggered by IMs.
The process and dossier phases are described in sections 13.1 and 13.2 below. For further details,
please see the PCS Quick Reference for Path Modification and Path Alteration.
1) Path Modification
Based on the path agreement, a RU intends to change some elements of the train or the timetable
that could impact the path details after the path has been booked. Such modifications can be
requested for one day, several days or all remaining booked days.
The preconditions for entering the Path Modification process are:
 The user belongs to RU (any RU involved in the dossier, not only the leading one)
 The dossier is in the phase “Active Timetable” (the process type of the dossier, i.e. New, Late or
Ad-Hoc Path Request does not matter)
The system requires that the user chooses one of the IM-timetables where the modification has to
be made. The IM-timetable is used because in the “Active Timetable” phase the IM-timetable
represents the state of the contract between RUs and IMs.
The RU user has to indicate which path/timetable modification(s) shall be applied to the dossier:
 Additional days
 Cancellation of days
 Modification of departure or arrival time
 Modification of route
 Modification of train parameters
 Border/Handover/Interchange times adaptation
It is important to mention that the RU user has the possibility to indicate which of the other involved
RU-IM pairs are affected. “Affected” means that the acceptance indicators (traffic lights) of the
selected RU-IM pair become YELLOW. If no operational days are touched or if no parameters / times
on the border stations are changed, the traffic lights of all involved RU-IM pairs remain green.
NOTE: The term “initiator-RU” is used for the RU that has started the process. The initiator-RU is
responsible in this process for changing the phases (phase promotion) in the same way as the
leading RU is responsible for that in other process types. This differs from other process types where
only the leading RU can start the process and change the phases. Instead of “involved agencies”
the term “affected agencies” is used since not all involved agencies are always affected by the
particular path modification. The term “pair IM” is used to indicate the IM of the RU-IM pair to which
the Path Modification Request is intended.
16
PCS Process Guidelines 2016
NOTE: The user has the possibility to choose between the options for replacement and adjustment
of the IM timetable. If the replacement is chosen, after the successful finalisation of the process, the
IM timetable from the phase of Active Timetable is replaced with the result of the Path Modification
process. If the adjustment is chosen, the user has to indicate the validity period of the adjustment
of the timetable. For example, only in one month of the whole timetable year for a train, the
locomotive change has to be applied on one national section. In that case, the validity period for the
change is entered and the original timetable from Active Timetable is kept, but without the month
indicated in the validity period. The new IM timetable containing the change will be added as an
adjustment of the “running” timetable. The “adjustment” timetables are interpreted by the system as
Subsidiary timetables since new release PCS 4.0.
Dossier phase – Path Modification Conference
The Dossier can be viewed and amended by all the participating RU’s (train composition, requested
RU-timetable) and IMs (comments, IM-timetable). Within the requested RU-timetable, each RU can
only make changes in the section assigned to them. Within the IM-timetable, each IM can only make
changes in the section assigned to them.
The aim of this stage of the process is for all affected RU’s to give their approval to the Dossier and
that the initiator-RU can place Path Modification Request.
Dossier phase – Path Modification Request
The initiator-RU passes on the Dossier as a Path Modification Request to its pair IM. This generally
happens when all the cooperating RU’s have given their approval (green light).
In this phase the RU’s cannot change the requested timetable and some other Dossier data any
more.
The pair IM receives the Path Modification Request for checking. The Path Modification Request can
be withdrawn by an initiator-RU. In this case the Dossier is withdrawn entirely and any timetables
created for the modification will be deleted. The dossier is brought back to the initial state, to “Active
Timetable”. If the Path Modification Request indicates major modification of the path, the pair IM can
decide whether the Path Modification Request should be rejected with the indication that the
completely new Ad-Hoc Path Request has to be placed.
If the Path Modification is rejected, the IM must indicate the reason for the rejection. The IM has one
of the following choices to indicate:
 No construction possible
 Conflict with other kind of traffic
 Train parameters not fitting to the path
 Other
In that case, the dossier is returned to “Active Timetable”, and the dossier history contains the record
about the rejected Path Modification Request. The dossier is brought back to the state it had before
starting the Path Modification Conference.
Dossier phase – Path Modification Elaboration
If the Request is estimated as proper by the pair IM, the pair IM should release Path Modification
Elaboration.
17
PCS Process Guidelines 2016
IM´s are supposed to elaborate the Path Modification request. All IMs have write-rights. RUs can
see the IM timetable, but they don't have write-rights on RU timetable. If all IM traffic lights
(acceptance indicators) are green, the pair IM can issue Path Modification Offer.
Dossier phase – Path Modification Offer
The affected and initiator RU traffic lights (acceptance indicators) are set back to yellow. If all affected
and initiator RUs set the lights to green, the initiator RU can accept the offer. The initiator RU can
reject the offer. In that case, the initiator RU has to indicate one of the following reasons for rejection:
 Difference between request and offer not acceptable concerning
-
Days of service
Times
Stops
Other
If the offer was rejected, the dossier is brought back to “Active Timetable”; to the state it had before
the Path Modification Conference was started (all new timetables that were created during the
modification process are removed). The system places a record in the dossier history that the
dossier has been rejected.
2) Path Alteration
Based on the path agreement, the RU can expect that a booked path is available up to its
operation. However, if an event occurs (e.g. disruption to the path) prior to the start of the operation
and the booked path from either the long-term (working timetable) or short term planning is no
longer available, the IM must inform the RU as soon as this fact is known.
A cause of the event (e.g. an interruption on the path) needs to be indicated to the RU. This can
happen at any time between the moment the path is booked and the departure of the train. The IM
is obliged to send an alternative proposal together with the indication that the path is not available.
If an alternative is not yet available, the IM must send the proposal as soon as possible.
This path alteration may refer to one single day, several days or all remaining days. It is also
possible to alter the whole path section or just a part of it.
The preconditions for entering the Path Alteration process are:
 The user belongs to IM (any IM involved in dossier, not only the leading one)
 The dossier is in the phase “Active Timetable” (the process type of the dossier, i.e. New, Late
or Ad-Hoc Path Request does not matter)
The IM user has to indicate which path/timetable modification(s) shall be applied to the dossier:
 Cancellation of days
 Modification of departure or arrival time
 Modification of route
 Modification of train parameters
 Path not available
 Border/Handover/Interchange times adaptation
It is important to mention that the IM user has the possibility to indicate which of the other involved
RU-IM pairs are affected. “Affected” means that the acceptance indicators (traffic lights) of the RU18
PCS Process Guidelines 2016
IM pair become YELLOW. If no operational days are touched or if no parameters / times on the
border stations are changed, the traffic lights of all involved RU-IM pairs remain green.
NOTE: The term “initiator-IM” is used for the IM that has started the process. The initiator-IM is
responsible in this process for changing the phases (phase promotion) in the same way as the
leading IM is responsible for that in other process types. This differs from other process types where
only the leading IM can change the phases. Instead of “involved agencies” the term “affected
agencies” is used since not all involved agencies are always affected by the particular path alteration.
The term “pair RU” is used to indicate the RU of the RU-IM pair to which the Path Alteration Request
is intended.
NOTE: The user has the possibility to choose between the options for replacement and adjustment
of the IM timetable. If the replacement is chosen, after the successful finalisation of the process, the
IM timetable from the phase of Active Timetable is replaced with the result of the Path Alteration
process. If the adjustment is chosen, the user has to indicate the validity period of the adjustment
of the timetable. For example, only in one month of the whole timetable year for a train, the route
has to be changed on one national section. In that case, the validity period for the change is entered
and the original timetable from Active Timetable is kept, but without the month indicated in the validity
period. The new IM timetable containing the change will be added as an adjustment of the “running”
timetable. The “adjustment” timetables are interpreted by the system as Subsidiary timetables since
new release PCS 4.0.
Dossier phase – Path Alteration Conference
The Dossier can be viewed and amended by all the participating RU’s (train composition, requested
RU-timetable) and IMs (comments, IM-timetable). Within the requested RU-timetable, each RU can
only make changes in the section assigned to them. Within the IM-timetable, each IM can only make
changes in the section assigned to them.
The aim of this stage of the process is for all affected IM’s to give their approval to the Dossier and
that the initiator-IM can place Path Alteration Offer.
Dossier phase – Path Alteration Offer
The initiator-IM passes on the Dossier as a Path Alteration Offer to its pair RU. This generally
happens when all the cooperating IM’s have given their approval (green light).
In this phase the RU’s cannot change the requested timetable and some other Dossier data any
more.
The IM timetable that was made in Path Alteration Conference remains for further processing. The
Path Alteration Offer can be withdrawn by an initiator-IM. In this case the Dossier is withdrawn
entirely. Then any timetables created for the alteration will be deleted and the dossier is brought
back to the initial state, to “Active Timetable”.
If the Path Alteration Offer is rejected, the RU must indicate the reason for the rejection. The RU has
one of the following choices to indicate:
 Difference between request and offer not acceptable:
-
Days of service
Times
Stops
Other
19
PCS Process Guidelines 2016
In that case, the dossier is returned to “Active Timetable”, and the dossier history contains the record
about the rejected Path Alteration Offer. The dossier is brought back to the state it had before starting
the Path Alteration Conference (the IM timetable will not contain any changes made during the Path
Alteration Conference, i.e. it will contain the same information as it had in the phase “Active
Timetable” before starting the process).
NOTE: If the Path Alteration Offer is the result of an unexpected event (e.g. a line blocked by a
landslide), the rejection of the Path Alteration Offer may result in the impossibility to run the train in
case no other alternative is available.
15. PARTIAL OFFERS
(to be continued in 2015 for TT 2016)
Background
Basically it is not possible in the New Path Request process to switch a PCS dossier to the next
phase (e.g. from path elaboration to draft timetable/Observations or from Post processing to Final
offer) if not all IMs have set their acceptance indicators to Green.
But it may happen that an IM is forced by national legislation to send draft or final offers to RUs at
the published deadlines, even if one or more involved IMs have not yet finished the Path
elaboration or the Post processing phase. It such cases the IMs having completed Path elaboration
or Post processing are not able to send any offers by PCS and will violate their national legislation.
The current possibility with Observation conference, allowing IMs to edit the IM timetable after the
Path elaboration phase in order to finish their work, is not satisfactory. With Observation
conference there is no formal offer for the IMs who have finished the dossier for the RU/IM pairs
where they are involved.
Decision of the RNE General Assembly
All RNE members agreed that customers expect complete offers provided at the published
deadlines and the primary objective of all activities is to meet these deadlines.
In order to avoid that RNE members have to violate national legislation, the RNE General
Assembly approved on 16 May 2013 “the implementation of the ‘Partial Offer’ function in PCS for
the annual timetabling process as an interim solution for two years and only if legal prescriptions
make it necessary”.
Partial offers in the New Path Request process
The new function should be based on the functions available in PCS for partially harmonised
requests in the Ad-hoc/short term process. The details of the interim solution allowing partial offers
in New Path Request process are described below.
Path elaboration phase
20
PCS Process Guidelines 2016
IMs of RU-IM pairs who have finished Path elaboration will set their acceptance indicators to
Green.
If the deadline for draft offers is reached and not all IMs have set their acceptance indicators to
Green, an IM being forced by national legislation to send the offer may start the partial offer
process.
a) Click button “Switch to partial offer”
b) A mandatory comments field opens. Enter information about the legal requirement for
switching the dossier to partial offer now, without all IM acceptance indicators Green.
c) Click button “Send draft offer”
The complete dossier will be visible for leading RU and involved RUs, allowing them to see RU/IM
pairs ready (acceptance indicators Green) and pairs with IMs not yet ready. In fact, RU/IM pairs of
the same dossier may be now in different phases:


RU/IM pair(s) with acceptance indicators Green: Draft timetable/Observations phase
RU/IM pair(s) with acceptance indicators not Green: Path elaboration phase
Note: A warning will be shown on pdf-exports or printouts of PCS dossiers in partial offer
for identification of these dossiers.
After one IM has activated partial offer function IMs of other RU/IM pairs who have finished their
part of the dossier may set their acceptance indicators to Green. These pairs will be automatically
switched to the Draft timetable/Observations phase.
An IM of a pair not ready for draft offers at the published deadline according to the RNE timetabling
calendar (acceptance indicator still Yellow or Red) is given one week after the published deadline
for finishing the dossier and switching his acceptance indicator to Green.
Published deadline for draft offers for Timetable 2016 is 6 July 2015
Note: For TT period 2016 draft offers shall be ready at noon of 6 July. This enables IMs to
check the status of their dossiers and initiate Partial offers prior to reaching the deadline at
midnight. If an IM is not ready at noon but will finish the dossier in time, he shall inform the
other IMs of the dossier. The automatic switching of dossiers with all acceptance indicators
Green will be active.
If the IM does not finish the dossier within the additional week, PCS will not prevent the IM from
finalising the draft offer later. But any additional delay may cause the applicant to reject the draft
offer.
Draft timetable (milestone)
With all IM acceptance indicators set to Green, the Path elaboration phase is completed.
Remember that Draft timetable is no formal phase but only a milestone and the dossiers are
automatically moved to the Observations phase.
21
PCS Process Guidelines 2016
Observations phase
RUs may check the draft offers and may make comments. The Conference Mode in Observations
will be deactivated as long as the Partial offer function is active in PCS. Please note that late
finalisation of dossiers in Partial offer may result in late answers by RUs. Dossiers received in
partial offer mode may be switched by RUs to post processing independently for each RU/IM pair.
Post processing phase
In the Post processing phase it may again be necessary to use the partial offer function for final
offers and the process will follow the same rules and use the same PCS functions.
Note: The partial offer function may be necessary once or twice for the same dossier in the
New Path Request process.
a) Partial offer necessary for draft offer and for final offers (with the same or with another
IM needing the partial offer function)
b) Partial offer necessary for draft offer only or for final offer only
IMs of RU-IM pairs having finished Post processing set their acceptance indicators to Green.
If the deadline for final offers is reached and not all IMs have set their acceptance indicators to
Green, an IM being forced by national legislation to send the offer may start the partial offer
process.
a) Click button “Switch to partial offer”
b) A mandatory comments field opens. Enter information about the legal requirement for
switching the dossier to partial offer now, without all IM acceptance indicators Green.
c) Click button “Send final offer”
The complete dossier will be visible for leading RU and involved RUs, allowing them to see RU/IM
pairs ready (acceptance indicators Green) and pairs with IMs not yet ready. In fact, RU/IM pairs of
the same dossier may be now in different phases:


RU/IM pair(s) with acceptance indicators Green: Final offer phase
RU/IM pair(s) with acceptance indicators not Green: Post processing phase
After one IM has activated partial offer function IMs of other RU/IM pairs who have finished their
part of the dossier may set their acceptance indicators to Green. These pairs will be automatically
switched to the Final offer phase.
An IM of a pair not ready for final offers at the published deadline according to the RNE timetabling
calendar (acceptance indicator still Yellow or Red) is given one week after the published deadline
for finishing the dossier and switching his acceptance indicator to Green.
Published deadline for final offers for Timetable 2016 is 24 August 2015
Note: For TT period 2016 final offers shall be ready at noon of 24 August. This enables IMs
to check the status of their dossiers and initiate Partial offers prior to reaching the deadline
at midnight. If an IM is not ready at noon but will finish the dossier in time, he shall inform
22
PCS Process Guidelines 2016
the other IMs of the dossier. The automatic switching of dossiers with all acceptance
indicators Green will be active.
If the IM does not finish the dossier within the additional week, PCS will not prevent the IMs from
finalising the final offer later. But this additional delay may cause the applicant to reject the final
offer.
Final offer phase
RUs may check the final offers and they may accept or reject the final offers. Please note again
that late finalisation of dossiers in Final offer may result in late answers by RUs.
Dossiers in Partial offer may only be switched harmonised to Active timetable. This is to prevent
dossier with one part still in post processing while other parts are already in Active timetable,
allowing starting the path modification process.
Once RUs have set their acceptance indicators to Green in a dossier in Partial offer mode and in
the Final offer phase, it is not possible to change again to Yellow or Red.
Active timetable phase
Dossiers switched harmonised to Active timetable will follow the normal PCS processes.
23
PCS Process Guidelines 2016
16. DEADLINES & MILESTONES (fully harmonised process)
12/01/2015: Finalisation/publication of Pre-arranged Paths (PaPs) and Catalogue Paths
19/01/2015 at 23:59 (limit for placing feasibility study requests for timetable 2016):
Automatically switching all dossiers which are in Path Consulting Conference to Feasibility Study
Elaboration Conference – applicants lights must be green or at least yellow.
20/01/2015 at 23:59: Automatically switching all dossiers in Path Consulting Conference to
Harmonisation if at least one applicant’s light is red of blue.
Note: The deadline of 8/15 days of no activity causing an automatic transfer from Path Consulting
Conference to Harmonisation is switched off until 20/01/2015 and it is switched on again after
20/01/2015.
16/03/2015 at 23.59 (limit for answering path study requests): Automatically switching all
dossiers which are in Feasibility Study Elaboration Conference to Harmonisation – IMs/ABs lights
may be green, yellow, red or blue (IMPORTANT: the Feasibility Study Result will be treated in the
system as ‘acknowledged’).
In case a feasibility study cannot be completed by the IM/AB in due time, and the dossier should not
yet automatically be switched to Harmonisation on 16/03/2015 at 23.59 h, the IM/AB has to switch
this dossier manually from conference to Feasibility Study Elaboration before 16/03/2015 at 23.59
h. Afterwards, the switching from Feasibility Study Elaboration to Feasibility Study Result has to be
done manually by the coordinating IM/AB.
Between 17/03/2015 and 21/03/2015, every night at 23:59: Automatically switching all dossiers
which are in Feasibility Study Result to Harmonisation (IMPORTANT: the Feasibility Study Result
will be treated in the system as ‘acknowledged’).
13/04/2015, at 03:00 and 23:00: All dossiers in the Harmonisation phase with all applicants (path
related) lights on green will be switched automatically to the Path Request phase.
If there are any remaining dossiers in the Path Consulting Conference, they will be transferred to
Harmonisation at 04:00 on 13/04/2015. Note: for the dossiers that have already ‘acknowledged’ the
Feasibility Study Result only. With this approach, the leading RUs will be able to check the dossiers
once more in the Harmonisation phase for the Path Request, and the dossiers will be considered on
automatic promotion at 23:00 h on the same day. Dossiers that have just started the Path Consulting
Conference will be kept in Path Consulting Conference.
The leading applicant must ensure that all participants agree with the request. This process is
controlled by making sure that all ‘lights’ are green. Unless all lights are green it will not be possible
to switch the dossier automatically to path request.
14/04/2015, at 00:01: All dossiers submitted after this deadline will be treated by the IMs/ABs as
late path requests. The system checks regularly (every night) the status of the acceptance indicators
of the dossiers and automatically transfers those dossiers where all applicants’ lights are on green
at 23:00 h to late path request until 12/10/2015.
24
PCS Process Guidelines 2016
14/04/2015: After having checked the consistency of the application, the coordinating IM/AB changes
the dossier status from Path Request to Path Elaboration mode for requests placed on time.
Subject to possible change: It is discussed to change the Path Request Phase to a Milestone. If
this will be decided, no manual switching from Path Request to Path elaboration by IMs/ABs will be
necessary. All dossiers in the Harmonisation Phase being manually promoted by the applicant or
automatically by PCS will be directly switched from Harmonisation via Path Request to the Path
Elaboration Phase.
Between 14/04/2015 and 28/04/2015, Corridor OSSs of the Rail Freight Corridors will reserve Prearranged paths (PaPs) and will reserve accepted alternative PaPs.
By 17/06/2015: In order to fulfil the harmonisation process during the RNE Technical Meeting, all
IMs/ABs have to guarantee the availability of the constructed/designed train path.
6/07/2015, at 02:00 and 23.00: All agreed and harmonised dossiers with all green lights will be
switched automatically from Path Elaboration via Draft Timetable to Observations. After this
deadline, the coordinating IM/AB may switch dossiers with all green lights manually. All lights of the
applicants will be changed to blue in Observations.
From 7/07/2015 to 7/08/2015 the system will check every night at 23.00 if there are any dossiers
with all IMs/ABs lights on green and will switch them directly from Path Elaboration to Observations.
From 7/07/2015 to 7/08/2015: applicants may make observations in the available field.
7/08/2015, at 23:00: At the end of this phase, all dossiers will be switched automatically from
Observations to Post-Processing mode on the deadline, independently of the colours of the lights of
the applicants (blue, green, yellow or red). Important: Only dossiers which have been switched to
Observations until 6/07/2015 (automatically or manually) will be automatically switched to PostProcessing. The dossier can also be switched manually to Post-Processing by the leading applicant
before the deadline. The IM/AB lights will change to blue in Post-Processing.
Between 8/08/2015 and 24/08/2015, IMs/ABs prepares the final answers to the customers. In this
phase, IMs/ABs may optimise the train path. Once all IMs/ABs have finished their final adjustments,
the dossier is moved to the Final Offer mode. From 11/08/2015 till 6/09/2015 at 23:00, the system
checks the status of the acceptance indicators of the dossiers and transfers those dossiers that have
all IMs/ABs light on green automatically to Final Offer.
Between 25/08/2015 and 7/09/2015, all involved applicants accept the Final offer by setting all
lights on green. In order to keep the dossier ‘alive’ after the construction of the annual timetable
once the final offer has been accepted, all dossiers with all applicants’ lights on green will be
switched automatically in the next phase Active Timetable from 26/08/2015 to 13/09/2015 at
02:00. This allows any participant to work on the dossier at any time. Participants also have read
and write access to the dossier.
Of course, applicants have the possibility either to accept or to refuse (with reds lights) the Final
offer. After acceptance of the offer, the formal acceptance is filed in the PCS archive.
12/10/2015 at 23:59: Latest time to place late path requests for the annual timetable 2016.
25
PCS Process Guidelines 2016
13/12/2015: Start of timetable 2016
13/10/2015 at 00:01: First moment for placing ad-hoc path requests for the running timetable 2016.
The system regularly checks (every night) the status of the acceptance indicators of the dossiers
and automatically transfers those dossiers where all applicants’ lights are on green at 23:00 to adhoc path request.
17. PCS REFERENCE HANDBOOK
The PCS Reference Handbooks serves as the detailed user manuals and process descriptions for
working
with
PCS.
Online
access
to
the
handbooks
is
available
via
http://pcs.rne.eu/tl_files/RNE_Upload/PCS/2013/RNE-PCS-R4.0_Reference-Manual-Index.pdf.
The original reference handbook (previously known as “Orange Book”) is replaced by the separated
manuals dedicated to the specific topics, like PaP-handling, Main/Subsidiary procedure or
Parameter Editing.
18. NATIONAL PATH REQUESTS
In cases where path requests are submitted by the applicant(s) exclusively through national
processes for each national section of a given path (i.e. without PCS) to each IM/AB separately
(generally on one network until the border station), IMs/ABs will not be able to guarantee a coordination of these separate path applications and to provide answers within the common calendar.
This situation does not arise, if it has been agreed that the involved partners are using the PCS
Integration Platform.
In cases where national requests end or start at a border, IMs/ABs will provide answers according
to the national calendar, and for the operating days requested country by country, according to the
following principles:
Arrival time from network A at the border station not later than the requested time
Departure time from the border station to network A not earlier than the requested time
26
PCS Process Guidelines 2016
19. SUPPORT
Service & Support
RailNetEurope Service Desk:
Mon – Thu: 09:00 – 16:00; Fri: 09:00 – 15:00
Phone: +43 1 907 62 72 25
E-mail: support.pcs@rne.eu
(Mail support: 24/7 for e-mails in English, max. response time 4h)
Should you have any questions about the timetable process please contact:
E-mail: philipp.koiser@rne.eu
Phone: +43 1 907 62 72 15
Should you have any technical questions or questions about access to
PCS, please contact:
E-mail: mate.bak@rne.eu
Phone: +43 1 907 62 72 24
For questions regarding PCS training, handbooks and future developments
please contact:
E-mail: jorge.campo@rne.eu
Phone: +43 1 907 62 72 24
You are welcome to try our eLearning programme as well!
http://www.rne.eu/index.php/pcs_elearning.html
20. REMARK
All times mentioned in this document refer to the ‘Central European Time’ (CET).
27