Airport Services

System and Message Overviews

Document Version: 5.2AAMessages

Date: March 3, 2014


Copyright © 2009-2021 Jeppesen. All rights reserved. Your use of the AIM Bookshelf and all supporting documentation is subject to a separate license agreement between you and Jeppesen, a copy of which is included in the zip file or can be obtained from Jeppesen. The AIM Bookshelf is delivered "AS IS" without warranty of any kind and is not guaranteed to be free from errors or defects. You rely on the AIM Bookshelf at your own risk. No support for the AIM Bookshelf is implied through its publication. The AIM Bookshelf is intended solely for use as a reference and examples of interfaces to Jeppesen systems. Jeppesen may revise, update or cease publication at any time, without notice. Building to the specifications set forth in the AIM Bookshelf does not mean that your intended integration needs will be met or that an interface will function as documented. We recommend contacting Jeppesen directly to discuss professional services options with respect to production application integration and validation efforts.

 


Document Revision History

The following revision history table reflects all substantive changes to this document.

Date

Description of Updates Made

01-October-09

Updates to AS001 message.

31-July-10 Updated AS001 from DRAFT to version 1.
30-August-10 Updated links for new Bookshelf directory structure.
23-July-13 New XSD
3-March-14 New XSD


Table Of Contents

 


1  Introduction

This document defines the interfaces which govern the interchange of data between an Airport Services system and other systems within an Airline Operation Center (AOC).  Each AOC interface is represented by a message described in an associated XSD (XML Schema Definition). The XSD defines and enforces the required, optional, and conditional data that can be included in a message.

1.1  Audience

The intended audience for this document includes existing and potential Jeppesen customers, integration partners, and personnel with roles associated with application architecture, application development, system testing, implementation, and application support within Airport Services.

1.2  Scope

This document discusses the Airport Services messages currently supported by the Jeppesen Solution Integrator. Each message description includes the following:

  • Overview for common message uses within an AOC
  • Message Version Summary listing all available versions of each message
  • Links to the message specifications including direct links to XSD documentation, where you can explore the XSD hierarchy and interface specifications in a navigable HTML format
  • Links to the XSD source code
  • Links to sample XML messages for each AIM message

Other data interfaces or formats not included in this document will be considered custom and not supported.

1.3  XML Schema/XSD

The XML schema for this ICD is published in the following file: AirportServices.XSD

 

2  Message Summary

Table 2-1 lists the messages that can be sent or handled by the application. The messages originated by this application (messages that begin with “AS”) are further discussed in Section 3 AOC Interface Messages.

Table 2-1 Message Summary

ID

Message

Publish

Subscribe

Request

Response

AS001

Airport Field Report

X

 

   

 

3 AOC Interface Messages

The following messages are processed by the Airport Analysis system.

3.1 AS001 – Airport Field Report

3.1.1  Message Overview

This message can be used to provide three types of reports:  Field reports, Frequency Reports, and Deicing Reports. 

A Field Report may either consist of field conditions, or both field conditions and frequency information.  Field conditions include local airport information such as runway, taxiway, and gate status/conditions for airports within the customer's carrier network. The frequency report/information contains local station frequencies used by local station personnel for use by pilots, dispatchers, and ground personnel at the local airport (station). The Field Report is used routinely, or on an ad-hoc basis for airports or off-line (off the carrier's network routes) Alternate airports.

The Deicing Report is used by dispatchers and contains local airport deicing information such as whether deicing is in effect or not, type of deicing fluid used, location, radio frequency(s) used for communications to deicing trucks, and estimated deicing time to OFF time at the local airport.   

3.1.2  Message System Flow

This message interacts with the systems as shown in Figure 1.

AS001 Message System Flow

Figure 1. AS001 message system flow

3.1.3 Message Details

The following table provides details on the message version and includes links to the message’s technical specification.

Message Version

AS001 v1

Message Header Details

msgName: AS001
msgClass: PUBLISH
version: 1

Message Specification

AS001 AirportFieldReportType

Defined in XSD

AirportServices.xsd

Sample Messages

AS001v1AirportDeicingReport.xml
AS001v1AirportFieldReport.xml
AS001v1AirportFrequencyReport.xml

Message Version History Original publication of version 1 of message.