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,

Contained data

We interested from DAS system with this information stream

Dispatch data

This holds for each planned flight

• status (on plan / delayed / cancelled )
• delay time
• Operating craft
  • type (e.g. Boing 747-8)
  • tail code

Planned interface approach

KORDEUS is building a KAFKAA interface, which subscribes to a "MOC/SARA" KAFKA Topic. Through this it which recieves messages of this type:

Operations updates

This information containing all operations planning items (typically 1-2 weeks ahead of the flight), but also for adhoc travel informaiton

• Departure date
• Flight number
• Planned craft type
• Tailcode
• status (on plan / delayed / cancelled )
• delay time

Solution

On the bridge server, the interface :

• recieves from SARA a shared cache with list of relevant flights (departure date, flight number, planned departure data) which bear future flights with passengers with SAR-Requests on it
• reads all the operations messages and builds a local cache with all future flights on it. Information older than one day will be deleted. This local cache can be queries by SARA at any time through an LAN-api.
• detects, if any of the operational data of the relevant flights receive operations updates, which do not match the planned information.
  • Relevant changes:
    • Plane change (Tailcode change) of an earlier assigned flight (chage from unplanned to planned is no change)
    • Departure information change
  • If this happens sends an MT-message to LH MOC digital that an operational flight change has occured providing the new operational information.

See also

• LHG:SARA Project
• LHG:Interface dependent use cases