SITA Departure Control Services Check-In Database User Guide

Passenger Solutions
SITA Departure Control Services

Check-In Database
User Guide
Revision: 9.2
Revision Date: 30-Nov-2015
Copyright © SITA Information Networking Computing USA Inc 2015. Confidential. All Rights Reserved.
Copyright Notice
Copyright © SITA Information Networking Computing USA Inc 2006-2015
Confidential Information
All Rights Reserved
The information contained in this document is the property of SITA. No part of this document may be
reproduced, stored in a retrieval system, or transmitted in any form, or by any means; mechanical,
photocopying, recording, or otherwise, without the prior written consent of SITA. Under the law, copying
includes translating into another language or format. Legal action will be taken against any infringement.
The information contained in this document is subject to change without notice and does not carry any
contractual obligation for SITA. SITA reserves the right to make changes to any products or services
described in this document at any time without notice. SITA shall not be held responsible for the direct or
indirect consequences of the use of the information contained in this document.
Table of Contents
1. Introduction .................................................................................................................................... 1
1.1. User Guide .............................................................................................................................................. 1
1.2. Guide Objectives..................................................................................................................................... 1
2. Airline Revenue Booking Designator ........................................................................................... 3

2.1. Master/Equivalent Classes (CD) ............................................................................................................. 3
2.1.1 Initial CD Table Creation ............................................................................................................. 3
2.2. Additional CD Tables Creation ................................................................................................................ 4
2.2.1 Requirements .............................................................................................................................. 4
2.2.2 Entry to Create Additional CD Tables .......................................................................................... 4
2.3. Entry to Display CD Tables ..................................................................................................................... 5
2.4. Entry to Amend or Update CD Tables within Flight Schedules ............................................................... 5
2.4.1 Aircraft/Equipment Change ......................................................................................................... 6
2.5. Aircraft Configuration Tables (CND:A) .................................................................................................... 6
2.6. First Available Table (CND:FAVAIL) ....................................................................................................... 8
2.7. Cancel a CND Table Number ............................................................................................................... 10
3. Check-In Station Creation ........................................................................................................... 11

3.1. Check-In Station Creation (DRC:) ......................................................................................................... 11
3.2. Check-In Station Delete (DRD:) ............................................................................................................ 11
4. Station Data .................................................................................................................................. 13

4.1. Passenger Weight Tables (CW:)........................................................................................................... 13
4.2. Staff Priority Tables (PZ:) ...................................................................................................................... 16
4.3. Passenger Message Address Tables (CX:) .......................................................................................... 19
4.4. Airport Gate Numbers (AZ:) .................................................................................................................. 24
4.5. Location Travel Times (LZ:) .................................................................................................................. 27
4.6. Static File Maintenance Display (SFM:) ................................................................................................ 30
5. Seat Maps ...................................................................................................................................... 31

5.1. Seat Map Creation (EQC:) .................................................................................................................... 31
5.2. Seat Map Creation Error Codes ............................................................................................................ 37
5.3. List of Seat Maps (ED:) ......................................................................................................................... 43
SITA Departure Control Services Check-In Database User Guide

Introduction
Revision Date: 30-Nov-2015, Revision: 9.2 Page v
Copyright © SITA Information Networking Computing
USA Inc 2015. Confidential. All Rights Reserved.
5.4. Seat Map Display (SEM: / SEI:) ............................................................................................................ 44
5.4.1 By Using the SEM Transaction .................................................................................................. 44
5.4.2 By Using the SEI Transaction .................................................................................................... 44
5.5. Amend Seat Map (EQ: / EQI:)............................................................................................................... 45
5.5.1 By Using the EQ Transaction .................................................................................................... 45
5.5.2 By Using the EQI Transaction ................................................................................................... 45
5.6. Delete/Amend Seat Map Date Ranges (EXM:) ..................................................................................... 46
5.6.1 Delete Seat Map ........................................................................................................................ 46
5.6.2 Amend Seat Map Dates ............................................................................................................ 46
5.6.3 Re-instating a Seat Map ............................................................................................................ 47
5.7. Movable Partitions (MP) ........................................................................................................................ 49
5.8. Split Compartments (F Y C Y)............................................................................................................... 50
5.8.1 Two Class Seat Maps (Split Compartments) ............................................................................. 51
5.8.2 Two Class Seat Maps (First Class Behind Second Class) ........................................................ 52
6. Flight Schedules Entries (FDC) .................................................................................................. 53

6.1. Flight Schedule Build / Display (BF:T/) ................................................................................................. 53
6.1.1 Build Flight Schedule ................................................................................................................. 53
6.1.2 Display Flight Schedules ........................................................................................................... 57
6.2. Amend Flight Schedule ......................................................................................................................... 57
6.2.1 Date Change ............................................................................................................................. 58
6.2.2 Application or Configuration Change ......................................................................................... 58
6.2.3 Routing Change......................................................................................................................... 59
6.2.4 Departure or Arrival Time Change ............................................................................................. 59
6.2.5 Cancellation of Schedule ........................................................................................................... 60
6.2.6 Copy Schedule .......................................................................................................................... 60
6.3. Staged Flights List (SFL:)...................................................................................................................... 61
6.4. Activate Flights (BPR: / ACT) ................................................................................................................ 62
6.5. Active Flights List (AFL) ........................................................................................................................ 63
6.6. Flight Schedule Period (FPD) ............................................................................................................... 63
6.7. Single Day Schedule Create / Change (DFD:) ...................................................................................... 64
6.8. Flight Data Display (CSD:) .................................................................................................................... 67

Introduction
Page vi Revision Date: 30-Nov-2015, Revision: 9.2
USA Inc 2009-2015. Confidential. All Rights Reserved.
6.9. Flight Data Amend (CSM:) .................................................................................................................... 67
7. Passenger Baggage Allowance/Excess Rate ............................................................................ 71

7.1. Free Baggage Allowance from Electronic Ticket Record ...................................................................... 71
7.2. Passenger Baggage Allowance Table .................................................................................................. 71
7.3. Passenger Excess Baggage Rates (JCD:) ........................................................................................... 73
8. Database Check List .................................................................................................................... 74

8.1. Check-In Entries ................................................................................................................................... 74
8.1.1 Seat Map Creation..................................................................................................................... 74
8.1.2 Aircraft Configuration Table (CND) ............................................................................................ 74
8.2. Flight Schedule Entries ......................................................................................................................... 74
8.3. Station Data Entries .............................................................................................................................. 75
9. Teletype Addresses ..................................................................................................................... 76

9.1. System Addresses ................................................................................................................................ 76
10. Conversion Table (General) ........................................................................................................ 77
11. Glossary ........................................................................................................................................ 79
12. Index .............................................................................................................................................. 83

Introduction
Revision Date: 30-Nov-2015, Revision: 9.2 Page vii
Introduction
Page viii Revision Date: 30-Nov-2015, Revision: 9.2
USA Inc 2009-2015. Confidential. All Rights Reserved.
Revision History
Revision Date Changes
7.1.1 26 Mar 2008 Replaced Passenger Message Address Tables section.
7.1.2 31 Mar 2008 Removed underline after PZM entry, added information to the list of
configuration table section.
7.2 30 Apr 2008 Customer release.
7.2.1 11 Aug 2008 Section 4.2 – Staff Priority Tables (PZ:) Dash inserted into modify entry.
Section 5.2 – Seat Map Creation Error Codes EQC 03 error added to
table.
7.3 29 Aug 2008 Customer release.
7.3.1 30 Apr 2009 Section 5.1 – Added EQC entry with Zones
Section 5.2 – Added Seat Map Creation errors
8.0 30 Apr 2009 Finalized revision 7.3.1 for publication.
9.0 31 Dec 2013 • Moved original Section 4.3 Master / Equivalent Classes to be
Section 2.1
• Added footer for even page numbers
9.1 30-Apr-2015 Maintenance release
9.2 30-Nov-2015 Added Section 7.1 to describe SDCS capability to determine Free
Baggage Allowance from Electronic Ticket Record.

Introduction
Revision Date: 30-Nov-2015, Revision: 9.2 Page ix
Introduction
Page x Revision Date: 30-Nov-2015, Revision: 9.2
1. Introduction
1.1. User Guide
The guide covers database requirements for Check-in.
Note: These User Guides are designed as a guide only to help the learning process of the SITA DCS
database creation.
1.2. Guide Objectives

This guide is designed for Airline Database Specialists, and assumes that the specialist will have some
previous knowledge of either manual check-in or knowledge of another automated DCS system.
The guide has two primary objectives for SDCS database specialists:
1. A clear understanding of all the SITA DCS applications (CKI and FDC), and how they relate to each
other.
2. The ability to create, amend, change, or update, when necessary, the following:
• Aircraft seat maps.
• Flight schedules.
• Any station data such as passenger weights, staff priorities, airport gate numbers, and message
address files.

Introduction
Revision Date: 30-Nov-2015, Revision: 9.2 Page 1
Introduction
Page 2 Revision Date: 30-Nov-2015, Revision: 9.2
2. Airline Revenue Booking Designator
2.1. Master/Equivalent Classes (CD)
The CD Table specifies the concept of master classes and any equivalent classes for the airline revenue
booking designator (RBD). CD Tables must be created for handled airlines as well as the host carrier.
Note: Each airline may have a maximum of nine different Booking Designator (CD) Tables but at least one
must be created for each handled airline as well as the host carrier. During initial creation, the default CD
Table will always be 1.
2.1.1 Initial CD Table Creation
The entry is:
CD: AIRLINE
 New CD Table:
►CGC: XS 1;
Classes are entered after the table number

Note: RBD order in the CD Table should be the same as the SITA Reservations schedules.
 Completed CD Table
CGC: XS 1; FPA/CDZ/J/YBKHSQENTLUV
Explanation:
Field Explanation
F/C/J/Y In this example F, C, J, and Y are Master Revenue Booking Designators.

Classes inserted after each master class are sub-classes.
Example
P and A are sub-classes of F.
Note:
If the table needs modification, type over the old data then transmit the screen
again.
It is possible to display the classes created for a flight by entering:
CD:FLIGHT/DATE/ALL
 Individual Flight CD (CD:XS983/./ALL)

ATL 310/200 FPA12CDZ30YBKHSQENTLUV150
LGA 310/200 FPA10CDZ20YBKHSQENTLUV140
BOS 310/200 FPA12CDZ30YBKHSQENTLUV150
CDG
Explanation:

Airline Revenue Booking Designator
This table displays the routing, the aircraft type, version, and the class and capacity (not configuration)
of the particular flight segment.
Error Responses
Response Explanation
AIRLINE Invalid airline code or missing.
CLASS Invalid character specified for class.
DUP Class code is specified more than once in the entry.
2.2. Additional CD Tables Creation

Based on business needs of the airline, additional CD Tables can be created.
2.2.1 Requirements
The following requirements must exist to use the concept of additional CD Tables:
1. All Additional CD Tables must have identical classes of service.
Example:
CD Table 1 and 3 listed below have different compartment layout but identical class of services.
CD: XS 1
CD: XS 3
CGC: XS 3; YBKHSQENTLUVCDZJFPA
2. Seat maps and aircraft configuration tables- master classes must match with those defined on
each respective CD Tables
Example:
Following aircraft seat map and configuration listed below have identical master classes with
above CD1 and 2.
ED: XS
1.310/200 F12C30Y150 30OCT14-OPEN
2. CRJ /200 Y48 30OCT14-OPEN
CND: XS/A
349 XS 310 200 FPA/12 CDZ/30 YBKHSQENTLUV/150
352 XS CRJ 200 YBKHSQENTLUVCDZJFPA/48
2.2.2 Entry to Create Additional CD Tables

The transaction to create addition CD table is: CGC: Airline Table Number
 Additional CD Table:
► CGC: XS 2;
Classes are entered after the table number.

Warning: The transaction to create additional CD Table is used when the initial (DEFAULT) CD Table has
been already defined and created.

Note: RBD order within the CD Table should be the same as the one defined in SITA Reservations
schedules.
 Completed CD 2 Table
CGC: XS 2; CDZJFPA/YBKHSQENTLUV
Note: When modifying a CD Table, the authorized agent must first retrieve the specific table number to
make applicable changes then transmit.
2.3. Entry to Display CD Tables

An authorized agent can use the SFM function to display all created CD Tables for a specific airline.
Entry is:
SFM: CD Airline
Example:
SFM: CD XS
CGC: XS 2; CDZJFPA/YBKHSQENTLUV
CGC: XS 3; YBKHSQENTLUVCDZJFPA
CGC: XS 4; JCDZFPA/YBKHSQENTLUV
Note: If Airline code not included in the entry, the system displays all the CD Tables created for the Host
and all Handled Airlines.
Note: To update or remove any RBD within a specific CD Table, the following process must be followed:
1. Display the selected Table.
2. Add or remove specific RBD
3. Transmit once completed.
2.4. Entry to Amend or Update CD Tables within Flight Schedules

An Authorized agent can amend or modify any CD Table through the CSM Data Screen of a specific flight
schedule. The change can be for a single day or for flight period with multiple frequencies.
Entries to amend the CD Table:
CSM: Flight/Date
1. Authorized agent requests retrieval of a CSD/CSM screen of a valid flight schedule (can be for
one date or a flight period).
2. The CSD/CSM screen will display a new field labeled ‘CD’:

1_ BUD CTL-OFC 0_ SD 2300 ED 0200+1 BDT 2230
EQ 747/ABC WTN 1_ CWT 262143 CFG F6C22YE480 CD 1
TCKI TCI TYPE NAM SS____ GO-SHOWS ___________
POS GATE GATES
MSG
PTM_TPM_PIL_PSM_COM_IDM_SOM_BTM_PFS_IFM_API_FTL_PRL_ETL_PIM_CAT___
TPL_______________________________________________________________
2_ FRA CTL-OFC 0_ SA 2358
SEGMENT DATA _________________________________________________
3. The default CD Table will always be 1. The agent is allowed to update this field to the CD Table
number required. If the CD Table number entered has not been created, then the error response
will be ‘CD Table Does Not Exist’.
4. If the flight is a multi-leg flight, then the required CD Table must be entered for each leg unless
using the default one (CD 1).
Note: On a multi-leg flight, the rule is that only matching CD Tables are allowed. So if the CD
Table required is 2, then CD 2 must be used for each segment leg. If an authorized agent tries to
enter a different table, the system will verify that all tables are the same or reject the entry with
error response: “‘CD Tables Not Matching”.
5. Once the agent has made the update, the entry is submitted to the system.
6. If the entries are valid, the CSD/CSM screen is updated. If any validation error is found, the
system responds with the applicable error and the agent must correct the error before re-
submitting.
2.4.1 Aircraft/Equipment Change
When the concept of additional CD Tables is used in conjunction with seat map including configuration
change, then the authorized agent must follow the check list for aircraft type and version change listed in
the Check-In Supervisor Manual.
2.5. Aircraft Configuration Tables (CND:A)

This screen displays a list, in numeric order, of all the aircraft configurations available in the CND table.
This table number is used when creating schedules (see BF:T) to identify to the system which aircraft type
and configuration to use. The CND contains all the aircraft configurations created in the system for the
host carrier as well as for all the handled carriers. A specific airline can be requested.
The entries are:
CND:A
CND:AIRLINE/A

 CND:A Response:
CND:A
1 BA 737 999 C/12 Y/138
2 BA 737 300 C/12 YMLQ/120
3 BA 737 C12 C/12 YMBL/120
4 BA 737 011 C/12 Y/138
5 OS 310 324 C/12 YMLQ/120
6 BA 100 T204 Y/100
7 OS 737 300Z C/12 Y/120
8 BA 737 PJ C/12 YMBL/120
9 OS 310 324 F/12 CD/30 YB/150
10 OS 146 7777 J/12 Y/62
+
Explanation:
The system displays a full page of all the numbers used, in numeric order. If any number is not used, it is
absent from the list. To move to the next page, enter PN (or NP) after the cursor position (usually
displayed at the bottom of the screen).
It is possible to start a display from a specific CND number.
The entry is:
CND:R/NUMBER

CND:R/78
It is also possible to display the list by particular aircraft type.
The entry is:
CND:A/AIRCRAFT TYPE
CND:AIRLINE/A/AIRCRAFT TYPE
 CND: Response for Specific Aircraft Type

CND:A/737
10 BA 737 A C/18 M/88
12 BA 737 B C/12 MK/90
50 LH 737 A M/106
51 LH 737 B C/36 M/70
52 LH 737 C C/40 M/66
78 ET 737 A C/12 YK/88
90 AF 737 A C/34 YMKG/76
Explanation:
This entry can be either for all 737 aircraft in the table or by individual airline.

2.6. First Available Table (CND:FAVAIL)
When a new aircraft configuration entry is required, either a known available number can be input in the
entry (CND:16), or the system can find the next available number (in numeric order).
The entry is:
CND:FAVAIL
 A Blank CND: Table

CNU: TABLE/ ___4 AIRLINE CODE: ___
EQUIPMENT: ___ VERSION: ___ CLASSIFICATION: _ WIDE_BODY: _
RES CHARACTERISTICS:
COMPARTMENT 0 CLASS(S):______________________ SEATS: ___
 A Completed CND: Table for an Upper Deck Equipped Aircraft

CNU: TABLE/ __11 AIRLINE CODE: 2M_
EQUIPMENT: 747 VERSION: SP___ CLASSIFICATION: J WIDE-BODY INDICATOR:
COMPARTMENT 1 CLASS(S): FAP_______________________ SEATS: 8___
COMPARTMENT 2 CLASS(S): CDIJ______________________ SEATS: 14__
COMPARTMENT 3 CLASS(S): YSXHUGNLWEOZBKQTV_________ SEATS: 319_
COMPARTMENT 4 CLASS(S): __________________________ SEATS: 0___
COMPARTMENT 5 CLASS(S): __________________________ SEATS: 0___
Explanation:
Field Explanation
AIRLINE Airline code of the applicable Host or Handled Airline.
EQUIPMENT Three-letter aircraft-type code is entered here. Use the aircraft type code
entered in the Seat Map creation.
VERSION Version code is entered here. This code may vary in size from one to five
alphanumeric.
CLASSIFICATION Specifies to the system whether the aircraft has jet engines or propellers. The
most common entries are:
P - Prop or Turbo Prop
J - Jet (this is also the system default)
WIDE-BODY Specifies to the system whether the aircraft is a wide or narrow body. The
INDICATOR: valid entries are:
Blank - Narrow body
W or * - Containerized
COMPARTMENT Compartment number. The system assigns the number when the screen is
transmitted. The system allows a maximum of five compartments.

Field Explanation
CLASS Master class code plus any equivalent class codes are entered here. It is
important that the master class code plus any equivalent class codes are
entered in the same order as the class codes entered in the CD:AIRLINE table
and those used by the airline's Reservation system for a flight using this CND
table, otherwise there will be wrong information on the PFS (passenger final
sales) message passed back to the Reservations system at the end of the
flight. FUI updates should not affect the Check In display. Not all CD Classes
may be shown.
It is best to create a CND table for the possibility of changing to an aircraft with
a different compartment layout. For example: you may have a CND showing
F/C/Y and subsequently need to change to a two-compartment aircraft C/Y. In
this case you should have one CND showing F/C/Y and another showing
CF/Y.
SEATS Maximum number of seats on the aircraft for this class (plus any equivalent
classes).
CND:
 A Filled-in CND Table Number:

CNU: TABLE/ 96 AIRLINE CODE: XS
EQUIPMENT: 747 VERSION: A CLASSIFICATION: J WIDE_BODY: *
COMPARTMENT 0 CLASS(S):F____________________ SEATS: 18
COMPARTMENT 0 CLASS(S):C____________________ SEATS: 32
COMPARTMENT 0 CLASS(S):YBM_________________ SEATS: 206

2.7. Cancel a CND Table Number
A CND table number is canceled by displaying the table number required, erasing the EQUIPMENT entry,
'tab' to the VERSION entry and transmitting the screen. The response should be 'ACCEPTED'.
 To Cancel Table 126 (display table CND:126):

CNU: TABLE/ _126 AIRLINE CODE: XS
EQUIPMENT: 727 VERSION: A CLASSIFICATION: J WIDE_BODY: _
Erase the 727 (after Equipment) and 'tab' to the A (after Version), and transmit the screen.
Response of Cancelled CND Table
CNU: TABLE/ _126 AIRLINE CODE: XS
EQUIPMENT: ___ VERSION: A CLASSIFICATION: J WIDE_BODY: _
ACCEPTED
CND table number 126 will be blank and available for re-use when required.
Error Responses
A/C VERSION CONTENT ERROR Invalid entry. Special characters not allowed. Must be alpha or
numeric.
ILLEGAL CHAR Entry not alpha.
INVALID INPUT Entry not numeric.
WIDE-BODY IND The only valid indicators are blank or * or W.

3. Check-In Station Creation
3.1. Check-In Station Creation (DRC:)
Before creating any flights for check-in, the stations on the planned routing must first be created via the
DRC: transaction. This includes the originating station for the host airline, and for any handled airlines. If
this is not done, then it is not possible to create the flight for CKI.
Note: The DRC: transaction is for CKI stations only, for load planning, these stations must be created via
the LAID: screen.
The first entry should be to check if the station has already been initialized for CKI.
The entry is:
DR:AIRLINE/STATION
Response to DR:XS/ATL
►DR:XS ATL
CITY
Explanation:
If the response is 'CITY', it means this station has not been initialized for CKI; therefore, the second entry
is to initialize the station.
The entry is:
DRC:AIRLINE/STATION
Response DRC:XS/ATL
►DRC:XS ATL
There is no need to enter anything more as this transaction initializes this station for CKI.
Note: If after the DRC entry, the response is still City, it indicates that the station is not built in the CITY
files (Check by entering CITY:V/ABC). Contact a Reservations expert or the SITA DCS Support team for
assistance.
3.2. Check-In Station Delete (DRD:)

If for some reason a CKI created station needs to be deleted from the system, then the entry is:
DRD:AIRLINE/STATION
Note: Be careful when deleting a station as this transaction will also delete any CX address tables
created for that station, and if it is an originating Automated DCS station, it will also delete any created
baggage allowance tables (JXD/JCD).

Check-In Station Creation
Check-In Station Creation
4. Station Data
4.1. Passenger Weight Tables (CW:)
This entry specifies the passenger weights and baggage details used by the system for check-in. Each
airline may have a maximum of nine different passenger weight tables but at least one must be created for
each handled airline as well as the host carrier.
The entry is:
CW:AIRLINE NBR
(If number not specified system defaults to 1)
Response of an Empty Weight Table (CW:XS1):
CWC:XS 1
►/18JULY04/0 KG GN
►PMAN MMAN FMAN CMAN IMAN BMAN HMAN EMAN
LAST DATE SPANNED _ (OPEN)
►
Explanation:
Field Explanation
CWC:XS 1 The function designator (CWC), plus the airline code (XS) and table number (1).
18JULY04 The date entered here is normally the effective date. For a new unused screen,
the system inserts the current date of display (today's date). It is possible to
have a date change, -/01APR97-30SEP97.., so the system will know if it needs
to change to different seasonal weights. The system allows a maximum of three
date ranges (with different passenger weights for summer and winter). See the
example below.
Note: When amending a CW table, it is important to amend this date to the
current (today's) date, otherwise the entry will be rejected.
 CW Table with Date Ranges and Weight Changes

CWC:XS1
►/01APR06_30SEP06/95 KG GN
►M75 F65 C35 I10 BMAN H0 E20
►/01OCT04_31MAR05/100 KG GN
►M78 F68 C43 I12 BMAN H0 E25
►/01APR04/95 KG GN
►M75 F65 C35 I10 BMAN H0 EMAN

Station Data
Field Explanation
95 KG GN This entry specifies the average weight of passenger and baggage(95) (for
planning purposes), the weight calculation used (KG or LB), and whether
gender (G), and number of bags (N), are required at check-in. If either item is
not required, it is deleted.
PMAN MMAN FMAN CMAN IMAN BMAN HMAN EMAN
These items are identified as follows:
P - Passenger (used for non gender flights)
M - Male (used for gender flights)
F - Female (used for gender flights)
C - Child
I - Infant
B - Baggage
H - Hand baggage
E - EDIFACT standard bag weights
If MAN (mandatory) follows the item, it means the actual weight of the item
must be entered in the Check-in transaction.
If a numeric weight follows the item, the system uses this weight as the standard
weight at check-in.
If P (Passenger) is specified, it must have a numeric weight, because MAN is
not allowed with this item. Also, P cannot be entered with M and F. The H
(Hand baggage) item must display MAN if the B item specifies MAN. If the H
(Hand baggage) entry is not mandatory any numeric value can be added to the
H item, but it will always be displayed as 0 (H0).
If N (Number of Bags) is deleted, then B cannot show MAN. It can show a fixed
weight value, but this is ignored during check in.
LAST DATE This denotes whether this table has an end effective date (on which date the
SPANNED - system deletes all the information from this table number) or whether it is open
(OPEN) ended.
Note: The best way to enter a new passenger weight table is to display the
table number required, enter, amend or delete the details as needed, and then
transmit after the H0 item. Do not forget to amend the date to today's date.
 CW Table for a Gender Required Flight

CWC:XS 1
►/18JULY06/95 KG GN
►M75 F65 C35 I12 BMAN H0 E20
►

Station Data
Field Explanation
LAST DATE
SPANNED -
 CW Table for a Non-Gender Flight
(OPEN) CWC:XS 1
(Continued) ►/18JULY06/100 KG N
►P78 C43 I10 BMAN H0 EMAN
Error Responses
BAG Invalid BAG entry or missing.
CONFLICT P is only allowed for non-gender flights, and M and F are only allowed for
gender flights. H cannot be mandatory unless B is mandatory. PMAN is
not allowed.
DATE An invalid date is specified.
NUMBER A numeric entered is either too large or invalid.

Station Data
4.2. Staff Priority Tables (PZ:)
This table maintains the priority onload of Revenue and Airline staff passengers in the order of the airline's
preference. The system uses this table to determine the correct order of onload (or offload if necessary)
of standby passengers at flight close-out. This table must be created for each handled airline as well
as the host carrier.
The display entry is:
PZ:AIRLINE
Response of a Default (no Airline Priorities) PZ Table
TRAVEL STATUS BOOKED WAITLISTED UNBOOKED
CODE PRIORITY PRIORITY PRIORITY
__________ __________ __________ _________
ALL (DEFAULT) 99 99 99
 A Created PZ Table
__________ ________ __________ _________
REVENUE 1 3 7
S1/ 2 6 # 10
R1 4 8 # 11
N1 5 # 9 # 12
#S2 # 30 # 30 #? 60
#R2 # 40 # 40 #? 65
#N2 # 50 # 50 #? 70
#OTHER # 90 # 90 #? 99
Explanation:
Field Explanation
TRAVEL STATUS The status codes required by the airline are entered here (each handled airline
CODE will have its own desired codes). The REVENUE code must always be the first
entry. A (/) after the code (S1/) means that the 'Date of Joining' cannot be
entered at check-in. If there is no (/), then the 'Date of Joining' may be an
optional entry at check-in.
The system can identify passengers who have the same codes, by onloading
them in priority of their 'Date of Joining' (providing this was added by the agent at
the time of check-in). If a (#) is specified before the code (#S2), this means this
passenger (PAD) is available for disembarkation (offload) regardless of booking
status. If the (#) is only displayed before a number, then this means this
passenger is available for disembarkation (PAD) under the specified conditions
(WAITLIST or UNBOOKED). The (?) indicates the passenger has a 'space
available' ticket and although the passenger may be listed on the PNL, he will
never be booked, and his acceptance will be based on the PAD (ID) limits rather
than the booking figures.

Station Data
Field Explanation
BOOKED Booked priority of the passenger. The lower the number, the higher the priority.
PRIORITY A booked passenger should not need a standby priority, however in certain cases
(e.g., when a flight is over booked) a booked passenger may check-in and go on
the standby list. A booked passenger who goes on the standby list should have a
higher priority than someone without a confirmed booking.
WAITLISTED Priority order for passengers who were entitled to make a booking, but because
PRIORITY the flight was full, they have only been able to get a waitlist booking. They should
have a lower priority than a booked passenger, but a higher priority than a
passenger who is not listed on the flight. Certain staff travel codes do not allow
the passenger to book on a flight (space available passengers); therefore the
booked and waitlist priorities can be the same.
UNBOOKED This is the priority order for passengers who have 'open' or 'space available'
PRIORITY tickets, and who were not listed on the PNL. Therefore a 'space available'
passenger who is not entitled to make a booking but who previously listed
themselves on a flight, should get a higher priority than a 'space available'
passenger who just turns up 'on chance' for a flight.
Apart from the display entry (PZ), there are two other types of entries that can be
made for this priority table:
1. The create entry (PZC)
2. The amend or modify entry (PZM)
CREATE ENTRY The PZC entry creates the table. After it is created, any additions or deletions are
made by the modify entry.
The initial create entry is:
PZC:AIRLINE;CODE,NBR,NBR,NBR;CODE,NBR,NBR,NBR etc.
An example of the initial create entry is:
PZC:XS;REVENUE,1,3,7;S1/,2,6,#10;R1,4,8,#11;#S2,30,30,?62
Note: Make sure the (,) and (;) are in the correct places. The (,) comes after
individual items of a code, and the (;) comes between each set of codes.
 A Designed PZ Display:
____________ ________ _________ _________
REVENUE 1 3 7
S1/ 2 6 # 10
R1 4 8 # 11
#S2 # 30 # 30 #? 60

Station Data
Field Explanation
MODIFY ENTRY The modify entry (PZM) must be preceded by the PZ display, because the modify
entry does not specify airline, and the system needs to know which airline table to
modify. For codes that are being added a plus (+) is entered followed by the
code, and for codes being deleted a minus (-) is entered followed by the code.
An example entry to add further codes to the previous create entry is:
PZM:+N1,5,#9,#?12;+#R2,40,40,?65;+#N2,50,50,?70,+#OTHER,90,90,?99
Note: The important thing is to enter the (+) before every code, and check the (,)
and (;) are in the correct places.
To delete a code, the entry is (after a previous PZ display):
PZM:-#OTHER,90,90,?99
Note: When deleting codes, it is important the identical information previously
entered, is re-entered here. If it is required just to change one priority number,
the whole code has to be deleted, and then re-entered with the corrected data (it
is not possible just to amend one individual priority number for a code). It is
possible when modifying the table to use the (+) and (-) in the same entry.

PZM:-N1,5,#9,#?12;+N1,5,#9,#?14
Error Responses
DUP Duplicate input items are specified or the item created already exists.
FORMAT Space available indicator '?' input without PAD indicator '#'.
NO DISPLAY A PZ display is required before a PZC or PZM.
REVENUE The REVENUE entry is a mandatory input.
UNABLE The requested entry has an error and cannot be actioned.

Station Data
4.3. Passenger Message Address Tables (CX:)
This table specifies the addresses for which the passenger messages will be dispatched at the end of a
flight. It also specifies certain locations where required warning messages (regarding the flight status) can
be sent. The table is set-up by station, and each station may have any number of tables from 1 to 99
(there is a table 0, but this must be used as a default only). Table 0 is recommended for use with
training and test flights.
By specifying the table number on the CSD:FLIGHT/DATE screen, the system identifies the correct
messages and addresses to dispatch during, and after completion of, a flight. The CSD: display always
defaults to table 0 thus requiring a change to the desired address table number.
An address table must be created for each handled airline as well as the host carrier.
DISPLAY ENTRY
CX:AIRLINE STN NBR (If NBR is not specified system defaults to 0.)
Response of a CX Table Not Yet Created
CX:XS ATL5
NO RECORD
 Address Table 50 for City ATL. (CX:XS ATL50)

CX:XS ATL50
DFL,8567 ALA,CD BAG,CD BKW,CD CCL,3344
CCL,ATLKKXS COM,3344 COM,ATLKPXS COM,CD EQC,CD
PIL,CD PRC,CD PSM,ATLKKXS PSM,ATLKPXS PTM,ATLKKXS
PTM,ATLKPXS PTM,CD FTL,ATLKKXS TPM,ATLAPXS IFM,ATLABXS
ETL/S/AF,ATLRRAF ETL/S/MA,ATLRHMA ETL/S/6A,ATLRH6A
Explanation:
Field Explanation
CODE Check-in message codes required for a given flight. All the codes entered are
optional, except for DFL (default). Every message address table must have a
DFL address, so the system knows where to send a message if it has been
specified on the CSD:FLIGHT/DATE screen and there is no address on the CX:
table for it. The other most common codes used are:
Passenger messages (are dispatched to):
COM - Closeout Message (all stations)
PFS - Passenger Final Sales (originating station only)
PSM - Passenger Service Message (all stations)
PTM - Passenger Transfer Message (all stations)
SOM - Seats Occupied Message (next downline station)
TPM - Teletype Passenger Manifest (all stations)
PIL - Passenger Information List (originating station only)
IDM - Industry Discount Message (next downline station on multi-sector
flights)
Station Data
Field Explanation
IFM - Industry Fallback Message (ITCI partner listed from departure city)
PTM - Passenger Transfer Message (all downline stations having transfers)
FTL - Frequent Traveler List (FQTV accounting system address of host,
handled carrier or code share partner of departing city table)
ETM - EDIFACT Transfer Message (ITCI partner listed from departure city LH
only)
BTM* - Bag Transfer Message (hard coded in system xxx BTxx , xxx = airport
and xx = airline). Entered on CX Table.
API - Advance Passenger Information
PMI - Passenger Manifest Information List
PIM - Passport Information Message
PRL - Passenger Reconcile List
CAT – Catering Message, Special Meals
ETL - Check-in Electronic Ticket List
ETL/W – Checked-in SITA ETDB Electronic Ticket List
ETL/S/xx (or ETL/S/xxx)– Targeted ETL list that contains checked-in e-ticket
passengers of marketing code share partner ‘xx’ (= 2 Character airline code)
or ‘xxx’ (= 3 Character airline code).
Note 1: Even if there is no information, NIL messages are sent to the specified
addresses.
Note 2: Messages PFS/FTL/PRL on code share flights require additional
entries by adding “/S” after the message type. This creates messages for the
marketing carrier, which contains information regarding only the marketing
carrier passengers.
Note 3: Message ETL/S/xxx (or ETL/S/xx) is for Targeted ETL (Split ETL) for
code share marketing partner. The ‘xxx’ or ‘xx’ is for 2 or 3 alpha numeric
character airline code.
Warnings/Advice:
ALA - Aircraft Limit Advice
ALW - Aircraft Limit Warning
BAG - Baggage Removal Warning
BKA - Booking Advice
BKW - Booking Warning
CCL - Flight Closed Warning
EQC - Equipment Change Warning
FCI - FDC Flight Conditions Irregular (abnormal) Warning
FCU - FDC Flight Conditions Unable Warning
FOC - FDC Flight Operational Changes Warning
NME - Non Matching Element (on PNL)
PRC - Protective Cover Warning
ADDRESS The specified addresses where these passenger and warning messages should

Station Data
Field Explanation
be sent. These addresses may be any of the following:
Note: For code share flights messages for the marketing carrier can only be
addressed to the applicable carrier. A check is made to match the airline code
in the address with the marketing airline code in the passenger record.
TELEX - This is the normal Teletype address.
PID NUMBER - This can be any valid PID number (CRT or printer).
CD - Control device (PID NBR is entered on the SDD:FLIGHT screen).
HC - Hard copy associated with the CRT releasing the messages.
NL - This message not required at this station (applies to multi-sector flights
only).
Note: The maximum number of telex addresses per code is limited to 32. ZZ
addresses are the same as Type-B format.
Apart from the display entry (CX), there are two other types of entries that can
be made for this priority table:
1. The create entry (CMC).
2. The amend or modify entry (CMM).

Station Data
Field Explanation
CREATE ENTRY The create entry initially creates the table. After it is created, any additions or
deletions are made by the modify entry.
Note: The system prevents the creation of new address tables for a STATION
unless the default table (0) is built first.
An example of the initial create entry for table 0 is:
CMC:AIRLINE STN 0;DFL,ADDRESS
For table 0, there is no need to add any other codes apart from the DFL. The
reason for this default table 0, is that if any test or training flights are created,
then the passenger and warning messages only go to the DFL address and not
to 'LIVE' addresses.
An example of the initial create entry for other tables is:
CMC:AIRLINE STN NBR;DFL,ADDRESS;CODE,ADDRESS;CODE,
ADDRESS etc.
Note: Every new table can have different codes and addresses, except for
DFL. This code is a mandatory entry for every table created. If a passenger
message (for example the PSM) is required for a flight on the CSD:FLIGHT-
/DATE screen, but there is no address entered for this message in the address
table, at the end of the flight when the message dispatch entry is initiated, if the
system cannot find an address for the message, it sends it to the DFL address.
Example of a new address table (after table 0 is created):
CMC:XS ATL 50;DFL,8567;CCL,3344,ATLKKXS;COM,3344,ATLKPXS,CD
 Newly Created Table CX:XSATL50

CX:XS ATL50
DFL,8567 CCL,3344 CCL,ATLKKXS COM,3344 COM,ATLKPXS
COM,CD
Note: Make sure the (,) and (;) are in the correct places. The (,) comes after the
code and between addresses for the same code, and the (;) follows each group
of codes and addresses (except for the last one entered).

Station Data
Field Explanation
MODIFY ENTRY The modify entry (CMM) must be preceded by the CX display, so the system
knows which airline table to modify. For codes that are being added a plus (+)
is entered, for codes being deleted a minus (-) is entered, followed by the code
and address or addresses required.
An example entry to add more codes and addresses to a previously created
table is below:
CMM:+PSM,ATLKKXS,ATLKPXS;+BAG,CD;+EQC,CD;+ETL/S/US,PITRMUS
Note: The important thing is to enter the '+' before every code, and check the ','
and ';' are in the correct places.
To delete a code and address, enter:
CMM:-COM,ATLKPXS
Or
CMM:-ETL/S/US,PITRMUS
Note: When deleting codes, it is important that the identical information is
entered (if there are various addresses entered for one code and only one
address is being deleted, it is only necessary to enter the address being deleted
and not all of them). It is possible when modifying the table to use the '+' and '-'
in the same entry.

CMM:+PTM,ATLKHXS,ATLWOXS;-PTM,ATLKPXS;+PTM,ATLKDXS
The DFL can never be deleted from a table, however it can be modified or
changed.
The following example changes the DFL address from ATLKKXS to a PID
number 8567:

CMM:-DFL,ATLKKXS;+DFL,8567
Error Responses
DEVICE CMC was entered without specifying a DFL address.
DUP More than one DFL address was specified, or message type and
address already exists.
MSG TYPE Invalid message type code was specified.
NO DISPLAY CMM was attempted without displaying the CX.
OFFICE A CMC was attempted for a new table number before creating table 0
for the specified station.

Station Data
UNABLE DFL cannot be deleted; therefore the table cannot be deleted. Contact
SITA Customer Support.
4.4. Airport Gate Numbers (AZ:)

Use this table to enter all the gate numbers, with their different zones, at an airport, into the system. The
defined gates and zones established are then linked to the Location Travel Times table (LZ) to establish
the time required for passengers to travel from a certain check-in area to the departure gate. For airports
that have check-in counters at the departure gate, a CRT PID number must be associated with that gate,
so once a gate number is assigned to a flight, check-in can continue at that gate. Also when a specified
time before flight departure is reached, all further check-in transactions are restricted to that gate.
Note: Once an AZ table is created, a LZ table must also be created, otherwise once a GATE number
from that AZ table is entered into a flight, then any check-in entries will get the response 'LOCATION
TRAVEL TIME X'.
DISPLAY ENTRY
AZ:STATION
Response of an AZ Table not yet Created
AZ:ABZ
NO RECORD
Response of an Existing AZ Table
AZ:BHX
ZONE GATE VDT (S)
_______ _______ __________
001 1
001 2
001 3A 7382
001 3B 1390
001 4
Explanation:
Field Explanation
ZONE For small airports, it is normally enough to have one zone defined. The zone
number should be the same as entered in the CONLINK files of the CRT's
authorized to do the check-in, as once the gate number has been assigned to
a flight, only those CRT's whose zones match the gate number zone are
allowed to check-in passengers. For larger airports, different zones can
restrict passenger check-in to the correct zones.
GATE Enter gate numbers here. They can be alpha/numeric and up to four
characters.

Station Data
Field Explanation
VDT Specifies the CRT PID numbers associated with the gate. If there are no
CRTS at the gate, this can be left blank. A maximum of 21 CRT PID numbers
are allowed for gate check-in per flight for a station, and a maximum of three
gates can be allocated (via the FUI transaction) per flight for that station. If
there is only one gate entered, it is possible to have a maximum of 21 CRT
PID numbers associated with that gate. The system only allows a maximum of
seven CRT PID numbers per one gate entry via the AZC transaction, if a gate
has more than seven CRTs, the same gate number must be repeated with the
different CRT PID numbers.
Note: This can only be done using the AZC transaction and not the AZM
(modify) transaction.

AZC:BRU 001,1/2278/2280/2284/3106/3108/3110/4560,1/4564/4566 etc.
Note: The bulk re-check transaction (transferring of passengers from one
flight to another) is restricted to a gate CRT only. For those airports that do not
have any CRTS at the gate, a 'dummy' (fictitious) gate, with the check-in
control agent's CRT PID numbers, can be set-up, so that when the occasion
arises, the check-in control agent can enter the dummy gate number to carry
out the transaction. Remember that an easier solution for the bulk re-check
transaction is to take out the Zone from the 'DPID: display' of the CRT
attempting the transaction (check the Check-in Supervisor Training Manual for
more information on this).
CREATE ENTRY Use the create entry (AZC) to initially create the table. After it is created, any
additions or deletions are made by the modify entry.
The initial gate create entry without CRT PID numbers is:
AZC:STATION ZONE,GATE,GATE,GATE etc.
An example of this create entry is:
AZC:BOS 001,1,2,3
Response of Newly Created AZ Table
AZ:BOS
ZONE GATE VDT (S)
_______ _______ __________
001 1
001 2
001 3
The initial gate create entry with CRT PID numbers is:
AZC:STATION ZONE,GATE/CRT/CRT/CRT,GATE/CRT/CRT etc.
AZC:BOS 001,1/4548/4550/4552,2/6389/6391,3/8343/8345/8347

Station Data
Field Explanation
CREATE ENTRY
(Continued)
 AZ Table with Gates
AZ:BOS
ZONE GATE VDT (S)
____ ____ _______
001 1 4548/4550/4552
001 2 6389/6391
001 3 8343/8347
Note: Be careful when using the AZC transaction, if a table is already
available, and a new AZC transaction is entered, the old table is deleted and
be replaced by the latest entry.
MODIFY ENTRY The modify entry (AZM) must be preceded by the AZ display, because the
modify entry does not specify the station, and the system needs to know which
station table to modify. For gates that are being added a plus '+' is entered
followed by the zone, and gate number (plus CRT PID number if required), and
for gates being deleted a minus '-' is entered.
An example to add a new gate number to the previous create entry is:
AZM:+001,4/9420/9422/9424/9426,5/7780
 AZ Table with Gate Number Change

AZ:BOS
ZONE GATE VDT (S)
____ ____ _______
001 1 4548/4550/4552
001 2 6389/6391
001 3 8343/8347
001 4 9420/9422/9424/9426
001 5 7780
To delete a gate number, the entry is (after a previous AZ display):
AZM:-ZONE, To change a CRT PID number for a gate, you must first delete the old one and
GATE/CRT/CRT/CRT then add the new one. The add and delete entries can be in the same
transaction but must be separated by a ( ; ).
Example to change CRT PID number 9422 to 9428 for gate 4 (ZONE 001), the
entry is:
AZM:-001,4/9422;+001,4/9428
If deleting a complete gate number that has CRT PID numbers associated with
it, then the gate number plus all the CRT PID numbers must be entered in the
transaction. If there are no CRT PID numbers associated with the gate, then
when adding or deleting gates, just enter the gate numbers required.

Station Data
Error Responses
ADDRESS Invalid CRT PID number specified.
DUP Attempt made to add the same gate/zone/PID twice.
NIL Attempt made to display an empty AZ table.
NO DISPLAY AZ display required before AZM.
NO RECORD A display was attempted for a non-existent table.
UNABLE Attempt was made to delete a non-existent table.
4.5. Location Travel Times (LZ:)

This table specifies the travel times between check-in zones and departure gates. Once the specified time
is reached, check-in is restricted to the gate only.
DISPLAY ENTRY
LZ:STATION ZONE
Response of a LZ Table Not Yet Created
LZ:BOS 2
APT ZONE
Response of an Existing Table for Zone 1:
LZ:BOS 1
TRAVEL TIMES TABLE FOR BOS ZONE 1
APT ZONE MIN INC
____ _____ ____ ____
BOS 1 0 0
Explanation:
Field Explanation
ZONE If the zone entered here is:

• 0 - any CRT can be used to check-in passengers (ignoring the CRT
DPID:/CONLINK file created zone) until the gate number is entered on
a flight, then the check-in is restricted only to those whose CRT
DPID:/CONLINK file created zone matches the input gate
number/zone.
• 1 - only CRTs that have CKZN1 in their DPID:/CONLINK file can
check-in passengers, even if the gate number is entered or not
(providing the gate number is associated with Zone 1 as well).
MIN Number of minutes it takes for a passenger to get to the gate from the check-in
CRT. If there is not enough time for the passenger to get to the gate before
flight departure, the system will respond with 'LOCATION TRAVEL TIME 0',

Station Data
Field Explanation
and the passenger will either be refused for the flight or sent to the gate 'on
chance' to try and check-in there.
Note: If an airline wants to be able to check-in until STD, then 0 minutes
should be entered here. If any other time is specified, then that is the number of
minutes before departure that any further passenger check-in will be prevented
(except at a gate CRT).
INC Sometimes it may be necessary to temporarily adjust the travel time between
the check-in desk and gate because of an operational reason (perhaps delays
and congestion getting through passport control and/or security checks). The
time can be increased but never decreased except back to its original time.
This adjustment is made by the LTA transaction.
CREATE ENTRY Use this entry (LZC) to initially creating the table. After it is created, then any
additions or deletions are made by the modify entry.
The initial gate create entry is:
LZC:STATION ZONE AIRPORT,ZONE/TIME
LZC:MAN 001 MAN,1/0
LZ:MAN 1 Example Response:
TRAVEL TIMES TABLE FOR MAN ZONE 1
APT ZONE MIN INC
___ ____ ____ ____
MAN 1 0 0
Note: Be careful when using the LZC transaction, because if a table has
already been created, and a new LZC transaction is entered, the old table is
deleted and replaced by the latest entry.
MODIFY ENTRY This entry (LZM) must be preceded by the LZ display, because the modify
entry does not specify the zone, and the system needs to know which zone
table to modify.
For zone times that are being added a plus '+' is entered followed by the zone
and times, for zones and times being deleted a minus '-' is entered.
LZM:+AIRPORT,ZONE/TIME
An example to add another zone and time to the previous create entry is:
LZM:+MAN,2/30
Response of LZ Change
LZ:MAN 1
TRAVEL TIMES TABLE FOR MAN ZONE 1
APT ZONE MIN INC
____ _____ ____ ___
MAN 1 0 0
MAN 2 30 0
Note: If the table for ZONE 1 only shows 0 under ZONE, then the system will
not let you add any other zones via the LZM transaction, you must create a
new table via the LZC transaction, otherwise you will keep getting the response

Station Data
Field Explanation
'UNABLE'.
To delete a zone and time, the entry is (after a previous LZ display):
LZM:-AIRPORT,ZONE/TIME
It is possible to add and delete zones and times in the same entry.
Response:
LZM:_MAN,2/30;+MAN,2/20
THROUGH CHECK- For Airline's using 'Through Check-in', remember to set-up the LZ table
IN correctly. This table must include the downline Transit City, otherwise if a
GATE number is entered on the onward flight, check-in is inhibited with the
response 'LOCATION TRAVEL TIME X'.
For example, if a passenger is being checked-in on flight XS397 operating ATL
- JFK, and being 'through' checked-in on flight XS937 JFK - BOS, and a Gate
number (Zone 1) is entered on flight XS937 out of JFK, the LZ table of ATL
should show ATL and JFK and likewise the JFK LZ table should show JFK and
ATL:
Response of Entry LZ:ATL1
TRAVEL TIMES TABLE FOR ATL ZONE 1
APT ZONE MIN INC
___ ____ ___ ___
ATL 1 0 0
JFK 1 0 0
If these tables are set-up correctly, 'Through' check-in can proceed, whether a
Gate number is entered on either flight or not.
Error Responses
APT ZONE Attempt made to display a non-existent check-in location travel times
table.
DUP Attempt made to add an airport/zone already created.

Station Data
4.6. Static File Maintenance Display (SFM:)
This transaction allows an agent to display all the entries (by airline or city) created in the system for a
specific 'STATION DATA' file, and have it transmitted to a CRT, a printer, or a telex address.
The station files that can be obtained using the SFM transaction are:
CW - Passenger Weight Tables
PZ - Staff Priority Tables
CD - Master/Equivalent Classes
CX - Passenger Message Address Tables
AZ - Airport Gate Numbers
LZ - Location Travel Times
DR - Destination Remarks
There are various display entries that can be output depending on the information required. To display all
the entries for a specific code to the transmitting CRT, the entry is:
SFM:CODE (SFM:AZ)
Note: It is possible to enter other codes not specified above, and although the response may be
'ACCEPTED', the system will not display or print anything.
Note: This display is limited to approximately 1350 lines. Entering a transaction code without an airline
code displays all data for each airline handled. This displays in the order that the airlines were added.
When this maximum is reached the display ends with "MAXIMUM PAGES REACHED". To view any
missing data enter the desired airline code.
To display all entries for one airline for a specific code to the transmitting CRT, the entry is:
SFM:CODE AIRLINE (SFM:CW SR)
To display the entries for one airline for a specific code, and send it to a telex address:
SFM:CODE AIRLINE/ADDRESS (SFM:CW LH/ATLGCXS)
To display all the entries for a specific code and send it to a PID number (CRT or printer):
SFM:CODE/PID NUMBER (SFM:DR/758)
Error Responses
ADDRESS Numeric PID number out of range, or invalid address specified.
AIRLINE Invalid airline code entered or missing.
NO INFO Requested airline's table is empty.
NO RECORD The requested AZ/LZ tables have not been created.

Station Data
5. Seat Maps
5.1. Seat Map Creation (EQC:)
This transaction is used for creating seat maps. Unlike most initial entries, this transaction is not
transmitted until the seat map is completed. The agents should first build a basic Seat Map and then after
the EQC: is accepted return to add the special usage descriptor codes. Once the agent becomes familiar
with the transaction this suggestion will not need to be followed.
 EQC: Entry:
EQC:XS/737/A/04OCT05 Header Line
F12Y87 Configuration
JMP1 Jump-Seat
F2,2 Max Number of Aisles/Seats in F Row
1-3/ABEF Row Numbers and Seat Designators
Y3,3 Max Number of Aisles/Seats in Y Row
4-7/ABCDEF Row Numbers and Seat Designators
8/#BCDE# Row Numbers and Seat Designators
9-17/ABCDEF Row Numbers and Seat Designators
18/AB#DEF Row Numbers and Seat Designators
B/4C,4D Bassinet Seats
S/3,11-18 Smoking Rows
E/6A-C Emergency Exit Rows
W/5-11 Over Looking Wing Rows
D/9D-F Handicapped Seats
I/4B-E Infant Seats
! File and Transmit Character
 EQC Entry with an Upper Deck

EQC:2M/747/SP /04OCT05
F8C14Y319
JMP4
UF2,2
70-71/ACJK
UC2,3
72-73/ACHJK;74/A#HJK
Y3,4,3
1/A#C####H#K;2/ABC####HJ#;3-9/ABC####HJK;10-15/0;9/3X
16-17/ABC#######;18-21/ABCDEF####;22/0;21/3X
23-24/ABC#######;25-38/ABCDEFGHJK;39/ABC####HJK;40/0;39/3X
41/ABC####HJK;42-46/ABCDEFGHJK;47-63/0
64/ABCDEFGHJK;65-66/A#CDEFGH#K;67/###DEFG###
B/U70K,1A,1K,18E,25E,25K,42E-F
H/8B,17B,37B,37J
R/1A-C,2H-J
I/U70A
!
Note: The Seat Map transaction is limited to the screen size; therefore, it is advisable to start with a blank
screen.

Seat Maps
Explanation:
Field Explanation
HEADER LINE The header line consists of the:

• function code (EQC)
• airline code
• aircraft type and version code
• effective and end dates
If there is no end date specified, then the seat map is valid until either an end
date is added or the seat map is marked for deletion (see EXM).
CONFIGURATION Valid configuration of the aircraft.
NUMBER OF SEATS Indicates how many seats per class and row are fitted on each side of the aisle
IN EACH ROW (the maximum number fitted in the class should be indicated because some
rows vary from others). For aircraft there are normally two aisles fitted, so the
maximum number of each row should be specified (Y3,4,3). For narrow body
aircraft, if a (/) is added at the end of this entry (F2,2/) this inserts a space
between the left and right side of the aircraft for the screen display, making it
easier to identify (it may be added to aircraft but as this causes the middle row
to be split in two). This (/) can only be specified once, and has to be added to
the first class specified in the display (if it is applied to any other class it will
cause an error EQC(15) on transmission of the screen).
Note: It is not possible to separate the left and right sides just for one class
(unless the configuration is all one class). So if it is added, it applies to the
whole aircraft.
ROW NUMBERS Indicates the row numbers and the seat designators fitted on the aircraft. Each
AND SEAT class must be entered separately. Every row that differs from the previous row
DESIGNATORS mentioned must be entered separately. The number of seat designators per
row must match the maximum number of seats specified in the class row (F2,2
= 4). If any seat designator is missing (not fitted) then this is replaced by the
character (#').
An example: if Y class has seat designators ABCDEF fitted on the aircraft,
and one row has A and F missing, perhaps for emergency exit, then the row
number would be followed by #BCDE#. Also, if a row is missing within a class
(example some airlines do not use row 13), then this row is indicated by
following it with a 0 (example 13/0), however if the missing rows are between
classes, then these can be ignored.
It is also possible to specify a space (from one to a maximum of three)
between each row for the seat map display. This is done by indicating the
rows required followed by the number of spaces and an X (example if one
space is required between rows 4 to 18, then the entry is 4-18/1X).

Seat Maps
Field Explanation
ROW NUMBERS
AND SEAT
 EQC Row Spacing Indicator
DESIGNATORS F12Y60
(Cont) F3,3
1-2/ABCDEF
1-2/2X
Y3,3
3-12ABCDEF
3-12/2X
SEAT CODES Various seat codes, known as SUD (special usage descriptor codes) can be
specified on the seat map display. There are two types of codes that can be
entered. Row codes (indicates the row but not the actual seat on the seat map
display) and Seat codes (indicates the actual seat on the seat map display).
Row Codes: Seat Codes:
Q - Quiet row K - Stretcher Seats
S - Smoking row D - Handicapped Seat (WCHR, Deaf, Blind)
W - Overlooking wing row B - Bassinet seat
E - Emergency Exit Seats
I - Infant row
C - Last to be used seat
H - Bulk-head seats
L - Extra leg room seat
N - No movie viewing seat
R - Restricted recline seat (/)
U - Unaccompanied minor seat
X - Blocked seat
Note: Designator Codes D, I, U, B, K cannot be assigned to seats having an
'E' (Emergency Exit Seat) Designator. Also, any passengers having the
following SSR codes of BSCT, BLND, DEAF, UMNR, WCHR, WCHS, WCHC,
INF, and MUS or the gender CHD, are restricted from having an E seat.
Note: 'K' (Stretcher Seats) is visible on a seat map (SE), only when a stretcher
passenger is indicated on a PNL/ADL and seats have been entered on the
EQC entry.

Seat Maps
Field Explanation
SEAT CODES The system accepts any of the following row or seat entries:
(Cont) 7A - One seat
7 - A whole row
L7 - The left side of one row
R7 - The right side of one row
7A-C - Seats ABC of one row
7-10 - Rows 7,8,9, and 10
7-10A - Seat A only of rows 7,8,9, and 10
7-10A-C - Seats ABC of rows 7,8,9, and 10
L7-10 - The left side of rows 7,8,9, and 10
R7-10 - The right side of rows 7,8,9, and 10
AIRCRAFT LIMITS The following limits can be applied so that check-in agents will get a warning at
check-in if they are reached:
I - Infants (followed by class and maximum number). Example: IY12 (if
class not specified then defaults to entire aircraft). The system default is
eight infants per compartment, ten per aircraft.
K - Pets in cabin (followed by class and maximum number). Example:
KF2 (if class is not specified then defaults to aircraft capacity).
L - Passenger numeric limit (followed by class and maximum number).
Example: LY80 (if class not specified then defaults to aircraft capacity).
W - Check-in weight limit. Example: W1000 (warning will be activated
when the check-in weight is 1000 below the maximum check-in weight
allowed).
JMP - Maximum number of jump seats allowed. Example: JMP4 (cannot
be restricted by class but must be for the entire aircraft).

Seat Maps
Field Explanation
FILE AND Once all the data is input, the '!' character is entered at the bottom of the
TRANSMIT display and the screen is transmitted. If there are no errors, the seat map gets
filed into the system.
 EQC Accepted Response

EQC:XS/737/A/22JUN06
ED:XS
1.737/A F12Y87 22JUN06-OPEN
However if there is an error, the system indicates where it detects an error,

with an error code (example ROW) and number (24), at the same time it
erases from the screen, everything that was correct to that point. To get the
whole display back on the screen, enter one of the paging functions (PN or PB)
and then you can make the required correction.
 EQC: with Error Returned

16/AB#DEF
^ ^ERR ROW(24)
B/4C,4D
S/3,11-18
E/6
W/5-11
!
When the whole screen is re-displayed, the error code is still displayed at the
place it detected the error, there is no need to delete this line, just make the
correction and re-transmit the screen. The system continues displaying error
responses until they are all corrected.
NO-SEAT MAP If the database is created for an aircraft type that has no seat plan details
DETAILS available, the system still requires a blank seat map to be built. The only
AVAILABLE details required to do this are the aircraft type and version and the
configuration.
Note: It is very important when a schedule (BF:T) is built using a NS seat
map, that the CSM be changed from SS to NS, otherwise it causes a system
error when the PNL attempts to load onto the flight.
 EQC - No Seat Map Details (Blank Seat Map)

EQC:XS/737/E/24JUL06
F8Y92
!
 EQC - No Seating (NS) Response to Blank Seat Map

EQC:XS/737/E/24JUL06
ED:XS
1.737/E F8Y92 NS 24JUL06-OPEN

Seat Maps
The EQC has an option to specify up to 10 zones on the seat map. Zones defined in the seat map are
used in the COM message when a flight is not linked to SITA LDP. For linked flights, zone information
used is taken from SITA LDP that appears in the weight and balance update.
EQC entry with Zones.
Entry:
EQC:MA/737/400a/09oct08

EQC:MA/737/400A/09OCT08
J12Y132
JMP1
ZON/6
ZNF/0A/1-3/0B/4-12/0C/14-17/0D/18-22/0E/23-25
ZNL/0F/26-28
J2,2
1-3/ABEF
Y3,3
4-7/ABCDEF
8/#BCDE#
9-12/ABCDEF
13/0
14-18/ABCDEF
19-28/AB#DEF
B/4C,4D
S/3,11-12
E/6A-C
W/5-11
D/9D-F
I/4B-E
!
Explanation:
Code Explanation
ZONES The Master seat map is enhanced to accommodate 10 zones.
ZON/6 (Optional) specifies the number of zones on the aircraft.
ZNF (mandatory if ZON is 1 or more) depicts the first five zones with the seat rows in each Zone
ZNL (Optional) required if number of zones is greater than five) the rest of the zones in excess of
five with the seat rows Specified.

Seat Maps
5.2. Seat Map Creation Error Codes
There are eight error type codes with their own numbers that may be seen when trying to file a new seat
map with errors on it. These are CMP (compartment), EQC (aircraft description), IMP (basic error), LIM
(limit), ROW (row), SET (seat), SUD (special usage descriptor), and MPT (moving partition). The following
tables list the errors and provide an explanation.
CMP
Code Explanation
CMP(02) The compartment or configuration is in error.
CMP(03) The compartment or configuration exceeds the maximum allowed.
CMP(06). The compartment is already described.
CMP(09) The compartment being described is not mentioned in the aircraft configuration.
CMP(12) The across row seating exceeds the maximum of 11 seats.
CMP(15) The number of aisles exceeds the maximum of four.
CMP(21) A compartment is described without any aisles.
CMP(24) An upper compartment is described without a lower.
CMP(27) The compartment configuration does not equal total seats described by a compartment's
row/seats descriptors.
CMP(30) The first and last row in a compartment must be present.
CMP(33) There must be at least one seat described on the left and right of an aisle and between
aisles of an aircraft.
EQC
Code Explanation
EQC(03) Aircraft identification is in error.
EQC(09) The date is in error.
EQC(12) The second date of the date range is in error.
EQC(15) Descriptor delimiter error. Either a / or ; or a new line is in error or required.
EQC(18) Descriptor cannot be identified or compartment not specified with descriptor or a (;) is
placed at the end of a line.
EQC(22) Maximum KM record size exceeded (contact DCS Support).
EQC(24) An alphabetic character has been entered where a numeric is required.

Seat Maps
EQC(30) The date range input overlaps the date range of an identical aircraft already created.
EQC(33) The 'file' (!) character has been entered but some data is missing.
IMP
Code Explanation
IMP(01) An error occurred performing an internal date string move.
IMP(03) A primitive error occurred; for example, compartment size or free form text.
IMP(06) A numeric was entered where an alphabetic was expected.
IMP(09) A character was entered which is not alphanumeric.
IMP(12) An alpha character was entered where a numeric was expected.
IMP(15) An invalid 'limit' descriptor was entered.
IMP(18) Invalid upper compartment letter specified.
IMP(24) Invalid SUD character entered.
LIM
Code Explanation
LIM(03) All specified 'limits' must precede compartment descriptors.
LIM(06) The 'limit' entered has already been specified.
LIM(12) Invalid 'limit' descriptor.
LIM(15) The compartment 'limit' entered is greater than the compartment maximum.
LIM(18) The 'limit' compartment entered is not in the configuration.
LIM(21) Invalid format of 'limit' entered.

Seat Maps
MPT
Code Explanation
MPT(01) More than two adjustable compartments.
MPT(02) The configuration range exceeds the maximum allowed.
MPT(03) The adjustable compartment minimum/maximum separator is in error.
MPT(04) The adjustable compartments do not follow each other on the input.
MPT(05) The minimum of one compartment plus the maximum of the other compartment does not
equal the total configuration.
MPT(06) A specific row was not input for the partition row.
MPT(07) Forward buffer rows exceeded or invalid input.
MPT(08) Aft buffer rows exceeded or invalid input.
MPT(10) A new compartment was described before the partition placement was input on the first
adjustable compartment.
MPT(12) Minimum configuration is not on a row border.
MPT(13) The configuration is not on a row border.
MPT(14) The initial partition placement does not match the stated configuration.
MPT(15) The maximum configuration exceeds the last row of the compartment.
MPT(18) An upper compartment was specified in an adjustable compartment.
MPT(19) The first 'moving partition' forward buffer compartment row is before the first row in the
compartment.
MPT(20) The last 'moving partition' aft buffer compartment row is after the last row in the
compartment.
MPT(21) The seats across are not equal in the two adjustable compartments.
MPT(22) The number of aisles is not the same in both adjustable compartments.
MPT(23) The aisle placements are not the same as both adjustable compartments.

Seat Maps
ROW
Code Explanation
ROW(03) A row/seat descriptor must be preceded by a descriptor for the compartment where the
row resides.
ROW(06) Invalid row entry.
ROW(12) Row or rows in the descriptor are already described in another compartment.
ROW(15) The character should be a '-' to separate rows, or a '/' between rows and seats.
ROW(18) The 'skipped' row spaces are not in the range 1 to 3.
ROW(21) The 'skipped' row entered has not been defined in the rows previously specified.
ROW(24) A row is out of sequence within a compartment or is a duplicate.
ROW(27) Less than a full row has been described where a full row is required for the SUD entered.
ROW(30) Less than a half row has been described where a half row is required for the SUD
entered.
ROW(36) The row or rows described exceed the number of rows in the compartment.
ROW(39) The rows associated with the SUD are not previously described.
ROW(42) All the compartments of the aircraft are not described.
ROW(45) No rows/seats are described in the previous compartment.
ROW(48) Spacing after an absent row is not allowed.

Seat Maps
SET
Code Explanation
SET(03) A numeric seat was specified instead of an alpha.
SET(06) An alpha seat was specified instead of a numeric.
SET(09) The numeric seats described on the 'R' side of the aircraft exceed the range to five.
SET(12) The numeric seats described on the 'L' side of the aircraft exceed the range one to six.
SET(18) Seat identifiers are not alphanumeric, or the '#' character, or they are less than specified
In the aisle descriptor.
SET(21) A seat identifier is out of sequence or duplicated.
SET(24) Seat identifiers in this row differ from the first row specified in this compartment.
SET(27) Too many seats are described for the row or rows.
SET(30) The seat area is invalid.
SET(33) The seat described does not exist in the row described for the SUD.
SET(36) The seat does not exist in the sequence of rows described for the SUD.
SET(39) There are no seats in the row or rows described for the SUD.
SUD
Code Explanation
SUD(01) A (-) is encountered before a (/) or (;).
SUD(03) The alpha character is not a valid SUD.
SUD(06) Seats associated with a SUD are not described for the compartment.
SUD(09) The SUD causes a conflict with another SUD, or is duplicated for the row.
SUD(12) The SUD causes a conflict with another SUD, or is duplicated for one or more seats in
the row.
ZON
Code Explanation
ZON(01) Format ('/' Missing in ZON/ZNF/ZNL)
ZON(03) Format (Zone # > maximum allowed)
ZON(04) Duplicate (ZON or ZNF or ZNL)

Seat Maps
Code Explanation
ZON(05) ZON Missing (Enter first ZON line)
ZON(06) ZNF Missing (Enter first ZNF line)
ZON(08) Not NUMERIC
ZON(09) Zone name error (0A)
ZON(10) Zone name duplicated
ZON(11) ZNL Not Needed
ZON(12) Error reading Zone name in ZNF
ZON(14) Error reading Start row in ZNF
ZON(15) Error reading Zone name in ZNL
ZON(16) Error reading Start row in ZNL
ZON(17) Start Row > End Row
ZON(18) Start Row < Previous Zone End Row
ZON(19) ZON>ZNF (Need more zone description)
ZON(20) ZNF>ZON (Too many zone descriptions)
ZON(21) ZON>ZNL (Need more zone description)
ZON(22) ZON>ZNL (Too many zone descriptions)
ZON(77) CU update error (System error – report to PSS-Helpdesk)
Note: Only the zone code is returned on the screen.

Seat Maps
Error Responses
AIRCRAFT Invalid aircraft type specified.
AIRLINE Invalid airline code specified.
CLASS-GROUP SPECIFICATION Compartment class must match master class shown in CD

REQUIRED table.
DATE Invalid date entered.
FORMAT Incorrect or missing 'file' (!) character.
SIZE Update exceeds allowable equipment size.
5.3. List of Seat Maps (ED:)

This display lists all the aircraft types and versions created with seat maps in the system along with their
effective and end dates of operation.
The entry is:
ED:AIRLINE
Response (ED:XS):
ED:XS
1.737/A F12Y87 22JUN04-OPEN
2.737/B C20M77 24JUL06-01SEP06
3.737/C F8Y88 DELETED
4.767/A F12C63Y126 01FEB04-OPEN
5.DC9/A F14Y93 NS 22APR04-OPEN
The seat maps which display DELETED (see Delete/Amend Seat Map Date Ranges (EXM:)) instead of a
date, are removed by the system during the 'nightly computer run' (this is activated every night) where the
system clears out all unwanted records and carries out other functions. Those seats maps with an END
date are also removed by the 'nightly computer run' when that date is reached.
It is also possible to display a list by aircraft type. The entry is:
ED:AIRLINE/AIRCRAFT TYPE
Response (ED:XS/737):
ED:XS
1.737/A F12Y87 22JUN04-OPEN
2.737/B C20M77 24JUL06-01SEP06

Seat Maps
5.4. Seat Map Display (SEM: / SEI:)
After a seat map is created it can be displayed on the screen to check that everything is correct. There
are two ways to do this.
 SEM Transaction
 SEI Transaction
5.4.1 By Using the SEM Transaction
The entry is:
SEM:AIRLINE/AIRCRAFT TYPE/VERSION
SEM:AIRLINE/AIRCRAFT TYPE/VERSION/CLASS,SUD (SEM:737/A/Y,S)
Entry (SEM:XS/737/D) and Response:
SEM:XS/737/D/22JUL04-OPEN F12Y92
F Y [ [ [ [ 1 [ [
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8
RF * * F F * * * * * * * * * * * * * * * FR
RE * * E E * * * * * * * * * * * * * * * / ER
RD * * D D * * * * * * * * * * * * * * * / DR
R = S = = = = E E = = = = S S S S S S R
L S S = = = = E E = = = = S S S S S S L
LC * * C C * * * * * * * * * * * * * * * / CL
LB * * B B * * * * * * * * * * * * * * * / BL
LA * * A A * * * * * * * * * * * * * * * AL
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8
F Y [ [ [ [ 1 [ [
5.4.2 By Using the SEI Transaction

This entry can only be used following an ED entry (ED:AIRLINE/AIRCRAFT TYPE). After the ED entry, a
numbered list is displayed and the required seat map is selected using the SEI transaction. The entry is:
SEI:NUMBER
The response is the same as for the SEM transaction.
Error Responses
COMPARTMENT Invalid version specified.
DATE Seat map is marked for 'DELETION' or the effective end date has passed.
ENTRY NBR Invalid SEI number or does not exist.
NO DISPLAY ED screen was not displayed prior to the EQI entry.

Seat Maps
5.5. Amend Seat Map (EQ: / EQI:)
After a seat map is created, it can be modified as required. There are two ways this can be done:
 EQ Transaction
 EQI Transaction
5.5.1 By Using the EQ Transaction

The entry is:
EQ:
EQ:AIRLINE/AIRCRAFT TYPE/VERSION
Entry (EQ:XS/737/A) and Response:
F12Y87
F2,2
1-3/ABEF
Y3,3
4-7/ABCDEF
8/#BCDE#
9-17/ABCDEF
18/AB#DEF
B/4C,4D
S/3,11-18
E/6
W/5-11
!
The system responds with the last EQC entry made, and any modifications are inserted. The date does
not need to be amended, but it is important to transmit the screen after the '!' character. If there are
any errors, the system responds with an error code and number.
5.5.2 By Using the EQI Transaction

This entry can only be used following an ED entry (ED:AIRLINE/AIRCRAFT TYPE). After the ED entry, a
numbered list is displayed and the required seat map is selected using the EQI transaction. The entry is:
EQI:NUMBER
The response is the same as for the EQ transaction.

Seat Maps
5.6. Delete/Amend Seat Map Date Ranges (EXM:)
A seat map can be cancelled from the system by deleting the date. This removes the seat map from the
system during the 'nightly computer run' (this is activated every night) when the system clears out all
unwanted records. It is also possible to amend the date range of a seat map.
The EXM transaction can only be used following an ED entry (ED:AIRLINE/AIRCRAFT TYPE). After the
ED entry, a numbered list is displayed and the required seat map is selected.
5.6.1 Delete Seat Map
The entry to delete a seat map is:
EXM:NUMBER D DATES
 To Delete Entry 3 from the Following ED Display

ED:XS
1.737/A F12Y87 22JUN04-OPEN
2.737/B C20M77 24JUL06-01SEP06
3.737/C F8Y88 01NOV04-OPEN
►EXM:3 D 01NOV04
Response of EXM Delete Transaction
ED:XS
1.737/A F12Y87 22JUN04-OPEN
2.737/B C20M77 24JUL06-01SEP06
Note: If the date is OPEN ended, then only the effective date need be entered. If there is an effective
and end date, then both dates must be entered.

EXM:2 D 24JUL06-01SEP06
5.6.2 Amend Seat Map Dates

The entry to amend the dates of a seat map is:
EXM:NUMBER R DATES
 To Amend Entry 3 from the following ED Display:

ED:XS
1.737/A F12Y87 22JUN04-OPEN
2.737/B C20M77 24JUL06-01SEP06
3.737/C F8Y88 01NOV-OPEN
►EXM:3 R 24JUL06-01SEP06
Note: If the effective start date has already passed, then either today's date or a date in the future has to
be inserted, otherwise the response will be 'DATE'.

Seat Maps
Response of EXM:
ED:XS
1.737/A F12Y87 22JUN04-OPEN
2.737/B C20M77 24JUL06-01SEP06
3.737/C F8Y88 24JUL06-01SEP06
 To make the end date of a seat map 'OPEN':

EXM:2 R 24JUL04
Response of ED and Seat Map Displays

ED:XS
1.737/A F12Y87 22JUN04-OPEN
2.737/B C20M77 24JUL06-OPEN
3.737/C F8Y88 24JUL06-01SEP06
5.6.3 Re-instating a Seat Map

If a seat map is marked for DELETION, and needs to be re-instated, the following procedure needs to be
carried out:
1. Display the ED list:
ED:XS
1.737/A F12Y87 DELETED
2.737/B C20M77 24JUL06-OPEN
2. Enter the EQI transaction (EQI:1), the response is:

(THIS ENTRY HAS BEEN MARKED FOR DELETION)
F12Y87
F2,2
1-3/ABEF
Y3,3
4-7/ABCDEF
8/#BCDE#
9-17/ABCDEF
18/AB#DEF
B/4C,4D
S/3,11-18
E/6
W/5-11
!
By deleting the second line that contains the message '(THIS ENTRY HAS BEEN MARKED FOR
DELETION)', and then re-transmitting the screen after the (!) character, the seat map is re-initialized in the
system.

Seat Maps
Response:
ED:XS
1.737/A F12Y87 22JUN04-OPEN
Error Responses
DATE The date ranges specified are invalid or overlap.
ENTRY NBR Invalid EXM number or does not exist.
FORMAT The EXM number is not numeric, or the action code is not R or
D, or the entry contains an error.
NIL There are no a/c descriptions for the input request.
NO DISPLAY ED was not displayed prior to the EXM entry.
NUMBER An output line number conversion error occurred.
SIZE The specified EXM exceeds allowable record size.
UNABLE The EXM is attempting to replace a deleted record.

Seat Maps
5.7. Movable Partitions (MP)
It is possible to create a master seat map that has movable partitions. This is particularly useful for those
airlines that have many different configurations for one aircraft type, and the actual flight operating-
configuration for the day is not known till after check-in has started. The EQC transaction is used with the
following variations:
1. The configuration line must contain the master configuration, plus the minimum and maximum
configurations.
Example for a master configuration of C12M131, the configuration can be anything from C0M143 to
C77M66. The configuration line should be entered as:
C12/0-77M131/66-143
It is important that the minimum configuration of one class (C0 or M66), and the maximum
configuration of the other class (C77 or M143) must equal the total seats (143) on the aircraft.
2. When specifying the row numbers for the first class, the last row number specified must be for the
maximum configuration for the class and not for the master configuration.
Example for a master configuration of C12M131, although the master C class configuration is 12
(which is rows 1 to 2), the maximum configuration can be C77 (which is rows 1 to 13), therefore the
rows specified for C class must include the last row that the C77 (row 13) configuration would use.
The second class need only specify the remaining rows.
3. The row where the master configuration ends and the movable partition begins must be specified. It is
also possible to enter buffer zones on either side of this row (the maximum number of buffer zones is
limited to the maximum number of rows allowed for that class). Buffer zones are created as C on the
seat map, so that on flight creation, this prevents passengers from checking into these seats, so when
a late configuration change is performed, it saves having to re-seat passengers who due to the
change might have been seated in the wrong class area.
Example for master configuration of C12M131, the movable partition would start from row 2, and if
one buffer zone is required in front of row 2 (maximum would be 2 in this case) and four buffer zones
after row 2 (maximum would be 11 in this case as row 13 is the furthest row that C class can go), the
entry would be:
2/1P4
EQC Entry:
EQC:XS/TU5/A/01MAY04
C12/0-77M131/66-143
C3,3
1-2/ABCDEF
3/ABCDE#
4-13/ABCDEF
2/1P4 MOVABLE ROW / REQUIRED BUFFER ROWS
M3,3
14-22/ABCDEF
23/#BCDE#
24-25/AB##EF
!

Seat Maps
Response to SEM:XS/TU5/A Entry:
SEM:XS/TU5/A/01MAY04_OPEN C12M131
C M 1 2
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
RF * C F F C C C * * * * * * * * * * * * * * * * * * FR
RE * C E E C C C C C * * * * * * * * * * * * * * * * * * ER
RD * C D D C C C C * * * * * * * * * * * * * * * * * DR
R = = = = = = = = = = = = = = = = = = = = = = = = = R
L = = = = = = = = = = = = = = = = = = = = = = = = = L
LC * C C C C C C C * * * * * * * * * * * * * * * * * CL
LB * C B B C C C C * * * * * * * * * * * * * * * * * * * BL
LA * C A A C C C C * * * * * * * * * * * * * * * * * AL
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
C M 1 2
Note: The above example is a basic seat map outline. Use normal procedures for SMOKING seats, plus
any other required seat codes.
5.8. Split Compartments (F Y C Y)

It is possible to build a seat map that has split compartments. This is where for example one class has
another class in the middle. The EQC transaction is used with the following variations:
1. The configuration line must contain the first row of the middle class (-R), and the last row of the first
compartment of the split class (+R).
Example of a master configuration of F12C63Y126, which is configured on the aircraft as
F12Y21C63Y105, the configuration line is entered as:
F12C63-R8Y126+R6
2. The rows within the split class that actually belong to the middle class must be defined (as 0) for row
continuity.
Example if the split class rows go from 4 to 6 and 17 to 31, and the middle class rows go from 8 to 16,
then the split class must define rows 7 to 16 as 0 (7-16/0).
Note: Upper deck seating is not considered as split compartment seating.
EQC Entry:
EQC:XS/767/C/01AUG04
F12C63-R8Y126+R6
F2,2,2
1-2/ABDEFG
C2,3,2
8-16/ABCDEFG
Y2,3,2
4-6/ABCDEFG
7-16/0 ROWS IN SEQUENCE NOT USED ENTER AS 0 (ZERO)
17-31/ABCDEFG
!

Seat Maps
Response to SEM:XS/767/C Entry:
SEM:XS/767/C/01AUG04-OPEN F12C63Y126
F Y C 1 Y1 2 3
1 2 4 5 6 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
RG * * G G * * * G G * * * * * * * * * G G * * * * * * * * * * * * * * * GR
RF * * F F * * * F F * * * * * * * * * F F * * * * * * * * * * * * * * * FR
R = = = = = = = = = = = = = = = = = = = = = = = = = = = = = R
R = = = = = = = = = = = = = = = = = = = = = = = = = = = = = R
RE * * E E * * * E E * * * * * * * * * E E * * * * * * * * * * * * * * * ER
LD * * D D * * * D D * * * * * * * * * D D * * * * * * * * * * * * * * * DL
L = = C * * * C C * * * * * * * * * C C * * * * * * * * * * * * * * * CL
L = = = = = = = = = = = = = = = = = = = = = = = = = = = = = L
LB * * B = = = = = = = = = = = = = = = = = = = = = = = = = = = L
LA * * A B * * * B B * * * * * * * * * B B * * * * * * * * * * * * * * * BL
L A * * * A A * * * * * * * * * A A * * * * * * * * * * * * * * * AL
1 2 4 5 6 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
F Y C 1 Y1 2 3
Note: The example is a basic seat map outline. Use normal procedures to include Infant seats and other
required seat codes.
5.8.1 Two Class Seat Maps (Split Compartments)

For two class seat maps, where the first class comes between the second class, the EQC transaction is
entered in the normal way, with the normal configuration of first class specified first, and then the second
class (F12Y87). The row numbers and seat designators are then entered in the normal way. Remember
when specifying the second-class row numbers to include the rows used in first class as 0 to keep the row
continuity. The same procedure can be applied for seat maps where the first class comes after the
second (not in the middle) class.
In both cases the seat map display is in class order and not in seat row number order. Therefore the
display is the first class first followed by the second class.
Entry of First Class Being Between the Second Class:
EQC:XS/737/P/01NOV04
F12Y90
F2,2
4-6/ABEF
4-6/1X1 1 SPACE IS REQUIRED BETWEEN ROWS 4 TO 6
Y3,3
1-3/ABCDEF
1-3/1X 1 SPACE IS REQUIRED BETWEEN ROWS 1 TO 3
4-6/0
3/2X 2 SPACES ARE REQUIRED AFTER ROW 3
7-18/ABCDEF
7-18/1X 1 SPACE IS REQUIRED BETWEEN ROWS 7 TO 18
!
Note: By using the entry 3/1X, this will put a space between the split Y class compartment (rows 3 and 7),
making it easier for the check-in agents to identify where the split compartments are.

Seat Maps
Response to SEM:XS/737/P Entry:
SEM:XS/737/P/01NOV04-OPEN F12Y90
F Y 1
4 5 6 1 2 3 7 8 9 0 1 2 3 4 5 6 7 8
RF * * * F F * * * * * * * * * * * * * * * FR
RE * * * E E * * * * * * * * * * * * * * * ER
RD * * * D D * * * * * * * * * * * * * * * DR
R = = = = = = = = = = = = = = = = = =
L = = = = = = = = = = = = = = = = = = L
LC * * * C C * * * * * * * * * * * * * * * CL
LB * * * B B * * * * * * * * * * * * * * * BL
LA * *..* A A * * * * * * * * * * * * * * * AL
4 5 6 1 2 3 7 8 9 0 1 2 3 4 5 6 7 8
F Y 1
5.8.2 Two Class Seat Maps (First Class Behind Second Class)
This entry is very similar to the split compartment, except in this case there is no need to specify the first
class rows as 0 in the second-class entry as these rows are not in the second-class sequence.
Entry of First Class Being Behind the Second Class:
EQC:XS/737/G/20SEP04
F12Y90
Y3,3
1-15/ABCDEF;1-15/1X 1 SPACE IS REQUIRED BETWEEN ROWS 1 TO 15
F2,2
17-19/ABCD;17-19/1X, 1 SPACE IS REQUIRED BETWEEN ROWS 17 TO 19
!
Response to SEM:XS/737/P Entry:
SEM:XS/737/G/01NOV04-OPEN F12Y90
Y 1 F 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 7 8 9
RF * * * * * * * * * * * * * * * * FR R
RE * * * * * * * * * * * * * * * * ER D * * * ER
RD * * * * * * * * * * * * * * * * DR C * * * DR
R = = = = = = = = = = = = = = = = R = = = R
L = = = = = = = = = = = = = = = = L = = = L
LC * * * * * * * * * * * * * * * * CL B * * * CL
LB * * * * * * * * * * * * * * * * BL A * * * BL
LA * * * * * * * * * * * * * * * * AL L
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 7 8 9
Y 1 F 1

Seat Maps
6. Flight Schedules Entries (FDC)
6.1. Flight Schedule Build / Display (BF:T/)
This transaction creates flight schedules that link the check-in and load planning applications together.
The display includes the dates and days of operation, the CND table number required, the routing, and the
departure and arrival times.
6.1.1 Build Flight Schedule
The entry to create a new schedule is:
BF:T/FLIGHT NUMBER/1/START DATE/END DATE/FREQUENCY
Note: The number 1 after the flight number denotes the number of aircraft types used in the routing.
Therefore if there are two different aircraft types used on a multi-sector routing, then enter a 2 (this inserts
two T1 lines on the display, so that two different CND table numbers can be inserted).
BF:T/ Response
►BF:T/XS105/1/18APR06/11OCT06/D
T1ALG EQT VERS APPL CONFIGURATION
T1
T2ALG APT ARR DC DEP DC BRD DC CSH1 CSH2 CSH3 CSH4 CSH5 CSH6 CSH7 CSH8 CSH9 T
T2
T2
T2
T2
T2
T2
T2
T2
BF:T/ Entry
►BF:T/XS105/1/18APR06/11OCT06/D
T1 1 KL 13
T2 1 ATL 1900 19 33
T2 2 MIA 2100
!A

Flight Schedules Entries (FDC)
Explanation:
Field Explanation
DATES/FREQUENCY It is not necessary to specify the year when entering the dates, (unless the
date is more than one year ahead), as the system defaults to the correct year
within the current year range. If a date is effective all year round, it is possible
just to create an effective date without specifying an end date.
This schedule then remains active until an end date is added. The frequency
applies to the days of the week the flight operates.
There are various ways of specifying the frequency, including:
D - Daily (everyday of the week)
1 - Monday (2 = Tuesday, 3 = Wednesday, 4 = Thursday, 5 = Friday,
6 = Saturday, 7 = Sunday)
X1 - Operates everyday except Monday.
It is also possible to enter more that one date range and frequency in the same
schedule.

BF:T/XS741/1/01APR06/31AUG06/D/01SEP06/31MAR98/2467
T1 The T1 line gives the flight operational requirements of which applications are
required and the CND table number used.
ALG The A stands for Amendment indicator, and LG stands for flight leg. The
amendment indicators for the T1 line are:
X - Cancel this flight for the dates shown on the header line.
A - Add new information to this line.
D - Delete information from this line.
C - Change information on this line.
The LG number is always entered as 1, even if it is a multi-sector flight, as long
as the same aircraft operates the whole routing. If there is a change of aircraft
on route, then the leg number where the aircraft change occurs is inserted
here (there would be two T1 lines in this case, the first line would be for leg 1,
and the second line for the leg where the a/c change occurs). If the wrong
amendment indicator is input, the system responds with an error message. If
the wrong LG number is input the system responds with an error message.
EQT / VERS These areas are for schedules built in the SITA Reservation System
(Equipment / Version). Schedules built in the DCS application will not use
them.

Field Explanation
APPL This stands for Application, check-in (CKI) and load planning (LDP). Flights
may be built with either or both applications. The codes are:
K - Check-in (automatic initialization after PNL received)
D - Check-in (manual (deferred) initialization after PNL received)
L - Load planning
Note: Use DFD instead of the BFT transaction to re-initialize a single day
flight.
The difference between K and D is:
1. Flights built with 'K' option initialize for check-in when the PNL arrives.
Note: If flights built with 'K' option are canceled using the DFL/NPRO
transaction (DFL:FLIGHT/DATE/NPRO), they can only be re-initialized by re-
displaying the BF:T schedule and re-filing, and re-activating (or
DFD:FLIGHT/DATE).
2. Flights with 'D' option have to be manually initialized by entering the 'IF'
transaction (IF:FLIGHT/DATE) after the PNL has arrived.
Note: If flights built with 'D' option are canceled using the DFL/NPRO
transaction (DFL:FLIGHT/DATE/NPRO), they can easily be re-initialized by
just entering the 'IF' transaction (IF:FLIGHT/DATE) again.
Although check-in has two codes, they can never be entered together,
otherwise you will get an error response.
CONFIGURATION CND configuration number. The system will only accept a valid number. If the
incorrect number or the actual configuration is entered the system will respond
with an error message.
T2 The T2 line gives the flight routing details, along with the departure and arrival
times.
ALG The A stands for Amendment indicator and the LG stands for flight leg. The
various amendment indicators for the T2 line are:
X - Cancel this station.
C - Change the station departure/arrival time.
Note: When the C is used here, it must also be inserted in the T1 line
otherwise the system responds with an error message.
APT Airport code (not city code) is entered here.

ARR DC/DEP DC Departure and arrival times are entered here (in local time). If there is any day
change (DC) in the arrival or next departure time, then this is specified by a ' +'
or ' -' and the number of days (+1 or -1) change from the first departure time.
BRD DC Boarding time (plus any day change) that is printed on the passenger boarding
card. If this item is left blank, the system prints the boarding time of 30
minutes before the departure. If a different boarding time is wanted, then the
required time is entered here.
CSH Entry is for the code share table number. Code share allows up to nine
marketing partners per flight.

Field Explanation
T Not used for DCS. It refers to a 'turn around' indicator and applies to a future
linked Reservation system, where the system will do certain checks against
the city pairs entered.
Note: It is possible to create Round Robin routings (routings that start and
end with the same station) in DCS for both CKI and LDP flights.
!A If the A is not added the schedule is only changed pending potential further
input. When a staged flight is reviewed, the agent number of the last agent
who worked with the schedule appears in the upper right corner. When the
schedule is ready to be activated the BPR/ACT transaction can be used or the
schedule can be re-displayed and activated by using the !A transaction.
Error Messages
Check airport/city pair.
Check arrival day change.
Check effective date.
Check end date.
Check flight identification.
Check arrival time.
Check departure time.
Check frequency.
Check CND table number.
Check departure day change.
Check number of stops.
Check input code.
Invalid leg number (T1 or T2).
Check application.
Check boarding time.
Check boarding day change.
Invalid amendment indicator (T1 or T2).
Airport missing (T2) must be canceled, not omitted, or Due to day change value, flight operates out of the
same airport twice on the same day.
Flight operates out of the same airport twice on 1 day.
Codeshare – No Table/Flight match.

6.1.2 Display Flight Schedules
To display flight schedules, the entry is:
BF:T/FLIGHT/DATE
Whenever a schedule is displayed on the screen, it must either be filed (!) or ignored (IG), otherwise the
system responds with 'SKED CHANGE PENDING', when another Agent attempts to access this schedule.
The file (!) entry is done from the bottom of the display, however the ignore (IG) entry can either be done
from the same place or it can be entered after the flight number (BF:T/FLIGHT/IG).
 Flight Schedule Display with the Ignore (IG) Entry at the Bottom
BF:T/XS105/1/18APR06/11OCT06/D
T1 1 KL 13
T2 1 ATL 1900
T2 2 MIA 2100
IG
The response to an IG entry is an SOE (►) on the next line. There is no further action required, and the
screen can be cleared and the next transaction input.
Display by date displays the flight period.
6.2. Amend Flight Schedule

After a schedule has been built it can be amended, either before activation (BP:R/ACT/FLIGHT) or after.
The various things that can be amended are:
 Date
 Application or Configuration
 Routing
 Departure or Arrival Time
 Cancellation of Schedule
 Copy Schedule

6.2.1 Date Change
When amending the date, display the schedule flight number required (example BF:T/FLIGHT/DATE), and
insert the new required dates. Be sure to insert the correct frequency.
Example, for a schedule that operated on a Tuesday and Thursday for the month of July, and will operate
on those days, plus every Friday, during the month of August,
The initial entry is:
BF:T/XS388/04JUL
 BF:T/ Response with !A

BF:T/XS105/1/03JUL04/31JUL06/02AUG06/31AUG06/245
T1 1 KL 13
T2 1 ATL 1900
T2 2 MIA 2100
!A
Enter the Following for the Date Change on BF:T/

BF:T/XS105/1/03JUL06/31JUL06/02AUG06/31AUG06/245
T1 1 KL 13
T2 1 ATL 1900
T2 2 MIA 2100
!A
Transmit the screen to activate the schedule.
6.2.2 Application or Configuration Change

If an application or CND table has to be changed; display the required schedule, enter a C under A on the
T1 line and make the required change by replacing the old data with the new.
 To Change the Check-In Application from D to K

T1C1 KL 13
T2 1 ATL 1900
T2 2 MIA 2100
!A

6.2.3 Routing Change
If you want to delete a station and add a new one, use the X under the A on the T2 line. Delete the
required station, and then insert a line (below the station being deleted). Insert the new station and details
using the same LG (LEG) number.
 To Replace MIA with LAX on BF:T/

T1 1 KL 13
T2 1 ATL 1900
T2X2 MIA 2100
T2 2 LAX 2120
!A
6.2.4 Departure or Arrival Time Change

If you want to change the departure or arrival time of a station, inset the C under A on the T1 and T2 line,
and replace the old time with the new time. I f you forget to enter the C under the A on the T1 line, you will
get an error response.
 Example Change of Arrival Time in MIA from 2100 to 2120 on BF:T/:

T1C1 KL 13
T2 1 ATL 1900
T2C2 MIA 2120
T2
!A

Note: It is possible to change the times without using the C amendment, but it is recommended that the
correct procedure be used.

6.2.5 Cancellation of Schedule
To completely cancel a schedule from the system, enter the flight number and dates required, and then
enter an X under the A on the T1 line.
 To Cancel the Schedule of BF:T/

T1X1 KL 13
T2 1 ATL 1900
T2 2 MIA 2100
!A
The schedule must be filed and activated (to activate the cancellation).
6.2.6 Copy Schedule

When creating many schedules it is possible to display an already created schedule, and to change the
flight number, adjust the dates and frequency, and make any other adjustments as required, and then
transmit the file to activate the schedule.
Example to display the first schedule to copy, enter:
BF:T/XS992/26JUL
Note: The C (change) character is only required if the flight period is currently active. If the flight period is
not active then all that is required is to re-enter.
Response for Copy Schedule:

T1 1 KL 13
T2 1 ATL 1900
T2 2 MIA 2100
!A
Change the Details by Replacing the Old Data with the New Data:
BF:T/XS217/1/18APR06/14DEC06/D
T1 1 KL 45
T2 1 ATL 1900
T2 2 PHX 2045
!A
The screen is then transmitted and activated.

Error Responses
AIRLINE Invalid airline code specified (or not created in AT table - check with
SITA Customer Support).
DATE Invalid date or dates entered.
FLT NBR RI index missing. Re-file and re-activate schedule.
FORMAT Incorrect entry, or missing data.
SKED CHANGE Another agent has displayed this flight, which prevents anyone else
from re-displaying it, until it has been actioned or ignored.
SCHED CHANGE PENDING Attempt to sign-out after displaying a flight without staging or ignoring
it.
TABLE FULL Free space record is full and new flight cannot be added. Contact
SITA Customer Support.
6.3. Staged Flights List (SFL:)

Once a flight has been created by the BF:T transaction, it goes into a 'staged' list. This is so that any final
changes can be done to the schedule before it is activated and processed into the 'live' system.
The entry to display any staged flights is:
SFL:AIRLINE
Response of SFL (Staged Flights List)
FLIGHT RECORD LISTINGS XS STAGED # _ TTY INPUT
XS 105 XS 269# XS 423 XS 559 XS 666 XS 729#
If there is a '#' after the flight number, it denotes that the flight schedule was built by a SITA Reservations
Agent using the SC:T form and not in DCS either by the BF:T form or DFD entry.
It is possible to display the flight schedule for an individual flight on this list by entering:
SFL:FLIGHT NUMBER
Response Individual Flight (SFL:XS105)
FLIGHT RECORD LISTINGS XS 105
►BF:T/XS105/18APR06 /11OCT06/D
It is possible to display the schedule by transmitting the screen after the frequency. The normal BF:T
schedule is displayed and any further changes can be carried out.
Note: To cancel a schedule that has not been activated, and which is still on the SFL list, is different from
the normal procedure. Enter 'IG' after the flight number, either from SFL display (BF:T/XS298/IG), or from
the BF:T display (the system will not accept X under A on the T1 line as it responds with the error 'DATE').
Once a flight is created, and has gone onto the staged list, it should be activated as soon as possible. It is
not advisable to leave too many flights on the staged list as this can lead to problems with that schedule
later on, especially if the effective date has passed.

On displaying the BF:T schedule for a staged flight, the screen responds with a flashing number on the top
right hand side. This indicates the agent sign-in number of the person who last worked, or who is still
working, on this schedule. Once a flight is activated, this number disappears.
 A BF:T of a Staged Flight

T1 1 KL 13
T2 1 ATL 1900
T2 2 MIA 2100
!
6.4. Activate Flights (BPR: / ACT)

After a flight is staged, and no further amendments are required, it must then be activated into the system.
Only one flight at a time can be active.
The entry is:
BP:R/ACT/FLIGHT NUMBER
The response to this entry will be a message that is sent to the transmitting CRT. By pushing the 'MSG
WAIT' key the following response is displayed on the screen:
FLIGHT LOAD COMPLETE
Note: Sometimes if the BP:R/ACT/FLIGHT transaction is entered too quickly after filing the BF:T
transaction, this causes the activation to fail. The result is that an error message goes to the KF reject
office queue with the response 'RI INDEX NOT FOUND', and on trying to initialize or display the flight, the
response is 'FLT NBR'. The way to solve this problem is to re-display, and re-file the BF:T schedule, wait
about ten seconds, and then try the BP:R/ACT/FLIGHT transaction again. If this does not solve the
problem, then contact SITA Customer Support.
Error Responses
FLT NBR Flight number format entry is incorrect.
BAD DATA IN FILE Attempting to activate a staged flight that has errors in it.
FLIGHT ACTIVATE IN PROGRESS A previous flight activate transaction was not completed.
Previous flight must be cleared or canceled first before
continuation.

6.5. Active Flights List (AFL)
Once a flight is activated into the system it goes on the 'active' flight list. This list is by airline and gives a
list of all the active flights for that airline. It cannot be displayed by date, only by airline or flight number.
The entry to display the active flights list is:
AFL:AIRLINE
AFL (Active Flight List) Response
FLIGHT RECORD LISTING XS # _ TTY INPUT
XS 069 XS 100# XS 101# XS 103# XS 111# XS 125 XS 200
XS 210# XS 220# XS 260# XS 270# XS 272 XS 290 XS 298
XS 300 XS 302 XS 310 XS 312# XS 330# XS 350# XS 355
If there is a (#) after the flight number, then this denotes that the flight schedule was built by a
Reservations Agent using the SC:T form and not in DCS either by the BF:T form or DFD entry.
It is possible to display the flight schedule for an individual flight on this list by entering:
AFL:FLIGHT NUMBER
Response for Individual Flight (AFL:XS298)
FLIGHT RECORD LISTINGS XS 298
►BF:T/XS298/01SEP06 /01DEC06/23
►BF:T/XS298/01JAN07 /00XXX00/D
It is also possible to display the BF:T schedule by transmitting the screen after the frequency of the
schedule date required (example BF:T/XS298/01SEP06 /01DEC06/23). The date displayed as '00XXX00'
means that this schedule has no end of operation date (infinity).
6.6. Flight Schedule Period (FPD)

The flight schedule period display will give all the master and active dates for a flight.
The entry is:
FPD:FLIGHT NUMBER
Flight Schedule Period Response (FPD:XS299)
FPD:XS299
MASTER PERIODS:
►FDD:XS299/07JUN06/MF 25OCT06 4
►FDD:XS299/09JUN06/MF 27OCT06 26
ACTIVE DATES:
►FDD:XS299/24JUL06/F
►FDD:XS299/26JUL06/F

Explanation:
Field Explanation
MASTER PERIODS The master periods are all the BF:T schedules created in the system for that
flight number. The MF after the effective date stands for Master Flight.
ACTIVE DATES The active dates are flights that are currently active in the system. If a flight
operates daily, then normally there will be four active dates, for two days back,
today, and tomorrow. The F after the effective date allows viewing the flight
while the schedule changes are in progress.
In addition to the current date, active flights will display for five days past and
three days in the future.
It is possible to display a list of either the Master periods or Active dates by themselves.
The entry for Master periods is:
FPD:FLIGHT NUMBER/M
The entry for Active dates is:
FPD:FLIGHT NUMBER/A
FDD:FLIGHT NUMBER/DATE Response
►FDD:XS102/27JULY
XS102 27JUL06 D __ACTIVE__
ATL 1055 T_13 737/A
MIA 1245
IRREGULAR OPERATION DETAILS
SUPPLEMENTAL INFORMATION
6.7. Single Day Schedule Create / Change (DFD:)

The DFD/EFD transactions allow an authorized agent to create or make schedule changes for a flight for a
single day, without having to use the BF:T transaction.
Note: The DFD/EFD transaction can be used even if the flight was originally created by the BF:T
transaction and involves many date ranges, as long as only one date is specified in the entry.
The entry is:
DFD:FLIGHT/DATE
DFD:FLT/DATE/DAY OF OP (for Two Aircraft Types on Schedule) DFD:/EFD:

 DFD:XS100/. Single Day Schedule
►EFD: XS100/1/26JUL06/4
T1
T2
T2
T2
 Single Day Schedule (DFD): Entry:

►EFD: XS100/1/26JUL06/4
T1 1 DL 7
T2 1 ATL 2300
T2 2 MIA 0030+1
!
After entering the (!), the response is:

ACCEPTED _ BACKGROUND TASK STARTED
The response to this entry is a message that is sent to the transmitting CRT. Pushing the 'MSG WAIT' key
displays the following response on the screen:
FLIGHT LOAD COMPLETE
Note: When using the DFD/EFD transactions, the flight does not get Staged (SFL) first, but is activated
onto the Active flight list (AFL). There is no need for the BP:R/ACT/FLT transaction to be used.
The following is a list of the operations that can be handled by the DFD/EFD transactions:
 Create a new flight for a one-day schedule.
 Delete (cancel) a flight for a one-day schedule.
 Change the CND table number for a one-day schedule.
 Add a station to the routing for a one-day schedule.
 Delete a station from the routing for a one-day schedule.
 Change the routing order for a one-day schedule.
 Change any of the departure, arrival, or boarding times.
All of the above are handled in exactly the same way as the BF:T transaction, so the X, C, D, A, etc. must
be used when necessary.
Also all the error code number responses are the same, so check the chapter on BF:T for explanation.
The main advantage of using the DFD transaction, rather than the BF:T transaction, is that a single
schedule (from a flight date range) can be amended without affecting the other flight dates, and thus
prevent many BF:T scheduling errors.
Note: Whenever a DFD schedule is displayed that it be either filed (!), or ignored (IG), otherwise the
system responds with 'SKED CHANGE’ when attempting to sign-out (SO) from the transmitting CRT.
Enter the 'IG' at the same position (but not at the same time) as the '!'.

DFD/EFD CND Table Number Change:
 Display the Schedule (Example 'DFD:XS583/04JUN04')

EFD: XS583/1/04JUN06/2
T1 1 DL 23
T2 1 ATL 1655
T2 2 LAX 1815
! Do not add an A with DFD: transaction.
 Enter the Required CND Number and Use 'C' Indicator and Re-File
EFD: XS583/1/04JUN06/2
T1C1 DL 47
T2 1 ATL 1655
T2 2 LAX 1815
!
The response should be 'ACCEPTED - BACKGROUND TASK STARTED'.

DFD/EFD Change of Departure and Arrival Times:
 Display the Schedule (Example 'DFD:XS927/03JUN06')

EFD: XS927/1/03JUN06/1
T1 1 DL 114
T2 1 ATL 0852
T2 2 SFO 1035
!
 Enter the New Required Times and Re-File the Schedule

EFD: XS927/1/03JUN06/1
T1C1 DL 114
T2C1 ATL 0905
T2C2 SFO 1050
!
The response should be 'ACCEPTED - BACKGROUND TASK STARTED'.

6.8. Flight Data Display (CSD:)
The CSD (created schedule data) can be displayed for a particular date or for a flight schedule period. It
gives information such as:
 office message address table number
 whether the flight is initialized on receiving the PNL (DF NO), or if it will be deferred for manual
initialization (DF YES)
 schedule departure time (STD)
 passenger boarding time (BDT)
 aircraft type and version (EQ)
 weight table number used (WTN)
 aircraft configuration (CFG)
 type of check-in (name, numeric, etc.), and if seating used
 passenger messages (MSG) required for this flight.
The entry is:
CSD:FLIGHT/START DATE/END DATE
CSD Response
CSD:1 FL XS846/23APR X7 SPAN 20APR06 14MAY06 DF YES
1 ATL CTL_OFFC 2 SD 1530 ED 1530 BDT 1500
EQ 737/A WTN 1 CWT 262143 CFG F12Y87
TCKI TCI TYPE NAM SS GO_SHOWS F511Y511
POS GATE GATES
MSG PTM TPM PIL PSM COM IDM SOM PFS BTM IFM API FTL PRL ETL PIM CAT
2 MIA CTL_OFFC 1 SA 1645
SEGMENT DATA
6.9. Flight Data Amend (CSM:)

The schedule flight data can be amended for a particular date or for the whole flight period. The date
range must be the same as shown on FPD. The date range is required if the flight is beyond five days.
The entry for one particular date is:
CSM:FLIGHT/DATE
The entry for a flight period is:
CSM:FLIGHT/START DATE/END DATE
CSM:FLIGHT/START DATE/OPEN
Note: The correct flight period dates must be entered, especially if many different date ranges have been
created for the same schedule (BF:T). The correct flight period can be checked by entering the
FPD:FLIGHT display and selecting the required dates.

The following example shows things that can be changed *in bold lettering*.
 What can be changed on a CSM

CSU:1 FL XS846/23APR X7 SPAN 20APR06 14MAY06 DF YES
1 ATL CTL_OFFC 2 SD 1530 ED 1530 BDT 1500
EQ 737/A WTN 1 CWT 262143 CFG F12Y87
TCKI TCI TYPE NAM SS GO_SHOWS F511Y511
POS GATE GATES
MSG PTM TPM PIL PSM COM IDM SOM BTM PFS IFM API FTL PRL ETL PIM CAT
2 MIA CTL_OFFC 1 SA 1645
SEGMENT DATA
Explanation:
Field Explanation
CTL-OFFC Number refers to the message address number created in the CX:DEST table, and
determines the address where the requested messages are sent.
WTN Number refers to the Passenger weight table created in the CW:AIRLINE table,
and determines whether Gender input is required at check-in.
CWT Check-in weight allowance. If no restricted weight is entered, the system defaults
to 262143.
TCKI Specifies whether 'through' transfer check-in is allowed onto another flight for those
stations connected to DCS downline. System defaults to TCI.
TYPE Type of check-in and the seating conditions for this flight. There are various types
of check-in, including:
NAM - NAME check-in. (Passenger's names on PNL)
NUM - NUMERIC check-in. (No names on PNL)
PNM - PARTIAL NAME check-in. (Special passengers only)
NON - NON-AUTOMATED station. (Non SITA DCS user)
TCL - TECHNICAL LANDING only. (No check-in allowed)
TYPE There are only two main types of seating conditions:
(Continued) SS - SEAT SELECTION (seat numbers used).
NS - NO SEAT SELECTION (free seating).
Note 1: On a multi-sector flight, it is not possible to change from an NS leg to an
SS leg, but it is possible to change from SS to NS.
Note 2: NS can be by class i.e., NSY would indicate no seating in Y class, but
seating applies in other classes.
It is possible to have seat selection in one class and free seating in another class.
In this case the NS entry is used specifying the class where free seating is used
(example NSY) and the system defaults to seating in the other class (or classes) on
this flight.
GO-SHOWS Not functional.
MSG Passenger message types required to be sent at the end of a flight and the system
checks the CTL-OFC number to find the correct message addresses. If any of

Field Explanation
these messages are not required, they should be deleted, otherwise the system
looks for an address.
The message types are:
PTM - Passenger Transfer Manifest.
TPM - Teletype Passenger Manifest.
PIL - Passenger Information List.
PSM - Passenger Service Message.
COM - Close-Out (final) Message.
IDM - Industry Discount Message.
SOM - Seats Occupied Message.
BTM - Baggage Transfer Message. (*See CX Table description.)
PFS - Passenger Final Sales Message.
IFM - Interline (EDIFACT flights) Fallback Message.
FTL - Frequent Traveler List.
API - Advance Passenger Information.
Note: Although API may be present the actual message is only created if a station
on the flight route requires it.
PRL - Passenger Reconciliation List.
ETL - Electronic Ticket List.
PIM - Passport Information Message.
PMI - Passenger Manifest Information.
ETM - EDIFACT Transfer Message.
CAT – Catering Message, Special Meals

Field Explanation
SEGMENT DATA This is used for entering any special information or restrictions on the flight. The
most common ones used are:
NLT - No Local Traffic check-in allowed traffic for this segment (no traffic rights).
NLD – No Local Traffic except ID passengers allowed.
NAV - No Live Animals allowed.
BPI – No-Pooled Baggage Indicator is used by selected airlines.
API - Inhibits the issuance of a boarding pass if the appropriate API data is
incomplete in the passenger record. (Supported by parameter APIC - contact
SITA Customer Support to turn on.)
These are entered as: SEGMENT/NLD (example MIALAX/NLD)
To remove enter as: SEGMENT/-NLD (example MIALAX/-NLD)
Note: Although these are entered via the CSM/CSU screen, they are only
displayed on the CSD screen. So always check the CSD screen if in doubt.
By using the TAB key, the cursor moves to a valid item that can be changed, and
the appropriate item is then entered. Once the changes are entered the system
should respond with 'ACCEPTED'.
If the changes are for a flight period the system may respond with 'ACCEPTED'
followed by 'ACTIVE DATES ARE:' In this case the system has only updated the
non-active flights, so the active flights have to be updated individually. This
prevents updates to active flights in case the new changes do not apply to them. If
they do apply, they must be amended individually.
Error Responses
CLASS Error with class groups used.
CONTROL MSG TYPE not NAM, so remove TPM, PIL, and PSM.
DATE Invalid date entered.
ERR-MANUAL CHECK-IN Check-in application not specified in BF:T.
FLT CANCELLED Flight specified is canceled.
FLT INIT Flight initialized so field cannot be updated.
FLT NBR Flight number format entry is incorrect.
FORMAT Invalid format entry.
GO-SHOW Invalid entry or exceeds compartment capacity.
SEAT SELECTION Invalid option entered or SS follows a NS segment.
SEGMENT Invalid segment entry or NLD/NLT entered together.
SKED-CHANGE Schedule change (BF:T) is in progress-must be cleared before displaying.

7. Passenger Baggage Allowance/Excess Rate
7.1. Free Baggage Allowance from Electronic Ticket Record
The Free Baggage Allowance (FBA) may be determined from information in the Electronic Ticket Record
(ETR). SITA Departure Control Services compares the baggage entered during check-in with the FBA in
the ETR and not the baggage allowance in the Passenger Baggage Allowance Table.
Notes:
If ‘FBA from ETR’ in the ETTD table is set to ‘Y’, and the FBA is determined to be exceeded, the SITA
Departure Control Services Passenger Excess Baggage Rates Table is used to determine the charge to
apply.
If ‘FBA from ETR’ is set to ‘N’, as the default, or the Free Baggage Allowance is not entered in the
Electronic Ticket Record or both, the system uses the baggage allowance from the Departure Control
Services tables.
This feature is a contract addendum. Please contact your SITA Representative.
7.2. Passenger Baggage Allowance Table
This screen is used to enter the weight or piece by class of the passenger check-in baggage allowance. It
also specifies what currency the excess baggage will be calculated in, and also allows the entry of other
currencies with their conversion rates for later conversion changes if required. An excess baggage
allowance table must be built for all handled carriers as well as the host.
The entry is:
JXD:AIRLINE
JXD Response
JXU: BAGGAGE ALLOWANCE FOR XS ATL
CLASS F C Y M K
WEIGHT ALLOWANCE 30 30 20 20 20
PIECE ALLOWANCE 2 2 1 1 1
LOCAL CURRENCY USD
FOREIGN CURRENCY GBP YEN DKM FFR
EXCHANGE RATE 0.625 157.8 1.7475 5.826
TO DISPLAY COSTS FOR DESTINATION ENTER CITY IN FIELD BELOW
►JCD:XS /ATL
Explanation:
Field Explanation
CLASS All of the master class codes used by the airline (check CD:airline) must be
entered here. It is not necessary to enter sub-classes as the check-in
transaction will be the default of the appropriate master class allowance. If a
sub-class should have an allowance different than the master, then that class
should also be entered here with its allowance.
WEIGHT/PIECE The weight and piece allowance for each class is entered here.
ALLOWANCE
LOCAL CURRENCY The currency entered here is the currency the excess baggage is calculated in
during the check-in transaction. Therefore the figures entered on the excess
baggage rates table (JCD:AIRLINE) are related to this currency.
Passenger Baggage Allowance/Excess Rate
Foreign Currency/Exchange Rate
If passengers are allowed to pay their excess baggage by other currencies, enter the conversion rate from
the local currency. It is possible for the check-in agent to insert the required currency for the excess
baggage at check-in, and the system calculates the new amount due.

7.3. Passenger Excess Baggage Rates (JCD:)
Use this screen to enter the excess baggage rates from the CRT station to the final destination of the
passenger. Therefore not only must all the destinations of the airline be entered, but all onward
connection destinations as well. An excess baggage rates table must be built for all handled carriers as
well as the host.
The entry is:
JCD:AIRLINE
JCD Response
JCU: EXCESS BAGGAGE COSTS FROM XS ATL
CITY W/P UNIT COST CITY W/P UNIT COST CITY W/P UNIT COST
CHI P 2.25 HOU P 1.50 JFK W 2.90
LAX P 2.30 LGW W 8.90 MEX W 5.45
MIA P 1.75 ORY W 10.35 ____ __ ______
** TO DELETE CITY ENTER X IN W/P FIELD **
Explanation:
Field Explanation
CITY The destinations are entered here (enter airport codes). They do not need to
be entered in alphabetical order, as the system does this when the screen is
transmitted.
If a CITY must be deleted, then enter an X under the W/P field, and transmit.
The selected CITY is deleted.
If only an amendment to the W/P or UNIT COST is required, make these by
replacing the old information with the new and transmitting (there is no need to
delete the CITY and re-enter).
W/P Enter whether the allowance is weight (W) or piece (P). Only one or the other
can be specified, but not both together.
UNIT COST Cost per KG or piece of the excess amount of baggage over the allowance.
The rate is based on the local currency entered on the JXD:AIRLINE screen.
If the screen is full, it is possible to move to other pages by inserting the
routing. Example JCD:ATLZRH (but be careful because if you only enter
JCD:ZRH by mistake, you will get a display of the excess baggage rates table
out of ZRH and not out of ATL).
Unit cost is by kilogram or pound based on weight unit shown in the weight
table.
Error Responses
**** WARNING ILLEGAL CHARACTER IN FIELD This indicates that a character (not X, P, or W)
was input in the entry.

8. Database Check List
8.1. Check-In Entries
DRC:XS STATION (INC OWN STN) Check-In STN Creation
8.1.1 Seat Map Creation

EQC:XS/(FLEET)/(VERSION)/DATE Seat Map Creation
SEM:XS/(FLEET)/(VERSION) Seat Map Display
ED:XS List of Seat Maps
ED:TYP List of all Created Types
EQI:ENTRY NUMBER Display EQC A/C Entry
EXM:ENTRY NUMBER D DATE RANGES To Delete Seat Maps
8.1.2 Aircraft Configuration Table (CND)

CND:A List of A/C Configs
CND:FAVAIL First Avail Number
CND:A/AIRCRAFT TYPE List of One A/C Type
8.2. Flight Schedule Entries

FPD:FLIGHT NUMBER Schedule Period
BF:T/FLIGHT NUMBER/DATE Schedule Display
BF:T/FLT NBR/1/START/END Schedule Build
DATE/FREQUENCY
SFL:XS Staged Flights
BP:R/ACT/FLIGHT NUMBER Activate Flight
DFD:FLIGHT/DATE One Day FLT Create/Amend FP
AFL:XS List Active FLTS
CSD:FLIGHT NUMBER/DATE Flight Data Display
CSM:FLIGHT NUMBER/START/END DATE Flight Period Update
FDD:FLIGHT NUMBER/DATE Active FLT Info
FUI:FLT NBR/DATE/STN/CODE/DATA Enter FLT Info

Database Check List
8.3. Station Data Entries
CW:XS PAX Weight Table
CWC:XS Create PAX WT Table
PZ:XS Staff Priority Table
PZC:XS Create Staff Priority
PZM:XS Modify Staff Priority
CD:XS Master/Equiv Classes
CGC:XS;MASTER EQUIV CLASS/ETC Create Equiv Classes
CX:XS/STN(OFFICE NUMBER) STN Messages Addresses
CMC:XS STN(OFF NBR);CODES,MSG ADDRESS Create Addresses
CMM:+CODES,MSG ADDRESS,PID NBR,CD Modify Addresses
ETC
JXD:XS Baggage Allowance
JCD:XS/ATL Excess Bag Rates
AZ:ATL Airport Gate Numbers
AZC:ATL ZONE,GATE,GATE Create Gate Numbers
AZM:+ZONE,GATE Add New Gate
SFM:(CODE) Display Specific Code

Database Check List
9. Teletype Addresses
9.1. System Addresses
These are the addresses required by DCS for the following messages so that they read into the SITA DCS
system:
PNL HDQCRxx 1 (Passenger Name List for CKI)

4
ADL HDQCRxx (Additional Name List for CKI)
4
SOM HDQCSxx (Seats Occupied Message for CKI/LDP)
4
LDM HDQLPxx (Load Message for LDP)
4
LPM HDQLPxx (Load Planning Message for LDP)
4
CPM HDQLPxx (Container/Pallet Message for LDP)
1 xx – Host airline.
Teletype Addresses
10. Conversion Table (General)
To Convert Into Multiply by
Centigrade Fahrenheit 9/5 + 32
Centimetres Inches 0. 3937
Centimetres Metres 0. 0100
Cubic feet Cubic centimetres 28320. 0000
Cubic feet Cubic inches 1728. 0000
Cubic inches Cubic centimetres 16. 3900
Cubic metres Cubic feet 35. 3100
Cubic metres Cubic inches 61. 0230
Inches Centimetres 2. 5400
Inch Millimetre 25. 4
Kilograms Pounds (16 ounces) 2. 2046
Kilograms per cubic foot Pounds per cubic foot 2. 2046
Kilograms per cubic foot Kilograms per cubic metre 35. 3100
Kilograms per cubic meter Pounds per cubic foot 0. 0624
Meters Centimetres 100. 0000
Metres Feet 3. 2808
Meters Inches 39. 3700
Millimetres Centimetres 0. 1000
Millimetres Inches 0. 0394
Pounds (16 ounces) Kilograms 0. 4536
Pounds per cubic foot Kilograms per cubic foot 0. 4536
Pounds per cubic foot Kilograms per cubic metre 16. 0166
Pounds per cubic metre Kilograms per cubic food 0. 0128

Conversion Table (General)

11. Glossary
-A-
ADL PNL addition/deletion list.
AEC Automatic Equipment Change.
ALD Automatic Load Planning.
API Advanced Passenger Information.
-B-
BI Basic Index.
BN Boarding Number.
BRC Bulk Recheck Accepted passengers.
BRN Bulk Recheck Not Checked-In Passengers.
BTM Baggage Transfer Message.
BW Basic Weight.
-C-
CAT Catering Message, Special Meals
CGO Cargo.
CKI Check-in.
CND Configuration Table Number Display.
COM Close Out (final) Message. (Dispatched to all stations)
CPM Container/Pallet Message.
CRT Cathode Ray Tube, this is the display.
CSD Created Schedule Data.
CSM Created Schedule Modification.
-D-
DFL Delete Flight.
DOI Dry Operating Index.
DOW Dry Operating Weight.
DPID Entry for Printer/Check-in Zone Information.
DRC Destination Remarks Creation.
-E-
EDIFACT Electronic Data Interchange for Administration, Commerce and Transport.

Glossary
ETL Electronic Ticket List.
ETR Electronic Ticket Record
ETM EDIFACT Transfer Message (ITCI partner listed from departure city LH only).
-F-
FBA Free Baggage Allowance
FDC Flight Schedule.
FDD Flight Data Display.
FIR Flight Irregular Operations.
FLP Flight Planning.
FTL Frequent Traveler List.
FUI Flight Update Information.
-G-
GMT Greenwich Mean Time.
-H-
HA Host Airline.
-I-
IDM Industry Discount Message. (Dispatched to next downline station on Multi-sector flights.)
IFM Interline (EDIFACT flights) Fallback Message.
-L-
LDP Load Planning.
LDVS System Selected Deck Version.
LEMAC Leading Edge Mean Aerodynamic Chord.
-M-
MAC Mean Aerodynamic Chord.
MD Manifest Display.
-N-
NAM SS Name Check-In with Seat Selection.

Glossary
-O-
OA Other Airline.
-P-
PAD Passenger Available for Disembarkation.
PCI Passenger Statistics.
PDQ Physical Device Queuing.
PFS Passenger Final Sales message. (Originating station only.)
PID Physical device identifier. Numeric address of a peripheral device that is also known as
position identifier or port identifier.
PIL Passenger Information List. (Originating station only)
PIM Passenger Information Message.
PN Page Next.
PNL Passenger Name List.
PRL Passenger Reconciliation List.
PSM Passenger Service Message. (Dispatched to all stations.)
PTM Passenger Transfer Manifest. (Dispatched to all stations having transfer.)
-S-
SB Standby Number.
SLD Statistical Load Summary.
SOM Seats Occupied Message. (Dispatched to next downline station.)
SSR Special Service Request.
STD Scheduled Time of Departure.
SUD Special Usage Description.
-T-
TOW Take Off Weight.
-X-
XS SITA Airline.
XX Any Generic Airline.

Glossary
Style Symbols
 Example indicator
 Start of Entry indicator

Glossary
12. Index
Activate Flight ................................................... 62 CW
Active Flight List ............................................... 63 , Passenger Weight Tables ....................... 13
AFL, Active Flight List ...................................... 63 CX Tables ........................................................ 19
Airline Revenue Booking Designator ................. 3 Database Checklist .......................................... 74
Airport Gate Numbers ...................................... 24 Date Change, Flight Schedule ......................... 58
Amend Flight Data ........................................... 67 Delete Check-In Station ................................... 11
Amend Flight Schedule .................................... 57 Delete Seat Map .............................................. 46
Amend Seat Map ............................................. 45 Delete Seat Map Date Ranges ........................ 46
Amend Seat Map Date Ranges ....................... 46 Departure Time Change, Flight Schedule ....... 59
Amend Seat Map Dates ................................... 46 DFD
Application or Configuration Change ............... 58 Transaction ................................................ 64

Dispatched Passenger Messages ................... 19
Application or Configuration Change, Flight
Schedule ....................................................... 58 Display Flight Data ........................................... 67
Arrival Time Change, Flight Schedule ............. 59 Display Flight Schedule ................................... 53
AZ, Airport Gate Numbers................................ 24 Display Flight Schedules ................................. 57
Baggage Allowance Table, Passenger ............ 71 Display Seat Map ............................................. 44
Build Flight Schedule ....................................... 53 DRC, Create Check-In Station ......................... 11
Cancel a CND Table Number .......................... 10 DRD, Delete Check-In Station ......................... 11
Cancel Schedule .............................................. 60 ED
CD ...................................................................... 3 Seat Map List ............................................ 43
Change Single Day Schedule .......................... 64 Entry, Flight Schedule ...................................... 53
Check-In Entries ............................................... 74 EQ Transaction, Using ..................................... 45
Check-In Station, Create .................................. 11 EQC
Check-In Station, Delete .................................. 11 Create Seat Map ....................................... 31

EQI Transaction, Using .................................... 45
CND
Equivalent Classes, CD ..................................... 3
FAVAIL Configuration Table ........................ 8
CND Table Number, Cancel a ......................... 10 Error Codes, Seat Map Creation ..................... 37
CNDTable........................................................... 6 Excess Baggage Rate ..................................... 71
Compartment, Split .......................................... 50 Excess Baggage Rates, Passenger ................ 73
Configuration Table, List of ................................ 6 FAVAIL Table..................................................... 8
Copy Schedule ................................................. 60 First Available Table .......................................... 8
Create Check-In Station ................................... 11 Flight Data Amend ........................................... 67
Create Seat Map .............................................. 31 Flight Data Display ........................................... 67
Create Single Day Schedule ............................ 64 Flight List, Active .............................................. 63

Index
Flight Schedule Date Change .......................... 58 Schedule, Copy................................................ 60
Flight Schedule Entries ..............................53, 74 Seat Map Creation ........................................... 31
Flight Schedule Period ..................................... 63 Seat Map Creation Error Codes ...................... 37
Flight Schedule, Amend ................................... 57 Seat Map Dates, Amend .................................. 46
Flight Schedule, Build ...................................... 53 Seat Map Display ............................................. 44
Flight Schedule, Display................................... 57 Seat Map, Amend ............................................ 45
Flight, Activate .................................................. 62 Seat Map, Delete ............................................. 46
Foreign Currency Exchange Rate .................... 72 Seat Map, Re-instating .................................... 47
FPD, Flight Schedule ....................................... 63 Seat Map, Two Class ................................. 51, 52
Free Baggage Allowance from Electronic Ticket Seat Maps ........................................................ 31
Record .......................................................... 71
Seat Maps, List ................................................ 43
Gate Numbers, Airport ..................................... 24
SEI
JCD
Seat Map Display ...................................... 44
, Excess Baggage Rates ........................... 73 SEI Transaction ............................................... 44
List of Configurations Table ............................... 6
SEM
List of Seat Maps ............................................. 43
Display Seat Map ...................................... 44
Location Travel Times ...................................... 27 SFM
LZ Table ........................................................... 27 , Static File Maintenance ........................... 30
Master/Equivalent Classes................................. 3 Single Day Schedule, Create or Change ......... 64
Message Address Tables, Passenger ............. 19 Split Compartment ........................................... 50
Movable Partitions ............................................ 49 Staff Priority Tables.......................................... 16
MP, Movable Partitions .................................... 49 Staged Flight List ............................................. 61
Passenger Baggage Allowance ....................... 71 Static File Maintenance Display....................... 30
Passenger Baggage Allowance Table ............. 71 Station Data ..................................................... 13
Passenger Excess Baggage Rates ................. 73 Station Data Entries ......................................... 75
Passenger Message Address Tables .............. 19 System Addresses ........................................... 76
Passenger Messages Dispatched ................... 19 Teletype Addresses ......................................... 76
Passenger Weight Tables ................................ 13 Travel Times, Location .................................... 27
Priority Tables, Staff ......................................... 16 Two Class Seat Map .................................. 51, 52
PZ Tables ......................................................... 16 Using the EQ Transaction .......................... 45, 47
Routing Change ............................................... 59 Using the EQI Transaction ............................... 45
Routing Change, Flight Schedule .................... 59 Weight Tables, Passenger ............................... 13
Schedule, Cancellation .................................... 60

Index

SITA Departure Control Services Check-In Database User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SITA Departure Control Services Check-In Database User Guide

Uploaded by

Copyright:

Available Formats

Passenger Solutions

SITA Departure Control Services

1.2. Guide Objectives..................................................................................................................................... 1

2. Airline Revenue Booking Designator ........................................................................................... 3

2.1.1 Initial CD Table Creation ............................................................................................................. 3

2.2. Additional CD Tables Creation ................................................................................................................ 4

2.2.1 Requirements .............................................................................................................................. 4

2.2.2 Entry to Create Additional CD Tables .......................................................................................... 4

2.3. Entry to Display CD Tables ..................................................................................................................... 5

2.4. Entry to Amend or Update CD Tables within Flight Schedules ............................................................... 5

2.4.1 Aircraft/Equipment Change ......................................................................................................... 6

2.5. Aircraft Configuration Tables (CND:A) .................................................................................................... 6

2.6. First Available Table (CND:FAVAIL) ....................................................................................................... 8

2.7. Cancel a CND Table Number ............................................................................................................... 10

3. Check-In Station Creation ........................................................................................................... 11

3.2. Check-In Station Delete (DRD:) ............................................................................................................ 11

4. Station Data .................................................................................................................................. 13

4.2. Staff Priority Tables (PZ:) ...................................................................................................................... 16

4.3. Passenger Message Address Tables (CX:) .......................................................................................... 19

4.4. Airport Gate Numbers (AZ:) .................................................................................................................. 24

4.5. Location Travel Times (LZ:) .................................................................................................................. 27

4.6. Static File Maintenance Display (SFM:) ................................................................................................ 30

5. Seat Maps ...................................................................................................................................... 31

5.2. Seat Map Creation Error Codes ............................................................................................................ 37

5.3. List of Seat Maps (ED:) ......................................................................................................................... 43

SITA Departure Control Services Check-In Database User Guide

5.4.1 By Using the SEM Transaction .................................................................................................. 44

5.4.2 By Using the SEI Transaction .................................................................................................... 44

5.5. Amend Seat Map (EQ: / EQI:)............................................................................................................... 45

5.5.1 By Using the EQ Transaction .................................................................................................... 45

5.5.2 By Using the EQI Transaction ................................................................................................... 45

5.6. Delete/Amend Seat Map Date Ranges (EXM:) ..................................................................................... 46

5.6.1 Delete Seat Map ........................................................................................................................ 46

5.6.2 Amend Seat Map Dates ............................................................................................................ 46

5.6.3 Re-instating a Seat Map ............................................................................................................ 47

5.7. Movable Partitions (MP) ........................................................................................................................ 49

5.8. Split Compartments (F Y C Y)............................................................................................................... 50

5.8.1 Two Class Seat Maps (Split Compartments) ............................................................................. 51

6. Flight Schedules Entries (FDC) .................................................................................................. 53

6.1.1 Build Flight Schedule ................................................................................................................. 53

6.1.2 Display Flight Schedules ........................................................................................................... 57

6.2. Amend Flight Schedule ......................................................................................................................... 57

6.2.1 Date Change ............................................................................................................................. 58

6.2.2 Application or Configuration Change ......................................................................................... 58

6.2.3 Routing Change......................................................................................................................... 59

6.2.4 Departure or Arrival Time Change ............................................................................................. 59

6.2.5 Cancellation of Schedule ........................................................................................................... 60

6.2.6 Copy Schedule .......................................................................................................................... 60

6.3. Staged Flights List (SFL:)...................................................................................................................... 61

6.4. Activate Flights (BPR: / ACT) ................................................................................................................ 62

6.5. Active Flights List (AFL) ........................................................................................................................ 63

6.6. Flight Schedule Period (FPD) ............................................................................................................... 63

6.7. Single Day Schedule Create / Change (DFD:) ...................................................................................... 64

6.8. Flight Data Display (CSD:) .................................................................................................................... 67

SITA Departure Control Services Check-In Database User Guide

7. Passenger Baggage Allowance/Excess Rate ............................................................................ 71

7.2. Passenger Baggage Allowance Table .................................................................................................. 71

7.3. Passenger Excess Baggage Rates (JCD:) ........................................................................................... 73

8. Database Check List .................................................................................................................... 74

8.1.1 Seat Map Creation..................................................................................................................... 74

8.1.2 Aircraft Configuration Table (CND) ............................................................................................ 74

8.2. Flight Schedule Entries ......................................................................................................................... 74

8.3. Station Data Entries .............................................................................................................................. 75