Table of contents

1. Introduction
2. IDs
3. System-Generated ID Structure
4. Add IDs manually
5. Manual IDs input
6. IDs validation

1. Introduction

This document describes the identifiers used in PCS-CB that are necessary for the communication and message exchange related to the path request or offers. Users can read about what IDs are available on the Graphical User Interface (GUI), how they can be generated, and what their structure is.

2. IDs

The IDs on the GUI are visible at 2 levels.

1. Reference train IDs
   • Route ID
   • Reference train ID
2. Territory level IDs:
   • Path request IDs

Each user can manually add or automatically generate IDs for the objects that they are the owner of.
Whether it’s generated, manually created or set up via TSI message, the identifier must be unique. When it’s not unique, the user can’t leave the screen.
Generate all will generate the IDs for the objects that belong to the agency in Draft and in Open.

• The generate button next to the ID will generate it for that field
• Manually, the leading applicant (LA) can add IDs to any object in Draft and Open. Later, only the responsible agency can define the ID for the object.
  Please note that if an object does not get a core element, we consider that as a “ghost” object, and those won’t be part of the outbound messages, but they are still displayed on the U

3. System-Generated ID Structure

The user can get the following automatically generated IDs from the system consisting of.

• A 4-character alphanumeric Company ID that is prefilled with the user agency ID, but is editable
• A 12-character alphanumeric digit core element (pattern: [-*0-9A-Z]{12})
• A 2-character alphanumeric variant ID
• The timetable year that is prefilled and not editable
• Reference Train ID
• Route ID
• Path Request ID
• Generating IDs fills the core element. If it is already filled, it is overwritten. Company ID, Variant and TTP are prefilled.

4. Add IDs manually

There is one level for the Reference train ID and Route ID.
For Reference Train, only variant 00 can be applied.
For Route ID, variant 00 cannot be applied. The default value is 01.
The Path Request IDs are grouped by territory.

5. Manual IDs input

If the user chooses to add the IDs manually, then they have the option to enter each ID manually or generate the IDs one by one for the reference train, route or path where they are the owner.

If the user chooses to generate IDs after the IDs have been added manually or automatically, they are warned that there are already existing IDs that will be overwritten.

6. IDs validation

According to the validation details, all IDs are considered as blocker if they are missing or wrongly defined. If an object is created, it’s not possible to continue the work without adding/generating ID.