Dev:Travel assistance service requests - Process flow

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”

à TAC.SegmentServiceRequest.Info

From here the service processing engine takes over on OC Digital side. It uses the

TAC.SegmentServiceRequest.Info to notify the patient on updates of the service segment requests. The patient digital then checks if the full TravelAssistanceRequest status has changed and propagates it to all participating MOCs.  

Related articles

• Kordeus.PAX