KIU_Space_Control_Manual

INVENTORY

1. Full flight inventory

The complete entry to view the inventory of a flight is as follows:

VIEFLIGHT / DATE ALL * ALL * indicates the complete flight with all the indicators

Example 1: Single stop flight

FLT  : 462           Flight 462

737                  Equipment

DATE : 20MAR18 TUE   Requested Date

JNB/18:15            Origin/Departure Time             

HRE/20:40            Final destination and arrival time  

/Z2                  Difference with Zulu time from the origin

22D                  Number of days left for the flight

BRD	                 Boarding city

OFF	                 Deplaning city

Cl                   Booking Classes

AC                   Aircraft Capacity

AU                   Authorized by cabin (It can be the real one according to the capacity of the equipment or modifiable based on the applied overbooking logic)

BS                   Space Block applicable per cabin and per section

SA                   Number of seats available per class (according to what was sold, authorized and allowed by sales limits,space block or overbooking.

SS                   Number of seats sold per class

 AS	                 Total seats sold by segment

ABS                  Total seats sold per segment (LEG)

WL                   Waiting list quantity by class

                    
 
WWL                  Amount of limit allowed for waiting list (if it is at 0 or when it reaches its limit allowed, a letter C (closed) will appear in the WL column)

LS                   Sales limit per class

LSS	                 Modified sales limit by nesting 

NG                   Group of classes with nesting (All those that contain the same indicator belong to the same group and they discount each other

-L-                  Nesting Level in classes (Order of hierarchy that gives the nesting, 1 is the header descending in importance)

OS					 Amount authorized for overbooking

-LOS                 Applicable overbooking logic

TSO                  Number of days and hours when opening of classes will take place before the start of the service

TSC                  Number of days and hours the classes will be closed before the start of the service

ST                Class status (if it is closed, indicator C appears or on request R, A V indicator may also appear, which warns that the PNRs of such classes will have automatic expiration.

Example 2: Flight with two or more stops

2. Inventory options

2.1 By airport

You can request an inventory from a particular airport on the route: The command is:

VIE4900/05NOVCOR	
COR indicates only segments from COR

VIE4900/05NOV	
Only if the origin of the terminal you are requesting is AEP, is it not necessary
clarify the departure airport

Note:
If the terminal that is requested in the VIE entry is from the origin, it can be ignored.

2.2 From an availability display

You can request the inventory from a previously displayed availability. The command is:

VIEA Item number

In this case,the origin is considered from the origin city of the  requested availability.

2.3 From an itinerary of a PNR

You can request the inventory from a previously displayed PNR. The command is

VIEP Item Number

In this case,the origin is considered from the  boarding point of the segment.

2.4 Display  unconfirmed sales 

VIE {flight} / {date} / SS (see Example 3)

System displays seats in each route that are being taken at that time but still not recorded  in the PNR.

SEGMENT SELL DETAILS

                                         AEP/BRC Y 2

                                         AEP/MDQ Y 3

Example 1

Example 2

Example 3

This example indicates that seats are being taken  without recording 2 on the AEPBRC leg and 3 seats on the AEPMDQ leg

2.5 Display unconfirmed sales lists

You can generate a list of unconfirmed sales, that is, those PNRs that are not closed and that are  in the creation process.

To verify the list, you must enter the following command and you must have Duty 8  in your user  signature .

VSSLIST

When performing this command, the system will respond the following information:

Description:

Notes:
System will show those seats that have been taken for more than 10 minutes and still  have not been recorded ,and after 25 to 30 minutes of inactivity will then be released.

2.6  Force Release of Unconfirmed Sales

You can force the release of seats taken by travel agencies using the following process:

VSSLIST/I/LIMI028001

Considerations:

•  The seat will not be ignored at that moment, but the system will advance the time to 25 minutes, so that when the "ignore" process occurs, those seats are ignored more quickly.
• This ticket can only be made for agency terminals

• The maximum time  allowed for  taking seats would go from +/- 25 minutes to +/- 15 minutes, since at 10 minutes appears in the list, when ignoring, you must wait for the process to run, which will be within the 5 minutes later

3. Inventory History

Once flights are created, a copy of how it was created  and every modification is kept in the flight history. Keep in mind that when a flight is split, the system deletes all indexes placed manually (Space Control VM commands) saving only those that have been placed by schedule change (KS commands).

The command to see the flight history is:

VIH{flight}/{date}

The display shows a copy of the inventory at the time it was created, with the indexes of the equipment . Changes occured in the indicators will be recorded in the history.

Example

There were some changes to the indexes of this flight that are being reflected in the history . For example, In the first change the flight was retrieved to be canceled:

 The command made is shown , also the terminal from where it was made and the agent, time and date of the execution. Also the modifications made by space control or flight loading  can be seen reflected as follows:

In the changes made with flight loading commands such as the KS, only the index that identifies  the change and the rest of the command made, in the space control (VM) appears the
complete command In the end, the agent, time and date of the execution will always be displayed.

The VIH of a flight will remain in the system until 48 hours after the operation of the flight, then will be removed from the system.

4. Departures and arrivals information

This command allows you to view the departures and arrivals of flights individually or in groups, by airport or by sections, showing the operation with their schedules and occupation by legs.

The options are the following:

• Complete Schedule:
  
  

VLC*ALL

VLC*ALLALL

• By flights:

         This command allows you to visualize by flight, operation and occupation.

 
VLC * Flight                           By flight number, a single flight

VLC * Flight * Flight                 By flight number, several at a time

VLC * Flight / Optional Date          with date of departure (if date is not specified, it defaults to today´s date.)

This command shows the flights sorted in ascending order by flights numbers .

• By segments

This command allows you to visualize by segment, the flights that are operating between the segment requested for a specific day. If no date is indicated the default is the current day.
You can replace one of the airports with the word ALL, this will indicate that the request will be the departures from a specific airport to all possible destinations or vice versa, from all
destinations to a specific airport.

VLC*AEPCOR/23MAR

Unlike the flight option command, a TIME column is shown at the beginning, which indicates the order of the flights by departure time from the requested segment.

In case a request is made from all airports to a specific one, the order will be given by the schedule of arrival at the specific airport. For example:

• By airport

This command allows you to visualize all the departures and arrivals of a specific airport. If no date is enter it defaults to the current day.

VLC*AEP

Unlike the  command option by segment, it shows an ST column after the TIME column, which indicates whether the flight leaves the requested airport (OUT) or arrives at the airport (IN).
In the case of circular flights, they will be shown twice, once when it takes off and once it lands. See in the example the flights 4134, 4320 and 4390. In the latter you can see that it departs
at 2330 and arrives at 0330 + 1, that is, the next day. The reason is that the commercial date of it is the day of the request. Therefore, it will enter within the requested date and not the next day.

5. Sales information by class and business parameters

There is a command to view sales inventory by class only. This command gathers characteristics of a flight inventory but only showing sales by classes and their indicators corresponding to the merchandising The command is:

VIS {flight} / {date} ALL

The header shows the same data as the inventory (VIE) and the indicators are the following:

Options:

You can use the minimum input command that would be:

VIS{flight}

Using this command, it defaults to the current day and the origin  airport only. It can also be requested by specific airport.

Example

6. Total Sales Information per cabin

There is a command to display total sales per cabin. This command shows the partial booked seats by segment and by cabin and the booked per cabin.

. 

VIL {flight} / {date}

Options:
You can use the minimum input command :

VIL {flight}

Using this command, it defaults to the current date and the airport of origin only. It can also be requested by specific airport.

Example:

7. Catering information

This commands displays amount of services that will have to be provided for a specific flight.

VCC {flight} / {date} {route}

Example:

The options for the request of the lists can be the following:

VCC {flight}    When no date is specified it defaults to current day. 
VCC {flight} / {date} Specific date
VCC {flight} / {date} {BRD} Specific date and origin

8. Occupancy per route

Through this command you can see at first glance the number of flights offered by a route by date or by parameter of dates and its general occupancy The input command is:

VAF {route} / {date}

Example: 

Note

The order of flights is according to your departure time.

You can also make the request for a date parameter. The command is:

VAF {route} / {date-date}

Example

The  flights order is by date and within the date, by departure schedule.

VAF entry  can be requested to verify some flights in particular:

VAF {route} / {date-date} * {flight}, {flight}

Example

Note: You can verify up to 5 flights  per command and each of them  must be separated by commas.

 VAF entry can be requested by verifying the information of a particular cabin only (F: First Class; C: Business Class; Y: Economy Class):

VAF {route} / {date-date} * {cabin}

Example: 

 VAF entry  can be requested by verifying flight information for the specified days of the week:

VAF {route} / {date-date} * {day of the week}

Example

Notes:
The indicators of the days of the week are the following:

MO Monday 
TU Tuesday 
WE Wednesday
TH Thursday 
FR Friday 
SA Saturday 
SU Sunday 

These  indicators can be combined to request flight information on some days of the week:

Example: VAFAEPCOR / 01JAN-09JAN * MOFR (flights on Mondays and Fridays).

The different filters can be combined with each other as shown below:

VAF {route} / {date-date} * {flights} * {cabin} * {frequency}

Example

8.1 VAF with primary compartment class closed

You can view if primary compartment classes are closed by adding the /C parameter at the end of the entry.

VAFEZEMAD/16FEB/C

The  / C filter can be used with any of the command combinations (date range, flight specific, days of the week) It also supports export to .CSV format.

The information contained in the VAF can be exported to a CSV file (file separated by commas)  adding the extension -CSV at the end of the entry

VAF {route} / {date-date} * {flights} * {cabin} * {frequency} -CSV

Inventory Control

The commands listed below are used for the commercial management of flights. You can apply to particular flights or flight parameters.

Important
Keep in mind that any of the actions applied by the Flight loading module , after the inventory control commands, will be reflected replacing the setting previously configured during  the flight creation.

1.  Sales limits Control

Sales limits can be controlled manually from fixed commands. You can set or remove sales limiters on any of the flights that are operational, whether or not they have limits prefixed in the flight load. The indicator will be reflected in the flight inventory under the acronym LS.

The command is:

1.1 Set Sales Limits

To set sales limits, the command is as follows:

VMLS {flight} {class} {date} {route} {index}

Example:

Response

DONE

1.2 Remove sales limits

To remove sales limits, the command is similar, adding  the words OPEN , GO or ON in the index.

Example

1.3 Close sales limits

To close the sales limits, the same previous command is executed but adding CLOSE or STOP or OFF, or the digit 0 (zero). in the index.

1.4 Options

You can set sales limits  to all classes ,or fight  segments  by date period.

• Per period of dates and days of the week

VMLS4118K18MAR25MARAEPSLA10MOTUWETHFR

Note:

Two digit code is used for days of the week.

MO Monday,TU Tuesday, WE Wednesday, TH Thursday, FR Friday, SA Saturday and SU Sunday.

The start and end dates are added together,then the index, and  every single day  will limit sales in the specified , together. If the day. If no date is specified the command works for all the operational period of the flight.

•  By classes
  
  

VMLS4118*22MARAEPSLA10MO

If an asterisk (*) is added instead of the classes will have effect on all classes.

• By flight segments

VMLS4118K22MARALLALL10MO

ALLALL is added instead of the segment, thus acting on all segments of the flight.

Note: You can combine all the options or just some of them.

Example:

All classes, by dates parameter, all  flight segments of the departing from AEP and all days of the week.

2.Wait List Control 

The waitlist can be closed, open or limited . The indicators will be reflected in the flight inventory under the acronym WLL. The commands to handle it are:

2.1 Close the Waiting List 

VMWL {Flight} {Class} {date} {route} STOP

Example:

Response

DONE

Note:
The STOP or CLOSE or OFF indicator can be used

2.2 Open the waiting list

VMWL {flight} {class} {date} {route} GO

Example:

Note:
The GO or OPEN or ON indicator can be used

2.3 Limit the waiting list

VMWL {flight} {class} {date} {route} 10

Example:

Response:

DONE

Note:
When closing or when the limit is reached  the waiting list will appear in the flight inventory (VIE), next to the WL counter of each class a letter C, which will indicate that it is closed. When it is reopened
the letter C disappears.

.4 Options

The same commands can be loaded for all flight classes, for all segments, by a range of dates and certain days of the week. This would avoid loading the indicators one by one.

The combined input command is:

VMWL 4118 * 15MAR31JUL ALLALL STOPMOTUWEFR

3. Closure Control and Class Opening

You can close or open the classes of a flight, a particular segment or an entire flight . The function is to hide that class and inhibit the sale. The indicator will be reflected in the inventory of the flight under the symbol ST with a C (Close).

This function does not prevent overbooking or reaccomodation by a schedule change.

3.1 Close the class of a flight

VMCL {flight} {class} {date} {route} STOP

Example

Response:

DONE

Note:
The STOP or CLOSE or OFF indicator can be used

3.2 Open the class of a flight

VMCL {flight} {class} {date} {route} GO

Example;

Response:

DONE

Note:
The GO or OPEN or ON indicator can be used

3.3 Options

The same commands can be loaded for all flight classes, for all segments, by a range of dates and certain days of the week. This would avoid loading the indicators one by one.
The input command is:

VMCL 4104 / 31MAR31JUL ALLALL STOPMOTUWEFR

.4. Class requirements Control

A class can be set for request only even though there are seats available . This function allows to control sales orders.Each sales request will be entered with HM code (required) in
the PNR and it will automatically be sent to queue 20 or 21.
In availability, the class that is found with this indicator will appear with a letter R. The indicator will be  will reflect in the inventory of the flight under the acronym ST with an R (Required)

4.1 Set a Class in Request Mode.

VMRQ {flight} {class} {date} {route} ON

Example:

4.2 Remove a Class in Request mode .

VMRQ {flight} {class} {date} {route} OFF

Example:

Response

Note:

The OFF or CLOSE or STOP indicator can be used

4.3 Options

The same commands can be used for all flight classes, for all segments, by a range of dates and certain days of the week. This would avoid adding the indicators one by one and setting a
flight or several as request status.

The input command is:

VMRQ 4104 / 31MAR31JUL ALLALL ON MOTUWEFR

5. Nesting

Class nesting can be controlled by flight.  All classes that have a hierarchical order must have sales limits to allow nesting.Several groups of nested classes can be added  within the same cabin The number of groups is unlimited.

The indicator will be reflected in the flight inventory  under the acronym NG-L (NG: Nesting Group L: Level). G  represents  and the L the class hierarchy.  LSS column will display sales limits calculated on the basis of the sales limits for each class and nesting. The nested classes in each group will be deducted from each other as sales occur.

5.1 Set Class hierarchy

VMNT {flight} {classes} {date} {route} ADD

Example:

Response:

DONE

Description:

The command to add class hierarchy is repeated as many times as many groups are added. Each group will be assigned a number and next to it the class hierarchy.

5.2 Remove class hierarchy

VMNT {flight} {classes} {date} {route} DEL

Example:

Response:

DONE

Description:

5.3 Options

The same commands can be added for all segments, for a range of dates and certain days of the week. This would avoid adding the indicators day by day.

The input command is:

VMNT 4104 BHKM 31MAR31JUL ALLALL ADD MOTUWEFR

6. Authorization Control

The original authorization of the flights can be modified, increasing or decreasing it even bringing it to zero. Such command can be executed by cabin from its corresponding cabin class (F, C or Y) and by sections or for the whole flight but not by segments, affecting all the classes created in the segment or flight

6.1 Increase or decrease the authorization

VMAU {flight} {class} {date} {route} {authorization}

Example:

Response

DONE

Description:

6.2 Increase or decrease an authorization on a flight

You can also increase or decrease the authorization on a flight. One option is to execute the Step 7.1 command for the desired amount. The other option is to execute the following command:

VMAU4600Y15MAYAEPTUC15ADD

The ADD indicator will order you to increase the authorization in 15 seats more.

To decrease the number of seats of the authorized value is the following command:

VMAU4600Y15MAYAEPTUC15DEL

The DEL indicator will order that you reduce the authorization in 15 fewer places.

6.3 Options

The same commands can be added by date period, for the entire flight and certain days of the week. This would avoid adding the indicators day by day.

The input command is:

VMAU4104Y31MAR31JULALLALL70MOTUWEFR

7. Block Space

A block can be placed on a flight in such a way that it reduces a certain number of seats by whatever the reason is, crew, technical limitation, etc., called "block space".
The block is done by cabin, using the cabin class and by sections or by the complete flight but not by segments. It must ba taken into account that when segments are blocked, all the segments belonging to such legs are also affected.

7.1 Block space on a flight

VMBS {flight} {class} {date} {route} {space amount}

Example:

Response

DONE

The change is reflected in the BS inventory column of. The command was executed on the CORSLA leg but it also affects the AEPSLA segment, thus it the BS indicator is modified with a new value of 20 *, the asterisk will indicate that it is being Inadvertently affected In the SA column (available seats) the offer was reduced by 20 seats.

7.2 Remove the space block on a flight

VMBS {flight} {class} {date} {route} {0 = zero}

Example:

Response:

DONE

Description:

The BS column will remain at zero.

7.3 Increase or decrease a space block on a flight

You can increase or decrease a space block already made. One option is to execute the command in step 8.1 by the desired amount. The other option is to execute the following command:

VMBS4600Y31MARAEPMDQ5ADD

The ADD indicator will order you to increase the space block in 5 more seats. A block can also be reduced. As in point 8.3, the command can be executed by the desired amount or, the command:

VMBS4600Y31MARAEPMDQ12DEL

7.4 Options

The same commands can be added  by date period, for the entire flight and certain days of the week. This would avoid adding  the indicators day by day.

The input command is:

VMBS4104Y31MAR31JULALLALL10MOTUWEFR

8. Temporary Sales Control

This command is used to temporarily control the opening and closing of classes .The commands allow classes to open and close for sale automatically some time before and after the service departure.

8.1 Automatic Class Opening for Sales

VMSO {flight} {class} {date} {route} {number of hours}

Example

Response:

DONE

In the TSO column you will see a a value of  2D00 (2 days and 0 hours), This is the time set for the class opening before  flight departure.

8.2 Automatic Class Closure for Sales

VMSC {flight} {class} {date} {route} {number of hours}

Example:

Response

DONE

Below the TSC column the days and hours will be shown as Days/Minutes (E.G 16D16 (16 days and 16 hours),This value will represent the timeframe before the flight departure.

Note:
The indicator is expressed in hours. At the moment of closing the class this indicator  will disappear and will be recorded in  the flight history and  C will appear in the STATUS column meaning class closure.

8.3 Remove Closing or Automatic Opening

VMSO {flight} {class} {date} {route} 0

Example:

Response

DONE

VMSC {flight} {class} {date} {route} 0

Response

DONE

8.4 Options

The same commands can be used for all classes, by date period, for the entire flight and certain days of the week. This would avoid adding the indicators day by day.

The input command would be:

VMSC4600*31MAR31JULALLALL12MOTUWEFR

9. Overbooking Logic Control 

This command is used to apply an overbooking logic by cabins.The logic to be applied are those are added in the OVERBOOKING LOGIC table (KSMCL).

9.1 Add an overbooking logic

VMOS {flight} {cabin} {date} {route} {logic number}

Example:

Response

DONE

Description:

When the inventory is retrieved, the number of spaces applied for overbooking added by the user will be displayed in the OS column and in the applicable logic number in the LOS one..

Example:

In the example, logic 10 was applied to cabin Y. (See column LOS). According to the logic corresponding to each cabin, the number of  additional spaces offered for sale will appear in the OS column
 and will be added to the authorized ones (AU) and to the available seats (SA)

9.2 Remove overbooking logic

To remove the overbooking logic you must perform the same command by applying 0 (zero) in place of the logic number

VMOS4600Y26MAYAEPTUC0 

Response

DONE

9.3 Options

The same commands can be added for all flight cabins, for all segments, by a range of dates , certain or all days of the week. This would avoid adding the indicator one by one the.

The input command would be:

VMOS4600 FCY 26MAY10JUNAEPALL1MOWEFR

This command will add  overbooking logic 1 applicable for  Monday, Wednesday and Friday to flight 4600 from 26MAY to 10JUN for FCY cabins between AEP and all destinations.

10. Remarks field

 This command is used to add a free text Remark to a specific segment and it  will appear in the availability request and in the inventory.

The input command would be:

10.1 Add a comment

VMRM {flight} * {date} {route} / {free text}

Example:

VMRM4176 * 14FEBAEPSLA / DEPARTING TERMINAL 2B

Response

DONE

Description:

DEPARTING TERMINAL 2B

When the inventory  command is requested again, a message is shown at the end of the inventory with added text.

Example:

10.2 Delete a Remark

The command to delete a comment is similar to the previous one but after the slash no text is entered.

Example:

VMRM4176*26MAYAEPSLA/

Response

DONE

10.3 Options

A comment can be added for all segments in one entry or only for those segments from the origin to all destinations or from all origins to the same destination. In this case, the
ALL indicator is used to replace all. It can also be applied to a range of dates and certain days of the week. This avoids adding one to one the indicators.

The input command is:

Example:

VMRM 4176*26MAY26MAYALLALLMOTUFR/VERIFY PASSPORTS

In this case the remark will be applied to all segments, from 26MAY to 31MAY and on Monday, Tuesday and Friday.

11. Add an airport terminal

This command is used to add departure and arrivals terminals  The terminals added support up to 2 digits and will appear in the availability request.

The input command is :

11.1 Add  a departure terminal

VMTD {flight} * {date} {airport} / {terminal}

Example:

Response

DONE

Description:

A4

The availbility display will display the following information adjacent to the departure airport code.

11.2 Add an arrival terminal

VMTA {flight} * {date} {airport} / {terminal}

Example:

VMTA4176*23MAYSLA/T2

Response

DONE

Description:

A4

The availability display will display the following information adjacent to the arrival airport code.

VMTD4500*23JULAEP/DEL

VMTA4500*23JULAEP/DEL

12. Catering service load

This command is used to load a new catering service to a specific leg. The service indicator can be up to 3 characters .

Input command is :

12.1 Add or modify services

VMML {flight} * {date} {route} / {service indicator up to 3 characters}

Example:

VMML4360*20DECAEPMDQ/L

Response

DONE

Description:

L

13. Modify Flight schedules

This command allows you to perform schedule changes for a specific date and flight without performing the regular Schedule Change process. It also updates  VIE  and VLC  entries and the availability, display. You must use  VLC command * {flight} / {date} in order  to visualize the whole flight .

This action does not modify the schedules in the reservations already made, but all reservations made after the schedules modification will be generated with the new schedule. It must be taken into account that the new flight schedule must always be within the departure day of the flight. same.

Regarding  Check-In, if the flight was initialized before the manual time change, the PC schedule (Control Panel) will remain as it originally configured,therefore it should also be changed manually.

In case the flight is  initialized after modifying  the schedule, the Control Panel  will have the new schedules.

It is not necessary that all reservations have the same schedule to perform the Check-In process,  It  will be done normally, but in case a user wishes  to have all the reservations with the same schedule 
these should be canceled and rebooked for the system to display new schedule.

The entry to manually modify the schedules is:

VMTM458*26MAYAEP/1030/1230

System Response:

The command must be re-added by adding / Y at the end to confirm the change. The entry of midnight hours is not accepted as 0000 or 2400, and must be replaced if needed by 2359 or 0001.

If the arrival time is the following day, the entry to be used is the following

VMTM458*26MAYAEP/2330/0050+1

In case the flight has more than one leg, the entry would be the following:

VMTM4200*2SEPAEP/1030/1230/EQS/1330/1400/BRC/1430/1700

In case the flight has a day change during a stop, the following entry should be used:

VMTM4200*2SEPAEP/2030/2230/EQS/2330/0005+1/BRC/0130/0300

These commands will be recorded in the flight history.

14. Overbooking Inhibition Control

This control allows to inhibit the overbooking of classes despite having the keywords that enable it (OVERSL, CHKOSL). The indicator will be reflected in the flight  inventory of the flight under the ST column with the letters Ox.
This function only allows overbooking in the reaccommodation by schedule change or in massive reaccomodation (VMOVE function).

14.1 Inhibit the overbooking of a class

VMIO {flight} {class} {date} {route} ON

Example:

Response

DONE

Note:
The ON or OPEN or GO indicator can be used

14.2 Remove the inhibition of overbooking of a class

VMIO {flight} {class} {date} {route} OFF

DONE

Note:
The ON or OPEN or GO indicator can be used

14.3 Options

You can load the same commands for all flight classes , segments, range of dates and certain days of the week. This avoids adding the indicators one by one. 

The input command is:

VMIO4320 / 31MAR31JUL ALLALL MONMOTUWEFR

Manual passengers transfer 

1. From a flight to another

This procedure allows you to transfer a list of passengers from one flight to another . The process is to eliminate all passengers in one segment and send them confirmed to another .

Duties 5, 7 or 8 are required. If the user only has duty 5 will also be required to have CHKLV2 keyword and will be able to modify flights departing 48 hours before and / or after the current day

The input command is:

VMOVE4420/13APRAEPMDQ#4444/13APRAEPMDQ

Once the command is executed, it requires a double validation, therefore the same command must be entered again with /Y and at the end.

Note: In case of applying on previous days or past flights, year should be added after the month in a  two-digit format. Example, 13APR18

1. Only those passengers with confirmed status (HK, TK, KK or KL) will be migrated. Status MM, HL, TL or HM will not be transferred.
   
   
2.  Passengers may be transferred on any other flight, regardless of the route and date.
   
   
3.  In case there is no match in the classes of the flight where passengers are being transferred, the system will respond with the corresponding error and should be clarified by the command thatI t is explained below which classes will be transferred. Control of Spaces Version 2.0 47
   
   
   

How to transfer  no-match classes

When a class does not match or has no equivalent in  the new flight it must be indicated  which class will match in the new flight when we transfer these PNRs. A hyphen(-) with the class that cannot be transferred followed by the new class which will correspond. Every single booking class will be separated by a -.

VMOVE4420/22DECAEPMDQ#4300/22DECAEPMDQ-HY-NB

In the example, flight 4420 class H will be transferred to class Y and class N  of flight 4420 will be will  transferred to class B of flight 4300.

In case of sending all no-match classes to another, the command would be:

VMOVE4420 / 22DECAEPMDQ # 4300 / 22DECAEPMDQ- * Y

In case of sending all classes (match/no-match) to a single one, the command is:

VMOVE4420/22DECAEPMDQ#4300/22DECAEPMDQ-øY

How the change is reflected in the PNR 

In the active part of the PNR the new flight with status TK will be displayed. In the historical part of the PNR a canceled flight segment(XS) where the passenger was booked and a sold segment(AS)
next to the sign initials and date when the command made.

How the change in flight history is reflected

In the flight history  the command made with the sign initials and date will be recorded.

2. From a flight to two or three flights

As previously described the same procedure can be carried out by sending the passengers of a flight to two or three different flights.

The command is the following:

VMOVE4420/13APRAEPMDQ#4444/13APRAEPMDQ#442/22DECAEPMDQ

Response:

Once the command is executed, it requires a double validation, therefore the same command must be entered again with /Y and at the end.

VMOVE4420/22DECAEPBRC#4300/22DECAEPMDQ#4444/22DECMDQBRC/Y

Note: Consider applying the same entries when a no-match class occurs in the new flight. This has to be done for each of the flights.

Example

In case there are three flights where passengers are transferred, # is added and the data of the third flight, the same way as with the second flight with respect to the first.

3. Sending to queues

You can send the list of passengers to queues at the time of transfer.

The command is:

VMOVE4420/22DECAEPMDQ#4300/22DECAEPMDQ/Q222

All PNRS will be sent to queue 222 of the city where the terminal is located. The other option is to send it to a queue from another city, with which the command is:

VMOVE4420/22DECAEPMDQ#4300/22DECAEPMDQ/QBRC222

After this the system displays the data of the passengers to be transferred requesting the validation to confirm. The same command must be executed with / Y at the end.

4. Partial passengers transfer

This procedure allows the transfer of a partial passengers list from one flight to another. The process is to eliminate all passengers in one segment and send them confirmed to another flight. 
Duties 5, 7 or 8 are requiered. If the user only has duty 5 will also be required to have CHKLV2  keyword. You can modify flights departing 48 hours before and / or after the current day.

The procedure must be done in 2 steps.

The first step displays the list of PNRS for later selection:

VMOVE4420/22DECAEPBRC

Description:

Response

Then, the second step, which is the selection of PNRS from the expanded list, must be executed. This list can be re-displayed  as many times as necessary with the VMOVE command *

To select the PNRS, the command is

VMOVE.1-2,5#4300/22DECAEPMDQ

Response

A List of actions is displayed asking to reconfirm by adding /Y at the end of the command.

Note:
The system will move all the passengers of a PNR. It is not possible to select a single passenger. Only transfer PNRS with confirmed status (HK, TK, KL, KK) s.

OVERBOOKING

1.Overbooking a flight

To  overbooking  a  fully booked flight or class a command can be used for users with duty code 8 and OVERSL keyword.

Command is OB and can be executed in two different ways

1) Direct Sell

04300Y24JANAEPMDQOB1

The direct sales command is pone by requesting the flight segment in  OB status.  The system sells it as OB and, when closing the PNR, this status is modified to HK. That change will be recorded in the PNR history  in the following format:

2) From a segment on the waiting list:

The PNR to be confirmed is displayed and the following command is performed:

(.) (segment number) OB

You can also use this entry.

(.) (segment number) KL

In both cases the system will respond:

1. HL/OB => KL

When closing the PNR, the status will become KL. This change will be recorded in the  PNR  history:

MS   XX4500Y 21NOV MO AEPCOR    HL/OB/KL1 07:50 09:00

2. Group PNR Creation(HM to HK)

To confirm a group in requested status HM s, the PNR must be retrieved . The command for Group segment confirmation is KK and it is executed in the following way:

(.) (segment number) KK

System response

After ending the transaction and redisplaying the PNR  the segment will be in KK status , which is a warning code and must be modified manually to HK status. Once the group creator has been notified it will be recorded in the PNR history.

Note:
This action will automatically place  PNR on queue 45 (CONFIRMED GROUPS) of the city code that created the PNR. 

3. Confirmation of Requested Individual Segments (HM to HK)

The action of requesting a segment with requested status (HM) generates a message to queue 20 (PNRs of the own airline or agencies) or 21 (PNRs of other OA companies)that generated it and the airline that manages the requested segment.
To confirm the segments that are in requested  status (HM) the same procedure is used  with the groups. PNR must be retrieved and the command to confirm the requested  status must be executed.

(.) (segment number) KK

System response

After ending the transaction and redisplaying the PNR  the segment will be in KK status , which is a warning code and must be modified manually to HK status. Once the group creator has been notified it will be recorded in the PNR history.

Note:
This action will automatically place  PNR on queue 45 (CONFIRMED PNRS) of the city code that created the PNR. 

4. Segments Subject to space availability Confirmation(MM to HK)

To force the confirmation of segments subject to space ie with MM status, there is a command that can be executed by those users that have the keyword OVERSL

(.) (segment number) KK

PNR status change will be recorded  in the history displaying  MM / KK

Note:
This action will automatically place  PNR on queue 45 (CONFIRMED PNRS) of the city code that created the PNR. 

5. Segment Status modification from Requested  status  to waiting list (HM to HL)

You can update  a PNR in the required state (HM) to the waiting list without the need to confirm it.

The command is:

(.) (segment number) HL

The system will change status HM to HL when recording the PNR. If space is available it will be possible to change segment status HL to KL.

6. Force a Closed Wait List

In case a closed waiting list is found or has reached the pre-established limit it is possible to force it and add a segment.

To perform this transaction, the user must have the WAITLA Keyword in the signature. The command can be made by direct segment or from a short reservation availability

Duplicate PNRS

1. Manual handling of duplicate PNRs

Duplicate PNRs that are generated in the system can be visualized by entering  a command that sends the dupes messages to queues.
The system considers dupes all thee surnames that are the same day in a same flight segment. These messages will be sent to queue 151 of the administering city of the system.

The command to execute is:

DP / DATE / {SEGMENT}

When retrieving the message from the queue it will look like this:

The flight, class, date, route, reservation code and surname / passenger name are considered duplicate.

The reservation locator has a link that allows you to retrieve the PNR on the screen or display it on the help screen.

Inventory update in other GDS

The following command allows you to update the flight inventory in other GDS (Global Distribution System). When executing this command the system sends a message to the other GDSs updating the availability of each class marketed on the flight (opening, closing or adjusting sales limits).

VAVS {flight} / {date}

Example: VAVS4500 / 18FEB

Notes:

1.  In order to execute this command, the airline must have its flights published in other GDS  in addition to KIU.
   
   
2.  When executing this command, a copy of the updated inventory is sent to the HDQ city Queue 175 .

1. VCD (View Count Details)

This command allows to get a numerical detail of the number of passengers, by sections and segments of the flight, grouped according to the type of passenger (adult, minors and infants) and the according to the itinerary status (confirmed, subject to space, to be request, on waiting list), as well as informs if there are unaccompanied minors.

The command that must be entered is the following:

VCD {flight} / {date}

Example: VCD4420 / 04MAY

Description:

If the date or the airport is not indicated, the system will default to the current date  and the user´s terminal location.

2. VCD from an availability display

To verify VCD entry from a flight availability display ,a flight query  must be previously displayed on the  screen and then enter the following command:

VCDA1

Description

3. VCD from a PNR

To check the VCD entry from a PNR, you must have previously displayed the booking  on the screen and then enter the following command:

VCDP1

Connection time control (VCT *)

The VCT * command (Verify Minimum Connecting Times) allows to verify if the minimum connecting times  between flights are observing the correct time  as configured  in the minimum connecting time  table  between airports.

The information provided is for information and it is not recorded in  history.

The command can be executed on an  segments itinerary in the process of creation  or on an already created one.

To enter, you must have one of the following duties: 2 to 8.

No special keyword is required to verify this information, and they can do it both the users of the airlines and those of the travel agencies

Entry

The command to verify minimum connecting times is as follows:

VCT*

When performing this entry the system will display different responses  according to the itinerary that is being checked:

Response 1:

When the minimum connection times apply correctly for the entire itinerary or reservation:

MINIMUM CONNECTING TIME VALID FOR ALL CONNECTIONS

Response 2:

When there is no itinerary with connections to apply:

NO CONNECTIONS TO PERFORM MINIMUM CONNECTING TIME

Response  3:

When the minimum connection is not being observed. 

INVALID CONNECTING TIME SEGS 2 AND 3 - MINIMUM IS 120 MINUTES VERIFY ANY REMAINING SEGS

When the minimum connection times are not observed, as configured by the airline, the system informs which are the segments between which the minimum connection times is not being observed (2 and 3 in example), and informs the minimum time established (120 minutes in the example). If connecting time fails  to comply with the minim system stops verifying the remaining segments of the itinerary.

You can check if the minimum connection times are correct by indicating the segments of the itinerary:

VCT*1,3

This entry informs if the minimum connection time between segments 1 and 3 is correct

VCT*2-4

This entry informs if the minimum connection time between segments 2 to 4 is correct.

Important:

The VCT * command applies only between segments with confirmed status (HK, KL, TK, KK, RR).
For the system to verify if the minimum connection time is correct, the time between arrival and departure must be less than zero minutes.