How Awery system operates with MVT messages

Preamble

The system automatically processes incoming MVT (Movement) messages to update actual departure and arrival details for flights. This feature helps ensure that flight tracking remains up-to-date without requiring manual intervention, as long as the messages follow expected formats.

What the Awery ERP Does

Upon receiving an MVT message, the system:

Parses the message and extracts operational data, such as:
- Flight call sign
- Aircraft registration number
- Departure and arrival airport codes
- Block-off / block-on times
- Actual departure / arrival times
- Flight day number (when provided)
Attempts to match the MVT to a flight record based on:
- Call sign and origin airport
- Shared operator codes (IATA / ICAO / internal call signs)
- Date range (typically same-day or one-day-shifted match)
Updates the matched waypoint (flight_waypoints) with:
- Actual departure date (if departure message)
- Actual arrival date (if arrival message)
- Actual block-off or Actual block-on times
Links the message to the flight for traceability, using the email ID if available
Logs all operations for further audit or review.

The MVT handler in the system is designed to enhance accuracy and automation, while respecting manual input and data integrity. It is optimized for airlines and cargo operators where MVTs are regularly received but must not cause unintended side effects.

If you expect alternative behavior, such as auto-creating waypoints or overriding manual data, please contact support to discuss enabling specific rules.

Sample of the messages

CODE

MVT
XRC0001/10.TSICB.CDG
AD0505/0522 EA0725 TUN

CODE

MVT
XRC0002/07.TSICD.CDG
AA0845/0900

CODE

MVT
XRC0003/09.TSICB.CDG
AA1718/1727

CODE

MVT
XRC0004/10.TSICD.CDG
AD0909/0928 EA1130 TUN

CODE

MVT
XRC0005/05.TSICD.CDG
AD0446/0459 EA0700 TUN

What the Awery ERP does not do

To ensure predictable behavior and avoid incorrect assumptions, the system does not:

Automatically create flights or waypoints from an MVT message if no match is found
Assume date corrections unless clearly derivable (e.g., no assumptions about month rollovers)
Generate customer-facing notifications unless.
Interpret incomplete or malformed messages — these will be logged but ignored for updates