Dev:Travel assistance service requests - Process flow: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
# '''Request definition phase''' - Passengers (PAX) or their travel agents creates and edits the [[Travel assistance service request|travel assistance service requests]] through an instance of a [[PAX Portal]] instance. Once the request is completed, the passenger digital contacts the OC digitals with its request. | # '''Request definition phase''' - Passengers (PAX) or their travel agents creates and edits the [[Travel assistance service request|travel assistance service requests]] through an instance of a [[PAX Portal]] instance. Once the request is completed, the passenger digital contacts the OC digitals with its request. | ||
# [[Dev:Service | # [[Dev:Travel Segment Service Item Claiming|Claim phase]] - This phase is happening entirely in the backgound without human interaction. It is implemented as part of the [[Dev:Travel Assistance Service Request Operation Automation Engine (TASR-OAE)|Travel Assistance Service Request Operation Automation Engine (TASR-OAE)]] . It claims responsibility for one or mulitple travel segment services of the [[Travel word definitions|itinerary]]. | ||
# '''Processing phase''' - From now on, the ''travel assistance operation centers (OC)'' are processing the request within their [[Travel Assistance Service Management Suite]] and | # '''Processing phase''' - From now on, the ''travel assistance operation centers (OC)'' are processing the request within their [[Travel Assistance Service Management Suite]] and | ||
#* may request further information from the PAX regarding the segments and services they have claimed responsibility for | #* may request further information from the PAX regarding the segments and services they have claimed responsibility for | ||
Revision as of 11:01, 25 November 2024
Core process & phases
Each travel assistance service request always follows this process flow pattern:
- Request definition phase - Passengers (PAX) or their travel agents creates and edits the travel assistance service requests through an instance of a PAX Portal instance. Once the request is completed, the passenger digital contacts the OC digitals with its request.
- Claim phase - This phase is happening entirely in the backgound without human interaction. It is implemented as part of the Travel Assistance Service Request Operation Automation Engine (TASR-OAE) . It claims responsibility for one or mulitple travel segment services of the itinerary.
- Processing phase - From now on, the travel assistance operation centers (OC) are processing the request within their Travel Assistance Service Management Suite and
- may request further information from the PAX regarding the segments and services they have claimed responsibility for
- fetch information from internal systems to see if services can be delivered at all
- may decide on if the service for one or all segments can be performed or is rejected
- may request a decision by special staff (e.g. doctors) , if the service can be performed or is rejected
- Collection phase - Once all information was collected and the service was considered performable, it may require money collection. In this phase the OC facilitates the money collection process. After this is performed the service is granted and the OC is monitoring and perfoming tasks to implement the service.
- Service delivery phase - During this phase the OC monitors the service delivery and performs actions to make sure that everything works out. The service delivery partner digitals use the PAX service delivery partner portal.
Communication patterns
à 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.