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. The table below shows the mapping from PSCRM 1708a and 1715 to ADD. Since it is the same data it is mapped once to the IataPrmData that are used to represent data from PAL, CAL and PSM. |
| Entity / ADD element | PSCRM 1708a Element No. | PSCRM 1715 Element No. | Comments |
|---|---|---|---|
| IataPrmData | |||
| 1.1 | Additional information about which detailed type of PRM message this is. | ||
| 2.4 | 2.4 | 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. | |
| 2.4 | 2.4 | The message contains scheduled departure date for the flight leg, local time. This must be converted to FlightDepartureDate before the service is called. | |
| 2.4 | 2.4 | The airport where the passenger boards the aircraft. Boarding point. Departure airport IATA code (see AirportIATA for description of term). | |
| 2.4 | 2.4 | Message part of any number of PRM data for this flight. Special handling for IataMessagePart = 1. For IATA messages with multiple "parts". | |
| 2.11 | |||
| PrmDestinationData 1..* | PrmDestinationData represents the destination specific data in the PAL/CAL/PSM message. | ||
There is always at least one destination. The AirportIATA that are the destination for the relevant FlightSegment. | |||
| 2.5 | 2.7 | Booking class (fare class) coded in accordance with IATA resolution 728. | |
| 2.5 | 2.7 | "True" : All information related to this booking class shall be deleted. This corresponds to "NIL" in message for the booking class. "False": Message contains passenger information. Indicates whether information regarding the indicated BookingClass should be deleted or not. | |
| |||
| 2.9 | 2.8 | The last name of a passenger | |
| 2.9 | 2.8 | The first (and middle) name of a passenger |
| 2.9 | 2.8 | Normally the passengers title (e.g MR, MRS....) | |
| NEW ADD term, og i modellen
| ||
| 2.10 | For transfer at DepartureAirportIATA (boarding point). The passenger arrives on InboundFlightId and departs on this flight (FlightId). The inbound FlightId for "something", for instance a passenger. | |
| NEW ADD term Must be derived from the local date/time that might be included in the PRM data. | ||
| 2.11 | 2.9 | For transfer at SegmentDestinationIATA. The passenger arrives on this flight (FlightId) and departs on OutboundFlightId. The outbound FlightId for "something", for instance a passenger. |
| NEW ADD term Must be derived from the local date/time that might be included in the PRM data. | ||
| |||
| 2.12 | 2.12 | Additional codes than the IATA defined ones can occur. | |
| 2.12 | 2.12 | NEW ADD term, type remarktext? NB!! Hva var dette egentlig?? Kommentar knyttet til request-koden. |