SARA data domains: Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
Stefanseiler (talk | contribs)
No edit summary
Stefanseiler (talk | contribs)
No edit summary
Line 11: Line 11:
!OC
!OC
!Del.P.
!Del.P.
|-
| colspan="6" |Communication
|-
|PAX with OC
|
|O
|P
|
|'''Agent''' is acting on behalf of the PAX!
|-
|Agent with OC
|
|O
|P
|
|
|-
| colspan="6" |Core
|-
|-
|Travel Group information
|Travel Group information
Line 45: Line 63:
| style="text-align:center; background-color:#FFCCCB" |O
| style="text-align:center; background-color:#FFCCCB" |O
| style="text-align:center; background-color:#ADD8E6" |P
| style="text-align:center; background-color:#ADD8E6" |P
|This holds the case and its meta-information and communication data
|This holds the case and its meta-information
|-
| colspan="6" |Delivery information
|-
|-
|Delivery requests & instructions
|Delivery requests & instructions

Revision as of 06:09, 26 June 2025

A travel assistance service requests holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information:

O=Owner, S=Shared, P=Processor Ownership & Storage Details
Agent PAX OC Del.P.
Communication
PAX with OC O P Agent is acting on behalf of the PAX!
Agent with OC O P
Core
Travel Group information O S S S
Personal information P O P S
Medical information P O P S
Journey Information P P O S Shared ownership, based on transport contract
Travel Assistance Service Case P P O P This holds the case and its meta-information
Delivery information
Delivery requests & instructions O P
Delivery status information O P LH ownership, due to service contract

Each travel assistance service request has data domains, which are owned, shared or processed by 4 b-op digital types:

  • Personal information
  • Personal Documents required for service delivery
  • The planned itinerary
  • Travel assistance services, which are requested for this itinerary
  • Travel Segment Service Items - holding the detail information on the services to be delivered and are used to communicate with the operation centers (oc)
  • General status on travel assistance request
  • Operation specific information
    • discussions
    • tasks

Available Status on passenger side

This status is stored at the travel assistance service request (db) and is only edited by the personal digital, which is the single point of truth where all information come together.

Status MOC status Process status description
In Preparation not visible This SAR has been created, but has not been submitted to the carriers
Submitted not visible This SAR has been created and has been submitted by the passenger. The request has been sent to the operation centers of the carriers. The request is waiting until all segments have been claimed by authorative operation centers (OCs)
Pending OC has opened a case on their side.

visible, but on segment level.

All segments of the SAR itinerary have been claimed by responsible OCs.
Waiting for Info At least one segment-service requires further action from the passenger. (for details see the status of travel segment service items status)
Finalized All requests are processed, ready to go (at least partially)
Closed All information exchanged, no more action required
Archived This request is no longer required. The data will be anonymized (DS-GVO) on the OC side after some time.

See also