How to accept general terms and conditions of RFCs in PCS

Content

Introduction

In case a freight Applicant selects a PaP into its dossier in order to be able to submit Path Request, every involved Applicant has to accept the general terms and conditions of the corridor. In case of multi corridor request, the Applicant has to do it as many times as many corridors exists and it uses in the dossier. The acceptance is valid for one timetable period. In a new timetable period, the Applicant should accept the terms again. Applicant should accept it per corridor and per dossier.

Acceptance of general terms and conditions should be done by the Applicants in the following way:

SectionApplicantAcceptance
FeederApplicant1Not necessary
PaP - RFC1Applicant2Necessary for RFC1
PaP - RFC2Applicant3Necessary for RFC2
OutflowApplicant4Not necessary

How to do it in PCS

Control

If the Applicant has PaPs in the dossier and it didn't accept yet the General terms and conditions (GTC) of the particular corridor, it will see a new type of warning below the acceptance indicators. Without the acceptance the Applicant won't be able to set green light in the dossier.

Control view of GTC

If the Applicant already accepted the GTC, the warning won't be visible anymore in the Control. When the user clicks on the link, the system will open a new view in Administration.

Administration

In the administration page, the user can search the states of acceptance per timetable periods. PCS will show all the used corridors on the screen.

Administration collapsed view

Selecting one of the used corridors user can accept or reject the GTC.

Administration extended view

Acceptance/Rejection

Any user can either accept or reject the GTC of the particular corridor, who has editing rights in PCS. As it was written above in order to submit path request (or actually to set green light) the Applicant has to accept the GTC. If the Applicant already accepted the GTC, but it changed its opinion and would like to reject, it's also possible. An applicant can reject GTC only if it didn't submit any path request yet for the particular timetable period and corridor. If the user still likes to reject GTC, he should withdraw all submitted requests.