Date division
Step 1:
| Code Block | ||||
|---|---|---|---|---|
| ||||
KA*4370 Fliht inventory is retrieved to be divided |
Step 2:
| Code Block | ||||
|---|---|---|---|---|
| ||||
KS.1 Item 1 is selected |
Response:
| No Format |
|---|
KS.1
CARRIER FLIGHT AEP.AEPXX-AA 1559/11JAN18
XX 4380
ITEM IDMASTERVL EFFECT DISCONT FREQUENCY NLG FRM END
1 0000011205 25FEB2018 --OPEN-- 12345-- X-SA-SU 2 AEP BHI
LEG BRD TD OFF TA DEPT ARRV 'BLK CD NBR/EQP NBC CAB DIST(km)
1 AEP MDQ 0800 0900 60 0 999/DC9 6 1 382
2 MDQ BHI 0930 1015 45 0 999/DC9 6 1 408
LEG BRD OFF # M-C AUTH BS LS NG-NL LSS TSO TSC NLOS WLL STATUS ML
1 AEP MDQ 01 Y Y 90 0 0 0 0 B
02 B 0 0 B
03 H 0 0 B
04 T 0 0 B
05 O 0 0 B
06 V 0 0 B
2 MDQ BHI 01 Y Y 90 0 0 0 0 B
02 B 0 0 B
03 H 0 0 B
04 T 0 0 B
05 O 0 0 B
06 V 0 0 B
AEP-BHI 01 Y Y 90 0 0 0 0 B
02 B 0 0 B
03 H 0 0 B
04 T 0 0 B
05 O 0 0 B
06 V 0 0 B
|
Step 3:
| Code Block |
|---|
KSD/01AUG/31AUG |
Descripción:
KSD | Division indicator command |
/ | Slash |
01AUG | Division start Date |
/ | Slash |
31AUG | Division stop date |
Response:
Options:
If the start date indicated in the item is selected (in the example it would be 01AUG) it can be ignored by placing a double bar after the division command.
Example:
| Code Block | ||||
|---|---|---|---|---|
| ||||
KSD//31AUG |
If the stop date indicated in the item is selected(in the example it would be OPEN) it can be ignored by only setting the start date of the division.}
Example:
| Code Block | ||||
|---|---|---|---|---|
| ||||
KSD/01AUG |
Step 4:
If the change is correct, it is accepted with YES, if it is not, CANCEL is selected and you return to step 1
Acceptance response:
| Code Block |
|---|
MASTERVUELOS CARRIER FLIGHT AEP.AEPXX-AA 1905/11JAN18
XX 4380
ITEM IDMASTERVL EFFECT DISCONT FREQUENCY NLG FRM END
1 0000011205 25FEB2018 31JUL2019 12345-- X-SA-SU 2 AEP BHI
2 0000011210 01AUG2018 31AUG2019 12345-- X-SA-SU 2 AEP BHI
3 0000011211 01SEP2018 --OPEN-- 12345-- X-SA-SU 2 AEP BHI
|
Frequency division
Steps 1 and 2 are the same as in the division of dates.
Step 3:
| Code Block | ||||
|---|---|---|---|---|
| ||||
KSD/1 Monday is divided (1) |
Response:
A new item is displayed dividing the indicated day
Step 4:
As in the date division, if the change is correct, it is accepted with YES, if it is not, CANCEL is selected and you return to step 1.
Date extension or frequencies addition
Steps 1 and 2 are the same as in the dates division
Step 3:
| Code Block |
|---|
KSD/6 Frequency 6 is added. |
Por ejemplo, un vuelo que opera los días 12345, se quiere agregar el 6 y 7, el comando sería:
In step 3 date or operational frequency is added
Note item number 2 with the added frequency.
You can also add the desired frequencies next to those already operating, so they would all be within the same item.
For example, a flight that operates on days 12345,and you intend to add 6 and 7, the command is:
| Code Block | ||||
|---|---|---|---|---|
| ||||
KSD/1234567 |
El paso 4 se acepta de la misma forma que en los casos anteriores.
También se puede crear un vuelo o una operatividad discontinuando la creada. Por ejemplo, hay un vuelo creado desde el 15MAR05 al 31MAR05 y hay que crear un vuelo idéntico o similar, se debe tomar el ítem que corresponde al 15MAR/31MAR y hacer el comando con las fechas deseadas en las cuales operará el vuelo:
Step 4 is accepted in the same way as in the previous cases.
You can also create a flight or an operation by discontinuing the one created. For example, A flight which is already created from 15MAY18 to 31MAY18 and you you have to create an identical or similar flight, you must take the item corresponding to 15MAY / 31MAY and do the command with the new dates in which the flight will operate:
| Code Block |
|---|
KSD/FECHADATE DESDEFROM/FECHADATE HASTATO |
EjemploExample:
| Code Block |
|---|
KSD/05JUN/05JUN o KSD/05JUN/31JUL |
| Note |
|---|
En todas las modificaciones que tengan que ver con la división de fechas, cuando se usa el comando KSD/FECHA/FECHA, si se deja el espacio en blanco en cualquiera de las dos fechas, el sistema toma por default la fecha del día en la efectividad o la fecha preestablecida en el vuelo ya creado en la discontinuidad. |
5.4 Ignorar Cambios de Husos Horarios DST:
En caso que una programacion genere error por un DST cargado después de la creación del vuelo, cualquier división posterior responderá con el siguiente error:
This command will create the same flight for the required dates and with the same frequencies.
| Note |
|---|
When the KSD / DATE / DATE command is used to modify a date, if a space is left blank in any of the two dates, system defaults to the effectiveness date or the pre-established date of the flight already created in the discontinuity. |
5.4 Ignore DST Time Changes :
In the event that a schedule generates an error due to a DST loaded after the creation of the flight, any subsequent division will respond with the following error:
| No Format |
|---|
ERROR - INVALID BLK TIME DUE TO DST <RUTA> INVALID TIME FLT(-15) / DST:<PAIS><COUNTRY> FROM 14APR201414APR2018 TO 29JUN2014<RUTA>29JUN2018<ROUTE> INVALID TIME FLT(-15) |
To ignore the control over the DST time change, the following indicator can be entered to ignore the control and proceed with the division, the indicator is / NDST (No Daylight Saving Time). El mismo se puede ingresar en cualquiera de las opciones de división
Ejemplo:It can be entered in any of the division options.
Example:
| Code Block | ||||
|---|---|---|---|---|
| ||||
KSD/26MAY/28MAY/NDST KSD/28MAY/NDST |