1. Envelope concept changes
PCS Web Services v.6
Envelope concept changes
Jana Karcheska, Valerija Velinovska
, Vienna

2. PCS Team (1) Valerija Velinovska Technical Coordinator Jana Karcheska
Architect, Product Owner Proxy
Gorazd Titizov
Project Manager, Scrum Master
Mate Back
Product Owner

3. PCS Team (2) Ignatij Gichevski Software Engineer Trajche Naumoski
Senior Software Engineer
Aleksandar Cindrikj
Senior UX Engineer
Hristijan Dimitrieski
Technical Coordinator
Aleksandra Hristov
UX Architect

4. PCS Team support Aleksandar Petreski Senior System Engineer
App Support Team (24/7)
Slavcho Trnkovski
Senior Database Administrator

5. New URL(s) Test system Production system (not yet available)
Production system (not yet available)

6. Authentication Request
AuthenticateData is removed
HTTP “X-Authorization” header should be sent
with each request instead
JSON Web token expires at 3AM every day

7. Web Service spring cleaning
Upgrade to latest libraries versions
Architectural improvements
Better test coverage
Unified model mapping configuration between web service model and domain
Unified authorization between web service layer and domain

8. Trivial changes (1) Complex types in CamelCase elements_underscored
Why is this important: remove complex mappings to our Java domain code and consistency
Request/Response elements are not changed to underscore notation from pragmatic reasons as they are too many and are not mapped to domain objects

9. Trivial changes (2) Removed previous versions target namespaces
Everything is now under
Remove obsolete operation that were not implemented or used
createDossier
getRegBodiesForIMAgency
getProdAgencyUserDataForDossier
getIMUserDataForDossier etc.

10. Changes in Trasse schema type
processingStatus
managedByPcs

11. Changes in TrasseElement schema type
Alternative
Origin
Departure time zone offset
Arrival manual offset
Alternative
Destination
Departure manual offset
Arrival time zone offset
Construction
Starting
Point

12. Changes in TrasseElement schema type
Earliest/Latest
Arrival Offset
Reference point
Earliest/Latest
Departure Offset
Traffic period Id
isHarmonized
midnights_arrival
midnights_departure
associated_trains

13. Changes in TrasseElement schema type
Use separate Agency Id fields for responsible RU and IM
Minimum Dwell period time is defined in minutes
Agency Id
Responsible IM Id
Agency
Responsible RU Agency Id
Min Dwell Period Time
Responsible agency fields are on path section level though according to EC rules all path section in one sub-path must have the same responsible pair. In PCS domain model Trasse is linked to a pair id. If the community agrees we can elevate the pair of id’s to Trasse in the web services schema as well. We decided to keep them initially on the path section level for flexibility to more easily accommodate different variants (path, user, tsi) and any changes in that area.

14. Changes in TrasseElement schema type
All catalogue fields in separate type UsedCatalogueData
All catalogue fields in catalogue dossiers in separate type CatalogueData
All train parameters are in a separate type TrainParameters
All times and offsets are in a separate type Times

15. Other important changes in types
Pathfinderintegration root element renamed to WsDossierContainer
Complex type defined to combine the choice between Agency PCS or Non PCS (UIC) ID

16. New Error codes
Calendar inconsistency error code for acceptance indicator update to green
Incorrect responsible RU/IM pair of id’s for path section
Several status codes regarding acceptance indicator, production and commercial progress status fields set inappropriately
Additional error codes could be expected
what is the desired behaviour, to raise an error on overlappings or to eliminate them by gradually switching them out?

17. New EC behavior – Switch calendar
Change to the running days in existing sub-path
New sub-paths with defined running days

18. New EC behavior – Acceptance Indicators downgrade
The system shall downgrade the acceptance indicator of the RU responsible in a neighbor territory when at least one of the following changes occur on the Border:
a) operation point
b) arrival or departure time
c) manual or time zone offset – in case it is done on the Border, otherwise an offset change in the middle of the Sub- path will trigger running days change
d) dwell time
e) running days
f) alternative origin or destination

19. TsiTrainId element will be moved from dossier to path element.
TSI Identifiers
TsiTrainId element will be moved from dossier to path element.
All paths that belong to one TSI Variant will have the same TsiTrainId but they will have different TsiPathId.
TsiPathId unique per dossier, can only be updated via web services – it represents path request in RU tt, path in IM tt id
- everything can be different
TsiTrainId unique per TSI variant, one variant is related to multiple sub path, there are constraints (same origin, borders, destinations, commercial stops)
- only variant id can be different
Agile approach if constraints are more strictly defined we might downgrade the TsiTrainId to path section level.

20. TSI Identifiers and new schema types

21. New Operations GetPathVariants CreateUserVariant UpdateUserVariant
To be used by RNE for warehouse
To be used by anyone who needs to get timetable combinations constructed by PCS
CreateUserVariant
Used by leading RU in Open phase
UpdateUserVariant
Used by leading RU in Open and Harmonization
GetTsiVariants
Used by TIL or RU’s integrated via PCS without CI/TIL
GetTsiVariant - everything that belongs to a train id
- list of sub-paths, but there could be multiple ones in the same territory
- should we construct combinations and have constructed paths
GetPathVariants - production train equals to
- decision: list of sub paths or one constructed path, list is equivalent to what we have in the domain as path variants

22. PCS Web service v.6 Timeline

23. Hands-on Demo
Questions & Answers