PCS IT Day 23 November 2017, Vienna.

Slides:



Advertisements
Similar presentations
MyFloridaMarketPlace MyFloridaMarketPlace User Meeting June 22, 2004.
Advertisements

May 3, BE 9.3 Eurocab Case Study EPFL - Industrial Automation Case Study: the Eurocab railways signaling Studienfall: die Eurocab-Signalisierung.
Oracle General Ledger, Financial Reporting and Data Warehouse 6/22/2015 RIAS PHASE II Overview.
Creating Web Page Forms
OLDC Version 3.0 October 18, How to Connect (Telephone Conference) The Deployment Teleconference consists of a telephone conference and a Bridgit.
Chapter 5 Introduction To Form Builder. Lesson A Objectives  Display Forms Builder forms in a Web browser  Use a data block form to view, insert, update,
Participant Portal APIs - Pilot Tomasz KAMINSKI, DIGIT B.5.
1 Record Modifications Chapter 13 Section 13.8 Neha Samant CS 257 (Section II) Id 222.
 BUT …. Terminal pilot REQUEST TO THE CCB
Network Services Interface
For Using of TAF Test Manager (TTM)
PCS Statistics and main development’s history 2017
PCS Technical Board Vienna, 28th February 2017.
12 Product Configurator
TTR IT Implementation Capacity Offer/Request/Allocation
Network Services Interface
Non-RU Applicant (NRA), PCS UG
Enhancement Notification Release 5.4
RFC Short Term Path Request Pilots
Current activities Vienna, 10th May 2017.
PCS Day 2016 CMS Vienna, 23rd November 2016.
Removal of national particularities, PCS UG
PCS Technical Board 17th October 2017, Vienna.
Envelope Concept report, PCS UG
PCS Outlook PCS User Group 12th September 2018, Vienna.
Team Up Calendar An open source calendar for keeping track of collaborative events across the county Anyone can add an event When you sign up, you can.
PCS Minor Release th February 2018, PCS UG.
PCS CCB Group 22nd February, 2017.
TAF-TSI Train Object 25th June 2018, Prague.
PaP Publication strategy TT2019 – Combined PaP
PCS Technical Board 1st June 2017, Vienna.
EEC Core Team 6th February 2018, Vienna.
PCS Day - Feedback 23th November 2016, Vienna.
Development roadmap PCS Day 2017.
PCS IT Day Operation Points updates from SNCF-Réseau’s interface.
IT Support for TTR Pilots
Removal of national particularities
PCS User Group 15th February, 2017.
PCS User Group Vienna, 13th September 2017.
PCS Developments – PCS CCB
Retrospective report of the past year
Update timetable in PCS dossier from national system
PCS Groups and Boards PCS Day 2016
TTR IT Landscape PCS-TTR Day Vienna, 21 November 2018.
TAF-TSI Pilot PCS Day 2017.
JS Pilot and TEG Meeting, Vienna, 12/02/2019
PCS CONTENT ON CMS.
Taskforce „TT Quality“: Report from First Workshop (short)
Handling of PaP identifiers
TSI Compliant PCS Mandatory Interface
JS Handbook overview of changes
ÖBB-Infrastruktur AG Network Access – Customer Care Patrick Wögenstein
Definition and modelling of Train and Path in TAF/TAP TSIs
PCS Link I-TMS 3 PCS IT Day
PR deadline experiences, PCS UG
PCS Envelope Concept Status of the project
Trainings before Problems: New user
Let’s go through Path Modification/Path Alteration process
RFC Short Term Path Request developments
Envelope concept changes
PCS Technical Board 27th February 2018, Vienna.
Connecting Europe, Railway Undertakings and ProRail
Envelope Concept report, PCS TB
Quick Border Information
Training timeline Train the trainer RFC 1st round RFC 3rd round
Modelling of Train and Path in TAF/TAP TSIs
PCS Test Group 9 July 2019, Vienna.
Status of Train and Path Cardinality Train-Path
TT Quality monitoring on borders
Railway timetabling tools with automatic solutions
Presentation transcript:

PCS IT Day 23 November 2017, Vienna

Agenda

Agenda Welcome & Introduction PCS Team presentations Path Alteration/Patm Modification How to go through the process? How to use the operations? IP Consolidation & automated tests Handling of PaP identifiers Developments in PCS to fulfill the TAF-TSI pilot PCS TB members’ presentations SNCF Réseau: Operation point maintenance, update dossier procedure SZDC: Update timetable in PCS from national system ÖBB: Handling of agency notifications Infrabel: Storing of PCS Ids for dossier updates Q & A (loco types, complementary calendar, etc.)

TAF-TSI Release in PCS

Dimensions of changes Database Process GUI Interface Changes New process steps New fields New codes Operation points New process

Core Endpoint Operation points IM Parameters New Core application https://pcs-taftsitest1.rne.eu/pcs/services/IProxyIntegrationService_v5_1?wsdl https://pcs-taftsitest1.rne.eu/pcs/login Operation points from CRD - No permanent connection - IM Parameters from PCS Production TT2018

Process step changes Ad-Hoc Request Offer Harmonization Path Request Path El. Acceptance Post-Pr. Final Offer Active Timetable Release Active Timetable Back to Harmonization Back to Path Elaboration

New process type TypeOfInformation: 19 pre-accepted offer Name: Ad-Hoc Pre Accepted Decision: dossier creation Constraint: no partial harmonization is supported Ad-Hoc Request Offer Harmonization Path Request Path El. Acceptance Post-Pr. Final Offer Active Timetable Release Active Timetable

Identification 23 February 2019 Object type: A two character element indicating the type of object this ID is for. TR for Train PA for Path PR for Path Request CR for Case Reference Company: A four character element is indicating the company who created the object (RICS Code) Example: http://www.cit-rail.org/en/additionals/list-of-codes-for-undertakings/ Core element: the main part of the ID. It is free format and determined by the company that creates it. It can use any digit from 0 to 9 and any upper case character from A to Z. It is fixed width 12 characters. If it is less than 12 characters long it must be left justified by padding out the remaining space with a horizontal dash “-”. Variant: The variant field is a fixed length of 2 characters. Timetable period: In order to allow the core element to be reused for different timetable periods the year is included to indicate which year it applies to. Start-Date (used only in operation): The start-date is the day of planned departure from the origin station of the object. The field is only present in the daily object.

Train ID This identifier should be stored on the dossier level in the Basic Data (under the international train number field).  It should be possible to define it during the dossier creation wizard in the 1st step and later it should be visible in the Basic Data. As the modification of the Train ID is not supported in later phases, the Leading RU can modify it only in Open phase. After releasing the dossier to Harmonization the field should be blocked.

PCS request ID/Path ID Path request ID/Path ID: 23 February 2019 Path request ID/Path ID: TsiPathID element is added to PCS Available only in web-services and defined as optional element Path Request ID meaning RU timetable (modification until the end of Harmonization) Path ID meaning IM timetable (modification until the end of Ad-Hoc request Offer)

Other PCS related changes 23 February 2019 Traction mode new value: „No leading Engine” is added to the list TrainCC system code table update → Route Class code list: Free text field was replaced with the following list: A, B, C, D, E, F, G, C2, C4, CM2, CM3, CM4, CM, CE, D2, D4, A2, A4, B1, B2, C3, D3, E4, E5 Brake type: „X” was added to the list Spelling mistakes had been fixed for „Braking” (instead of „Breaking”) Dangerous goods indication - new fields Danger Label: It should be added to the dangerous goods area. Free text. Dangerous Goods Volume: It should be added to the dangerous goods area. Values are expected in cubic meters. Limited Quantiy Indicator: New check box in the dangerous goods area Release notes: http://cms.rne.eu/pcs/pcs-documentation/version-19x-changes-taf-tsi ETCS Level 0 EBICAB 700 NEXTEO ASFA ETCS Level NSC LS DAAT EBICAB 900 ETCS Level 1 ZUB 123 EVM SELCAB ETCS Level 2 ALSN CAWS SIGNUM ETCS Level 3 ATP-VR/RHK ATP ZUB PZB KVB BACC ATB 1st Gen LZB TVM 300 RSDD/SCMT ATB Next Gen Crocodile TVM 430 SSC GW ATP TBL 1 KVBP MEMOR II+ RETB TBL 2 KCVP SHP TPWS TVM 430TBL1+ KCVB PKP

Transition and Integration layer between PCS and CI 23 February 2019 Transition and Integration layer between PCS and CI