CAPÍTULO V PRODUCTO
5.2 MARCA
The PU transaction can add initial passport information to a passenger record with a PSPT item after a passenger has been accepted on the flight, or to amend existing PSPT information. An OCR
document scanner can accept PSPT information.
PU Use and Restrictions
A PU transaction requires a prior PDD or PS display.
If a PSPT item is already present in a passenger record but needs to be updated with a new PSPT item, a PW entry will need to be used to delete to the old PSPT item and then updated using the PU entry.
PU Input
The PSPT item is input with the PU transaction as are other passenger handling items in the following format:
►PU: entry nbr,PSPT/passport details
Details for the PSPT item are listed below. An oblique follows all items (numbered 1 thru 8).
PSPT/ Mandatory
1. passport number Mandatory maximum 35 characters 2. IATA country code of issue Mandatory Two or three-alpha characters 3. date of birth Mandatory da/mon/yr (e.g., 01JAN50)
4. gender code Mandatory M - male
F - female
5. surname Mandatory
6. first name Mandatory
7. expiration date Optional da/mon/yr (e.g., 01JAN06) 8. Nationality Mandatory Two or three-alpha characters Example of the PSPT input on a passenger without an expiry date:
An oblique follows all passport details. If the optional expiry date is omitted, oblique’s are consecutive. For example a passenger with a PSPT remark where the expiration date is omitted:
►PU:1,PSPT/P094158760/US/22MAR57/F/SMITH/MARY//US Example of the PSPT item added with all details entered.
►PU:1,PSPT/P04126490/US/20AUG65/M/SMITH/JOHN/01JAN06/US
If an OCR document scanner processes the passports, then the PSPT item is input with the PU transaction in the following format:
Page 96
© SITA 2008 All Rights Reserved
SITA Departure Control Services – Check In Agent Guide Passenger Acceptance / Modification / Withdrawal 29 August 2008 – Revision 7.2
1
Example of the PSPT DOB entry:►PA:1,PSPT/B/20AUG65/SMITH/JOHN
PSPT DOB can also be used for an infant by adding an “I” after PSPT.
1
Example of the PSPT DOB entry for an infant:►PA:1,PSPTI/B/20AUG65/SMITH/ANGELA
8.2.16 Deletion of PSPT Remark
The PW transaction can delete a PSPT item from a passenger’s record.
PW Use and Restrictions
The PW transaction is allowed after a prior PS, SB or PDD display.
.
PW Input
A PW transaction can delete a PSPT item from a passengers record with the following format:
►PW:1,PSPT/ALL
1
Example of a transaction to delete one of the PSPT items on multi-passenger record.►PW:1,PSPT/1
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 The format of the PSPT deletion is incorrect.
Modification Not Possible There is not a PSPT item to delete in this passenger record.
Table 8.12 Delete PSPT Remark Error Responses Subsequent Processing
All processing not specifically mentioned remains unchanged.
8.2.17 Passenger Handling Displays PS Display
Passengers with passport remarks are easily identified with the PSPT items on the PS display for each passenger having passport remarks.
PS Input
1
An example of the PS input, with PSPT as the option.►PS:FLT/DATE/CLASS,PSPT PS Output
1
An example of a PS list sorted with the PSPT item is shown below:PS: XS500/29AUGXATL,PSPT OP/NAM DC9/JRAM GTD/???? POS/GATE BDT1730 SD1800 ED1800 1. 2CHARLES/MR BN002 SN27C Y JFK MSG PSPT CHARLES/MRS BN003 SN27B Y JFK PSM 2. 2CURIE/PIER+ Y JFK PSPT CURIE/MADA+ Y JFK PSPT 3. 1DOUGLAS/KIRK BN001 SN14F Y JFK PSM MSG PSPT 4. 1EINSTEIN/ALBE+ Y JFK PSPT 8.2.18 PDD Display
Each passenger record shows the PSPT remark, much as the other special remarks or items are displayed.
1
An example of the output when a PSPT item is present in the passenger record is shown below.8.2.19 Boarding Pass Inhibit for APIS Flights
The ability to inhibit boarding pass issuance until all required APIS data is entered in the passenger’s record is available on all APIS flights. The SITA Helpdesk should be contacted to set the Boarding Pass Inhibit parameter. In addition, segment data for the city pairs requiring boarding Pass inhibit should be added to the CSM for each flight requiring this function. For information on adding segment data to the CSM see the Check-in Supervisor User Guide.
8.2.19.1Crew Mask Entries
Some countries may require travel document and other information for crew members. This
PDD:1 PDD: XS500/26AUGYATL,1 1. CHARLES/MR BN004 SN10C Y MSP BAG1/10/0 CHARLES/MRS BN005 SN10B Y MSP ACC VDT965 AGT1/26AUG1406 PSPT-CHARLES/RAYMR/P123456/GB/01JAN50/M/01JAN06 CHARLES/RAYNELMR
Page 98
© SITA 2008 All Rights Reserved
SITA Departure Control Services – Check In Agent Guide Passenger Acceptance / Modification / Withdrawal 29 August 2008 – Revision 7.2
*Personal Information
Surname:________________________________________
Given/Middle Name:___________________ / _________________________
Gender:_ Nationality:___ Birth date: _______
PCTC: ______________________________________________________________
Residence country:___ Address Details:___________________________
ZIP/Postal Code:____________ City:_________________________________
State/Province/Country:_______________________________
Final Destination:___ Birth Place:_____________________________
Crew Status:___ Crew Title:_________________________
*Document Information
P = Passport C = US Resident card
M = Military-ID T = US Re-entry permit A = Alien registration card Document type:___ Expiration date:_______ Country of issue: ___
Document Number:__________________________________________
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:________________ 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
Crew information will vary according to government requirements. Above is an example of a completed crew mask based on inbound flight requirements for the US.
To display a list of crew members, us the PS entry:
PS:FLT/DTE,CREW
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 100
© SITA 2008 All Rights Reserved
SITA Departure Control Services – Check In Agent Guide Passenger Acceptance / Modification / Withdrawal 29 August 2008 – Revision 7.2
1
PDD displays as follows:PDD:01 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:___ 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
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
CREW:XS 0047 /13SEP07 /JFK 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
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
8.2.20 Advanced Passenger Processing System (APP)
Every passenger traveling into, out of, or through an Advanced Passenger Processing (APP) country is screened for authorization to board before a boarding pass is issued. This can include travel inbound to, outbound from or transiting an APP participating country. At this time the participating countries are Australia, New Zealand, Kuwait and Bahrain. The flight data can include information on a series of flights and ports on an international itinerary. The APP can involve passengers traveling on up to three separate flights and four separate ports.
Page 102
© SITA 2008 All Rights Reserved
SITA Departure Control Services – Check In Agent Guide Passenger Acceptance / Modification / Withdrawal 29 August 2008 – Revision 7.2
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
The normal passenger check-in entry is:
►PA:1, DOCS/P/USA/T67778/USA/12jul67/M/12JUL15/SMITH/JOHN
Note: To trigger the APP query DOCS or PSPT entries can be used.
8.2.21.2 To Check Multiple Passengers:
Use the PS List (e.g., PS:XS123/., NAMBERRY;NAMALVAREZ):
► ps123/+,NAMBERRY;NAMALVAREZ
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 SA2300 FT0800 1. SMITH/JOHN BN003 SN21D
WARNING - APP FLIGHT - PSPT DATA -
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 FT0800 1. 1SMITH/JOHN BN003 SN21D Y SYD APP
-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 FT0800 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 FT0800 1. SMITH/JOHN BN003 SN21D
APP TRANSACTION IN PROGRESS AU APP* (0502) OK TO BOARD/BN3
Page 104
© SITA 2008 All Rights Reserved
SITA Departure Control Services – Check In Agent Guide Passenger Acceptance / Modification / Withdrawal 29 August 2008 – Revision 7.2
8.2.21.4 Check-in of Multiple Passengers - Partial Acceptance by CPS System.
Boarding pass printing is suppressed for any passenger not receiving authorization to travel.
1
Example: Where one passenger receives OK and the other Not OK:1. SMITH/TMR BN050 SN14A *Australia APP * OK TO BRD/BN050 2. TALBOT/KMRS BN051 SN14B Australia APP * DO NOT BRD/BN051 *Australia APP Transaction in Progress ***Delete passenger***
► PW-2,APP
In this case, the boarding pass for BN050 is printed, but not for BN051. The response from CPS System displays under each passenger name.
In addition the ► symbol ►PW-2,APP (for second passenger) transaction is presented to delete the passenger, if necessary.
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 and the
passenger is granted clearance to board.
DO NOT BRD (D) 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 country’s regulations, the Do Not Board directive may be overridden by the check-in agent.
DO NOT BRD (X) All data required to assess the passenger is available and the passenger is denied clearance to board. The check-in agent cannot override this directive.
Miscellaneous Messages (U) Unable to determine the passenger status. The passenger identity cannot be uniquely determined because multiple records match the supplied data or there is a problem with database. Supply more
specific passenger data to allow the system to assess the passenger. If this fails, get advice from the government agencies.
Miscellaneous Messages (I) Insufficient data is available for an assessment. Provide additional passenger data.
Miscellaneous Messages (E) Error is detected. Correct the error.
Table 8.13 APP Query Responses
Page 106
© SITA 2008 All Rights Reserved
SITA Departure Control Services – Check In Agent Guide Passenger Acceptance / Modification / Withdrawal 29 August 2008 – Revision 7.2
8.2.21.5 Passenger Cancellation Normal DCS processing for a PW applies.
1
Example of cancellation of a previous APP (ok to board) passenger:► -pw:-1
-PW: XS7777/20OCTYSYD-1 AV C12Y138 PAD C0Y0
320/A GTD/???? POS/GATE BDT1130 SD1200 ED1200 SA2300 FT0800 1. SMITH/JOSEPH DELETED
APP TRANSACTION IN PROGRESS AU APP* (8505) CANCELLED/BN1
8.2.21.6 Limits on Number of Passengers
The APP application allows queries for up to five passengers at a time. Thus, if the Airline
configuration for APP is set, SDCS will not check in more than five passengers at a time. For PW the limit is the same.
If more than the limit is attempted, SDCS returns:
(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 LMTS Y MEL URES IDID00S101 APPB-AU /8501/OK TO BOARD
-
Or if the response is negative:
* AUSTRALIA APP TRANSACTION IN PROGRESS
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 108
© SITA 2008 All Rights Reserved
SITA Departure Control Services – Check In Agent Guide Passenger Acceptance / Modification / Withdrawal 29 August 2008 – Revision 7.2
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 -
Note: To override infants, the transaction is the following:
PU:1,INFAPPG/NZ/FREE TEXT PU:1,INFAPPA/NZ/FREE TEXT
8.2.21.9 Re-sending APP Message
To clear some of the passenger status we can try to re-send the APP message with the following transaction after PDD display:
PU:1,APP
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 12JUL OUT 15JUL CTCH-HAN-SUNNY HOTEL-IN 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:-
8.2.21.10 Status Codes
After check-in the passengers can have the following status:
• 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 110
© SITA 2008 All Rights Reserved
SITA Departure Control Services – Check In Agent Guide Passenger Acceptance / Modification / Withdrawal 29 August 2008 – Revision 7.2
8.2.21.11 DFL Prohibited
DFL for any APP flight is prohibited. If a DFL is attempted for an APP flight where check-in has taken place, the following warning will be displayed:
DFL:781/./ALL
805 - APP FLIGHT - DFL NOT PERMITTED -
Note: Contact SITA Helpdesk staff to DFL any APP flight.
8.2.21.12 CREW Check-in
APP will be sent when the crew mask is completed and entered after the required fields. If an override is necessary the information is entered as shown below in the example:
CREW:MH 0141 /19MAR08 /SYD Delete crewman:_
*Personal Information
Surname: PILOT______ Given/Middle Name: JOHN_ /_____________
Gender: M Nationality: AUS Birth date:10JUN65 PCTC: ______________________________________________________________
Residence country: AUS Address Details: 10_ANY_ST____________________
ZIP/Postal Code: 54331____________ City: SYDNEY_______________________
State/Province/Country: AUS___________________
Final Destination: SYD Birth Place: AUS______________________
Crew Status: CR1 Crew Title: PILOT___________
*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: 22JUN10 Country of issue: AUS Document Number: 49842938498________________________
VISA Number: __________________________ Issued for country: ___
VISA Issue Date: _______ Place of Issue: _____________________________
Airline or Gov Override Indicator (APP only): G Override Country: AUS Authorized by:PER_AU_AUTH_221321_______________________________
*Pilot Information (UN PAXLST only)
License number: ____________________ Country of issue:___
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
Below is an example of an AQQ transaction using Passenger Acceptance (PA) receiving an OK TO