The SSM operations does not support everything that is possible with SSM. All data elements are not supported and not all message types are supported. This is also reflected in the definition of IataSSMIdentifier. The mapping table below shows the SSM elements that are mapped to Airport Data Dictionary (ADD) elements. Not all are used in the SSM operations.
NB!
- For SSM elements that are duplicated in the structure below the the set "furthest down" is the one to use.
Entity / ADD element | SSM Element No. | Comments |
---|---|---|
IataSSMData | ||
Additional information about which detailed type of SSM this is. Insert / Update (SubmitSSMInsertUpdateData / IataSSMInsertUpdateData)
Delete (SubmitSSMDeleteData / IataSSMDeleteData)
Change FlightId (SubmitSSMChangeFlightIdData / IataSSMChangeFlightIdData)
Change period (SubmitSSMChangePeriodData / IataSSMChangePeriodData)
| ||
| Indicates if the SSM data can overwrite ASM data. | |
IataSSMFlightData | ||
IATA based identifier for this flight, usually issued long before the flight actually takes place. FlightId is normally the concatenation of OperatingAirlineIATA, FlightNumber and OperationalSuffix. FlightId typically identifies a flight to the majority of systems, but it is not unique across time. It's unique only in conjunction with FlightDepartureDate. Exception: Some airlines use their ICAO code (OperatingAirlineICAO) instead of OperatingAirlineIATA. This might be because they aren't an IATA member or because they just prefer the ICAO code. Regardless, this means that it is allowed to use OperatingAirlineICAO as part of FlightId. FlightId is then defined as the concatenation of AirlineIATAorICAO, FlightNumber and OperationalSuffix. | ||
| DEI 1. | Ignored NILLABLE |
DEI 2. | NILLABLE The airline code which will appear on the passengers' tickets for a codeshare for this flight. This can be either the IATA or ICAO code. See AirlineIATA or AirlineICAO for definition of content. | |
| DEI 3. | NILLABLE IATA code of the owner of the aircraft. See "AirlineIATA" for description of term. Not all aircraft are owned by an airline operator with an IATA code. |
| DEI 4. | NILLABLE Ignored |
| DEI 5. | NILLABLE Ignored |
| DEI 9. | NILLABLE The IATA code of the airline operating the flight. See AirlineIATA for definition of term. |
IataSSMExistingPeriode 0..1 | ||
Existing period, only used for SSM/REV | ||
IataSSMPeriodeData 1..* | There can be multiple periods for the same FlightId. | |
The first day of the Schedule. | ||
The last day of the schedule. This is actually the last day for the arriving flight. A departing flight can be up to ScheduleOverMidnights days later. | ||
Also known as DOOP, days of operation. This is a pattern that defines the days of the week which has scheduled flights. | ||
| Default 1 Also known as WOOP, weeks of operation. Allowed values are: | |
| DEI 1. | Ignored |
DEI 2. | NILLABLE Overrides any data "above" | |
| DEI 3. | NILLABLE Overrides any data "above" |
| DEI 4. | NILLABLE Ignored |
| DEI 5. | NILLABLE Ignored |
DEI 6. | NILLABLE The FlightId of the departing flight to which this flight (leg) is linked by a Turnaround. | |
| DEI 9. | NILLABLE Overrides any data "above" |
Pr. IataSSMPeriodeData New flight information 0..1 | The new FlightId. Only relevant for SSM/FLT. | |
Pr. IataSSMPeriodeData IataSSMAircraftData 0..* | ||
IATA SSIM Appendix C Service Types. | ||
3 character code as designated by International Air Transport Association (IATA) to uniquely designate Aircraft Type. Local (non-IATA) codes can be added as required as long as they are unique for aircraft types within the defined context. | ||
| Ignored | |
| Ignored | |
Detailed information about the aircraft configuration, received in the aircraft_conf_version field in the ASM and SSM IATA messages. | ||
DEI 2. | NILLABLE Overrides any data "above" | |
| DEI 3. | NILLABLE Overrides any data "above" |
| DEI 4. | NILLABLE Ignored |
| DEI 5. | NILLABLE Ignored |
DEI 6. 0..1 | NILLABLE Overrides any data "above" | |
| DEI 9. 0..1 | NILLABLE Overrides any data "above" |
Pr. IataSSMAircraftData or IataSSMPeriodeData IataSSMRoutingData 0..* | ||
Departure airport IATA code (see AirportIATA for description of term). | ||
FlightDepartureDate is the departure date for a flight (leg), or the date for the first departure on a multi leg flight. The number of midnights between FlightDepartureDate and the SOBTotp for one leg of a multi leg flight. For the first leg DepartureOffsetFromFlightDepartureDate will always be 0. | ||
| The "departure time" that the passenger should see. | |
Arrival airport IATA code (see AirportIATA for description of term). | ||
FlightDepartureDate is the departure date for a flight (leg), or the date for the first departure on a multi leg flight. The number of midnights between FlightDepartureDate and the SIBTotp for one leg of a multi leg flight. | ||
| The "arrival time" that the passenger should see. | |
| DEI 1. | NILLABLE Ignored |
DEI 2. | NILLABLE Overrides any data "above" | |
| DEI 3. | NILLABLE Overrides any data "above" |
| DEI 4. | NILLABLE Ignored |
| DEI 5. | NILLABLE Ignored |
DEI 6. | NILLABLE Overrides any data "above" | |
| DEI 7. | NILLABLE Ignored |
| DEI 9. | NILLABLE Overrides any data "above" |
| DEI 10 | NILLABLE The "full" FlightId for the codeshare flight (leg). |
Pr. period Segment information 0..1
| Ignored, apart from any codeshare information. | |
Pr. period Supplementary information 0..1 | Ignored | |