Table of Contents |
---|
Info |
---|
This module covers all the different steps on how to accept passengers on a flight followed by the boarding process |
Accepting passengers with contact number
To accept a passenger with a contact number the command is through the SSR PCTC. The structure of the PCTC is:
1PU<item>,PCTC/<CONTACT NAME>/<COUNTRY CODE><PHONE NUMBER>{.<FREE TEXT>}
2PE-<secuence>,PCTC/<CONTACT NAME>/<COUNTRY CODE><PHONE NUMBER>{.<FREE TEXT>}
Example:
PU1,PCTC/JOE SMITH/US12548.PARTNER CONTACT
PU1,PCTC/JOE SMITH/US12548.PARTNER CONTACT
Info |
---|
If there is a PCTC in the reservation, and then another one is entered in the PU or PE, the one entered will be informed in the check-in process. The detailed information of the PCTC is included in the FLT file (version 1.5 onwards) The PCTC will be displayed in the PE, PH and PLC commands with the /* extension (Example: PLC4176/*, see Passenger Lists) |
The use of the contact number depends on the [CTC] PAX CONTACT REQUIRED parameter of the JJCHK table, which allows establishing whether the Check-In system will look for the PCTC information in the PNR or not. The parameter options are:
NO: the system will not look for the PCTC info in the reservation. It will only be included in the PLC and FLT file, if the PCTC is entered in the PU or PE commands.
OPTIONAL: the system will look for the PCTC information in the reservation (SSR PCTC), if it was not entered in the check-in commands. If the PCTC is not entered at check-in, or at the reservation, the check-in can be carried out without inconveniences; it is for this reason that the variable is called Optional.
MANDATORY: the system will look for the PCTC information in the reservation (SSR PCTC), if it was not entered in the check-in commands. If the PCTC is not entered at check-in, or at the reservation, the check-in cannot be performed; it is for this reason that the variable is called Mandatory (this variable is not yet available).
Accept passenger ignoring seat control (not implemented)
Those seats that might have a characteristic that does not allow the passenger to be seated will show a warning message indicating that the seat can’t be assigned, nevertheless the control can be override using different parameters
Note |
---|
The airport agent needs to have the keyword CHKSIC assigned on its profile |
Ignore Only Adults seats
The parameter is ,XSOA
(except seat only adult)
Example:
In this case row 13 doesn’t allow children or infant but when ,XSOA is entered the control is override and the seat is assigned. The action will be reflected on the flight’s history
Code Block |
---|
PV4444/29MAYAEP F C Y 1 2 3 4 5 6 7 8 9 10 11 12 13 14 F A iA A iA A iA iA A A iA iO O E A iA A iA iA A A iA iO O D A iA iA A A iA iO O » = = C A iA iA A A iA · O B A iA iA A iA iA A A iA iO O O A A iA M$ iA iA A i* + iA A A iA iO O O PU2-3,XSOA,ST13FE CHECKIN->XX4444/29MAY AEP ORD CODE NAME FOID OFF CC PARTY NAT. SEAT H.BAG BAG 011. PGOIDW GOMEZ CHAVARRO/PAULA *CHD PP59231817 MDQ YY AB2 13F 0/000 012. PGOIDW RIVAS/GUILLERMO *CHD PP77864788 MDQ YY AB2 13E 0/000 PH4444/29MAYAEP PU #011 GOMEZ CHAVARRO/PAULA SOFIA *CHD PP59231817 CC:YY SEAT:13F BAG:0/0 *BZ: ZONE C *XSOA* 9990210033619C1 MBT:CIERR DOMES AEP-MDQ AEPXX-GL 1528 8MAR21 PU #012 RIVAS/GUILLERMO *CHD PP77864788 CC:YY SEAT:13E BAG:0/0 *BZ: ZONE C *XSOA* 9990210033620C1 MBT:CIERR DOMES AEP-MDQ AEPXX-GL 1528 8MAR21 |
Assign infant passenger to any seat
The parameter is ,XSAI
(except seat assing infant)
Example:
In this case sear 9A doesn’t allow infants but when ,XSAI is entered the control is override and the seat is assigned. The action will be reflected on the flight’s history
Code Block |
---|
PV4444/29MAYAEP F C Y 1 2 3 4 5 6 7 8 9 10 11 12 13 14 F A iA A iA A iA iA A A iA iO O E A iA A iA iA A A iA iO O D A iA iA A A iA iO O » = = C A iA iA A A iA · O B A iA iA A iA iA A A iA iO O O A A iA M$ iA iA A i* + iA A A iA iO O O PU1+4,ST9A,XSAI CHECKIN->XX4444/29MAY AEP ORD CODE NAME FOID OFF CC PARTY NAT. SEAT H.BAG BAG 013. GYSOFL GAVIRIA ARROYAVE/CAR PP 77668229 MDQ YY 9A 0/000 014. GYSOFL INF/INF *INF PP22222 MDQ YY 0/000 PH4444/29MAYAEP/PU ** HISTORY ** * FILTER APPLIED * FLT: XX4444 BRD: AEP SAT 29MAY21 PU #013 GAVIRIA ARROYAVE/CAROLINA PP 77668229 CC:YY SEAT:9A BAG:0/0 *BZ: ZONE A1 *XSAI* 9990210033645C1 MBT:CIERR DOMES AEP-MDQ AEPXX-GL 1613 8MAR21 PU #014 INF/INF *INF PP22222 CC:YY BAG:0/0 *BZ: ZONE A1 *XSAI* 9990210033648C1 MBT:CIERR DOMES AEP-MDQ AEPXX-GL 1613 8MAR21 |
Edit checked passengers
In order to edit passenger information, retrieve the passenger details by sequence number, seat or last name.
Passenger details can be retrieved from the PLC or from the passenger search entry (PF)
The number located after the " - " is the sequence number assigned by the system at the check-in
Search
Note |
---|
DCS system will display the passenger that is stored in memory, en case the info is expired or if you want to make sure you have the right passenger you will have to add the complete flight information after command line PE Example:
|
Search by sequence Number
PE-<sequence number>
Description:
Code Block | ||
---|---|---|
| ||
PE-11 |
PE | Passenger Edit Indicator |
---|---|
- | Dash |
11 | Passenger's sequence number |
Search by seat number
PE-<seat number>
Example:
PE-12A
Search by last name
PE-<last name>
Example:
PE-SMITH
Search by bagtag number
You may search by bagtag number or carrier + bagtag number (6 numeric characters). This type of seacrh works with automatico or semi-automatic bags
PE-BT<bagtag>
Example:
PE-BT005565
PE-BTXX123456
Search by party number
Search using party number
PE-<party number>
Example:
PE-AA4
Search by FOID
You may search using the first characters of foid indication type and space, if it exists.
PE-FO<FOID>
Example:
PE-FOPP12345678Z
Search by frequent flyer
You may search indicating carrier and the firsts characters of frequen flyer
PE-FF<carrier code>/<FF number>
Example:
PE-FFXX/9876
Handling Baggage from an Inbound Flight ( No IATCI )
ADDING INBOUND BAGGAGE DATA
Inbound baggage is the luggage that has been tagged in a previous airport in connection with our flight when there is not an IATCI agreement between carriers.
Once the passenger has been accepted on the local flight with the PU command, add the inbound baggage details using the PE command to generate the corresponding BSM as per IATA Recommended Practice 1745:
PE<Flight>/<Date><Route>-<Item or Boarding Number>,+<Number of Bags>/<Kg>/<Inbound Airline Bag Tag Number>, O |
Example:
PE089/18SEPAEPCOR-2,+1/15/LA123456,HB1/5,O
*HB is hand baggage and it is optional . Token BAF on JJCHK needs to be set as 2.
Considerations:
Actually inbound baggage can only be added using the Passenger Edition command (PE).
The token BAGT must be Y as it is not supported when BAGTS nor if BAGTN.
Bags must be individually added when the passenger has several bags as it is not yet supported adding more than one bag per command (i.e. PE-1,+2/30/LA123456/457,O) and neither when adding the baggage individually on same entry (i.e.:PE-1,+1/10+1/14/LA123456/457,O)
The inbound carrier airline must be on JJDCSOA/* table1 with an active baggage agreement
KIU system checks that bag tag number is not duplicated on the flight and when duplicated, the system will display following warning message: “INVALID - AT LEAST ONE BAG TAG EXISTS IN THE CURRENT FLIGHT" .
Combining inbound baggage with local checked-in baggage on the same entry is not supported (i.e. PE-28,+1/15+1/12/DL000522,O) The system will display error: “ADDING INTERLINE AND ONLINE BAGS AT SAME TIME IN SAME ENTRY NOT ALLOWED". It is not possible to mix inbound baggage informed by a received BTM (Baggage Transfer Message) with an online baggage BSM (Baggage Source Message) informing the airport BRS/BSS of a local checked-in baggage.
Pending to develop the process to control that there is not any unaccompanied baggage at CHKCLOSE but all baggage have been associated to a passenger. This control will be developed when the KIU system automatically processes inbound BTM. Meantime KIU system can generate a copy of the received Inbound BTM by e-mail at airline request.
1 JJDCSOA/* displays the DCS table showing airline interline and/or IATCI agreements with other airlines is explained below. Adding Inbound Baggage for a transit passenger is only available if the Inbound Airline is active on this table meaning there is an active baggage agreement.
Example of Baggage Source Message (BSM)
BSM
.V/1LAEP
.F/XX089/18SEP/COR
.N/045345678001
.W/K/1/15
.S/Y/10A/C/009
.P/BLANCO/A
.L/DACHYB
ENDBSM
BSM | Message Identifier |
.V/1LAEP | Boarding Airport |
.F/XX089/18SEP/COR | Airline Flight Number/Date/Destination Airport |
.N/045345678001 | Only one Bag (8001) and Bag Tag Number |
.W/K/1/15 | Weight/ Kg |
.S/Y/10A/C/009 | Reconciliation Data |
.P/BLANCO/A | Passenger |
.L/DACHYB | Record Locator |
ENDBSM | End of Message Identifier |
DELETING INBOUND BAGGAGE DATA
Once you have searched for the corresponding passenger, use the following entry to delete the previous entered Inbound baggage:
PE<Local Flight Number>/<Date><Route>-<Boarding Number or Item>,-<Number of Bags>/<Exact Number of Kg>/<Inbound Bag Tag Number>,O |
Example:
PE089/1NOVAEPCOR-6,-1/10/LA800457,O
Deleting an inbound piece of baggage will automatically generate a BSM DEL for the Airport BRS/BSS or BHS (Baggage Reconciliation System and Baggage Sortation System) as shown on example below:
BSM
DEL
.V/1LAEP
.F/XX089/01NOV/COR
.O/XX123/01NOV/NQN
.N/999008612001
.W/K/1/15
.S/Y/10A/C/002
.P/A/GOMEZ/LUIS
ENDBSM
BSM | Standard Message Identifier |
---|---|
DEL | Delete |
.V/1LAEP | Boarding Airport is Aeroparque, AEP in Buenos Aires (Argentina) |
.F/XX089/01NOV/COR | Airline Flight Number/Date/Destination Airport |
.O/XX123/01NOV/NQN | Connecting with Airline Flight Number/Date/Destination Airport |
.N/999008612001 | Only one Bag (12001) and Bag Tag Number |
W/K/1/15 | Weight/ Kg/One Bag/15 Kg |
.S/Y/10A/C/002 | Reconciliation Data |
P/GOMEZ/LUIS | Passenger Name |
ENDBSM | End of Message Identifier |
JJDCSOA - lnterline Agreements table for DCS
The command for displaying the DCS table for Interline Agreements between carrier airlines is:
JJDCSOA/*
CARRIER | AIRLINE IATA CODE |
---|---|
ACC | ACCOUNTING CODE NUMBER |
ACT. | ACTIVE YES OR ACTIVE NO |
ALLOW MANUAL INPUT | ALLOWED TO ENTER MANUAL DATA |
AGREEMENT TYPE | EITHER IATCI OR BAGGAGE ONLY |
This table is complemented with the JJIATCI table which is specifically for IATCI agreements. So far there are no entries for configuring the JJDCSOA/* table but at least, it allows the airlines to check their IATCI and BAGGAGE ONLY agreements. KIU can configure if manual flight connections are allowed for Check-in or if only the command BTOA can be used when the connection flights are in the PNR.
PU and PE commands check on these tables from now on. Attempting a check-in when a carrier airline is not present or it is not active on the JJDCSOA/* table will cause the following message: INVALID - NO AGREEMENT BETWEEN CARRIERS .
Same message will be displayed if the carrier airline has an IATCI agreement but the agreement does not exist or it is not active on the JJIATCI.
The JJDCSOA/* is internally related to the JJIATCI table and so will be to the new BTM table not yet developed but as the management circuit is not yet developed, they may not be manually related by mistake. In order to have the visibility when this happens, following message will be added to airline line * NOT EXISTS SETUP DATA *. The display of the JJIATCI table will be like the display of the BTM table when it is developed but the commands could fail when internally unrelated.
The IATA accounting code (ACC) must be the correct one as the code is added as part of the bag tag number when they are generated by the BTM IN.
BTM
.V/1TJNB
.I/BP201/20OCT/GBE/Y
.F/ET1818/200CT/CPT/Y
.N/0074123512002
.W/K/1/3
.S/Y/3B/C/007
.P/A/JOHNSON/SUSAN MRS
ENDBTM
BTM | Standard Message Identifier (Baggage Transfer Message) |
---|---|
.V/1TJNB | Transfer baggage at JNB |
.I/BP201/20OCT/GBE/Y | Inbound Flight Number/Date/Boarding Airport/Class Y |
.F/ET1818/20OCT/CPT/Y | Transfer/Connecting Airline Flight Number/Date/Destination Airport, CPT/Class Y |
.N/0074123512002 | 2 Pieces Of Baggage starting with Bag Tag Number 00741235120 and two pieces 2002 |
.P/JOHNSON/SUSAN | Passenger Name |
ENDBTM | End of Message Identifier |
BAGGAGE MESSAGING HISTORY
Generated Baggage messages can be searched using the following input:
PH<Flight Number>/<Date><Boarding Airport>/MSGBAG |
Example:
PHXX089/01NOVAEP/MSGBAG *** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT BSM *** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT BSM *** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT BSM *** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT BSM *** BTM FOR LA TO BE USED AT COR CONNECTING AIRPORT |
NOTES:
1 *** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT
NOT SENT DUE TO MISSING CONFIGURATION // AT 2023-09-07 18:32Z *** (BSM message was generated but could not be sent due to missing BSM destination address or any other configuration data// Date and GMT Time).
2 *** BTM FOR LA TO BE USED AT COR CONNECTING AIRPORT
SENT BY TTY TO FRABM1C // AT 2023-09-07 18:59Z *** (BTM message was generated and sent to the teletype address FRABM1C// Date and GMT Time)
So far there are two filters available for a more accurate baggage message search on the PH history. The first one is the BSM and the second one is the BTM. For more accuracy, both filters can be also combined with the bag tag number or numbers.
For a more accurate search, bag tag numbers can be also added to the command as shown below:
PH<FLIGHT NUMBER>/<DATE><BOARDING AIRPORT>/MSGBAG<6 BAG TAG NUMBERS FOR ONE BAG+ 6 OR10 BAG TAG NUMBERS FOR ANOTHER BAG> |
Example:
PHXX089/01NOVAEP/MSGBAG008612+9990008647
MESSAGES GENERATED FOR BAGGAGE SORTATION/RECONCILIATION
FILTERED FOR BAGTAGS: 008612+999008647
*** BSM FOR XX TO BE USED AT AEP LOCAL AIRPORT
NOT SENT DUE TO MISSING CONFIGURATION // AT 2023-09-07 18:32Z ***
BSM
DEL
.V/1LAEP
.F/XX089/01NOV/COR
.O/XX123/01NOV/NQN
.N/999008612001
.W/K/1/15
.S/Y/3A/C/006
.P/A/CORNQN MR
ENDBSM
PH<Flight Number>/<Date><Boarding Airport>/MSGBSM |
The second filter is for BTM message:
PH<Flight Number>/<Date><Boarding Airport>/MSGBTM |
Example:
The type of baggage message can be combined with the bag tag number/s as for more accuracy:
PH<Flight Number>/<Date><Boarding Airport>/MSGBSM<6 Bag Tag Numbers for one bag> +<6 or 10 Bag Tag Numbers for another bag> |
PHXX089/18SEPAEP/MSGBSM123456+0552345670
Accepting baggage in connection with other airlines flights
If an airport agent needs to accept and print a bag tag for a connecting flight with another airline, here are the steps to follow.
Note |
---|
Only valid for flights with automatic bag tag printing (check Control Panel BAGT:Y) |
In order to activate this feature parameter POA - ALLOW PRINT WITH OTHER AIRLINE SEGMENTS
must be turned on at JJCHK table, please contact our helpdesk at host@kiusys.com or contact your account executive. Available configurations are:
Y: it allows to print only those flights that are present in the passenger itinerary.
N: it does not allow to print segments from other airlines
M: it allows manual input of flights from other airlines which are not on passenger itinerary besides the ones that are present in the passenger itinerary.
Accepting baggage in connection with other airlines flights on passenger´s itinerary
An airport agent should follow these steps for issuing bag tags for connecting flights which are present on passenger's itinerary and when there is not an IATCI agreement between the airlines.
Accept the passenger in all the flights but without adding any piece of baggage
Edit the passenger adding the baggage information, this action will add the bags to the online flights as well as those offline . Token is
,BTOAO<amount of connecting segments>
Connecting segments are those segments shown as outbound ./O on the passenger search (Command line PC) and without considering the online segments
PE<flight>/<date><route>-<sequence number>,O,BTOAO<number of connecting flights>,+<bag quantity>/<weight>
Example:
Code Block |
---|
PF119/25JULMVDAEP-DE CAMPOS CHECKIN-M> XX 119 /25JUL MVD ITEM CODE NAME FOID OFF ST CC SEAT NAT. BAG.ALLOW KAM FF #009* DRBDFJ DE CAMPOS/CECILIA AEP 11A .O/HK XX006 Y 25JUL SU AEPCOR 0800 1000 .O/HK AR667 Y 26JUL MO CORSCL 0700 0800 .O/HK AR618 Y 26JUL MO SCLLIM 1100 1300 |
Code Block |
---|
PE119/25JULMVDAEP-9,BTOAO2,+1/20,O CHECKIN-> XX119/25JUL MVD ORD CODE NAME FOID OFF PARTY NAT. SEAT H.BAG BAG #009. DRBDFJ DE CAMPOS/CECILIA AEP 11A LIM 1/020 (>XX005867) MBT:CIERRE INTERNAC ALL -> XX 006/25JUL AEP COR - UPDATED OK #003 >ST: 11A >BT: 07:00 >GATE: >ET: SEGMENTS VALID ONLY FOR BAGTAGS -> AR 667/26JUL COR SCL ### NO THROUGH CHECK-IN |
Info |
---|
Bag tag data is saved on flight history with the legend The BTOA indicator can only be used when checking-in the first bag/s because the KIU system assumes that all bags' final destination is the same as using the same combination. This is the reason why the route is entered only once for checking-in the first bag but additional bags will be automatically addressed to the same destination. Accepting baggage in connection with other airlines generates a BTM or Baggage Transfer Message as per IATA Resolution 709 , RP 1745. |
Warning |
---|
This option can only be used if there is not a previous piece of baggage accepted for that passenger, otherwise the system will respond with the following error message:
When adding offline flights that create a mismatch because flight arrives and departs from different airports , the system will display the following error message:
|
Accepting baggage in connection with other airlines flights not included on passenger´s itinerary
Please follow these steps for issuing bag tags for connecting flights that are not present on passenger's itinerary:
Accept the passenger in all the flights but without adding any piece of baggage
Edit the passenger adding the baggage information, this action will add the bags to the online flights as well as those offline (flight segments that are not on passengers itinerary). Token is
,BTOA
(bag tag other airlines) followed by carrier code, flight number and destination airport. If needed, multiple connecting flights can be added if separated by a period (.)
PE<flight>/<date><route>-<sequence number>,O,BTOA<carrier code><flight number><destination airport>.<carrier code><flight number><destination airport>
Example:
Code Block |
---|
PE4444/29MAYAEPMDQ-13,O,+1/1,BTOAAR4545LPB.LA41+LIM.LA325MIA.AA1578JFK.AA1945LAX CHECKIN-> XX4444/29MAY AEP ORD CODE NAME FOID OFF PARTY NAT. SEAT H.BAG BAG #013. GYSOFL GAVIRIA ARROYAVE/CAROL PP 77668229 MDQ 9A LAX 1/001 (>XX005809) MBT:CIERR DOMES AEP-MDQ SEGMENTS VALID ONLY FOR BAGTAGS -> AR4545/29MAY MDQ LPB ### NO THROUGH CHECK-IN / SEGMENT MANUAL INPUT -> LA 041/30MAY LPB LIM ### NO THROUGH CHECK-IN / SEGMENT MANUAL INPUT -> LA 325/30MAY LIM MIA ### NO THROUGH CHECK-IN / SEGMENT MANUAL INPUT -> AA1578/30MAY MIA JFK ### NO THROUGH CHECK-IN / SEGMENT MANUAL INPUT -> AA1945/30MAY JFK LAX ### NO THROUGH CHECK-IN / SEGMENT MANUAL INPUT |
Info |
---|
Flight number must be between 1 and 4 characters. Next day flight can be marked by adding a plus sign after flight number or a minus sign to mark previous day flight. Example Bag tag data is saved on flight history with the legend The BTOA indicator can only be used when checking-in the first bag/s because the KIU system assumes that all bags' final destination is the same as using the same combination. This is the reason why the route is entered only once for checking-in the first bag but additional bags will be automatically addressed to the same destination. Accepting baggage in connection with other airlines generates a BTM or Baggage Transfer Message as per IATA Resolution 709 , RP 1745. |
Warning |
---|
This option can only be used if there is no previous baggage accepted for that passenger, otherwise the system response will be:
Up to 6 flight connections, including the online flight segment are accepted. When necessary, two linked bag tags will be issued as otherwise the system will display following error: If any incorrect data for the other airline flight is entered, the system will display an error message related to the wrong data (missin carrier code, non-numeric flight, invalid airport, etc)
|
Passenger edition using using 2D/QR scanners
You can use a 2D/QR scanner to invoque and display the information from a passengers boarding pass, the command line is
PE-R
The intimidate response changes according to the environment where it's executed:
CUTE airports (SITA-ULTRA-ARINC-RESA): the command line awaits for the boarding pass to be scanned
Code Block |
---|
PE-R WAITING BOARDING PASS .... |
Info |
---|
The reader used in the CUTE environment might be overrride using the following commnad line. This action forces the behaviour emulating this functionality on an NON CUTE airport
IMPORTANT: this commnad lines only overrrides the configuration, we can´t guarantee the correct funtionality as the environment is controlled by a common use platform that might reject the use of an external peripheral |
NON CUTE airports: the command line executes a pop-up windows that enables the use of the scanner, bare in mind that this pop-up is single use, one scan at the time, instead of multiple scans used at boarding process. Every time the airport agents wants to use the scanner the command line should be triggered. In order to use this feature the agent should be using KIU v1.700.102 or higher and PBR2 option must be set up on the Readers Setup in table JJCHK
The information displayed on the screen is the same for both environments, a search by sequence number is displayed along with a combinad line ready to be used with the variables the airport agent may need
Example:
Code Block |
---|
PE-R CHECKIN-> XX4444/12JUN mad ORD CODE NAME FOID OFF PARTY NAT. SEAT H.BAG BAG #001.w IYCYKD SMITH/MERY PP21321546 EZE 11C 0/000 MBT:GATE CLOSES 15 MINUTES BEFEORE DEPARTURE ** PRE-CHECKED PASSENGER ** ENTER FOLLOWING COMMAND TO EDIT CHECK-IN INFORMATION PE4444/12JUNMADEZE-1, |