Documente Academic
Documente Profesional
Documente Cultură
Copyright Notice
SITA, 2000 2008
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. General Information ................................................................................................................................ 1
1.2. Course Objective .................................................................................................................................... 1
2.
3.
4.
5.
6.
Page v
SITA 2008 All Rights Reserved
7.
8.
Page vi
SITA 2008 All Rights Reserved
8.2.21.11
8.2.21.12
Page vii
SITA 2008 All Rights Reserved
Page ix
SITA 2008 All Rights Reserved
9.
List of Tables
Table 2.1 Sign in entry description ...................................................................................................... 4
Table 2.2 Sign in entry description ...................................................................................................... 5
Table 2.3 Sign in entry description ...................................................................................................... 5
Table 2.4 Sign In Error Response Descriptions..................................................................................5
Table 2.5 Agent-In Error Response Descriptions ............................................................................... 7
Table 2.6 Multiple Areas Response Descriptions............................................................................... 8
Table 2.7 Display Area Response Descriptions..................................................................................9
Table 2.8 Paging Command Descriptions .........................................................................................10
Table 2.8 Paging Command Descriptions .........................................................................................10
Table 2.9 Encode/Decode Benefits .................................................................................................... 11
Table 3.1 Check In Flight List Display Options to Limit Size of Display ........................................ 17
Table 3.2 Check In Flight List Display Options to used with Airline or ALL Entries.....................18
Table 3.3 CFL Display Field Descriptions.......................................................................................... 20
Table 3.4 Check In Equipment/Type Errors......................................................................................21
Table 4.1 Flight Data Display Field Descriptions (Master Flight) .................................................... 23
Table 4.2 Flight Data Display Field Descriptions (Active Flight).....................................................24
Table 5.1 Seat Map Viewing ................................................................................................................ 28
Table 5.2 Seat Map Viewing (Aisle) .................................................................................................... 28
Table 5.3 Seat Map Viewing (Special Usage Descriptors) ...............................................................29
Table 5.4 Seat Map Request Descriptions......................................................................................... 30
Table 6.1 Passenger Survey Display Response Explanation (Row 1)............................................ 34
Table 6.2 Passenger Survey Display Status Indicators ...................................................................34
Table 6.3 Passenger Survey Display Response Explanation (Row 2)............................................ 35
Table 6.4 Passenger Survey Display Response Explanation (Row 3)............................................ 35
Table 6.5 Passenger Survey Display Response Explanation (Row 4)............................................ 36
Table 6.6 Passenger Survey Display Response Explanation (Row 6)............................................ 36
Table 6.7 Passenger Survey Display Response Explanation (Row 7)............................................ 37
Table 6.8 Passenger Survey Display Response Explanation (Row 8)............................................ 37
Table 6.9 Passenger Survey Display Response Explanation (Row 10)..........................................37
Table 6.10 Passenger Survey Display Response Explanation (Row 11)........................................37
Table 6.11 Passenger Survey Display Response Explanation (Row 12)........................................38
SITA Departure Control Services Check In Agent Guide
List of Tables
29 August 2008 Revision 7.2
Page xi
SITA 2008 All Rights Reserved
Table 6.12 Passenger Survey Display for Code share Flight with Multiple Partners.................... 39
Table 6.13 Passenger Survey Display for Code share Flight with Marketing Partner Only ......... 40
Table 7.1 Booked/Checked In Response Description ......................................................................44
Table 7.2 Booked/Checked In Display Code Descriptions ..............................................................47
Table 7.3 Passenger Display Request Descriptions ........................................................................48
Table 7.4 Response to Standby Description .....................................................................................50
Table 7.5 Need Notification Example Descriptions ..........................................................................51
Table 7.6 Standby Example Descriptions.......................................................................................... 51
Table 7.7 Passenger Record Code Descriptions ..............................................................................54
Table 8.1 Passenger Handling Transactions.....................................................................................59
Table 8.2 Gender Required Flight Titles ............................................................................................ 62
Table 8.3 Check In SSR and Information Codes ...............................................................................65
Table 8.5 Acceptable Travel Document Types..................................................................................80
Table 8.6 DOCS Entry Edits ................................................................................................................ 81
Table 8.7 DOCA Entry Edits ................................................................................................................ 85
Table 8.8 DOCO Entry Edits ................................................................................................................ 88
Table 8.9 Error Responses for UN Paxlist ......................................................................................... 93
Table 8.10 Passport Information at Check In Error Responses ...................................................... 94
Table 8.11 Passenger Update at Check In Error Responses...........................................................95
Table 8.12 Delete PSPT Remark Error Responses ...........................................................................96
Table 8.13 APP Query Responses....................................................................................................105
Table 8.14 ITCI Valid Seat Request Codes ......................................................................................128
Table 8.15 Valid Entries for a Boarding Card Re-issue..................................................................141
Table 8.16 Bag Tag Delete Error Responses...................................................................................159
Table 8.17 Bag Tag Number Explanation ........................................................................................160
Table 8.18 Baggage Action List Options (CITY Options)...............................................................161
Table 8.19 Baggage Action List Options (Address Options).........................................................161
Revision History
Revision
Date
Changes
7.0.1
7.0.2
01 Apr 2008
7.0.3
22 Apr 2008
7.1
30 Apr 2008
Customer release.
7.1.1
10 Jul 2008
7.1.2
08 Aug 2008
7.1.3
08 Aug 2008
7.2
29 Aug 2008
Customer release.
Page i
SITA 2008 All Rights Reserved
1. Introduction
1.1. General Information
This training manual covers all the main SDCS check-in entries required for a check-in agent to carry
out their normal duties. For more advanced and control transactions please refer to the Check-in
Agent Supervisor User Guide manual.
Add any special passenger information to a passenger's record either before, during, or after
check-in.
Have the confidence to give the best possible passenger service to the passenger as you check-in,
and supplement it with any specific seat or special passenger handling requests.
Page 1
SITA 2008 All Rights Reserved
2. System Functions
2.1. Agent Control
Access to the SITA Departure Control Services system (the System) is by work stations and controlled
by three verification methods.
1. System-stored Workstation and agent information files.
2. A formal sign-in procedure.
3. User groups or Security Tables used to classify transactions.
Usually each staff is assigned one User Group appropriate for their daily work assignments. Staff may
be assigned more than one User Group to perform different tasks or duties. When you sign into a
Workstation and make an entry, the User Group authority is verified on each transaction.
User Groups / Security Tables:
Permit you to perform additional duties and is included as part of your sign-in entry.
2.1.1
Workstation Information
Workstations are classified as either protected or unprotected. Protected workstations require the
inclusion of a personal account number and check letter during sign-in, whereas unprotected work
stations do not.
A workstation can be used by one staff or shared by up to five because it has five work areas (A, B, C,
D, E). Switching between work areas is possible. For example an agent may move from work area A
to D and then back to A without losing any information originally displayed in area A. Only one work
area may be physically in use, (active), at a time.
System control and security is provided by a formal sign-in code. To maintain system integrity, a
series of security checks are routinely performed during each sign-in.
Automatic system checks on the Workstation:
Is the workstation set up for a specific application only, for example, Ticketing?
Page 3
SITA 2008 All Rights Reserved
Agent Information
2.1.2
When an agent begins the sign-in entry, the system performs a series of security checks. The system
checks the information stored in the agent files and access is either granted or denied. Agent files
store all related agent information and the system uses this information to validate an agent's attempt
to sign-in. Agent files are built during the pre-implementation phase of SDCS. Usually the User File
Maintenance" group will coordinate the creation of these files.
Automatic system checks on the agent record are:
Personal Account Number (Security Code). Validates account number against agent number.
User Group(s). Determines the transactions that are valid for the agent.
Agent Sign-In
2.1.3
Sign-In establishes the relationship between an agent, the workstation and the system. A successful
Sign-In is the result of the entry data matching the stored data for both the workstation and the agent.
Entry:
SI:Agent File Number/Agent User Group Sign-in
SI:44/124/ATL501
(Unprotected sign-in)
Entry
Description
SI
The Function Designator for Sign-In is SI: (the colon ' : ' is optional). The SI is
always the first part of the sign-in entry.
44
Agent file number that tells the system who you are and what User Groups you may
use.
AGENT
SIGN-IN
Entry
Description
SI
Function Designator.
Agent
Number
Entry
Description
SI
44
Description
PROT SET
CUSTOMER
NUMBER
Sign in entry/Customer Number in your agent file does not match the Customer
Number used in your sign in entry.
NO RECORD
No record of the agent number you have used in your sign in entry. You
probably have made a typing error.
USER GRP
User Group included with your sign in entry does not match the USER Group in
your agent file.
CITY
City included in your sign in entry is not allowed by the validation controls in your
agent record or the CRT's CONLNK record.
OFFICE
Office included in your sign in entry is not allowed by the validation controls in
your agent record or the CRT's CONLNK record.
FUNCTION
The Function Code received by the System was not intelligible. This can be due
to a typing error or because of interference and static on the circuit connection
from your CRT to the system. If your entry is correct and this continues to occur
you must report this as a communications problem to your local SITA office.
Page 5
SITA 2008 All Rights Reserved
2.1.4
The Agent-Out entry allows you to temporarily release control of the CRT to another agent or to
inactivate control of the screen for a short period of time, for example, to go for a break. You may also
want to go to another screen for information without having to erase the information on your original
screen. The information left on your screen is maintained in the area where you were signed in and is
available to you once you enter the Agent - In entry.
Entry:
AO
Response: Agent C - OUT or Letter of work area leaving AGENT-IN
Error Response:
SI
Indicates you are attempting to enter an Agent Out before signing in. The
Agent-in Entry re-establishes control over a CRT after an Agent-Out Entry
was entered and accepted. If the CRT screen is being shared, the Agent-In
entry performs an Agent-Out for the agent currently in control of the CRT.
The Agent-In entry allows you to return to an area of the CRT previously
being worked and the transaction last being worked.
SYSTEM
PSA
ONLINE
Error Responses
Response
Description
FORMAT
PROT SET
SI
Page 7
SITA 2008 All Rights Reserved
2.1.5
The Sign-Out (SO) entry ends your association with the current work area. If you are associated with
more than one work area only the current work area is signed out. You are then required to Agent-In
to your next work area before you could continue your sign out process.
If a CRT is left inactive for more than the number of minutes defined in User parameters, the CRT is
signed out. All incomplete transactions are ignored. All work areas must be signed out before leaving
the office.
Entry:
SO
Response:
ATL501
44 signed
out
ATL501
44
44
44
1347
1737
Response
SIGNED
124
129
OUT B
ATL501
ATL501
Description
ATL501
City/Office.
44
Agent Number.
44
Agent Number.
1602
124
User Group.
ATL501
City/Office.
2.1.6
The Display Area function provides basic information about the current status of the various
workstation areas. The display shows which areas staff is signed-in and those available. The
response to the display also gives the Position Identifier (PID) number of the CRT and the hardcopy
printer device associated with the CRT.
Entry:
DA
Response:
A
AVAIL
B*
44
1222
124
C
AVAIL
D
106 1230
130
E
44
1223
124
PID = 735 HARDCOPY
SYSTEM ON-LINE
ATL501
ATL501
ATL501
= 136
Description
A, B* 1, C, D, E
Agent Work Areas - Areas B, D, E Controls Computer A and C are Available for Sign-In. The agent is signed into B.
44, 106, 44
124, 130,124
ATL
City Code.
501
Office Code.
PID = 735
HARDCOPY = 136
SYSTEM ON-LINE
Page 9
SITA 2008 All Rights Reserved
2.2. Paging
The paging system allows you to move within a display, when the display is more than one page, or
between displays using specific paging commands. Paging commands are easy to use.
Commands
Definition
Description
PF: or FP:
PB: or LP:
PN: or NP:
PL:
Page Last
PG:
Page by Line
Clear Page
PG:+5 PG:-10
CP:
Description
Definition
PC:
Print Current
PT:
Print Total
Description
Airline
Name, code, IATA controlled code duplication and airline code share information.
City
Name, code, airports, heliports, state/province name and code, nation name and
code, local time and date, time difference from Greenwich Mean Time (GMT),
daylight savings observance period, and daylight savings time difference for the
Encode/Decode function helps the staff obtain codes and names for:
Cities
Airports
Airlines
Countries
Currencies
Encode/Decode gathers the information and displays it in a simple format.
Airport
Name and code, city code, state/province name and code, nation name and code,
local time and date, time difference from GMT, daylight savings observance period
and daylight savings time difference from GMT.
Country
Name, country code, and currency code for over 180 countries.
1. Entry: Encode the "Airline" Air Europa (this entry converts an airline name to code).
EX:A/AIREUROPA
Response:
EX:A/AIREUROPA
UX
* AIR EUROPA LINEAS AEREAS,S.A
Page 11
SITA 2008 All Rights Reserved
2. Entry: Encode the "City" Madrid (this entry converts a city name to three letter code).
EX:C/MADRID
Response:
EX:C/MADRID
MAD
MADRID, SPAIN
1856/23MAR
MADRID, SPAIN
1857/23MAR
GMT +01.0 DST EFF 0200 26MAR06-29OCT06 0200 DGMT +02.0
0200 25MAR07-28OCT07 0200
END
4. Entry: Encode the "Nation" Seychelles (this entry converts a country name to ISO country code and
currency code).
EX:N/SEYCHELLES
Response:
EX:N/SEYCHELLES
SC
SEYCHELLES, REPUBLIC OF
SCR
In this example the ISO Country code is (SC) and the ISO Currency code is (SCR).
2.5.2
1. Entry: Decode the "Airline" code UX (this entry decodes an airlines two letter code).
DX:A/UX
Response:
DX:A/UX
UX
*
The asterisk (*) indicates Air Europa shares the operation of some flights.
To see what carriers share operations with UX enter the following entry:
2. Entry:
DX:AF/UX
(This entry shows code share agreement flights).
Response:
DX:AF/UX
UX
* AIR EUROPA LINEAS AEREAS,S.A
* ADDR CTRA ARENAL-LLUCMAJOR KM21.5 POLIGONO SON NOGUERA
* ADR2 07620 LLUCMAJOR, SPAIN
* TEXT CAT. I - PRIMARY CODE HOLDER
* IATA 996
SHARE
UX 017
CO 063 - CONTINENTAL AIRLINES INC.
UX 018
CO 062 - CONTINENTAL AIRLINES INC.
UX 3001-3004 AF
- AIR FRANCE
UX 3011-3018 AF
- AIR FRANCE
UX 3021-3023 AF
- AIR FRANCE
UX 3024 CDG 15MAR06-25MAR06 X7
AF 5578 - AIR FRANCE
UX 3024 CDG 27MAR06-28OCT06 X7
AF
- AIR FRANCE
UX 3025-3026 AF
- AIR FRANCE
UX 3031-3032 AF
- AIR FRANCE
UX 3036
AF 1476 - AIR FRANCE
UX 3037
AF 1477 - AIR FRANCE
UX 3038
AF 1030 - AIR FRANCE
UX 3039
AF 1031 - AIR FRANCE
UX 3041-3042 AF
- AIR FRANCE
UX 3051
CU 471 - CUBANA DE AVIACION
UX 3052
CU 470 - CUBANA DE AVIACION
Note: Both the Airline's address and IATA accounting code are shown.
3. Entry: Decode the "City" code MAD (this entry converts the three-letter city code into the name of a
city).
DX:C/MAD
Response:
DX:C/MAD
MAD
MADRID, SPAIN
1903/23MAR
Page 13
SITA 2008 All Rights Reserved
4. Entry: Decode the "Nation" code SC (this entry converts the two letter ISO code of a country to the
name of the country).
DX:N/SC
Response:
DX:N/SC
SC
SEYCHELLES, REPUBLIC OF
2.5.3
SCR
1. Entry: Calculate the present time between LLW - Lilongwe and ADD - Addis Ababa.
TCC:LLWADD
Response:
TCC:LLWADD
LLW.... 1635/23DEC
GMT +02.0
+01.0 HOURS DIFFERENCE
ADD.... 1735/23DEC
GMT +03.0
DISTANCE 1623 M
2612 K
Time Conversion
2. Entry: Calculate the time in LLW for today if the current time in ATL is 1800 GMT.
TCC:ATL 1800/. LLW
TCC:ATL1800/23DECLLW
Response:
TCC:ATL1800/. LLW
ATL.... 1800/23DEC
GMT -05.0
+07.0 HOURS DIFFERENCE
LLW.... 0100/24DEC
GMT +02.0
DISTANCE 8354 M 13445 K
Last Update
FUNCTION-CODES/FDC-FLT-DATA-CTL/FDD/FDD 2/10/532/1
Function: FDD:
Application: FDC
Description: FDD: is used to display flight schedule information
for all flights built by data load.
Restriction:
22 May 00
The first page provides details of the application and use of the transaction and the second or
subsequent pages for examples may be displayed by placing the cursor after the PN (page next) and
pressing the transmit key. The next page will appear.
HELP:/PN
= Transmit after the PN
Response of Second Page
HELP:/PN
Last Update
22 May
00
Entry:
FDD:HA700/05AUG
Explanation of The Entry:
FDD:
= (M) Function Code
HA700 = (M) Airline/Flight Number
05AUG = (M) Date
** END **
Page 15
SITA 2008 All Rights Reserved
2. Entry:
PA?
Response:
HELP:/PN
Last Update
22 May 00
FUNCTION-CODES/CKI-CHECK-IN/PA/PA 2/4/484/1
Function: PA:
Application: CKI
+
HELP FACILITY
Description: PA: (Passenger Acceptance) is used to 1) accept or
place a passenger on standby when they check-in,
2) recheck passengers if they haven't checked-in
on the first flight or 3) reserve seats or add
items for not present, not checked-in passengers.
Restriction: 1) After initial close, PA: can only be done at the gate.
2) After final close, PA: is restricted to rechecking passengers at the
gate.
Note: It is optional for two-letter function codes to include the colon (:) (for example, PA:? or PA?) but
the colon is mandatory for three letter designators.
1
CFL:XS/./DACLHR/S
CFL:XS/./DAC
The airport entered in the CFL transaction can be anywhere on a flight route, including the destination.
If no airport is input, the system defaults to the airport shown in the agents sign in (VDU airport).
When a city pair (segment) is input, both cities must be on the flight route for the flight to display.
It is possible just to enter CFL: as the system defaults to the Host Airline, today's date, and the airport
of the CRT sign in (VDU airport).
Formats
There are two different CFL response formats.
1. The /S option displays flights with all available segment information.
2. Omitting the /S option displays a shorter format having flight numbers only.
Options
Options exist to limit the size of a display and return only needed information.
Option
Description
All available SEGMENT information and determines the format of the display.
Table 3.1 Check In Flight List Display Options to Limit Size of Display
The CFL transaction can be entered for an airline or all airlines in the Host's SITA Departure Control
Service. All airlines are specified by a code of ALL instead of an airline code. Where the airline code
is omitted, the output is for the host airline.
When a city, city pair (segment) or the following options are entered in a transaction the airline or the
designator ALL must be entered.
ALLList of all Airlines and flights handled by the Host carrier.
SITA Departure Control Services Check In Agent Guide
Daily Flight List Display
29 August 2008 Revision 7.2
Page 17
SITA 2008 All Rights Reserved
Entry:
CFL:AIRLINE/CITY/ OPTION
CFL:ALL/OPTION
Example:
CFL:XS/MIA/I
CFL:ALL/CN
Option
Description
CN
CL
DI
FD
II
MB
NC
NT
CL
DI
Table 3.2 Check In Flight List Display Options to used with Airline or ALL Entries
Note: It is possible to request more than one option at the same time but the transaction will be
rejected if the requested options conflict. For instance you cannot request C with O or I with N.
1 CFL Examples
Response to CFL:O (List of all flights open for check-in)
FLIGHT RECORD LISTINGS: XS ** SITA AIRLINE************************
XS259
XS267 XS301
XS456
XS472 XS488 XS490 XS499 XS501 XS544
XS636
XS677 XS685 XS704 XS723 XS737 XS782
XS810
XS820 XS830 XS866 XS923 XS945 XS967
XS1001
XS1007 XS9999
04JUN
** SITA
*********************************
Response to CFL:airline/CN (List for all cancelled flights needs airline or ALL)
CFL:XS/CN
XS090
XS200
XS340
Response To CFL:S Entry Where AAA is Default City
CFL:S
FLIGHT RECORD LISTINGS: XS ** SITA AIRLINES *********** 15NOV
XS100 ARRIVES DEPARTS BOARDS STAT POS GATE CKD
EQUIP
AAA
0700
0630
CC
67
23
C10M43
737/A
ALP
0910
XS160 ARRIVES DEPARTS BOARDS STAT POS GATE CKD
EQUIP
AAA
0700
0630
CC
45
27
C8M43
734/A
FRA
0915
XS778
ARRIVES DEPARTS BOARDS STAT POS GATE BKD
EQUIP
AAA
0700
0630
OPEN GATE ???? C0Y50
340/B
ATL
0900
1020
0940
OPEN GATE ???? C0Y145
340/A
SJU
1310
XS520
ARRIVES DEPARTS BOARDS STAT POS GATE CKD
EQUIP
AAA
0730
0700
CC
74
28
C4M18
CRJ/CRJI
DOH
0900
XS930 ARRIVES DEPARTS BOARDS STAT POS GATE CKD
EQUIP
AAA
0730
0700
CC
78
21
C2M12
734/AGD
MUC
0850
XS490 ARRIVES DEPARTS BOARDS STAT POS GATE BKD
EQUIP
AAA
1130
1100
NINT GATE ????
762/A
JFK
2125
+
TYPE
NAM
TYPE
NAM
TYPE
NAM
NAM
TYPE
NAM
TYPE
NAM
TYPE
NAM
Note: The flights are displayed in TIME order based on the default city or origin city of a segment. It
is also possible to display the list from a particular input time (Example: CFL:S/1800).
An X before the City Code indicates that the flight is cancelled.
DEPARTS
BOARDS
STAT
POS
GATES
BKD
EQUIP
0010
2340
NINT
GATE
B17
F06Y168
767/A
10
Page 19
SITA 2008 All Rights Reserved
Explanation:
Field
Description
CKDNumber of passengers checked in shown once the flight has been released.
BKDNumber of passengers booked is shown while the flight is open.
10
11
Type of check-in out of this airport. It is possible to display the following types:
NAMPassenger name check-in from a PNL.
NUMNumeric check-in.
PNMPartial name check-in for passengers with special requests only.
NONNon SITA DCS check-in. (Manual check-in)
TCLTechnical landing, no check-in allowed.
When a schedule is built, the default type of Check-In is NAM. If the Control Agent does not change
the NAM to NON for non-mechanized stations the PNL will not process because the system is waiting
on the additional PNLs from the reservation system. The CFL: display allows you to catch errors early.
Error
EQUIP
Correct
TYPE
EQUIP
TYPE
TU5/C3
NAM
TU5/C3
NAM
TU5/C3
NAM
TU5/C3
NON
TU5/C3
NAM
TU5/C3
NON
04JUN
737/73S
737/73S
NAM
NAM
EQUIP
737/DF
TYPE
NAM
EQUIP
DH8/C
TYPE
NAM
EQUIP
DH8/C
TYPE
NAM
EQUIP
DH8/C
TYPE
NAM
EQUIP
DH8/C
TYPE
NAM
EQUIP
DH8/C
DH8/C
TYPE
NAM
NAM +
No Segment Information
The CFL:S entry may display flight numbers with the response '**NO SEGMENT INFO**'. When this
occurs, there are two possible reasons.
1. The flight has been created with a "D" option and the system will not give the segment information
until the flight is initialized.
2. When the flights are created with a "K" option, the segment should display the segment
information. When it does not, check to see if everything is correct with the seat map and
configuration.
Page 21
SITA 2008 All Rights Reserved
** SITA
*********************************
**
**
**
**
A flight schedule may be activated for five days - today plus four consecutive future days. Activation is
part of a nightly maintenance program run by the system. In the example below, a Flight Period
Display shows a schedule is built for a flight from 23 June on till infinity. This transaction is used only
by a DCS Database Specialist but shows that the flight schedule has not been activated for XS206.
Data Base Restricted Entry Shows the Flight Is Not Activated
FPD:206
FPD:XS 0206
->> MASTER PERIODS:
FDD:XS 0206 /23JUN98/MF
->> ACTIVE DATES:
00XXX00 D
If a Check-In Agent enters the transaction to display a seat map the flight is activated normally if the
schedule conflict is corrected. The flight will then appear correctly on the CFL display.
routing
ATL
JFK
- 23MAR05
156
T-32
--MASTER-737/A
Field
Description
XS587
Flight Number.
11FEB05 23MAR05
Date Range.
156
Flight frequency:
There are various ways of specifying the frequency as follows:
D - Daily (everyday of the week)
1 - Monday (2 = Tuesday, 3 = Wednesday, 4 = Thursday,
5 = Friday, 6 = Saturday, 7 = Sunday) This flight will operate on Monday, Friday and
Saturday.
ATL
JFK
Next or Final Station (with arrival time of 1635). Copied from schedule.
T-32
CND Table Number for aircraft configuration. Copied from schedule. Can also show
RBD configuration if the schedule was created by SITA Reservations.
737/A
Page 23
SITA 2008 All Rights Reserved
XS587 14FEB06
ADJ 1510
ETA 1735
--ACTIVE-1/00 LATE
1/00 LATE
T-32
737/A
R:G-LMWP
Field
Description
1/00 LATE
R:G-LMWP
IRREGULAR OPERATION
DETAILS
Location and reason for schedule adjustment. Use the FIR transaction to enter the delay codes.
A Supervisor or Operations Agent will update the FDD
information.
SUPPLEMENTAL INFORMATION
X67
--ACTIVE-20
71
T-518
73G/73GBBR:HALOR
Explanation:
***CODE SHARE***SN5144
Note: Code share flights now allow up to nine marketing partners between SDCS users and partners.
Page 25
SITA 2008 All Rights Reserved
1
SE:XS835/17JUN
SE:XS835Y
SE:XS835/ATLMIA
SE:XS835/17JUN Y ATLMIA
Response to SE:835/. Transaction
SE:XS835/17JUN06/ATLMIA
737/A
SE:XS835/17JUN06/MIASJU
F
Y
1 2
3
RF T *
F
F
.
RE T *
E
E
.
RD * V D
D
.
R
= S
=
L
LC
LB
LA
F
:
.
+
.
1
S
*
*
V
2
C
B
A
C
B
A
Y
=
H
R
R
3
4
*
*
*
=
5
T
*
T
=
=
*
*
*
4
=
*
T
T
5
[
6
*
*
*
=
[
7
=
*
*
*
6
[
=
L
L
L
L
=
7
[
[
8
*
*
*
=
[
9
P
P
*
=
1
0
*
*
*
=
[
1
T
T
*
=
[
2
*
*
*
=
=
*
*
*
8
[
=
*
*
*
9
[
=
*
*
P
0
1
=
*
.
.
1
[
=
*
*
T
2
[
3
.
*
.
S
4
.
.
*
S
5
.
*
*
S
6
*
*
*
S
7
*
*
*
S
8
/
/
/
S
S
.
*
T
3
S
*
*
.
4
S
*
*
*
5
S
.
R
R
6
S
R
R
*
7
S
/
/
/
8
FR
ER
DR
R
L
CL
BL
AL
Note: When there is an aircraft change in the route, the default segment is displayed first. The
second segment allows the seat map display for the second aircraft on the flight.
Page 27
SITA 2008 All Rights Reserved
Code
Definition
FY
Classes of service
+/-
Indicates the seat map has additional rows, press Page Up and Page Down to scroll through
the additional sections of the seat map.
Definition
Indicates AISLE.
Indicates that an infant is seated on that side of the row on the aircraft.
SMOKING row.
Description
Handicap seat.
Infant seat.
SITA Departure Control Services Check In Agent Guide
Seat Map Display
Page 28
SITA 2008 All Rights Reserved
SUD
Description
Seat automatically reserved for passenger by RES from PNL or ASR on ADL after flight
initialization.
Occupied by Transit passenger (Manual check-in Up line Station only - otherwise shows as a
'.' for Thru-checked-in passengers from an automated Up line Station).
Page 29
SITA 2008 All Rights Reserved
At check-in it is possible for agents to request specific area seating. The letter R notifies the system a
Request for a specific area on the aircraft is being made.
Description
RS
Smoking seat
RN
RW
Window seat
RSW
REW
RI
Aisle seat
RSI
RF
Forward seat
RA
Aft seat
320/R
FR
ER
DR
R
L
CL
BL
AL
Note: Code share flights can accept up to nine marketing partners between SDCS users and
partners.
Note: Seats may have multiple Special Usage Descriptors (SUDs) assigned. The seat map displays
the most restrictive SUD assigned to the seat. Seats with multiple SUDs will display the less restrictive
SUD when a more restrictive SUD is removed from a seat.
Individual Passenger Record Display (PDD), Section 7. The flight check-in control messages are of
two types: limit warnings and limit advice. The warnings are sent when a capacity is approached. The
advice is sent when a capacity is reached. The SDCS Database User Guide Section 9.4 describes
warning message addresses.
Page 31
SITA 2008 All Rights Reserved
aircraft type
gate number
boarding time
passenger configuration
capacity
Booking details.
The SDD screen controls the acceptance of GO-SHOW passengers and ID passengers. The display
also provides a total of passengers checked-in for a flight, and by individual segment for multi-sector
flights.
The entry is:
SDD:FLIGHT NUMBER/DATE
1
SDD:XS835/.
Note: Class code is not entered.
Response to SDD:XS835/.
1. SDD: XS835/23SEP ATL/1
OP/NAM
2. CWT015000 UWT014885 CAW014406 UAW013281 WTN1 KG TCI
3. 737/a
GTD/G17 POS/GATE BDT1730 SD1800 ED1830
AK07125 CD09127
4. ARN/A1234-AA
CNF/F12Y94 CAP/F12Y94 AV/F12Y81 PADC/C0M0
5. FLIGHT DELAY DUE TO LATE CATERING
6. *ATLMIA R0004/0069 C0000/013
B0013 UM000 WCH00 I00
7.
SB0000/003 B0003
STCR00 PETC00 AVIH00 J00
8.
SA0000/004
EXST00/00 XCR00/00 DHC00/00
9. *ONLY ALLOW ONE PIECE OF HANDLUGGAGE PER PERSON ONBOARD*
10. SX
ATLMIA/F2
11. HL
ATLMIA/Y90
12.
GS
ID
ATL 003/015
001/005
Page 33
SITA 2008 All Rights Reserved
Explanation:
Row 1.
Entry
Explanation
SDD
XS835/.
Flight number/date.
ATL1
OP
Explanation
OG
OE
CI
CE
EC
CL
CC
PC
XX
Flight Cancelled.
NAM
Explanation
CWT
Check-in weight allowance (comes from the CSM and system calculates it using
the average passenger weight from CW).
UWT
UWT-
CAW
Load planning weight allowance (only comes across to CKI once the estimated
baggage figures are created in LDP).
Status Indicator
Explanation
UAW
UAW-
WTN1
KG
TCI
Explanation
737/A
GTD
POS
BDT
SD
ED
AK
CD
Page 35
SITA 2008 All Rights Reserved
Row 4.
Status Indicator
Explanation
ARN
CNF
CAP
AV
PADC
Explanation
ATL/MIA
Flight segment.
Checked-in passengers.
UM
WCH
Row 7.
Status Indicator
Explanation
SB
STCR
PETC
AVIH
Explanation
SA
EXST
XCR
DHC
Deadhead Crew.
Explanation
Seating restriction.
Explanation
Numeric limit by class for passenger acceptance, and only displays when set.
Page 37
SITA 2008 All Rights Reserved
Row 12.
Status Indicator
Explanation
GS
ID
Number of seats available by class for PAD (ID) passengers. If it is zero then
these passengers are put on standby at the departure station.
Description
***CODESHARE ****YY9084
ZZ2684 BB9984
Table 6.12 Passenger Survey Display for Code share Flight with Multiple Partners
Page 39
SITA 2008 All Rights Reserved
Field
Description
Table 6.13 Passenger Survey Display for Code share Flight with Marketing Partner Only
Note: Code share flights can accept up to nine marketing partners between SDCS users and
partners.
Page 41
SITA 2008 All Rights Reserved
7. Passenger Displays
7.1. Booked / Checked-In Display (PS)
Any agent can display the booked/checked-in display. Enter:
PS:FLIGHT
It is possible to enter a particular class, but this displays only those passengers booked in that specific
class.
1
PS:XS735
Response to PS:XS735
PS: XS735/08JUNATL
OP/NAM
737/106C GTD/B17 POS/GATE BTD/1930 SD2000 ED2000 SA2105 FT0105
1.
2ABOTT/LMR
A2
SN17E
M
MIA
INF
PSM
ABOTT/GMRS
A2
SN17F
M
MIA
RES
PSPT
2.
1ADAM/GMST+
BN002
SN2A
C
MIA
UM
RES
3.
2ALLEN/TMR
B2
M
MIA
PSPT TKNE
ALLEN/LMRS
B2
M
MIA
PSPT TKNE
4.
4ANDREWS/DMR
C4
M
MIA
O
MKT
ANDREWS/RMRS
C4
M
MIA
O
MKT
ANDREWS/YMIS+
C4
M
MIA
O
MKT
ANDREWS/RMST+
C4
M
MIA
O
MKT
5.
1BAILEY/DAVI+
SN2D
C
MIA
RES
BLND
6.
1BARNES/EMR
SN1C
C
MIA
RES
WCHR
7.
1BAXTER/TMR
D2
M
MIA
PSPT TKNA
8.
2BROOMFIELD/MR
E2
C
MIA
MKT
TKNM
BROOMFIELD/MRS
E2
C
MIA
O
PSPT
9.
1BRUNSWICK/TMIS+
BN001
SN14D
M
MIA
UM
RES
10. 2BURNETT/FMRS
F2
M
MIA
I
PSPT
BURNETT/SMRS
F2
M
MIA
I
PSPT
11. 1CHAPPELL/MARY
D2
M
MIA
MKT
12. 1COLEMAN/OMR
SB035
M
MIA
PSM
ID SA
13. 1COOPER/DMR
C
MIA
14. 2DIXON/PMRS
G2
M
MIA
PSM
PETC
DIXON/AMIS+
G2
M
MIA
O
15. 1GIBSON/JMRS
K3 BN006
SN12A
M
MIA
MSG
+
1
2
3
4
5
6
7
8
9
10
Note: Passengers booked together with the same surname are not assigned a group code unless
there are passengers with different surnames in the same booking, e.g., 2ABOTT is not assigned A2.
Page 43
SITA 2008 All Rights Reserved
Field
Explanation
Passenger's name. If the surname is more than 12 characters or the initials and title are
more than four characters the system displays a + indicating that the full name or initials and
title has not been displayed. It is possible to see the full name with a passenger record
display (PDD).
Seat number.
Class of booking.
Destination.
Items.
10
The + denotes that there are more pages to the display. Enter PN (NP) where the SOE ()
is displayed to move to the next page.
Code
Description
ACC
Accepted Passengers.
ACS
ADSR
Adjoining Seats.
ADV
AEC
AECX
ASR
AVIH
BAG
Page 44
SITA 2008 All Rights Reserved
Code
Description
BLND
Blind Passenger.
BSCT
Bassinet.
CHD
Child.
COUR
CRS
DBI
DBV
DEAF
Deaf Passengers.
DEL
Deleted Passengers.
DNG
Downgraded Passengers.
EXBG
EXST
Extra Seats.
FQTV
GRI(+REF)
GRP
Groups.
I(FLT NBR)
ID
INF
ITCI
ITCU
ITCX
JMP
MAAS
MEDA
Medical Case.
MKT
MSG
MUS
NACC
NAM
NREC
NOREC Passenger.
NRS
Page 45
SITA 2008 All Rights Reserved
Code
Description
O (FLT NBR)
OSR
OTHS
Other Information.
OVR
PAD
PAD Passengers.
PCTC
PDNG
PETC
PSM
PUPG
RES
SA
SBY
Standby Passengers.
SEMN
Seaman.
SPML
STCR
Stretcher Passengers.
TKNA
TKNE
TKNM
TOP
UGPA
UM
Unaccompanied Minors.
UPG
Upgraded Passengers.
URES
WCH
Wheelchair Passengers.
WL
Waitlisted Passengers.
XBAG
XRES
N Placed before any Other Item Except I, O, Z gives a List Excluding that
Particular Item.
SITA Departure Control Services Check In Agent Guide
Passenger Displays
Page 46
SITA 2008 All Rights Reserved
Code
Description
NACC
@Y (COMPARTMENT)
Page 47
SITA 2008 All Rights Reserved
Description
PS:XS493
PS:XS493/.C
PS:XS493/.,UM
PS:XS493/.,ACC
PS:XS493/.,MSG
PS:XS493/.,WCH
PS:XS493/.,GRP
PS:XS493/.,CHD,INF
PS:XS493/.C,NAMP
PS:XS493/.,TKNE
PS:XS493/.,O
PS:XS493/.,I
PS:XS493/.,MKT
PS:XS493/.,PSPT
PS:XS493/.@Y
PS:XS493/.@C
PS:XS493/.,NAMWARD;
NAMGILL
1
SB:XS735/.
This list can consist of the following categories of passengers:
7.2.2
Need Notification
These are passengers who may or may have not checked-in but some change has been made to their
passenger record and they need to be notified. For example, a passenger not booked on the flight
may check-in and the system puts him on the standby list. Later due to some change on the flight
some seats become available and the system may automatically accept him. As the passenger may
not be present at the check-in desk at that moment, the system places the name on to the notification
list to remind the agents that this passenger needs to be notified that he has now been accepted on
the flight. Names are listed alphabetically.
7.2.3
Transit PAD
This is a list of all PAD passengers accepted up line on TRANSIT flights. Names are listed in Offload
Priority order with first to be offloaded passengers listed first and last to be offloaded listed last.
7.2.4
Local PAD
This is a list of all accepted PAD passengers at this station. Names are listed in Offload Priority order.
With first to be offloaded passengers listed first and last to be offloaded listed last.
7.2.5
Standby
This is a list of all passengers on STANDBY at this station. Names are listed in Onload Priority order.
With first to be onloaded listed first, and last to be onloaded at the bottom.
Response to SB:XS735.
SB: XS735/08JUNATL
OP/NAM
737/106C
GTD/B17
POS/GATE
FT0105
AV C4M63
PAD C0M0
NEED NOTIFICATION
1. 2BLAKE/MMR
B2
BN002
BLAKE/TMS
B2
BN003
2. 1KELLY/LMRS
BN019
LOCAL PAD
3. 1PORTER/GMRS
BN045
4. 1EDWARDS/YMR
BN023
STANDBY
5. 1CARLTON/N
SB025
6. 3FERGUSON/SMR K3
SB035
FERGUSON/YMRS K3
SB036
FERGUSON/LMIS+K3
SB037
7. 1BOOTH/AMR
SB019
1. 2.
3.
4.
5.
BTD/1930
SD2000
ED2000
SA2105
SN1A
SN1C
SN23D
C
C
M
MIA
MIA
MIA
ACC/SB007
ACC/SB008
PU/NP
SN3C
SN4A
C
C
MIA
MIA
P08 IDN1/MAR71
P05 IDS1/AUG69
PAD
PAD
PAD
PAD
LMTS
6.
M
M
M
M
M
7.
MIA
MIA
MIA
MIA
MIA
8.
P20
P50
P50
P50
P90
9.
IDS2/MAY71
IDN2/APR79
IDN2/APR79
IDN2/APR79
IDR2/SEP85
Explanation:
Field
Explanation
Page 49
SITA 2008 All Rights Reserved
Field
Explanation
Passenger's name. If the surname is more than 12 characters or the initials and title are more
than four-characters the system displays a + indicating that the full name or initials and title
have not been displayed. To see the full name with a passenger record display (enter
PDD:5).
Class of check-in.
Destination.
It is possible to display information from the following sections, Table 7.4 Response to
Standby Description
Need Notification (Section 0) and Table 7.5 Need Notification Example Descriptions
Standby (Section 0).
Need Notification
Example
Explanation
ACC/SB007
Accepted from standby list with passenger holding this standby number.
DEL/BN038
DEL/SB025
PA/NP
Page 50
SITA 2008 All Rights Reserved
Example
Explanation
PU/NP
Passenger record updated (perhaps new seat number) while passenger not present.
PW/NP
SBY/BN056
Passenger put on standby with boarding number being held by the passenger.
Standby
Example
Explanation
P90
Priority Number. Comes from the PZ:AIRLINE table (The higher the number, the lower
the priority).
IDN2/APR79
Time of passenger check-in and record of Agent/CRT that entered the initial transaction.
Subsequent list of time and Agent/CRT of any additional/modification entries to the passenger
record.
Note: The system lists a record of all the LOCAL times and Agents/CRT that did any entries to a
particular passenger record, and also lists whether the modification was a PU or PW etc.
The PDD transaction is normally entered after a PS or SB display using a passenger display entry
number, but it can also be entered by passenger name, seat number, boarding number, or standby
number.
The entry after a PS or SB display, is: 'PDD:ENTRY NUMBER'.
Page 51
SITA 2008 All Rights Reserved
OP/NAM
SD2000 ED2000 SA2105 FT0105
M
MIA
INF
PSM RES
M
MIA
RES
C
MIA
UM
RES
M
MIA
M
MIA
SB1014 LMTS M
MIA
URES
BTD/1930
SN17E
SN17F
SN2A
BAG1/12/0
UM10
To display a SB list:
SB:XS735/.
Response of SB:XS735/.
SB: XS735/09JUN ATL
737/106C GTD/???? POS/GATE BDT1930 SD2000 ED2000
AV C12M98
PAD C0M0
STANDBY
1. 1BRANDON/JMR
SB1014
LMTS Y MIA P3
SA2005
OP/NAM
FT2005
URES
Y LHR M1/75
Note: Code share flights can accept up to nine marketing partners between SDCS users and
partners.
The following is an example of a PDD with double oncarriage segments:
Y LUX
Y FRA
Y FRA
M1/75
Explanation
ACC
ADV
APT
Airport Tax.
ASR
***CODESHARE**** YY141
DEB
De-Boarded passenger.
DEL
Passenger deleted.
ITCI
ITCU
ITCX
NPA
OFL
OFEC
Page 53
SITA 2008 All Rights Reserved
Code
Explanation
NRS
PDN
PRC
PU
PW
RES
Reserved Seat Request from PNL and ADL shown as R on seat map.
SBY
SEA
SPC
XBC
XPD
XPR
1 Example
PDD:XS735Y,1ADAM
Note: If the class is not known, omit class, and if the number of passengers associated with name is
not known enter 1. It is not necessary to enter the full name, but the more details entered, the more
chance the system has of finding the requested name. The system either displays the record of the
passenger requested, or responds with a similar names list (a subsequent PDD transaction can use an
entry number from this response to identify the correct passenger).
B)PDD by Seat Number
The entry is:
PDD:FLIGHT NUMBER, SEAT NUMBER
SITA Departure Control Services Check In Agent Guide
Passenger Displays
Page 54
SITA 2008 All Rights Reserved
1
PDD:XS735,SN17A
C)PDD by Boarding Number
The entry is:
PDD:FLIGHT NUMBER, BOARDING NUMBER
1
PDD:XS735,BN114
D)PDD by Standby Number
The entry is:
PDD:STANDBY NUMBER
1
PDD:SB121
Note: There is no requirement to enter flight number when entering a request by standby number. A
passenger retrieval selection transaction can also be done using an entry number from a PA selection
response, because standby numbers are assigned on an airline basis and not by individual flight. This
allows standby passengers to be moved from one flight to another and keep the same number.
The PDD display entry number can also be used to identify passengers after the following transaction
entries:
PU
Passenger Update
PW
Passenger Delete
NO
Passenger Notification
BC
After any initial PDD display from a PS or SB list, it is possible to do further PDD displays without reentering the PS or SB list providing the entry number is known.
The entry is:
PDD:ENTRY NUMBER PS
1
PDD:12PS
Page 55
SITA 2008 All Rights Reserved
PDD:ENTRY NUMBER SB
1
PDD:5SB
E.) PDD by Ticket Number
PDD:FLT/DATE,TKNE/1234567890123C3
F.) PDD by Frequent Travel Number
PDD:FLT/DATE,FQTV/123456789
G.) PDD by Passport Number
PDD:FLT/DATE,PSPT/A123456
Note: The date may equal a period (.) for the current date, a minus sign () for yesterday, a plus sign
(+) for tomorrow or be in DDMMM format (e.g., 23OCT).
H.)PDD Display for a Passenger from another Station
PDD:FLIGHT/.STN,BN NUMBER
PDD:FLIGHT/.STN,SN NUMBER
PDD:FLIGHT/.STN,1PAX NAME
1
PDD:XS100, BT XS123456
PDD:XS100,0950123456
Response to PDD:XS100,BT XS123456
PDD:XS100/08JAN ATL,BTXS123456
1.
HUNT/JAMES MR BN008 SN11G
BAGTAGS ISSUED: ATL 1/9
0950123456/MIA
ACC VDT8267 AGT66/08JAN1414
MIA BAG/9/0
Note: If exactly ten numbers are not entered or the bag tag number cannot be found, the system
responds 020-PSGR ID.
7.4.1
Manual bag tags that are entered with a two- or three-letter airline code are displayed in the PDD with
the numeric airline code (with a +) rather than the letter code.
SITA Departure Control Services Check In Agent Guide
Passenger Displays
Page 56
SITA 2008 All Rights Reserved
1
PA1,1/10,B/XS123456/MIA
PDD:1
Response to PDD:01
PDD:XS170/08JAN Y ATL,1
1. GRANT/MARY
BN025
SN22A Y MIA
BAGTAGS ISSUED: ATL 1/10
0950123456+/MIA
ACC
VDT72846 AGT91/08JAN192
BAG 1/10
Page 57
SITA 2008 All Rights Reserved
Description
PA
Passenger Acceptance
PU
PW
The passenger name is required for all check-in transactions and all booked passenger names are
checked against a system-held PNL (passenger name list).
B)
The passengers are checked-in on a first come basis, and the system does not check for names
against a Passenger Name List (PNL).
C)
This is an extension of numeric check-in, in that the system only checks a PNL for passengers with
special remarks, such as wheelchair required passengers or unaccompanied minors. The other
passengers are checked-in depending on numeric limits rather than on names.
This User Guide mainly describes Name check-in. This means that for any examples shown, it is
assumed that the system does a check against a system-held PNL. Also for those Airlines that use
the BAG TAG (B) printing option, this is explained in the section on Bag Tag Issuance (B) (8.14).
Page 59
SITA 2008 All Rights Reserved
8.2.1
Check-In Procedures
1
Passenger MR.L.COOPER who is booked in C class on flight XS593 to JFK today can be checked-in
as follows:
PS:XS593C,NACC,NAMC
This gives a list of all Not Accepted Passengers with Names starting with C.
Response to PS:XS593C,NACC,NAMC
PS:XS593/08JUNCATL,NACC,NAMC
737/106C
GTD/B24
POS/GATE
1.
1CHARLES/JOHN
D2
2.
1COLLIE/TMR
3.
1COOPER/LMR
BTD/0930
SD1000
ED1000
C
JFK
C
JFK
C
JFK
SA1105
OP/NAM
FT0105
By using the correct entry number, in this case number 3, and adding some baggage details (1 piece
at 12 kgs), the entry would be:
PA:3,1/12
Response to PA:3,1/12
PA:XS593/08JUNCJFK1COOPER/LMR,1/12
AV C12M54
PAD C0M2
737/106C
GTD/B24
POS/GATE
BTD/0930
1.
COOPER/LMR
BN019
SD1000
SN07A
ED1000
*JFK*
SA1105
FT0105
Passenger is now checked-in and his boarding card issued. The check-in transaction is complete.
The check-in transaction issues a boarding pass with the following exceptions, if:
Excess baggage charges are applied the response shows the amount of excess bag charges to
be assessed with the comment BOARDING PASS PRINT INHIBITED.
API data is required and is not complete the response is BOARDING CARD INHIBITED MISSING
DOCUMENT DATA
To check-in as above and also issue bags tags, the entry would be as follows:
PA:3,1/12,B
The details of the bag tags can be seen in the passenger's PDD.
8.2.1.2 Check-in Detailed Entry
The Detailed Entry involves entering the Flight Number, Class of travel, Destination (for multi-sector
flights only), Number of passengers traveling, the Family Name plus any titles or first names, the
Gender (for GENDER required flights only), the Baggage details plus any additional information such
as special seat requests, Onward connections, PSM remarks etc.
1 Example:
1 Example:
SD1000
ED1000
SA1105
*JFK*
Check-in for a single sector flight that does not require gender
PA:XS772 Y 1MACKAY/JMR,1/15,B
Response to PA:XS772 Y 1MACKAY/JMR,1/15
PA:XS772/08JUNCMIA1MACKAY/JMR,M1,1/15,B
AV Y075
PAD Y2
727/A GTD/B24
POS/GATE
BTD/1330
SD1400
1.
MACKAY/JR BN035
SN26C
ED1300
SA1405
FT0105
Page 61
SITA 2008 All Rights Reserved
8.2.2
For GENDER required flights, the system calculates the genders of each passenger from the PNL,
based on TITLE attached to the name, using the following standards:
Title
Gender
MR, DEFAULT
M (MALE)
MRS,
F (FEMALE)
CHD (CHILD)
FEMALE
CHILD
CHD
INFANT
INF
Note: For more than one infant, the INF is followed by the total number of infants then the each name
is separated by a + (INF2DAVID+MARY or INF3JANE+IAN+JOHN). This transaction is limited to the
number of infants being equal or less than the number of adults or children at check-in.
When a passenger is checking-in, the system first looks for an EXACT name match, and if it finds it,
then the passenger is checked-in. However if the system cannot find an exact match, or if it finds
SIMILAR names, it responds with a names list, including a NOREC name, and the agent then must
identify the correct passenger.
Note: If the system responds with a name list, this list may include passengers in other classes and
also passengers already checked-in, providing their names correspond to the name entered.
1
Check-In for a Non-Gender required flight:
PA:XS593/08JUNMJFK1FLETCHER,1/12,B
Response to PA:XS593/08JUNMJFK1FLETCHER,1/12
PA:XS593/08JUNMJFK1FLETCHER,1/12,B
1.
1FLETCHER/ -NOREC PSGR
2.
1FLETCHER/GMR
3.
2FLETCHER/JMR
D2
FLETCHER/FMRS
D2
4.
1FLETCHER/PETER BN023 SN22D
M
C
C
M
JFK
JFK
JFK
JFK
Page 63
SITA 2008 All Rights Reserved
The following SSR and information codes can be input with the check-in entry:
SSR Code
Explanation
ADSR
AVIH (P/W)
BLND
Blind passenger.
BSCT (NBR)
CHD (NBR)
COUR
Courier.
DBI
DBV
DEAF
Deaf passenger.
EXST
F (NBR)
FOID
FQTV
ID
INF (NBR)
JMP
Jump-seat passenger.
M (NBR)
MSG
MUS (WT)
NAM (NBR)
PCTC
PETC (P/W)
PSM
PSPT
SEMN
SNR
SNRGRP
SPML
SSR Code
Explanation
STCR
TKNA
TKNE
TKNM
TOP
UM
URES
WCHR
WCHS
WCHC
XBP
(P/W)
Pieces/Weight required.
(NBR)
Number required.
(WT)
Weight required.
Page 65
SITA 2008 All Rights Reserved
8.2.3
Upgrade/Downgrade Passengers
Passengers can be upgraded or downgraded before or after check-in. Passenger Upgrades and
Downgrades are subject to standby limits at check-in. It is optional to indicate whether a pre-upgrade
is voluntary "/V" or involuntary "/I" following the upgrade or downgrade entry.
8.2.3.1 Pre-Upgrade / Pre-Downgrade
The entry to pre-upgrade to F class:
PU:#ENTRY NBR,PUPG F/V
1
PU:#1,PUPGF/V
The entry to pre-downgrade to Y class:
PU:#ENTRY NBR,PDNGY/I
1
PU:#1,PDNGY/I
Note: It is not possible to upgrade or downgrade a passenger during the check-in process. It can only
be done before or after check-in.
8.2.3.2 Upgrade (UPG)/Downgrade (DNG) Passengers Already Checked-In
When upgrading or downgrading a checked-in passenger, it is mandatory to indicate whether an
upgrade is voluntary "/V" or involuntary "/I" following the upgrade or downgrade entry.
The entry to downgrade a checked-in passenger to Y class:
PU:ENTRY NBR,DNGY/V
1
PU:1,DNGY/V
The entry to upgrade a checked-in passenger to F class:
PU:ENTRY NBR,UPGF/I
1
PU:1,UPGF/I
Note: There must be some GO-SHOW or ID figures set for the class being requested BEFORE the
transaction can be entered; otherwise, it is rejected with the response: MODIFICATION WOULD
CAUSE STANDBYING LMTS.
1
PW:#1,PUPG
The entry to cancel a pre-downgrade is:
PW:#ENTRY NBR,PDNG
1
PW:#1,PDNG
Note: When canceling an upgrade (or downgrade), use the PW entry and re-enter the same code that
was originally entered with the PU but this time without the class (Example if the PU entry was
PU#1,PUPGF then the PW entry is PW#1,PUPG).
Note: Passenger upgrade and downgrade limits are subject to the standby limits for check-in.
8.2.4
A passenger can be rechecked to a new flight, or a new destination on the same flight. The entry code
that identifies a recheck is being attempted is a 'Z'.
The PA transaction can recheck a passenger onto a new flight, or it can recheck a passenger to a
different destination on the same flight.
The entry from a PS list is:
PA:ENTRY NBR,Z NEW FLT CLS DEST,P/W
PA:ENTRY NBR,Z FLT NBR CLSS NEW DESTINATION,P/W
1
PA:1,Z387YBBB,1/10
Note: The Z and flight number, class, and destination details must be entered before the baggage
details otherwise the entry is rejected with the response: 015 FORMAT.
PU Entry (Passenger Update)
The PU transaction can recheck a passenger onto a new flight, or it can recheck a passenger short of
their original destination on the same flight. The PU entry does not allow the update check-in of
passengers past their original destination on the same flight.
Note: If after check-in a passenger wishes to check-in to a destination past the original destination,
then offload the passenger (PW) and enter the recheck with the PA entry. If the attempt is done with
the PU entry the response is: 441 - RECHECK FLIGHT-DESTINATION
Page 67
SITA 2008 All Rights Reserved
8.2.5
Passengers may be booked with two different segments to the same destination. An agent can select
one of the two segments at check-in.
Example: Passenger Adams is checking in with double oncarriage segments. His PDD appears as
follows:
Y JFK
Y LHR
Y LHR
M1/75
If the agent attempts to check in the passenger using PA:1,1/20,O the system responds with the
following error:
596 - DOUBLE ONCARRIAGE - SELECT CONNECTING FLIGHT
The agent needs to select which flight the passenger will travel on with the following entry:
PA:1,1/20,OXS061/04NOVYLHR
The passenger is now checked in for XS061/04NOV.
Note: A duplicate segment must be entered with an ADL.
To delete an outbound segment, enter:
PW:1,O
8.2.6
Passengers can be accepted on an overweight flight provided the URM parameters is set to do so.
Acceptance is done with a normal PA entry as follows:
PA:1,1/10,B
SA2330
FT0030
Note: Overweight parameters are controlled by the ATL Customer Support group and they should be
contacted when needed.
8.2.7
Oncarriage Check-In
If a passenger has oncarriage details in his record, the O need only be inserted if the passenger is to
be through checked-in onto his next flight (PA:ENTRY NUMBER,P/W,O). Provided through check-in
is permitted, two boarding cards will be issued. If the O is left off, he will not be through checked-in,
nor will a second boarding card be issued. If the O is left off in error, and the passenger needs to be
through checked-in, the O can be added later with the PU entry (PU:ENTRY NUMBER,O). SSR and
information codes must precede the ",O". Seat requests on the outbound flight are entered after the
",O".
Note: If a parameter is set and the outbound flight leaves before arrival of the origin flight, an error
message Check Flight Continuity will display.
The system accepts multiple onward flight connections; however, a bag tag is limited to three flights.
Any additional flights will produce additional bag tags. The entry for oncarriage baggage checks is:
PU:FLIGHT CLS DEST,P/W,B/XXX.O FLT CLS DEST,O FLT CLS DEST
Note: The final destination of the bag (B) is mandatory when automated bag tags are issued. A date
is required for the onward flights if they are not for the current date.
1
PU:XS837 Y JFK0,1/10,B/ATH,OYY937MZRH,OAZ518YFCO,OOA826YATH
To delete a bag tag with oncarriage processing, enter:
PW:FLT CLS DEST 0,P/W,B/NUMBER
Note: If bag tags have been issued or manually entered, then it is mandatory for the B/ to be
followed by the position number on the line, for example, B/1 or B/2. The 1 indicates the first tag on
line, and 2 would designate the second bag. The system also accepts the actual bag tag number.
Page 69
SITA 2008 All Rights Reserved
8.2.8
When checking in a passenger with connecting segments, the ',O' indicates the onward segment.
Depending on which segment the connection begins, the check-in entry is followed by a ,O or ,O2 or
,O3 etc.
To check in a passenger from the PS list with the next segment on a connecting flight, use the
following entry:
Note: For the Interline through check-in process, the coupon is validated in the electronic ticket
database before the check-in process continues. If the ticket is for an ITCI flight, then the partner
airline validates the coupons before the check-in process continues.
1
PA1,1/12,B,O
To check in a passenger from the PS list with the second outbound segment on an interline thru
check-in flight, use the following entry:
1
PA1,1/10,B,O2
The 'PA' input entry is the same as it is for THRU CHECK-IN' whether the acceptance is from a 'PS'
list, or whether the actual flight number and passenger's name is used in the check-in entry.
Note: In the following examples, O designates an onward or ITCI check-in.
8.2.9
Through Check-In
Through Check-In involving Electronic Ticket on one flight and paper ticket on the other flight
1 Example of process:
1. Enter:
PA:1,1/12,B/xxx,O (xxx = destination of the bag).
2. A validation message is generated for both flights and if both coupons are valid, check-in is
completed.
Note: If the local flight has a valid coupon but the onward flight it is invalid, then the passenger is only
checked-in on the local flight.
8.2.9.2 Through Check-in Electronic Ticket on One Flight and Paper Ticket on Other Flight
If the passenger has an e-ticket and a paper ticket, the check-in requires additional processing
procedures. The SITA Departure Control Services system verifies that the passenger has a valid eticket on the local flights. If it is valid, then the onward flight check-in is completed and the boarding
passes issued for both flights.
1 Example of process:
1. Enter
PA:1,1/12,B/XXX,0 (XXX= destination of the bag).
2. A validation message is generated for the e-ticket flight and if the coupon is valid, check-in is
completed. On the boarding pass for the e-ticket flight ELECTRONIC TICKETED PASSENGER
WITH TICKET NUMBER is printed. On the paper ticket flight the boarding pass will print NOT
VALID WITHOUT FLIGHT COUPON.
8.2.10 Examples of Different Check-In (PA) Entries
Examples of various check-in entries:
1. Check-in booked Y Class passenger Jane Wright who is 8 years old with 1/14 baggage and is
traveling alone, and add the item that she is an Unaccompanied Minor:
PA:XS836Y1WRIGHT/JANE,1/14,CHD1,UM8
Or check-in from the PS list:
PA:ENTRY NBR,CHD1,1/14,UM8
Note: The UM indicator gets added to the PSM message for notification to the destination station.
Also the age gets included on the PSM if it is added along with the UM code.
2. Check in Y class passengers Andersen/A and Sergeant/B traveling together on XS397 with 3/33
bags:
PA:XS377Y1ANDERSEN/A, M1,3/33;SERGEANT/B,F1
Or check-in from the PS list:
PA:ENTRY NBR,3/33;ENTRY NBR
3. Check-in the second passenger from a family of three from entry number 2 with 1/10 baggage.
PA:2P2,M1,1/10
4. Check-in booked Y Class passenger from PS list entry number 4 who is traveling with PS entry
number 12 but who are not booked together and the second passenger has not arrived at check-in yet.
They want to sit together:
PA:4,1/10,R17A;#12,R17B
5. Check-in booked M Class passenger Mr. T.BROOK who is traveling with his wife, his son, and his
baby daughter named Mary on flight XS397:
PA:XS397M3BROOK/MR/MRS/MSTR,M1,F1,CHD1,INF1MARY,3/30
Or check in from the PS list:
PA:ENTRY NBR,3/30,INF1MARY
Note: The infant is not included in the passenger number but a name must be added after the INF1
item.
6. Check-in URES C Class passengers Mr. D.Kent and Mrs. J.Cannon who are traveling together:
Page 71
SITA 2008 All Rights Reserved
PA:XS296C1KENT/DMR,M1,2/30,URES;1CANNON/JMRS,F1,URES
7. Check-in booked Y Class passenger Mrs. K.Davidson with 1/12 bags, and add onward flight
KL204YAMS which is not in the passenger record:
PA:XS622Y1DAVIDSON/KMRS,F1,1/12,OKL204YAMS,URES
Or check in from the PS list:
PA:ENTRY NBR,1/12,OKL204YAMS,URES
Note: The URES at the end denotes that the oncarriage and not the passenger was a new item to the
original passenger record.
8. Check-in URES Y Class passenger Mr. T. Simpson with 1/14 bags, with confirmed Onward flight
DL881YLAX:
PA:XS937Y1SIMPSON/TMR,1/14,URES,ODL881/07NOVYLAX
Note: The URES is entered after the baggage details and not at the end of the transaction. If it is
entered at the end, instead of after the baggage, the system would treat the passenger as a NOREC
and the onward connection as the URES.
9. Check-in a PAD passenger (N2) who was not previously listed on a flight and add his Date of
Joining his airline company:
PA:XS118M1HULBERT/LMR,1/12,IDN2/APR79,URES
10. Check-in two Crew in C Class, who are traveling on the flight in passenger seats without any
baggage:
PA:XS633 C 2XXXCREW,0/0,M1,F1
Note: These passengers are included in the total passenger figures but are also displayed separately
under XCR on the SDD display.
11. Check-in passenger from PS display, Entry Number six. Passenger requests an Aisle seat.
PA:6,1/15,RI
Note: The R stands for seat request; the I stands for aisle, and the S for smoking.
12. Check-in booked M Class passenger YORK and add the message for the PSM that he is blind.
PA:XS383M1YORK,1/10,PSM/PLSE MAAS AS PAX IS BLIND
Note: The '/' after the PSM specifies that this message must go on the PSM. If it is omitted, then it will
not be sent. MAAS means meet and assist.
13a. Check-in booked Y class family WATSON who has one child and two infants.
PA:XS927Y3WATSON/MR/MRS/MSTR,3/30,M1,F1,CHD1,INF2IAN+MARY
Note: A '+' is inserted between the infant names.
13b. Check-In two infants with two separate adult entries.
PA1,2/20,INF1JOEY;2,INF1SUSAN
14. Add a Name to a NONAME during check-in:
PA:FLIGHT CLASS 1 NONAME,M1,P/W,NAM(NEW NAME)
PA:XS100Y1NONAME,M1,1/10,NAM1JONES/MR
Or check in from the PS list:
PA1,NAM1SMITH/JOHN,M1,1/10
15. Y Class passenger GRANT is Booked MIA to JFK on flight XS397 that operates MIA to ATL to
JFK, but now wants to disembark at ATL:
PA:1,ZXS397YATL,1/10
Note: The baggage must be entered after the Z item.
Page 73
SITA 2008 All Rights Reserved
16. Check-in booked Y Class Family of four AHMED/MR/MRS/MSTR/MSTR with two Infants, a Pet
Dog in the cabin, 4/50 baggage, an unbooked Onward connection to flight BA854 to LHR, and add
remark for PSM that they need assistance, as they speak no English:
PA:XS761YJFK4AHMED/MR/MRS/MSTR/MSTR,M1,F1,CHD2,INF2ANA+DAR,4/50,
-PETC1/10,PSM/PLEASE MAAS AS PAX SPEAK NO ENGLISH,OBA854YLHR,URES
User modification. PETC and AVIH count and weight will calculate excess baggage charges.
Note: If more than one line is needed, start the second line with a - and always remember to
put the Onward connection as the last item, otherwise the system ignores it.
17. Check-in URES Y class passenger Celina Johnson for the operating carrier of code share flight
XS761 with 1/12 baggage:
PA:XS761YJFK1JOHNSON/CELINA,F1,1/12,URES
18. Check-in URES M Class passenger Mary White for the marketing carrier of code share flight
XS761 marketing with YY761 with 2/24 baggage:
PA:XS761YJFK1WHITE/MARY,F1,2/24,MKTYY761M23ATLJFK,URES
19. Check in booked Y class passenger James Wilson by name for the next day flight with 1/12
baggage:
PA:XS761/+Y1WILSON/ROBERT,M1,1/12
20. Check in booked Y class passenger Allen Adams by name on XS761 with an interline through
check-in segment on YY851 with 1/12 baggage:
PA:XSY761Y1ADAMS/ALLEN,M1,1/12,O
Or from PS list:
PA:ENTRY NBR,1/12,O2
21. Check in booked Y class passenger John Wells by name on XS761 with 2 interline through checkin segments on YY851 and YY950 with 1/12 baggage:
PA:XS761Y1WELLS/JOHN,M1,1/12,O2
Or from PS list:
PA:ENTRY NBR,1/12,O2
22. Check in booked Y class passenger Sandra Smith by name on XS761 connecting to XS319 and
one interline through check-in segment on YY1152 with 2/24 baggage:
PA:XS761Y1SMITH/SANDRA,F1,2/24,O2
Or from the PS list:
PA;ENTRY NBR,2/24,O2
Note: When the interline through check-in segment falls on the third segment of the passengers
itinerary, the letter "O", followed by the Number "2" should be used, indicating the second segment of
the down line flights is the ITCI segment.
23. Check in Y class passenger Johnson/David from PS list on XS100 and change the last name to
the correct spelling of Johanssen with 1/12 baggage:
PA:ENTRY NBR,NAM1JOHANSSEN/DAVID,M1,1/12
24. Check-in Y class passenger Johnson/David with 1/20 BAGS from PS list on XS112 and choose
XS113 as his oncarriage flight to LHR:
SITA Departure Control Services Check In Agent Guide
Passenger Acceptance / Modification / Withdrawal
Page 74
SITA 2008 All Rights Reserved
PA:ENTRY NBR,1/20,OXS113YLHR
25. To enter one or more TKNE elements in the same entry, the format is:
PA:XX857Y2TOMS/J/K,M1,F1,1/10,B,TKNE1/1251234567890C1,
-TKNE2/1251234567891C1,URES
26. To check in two TKNE URES passengers with different names.
PA:XX857Y1TOMS/JACKIE,F1,2/48,B,TKNE/1251234567890C1,URES;
-1SMITH/CAROL,F1,TKNE/1251234567898C1,URES
27. To check-in a TKNE URES passengers with an onward connection.
PA:XX857Y1TOMS/JACKIE,F1,1/10,B,TKNE/1251234567890C1,URES,
-OXS789YMAD,TKNE/1251234567890C2,URES
28. When a passenger checks-in with an infant, and the infant TKNE is already present in the same
PNR, then current check-in procedures apply.
If the passenger is a URES or a TKNE has to be added for an infant during the PA entry, then
the following Infant TKNE check-in format should be used:
PA:XX857Y1TOMS/LYNMRS,F1,INF1BOB,1/10,B,TKNE/1251234567890C1,
-TKNE/1251234567891C1-INF,URES
Note: The INF indicator must be inserted after the TKNE element and the ticket number.
Page 75
SITA 2008 All Rights Reserved
FT0331
SA1720
FT0331
PNR RL PB272
SN6F
Y TIJ BAG1/10/0
TKNE/6A/0952100004111C1
PSM- /INFT HK1 5MTHS OCCUPYING SEAT-1THOMAS/BMISS
THOMAS/BMISS
BN002 SN6E
Y TIJ TKNE/6A/0952100004113C1
ACC VDT53640 AGT102/01MAY0920/OVR
BN001
Note: The infant counter on the SDD is not updated by check-in acceptance of seat holding infant. In
other words the weight of the infant is recorded as an adult.
34. Check-in acceptance of infant not occupying seat.
-PA:1,1/10,INF1BABYTWO,OVR
-PA: 6A470/01MAYYTIJ1,1/10,INF1BABYTWO,OVR
AV Y162
PAD Y0
72S/200
GTD/???? POS/GATE BDT1519 SD1549 ED1549
1. ROHA/AMR
BN001 SN22D
PSM OSR
ROHA/BMRS
BN002 SN22E
OSR
PSM- /INFT HK1 ROHA/BABYTWO 4MTHS -1ROHA/AMR
PDD:1
PDD: 6A470/01MAYYMEX,1
1. ROHA/AMR
BN001
SA1720
FT0331
PNR RL P1272
SN22D
Y TIJ INF1 BAG1/10/0 OSR
TKNE/6A/0952100004111C1
TKNE/INF/6A/0952100004113C1
INF-BABYTWO
PSM- /INFT HK1 ROHA/BABYTWO 4MTHS -1ROHA/AMR
ROHA/BMRS
BN002 SN22E
Y TIJ OSR OSR
TKNE/6A/0952100004112C1
RES AUTO 01MAY0753
ACC VDT53640 AGT102/01MAY0756/OVR
Page 77
SITA 2008 All Rights Reserved
PNR RL P1272
SN22D
Y TIJ RES INF1
TKNE/6A/0952100004111C1
TKNE/INF/6A/0952100004113C1
1 PA transaction example:
PA1,1/10,B
PCTC REQUIRED
PA1,1/10,B,PCTC/MARIA JONES 770-555-1212
1 PU transaction example:
PU1,PCTC/JOHN SMITH 770-555-1212
PCTC REQUIRED
1 PW transaction example:
PW1,PCTC
A list of passengers with PCTC remarks can be displayed with the following transaction:
PS:XS123/12YY , PCTC
Page 79
SITA 2008 All Rights Reserved
Document
Passport
Re-entry permit/refugee
INS Pass
Military ID
Naturalization Certificate
Facilitation Document
Edit
Check-in code
PA or PU
Pax Entry #
DOCS
Issuing Country
Document number
Up to 15 alpha/numerics
Passenger Nationality
Date of Birth
14AUG65
Gender
M or F
FI or MI (infant indicator)
Expiration date
28JAN09
Surname
BYRD
Given name
MILLY
Middle name
(optional)
Page 81
SITA 2008 All Rights Reserved
SA2345
FT0045
CC/NAM
PNR RL DI93KD
M ATL M1/80
PDD: XS1548/03MARMMEX,01
PNR RL DI93KD
1. BYRD/MILLY
BN001 SN21J
M ATL OKT M1/80
DOCS-P /USA/920881/USA/14AUG65/F /28JAN09/BYRD/MILLY//
ACC VDT2110 AGT877/03MAR1105
Note: When using a facilitation document (DOCS/F), it is possible to have a document with no
expiration date. In this case replace the expiration date with a /.
To enter a document with no expiration date, use the following entry:
PA1,0/0,DOCS/F/CAN/989898/CAN/14AUG65/F//BYRD/MILLY
Page 83
SITA 2008 All Rights Reserved
Entry:
PW1,DOCS/ALL
Response:
PDD:01
PDD: XS060/11JANYATL,01
1. MCCOLM/A MR
BN009 SN35K
Y YYZ M1/88 F1/70
DOCA-D/CAN/222 LEE ST/TORONTO/
DOCS-P /CAN/9483938/CAN/12JUL64/M /15OCT05/MCCOLM/ALLEN//
MCCOLM/B MRS
BN010 SN35J
Y YYZ
DOCA-D/CAN/222 LEE ST/TORONTO/
DOCS-P /CAN/2191929/CAN/12JUL65/F /15OCT05/MCCOLM/BETH//
ACC VDT2110 AGT877/11JAN1117/P1/SN35K
ACC VDT2110 AGT877/11JAN1117/P2/SN35J
Note: The above procedures for deletion are DOCS are the same required for deletion of DOCA and
DOCO.
8.2.12.3DOCA - Address Information
Different governments require UN Paxlist information based upon the passengers residence or
destination address, both residence and destination address, or the passengers country of residence.
The passenger address information is defined in the element type:
Residence Address
Destination Address
Edit
Check-in code
PA or PU
Pax Entry #
DOCA
Type of address
R = Residence
D = Destination
Address Details
10 Peachtree Road
City
Atlanta
State/Province/County
GA
30330
Infant Indicator
Page 85
SITA 2008 All Rights Reserved
PDD:01
PDD: XS1548/03MARYMEX,01
PNR RL 92K292
1. PETRALLI/INGE
BN003 SN27A
Y ATL OKT M1/80
ACC VDT2110 AGT877/03MAR1304
SCW VDT2110 AGT877/03MAR1304/OKT
9. Add the destination address to this passengers record using the PU entry:
PU1,DOCA/D/USA/10 PEACHTREE ST/ATLANTA/GA/33030
The PDD now includes the destination address in the passenger record.
PDD:01
PDD: XS1548/03MARYMEX,01
PNR RL 92K292
1. PETRALLI/INGE
BN003 SN27A
Y ATL OKT M1/80
DOCA-D/USA/10 PEACHTREE ST/ATLANTA/GA/33030/
ACC VDT2110 AGT877/03MAR1304
SCW VDT2110 AGT877/03MAR1304/OKT
PU
VDT2110 AGT877/03MAR1306/DOCA
10. Using the same passenger we will add a country of residence with no additional address
information with the following entry:
PU1,DOCA/R/DEU
Redisplay the passenger record to see it contains the DOCA entry with the country of residence.
PDD:01
PDD: XS1548/03MARYMEX,01
PNR RL 92K292
1. PETRALLI/INGE
BN003 SN27A
Y ATL OKT M1/80
DOCA-R/DEU//
DOCA-D/USA/10 PEACHTREE ST/ATLANTA/GA/33030/
ACC VDT2110 AGT877/03MAR1304
SCW VDT2110 AGT877/03MAR1304/OKT
PU
VDT2110 AGT877/03MAR1306/DOCA
PU
VDT2110 AGT877/03MAR1313/DOCA
Adding Infants Address Information
Infants may require:
destination address
residence address
country of residence
The DOCA entry for infants is almost identical to adults with one exception. An /I is added to the end
of the entry to identify the infant.
An infant has been added to the previous passenger record in order to demonstrate how to add an
infant passport.
11. Display the passenger record:
PDD:01
PDD: XS1548/03MARYMEX,01
PNR RL 92K292
1. PETRALLI/INGE
BN003 SN31J S Y ATL OKT INF1/10 M1/80
INF-GRETCHEN
DOCA-R/DEU//
DOCA-D/USA/10 PEACHTREE ST/ATLANTA/GA/33030/
ACC VDT2110 AGT877/03MAR1304
SCW VDT2110 AGT877/03MAR1304/OKT
PU
VDT2110 AGT877/03MAR1306/DOCA
PU
VDT2110 AGT877/03MAR1313/DOCA
PU
VDT2110 AGT877/03MAR1337/INF
12. The following entry adds a destination address for the infant:
PU1,DOCA/D/USA/10 PEACHTREE ROAD/ATLANTA/GA/33030/I
13. An infant destination address now displays in the passenger record:
PDD:01
PDD: XS1548/03MARYMEX,01
PNR RL 92K292
1. PETRALLI/INGE
BN003 SN31J S Y ATL OKT INF1/10 M1/80
INF-GRETCHEN
DOCA-D/USA/10 PEACHTREE ROAD/ATLANTA/GA/33030/I
DOCA-R/DEU//
DOCA-D/USA/10 PEACHTREE ST/ATLANTA/GA/33030/
ACC VDT2110 AGT877/03MAR1304
SCW VDT2110 AGT877/03MAR1304/OKT
PU
VDT2110 AGT877/03MAR1306/DOCA
PU
VDT2110 AGT877/03MAR1313/DOCA
PU
VDT2110 AGT877/03MAR1337/INF
PU
VDT2110 AGT877/03MAR1357/DOCA
14. We will also add a country of residence for the infant to the passenger record with the following
entry:
PU1,DOCA/R/DEU/////I
Note: It is mandatory to add five slashes between the country of residence and the infant indicator
when adding country of residence only.
15. Display the passenger record to verify that the infant country of residence was added to the
passenger record, enter:
PDD:01
Page 87
SITA 2008 All Rights Reserved
To display:
PDD: XS1548/03MARYMEX,01
PNR RL 92K292
1. PETRALLI/INGE
BN003 SN31J S Y ATL OKT INF1/10 M1/80
INF-GRETCHEN
DOCA-R/DEU//I
DOCA-D/USA/10 PEACHTREE ROAD/ATLANTA/GA/33030/I
DOCA-R/DEU//
DOCA-D/USA/10 PEACHTREE ST/ATLANTA/GA/33030/
ACC VDT2110 AGT877/03MAR1304
SCW VDT2110 AGT877/03MAR1304/OKT
PU
VDT2110 AGT877/03MAR1306/DOCA
PU
VDT2110 AGT877/03MAR1313/DOCA
PU
VDT2110 AGT877/03MAR1337/INF
PU
VDT2110 AGT877/03MAR1357/DOCA
PU
VDT2110 AGT877/03MAR1400/DOCA
Edit
Check-in code
PA or PU
Pax Entry #
doco
Sydney AUS
Document Type
Document number
Up to 15
alpha/numerics
15DEC05
Page 89
SITA 2008 All Rights Reserved
21. The PDD now displays the infant Place of Birth and VISA information, enter:
PDD:01
To display:
PDD: XS1548/03MARFMEX,01
PNR RL DK29D2
1. FIELD/DONALD
BN004 SN2D
F ATL OKT INF1/10 M1/80
INF-JOHN
DOCO-SYDNEY AUS/V/CD1234567/SYDNEY/15DEC05/USA/I
DOCO-SYDNEY AUS/V/AB54321/SYDNEY/15DEC05/USA/
ACC VDT2110 AGT877/03MAR1446
SCW VDT2110 AGT877/03MAR1446/OKT
PU
VDT2110 AGT877/03MAR1449/DOCO
PU
VDT2110 AGT877/03MAR1459/INF
PU
VDT2110 AGT877/03MAR1505/DOCO
8.2.12.5Entries to List Passengers with DOCS, DOCO or DOCA Information
To identify passengers with travel document information:
DOCS
22. Enter Flight/Date,DOCS.
PS:218/.,DOCS
The response is a list of all passengers with DOCS information.
PS: 2M218/27FEB CDG,DOCS
OP/NAM
757/200
GTD/???? POS/GATE BDT2230 SD2300 ED2300+1 SA0600+1 FT1300
1. 1HERNANDEZ/LMR
BN004 SN36F
Y ATL DOCA DOCS
2. 3MOUSSA/AMR
BN001 SN13C
Y ATL O DOCA DOCO DOCS
MOUSSA/BMR
BN002 SN13B
Y ATL O DOCA DOCO DOCS
MOUSSA/CMRS
BN003 SN13A
Y ATL O DOCA DOCO DOCS
3. 1YAGO/CRMS
BN005 SN25F
Y ATL DOCA DOCS
DOCA
23. Enter Flight/Date,DOCA.
PS:218/.,DOCA
The response is a list of all passengers with DOCA information.
PS: 2M218/27FEB CDG,DOCA
OP/NAM
757/200
GTD/???? POS/GATE BDT2230 SD2300 ED2300+1 SA0600+1 FT1300
1. 3MOUSSA/AMR
BN001 SN13C
Y ATL O DOCA DOCO DOCS
MOUSSA/BMR
BN002 SN13B
Y ATL O DOCA DOCO DOCS
MOUSSA/CMRS
BN003 SN13A
Y ATL O DOCA DOCO DOCS
DOCO
24. Enter Flight/Date,DOCO.
PS:218/.,DOCO
The SITA DCS system provides a listing of passengers on the flight and date who have DOCO travel
document information available. For example:
PS:218/-,DOCO
PS: 2M218/27FEB CDG,DOCO
OP/NAM
757/200
GTD/???? POS/GATE BDT2230 SD2300 ED2300+1 SA0600+1 FT1300
1. 3MOUSSA/AMR
BN001 SN13C
Y ATL O DOCA DOCO DOCS
MOUSSA/BMR
BN002 SN13B
Y ATL O DOCA DOCO DOCS
MOUSSA/CMRS
BN003 SN13A
Y ATL O DOCA DOCO DOCS
8.2.12.6Entries to List Passengers Missing DOCS, DOCO or DOCA Information
To identify passengers missing travel document information:
25. Enter Flight/Date,NDOCS.
PS:1548/.,ndocs
The SITA DCS system displays a listing of passengers on the flight and date who are missing DOCS
travel document information.
ps1548,ndocs
OP/NAM
OP/NAM
Page 91
SITA 2008 All Rights Reserved
OP/NAM
Definition
BIRTHDATE REQUIRED
GENDER REQUIRED
A code other than an "R" or "D" was entered the DOCA field.
ISSUE DATE
ISSUING COUNTRY/STATE
NATIONALITY REQUIRED
Page 92
SITA 2008 All Rights Reserved
INFANT INDICATOR
INVALID DATE
INVALID GENDER
Mandatory
1. passport number
Mandatory
Maximum 35 characters.
Mandatory
3. date of birth
Mandatory
4. gender code
Mandatory
M-male F-female.
5. surname
Mandatory
6. first name
Mandatory
7. expiration date
Optional
8. Nationality
Mandatory
All passport details are followed by an oblique. If the optional field of expiry date is omitted, obliques
will be consecutive. For example a passenger with a PSPT remark where the expiration date is
omitted is input as shown below:
PA1,1/10,B,PSPT/F/P094158760/US/22MAR57/F/SMITH/MARY//US
Page 93
SITA 2008 All Rights Reserved
PA:1,1/10,B,PSPT/P/P04126490/US/20AUG65/M/SMITH/JOHN/01JAN06/US
Explanation
Country
Date
Gender Required
Number
Name Required
Nationality Required
Nationality is missing
Mandatory
1. passport number
Mandatory
maximum 35 characters
Mandatory
3. date of birth
Mandatory
4. gender code
Mandatory
M - male
F - female
5. surname
Mandatory
6. first name
Mandatory
7. expiration date
Optional
8. Nationality
Mandatory
Page 95
SITA 2008 All Rights Reserved
1 Example of a transaction to delete PSPT items from passengers one, three and four of a
passenger record.
PW:1,PSPT/1/3/4
1 Example of a transaction to delete all the PSPT items from a multi passenger record.
PW:1,PSPT/ALL
Processing
The PSPT item is deleted from the passengers record is included in the PDD transaction for a specific
passenger or passengers. The PDD history includes deletion of the PSPT item, within the current
design of the PDD history.
PW Output
The output for a successfully completed PW transaction is a passenger status response display.
There is no change to the existing response.
Error Responses
Response
Explanation
Format
BDT1730
SD1800
BN002 SN27C
BN003 SN27B
BN001
SN14F
Y
Y
Y
Y
Y
Y
OP/NAM
ED1800
JFK MSG PSPT
JFK PSM
JFK PSPT
JFK PSPT
JFK PSM MSG PSPT
JFK PSPT
1 An example of the output when a PSPT item is present in the passenger record is shown below.
PDD:1
PDD: XS500/26AUGYATL,1
1. CHARLES/MR
BN004 SN10C
Y MSP
CHARLES/MRS
BN005 SN10B
Y MSP
ACC VDT965 AGT1/26AUG1406
PSPT-CHARLES/RAYMR/P123456/GB/01JAN50/M/01JAN06
CHARLES/RAYNELMR
BAG1/10/0
Delete crewman:_
Page 97
SITA 2008 All Rights Reserved
*Personal Information
Surname:________________________________________
Given/Middle Name:___________________ /_________________________
Gender:_
Nationality:___
Birth date:_______
PCTC: ______________________________________________________________
Residence country:___ Address Details:___________________________
ZIP/Postal Code:____________
City:_________________________________
State/Province/Country:_______________________________
Final Destination:___
Crew Status:___
Birth Place:_____________________________
Crew Title:_________________________
*Document Information
P = Passport
C = US Resident card
Expiration date:_______
Country of issue:___
Document Number:__________________________________________
VISA Number:________________________
Override Country:___
Authorized By:___________________________________________________
*Pilot Information (UN PAXLST only)
License number:________________
Country of issue:___
1 Add required information to the crew mask for the country you are sending to:
CREW:XS 1548/06MAR06 /ATL
_
Delete crewman:
*Personal Information
Surname: SMITH___________________________________
Given/Middle Name: JOHN______________ / _______
Gender: M
Nationality: USA
Birth date: 29JAN65_______
PCTC: 1234567890_____________________________________________________________
Residence country USA
Address Details: 10 ANY ST__________________________
ZIP/Postal Code: 12345__________ City: ATLANTA____________________________
State/Province/Country: GA USA_____________________________
Final Destination: ATL
Birth Place: USA+ATLANTA+GA_____________________
Crew Status: CR1
Crew Title: CAPTAIN_____________________
*Document Information
P = Passport
C = US Resident card
M = Military-ID T = US Re-entry permit A = Alien registration card
Document type:
P__
Expiration date: 23AUG08
Country of issue: USA
Document Number: 938498988__________________________
VISA
Number: ________________________________ Issued for country: ___
VISA Issue Date: _____ Place of Issue: ___________________________________
Airline or Gov Override Indicator (APP only): _
Override Country: ___
Authorized by:______________________________________________________________
*Pilot Information (UN PAXLST only)
License number: 9389898_____________
Country of issue: USA
1. 1SMITH/JOHN
SA1400
FT2001
The crew records can be displayed either by the PDD or the Crew Mask using the following entries:
To display the PDD:
PDD:NBR
PDD:01
Page 99
SITA 2008 All Rights Reserved
PNR RL CREW
1. SMITH/JOHN
! ATL
PCTC-1234567890
CREW-
/CR1/CAPTAIN
LICENSE-USA/9389898
APP DOCA-R/USA/10 ANY ST/ATLANTA/GA USA/12345/
DOCO-USA+ATLANTA+GA/V/
DOCS-P /USA/938498988/USA/29JAN65/M /23AUG08/SMITH/JOHN//
PSPT-P/938498988/USA/10JAN65/M/SMITH/JOHN/23AUG08/USA
To display the crewmember by mask: CREW:NBR
CREW:XS 1548 /06MAR06 /ATL
Delete crewman:_
*Personal Information
Surname:SMITH___________________________________
Given/Middle Name:JOHN______________ /___________________________
Gender:M
Nationality:USA
Birth date:29JAN65
PCTC:1234567890_____________________________________________________
Residence country:USA
Address Details:10_ANY_ST_________________
ZIP/Postal Code:12345_____
City:ATLANTA__________________
State/Province/Country:GA_USA_______________________
Final Destination:___
Crew Status:CR1
Birth Place:USA+ATLANTA+GA____________
Crew Title:CAPTAIN___________________
*Document Information
P = Passport
C = US Resident card
Country of issue:USA
Document Number:938498988__________________________
VISA Number:____________________________
VISA Issue Date:____
Place of Issue:________________________
Country of issue:USA
To delete a crewmember, pull up the crew mask by the number on the PS List. Enter Y in the Delete
Crewman line:
CREW:1
Delete crewman:Y
*Personal Information
Surname:SMITH___________
Given/Middle Name:JOHN_______________ /______________________
Gender:M
Nationality:USA
Birth date:10JAN65
PCTC:1234567890_________________________________________________
Residence country:USA
Address Details:10_ANY_ST______________
ZIP/Postal Code:12345______ City:ATLANTA____________________________
State/Province/Country:GA_USA________________
Final Destination:___
Birth Place:USA+ATLANTA+GA_____________
Crew Status:CR1
Crew Title:CAPTAIN___________________
*Document Information
P = Passport
C = US Resident card
Document Number:938498988__________________________
VISA Number:__________________
VISA Issue Date:_______
Place of Issue:__________________________
Country of issue:USA
Passengers traveling to, from or through an APP country require a PA transaction to CPS seeking
authorization to board. All messages received by the CPS must be for a flight that is known to
them.
Agents can modify passport data in a passenger record prior to a check-in transaction.
Passengers without authorization to board will not receive a boarding pass and the agent will be
prompted to delete the passenger.
The system checks applicable Passenger Acceptance, Passenger Update, and Passenger Withdrawal
transactions for an APP airline parameter and to which country the travel will involve. The system then
SITA Departure Control Services Check In Agent Guide
Passenger Acceptance / Modification / Withdrawal
29 August 2008 Revision 7.2
Page 101
SITA 2008 All Rights Reserved
determines if either of the city pair (to/from) is in the APP participating country, and if the response is
yes a message for PA, PU, or PW is generated.
8.2.21 Check-In
8.2.21.1 To Check Single Passengers:
Use the PS List, for example:
xs7777,namSMITH
-PS: xs7777/10OCT SGN,NAMSMITH
OP/NAM
320/A
GTD/???? POS/GATE BDT1130 SD1200 ED1200
1. 1SMITH/JOHN
Y SYD
-
SA2300
FT0800
SA2300
FT0800
-PA1,0/0,DOCS/P/USA/T67778/USA/12jul67/M/12JUL15/ALVAREZ/JOSE;2,
- DOCS/P/USA/T67234/USA/13SEP70/M/13SEP15/BERRY/JOHN
8.2.21.3 Checking a Passenger without PSPT or DOCS data:
If an agent attempts to check in any passenger(s) where PSPT or DOCS data is not present, the
PSPT DATA REQUIRED error response returns.
-PA: XS123/11OCTYSYD3,0/0
AV C12Y135
PAD C0Y0
320/A
GTD/???? POS/GATE BDT1130 SD1200 ED1200
1. SMITH/JOHN
BN003 SN21D
SA2300
FT0800
The PSPT or DOCS data can be added after the passengers is checked-in with the PU
transaction, however this alone does not trigger the APP query; therefore another PU transaction
needs to be done to send the APP query.
Ps123/+,NAMSMITH
-PS: xs123/11OCT SGN,NAMSMITH
OP/NAM
320/A
GTD/???? POS/GATE BDT1130 SD1200 ED1200
SA2300
1. 1SMITH/JOHN
BN003 SN21D
Y SYD APP
FT0800
-PU:1,DOCS/P/USA/T67778/USA/12JUL67/M/12JUL15/SMITH/JOHN
-PU: XS123/11OCTYSYD1,DOCS/P/USA/Y67778/USA/12JUL67/M/12JUL15/SMITH/JOHN
AV C12Y135
PAD C0Y0
320/A
GTD/???? POS/GATE BDT1130 SD1200 ED1200
SA2300
FT0800
1. SMITH/JOHN
BN003 SN21D
ps123/+,NAMSMITH
-PS: XS123/11OCT SGN,NAMSMITH
OP/NAM
320/A
GTD/???? POS/GATE BDT1130 SD1200 ED1200
SA2300
1. 1SMITH/JOHN
BN003 SN21D
Y SYD DOCS APP
-PU:1,APP
-PU: XS123/11OCTYSYD1,app
AV C12Y135
PAD C0Y0
320/A
GTD/???? POS/GATE BDT1130 SD1200 ED1200
SA2300
1. SMITH/JOHN
BN003 SN21D
APP TRANSACTION IN PROGRESS
AU APP* (0502) OK TO BOARD/BN3
FT0800
FT0800
Page 103
SITA 2008 All Rights Reserved
1 Example: Where one passenger receives OK and the other Not OK:
1.
2.
SMITH/TMR
BN050
SN14A
*Australia APP * OK TO BRD/BN050
TALBOT/KMRS
Australia APP
BN051
SN14B
* DO NOT BRD/BN051
After SDCS sends the APP queries, the CPS system generates an appropriate response from the
following list:
Response
Explanation
OK TO BRD
All data required to assess the passenger is available but the directive
from the country indicates that the passenger is not permitted to board.
After consultation with a government authority or a determination by the
check-in agent that the passenger conforms to requirements of a
special category of traveler according to the countrys regulations, the
Do Not Board directive may be overridden by the check-in agent.
Page 105
SITA 2008 All Rights Reserved
SA2300
FT0800
(For PA or PU) Country Name APP Flight, 5 passenger maximum group size.
(For PW) Country Name APP Flight, 5 passenger maximum group size.
8.2.21.7 Standbys
All PA entries result in an APP message being sent, however, if the passenger is not accommodated,
but placed on standby, he does this with the benefit of being pre-approved. If the APP message is
negative, the agent is notified and can take the appropriate action.
Response (positive) :
* AUSTRALIA APP TRANSACTION IN PROGRESS
PDD: VN516/19JULYHAN,1
1. QUINCY/QUINT
SB0222
APPB-AU /8501/OK TO BOARD
-
PDD: VN516/19JULYHAN,1
1. QUINCY/QUINT
SB0222
LMTS Y MEL URES IDID00S101
APPI-AU /8513/DO NOT BOARD - PAX NOT KNOWN
***Uncheck passenger***
PW
Page 107
SITA 2008 All Rights Reserved
8.2.21.8 Override
To override Do not board passengers the transaction is the following:
PU:1,APPG/AU/FREE TEXT
PU:1,APPA/AU/FREE TEXT
AV C12Y137
PAD C0Y0
320/A
GTD/???? POS/GATE BDT2230 SD2300 ED2300
SA0600+1 FT0400
1. ADAMS/BILL
BN001 SN26C
*SYD* ***PAX:NGOTHANHLAN(TOI PHAM)->GOI CACK--KT KY VSA/PSPT + TIETAB
RATE NOT FOUND. NO JCD TABLE ENTRY FOR THIS DESTINATION: SYD
-EXB:1/SPCH/CASH/VND0.0
APP TRANSACTION IN PROGRESS
AU APP* (8502) DO NOT BOARD/BN1
**Delete -DO NOT BOARD- Passenger(s)
-PW:-pu:1,appg/au/free text
-PU: VN7777/20JULYSYD1,appg/au/free text
AV C12Y137
PAD C0Y0
320/A
GTD/???? POS/GATE BDT2230 SD2300 ED2300
SA0600+1 FT0400
1. ADAMS/BILL
BN001 SN26C
*SYD* ***PAX:NGOTHANHLAN(TOI PHAM)->GOI CACK--KT KY VSA/PSPT + TIETAB
APP TRANSACTION IN PROGRESS
AU APP* (8517) MAY BOARD
- OVERRIDE ACCEPTED/BN1
-
pu:1,app
-PU: XS781/21JULLMEL1,app
AV C25Y281
PAD C0Y0
777/77C
GTD/???? POS/GATE BDT1630 SD1700 ED1700
SA0835
FT1235
1. BRAVO/ROSALYN +B2 BN001 SN16G
SGN PSM
SN31K
MEL
PSM- CTCH-SGN-GRAND HOTEL-04JUL OUT 10JUL CTCH-DLI-EMPRESS HOTEL-10JUL OUT
12JUL CTCH-HOI AN-HOI AN HOTEL-12JUL OUT 15JUL CTCH-HAN-SUNNY HOTELIN
15JUL OUT 21JUL
EQ CHG SGN
APP TRANSACTION IN PROGRESS
AU APP* (8510) DO NOT BOARD - CONTACT EOC/BN1
**Delete -DO NOT BOARD- Passenger(s)
-PW:-
APPB The passenger has been given clearance to board. (Screen message OK to BRD).
APPD The passenger is not to be permitted to board. After a consultation with governments
authorities or a determination by the check-in supervisor that passenger conforms to the
requirements according to the regulation of the country, the boarding directive may be overridden
by the check-in supervisor. (Screen message DO NOT BRD).
APPU Unable to determine the status of the passenger. Multiple records have been found
matching the data supplied. More specific bio-data must be supplied. (Screen message: Will vary
depending on conditions).
APPI Insufficient data is available. (Screen message: Will vary depending on conditions).
APPE An error condition has been detected. All error conditions must be corrected before
processing. (Screen message: Will vary depending on conditions).
APPP The message going or coming back was lost and response is pending. Try to re-send.
Note: If any passenger has status D / U / I / P or E, the check-in supervisor will not be able to close
the flight. All conditions must be corrected before being able to close the flight.
Page 109
SITA 2008 All Rights Reserved
8.2.22 AQQ
AQQ, APIS Quick Query, is currently being introduced by the US Government. AQQ has similarities to
APP as it allows for immediate clearance of passengers upon check-in using a PA or PU entry.
Passengers will receive one of three responses when an agent attempts acceptance of the passenger.
These responses are OK TO BOARD, DO NOT BOARD CONTACT CBP or SELECTEE status.
8.2.22.1Passenger Check-in and Update
Below is an example of an AQQ transaction using Passenger Acceptance (PA) receiving an OK TO
BOARD response:
PS:XS123,NAMSOLE
_PS: XS123/21FEB JFK,NAMSOLE
767/B
GTD/???? POS/GATE BDT1830 SD1900 ED1900
SA2200
1. 1SOLENKO/VIKA+
Y KBP ADV-PU/NP DOCA DOCS APP
PA1,0/0
PA: XS123/21FEBYKBP1,0/0
1. SOLENKO/VIKARO
BN012 SN14C
NOTIFIED
NO EXCESS BAGGAGE INFORMATION
_APP_ TRANSACTION IN PROGRESS
US APP* (8501) OK TO BOARD/BN12
OP/NAM
Below is an example of an AQQ transaction using Passenger Acceptance with a NO-FLY status:
PS:XS123,NAMALEX
_PS: XS123/21FEB JFK,NAMALEX
767/B
GTD/???? POS/GATE BDT1830 SD1900 ED1900
1. 1ALEXANDER/CREW+
Y KBP DOCA DOCS
PA1,0/0
1. ALEXANDER/CREWE
BN001 SN25A
_APP_ TRANSACTION IN PROGRESS
US APP* (8540) DO NOT BOARD - CONTACT CBP (US)/BN1
**Delete -DO NOT BOARD- Passenger(s)
_PW:-
OP/NAM
SA2200
When receiving a No-FLY response, the agent should contact the US authorities. AQQ does not allow
for an override transaction as is used for APP. If it is determined by the authorities that an OK to
Board will be allowed, the authorization will be received through an Unsolicited Message. The agent
will then need to update the passenger record using a PU1,APP transaction.
An example of a PU1,APP transaction to update passenger status:
PU1,APP
_PU: XS123/21FEBYKBP1,app
AV C19Y192
PAD C0Y0
1. ALEXANDER/CREWE
BN012
_APP_ TRANSACTION IN PROGRESS
US APP* (8501) OK TO BOARD/BN12
SN25A
SA2200
FT2000
8.2.22.2Passenger cancellation:
A passenger may be deleted from an AQQ flight with a Cleared or Selectee status using the PW entry.
SA2200
FT2100
If the passenger being deleted is a NoFly passenger, no response will be received upon deletion of
the passenger.
Page 111
SITA 2008 All Rights Reserved
(For PA or PU) Country Name APP Flight, 5 passenger maximum group size.
(For PW) Country Name APP Flight, 5 passenger maximum group size.
Example 1:
Normal Check-in
Y YVR
FT0245
Note 1: The item OKT (OK to travel) is attached to the passengers record to identify that a check
was made and there was no match found for this passenger. The action code SCW (Security
Checked Watch List) is also added to the history element.
Note 2: If the check-in does not involve an airport to or froma Watchlist country, then no codes are
attached to the passengers record even if they may be on the Watch List.
Note 3: For passengers with an onward connection, by through check-in, to a flight that involves a
Watchlist airport then the same procedures apply to the onward flight. The check-in agent will get a
warning if a match is found on the Watch List for the onward flight but the passenger will not be
inhibited from checking-in on their flights. However, for NNN and depending on a parameter setting for
SSS, they will be denied a boarding card.
Page 113
SITA 2008 All Rights Reserved
Example 2:
Selectee Check-in
Y YYZ
Example 3:
No Fly check-in
Y YYZ
Page 115
SITA 2008 All Rights Reserved
Name Search:
38. Enter Passenger Name, Last Name/First Name (No match found):
XSCW:SABEL/RON
Response:
NO MATCH FOUND
Example:
BN85
SN22D
Y BOS NNN
43. To close flight, use one of the following Options:Delete passenger from flight
XPW:-1Use override entry (if passenger cleared to travel) after retrieving record (PDD:1)
XPU1,OVRW
Note: The OVRW is used for passengers that have been given security clearance to travel and is
restricted by sign-in code. The action/PID number/Agent and time is recorded in passengers PDD
record.
Note: After a passenger override, the boarding card must be printed. Enter BC:1 to print the boarding
card.
8.2.23.5Passenger Updates
If any passenger updates such as Name change or added PSPT or DOCS elements are entered after
the passenger has been checked-in, a new check against the watch list is initiated. If a match is
found, the record is marked with the appropriate NNN or SSS code and even though the boarding card
was previously issued, it is rejected if boarding is attempted.
8.2.23.6Passenger Displays (PS)
It is possible to display passengers by SSS, NNN, or OVRW codes.
Example:
PS SSS List:
ED2000
Y
MIA
Y
MIA
Y
MIA
Y
MIA
SA2100
FT0100
SSS PSPT TKNE
SSS I PSM
SSS NRS ASR TKNM
SSS TKNE
Page 117
SITA 2008 All Rights Reserved
OP/NAM
BTD/0930 SD1000 ED1000 SA1105 FT0105
E15
GROUP Y
JFK
P5
GROUP C
JFK
G25
GROUP Y
JFK
4
5
6
7
Field
Description
The '0' in front of the name signifies that this is a group name and not a passenger. It is not
possible to check-in any names that start with 0.
Name of the group. This display does not list the name of the passengers in the group, only
the group name.
Group identifier followed by the number in the group. This group identifier comes from the
PNL.
The next step after displaying the list of groups is to display the names for the individual groups. This
is done by making a note of the group identifier, and entering the following:
PS:FLIGHT ,GRI (GROUP IDENTIFIER)
Example to identify the names in group GOLFTEAM (the group identifier is J9), the entry is:
PS:XS227 ,GRI J
Note: Only the letter code of the group identifier is entered, not the number.
1
PS:XS227,GRIJ,NGRP
Response to PS:XS227,GRIJ,NGRP
PS:XS227/08JUNATL,GRIJ,NGRP
OP/NAM
767/A
GTD/A7
POS/GATE BTD/0930 SD1000 ED1000 SA1105 FT0105
1. 2DAWSON/MR
J9
C
JFK
DAWSON/MRS
J9
C
JFK
2. 1MORRISON/D
J9
C
JFK
3. 2MARTIN/KMR
J9
C
JFK
MARTIN/WMRS
J9
C
JFK
4. 1OBRIEN/IAN
J9
C
JFK
5. 1PALMER/MR
J9
C
JFK
6. 2REYNOLDS/S
J9
C
JFK
REYNOLDS/T
J9
C
JFK
By adding the NGRP in the initial entry, this omits the group name from the display, and now the whole
group can be checked-in with one transaction.
If a group has no pre-assigned seats, it is possible for a supervisor to reserve an area on the seat map
(using the RS entry which puts a G on the requested seats), so that at check-in if the agent adds the
code 'SNRGRP' the passengers are allocated this designated area.
Example:
PA:1,P/W,SNRGRP
(individual passenger)
PA:1,P/W,SNRGRP;2;4;5
(range of passengers)
PA:1,P/W,SNRGRP;2-5
Note: The following entry is not allowed: PA:1-6,P/W,SNRGRP. The check-in agents should not use
the transaction above because it causes discrepancies especially when deleting one or more
passengers from the group.
Page 119
SITA 2008 All Rights Reserved
NOREC Check-In
If the passenger is a NOREC, the normal check-in entry is used. A NOREC check-in requires two
entries, as the system first checks the booked list to see if it can find the name entered or any similar
names. Then it displays them, and the agent must either identify the NOREC entry or select another
passenger on the list.
Example:
PA:XS679Y1SMITH/D,M1,1/10,B
Response to PA:XS679Y1SMITH/D,M1,1/10
PA:XS679/28JULYMIA1SMITH/D,M1,1/10,B
1. 1SMITH/D -NOREC PSGR
2. 2SMITHSON/MR
K2
Y
MIA
3. SMITHSON/MRS
K2
Y
MIA
M1/78
F1/68
The check-in has not yet been completed, so if an error is made, the screen can be erased, and the
transaction entered is ignored. However if the passenger is a NOREC then enter 'PA:1' and the
system completes the normal check-in. The passenger is either accepted into a seat or put on the
standby list depending on the GS figures entered on the SDD screen.
1
PA:1
In some cases the passenger name entered in the initial check-in entry might be slightly different from
the name registered on the list. If so, the system responds with a NOREC list plus the names of other
passengers who have similar names.
If the check-in agent finds that the passenger is not a NOREC but is one of the passengers on the
similar names list, then the check-in can be completed by entering the PA followed by the entry
number of the correct passenger (PA:ENTRY NUMBER) on this list.
Note: Although the name of the passenger was originally checked-in differently from the name on the
list, the system ignores the check-in entered name and keeps the system displayed name (if the name
is wrong and has to be changed, then correct it with the PU transaction).
The PDD display of a NOREC passenger who has gone on standby shows the code NREC.
NREC
M1/78 BAG1/10/0
8.4.2
URES Check-In
If the passenger is a URES, the normal check-in entry is followed by the code 'URES'. When the
URES code is used, the system does not check any booked list, and the check-in transaction can be
completed in one entry.
1
PA:XS679Y1SMITH/D,M1,1/10,URES
The check-in is completed normally and the passenger is either accepted into a seat or placed on the
standby list depending on the GS figures entered on the SDD screen.
The PDD display of a URES passenger who has gone on standby shows only URES.
MIA
URES
M1/78 BAG1/10/0
The transaction for EXST with ETKT processing for URES is:
PA: Flight Date ClassDestination1Last name/First name, 0/0, Gender, EXST,
TKNE/XXXXXXXXXXXXXC1,
TKNE- /XXXXXXXXXXXXXC1-EXST, URES
8.4.3
PAD Check-In
If a PAD passenger is listed on the flight, enter the ID element with the initial check-in entry but the
item URES is not required. If the PAD passenger is not previously listed on the flight, then the URES
item must also be input, otherwise the system responds with the NOREC display.
An example entry for a PAD passenger who has not been previously listed is:
PA:FLIGHT CLASS NBR NAME,GENDER,P/W,ID CODE,URES
1
PA:XS679 Y 1JONES/MR,M1,1/12,ID00N2/JAN88,URES
PA:XS679Y1JONES/MRS, F1,1/12,IDB2,URES
PA:XS679C1JONES/MARY,F1,1/12,IDAD00R1,URES
PA:XS679C1JONES/MARTIN,M1,1/12,IDID1,URES
Note: The ID code depends on the codes entered on the PZ:AIRLINE table. Also the 'date of joining'
is an optional entry. However if the 'date of joining' is entered, then the system can onload by
seniority, for those PAD passengers who have the same ID code. If the 'date of joining' is not entered,
the system will onload in order of check-in (first checked-in, first onloaded).
1 Example of a PDD Display of a URES PAD Passenger who has Gone on Standby:
PDD:XS679/28JULYATL,1
1. JONES/MR SB020 PAD
Y
SBY VDT2967 AGT296/28JUL0815
MIA
URES
Page 121
SITA 2008 All Rights Reserved
8.4.4
When checking-in a passenger with valid oncarriage and the passenger goes on standby on the first
flight, the oncarriage check-in is inhibited. Later, if the passenger is accepted on the flight, then the
agent must re-initiate the onward check-in (PS:1,10) to complete the check in process for the
passenger.
8.4.5
If the GS/ID figures have been updated on the SDD screen, to accept any NOREC or URES
passengers checking-in, and these passengers have oncarriage, it is important the URES item is
inserted in the correct place.
If the following passenger is a URES on the first flight and not a NOREC, and the URES item is
inserted at the end of the transaction the following response is received:
1
PA:XS679Y1JAMES/MRS,F1,1/9,OBA292YLHR,URES
The response is a NOREC List:
PA:XS679/28JULYMIA1JAMES/MRS,F1,1/9,OBA292YLHR,URES
1. 1JAMES/MRS -NOREC PSGR
The system assumes the passenger is booked, and that the oncarriage details are the URES item.
The correct entry is:
PA:XS679Y1JAMES/MRS,F1,1/9,URES,OBA292YLHR,URES
The URES item must be input before the oncarriage details in order for the passenger to be
recognized as a URES on the first flight. Putting URES after the oncarriage indicates the passenger is
a URES on the oncarriage flight only.
Response to URES in Oncarriage:
PA:XS679/28JUNYMIA1JAMES/MRS,F1,1/9,URES,OBA292YLHR,URES
AV F10Y43
PAD F0Y3
747/A GTD/C19 POS/GATE BDT1930 SD2000 ED2000 SA2145 FT0145
1. JAMES/MRS
BN067 SN23A O
TRANSFER MIA BA292/28JUNYLHR CHECK-IN UNAVAILABLE
8.4.6
Passengers that are NOREC or URES on a marketing segment of a Code share flight can be
checked-in either by checking the passenger in using the marketing flight number OR checking in
using the operating carrier with a marketing indicator.
The following entry is for a NOREC passenger holding a marketing ticket on a code share flight using
the marketing flight for check- in:
1 Example: NOREC Y passenger David Smith holding a ticket on marketing flight YY141
operating as XS040:
PA:YY141Y1SMITH/DAVID,M1,1/10
Note: Checking in a NOREC/URES passenger with the marketing flight adds the MKT item to the
PDD.
The following entry is for a NOREC passenger holding a marketing ticket on a Code share flight using
the operating carrier with a marketing indicator for check-in:
1 Example: NOREC Y passenger David Smith holding a ticket on marketing flight YY141
operating as XS040:
PA:XS040Y1SMITH/DAVID,M1,1/10,MKTYY141Y01ATLJFK
The following entry is for a URES passenger holding a marketing ticket on a Code share flight using
the marketing carrier for check-in:
1 Example: URES Y passenger David Smith holding a ticket on a marketing flight and
checking in for YY141 operating as XS040:
PA:YY141Y1SMITH/DAVID,M1,1/10,URES
The following entry is for a URES passenger holding a marketing ticket on a Code share flight using
the operating carrier with a marketing indicator for check-in:
1 Example: URES Y passenger David Smith holding a ticket on a marketing flight and
checking in for YY141 operating as XS040:
PA:XS040Y1SMITH/DAVID,M1,1/10,MKTYY141Y01ATLJFK,URES
Passengers checking in as NOREC or URES passengers holding a ticket for the operating carrier of a
Code share flight will be checked in as normal NOREC and URES passengers.
1 Example: NOREC Y Passenger David Smith Holding a Ticket on Operating Flight XS040:
PA:XS040Y1SMITH/DAVID,M1,1/10
Or from PS list:
PA:ENTRY NBR,1/10
Page 123
SITA 2008 All Rights Reserved
General Description
As ITCI deals with passenger handling procedures, these topics are covered in the following sections:
8.5.2
PA Input
The passenger acceptance transaction is the same as Thru Check-In procedures, only the Responses
are different.
Note: To ITCI requires a .0, .02 or .03 indicating where in the line of flight ITCI exchange will take
place.
PA Use and Restrictions
Any Agent with the appropriate authority level can use the PA transaction.
The following restrictions apply for attempting to use ITCI for the Thru Check-In onto another Airline's
flight and DCS system:
Most airlines consider restricting ITCI for the following types of passengers:
ADSR
COUR
EXST
ID2
JMP
MUS
STCR
URES or NOREC passengers are not eligible for ITCI unless advised by the airlines.
Airlines bilaterally agree on the SSR types to be allowed. Some of the SSRs allowed are, but not
limited to:
CHD
INF
BLND
SCST
DEAF
DOCO
SITA Departure Control Services Check In Agent Guide
Passenger Acceptance / Modification / Withdrawal
Page 124
SITA 2008 All Rights Reserved
DOCA
EXBG
FQTV
SDML
PETC
PRML
TKNA
TKNE
TKNO
UMNR
PA Input/Response
The 'PA' input entry remains the same as for Thru Check-In whether the acceptance is from a 'PS' list,
or whether the actual flight number and passenger's name is used in the check-in entry.
Responses to a PA transaction where ITCI is attempted from either SDCS or the partner
system/airline. Responses from SDCS are described in the Check-In Functional Specifications. All
processing and error responses apply. Responses from the partner host or partner airline are
preceded by EDI * when displayed to the screen. Other SSR codes are restricted by the connecting
carrier.
The following examples apply to passengers that are being Thru Checked-In onto onward connections
and processed through ITCI.
Page 125
SITA 2008 All Rights Reserved
PNR RL
H297S
Y LHR M1/77
Y MAN
1
PA:XS378/01MARYATL,1/12,O
AV F12Y54
PAD F0Y2
D10/A
GTD/B24
POS/GATE
BTD/0930
SD1000
ED1000
SA2305
1. ADAMS/AMR
BN023
SN12C
O
O/YY827/02MAR
Y MAN
EDIFACT THRU CHECK-IN IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
TRANSFER LHR YY827/02MARJUN MAN
1. ADAMS/AMR
BN009
SN17D
OP/NAM
FT0805
PNR RL
H297S
Y LHR M1/77
Y MAN
Response:
PA:XS378/01MARYATL,1/12,O
AV F12Y54
PAD F0Y2
D10/A
GTD/B24
POS/GATE
BTD/0930
SD1000
ED1000
SA2305
1. ADAMS/AMR
BN023
SN12C
O
O/YY827/02MAR
Y MAN
EDIFACT THRU CHECK-IN IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
OP/NAM
FT0805
After 20 seconds if the system is unable to complete the transaction, the response is:
- EDIFACT QUERY TIMED OUT
This means that the system was unable to complete the 'THRU CHECK-IN' transaction and so the
second Boarding Card or Boarding Number is not issued. The check-in process stops at this stage
and the passenger must be advised that he must check-in again at his transfer point.
Further attempts to check-in on the onward connection, with a PU1,O could result in the same
response, or could result in a successful check in. Repeated attempts cause unnecessary processing
if the partner system is still not responding.
PNR RL
H297S
Y LHR M1/77
Y MAN
If the system cannot complete the transaction, the response is an error or warning response such as:
EDI * FLIGHT NOT OPEN FOR THROUGH CHECK-IN
The system was not able to complete the 'THRU CHECK-IN' transaction for the specified reason, and
so the second Boarding Card or Boarding Number is not issued. The check-in process stops at this
stage and the passenger advised that he must check-in again at his transfer destination.
Page 127
SITA 2008 All Rights Reserved
Description
Aisle Seat.
Exit Seat.
Front Seat.
Bulkhead Seat.
Legroom Seat.
Left Seat.
Right Seat.
Quiet Zone.
Smoking Seat.
Window Seat.
Movie Seat.
Center Seat.
1 Example entry:
PA:1,2/15,R11A,O,RW
1 Example response:
PA:XS378/01MARYATL,2/15,R11A,O,RW
AV F10Y44
PAD F0Y2
D10/A
GTD/B24
POS/GATE
BTD/0930
SD1000
ED1000
SA2305
1. GRANT/DMR
BN069
SN11A
O
O/YY827/02MAR
Y MAN
EDIFACT THRU CHECK-IN IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
TRANSFER LHR YY827/02MAR MAN
1. GRANT/DMR
BN010
SN23A
FT0805
the onward Airline. The transaction will either be accepted or rejected with an error or warning
response.
8.5.3
8.5.3.1 PU Processing
The passenger acceptance transaction is same as 'THRU CHECK-IN' procedures, only the
'RESPONSES' are different.
8.5.3.2 PU Use and Restrictions
The PU transaction can be used by any Agent with the appropriate authority level.
The following restrictions apply for attempting to update a passenger's record on a flight, through
EDIFACT, on another Airline's DCS system:
Passengers with EXTRA seats (COUR, EXST, MUS, STCR) are not allowed.
ITCI is attempted on the first onward connection in the passenger record only.
Passengers with any SSR items on the Onward flight may not be accepted based on the ITCI
agreement. These include, but are not limited to,
UM/INF/BSCT/DEAF/BLND/FF/SPML/PETC/SNR (seat change requests) and all WCH requests.
8.5.3.3 PU Input/Response
The 'PU' input entry remains the same as it is for 'THRU CHECK-IN' whether the acceptance is from a
PS' list, or the actual flight number and passenger's name is used in the check-in update.
Responses to a PU transaction where ITCI is attempted come from either SDCS or the partner
system/airline. Responses from SDCS are described in the Check-In Functional Specifications. All
processing and error responses apply. Responses from the partner host or partner airline are
preceded by EDI * when displayed to the screen.
The following examples only apply to passengers that have been 'THRU CHECKED-IN' onto onward
flights being processed through EDIFACT.
Page 129
SITA 2008 All Rights Reserved
SN10C
SN06D
PNR RL
H522T
Y LHR BAG1/12/0 M1/77
Y MAN
FT0805
At this stage there is a short wait and the system should respond with a reply. If the attempt is
successful, the system responds:
PU: XS378/01MARYATL,1,WCHR
OP/NAM
AV F10Y36
D10/A
GTD/B24 POS/GATE BDT/0930 SD1000 ED1000 ED1000 SA2305
1. COOPER/CMR
BN065
SN10C
O/YY827/02MAR
BN012
SN06D
Y MAN
EDIFACT UPDATE IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
TRANSFER
LHR YY827/02MAR MAN
1. COOPER/CMR
BN012
SN06D
FT0805
At this stage the passenger update is complete and no further action is required.
SN10C
SN06D
PNR RL
H522T
Y LHR BAG1/12/0 M1/77
Y MAN
FT0805
After 20 seconds if the system cannot complete the transaction, the response is:
EDIFACT QUERY TIMED OUT
This indicates the system cannot complete the 'UPDATE' transaction and the entry process stops.
The passenger must be advised that he must check again at the transfer destination. In this case the
system sends an IFM message in case the transaction reached the onward flight but 'ran out' of time
before a response could be sent.
Note: There is no reason why the 'UPDATE' cannot be attempted again using the PU transaction
although the response could remain the same.
Page 131
SITA 2008 All Rights Reserved
PNR RL
H522T
Y LHR BAG1/12/0 M1/77
Y MAN
FT0805
1 Example entry:
PU:1,O,R6F
1 Example response:
PU:XS378/01MARYATL,O,R6F
OP/NAM
AV F10Y44
PAD F0Y2
D10/A GTD/B24
POS/GATE
BTD/0930
SD1000
ED1000
SA2305
FT0805
1. GRANT/DMR
BN069
SN11A
O
O/YY827/02JMAR
BN010
SN06A
Y MAN
EDIFACT UPDATE IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
TRANSFER
LHR YY827/02MAR MAN
1. GRANT/DMR
BN010
SN6F
8.5.4
8.5.4.1 PW Input
The passenger delete transactions for 'THRU CHECK-IN' passengers are the same as 'PW'
procedures except some of the 'RESPONSES' are different.
8.5.4.2 PW Use and Restrictions
Any agent with the appropriate authority level can use he PW transaction.
The following restrictions apply for attempting to update a passenger's record on a flight, through ITCI,
on another Airline's DCS system:
Only one passenger 'entry number' can be deleted in the same transaction.
When deleting items, the items must be associated with the passenger, and the counts and
weights cannot exceed the original value of the items.
8.5.4.3 PW Input/Response
The 'PW' input entry remains the same for updating passenger records on flights that were processed
for 'THRU CHECK-IN' with ITCI, only some of the responses may differ.
The following examples only apply to passengers that have been 'THRU CHECKED-IN' onto onward
flights being processed through ITCI.
Page 133
SITA 2008 All Rights Reserved
PNR RL
H681G
Y LHR BAG1/12/0 M1/77
Y MAN
1 B/Example of a 'Time Out Response' when a 'PW' for a Passengers Item is Attempted:
Display passenger PDD:
PDD: XS378/01MARYATL,1
1. HARRIS/C/MR
BN015
SN18F
Y LHR
O/YY827/02MAR BN004
SN18F
BAGTAGS ISSUED:
0182526567 0182526568
ACC VDT10655 AGT299/01MAR0820
Y MAN
PNR RL
H681G
BAG2/22/0 M1/77
WCHR
Page 135
SITA 2008 All Rights Reserved
Y LHR
Y MAN
PNR RL
H681G
BAG2/20/0 M1/77
1 D/Example of a 'Normal Response' when a 'PW' is Used to Delete a Passenger on the Onward
Flight Only:
PNR RL
SN14A
SN09F
H847I
Y LHR
Y MAN
BAG1/12/0 F1/65
OP/NAM
SD1000 ED1000 SA2305 FT0805
SN14A
SN09F
Y MAN
FLIGHT YY827/02MAR/Y/LHRMAN
At this stage there is a short wait and the system should respond. If the attempt is successful, the
system responds:
PW XS378/01MARYATL,1,O
OP/NAM
AV F060Y22
D10/A GTD/B24 POS/GATE BDT/0930 SD1000 ED1000 SA2305 FT0805
1. MORRIS/FMRS
BN049
SN14A
O/YY827/02MAR
BN019
SN09F
Y MAN
EDIFACT DELETION IN PROGRESS FOR FLIGHT YY827/02MAR/Y/LHRMAN
TRANSFER
LHR YY827/02MAR MAN
1. MORRIS/FMRS
DELETED
At this stage the passenger update is complete and no further action is required.
Page 137
SITA 2008 All Rights Reserved
1 E/Example of a 'Normal Response' when a 'PW' is Used to Completely Delete a Passenger from
both Flights:
PNR RL
SN14A
SN09F
H847I
Y LHR BAG1/12/0 F1/65
Y MAN
1 F/Example of a 'Normal Response' when a 'PW' is used to Delete an Onward Flight Before and
After Check-In:
Before Check-In
Display passenger PDD:
PDD: XS378/01MARYATL,1
1. PHILIPS/MR
O/YY827/02MAR
PNR RL
H847I
Y LHR M1/77
Y MAN
Y LHR
PNR RL
H847I
ADV-PW/NP M1/77
It is then possible to add a new onward flight with the PA entry providing the URES is added at the end
of the entry (PA:1,1/12,OYZ837YGLA,URES).
After Check-In
Display passenger PDD after check-in:
PDD: XS378/01MARYATL,1
PNR RL
1. PHILIPS/MR
BN055 SN19K
O/YY827/02MAR
BAGTAGS ISSUED:
0182526583
ACC VDT10455 AGT279/01MAR0912
H847I
Y LHR
Y MAN
1/12/0 M1/77
H847I
Y LHR
1/12/0 M1/77
It is then possible to add a new onward flight, if required, with the PU entry (PU:1,OYZ837YGLA).
Example of E-Ticket passenger with EXST has the EXST removed prior or after check in.
Prior to check in the entry is
PW: #1, EXST
This entry would remove both the EXST and the TKNE associated with it. The status of the EXST
coupon would be changed to OPEN FOR USE.
After check in
PW:-1
Both the passenger and the EXST coupon should have the status changed to OPEN FOR USE.
Page 139
SITA 2008 All Rights Reserved
8.5.5
ID1
ID2
ID1 passengers are usually 'booked' staff passengers, and are therefore permitted for 'INTERLINE
THRU CHECK-IN' providing they are also booked on the onward flight, as they are treated as a normal
'OK' passenger. Any 'unbooked' ID1 passengers will not be accepted for the onward flight as the
system rejects any URES or NOREC passengers, unless the name is found on the onward flight.
ID2 passengers are 'unbooked' staff passengers and are inhibited from check-in on the onward flight.
8.5.6
The following sections explain the difference between a URES and a NOREC passenger.
8.5.6.1 URES
A URES passenger is any passenger who wants to travel on a flight but who is not 'Booked' (Open
ticket) or Listed for the flight on the passenger name list (PNL). For the PFS (passenger final sales)
report sent to their Reservations Department at the end of a flight, the system treats these passengers
either as GO-SHOW passengers (if they are Full-Fare Revenue passengers), or as ID PAD
passengers if they are Airline staff.
8.5.6.2 NOREC
A NOREC passenger is a passenger who holds a 'Booking' in his ticket for the flight but whose name
is not included on the Passenger Name List (PNL).
Note: At check-in time when a URES passenger is being checked-in, that the agent remembers to
add the item URES to the transaction. Otherwise the system assumes the passenger is a NOREC,
and this causes erroneous information being passed back via the PFS report to the Reservations
department at the end of the flight.
8.5.6.3 Boarding Card Re-Issue (BC)
Entry:
The Boarding Card for the origin flight is printed when the passenger check-in transaction is
completed. The second Boarding card is issued when the return response from the ITCI process is
successful.
If it is necessary to re-issue a Boarding card, the following are the only valid entries:
Entry
Description
BC:1
BC:1,O
Re-issue Boarding Card for first onward flight only, which is the ITCI flight.
Page 141
SITA 2008 All Rights Reserved
8.5.7
1 Example entry:
PDD:1,O
The response is:
PDD:XS378/01MARYATL,1,O
1. GIBSON/IAN
BN008
SN03D
BN026
SN05C
BAGTAGS ISSUED:
0182526661
ACC VDT10651 AGT311/01MAR0827
EDIFACT PROCESSING IN PROGRESS
Y LHR
Y MAN
PNR RL H337F
BAG1/10/0 M1/77O/YY827/02MAR
PNR RL H337F
Y LHR BAG1/10/0
Y MAN
If the entry is not successful, then a corresponding Error or Warning message is returned to the
screen.
8.5.7.2 Restrictions
The following restrictions apply on attempting to display the PDD:1,O transaction for a passenger
listed on an onward flight using ITCI.
PNR RL
H847I
Y LHR M1/77
Y MAN
Although the basic SE entry/display is not changed, there is now an additional entry to display a seat
map for an onward flight. This applies to flights that are 'THRU CHECKED' using the EDIFACT
process.
The entry is:
SE:FLIGHT/DATE ORIG DEST
1 Example entry:
SE:YY827/+LHRMAN
The response is:
EDIFACT SEAT MAP REQUEST SENT FOR FLIGHT YY827/02MAR/LHRMAN
Page 143
SITA 2008 All Rights Reserved
=
.R
*
*
F
S
F
*
R
=
F
E
D
=
.
E
D
=
R
.
.
=
.
*
*
Y
E
*
*
.
E
*
*
.
= = = = S S S S S S R
. * . * . . . * * .
FR
* * * * . * * . * *
ER
* * R * * * . * * * . * DR
[ [ [ 1 [ [
Although it is possible to display this seat map, it is not possible to revise it.
Note: Some ITCI partners require that the class be input with the SE entry. If the entry is not
successful, then an Error or Warning message is returned to the screen.
When checking-in the unattached bags, please remember the initial code is PU and not PA.
The entry to check in without bag tags is:
PU:FLIGHT CLASS DEST 0, P/W
PU:XS100YMEX0,2/30
SA2000 FT0200
SA2245
FT0045
SA0
Page 145
SITA 2008 All Rights Reserved
8.8.2
1 Example response:
PDD:XS100 ,0
PDD:XS100/02AUGATL,0
MEX 3/42 UNATTACHED BAGS
ACC VDT 1967 AGT286/02AUG1743
ACC VDT 5926 AGT518/02AUG1836
1/10
8.8.3
If an unattached bag must be removed from the flight, use the following entries:
To delete bags without bag tag numbers:
PW:FLIGHT CLASS DEST 0, P/W
A record of the bag tag deletion is sent to the KB queue and the Baggage Action List (BAL).
1 Example Response:PW:XS100YMEX0,1/10
PW:XS100/02AUGYMEX0,1/10
AV F14Y58 PAD F0Y0
DC9/A GTD/???? POS/GATE
UNATTACHED BAGS DELETED
SA2000 FT0200
1
PW:XS100YMEX0,1/10,B/1
1 Example Response:PW:XS100YMEX0,1/10,B/1
PW: XS100/24OCTYMEX0,1/10,B/1
AV C36M110
PAD C0M0
DC9A
GTD/???? POS/GATE BDT2315 SD2345 ED
To delete bags using a tag number:
PW:FLIGHT CLASS DEST 0,P/W.B/XS1234567
SA0030+1 FT0045
1 Example response:
DVC-7382 1844 02AUG90
CKI XS100/02AUG ATL REMOVE BAGGAGE
UNATTACHED BAGS
DEST/MEX BAG/1/10 AGT836
This is a security message, so that if there is a baggage figure discrepancy at the aircraft, the
supervisor can quickly identify if any baggage was cancelled from the system after check-in by
checking these warning messages.
8.8.4
The system allows the entry and issuance of bag tags for expedite bags where no part of the itinerary
is on a SDCS operated flight.
1
SITA Departure Control Services Check In Agent Guide
Passenger Acceptance / Modification / Withdrawal
29 August 2008 Revision 7.2
Page 147
SITA 2008 All Rights Reserved
EXP:D
EXP:
Pieces/Weight
0
Origin/Date BUD/17JUN06
Passenger Last/First Name
Flight/Date
Flight/Date
Flight/Date
/
/
/
/0
/
Destination
Destination
Destination
It is possible to display all unattached baggage details entered for a non-SDCS operated flight out of
the signed in city for the current date.
1
EXP:D
After the initial EXP:D entry, it is possible to select and update baggage details associated with a
specific entry number.
1
EXP:U1
Note: If all Baggage is removed (0/0 entered in Piece/Weight field), then after Transmit, all the
baggage details are also deleted.
If baggage is added, then either a manual bag tag must also be added, or on transmit an automated
bag tag is issued.
If the baggage is being reduced, then the Transmit transaction is ignored unless a corresponding bag
tag is also deleted. There is an additional field displayed at the end of each bag tag where an X is
placed for selected bag tag to be deleted.
Before Check-In
After Check-In
Page 149
SITA 2008 All Rights Reserved
1
SB:XS735
Response to SB:XS735
SB: XS735/08JUNATL
OP/NAM
737/106C GTD/B17 POS/GATE BTD/1930 SD2000 ED2000 SA2105 FT0105
AV C4M63
PAD C0M0
NEED NOTIFICATION
1. 2BLAKE/MMR
B2
BN002 SN1A
C
MIA
ACC/SB007
BLAKE/TMS
B2
BN003 SN1C
C
MIA
ACC/SB008
2. 1KELLY/LMRS
BN019 SN23D
M
MIA
PU/NP
LOCAL PAD
3. 1PORTER/GMRS
BN045 SN3C
C
MIA
P08
IDN1/MAR71
4. 1EDWARDS/YMR
BN023 SN4A
C
MIA
P05
IDS1/AUG69
STANDBY
5. 1CARLTON/N
SB025 LMTS
M
MIA
P20
IDS2/MAY71
6. 3FERGUSON/SMR K3
SB035 LMTS
M
MIA
P50
IDN2/APR79
FERGUSON/YMRS K3 SB036 LMTS
M
MIA
P50
IDN2/APR79
FERGUSON/LMIS+K3 SB037 LMTS
M
MIA
P50
IDN2/APR79
7. 1BOOTH/AMR
SB019 LMTS
M
MIA
P90
IDR2/SEP85
The passengers that Need Notification are listed first, followed by the Standby passengers (Accepted
and Listed).
To Action the Notification just enter:
NO:ENTRY NUMBER
1
NO:1-2
This clears the Notification status for 2BLAKES and 1KELLY. This transaction should be entered for
all passengers that Need Notification before the flight closes (CI) for check-in, otherwise the list of all
the Need Notification passengers will be displayed on the screen when the Flight Close (CI) is
attempted.
Excess baggage charges are applied the response shows the amount of excess bag charges to
be assessed with the comment BOARDING PASS PRINT INHIBITED.
API data is required and is not complete the response is BOARDING CARD INHIBITED MISSING
DOCUMENT DATA.
1 Examples:
1.By Boarding Number:
BC:FLIGHT NUMBER CLASS, BN NUMBER
BC:XS496M,BN098
2.By Seat Number:
BC:FLIGHT NUMBER CLASS, SN NUMBER
BC:XS338Y,SN17B
3.By Standby Number:
BC:SB NUMBER (flight number is not required)
BC:SB137
4.By Group Name:
BC:FLIGHT NUMBER CLASS, GROUP NAME
Note: Group names must be entered exactly as displayed on list and even though passengers may
have been checked-in by their own names, issuing boarding cards by group name will only display the
group name on the boarding card.
BC:XS299Y,SUNTOURS
5.
6.
Note: The BC entry is not allowed for passengers that have already boarded. If a boarding card has
to be re-issued for a boarded passenger, then they must be de-boarded first.
Page 151
SITA 2008 All Rights Reserved
Only the weight of baggage, or the number of pieces, depending on which restriction applies, at
the time of check-in is used for the system calculation.
The total number of checked bags (weight or pieces) for a family or group is calculated against the
total allowance for those checking-in at the same time.
Note: An infant has no baggage weight allowance but is allowed one piece of baggage when piece
concept is used.
The system calculates the amount of excess baggage to the passenger's final destination (that
includes oncarriage details if these are entered at the time of check-in) providing that the destination is
entered in the excess baggage destination cost display table (JCD).
Example of a passenger with excess baggage using weight concept without the inhibit boarding card
program being loaded:
PA:XS639YMIA1GRAHAM/FMR,2/25
Response to PA:XS639YMIA1GRAHAM/FMR,2/25
PA:XS639/22JUNYMIA1GRAHAM/FMR,2/25
AV Y75
PAD Y2
737/A
GTD/G07 POS/GATE BTD1635 SD1700 ED1700 SA1930 FT0230
1. GRAHAM/FMR
BN031 SN12F
EXB:1/5KG/CASH/USD65
EXCESS BAGGAGE CHARGE/UNIT $ 13.0
The passenger has to pay USD65 for 5 kgs excess 2. The excess baggage charge in this example is
USD13 per one kg and even though the passenger has excess baggage, the boarding card will print.
Example of same passenger with excess baggage using weight concept but this time the inhibit
boarding card program is loaded:
PA:XS639YMIA1GRAHAM/FMR,2/25
Optionally, the boarding card print can be inhibited.
The charge has to be accepted by transmitting after the 65; otherwise, the excess amount is not
recorded in the excess baggage statistics.
SITA Departure Control Services Check In Agent Guide
Passenger Acceptance / Modification / Withdrawal
Page 152
SITA 2008 All Rights Reserved
Response to PA:XS639YMIA1GRAHAM/FMR,2/25
PA:XS639/22JUNYMIA1GRAHAM/FMR,2/25
AV Y75
PAD Y2
737 A
GTD/G07 POS/GATE BTD1635 SD1700 ED1700 SA1930 FT0230
1. GRAHAM/FMR
BN031 SN12F
EXB:1/5KG/CASH/USD65
EXCESS BAGGAGE CHARGE/UNIT $ 13.0
BOARDING PASS PRINT INHIBITED
The passenger must now pay the excess charge. Once that is completed the boarding card can be
issued. However, this involves four steps:
1.
The agent must re-display the passenger record. This can be retrieved by name, boarding
number, or seat number.
Example:
PDD:XS639Y,BN031
Response PDD:XS639Y,BN031
PDD:XS639/22JUNYMIA,BN031
1. GRAHAM/FMR
BN031
ACC VDT3823 AGT724/22JUN1502
2.
SN12F
Y MIA
BAG2/25/0
Enter EXB followed by the entry number which should be 1, then a / and the system gives the
correct amount of excess due.
EXB:1/
Response to EXB:1/
EXB:1/5KG/CASH/USD65
Note: It is possible to enter a particular type of currency after CASH so that the system converts the
charge to that currency (providing that currency rate of exchange is entered in the JXD table).
Example:
EXB:1/5KG/CASH/UKL
Response to EXB:1/5KG/CASH/UKL
EXB:1/5KG/CASH/UKL39
3.
When the system responds with the cost of the amount to be charged, go to the end of this
entry and re-transmit:
EXB:1/5KG/CASH/USD65
<Transmit>
Response to EXB:1/5KG/CASH/USD65
CHARGE ACCEPTED
Page 153
SITA 2008 All Rights Reserved
Destination. Unless the check-in is for a single flight only, it is advisable to always enter the Bag
Destination in the check-in entry.
Bag Tag number, to allow the agent to input a manual Bag Tag.
A bag can be marked hot for baggage with close connecting times or other airline reasons.
1
Checks in passenger, issues no Bag Tags.
PA:1,1/10
Checks in passenger, attempts through check-in. Issues no Bag Tags, so EDIFACT check-in is not
attempted.
PA:1,1/10,O
Will check in passenger, and issue Bag Tags to the checked-in destination. If the passenger has an
outbound remark in his record, no through check-in or EDIFACT check-in is attempted, as the input did
not include the O option.
PA:1,1/10,B
Will check in passenger, and issue Bag Tags to the destination specified, as long as that destination is
in the passenger's record and at the same time attempting the through check-in or EDIFACT
processing.
PA:1,1/10,B/DEST,O
Will check in passenger, update passenger record with manually entered tag number (so no automatic
Bag Tag is printed); and attempts through check-in or EDIFACT processing.
PA:1,1/10,B/LHR/AA123456,O
An example of how to input manual Bag Tag numbers by range.
PA:1,3/30,B/ATL/AA123456-458
Designate a bag as hot. To utilize the hot feature, the airlines Bag Tag PECTAB must be changed.
Contact SITA Customer Support for assistance.
PA:1,1/10,B/DEST/H,O
Subsequent Processing
Only manually added Bag Tags are allowed without the requirement of a PID number entered for
BTAG on the DPID: display. If the system attempts to print Bag Tags, then the system checks to
make sure a PID number was entered otherwise it provides the following error response:
042 - UNABLE
Note: Online 'through check-in is permitted without Bag Tag information, however EDIFACT
processing is not attempted if bag count and tag counts are not equal.
Error Responses
If no baggage is input with the PA transaction, the previous options are not allowed and a 'FORMAT'
rejection message displays.
Page 155
SITA 2008 All Rights Reserved
1 Examples:
Update passenger record, issue no Bag Tags.
PU:1,1/10
Update passenger's record, and issue Bag Tags to the checked-in destination. If the passenger has
an outbound remarks in his record, no through check-in or EDIFACT check-in is attempted, as the
input did not include the O option.
PU:1,1/10,B
Update passenger record, and issue Bag Tags to the destination specified, as long as that destination
is in the passenger's record. At the same time attempt the through check-in or EDIFACT processing
to issue Bag Tags as far as the Outbound to the first outbound destination while attempting through
check in or EDIFACT processing.
PU:1,1/10,B/DEST,O
Updates passenger record with manually entered Bag Tag numbers, and attempt through check in or
EDIFACT processing.
PU:1,1/10,B/LHR/AA12345678,O
An example of how to input manual Bag Tag numbers by range.
PU:1,3/30,B/ATL/AA12345678-680
Issue Bag Tags for bags already entered in the record providing no Bag Tags are already present (for
example if the agent failed to request the Bag Tags at PA).
PU:1,B
Reissue all Bag Tags in record.
PU:1,BR
Reissue the first and third Bag Tag in the record.
PU:1,BR1/3
Reissue the first five Bag Tags in the record.
PU:1, BR1-5
Note: The system does not allow the re-issue of manually entered and System generated Bag Tags in
the same entry. If the record does contain a mixture, then make sure the re-issue request is either for
only the Manually entered Bag Tags, or System generated Bag Tags, otherwise the entry is rejected.
For reissued bag tags, a user parameter determines if the same tag number or a new tag number is
issued. This parameter is controlled by pss.helpdesk@sita.aero.
1 Example of PDD with original and new bag tags listed (the * indicates the original one):
PDD:XS166/16JUN Y ATL,1
PNR RL HE103YD
1. HUNTER/MMRS
BN023 SN10DY MIA TKNA/XS/0952485629412C1
BAG1/10/0 F1/75
BAGTAGS ISSUED: ATL 1/10
0182938473/MIA
*0182938472/MIA
ACC VDT27236 AGT97/16JUN1026
PU VDT27236 AGT97/16JUN1029/BAG
Error Responses
If no baggage is input with the PU transaction, the previous options are inhibited and a 'FORMAT'
rejection message displays.
8.14.3 PW Input / Response
Other PW functionality remains as it is, whether used to modify a passenger record from a prior PS
display, or PDD display.
O, O2, and O3 check-in and processing remain the same. All examples use O for simplicity.
1
PW:1,3/35,B/ALL
PW:1,1/10,B/1
PW:1,2/23,B/1/4
Delete bags and the first and fourth tag in the record.
Subsequent Processing
If the passenger has been through checked in or EDIFACT through checked in, the PW cascades
down as it currently does.
If it is necessary to cancel a Bag Tag number, the system deletes it from the passenger's PDD record
but also sends a warning message to the GQ queue with the details of the Bag Tag number deleted,
the flight number, the passengers name, and the BN number associated with that bag. This is for
security reasons to help identify baggage discrepancies.
Page 157
SITA 2008 All Rights Reserved
1
PDD:1
PDD: XS3227/18MARMATL,1
1. HUNTER/MRS
BN002 SN14C
M MIA BAG1/12/0 F1/75
O/XX935/18MAR
M ZRH
BAGTAGS ISSUED: ATL 1/12
0182001203/MIA
*0182001202/MIA
ACC VDT2766 AGT66/18MAR0950
PU
VDT2766 AGT66/18MAR1009/BAG 1/10
PW
VDT2766 AGT66/18MAR1009/BAG 1/10
PU
VDT2766 AGT66/18MAR1010/BAG 1/12
*** OUTBOUND XX0935 MIAZRH ***
Error Responses
If baggage is deleted from a passenger's record, the deletion of corresponding number of Bag Tags is
required.
The following Error Responses may display due to an incorrect entry:
Error Message
Explanation
BAG NUMBER
BAG TAG
DUP REF
ENTRY NUMBER
FLT CANCELLED
FLT CLOSED
INV INPUT
NO ACTION
NO DISPLAY
UNABLE
Page 159
SITA 2008 All Rights Reserved
H522T
MIA
BAG1/12/0
UM10
Explanation
0 - Interline Tag.
1 - Fallback Tag (for sortation systems).
2 - Interline 'Expedite' Tag.
3 - Individual Airline's own use.
2nd to 4th
5th to 10th
Six-digit number of the Bag Tag (the first number issued will be 000001 up to
999999, then the system starts at 000001 again).
JL:NT/FLIGHT/DATE/CLASS
Description
AL
HL
Baggage to Hold.
LD
Baggage to Load.
RM
Baggage to Remove.
XL
XR
Description
DEFAULT
PRINTER
TELEX
Page 161
SITA 2008 All Rights Reserved
The PU transaction cannot be used to check-in a passenger, except to transfer to a new flight or to
through-check a passenger on to connecting flights once he has been checked onto the first flight.
The PU transaction can only be entered using range numbers from a previous display; it cannot be
entered by passenger's name. However a series of range numbers can only be used for items: O,
I, APT, PUPG, PDNG, UGPA, for all other items only one range number per passenger
transaction is permitted.
PU is restricted to gate CRT after initial (CI) close, but only if there is a CRT associated with the
gate entered for the flight.
A PU transaction for a not present (#) passenger cannot contain any of the following items: M, F,
CHD, O, MUS, COUR, EXST, JMP, XRES, UPG, DNG, URES, Z.
The PU transaction cannot be used to change gender for a checked-in passenger. The passenger
must be offloaded (PW), and then checked-in again (PA) with the correct gender.
The PU transaction for a checked-in passenger cannot contain the items: ID, STCR, GRP, and
URES unless the URES is after an O item.
Only MSG, PSM, URES, XRES, SNR, RQST, JMP, INF, BSCT, are allowed after an O item.
The PU transaction can be used to recheck passengers short of their original destination on the
same flight (Example: PU:ENTRY,Z FLT CLS NEW DEST ).
Page 163
SITA 2008 All Rights Reserved
10.
Check in passenger Lauren Wells on a connecting segment after checking in on the first flight
only:
Example:
PU1,O
Example:
PU1,O FLT NBR/DATE CLASS DEST
11. Add a double oncarriage segment to a passengers record after check-in:
Example:
PU1,OXS113YLHR
12. Add denied boarding voluntary remarks to a passenger's record after check-in:
Example:
PU1,DBV/PASSENGER REBOOKED XS111
13. Add denied boarding involuntary remarks to passengers record after check-in:
Example:
PU1,DBI/PASSENGER REBOOKED XS111
Note: Free text up to 25 characters is allowed with DBV and DBI entries.
14.
Add a second connecting flight as double oncarriage, XS133, Y CLASS ATLMIA, to passenger
John Hoffman after he is already checked in:
Example:
PU1,OXS133YMIA
15.
If a passenger checked-in without a TKNE element, which now needs to be added, then the
passenger must first be deleted from the flight, and checked-in again but this time the TKNE
element must be included:
PU:1,O,TKNE/0958476394863C1
16.
17.
Add EXST with TKNE for a passenger who has not yet checked in:
PU#1,EXST,TKNE/XXXXXXXXXXXXXC1-EXST
Page 165
SITA 2008 All Rights Reserved
There is no change to current processing in using the PW entry except for the TKNE
element. Attempting to remove a TKNE element before or after check-in is inhibited. A
warning message displays if an agent tries to remove a TKNE element.
15.
A Reconciliation Exist whereby you receive an unsuccessful ITCI attempt. At this point it is likely both
systems are not synchronized.
PDD:1,O
Page 166
SITA 2008 All Rights Reserved
Page 167
SITA 2008 All Rights Reserved
BOOKED
PRIORITY
-------1
2
4
5
# 30
# 40
# 50
# 90
WAITLISTED
PRIORITY
---------3
6
8
# 9
# 30
# 40
# 50
# 90
UNBOOKED
PRIORITY
--------7
# 10
# 11
# 12
#?60
#?65
#?70
#?99
The lower the number, the higher the priority. If the travel status code is followed by a '/', there is no
requirement to add the date of joining. Those codes which do not have the / indicate the date of
joining is an optional entry. It is entered as three letters for month followed by two numbers for year
(example: JAN89).
The '#' before the number indicates that the passenger is available for disembarkation (PAD) and the
'?' indicates that the passenger has a space available ticket.
Page 169
SITA 2008 All Rights Reserved
1
RK:XS826/+ MIA
1
DR:KL JFK
Page 171
SITA 2008 All Rights Reserved
Page 173
SITA 2008 All Rights Reserved
CC/NAM
SA2100
FT0240
If the list contains fewer than 50, then the actual passenger names display. If the list contains more
than 50 names, then only the total number of passengers still to board displays. The display provides
the names of the passengers, the boarding numbers, seat numbers with class, and destination.
Note: If only one passenger from a 'family' entry number is 'Boarded', the system continues to display
the whole family as 'Not Boarded', until the whole entry has Boarded.
Page 175
SITA 2008 All Rights Reserved
Page 177
SITA 2008 All Rights Reserved
13. Glossary
-AADL - Add/Delete List.
AEC - Automatic Equipment Change.
ALD - Automatic Load Planning.
AO - Agent Out Screen.
API - Advance Passenger Information.
APP - Advanced Passenger Processing System
-BBAB - Boarding Acceptance by Boarding Number screen.
BAS - Boarding Acceptance Screen.
BC - Boarding Card Issuance, Boarding Card Inhibit.
BDS - Boarding Delete Screen.
BI - Basic Index.
BN - Boarding Number.
BRC - Bulk Recheck Accepted passengers.
BRN - Bulk Recheck Not Checked-In Passengers.
BSD - Boarding Status Display screen.
BTM - Baggage Transfer Message.
-CCFL - Check In Flight List Display.
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.
Page 179
SITA 2008 All Rights Reserved
-IIDM - Industry Discount Message. (Dispatched to next down line station on Multi-sector flights.)
IFM - Interline (EDIFACT flights) Fallback Message.
IOD - Inbound/Outbound Display Screen.
-LLDP - Load Planning.
LDVS - System Selected Deck Version.
-MMD - Manifest Display.
MVT - Movement Message.
-NNAM SS - Name Check-In with Seat Selection.
NPRO - Releases all records, except the PNL / ADL records for the flight, and clears the Manifest
Index so a PNL will no longer show processed.
NOREC - No Record. A passenger with a booking but whose name is not on the PNL.
-PPA - Passenger Acceptance screen.
PAD - Passenger Available for Disembarkation.
PCI - Passenger Statistics.
PCTC - Passenger Contact.
PDD - Individual Passenger Record Display.
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.
PS - Passenger Display Screen.
Protected WorkstationProtected workstations require a personal account number and check letter
during sign-in.
PSM - Passenger Service Message. (Dispatched to all stations.)
PTM - Passenger Transfer Manifest. (Dispatched to all stations having transfer.)
PU - Passenger Upgrade.
PW - Passenger or Item Withdrawal or Delete.
PZ - Staff Priority Table Display screen.
Page 181
SITA 2008 All Rights Reserved
1 Example indicator
X Start of Entry indicator
14. Index
Acceptance
Passenger..................................................59
Access to SITA DCS ..........................................3
Active Code share Flight
Example.....................................................24
Active Flight......................................................23
Example.....................................................24
Adding Infants
Address Information ...............................86
Place of Birth and VISA Information......89
Adding PSPT after Initial Check-in...................95
Address Information
Adding Infants..........................................86
Address Information .........................................85
Advanced Passenger Processing System101, 110
Agent
Automatic System Checks...........................4
Agent Control .....................................................3
Agent Information...............................................4
Agent Number
Agent Sign-In ...............................................5
Agent Sign-In .....................................................4
Cancellation............................................. 106
Check Multiple Passengers..................... 102
Check Single Passenger ......................... 102
Check-in Multiple Passengers................. 104
Passenger Limits.............................106, 112
Standby ................................................... 107
Automated Bag Tags
Check-in Unattached Bags Example ...... 145
Automatic System Checks
Agent ........................................................... 4
Available Restricted Film View Seat
SUD ........................................................... 29
Available Restricted Recline Seat
SUD ........................................................... 28
Available Seat
SUD ........................................................... 28
Available Seat for Unaccompanied Minor
SUD ........................................................... 29
Bag Tag
Expedite................................................... 148
JL List ......................................................160
Manual....................................................... 58
Bag Tag Delete
Agent-In..............................................................6
Agent-In/Agent-Out
Error Response............................................6
Agent-Out ...........................................................6
Aircraft Compartment Limits/Control Messages31
Airline
Encode/Decode .........................................11
Airport
Encode/Decode .........................................11
Amount Over Load Planning Weight
Allowance .....................................................35
SUD ........................................................... 28
Blocked Seat
SUD ........................................................... 29
Boarding Acceptance
APP
SITA Departure Control Services Check In Agent Guide
Index
29 August 2008 Revision 7.2
Page 183
SITA 2008 All Rights Reserved
Boarding Process
USA Watchlist..........................................116
Boarding Status Display.................................175
Booked Display ................................................43
Bulkhead Seat
SUD ...........................................................29
Cancel
APP..........................................................106
CFL Examples..................................................18
CFL Transaction...............................................17
No Segment Information............................21
Check in
ID .............................................................140
NOREC....................................................140
URES.......................................................140
Check In Entry Examples.................................71
Check Multiple Passengers
APP..........................................................102
Check Single Passenger
APP..........................................................102
Checked-In Display ..........................................43
Checked-In Passengers
Upgrade/Downgrade .................................66
Check-in
Unattached Bags .....................................145
Check-In
Dead Head Crew .....................................145
Detailed......................................................61
Detailed Entry...........................................60
Example Check-In of a Multi Sector Flight
with Gender ...............................................61
Example Check-In of a Single-Sector
Flight that does not Require Gender .........61
Example for a Non-Gender Required
Flight ..........................................................63
Gender Required Flights ...........................62
Group.......................................................118
Norec .......................................................120
Oncarriage .................................................69
Page 184
SITA 2008 All Rights Reserved
Passenger ................................................. 43
PDD by Boarding Number......................... 56
PDD by Name ........................................... 55
PDD by Passenger from another Station .. 57
PDD by Seat Number................................ 56
PDD by Standby Number .......................... 56
PDD for Code share Passenger................ 54
PDD with Double Oncarriage Segment..... 54
Seat Map ................................................... 27
Staff Priority Table................................... 169
Standby ..................................................... 49
Standby/Notification .................................. 49
Display Area....................................................... 9
Display Deleted Bag Tags in Passenger
Record........................................................ 158
Display Paging ................................................. 10
Error Responses........................................96
Processing .................................................96
PW Input ....................................................96
PW Output .................................................96
Use and Restrictions .................................96
Delete Unattached Bags ................................147
DOCA............................................................... 79
DOCS............................................................... 79
Oncarriage .................................................69
Deleting a Passenger Item.............................134
Cancel ....................................................... 67
Emergency Exit Seat
SUD ........................................................... 28
Encode............................................................. 11
Entry .......................................................... 11
Encode/Decode
Airline......................................................... 11
Airport ........................................................ 11
City ............................................................ 11
Currency .................................................... 11
Entries to List Passengers with DOCS, DOCO
or DOCA Information.................................... 90
Entries to List Passengers with Missing
DOCS, DOCO or DOCA Information ........... 91
Error Response
Agent Sign-In/Sign-Out ............................... 6
Error Responses
Page 185
SITA 2008 All Rights Reserved
Page 186
SITA 2008 All Rights Reserved
SUD ...........................................................28
Load Planning Weight Allowance ....................35
Oncarriage
Master Flight
Check-In .................................................... 69
Deleting a Bag Tag.................................... 69
NOREC/URES Passengers .................... 122
NOREC/URES Standby Passengers ...... 122
Oncarriage Segments
Example.....................................................23
Master Flight ....................................................23
Modification
Passenger..................................................59
Multi-Page Displays
Overweight Flight
Paging........................................................10
Multiple Areas
Checking in Passengers............................ 68
Overweight Flight with SDD............................. 41
PA Input
Sign-Out.......................................................8
Name Check-in ................................................59
Need Notification..............................................49
PA Subsequent Processing
Example.....................................................51
No Record
Paging.............................................................. 10
Multi-Page Displays................................... 10
Partial Name Check-in..................................... 59
Passenger
NOREC.................................................... 141
URES....................................................... 141
Passenger Acceptance............................59, 124
Check-In .................................................... 59
Passenger Boarding Control.......................... 175
Normal Response
Deleting a Passenger on an Onward Flight137
Deleting a Passenger on Both Flights .....138
Deleting an Onward Flight Before/After
Check-in...................................................138
Numberic Check-in...........................................59
Occupied Seat
SUD ...........................................................28
Office
PS Input..................................................... 97
Page 187
SITA 2008 All Rights Reserved
PS Output ..................................................97
Passenger Handling Procedures
ITCI ..........................................................124
Passenger Limits
APP..................................................106, 112
Passenger Manifest Information ......................79
Passenger Modification....................................59
Pre-upgrade Passengers................................. 66
Check-In .................................................... 60
Printing............................................................. 10
Passenger Updates
USA Watchlist..........................................117
Passenger Withdrawal .....................................59
Passengers
Cancel Pre-upgrade/Pre-downgrade.........67
Pre-upgrade/Pre-downgrade .....................66
Upgrade/Downgrade .................................66
Passengers Checking-In Passengers on an
Overweight Flight..........................................68
Passengers with a Destination or
Residence Address
Checking in ..............................................85
Passport Information at Check-In Time ...........93
Error Responses........................................94
PA Input .....................................................93
PU Input.....................................................95
Use and Restrictions ...........................93, 95
Paxlist
UN..............................................................79
PCTC Parameter..............................................79
PDD
Input.........................................................142
Restrictions ..............................................142
PDD by Boarding Number................................56
PDD by Name ..................................................55
PDD by Passenger from different Station ........57
PDD by Seat Number.......................................56
PDD by Standby Number.................................56
Processing
Page 188
SITA 2008 All Rights Reserved
Stretcner Seats
Recline Seat
SUD ........................................................... 29
System Control and Security ............................. 3
SUD ...........................................................28
Reissue, Boarding Card .................................141
Thru Check In
Search by Bagtag.............................................57
Seat Codes
Thru Check In ..........................................128
Seat Map ..........................................................27
Time Conversion.............................................. 14
Time Out Response ....................................... 135
Transit PAD...................................................... 49
UN Paxlist ........................................................ 79
UN Paxlist Error Responses ............................ 92
Unattached Baggage Check-In...................... 145
Unattached Bags
Check-in .................................................. 145
Delete ...................................................... 147
Display..................................................... 146
Under Check-In Weight Allowance .................. 34
Unprotected Workstation ................................... 3
Update Entry
Passenger ................................................. 67
Upgrade Passengers ....................................... 66
Cancel ....................................................... 67
Upgrade/Downgrade Checked-In Passengers 66
URES ............................................................. 141
URES Check in .............................................. 140
URES Check-In......................................120, 121
URES Passenger........................................... 141
URES/NOREC/ID Check in ........................... 140
USA Watchlist ................................................ 112
Boarding Process .................................... 116
Flight Close Out Process......................... 117
ITCI.......................................................... 115
Passenger Displays................................. 117
Page 189
SITA 2008 All Rights Reserved
Withdrawal
Passenger ................................................. 59
Workstation Information ..................................... 3
Zone Entry with SDD ....................................... 38