Dev:Travel Segment Service Item Claiming: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) No edit summary |
Stefanseiler (talk | contribs) No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=== Prerequisites === | === Prerequisites === | ||
Once a ''PAX personal digital'' starts connects or is created at a [[PAX Portal|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]]. | Once a ''PAX personal digital'' starts connects or is created at a [[PAX.Portal|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 === | === Process === | ||
# Once the ''personal digital'' decides to submit the request, it sends out the [[travel assistance service request]] to all known operation centers through the {{Blue-Tag|BlueText=MT-Message}} <code>TAC.TravelAssistanceRequest.Info</code>'''.''' It holds a [[Travel word definitions|travel itinerary]] consisting of multiple [[Travel word definitions|travel segments]] and a list of requested [[App:Travel assistance service administration|travel assistance services]]. | # Once the ''personal digital'' decides to submit the request, it sends out the [[travel assistance service request]] to all known operation centers through the {{Blue-Tag|BlueText=MT-Message}} <code>TAC.TravelAssistanceRequest.Info</code>'''.''' It holds a [[Travel word definitions|travel itinerary]] consisting of multiple [[Travel word definitions|travel segments]] and a list of requested [[App:Travel assistance service administration|travel assistance services]]. | ||
# Upon arrival of this message, the [[Dev: | # Upon arrival of this message, the [[Dev:SARA.ProcessAutomationEngine|SARA.ProcessAutomationEngine]] analyses the request in these steps: | ||
#* '''Compute embarcation and disembarcation points''' of this itinerary, as this is sometimes required for service devliery. Criteria: disembarkation port == last port of journey || disembarkation port != next segment boarding port || layover between disembarkation port and next embarkation time > 24h | #* '''Compute embarcation and disembarcation points''' of this itinerary, as this is sometimes required for service devliery. Criteria: disembarkation port == last port of journey || disembarkation port != next segment boarding port || layover between disembarkation port and next embarkation time > 24h | ||
#* '''Compute relevant segments''', which this OC can claim. This is done, if it is authorative for the [[Travel word definitions|operator]] of this travel segment. | #* '''Compute relevant segments''', which this OC can claim. This is done, if it is authorative for the [[Travel word definitions|operator]] of this travel segment. | ||
Latest revision as of 05:39, 26 June 2025
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 through the MT-Message
TAC.TravelAssistanceRequest.Info. It holds a travel itinerary consisting of multiple travel segments and a list of requested travel assistance services. - Upon arrival of this message, the SARA.ProcessAutomationEngine analyses the request in these steps:
- Compute embarcation and disembarcation points of this itinerary, as this is sometimes required for service devliery. Criteria: disembarkation port == last port of journey || disembarkation port != next segment boarding port || layover between disembarkation port and next embarkation time > 24h
- Compute relevant segments, which this OC can claim. This is done, if it is authorative for the operator of this travel segment.
- For each relevant segment
- create travel segment service items for each travel service to deliver.
- by default set the status to created
- check if the service is available on this segment. If the service is not available set the travel segment service item status to undeliverable.
- Notify the PAX personal digital on the claimed services through sending an MT-Message
TAC.TravelAssistanceRequest.SegmentServiceItemUpdate. It holds all segments, this OC is authorative for and the new status information on them.
Claim process status (on passenger side)
| Status | Process status description |
|---|---|
| Open for claim | This SAR has been created, but has not been transmitted to the carriers |
| Claimed | This SAR has been created and has been submitted by the passenger. The request has been sent to the operation centers of the carriers. The request is waiting until all segments have been claimed by authorative operation centers (OCs) |
| No OC Exists | If all OCs answer "not responsible", then the status "No OC exists" will be set. This will trigger an email to PAX that this segment cannot be covered. |