Kordeus.PAX: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) No edit summary |
Stefanseiler (talk | contribs) |
||
| (46 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Kordeus PAX is | [[File:Interacting parties of Kordeus.PAX.png|thumb|644x644px|The digital Travel Assistance Service Requests (TASR) ecosystem]]'''Kordeus.PAX''' is an platform designed to streamline the end-to-end management of [[Travel assistance service request|travel assistance service requests]] through a secure, peer-to-peer ecosystem. | ||
Why SARA stands out from traditional centralized or generic task platforms: | |||
* '''Purpose-built for travel assistance''' – Tailored specifically to meet the complex needs of the travel assistance industry. | |||
* '''Data ownership, redefined''' – Ensures that individuals maintain full control over their personal data at all times. | |||
* '''Secure by design''' – Enables trusted, encrypted communication between all involved parties. | |||
* '''Scalable and open architecture''' – Ready to grow and adapt with your business needs. | |||
* '''Compliance without compromise''' – Supports data residency in required legal jurisdictions while operating as a unified system. | |||
== | == Interacting parties & Business processes == | ||
The travel assistance service delivery ecosystem hosts 5 different roles, which are represented by [[:Category:Digital Types|types of digitals]], where each have their | |||
* | *individual [[SARA business process domains|business process domains]] | ||
* see | * specific interactions with each other. You may see [[SARA digital interaction flows|digital interaction flows]] or [[Dev:Partner creation processes|digital creation processes]] for further information | ||
<u>Interacting digitals</u> - digital twins to natural or legal persons | |||
* | * [[Carrier digital|Carrier digitals]] - delivering core information on available services and access to reservation systems | ||
* | * [[Passenger digitals|Passenger digital]] - storing health information and status of special assistance requests from the patients perspective. | ||
* | * [[Travel partner digitals|Travel partner digital]] - supporting passengers on creation and management of their travel service requests (optional) | ||
* [[Travel assistance service operation center digitals|Travel assistance service operation center digital]] - the operation central, which processes requests and governs the service delivery process. (e.g. LH Medical Operation Center) | |||
* [[Delivery partner digitals]] - the partners, which ultimately performing tasks as instructed by the operation centers (e.g. Airports, Technics, Intermodal operation centers, ... ) | |||
<u>Human interface service digitals</u> - delivering multi digital platforms to allow parties, which do not have their own applications to interact with their digitals | |||
* [[PAX Portal digitals|PAX Portal digital]] - hosting the LH Group PAX.Portals, allowing [[passenger digitals]] and [[travel partner digitals]] to create, file and manage their special assistance requests | |||
* [[Delivery partner digitals|Delivery partner digital]] - hosting the LH Group Deliery Portals, allowing the [[delivery partner digitals]], to manage the services ordered by the operation center | |||
== Data domains & data ownership == | |||
A [[Travel assistance service request|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. See this article on [[SARA data domains]] for further details. | |||
== Service bundles == | |||
Kordeus.PAX consists of two major building blocks: | |||
* [[PAX.Portal]] - This application is for passengers and their agents | |||
** enabling patients to request services and communicate with the operations centers responsible at the travel carrier | |||
** enabling patient proxies (e.g. travel agents) to file requests on behalf of the patients | |||
* Tools for managing [[Travel assistance service request|travel assistance service requests]] | |||
** Portal Backend (v1) - An application, which covers fully manual backend processes without automation. (EOL Mid 2026) | |||
** SARA Backend Tools (v2) - A bundle of applications, which enable the core structured and rule based processing on the backend side. It contains these subservices | |||
** | *** [[SARA.Core (Special Assistance Request Management Suite)|SARA.Core]] - the main tool for management of travel service requests and travel service delivery governance | ||
** | *** [[SARA.DeliveryPartnerPortal]] - for service delivery partner digitals | ||
* [[Special Assistance Request Management Suite | **** interact with operation ce<nowiki/>nters of the carriers | ||
**** allowing to see and confir<nowiki/>m pending tasks | |||
* | *** [[Carrier Admininistration Tools|Carrier Admininistration T]]<nowiki/>[[Carrier Admininistration Tools|ools]] - for carrier's core digital to define service and service delivery processes | ||
* | *** [[Travel Service Operation Center Administration Tools|Travel Service Operation C]]<nowiki/>[[Travel Service Operation Center Administration Tools|enter Administration Tools]] - the tools for defining: | ||
* [[ | **** service delivery options and constraints | ||
** interact with operation ce<nowiki/>nters of the carriers | **** process automation rules within SARA.Core | ||
** allowing to see and confir<nowiki/>m pending tasks | *** [[SARA.ProcessAutomationEngine|SARA.ProcessAutomationEngi]][[SARA.ProcessAutomationEngine|ne]] - the main tool for automation of work in SARA.Core | ||
* [[ | |||
== See also == | == See also == | ||
* [[Dev: | * [[Travel assistance service request]]__NOTOC__ | ||
* [[SARA data domains]] | |||
* [[Dev:Partner creation processes]] | |||
Latest revision as of 14:38, 10 December 2025
Kordeus.PAX is an platform designed to streamline the end-to-end management of travel assistance service requests through a secure, peer-to-peer ecosystem.
Why SARA stands out from traditional centralized or generic task platforms:
- Purpose-built for travel assistance – Tailored specifically to meet the complex needs of the travel assistance industry.
- Data ownership, redefined – Ensures that individuals maintain full control over their personal data at all times.
- Secure by design – Enables trusted, encrypted communication between all involved parties.
- Scalable and open architecture – Ready to grow and adapt with your business needs.
- Compliance without compromise – Supports data residency in required legal jurisdictions while operating as a unified system.
Interacting parties & Business processes
The travel assistance service delivery ecosystem hosts 5 different roles, which are represented by types of digitals, where each have their
- individual business process domains
- specific interactions with each other. You may see digital interaction flows or digital creation processes for further information
Interacting digitals - digital twins to natural or legal persons
- Carrier digitals - delivering core information on available services and access to reservation systems
- Passenger digital - storing health information and status of special assistance requests from the patients perspective.
- Travel partner digital - supporting passengers on creation and management of their travel service requests (optional)
- Travel assistance service operation center digital - the operation central, which processes requests and governs the service delivery process. (e.g. LH Medical Operation Center)
- Delivery partner digitals - the partners, which ultimately performing tasks as instructed by the operation centers (e.g. Airports, Technics, Intermodal operation centers, ... )
Human interface service digitals - delivering multi digital platforms to allow parties, which do not have their own applications to interact with their digitals
- PAX Portal digital - hosting the LH Group PAX.Portals, allowing passenger digitals and travel partner digitals to create, file and manage their special assistance requests
- Delivery partner digital - hosting the LH Group Deliery Portals, allowing the delivery partner digitals, to manage the services ordered by the operation center
Data domains & data ownership
A travel assistance service requests holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. See this article on SARA data domains for further details.
Service bundles
Kordeus.PAX consists of two major building blocks:
- PAX.Portal - This application is for passengers and their agents
- enabling patients to request services and communicate with the operations centers responsible at the travel carrier
- enabling patient proxies (e.g. travel agents) to file requests on behalf of the patients
- Tools for managing travel assistance service requests
- Portal Backend (v1) - An application, which covers fully manual backend processes without automation. (EOL Mid 2026)
- SARA Backend Tools (v2) - A bundle of applications, which enable the core structured and rule based processing on the backend side. It contains these subservices
- SARA.Core - the main tool for management of travel service requests and travel service delivery governance
- SARA.DeliveryPartnerPortal - for service delivery partner digitals
- interact with operation centers of the carriers
- allowing to see and confirm pending tasks
- Carrier Admininistration Tools - for carrier's core digital to define service and service delivery processes
- Travel Service Operation Center Administration Tools - the tools for defining:
- service delivery options and constraints
- process automation rules within SARA.Core
- SARA.ProcessAutomationEngine - the main tool for automation of work in SARA.Core