Dev:Travel Segment Service Item Claiming: Difference between revisions
Stefanseiler (talk | contribs) No edit summary |
Stefanseiler (talk | contribs) No edit summary |
||
| Line 9: | Line 9: | ||
#* '''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. | ||
#* For each relevant segment | #* For each relevant segment | ||
#** create | #** create travel segment service items for each travel service to deliver. | ||
#** by default set the status to created | #** 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. | #** check if the service is available on this segment. If the service is not available set the travel segment service item status to undeliverable. | ||
Revision as of 11:00, 25 November 2024
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 Travel Assistance Service Request Operation Automation Engine 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.ServiceSegmentItemUpdate. It holds all segments, this OC is authorative for.
TravelAssistanceRequest is created or updated in MOC Digital!
à Analysing itinerary
·
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:
· 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”