AircraftDispositionData

Aircraft disposition data is aircraft oriented - not flight (leg) oriented. It will result in the update of one or more flight legs for the given FlightDepartureDate

Entity / ADD element

AircraftDispositionFlightData 0..*

  • 0 only if DeleteAllRegistrations = true
  • DeleteAllRegistrations can be true and AircraftDispositionFlightData contains data. The defined flight legs should then be updated.


FuelRequestData

Entity / ADD element
FuelRequestData

IataASMCancelData

The figure below shows the Airport Data Dictionary based data structure representing the following IATA ASM message types:

  • CNL 

For more information on the mapping from IATA ASM data to ADD, see: ASM data to ADD data

Entity / ADD element
IataASMCancelData


IataASMRoutingData 0..*

Only departure/arrival airport are used for SubmitASMCancelData.

IataASMChangeFlightIdData

The figure below shows the Airport Data Dictionary based data structure representing the following IATA ASM message types:

  • FLT

For more information on the mapping from IATA ASM data to ADD, see: ASM data to ADD data

Entity / ADD element


IataASMRoutingData 0..*

Only departure/arrival airport are used for IataASMChangeFlightIdData.

IataASMInsertUpdateData

The figure below shows the Airport Data Dictionary based data structure representing the following IATA ASM message types:

  • NEW
  • RPL
  • ADM
  • CON
  • EQT
  • TIM
  • RRT

For more information on the mapping from IATA ASM data to ADD, see: ASM data to ADD data

Entity / ADD element
IataASMInsertUpdateData


IataASMAircraftData 0..*


IataASMRoutingData 0..*


IataASMReinstateData

The figure below shows the Airport Data Dictionary based data structure representing the following IATA ASM message types:

  • RIN

For more information on the mapping from IATA ASM data to ADD, see: ASM data to ADD data

Entity / ADD element
IataASMReinstateData


IataASMRoutingData 0..*

Only departure/arrival airport are used for SubmitASMReinstateData.

IataDivData

The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Diversion Message (DIV) as defined in the Airport Handling Manual (AHM) 781.

Entity / ADD element
  • ELDT (at diversion airport)
  • EIBT (at diversion airport)

IataLoadData

The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Load Message (LDM) as defined in the Airport Handling Manual (AHM). 

For more mapping information, see: LDM data to ADD data 

Entity / ADD element
IataLoadData

IataLoadDestinationData  


IataLoadCompartmentData 


IataMvtData

The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Movement Message (MVT) as defined in the Airport Handling Manual (AHM). For details about mapping from AHM 780 AIRCRAFT MOVEMENT MESSAGE to ADD, see MVT data to ADD data

Entity / ADD element
IataMvtData
  • ETOT 0..1 NILLABLE
  • AOBT 0..1 NILLABLE
  • ATOT 0..1 NILLABLE
  • ELDT 0..1 NILLABLE
  • EIBT 0..1 NILLABLE
  • ALDT 0..1 NILLABLE
  • AIBT 0..1 NILLABLE

IataDelay


IataPrmData

The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Passenger Assistance List (PAL), Change Assistance List (CAL) and Passenger Service Message (PSM).

PAL and CAL are defined in the Passenger Services Conference Resolutions Manual (PSCRM) Recommended Practice 1708a.
PSM is defined in the Passenger Services Conference Resolutions Manual (PSCRM) Recommended Practice 1715.

For more mapping information, see: PRM data to ADD data

Entity / ADD element
IataPrmData

IataPrmDestinationData 0..*

If PRM destination-data is missing it means that all PRM data related to this flight leg should be removed.


  • IataPrmPassengerInformation 

  • IataPrmPassengerService 



IataPtmData

The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Passenger Transfer Message (PTM) as defined in the Passenger Services Conference Resolutions Manual (PSCRM) RP 1718.

NB! Transfer data is FlightSegment-oriented.



Entity / ADD elementComments
IataPtmDataIdentifies the FlightSegment passengers transfer from. IataPtmTransferToData identifies the flight the passengers transfer to, and the number of passengers.

If part '1' comes again all transfer data previously received for this flight leg should be discarded, as it will be resent.

The FlightId for the flight segment. This will also be the FlightId for the arriving flight leg on the segment destination.

Date part of SOBT

The start airport for the flight segment. 

The end airport for the flight segment. Transfer information is from this airport. Flight leg transfer numbers are for the flight leg arriving at this airport.



IataPtmTransferToData 0..*

This is the flight passengers on the flight segment identified above transfer to. 
There will often be multiple data sets for the same flight. 

NB! If IataPtmTransferToData is "missing" then all previously received PTM data for this flight should be deleted. New PTM data will most likely be forthcoming.

FlightId for the connecting flight the passenger(s) transfers to.

Date of the connecting flight, local time. 
Transfer airport. This will be the same airport as the segment "ArrivalAirport" above. 
Destination airport for the passenger.

The name string as it appears on a ticket. Can contain multiple names.

Number of adult passengers transferring from the arriving flight leg, defined by the FlightSegment information, to the departing flight leg.

As above, but children.

As above, but infants.

As above, but for baggage.


110626443

The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA SSIM file row.

Entity / ADD element

IataSSMChangeFlightIdData

The figure below shows the Airport Data Dictionary based data structure representing the following IATA SSM message types:

  • FLT

For more information on the mapping from IATA SSM data to ADD, see: SSM data to ADD data


Entity / ADD element

IataSSMChangePeriodData

The figure below shows the Airport Data Dictionary based data structure representing the following IATA SSM message types:

  • REV

The table below lists, for ease of reference, the elements included in the entity. For more information on the mapping from IATA SSM data to ADD, see: SSM data to ADD data

Entity / ADD elementComments
IataSSMChangePeriodData


  • oldIataSSMPeriod
See definition → 
  • newIataSSMPeriod
See definition → 
Entity / ADD elementComments
IataSSMPeriodData





IataSSMDeleteData

The figure below shows the Airport Data Dictionary based data structure representing the following IATA SSM message types:

  • CNL 
  • SKD

The table below lists, for ease of reference, the elements included in the IataSSMDeleteData. For more information on the mapping from IATA SSM data to ADD, see: SSM data to ADD data

Entity / ADD element
IataSSMDeleteData




IataSSMInsertUpdateData

The figure below shows the Airport Data Dictionary based data structure representing the following IATA SSM message types:

  • NEW
  • RPL
  • ADM
  • CON
  • EQT
  • TIM

The table below lists, for ease of reference, the elements included in the IataSSMInsertUpdateData. For more information on the mapping from IATA SSM data to ADD, see: SSM data to ADD data


Entity / ADD element
IataSSMInsertUpdateData


IataSSMPeriodData 


IataSSMAircraftData 


IataSSMRoutingData 




70550297

Entity / ADD elementComments


If departure and arrival airport is omitted FlightId and FlightDepartureDate must identify a single leg in the relevant context.






ResponseStatus

statusCode : ResponseStatusCode

ResponseStatusCode indicates if the operation succeeded or failed, and if it failed - why. ResponseStatusText is a textual description of ResponseStatusCode. For all operations the set of response codes must be defined. The actual set is dependent upon the context.

 

  • "OK": Operation succeded.
  • "ERR01":
  • "ERR02":
  • "":
  • "":
  • "ERR99": Other error. "statusText" should describe the error.

 

Must be defined!

statusText : ResponseStatusText
A textual description of ResponseStatusCode.

TransData

CorrelationId
Identifier that can be used to correlate messages, transactions, log entries etc. The identifier should be unique across all relevant systems. It is the responsibility of the creator of the message/transaction/log entry/...  to guarantee uniqueness. The CorrelationId can for instance be a GUID, or something shorter based on site specific rules.
SourceOrganization
Name of the organization/company that created the original data. This will typically be an airline company or an handler. The value set are site specific.

SourceTimestamp

UTC timestamp for when the source was updated. If unknown, use current (UTC) time.
SourceData
SourceData will only exist when the source data is something else than XML or JSON. SourceData will typically be the IATA message or an EFD message from Eurocontrol.

  • No labels