Introduction

Overview

This service description defines one service with a set of operations to create, update and flight schedules. The service is airport oriented as the slot allocation is by it's nature airport oriented. The airport implements this service and the slot coordinator uses it.

All data elements are defined by the Airport Data Dictionary.

Implementation considerations

Any implementation of this service MUST use the WSDL and XSD files provided here: WSDL and XSDs

It is however up to the service provider which data elements to support. To enable this most elements are optional. The user of the service (the slot coordinator) must however provide enough information to make information provided unambiguous and meaningful.

Any service provider (the airport) should make available documentation about the actual implementation, including:

• • the address of the service.
  • the connection detail. As this service updates information at the airport it is expected that a secure communication setup is necessary.
  • any limitations in the implementation.

Purpose of this service description

This service description has the following purpose:

• • • Describe of service in enough detail for a service provider to implement it.
    • Describe the service so that a client (of this service) developer can use it.
    • Make available the WSDL and XSD files necessary to implement and use the service.

Intended readership

• • IT architects
  • Developers
  • Business architects
  • Interested parties in the aviation community

Service overview

High level

The figure below shows a typical setup.

• The slot coordinator creates client software, the "Slot System AODB Client" below, which is responsible for communicating with the "AirportSlotDataService" provided by the airport. The "AirportSlotDataService" will typically be a front end service for some AODB (Airport Operational DataBase) software.
• Based on events in the "Slot Coordinating System" the "Slot System AODB Client" will insert, update or delete information in the AODB using the "AirportSlotDataService".
  

Operations overview

The "AirportSlotDataService" provides 4 operations, as shown below.

Signatures of the operations

The figure below shows the available operations on the FlightSlotDataService. The operations are described in detail in Service operations.

Service operations

Data entities

XML Usage

WSDL and XSDs