SARA.Core (Special Assistance Request Management Suite): Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
Stefanseiler (talk | contribs)
Stefanseiler (talk | contribs)
Line 20: Line 20:
*[[Dev:Travel Assistance Service Request Operation Automation Engine (TASR-OAE)|Travel Assistance Service Request Operation Automation Engine (TASR-OAE)]] - the background service, which automates and processes background tasks within the operation centers
*[[Dev:Travel Assistance Service Request Operation Automation Engine (TASR-OAE)|Travel Assistance Service Request Operation Automation Engine (TASR-OAE)]] - the background service, which automates and processes background tasks within the operation centers
*[[App:Travel assistance service administration|Travel Assistance Service Administration]] - allows the definition of supported services by a carrier and tasks/actions associated with the services
*[[App:Travel assistance service administration|Travel Assistance Service Administration]] - allows the definition of supported services by a carrier and tasks/actions associated with the services
*[[App:Delivery partner administration app|Delivery partner administration app]] - allows the administration of service providers, which deliver services at the ports
* [[Service operations flow designer]] - allows the definition of operation events for each supported service/service-flavour and tasks/actions associated with these events.
* [[Service operations flow designer]] - allows the definition of operation events for each supported service/service-flavour and tasks/actions associated with these events.



Revision as of 06:46, 26 November 2024

PAX Operations Portal main process

This service bundle for carriers contains services, which

  • allow them to define their services availability and dependencies and
  • allows their staff members to perform all necessary tasks to analyse and fulfill requests of their passengers.

Core process within the OC

Once the request has been created by passengers (PAX) through an instance of a PAX Portal instance, the passenger digital contacts the operaton center (OC) digitals with its request. Once a OC digital has claimed a service-segment of the itinerary with the travel assistance service request, the work for the OC starts:

  1. Processing phase - From now on, the travel assistance operation centers (OC) are processing the request 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
  2. 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.
  3. Service delivery phase - During this phase the OC monitors the service delivery and performs actions to make sure that everything works out.

Contained services

The service bundle contains these services:

Related articles