Table of contents
1. Introduction
This document describes in detail the report fields in the generated PAMT report. It does not describe how to use the PAMT search or how to generate the report. These are described in other documents, please check out the “How To” user guides.
2. Report (export) structure
The downloaded PAMT report starts with the header columns which consist of 3 merged cells.
Below the header, the data is presented. The length of the report depends on the:
- imported PaPs for the C-OSS manager
- number of requests placed by the applicants for the specific PaP section.
2.1 Column descriptions:
- Dossier Summary Line: it works like a header and is marked with the letter “X”, representing sections if the dossier contains several PaP requests eg.: AGE RFC Bp training section contains 2 PaP requests
- Dossier Name: name of the dossier
- If the dossier is a:
- PaP dossier: PaP origin-destination pair defined by the C-OSS manager
- “Normal Dossier”: defined by the creator of the dossier
- If the dossier is a:
- PaP intended for: process type of the PaP when it was published
- Process type: information for the intended usage of the PaP. if the PaP is not requested by the applicants it shows “PreArranged Path”
- Dossier name: name of the dossier given by the creator
- Dossier Id: system-generated number once the dossier is created, identification of the dossier
- International train number: it shows the international train number if it was filled
- Path Request Date: date of the submission of the path request
- Path Id: system-generated number once the dossier is created, each Patch has its own identification number, number field without decimals
- Sub-path title: title of the sub-path
- RFC: involved RFCs
- Direction: direction between the origin-destination. It can be S-N, N-S, E-W or W-E
- Responsible Applicant
- Leading Applicant: the Applicant who has the leading role in the dossier
- Responsible IM
- PaP Dossier Id: system-generated number, identification of the PaP dossier
- Alternative PaP Id’: alternative PaP offered by the C-OSS manager to replace existing PaP in the alternative offer branch phases
- PaP Id: identification of the PaP origin-destination pair assigned by the C-OSS manager, number field without decimals
- Request Status: it shows the PaP request status
- Allocation Status: it shows the PaP origin-destination pair allocation status under the dossier life-cycle.
- Feeder Points: location/s where a non-corridor path enters the corridor
- PaP Origin: the PaP request origin point
- PaP Origin Arrival: the PaP request the origin point arrival time
- PaP Origin Departure: PaP request origin point departure time
- PaP Destination: PaP request destination point
- PaP Destination Arrival: PaP request destination point arrival time
- PaP Destination Departure: PaP request destination point departure time
- Outflow Points: location/s where a non-corridor path exists in the corridor
- Distance: length between two location points in km. number field with 2 decimals
- Running Days: PaP request published available days, number field without decimals
- K-Value: described below in the table, number field with 2 decimals
- Circulation Days: weekly circulation days where weekdays are presented in numbers
3. Distance calculation
K-Value | NetPaP K-Value | K-Value Total Dossier | |
Summary | Sum (distance of PaP request)xrunning day (reference point of the Applicant main timetable) | Sum (distance of NetPaP request)xrunning day (reference point of the Applicant main timetable) | Sum (K-Value of PaP request) |
PaP Requests | Distancexrunning days (1st path section of the PaP request) | If PaP request is FROM NetPaP dossierTHENDistance x running days | n.a. |