LHG:SHED-Connect: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) No edit summary |
Stefanseiler (talk | contribs) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=== | This interface is planned to deliver regular flight schedule to its B-Op Consumers. | ||
====== Required data fields by Kordeus ====== | |||
This delivers the planned flights: | |||
* FLIGHT NUMBER | * FLIGHT NUMBER | ||
* FROM | * Period of operation (Period start, Period end, weekdays, monthly, exact dates) | ||
* TO | * FROM (Departure Airport) | ||
* TO (Arrival Airport) | |||
* LOCAL DEPARTURE TIME | * LOCAL DEPARTURE TIME | ||
* DEPARTURE TIME UTC | |||
* LOCAL ARRIVAL TIME | * LOCAL ARRIVAL TIME | ||
* LOCAL ARRIVAL UTC | |||
* Planned flight duration | * Planned flight duration | ||
* Planned craft type | * Planned air craft type | ||
* | * Planned air craft version | ||
* Operating Carriers (currently only LH, 4Y & VL) | |||
* Codeshares | * Codeshares (list of all codeshares for the flights operated by the operating carriers) | ||
====== Screenshare ====== | ====== Screenshare of Leading LH System (SCHED-Connect) ====== | ||
[[File:LH SCHED Connect.png|800x800px]] | [[File:LH SCHED Connect.png|800x800px]] | ||
== | ====== Scheduling and Transmission ====== | ||
* Every day for the 12 months | |||
* Transmission to SFTP server within reach of LH Core Digital. | |||
* LH Core Digital picks it up from there and processed it into Flightplan data | |||
* Then reshares over SLH to all data internal consumers | |||
====== Processing on Kordeus side ====== | |||
* into one standard Flighplan of LH operated flights (startdate <code>01.01.2026</code> - end open) | |||
* into one standard Flighplan of 4Y operated flights (startdate <code>01.01.2026</code> - end open) | |||
* into one standard Flighplan of VL operated flights (startdate <code>01.01.2026</code> - end open) [Bus, Intermodals] | |||
Latest revision as of 10:59, 9 January 2026
This interface is planned to deliver regular flight schedule to its B-Op Consumers.
Required data fields by Kordeus
This delivers the planned flights:
- FLIGHT NUMBER
- Period of operation (Period start, Period end, weekdays, monthly, exact dates)
- FROM (Departure Airport)
- TO (Arrival Airport)
- LOCAL DEPARTURE TIME
- DEPARTURE TIME UTC
- LOCAL ARRIVAL TIME
- LOCAL ARRIVAL UTC
- Planned flight duration
- Planned air craft type
- Planned air craft version
- Operating Carriers (currently only LH, 4Y & VL)
- Codeshares (list of all codeshares for the flights operated by the operating carriers)
Scheduling and Transmission
- Every day for the 12 months
- Transmission to SFTP server within reach of LH Core Digital.
- LH Core Digital picks it up from there and processed it into Flightplan data
- Then reshares over SLH to all data internal consumers
Processing on Kordeus side
- into one standard Flighplan of LH operated flights (startdate
01.01.2026- end open) - into one standard Flighplan of 4Y operated flights (startdate
01.01.2026- end open) - into one standard Flighplan of VL operated flights (startdate
01.01.2026- end open) [Bus, Intermodals]