RmsData
Resource Management Data in this setting is data a RMS / Apron Management / Aircraft Parking system updates for one flight leg. A RMS system is by nature airport oriented and will often operate on turnarounds. In this setting it's usual to update two flight legs, the inbound flight leg and the outbound flight leg.
Please remember that arrival and departure data on a flight leg is on two airports, but when viewed as a turnaround arrival and departure data is on the same airport, but on two flight legs.
A RMS system will typically only update:
- Arrival data, including linked departure, for the incoming flight leg.
- Departure data, including linked arrival, for the outgoing flight leg.
Contains the data elements to set check-in data. Identification
NB! This will be either the inbound flight leg or the outbound flight leg of a turnaround.Departure data Departure data for the outgoing flight leg. If used, arrival data is not expected to be present. GateDeparture NILABLE AircraftParkingPositionDeparture NILABLE UniqueFlightLegIdLinkedArrival NILABLE Arrival data Arrival data for the incoming flight leg. If used, departure data is not expected to be present. GateArrival NILABLE AircraftParkingPositionArrival NILABLE UniqueFlightLegIdLinkedDeparture NILABLE