MAN_Movement Message

Cargo Operating Message

To send an operational message, the corresponding mask is used and it is displayed with the following command:

PML<FLIGHT>/<DATE><ORIGIN>

Example:

PML4580/26JULAEP

LDM MESSAGE
FLT: 4580 BRD: AEP WED 26JUL06 REGISTRATION: LV-KKK

CREW:
   1. BARBERIS/ALDO
   2. MERLO/FRANCO
   3. DIEZ/ANDREA

	 OFF	ADT	CHD	INF	WEIGHT	BAG	LOAD	MAIL
	 COR	16	4	4	1340	18/335	188	156

TTL LOCAL	16	4	4	1340	18/335	188	156

TTL DEP		16	4	4	1340 	18/335	188	156

HOLD:
ALTERNATIVE:				FOB:	SURPLUS: 0
						CHARGE: 0
						TOTAL: 0
AEP.AEPXX-WP 1845/26JUL06

Description:

The first part corresponds to the same data as the traffic manifest. Then the following indicators are displayed:

HOLD	Warehouse
ALTERNATIVES	Alternative airports
FOB	Fuel on Board
SURPLUS	Fuel remnant
CHARGE	Fuel charge
TOTAL	Total
AEP-AEPXX-WP 1845/26JUL06	User-Time/Date

In order to load the Warehouse Distribution, Alternative, and Fuel data, the following command is executed:

PML,HLD1/100 2/110 3/123,ALTROS/SFN,FOB2000/10000

PML	Command
,	mandatory comma
HLD	Warehouse indicator
1	Warehouse number 1
/	mandatory slash
100	Weight (free text) (kilos)
2	Warehouse number 2
/	mandatory slash
100	Weight (free text) (kilos)
3	Warehouse number 3
/	mandatory slash
123	Weight (free text) (kilos)
,	comma
ALT	Alternative
ROS	Airport
/	mandatory slash
SFN	Second alternative airport
,	comma
FOB	Fuel on Board
2000	Remant Fuel (kilos)
/	mandatory slash
10000	Loaded Fuel weight (kilos)

Response:

OK

You can load up to 5 alternative airports separated by slashes (/).

To display the message before sending it, the command is:

PML<Flight>/<Date><Airport>

To send the message, the command is:

PML-SEND

The system will display it as follows:

OK. MSG SEND
LDM MESSAGE
FLT: 4580 BRD: AEP WED 26JUL06 REGISTRATION: LV-KKK
CREW:
	1. BARBERIS/ALDO
	2. MERLO/FRANCO
	3. DIEZ/ANDREA
 		OFF	ADT	CHD	INF	WEIGHT	BAG	LOAD	MAIL
		COR	16	4	4	1340	18/335	188	156
TTL LOCAL		16	4	4	1340	18/335	188	156

TTL DEP			16	4	4	1340	18/335	188	156
HOLD:1/100
ALTERNATIVE: ROS 				FOB: 		SURPLUS: 200
 								CHARGE: 1000
								TOTAL:  1200

Once the message has been sent, it generates the following message on the control panel:

** MSG LMD MESSAGE **

If at the time of executing the PML command the system responds with the following message, it means that the closure of the flight has not been performed (PD) at the previous airport:

CHECK PREVIOUS POST-DEPARTURE PROCESS

In order to continue, the flight must be closed on the previous scale and then re-enter the command PML

Takeoff Message

This message contains the flight departure, gate closure, and takeoff time data, but also it may contain the estimated arrival time (ETA) and in case of delay, the IATA codes of delay with the minutes that correspond to each of them, whose total sum must coincide with the difference between the Scheduled Time of the PC and the Door Closing (CDT) of the message that is sent.

PMD<FLIGHT>/<DATE><ORIGIN>

Example:

PMD3136/20SEPAEP

Description:

DEPARTURE TIME	Time of departure
UTC	Coordinated Universal Time
CD	Close door
CO	Shims removal
AD	Departure time
DELAY TIME	Delay time (in minutes)
CODE	Delay code (minutes included per each code)
OBSERVATION	Free text up to 99 characters

At times the sign - (minus) should be indicated in the schedule when it corresponds to the previous day (always taking into account the day regarding the Zulu time).
The CDT schedule is what the system considers to calculate the delay time if there is one. If entering one or more delay codes, its use becomes mandatory so that the system can correctly calculate the minutes of it.
Up to 5 delay codes can be added, each of them must be followed by the minutes that correspond to each code, and added the minutes must match the difference between the Schedule Time and the CDT (Close Door Time). If there is only one code of
delay is not necessary to clarify the minutes since the system will calculate the delay time automatically.
If the inserted delay minutes do not match the difference between the Schedule Time and the CDT (Close Door Time or Door Closing) system will respond with the following error message:

INVALID - CHECK DELAY

To entre the load data, the following command will be executed:

PMD,CDT2355,COT0005+,ADT0010+,ETA0200+,DLY73.5*14.10*91.15/FREE TEXT

PMD	Takeoff Message indicator
,	mandatory comma
CDT	Close door time indicator
2355	Close door time in UTC
,	mandatory comma
COT	Shims removal time indicator
0005	Shims removal time in UTC
+	Following day indicator (if necessary)
,	mandatory comma
ADT	Departure time indicator
0010	Departure time in UTC
+	Following day indicator (if necessary)
,	mandatory comma
ETA	Estimated arrival time indicator
0200	Estimated arrival time in UTC
+	Following day indicator (if necessary)
,	mandatory comma
DLY	Delay code indicator (Optional)
73	Delay code To verify codes: HLP*DLY (Optional)
.	dot
5	Delay minutes corresponding to previous delay code
*	asterisc (delay code separator, maximum of 5 codes)
14	Delay code
.	dot
10	Delay minutes
*	asterisc
91	Delay code
.	dot
15	Delay minutes
/	mandatory slash
Free Text	Optional comment when the indicator DLY is included

Response:

OK

Example of a flight departing at 9.00 pm (local time) from a city with Zulu time -3:

PMD,CDT2350-,COT2358-,ADT0005

Close door at 8.50 pm LT
Shims removal at 8.58 pm LT
Departure at 9.05 pm LT

PMD,CDT0000-,COT0008-,ADT0015

Close door at 9.00 pm LT
Shims removal at 9.08 pm LT
Departure at 9.15 pm LT

PMD,CDT2350-,COT2355-,ADT2358

Close door at 8.50 pm LT
Shims removal at 8.55 pm LT
Departure at 8.58 pm LT

There may not be more than six hours difference between the schedules entered.

Modify

To modify the data, the command must be added again.

PMD,CDT2130,COT2135,ADT2145,ETA2345,DLY73.5*14.10*91.15/FREE TEXT

Delete delay code

To modify the data, the command must be added again.

PMD<FLIGHT>,CDT<TIME>,COT<TIME>,ADT<TIME>,DLYNIL

NIL is a fixed text and it means to eliminate the previously entered codes

Display

To display the already entered data:

PM

Send

To send the message:

PMD-SEND

Response:

Once the message has been sent, it generates the following message on the control panel:

** MVT DEPARTURE SEND **

Reports

Once the message has been sent, TFR2 and TFR6 reports are updated with the corresponding data of flight delay
The TFR2 flown report will show the complete information on the delays and their codes.
The TFR6 report will show the delay and its options will show those flights that have exceeded the minutes of tolerance configured in the JJSTAT. It will also show the following text when displaying the report in the auxiliary screen

FLIGHTS DEPARTED WITHIN THE ACCEPTABLE DELAY TOLERANCE TIME RANGE DEFINED BY EACH AIRLINE ARE NOT INCLUDED IN THIS REPORT

If you would like to view the report omitting the tolerance, use the following command:

TFR6/FECHA/NT

NT refers to No Tolerance, this means not considering the configured tolerance

IATA Coding List for delay

HLP*DLY

To see a code, in particular, you can use the command HLP * DLY / <delay code>

Arrival Message

To send the arrival message, the corresponding mask is used which is displayed with the following command:

PMA<FLIGHT>/<DATE><DESTINATION>

Example:

PMA4302/20APRREL

Response:

Description:

ARRIVAL TIME	Departure time
UTC	UTC time
AA	Arrival time
CI	Shims settings
OD	Open door

To load the data the following command will be executed:

PMA,AAT0210+,CIT0215+,ODT0218+

PMA	Send indicator
,	mandatory comma
AAT	Arrival time indicator (mandatory)
0210	Arrival time in UTC (mandatory)
+	Following day indicator (optional)
,	optional comma
CIT	Shims setting indicator (optional)
0215	shims setting time (optional)
+	Following day indicator (optional)
,	optional comma
ODT	Open door indicator (optional)
0218	Open door time (optional)
+	Following day indicator (optional)

Response:

OK

To display the previous message sent, the command is:

PM

To send the message:

PMA-SEND

The system will respond as follows:

At times the sign - (minus) should be indicated in the schedule if it corresponds to the previous day (always taking into account the day with respect to the Zulu time). The application mode is the same as for the message of take-off PMD.

There may not be more than six hours difference between the schedules entered. The message of Arrival can be entered up to 12 hours after the original schedule.

Generation of Standardized Operational Messages for Other Uses

Referencia: IATA Airport Handling Manual - AHM780

Introduction

MVT movement messages are generated from the check-in / back-office / operations module to those flights that operate on the day of the date and +/- 24 hours, that is, yesterday, today and tomorrow.

MVT departure or arrival messages should be generated immediately after departure or arrival of the aircraft
MVT delay messages should be generated as soon as the delay is known
All dates and times will be expressed in UTC

Components and Elements of Messages

This is an example of an MVT message sent through type B messaging. Following it is detailed the MVT message content in general.

Recipient and Sender

Only if it is sent through type B messaging. If the messages are sent by email, they don't include this data.

QU HDQBBYY	Destination TTY address
.HDQBBXX	Origin TTY address

Header of the Message

The message header always contains the same fields regardless of the type of message (departure, arrival, etc.) that is being generated.

MVT	Message identifier
XX014/31.LVSSS.USH	Flight data
XX014	Flight number
/	mandatory slash
31	Operations UTC day
.	mandatory dot
LVSSS	Flight plate (XXXXX if it is not informed)
.	mandatory dot
USH	Airport of origin

Schedule

In all cases, schedules are UTC. The format can be DDHHMM or HHMM.

ED312115	Estimated UTC day and time of departure
AD2228/2230	UTC departure time (COT / ADT)
EA1840	Estimated UTC Arrival Time (ETA)
DL99/98/0105/0005	Delay code and delay time for each code in hours
ED93/92/0005/0005	Extra delay code and time for each code in hours
AA0340/0340	UTC arrival time (AAT / CIT)
SI FREE TEXT UP TO 65 CHARACTERS	Free text (To be developed soon)

Message Generation From KIU

Based on the following flight, it is detailed the different commands available in KIU and the MVT message that would result from each of them.

The system will check the NOOP field where the marketing flight data appears and then the JJMSG table where it will be verified if any of the airlines indicated as marketing is configured to receive the MVT messages