Kordeus.PAX: Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
Stefanseiler (talk | contribs)
Stefanseiler (talk | contribs)
No edit summary
Line 1: Line 1:
Kordeus PAX is a product, which allows end-to-end processing of a [[travel assistance service request]].
Kordeus PAX is a product, which allows end-to-end processing of a [[travel assistance service request]].


== Building blocks ==
== Interacting parties ==
Facilitating this process means constant interaction with parties involved. These are:
 
=== Passengers (PAX) ===
During the entire process, passengers can use the [[PAX Portal]] to:
 
* file the [[Travel assistance service request|travel assistance service requests]]
* see the combined status of the all the service requests, segment by segment
* provide missing information
 
=== Operation centers (OC / MOC) ===
Operation centers can use the [[PAX Operations Portal]] service bundle to:
 
* communicate with the PAX to retrieve further information for decisionmaking and notify them on decisions
* receive, process and decide, which services can and will be delivered.
* provide tasks to delivery partners in order to fulfill the desired [[Travel assistance service request|travel assistance services]].
 
=== Delivery partners (DLP) ===
Once services are granted/confirmed, they are typically not delivered by the operation center (OC) themselves, but by delivery partners. OCs push information and tasks to them within the core process. The delivery partners use a [[PAX Service Delivery Partner Portal]] to:
 
* receive and confirm tasks
* confirm service delivery
* communicate with operation centers
 
== Service bundles ==
Kordeus.PAX consists of three service bundles, each delivering the required tools for the interacting parties:
* [[PAX Portal]] - for passengers and their agents
* [[PAX Portal]] - for passengers and their agents
** allowing patients to request services and communicate with the operations centers responsible at the travel carrier
** allowing patients to request services and communicate with the operations centers responsible at the travel carrier

Revision as of 21:23, 24 November 2024

Kordeus PAX is a product, which allows end-to-end processing of a travel assistance service request.

Interacting parties

Facilitating this process means constant interaction with parties involved. These are:

Passengers (PAX)

During the entire process, passengers can use the PAX Portal to:

Operation centers (OC / MOC)

Operation centers can use the PAX Operations Portal service bundle to:

  • communicate with the PAX to retrieve further information for decisionmaking and notify them on decisions
  • receive, process and decide, which services can and will be delivered.
  • provide tasks to delivery partners in order to fulfill the desired travel assistance services.

Delivery partners (DLP)

Once services are granted/confirmed, they are typically not delivered by the operation center (OC) themselves, but by delivery partners. OCs push information and tasks to them within the core process. The delivery partners use a PAX Service Delivery Partner Portal to:

  • receive and confirm tasks
  • confirm service delivery
  • communicate with operation centers

Service bundles

Kordeus.PAX consists of three service bundles, each delivering the required tools for the interacting parties:

  • PAX Portal - for passengers and their agents
    • allowing patients to request services and communicate with the operations centers responsible at the travel carrier
    • allowing patient proxies (e.g. travel agencies) to file requests on behalf of the patients
  • PAX Operations Portal - for operation centers and their staff
    • allowing to digitally interact with the service requesting parties
    • high automation potential through operation center service decision workflow engine
    • allowing digital interaction with service partners
  • PAX Service Delivery Partner Portal - for service delivery partner digitals
    • interact with operation centers of the carriers
    • allowing to see and confirm pending tasks