LHG:DAS Interface
DAS is a Lufthansa tool which holds flight information. It is required for these interface dependent use cases in SARA and Portals,
Usecase
Lufthansa MOC team needs to be notified by our SARA system as fast as possible on certain changes relevant to PAX. Currently the team is checking on a regular (daily) basis if any relevant flights have changed which transport passengers. Relevant changes are:
- changes on aircraft
- changes on aircraft type
- delays
- status change (on plan / delayed / cancelled )
So we would like to listen to DAS over Kafka to receive all changes and select from the stream messages, which affect passengers with special assistance requests being filed.
Implementation
This is a two components concept
Bridge server digital (residing inside LH intranet)
On the Bridge Server Digital:
- We implement an indexed local data cache (LDC controller) which consists of a set of files. For each day, we have one file. The DAS-Files adhere to this structure.
- We implement a proprietary service which constantly receives update messages from the KAFKA Topic and stores it in local files.
- We implement a Shared Data Cache controller (indexed: per day), which shares the DAS-Files to any digital (e.g. LH MOC Digital) where an adequate trust relation exists
- Required trust on sending side has TCI Share-DAS-information.
LH Operation Center (MOC) digital
On the MOC side the
- DAS-Files containing the LH rotation planning are received through the SDC controller, if the trust relation on receiving side has Accept-DAS-information
- MOC digital builds a local data cache (LDC) with list of relevant flights (departure date, flight number, planned departure data) which bear future flights with passengers with SAR-Requests on it
- A background service detects relevant changes to the flight planning, whenever the shared cache (rotation planning) or the local cache (with flights with SAR on them) is updated and triggers:
- an update of the service delivery tree
- (optionally) a task creation for MOC team
- Relevant changes are:
- Plane change (Tailcode change) of an earlier assigned flight (chage from unplanned to planned is no change)
- Departure information change
- Passenger journey change