PAMT report

Content

Introduction

PaP Availability Management Tool (PAMT) allows C-OSS managers to get an overview of their PaP's current statuses and it shows which dossiers contain these PaPs as requests

It is possible to export the PAMT report in XLSX format, which can be used as a basis for calculating capacity KPIs. 

However, the search is available for Applicants and IMs too, where they can check the PaPs that are used by them or on their network

It is located under the Pre-constructed Products menu in the PAMT search submenu:

 

PAMT Search

It opens the search window where you can define the search criteria based on the followings:

  • Timetable period: timetable year, single selection drop-down list where the current year is set by default  
  • Train type: type of the train, single selection drop-down list where the default value is "Cargo"
  • Timetable: type of the timetable, single selection drop-down list, the default value is "C-OSS" 
  • PaP ID: optional text field, this ID is defined by the C-OSS manager to identify the PaP origin-destination pairs, it is max. 12 characters long. If you want to search according to the PaP ID number you must enter the exact PaP ID number otherwise the list will be empty!
  • Direction: optional text field, multi-selection drop-down list where define the origin-destination direction
  • RFC corridor: optional text field,  multi-selection drop-down list to select the Rail Freight Corridor who published the PaP origin-destination pair. This field is grayed out by default if the PAMT Search is accessed by the Corridor account otherwise it is enabled for the Applicant or IMs to narrow down the search criteria
  • RFC Dossier type: mandatory text field, multi-selection drop-down list where define the type of Fix or Flex
  • Allocation statuses: optional text field, multi-selection drop-down list, define the status of the PaP request and represents the result of the C-OSS manager's decision
    • The following statuses are available in the system:
      • Requested: requested by the Applicants,  when entering the first time the Pre-booking phase the PaP request is in requested status
      • Reserved: C-OSS manager agrees with the PaP request and reserves it for the Applicants request
      • Conflict: if the same PaP request is part of two or more dossiers, the system indicates that the PaP requests conflict. PCS has a built-in conflict solving tool to identify these situations
      • Tailor-made: if the C-OSS manager NOT agrees with the PaP request and the C-OSS manager changes it into a tailor-made request. It means that the dossier will NOT contain the PaP request anymore, it will look like normal locations
      • Waiting for alternative: when the same PaP is requested by more than one Applicant then the first PaP request is accepted by the C-OSS manager, changed to a reserved state, and the second request is still waiting for an alternative solution. E.g.: the 7PaP00Demo2 PaP ID is requested in two dossiers in DossierA and DossierB. The C-OSS manager accepted the PaP in the first dossier, in DossierA and changed the status to reserved. The PaP request in the other dossier, in DossierB, is now waiting for alternative status
      • Reserved alternative: when the dossier goes into the alternative offer branch phases and the C-OSS manager offers an alternative PaP to replace the existing PaP request in the dossier. The C-OSS manager reserves the new PaP request and the C-OSS timetable updates with the new alternative PaP
      • Alternative offered: the C-OSS manager submits the reserved PaP request as an alternative offer to inform the involved Applicants about changes.
      • Alternative rejected: if the Applicant rejects the Alternate Offer received from the C-OSS manager
      • Alternative accepted: if  Applicant accepts the Alternate Offer received from the C-OSS manager
      • Drafted: C-OSS sends submits draft timetable the PaP request will be in drafted status
      • Offered: In the Final Offer phase the PaP request will be in an Offered status
      • Allocated: In the Active Timetable phase the PaP request will be allocated

Search result & visibility

There are two main options to set the search result visibility:

  • With requests only: with this option list all PaP dossiers were  requested in a dossier according to the defined search criteria
  • All: every published PaP dossier will be listed there according to the defined search criteria

Click the arrow at the first column to expand for details of the PaP request. If the detailed window is empty it means that the particular PaP is not part of any dossier meaning has not been requested by any Applicant:

Now search for dossiers where the PaP requests are used. In this case, tick the check-box "With requests only". The result excludes all published PaPs that have NOT been requested by the Applicants.

In a particular PaP is requested the details window look like:

Generate PAMT Report

First, open the PAMT search to specify the filter criteria for searching for PaPs to get a detailed report on it.  By default, the "Generate PAMT report" button is disabled, you need to select one report and the button will appear.

There are two ways to select PaPs:

  • One by one
  • Select All: Select the check box in the header first column then two more buttons will be visible:
    • All Pages
    • On this page

After the filter criteria setup completed click the "Generate PAMT report" button to create the report. It opens the Generate PAMT report window where you name your report and/or set the report status.

The personal report means the report is visible only to the user who created it (in private mode), but  the default settings are to share it with your colleagues within your agency:

To generate the report takes a while, it runs in the background and the user gets a notification in e-mail when the report is ready.

Download report

When the report is ready it will be available to download in the "Reporting" submenu: 

To download the report click the report name link to browse for the place to save the file. It works the same way as in the Windows operating system when saving a file.

Report file description

The first three rows are the headers, each of the columns merging the cells vertically.

The  generated report contains the following columns:

  • Dossier Summary Line:  it works like a header and marked with the letter 'X', representing additional data and introducing sections. Each dossier number is a section, if the dossier contains several PaP requests it shows the PaP origin-destination pairs in subsections by request and allocation status.

  • Type: indicates the type of dossier. If it is a PaP dossier (Flex or FIX) then the report does not contain subsection information. The "Dossier ID" column equals the "PaP Dossier ID" column. 

  • 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
  • Dossier Id: system-generated number once the dossier created, identification of the dossier
  • Path Id:  system-generated number once the dossier created, each Patch has its own identification number     
  • 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        
  • Net PaP Id: identification number of the Network PaP defined by C-OSS managers       
  • Request Status: 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 noncorridor path enters the corridor
  • PaP Origin: the PaP request origin point        
  • PaP Origin Arrival:  the PaP request 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 noncorridor path exists the corridor
  • Distance: length between two location points in km
  • Running Days: PaP request published available days        
  • K-Value: described below the table      
  • Circulation Days:  weekly circulation days where weekdays presented in numbers       

If there are many requests for a PaP ID, PCS may not be able to display all the folders on one screen. In this case, the user can scroll right and check the other request.

Errors

Distance (KM) is not the same as it has been imported or distance shows null

Imagine that we have 3 operation points X, Y, and Z. The distance between X and Z is equal to the distance between X and Y plus the distance between Y and Z. The distances that are entered are between origin and destination. The way how calculation of the distances works is that PCS calculates distances between neighbor stations.

Let's see an example.: Rostock Seehafen -> Dresden-Friedrichstadt -> Bad Schandau Grenze. If the distances between Rostock Seahafen and NBad Schandau Grenze is defined as 455,51 km.

In PCS has the distance between Rostock Seehafen and Dresden-Friedrichstadt is 402,5 previously stored.

The distance between Dresden-Friedrichstadt and Bad Schandau Grenze does not exist because the user didn't enter that pair in the distances sheet.

So the distance between these two operation points will be 0.

That means that the final distance between Rostock Seehafen and Bad Schandau Grenze will be 402,5.

Resolution: define the missing distance pairs and reimport the file. If your PaPs are in the published state it will not update your already published PaPs, the system will skip these PaPs. But if you have dossiers with lights blue and orange it will generate a new version number by updating them.

 

Distance calculation

 K-ValueNetPaP K-ValueK-Value Total Dossier
Summary

Sum (distance of PaP request)

x

running day (reference point of the Applicant main timetable)

Sum (distance of NetPaP request)

x

running day (reference point of the Applicant main timetable)

Sum (K-Value of PaP request)
PaP Requests

Distance

x

running days (1st path section of the PaP request)

If PaP request is FROM NetPaP dossier

THEN

Distance x running days

n.a.