Dev:Travel Segment Service Item Claiming
Prerequisites
Once a PAX personal digital starts connects or is created at a PAX portal, it receives a list of all operation centers from the PAX portal. The personal digital uses the PAX portal to create and complete a travel assistance service request.
Process
Once the personal digital decides to submit the request, it sends out the travel assistance service request to all known operation centers.
Once the request has arrived with the OC
they need to claim the service segment items which they
requests is received by one or multiple travel assistance operation centers (OC). It holds a travel itinerary consisting of multiple travel segments and a list of requested travel assistance services.
MT-Message “TAC.TravelAssistanceRequest.Info”
(From Passenger Digital to LH MOC FRA and other MOCs)
TravelAssistanceRequest is created or updated in MOC Digital!
à Analysing itinerary
· Number of relevant segments to which this OC is responsible 1
FRA-BEG (LH)
à TAC.TravelAssistanceRequest.ClaimSegmentResponsibility
· Number of irrelevant segments to which this OC is not responsible 2
BEG-ZRH (LX), ZRH-FRA (LX) à TAC.TravelAssistanceRequest.NameSegmentResponsibleOCDigitals
· Subjourney detection
1. FRA-BEG
2. BEG-ZRH (LX), ZRH-FRA (LX)
Criterion: disembarkation port == last port of journey || disembarkation port != next segment boarding port || layover between disembarkation port and next embarkation time > 24h
· Embarcation relevant ports à FRA (relevant), BEG (not relevant)
· Disembarcation relevant ports à BEG (relevant), FRA (not relevant)
à Create Travel Service Request in LH MOC FRA
à Create local segment based service product entries
· segment x requested services
· ditch segments, which do not support this service
à send to PAX Portal message, that service is not supported for this segment
· For all other create segment-service-requests and associate them with the
Travel Service Request. Set status of segment-service-request to ”created”