Defines message metadata elements and some negotiation related elements in support of messaging-related aspects required by the FF-ICE/1 concept and guidance document: FF-ICE Manual d0.91.docx. =========================================== Copyright (c) 2020 Airservices Australia, DSNA, EUROCONTROL, GCAA UAE, IATA, International Coordinating Council of Aerospace Industries Associations, JCAB, NATS Limited, NAV CANADA, SESAR Joint Undertaking and US FAA =========================================== All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the disclaimer in the documentation and/or other materials provided with the distribution. - Neither the names of Airservices Australia, DSNA, EUROCONTROL, GCAA UAE, IATA, International Coordinating Council of Aerospace Industries Associations, JCAB, NATS Limited, NAV CANADA, SESAR Joint Undertaking and US FAA nor the names of their contributors may be used to endorse or promote products derived from this specification without specific prior written permission. DISCLAIMER THIS SPECIFICATION IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ========================================== Editorial note: this license is an instance of the BSD license template as provided by the Open Source Initiative: http://www.opensource.org/licenses/bsd-license.php The authoritative reference for FIXM is www.FIXM.aero. Details on Airservices Australia: http://www.airservicesaustralia.com/ Details on DSNA: http://www.developpement-durable.gouv.fr/-Navigation-aerienne-.html Details on EUROCONTROL: http://www.eurocontrol.int/ Details on IATA: http://www.iata.org/Pages/default.aspx Details on JCAB: http://www.mlit.go.jp/en/koku/index.html Details on NATS Limited: http://www.nats.co.uk/ Details on NAV CANADA: http://www.navcanada.ca/ Details on the UAE GCAA: https://www.gcaa.gov.ae Details on the ICCAIA: www.iccaia.org Details on the SESAR JU and its members: http://www.sesarju.eu/discover-sesar/partnering-smarter-aviation/members Details on the US FAA: http://www.faa.gov/ The FficeMessage element is an entry point to the FIXM model. Possible values of an operational filing status (ACCEPTABLE, NOT_ACCEPTABLE). [FF-ICE] The flight plan and in particular the Filed Trajectory/route is acceptable. [FF-ICE] The flight plan, typically the route/trajectory, does not comply with operational requirements. [FF-ICE] Represents the type of message. [FIXM] The ATS flight plan as provided by the pilot or a designated representative. [FF-ICE] Provides information concerning the status of the filed flight plan and typically concerns route/trajectory acceptability. [FF-ICE] A Flight Arrival message can be used in any situation where an ARR message would have been used per PANS-ATM 11.4.2.2.7. [FF-ICE] Used to delete or remove a flight plan (Preliminary and/or Filed). [FF-ICE] Used to obtain information about a flight. Designed to allow customized flight data queries, but the following should be a minimum set for implementation: a) Flight Plan - request a copy of the flight plan as submitted. b) Supplementary Plan - request a copy of the supplementary data filed for the flight. c) Flight Status - request a copy of the latest Planning or Filing status for the flight. [FF-ICE] Used to return the information requested by a Flight Data Request. [FIXM] A Flight Departure Message can be used in any situation where a DEP message would have been used per PANS-ATM 11.4.2.2.6. [FF-ICE] A Flight Plan Update may be used to update either a Preliminary Flight Plan or a Filed Flight Plan. [FF-ICE] Provides information concerning the status of the preliminary flight plan and typically concerns route/trajectory acceptability. [FF-ICE] Specified information submitted by an operator to conduct collaborative planning of a flight prior to submission of a Filed Flight Plan. [FF-ICE] An immediate response provided by an eASP to the message originator indicating acceptance or rejection of the message received. [FF-ICE] A Trial Request may be submitted to evaluate changes to either a Preliminary or Filed flight plan. Existing flight plan data will not be modified as a result of a Trial Request. [FF-ICE] Provides information concerning the status of a Trial Request and typically concerns route/trajectory acceptability. [FIXM] The applicable planning status values (CONCUR, NON_CONCUR, NEGOTIATE) of the route and trajectory, as submitted. [FF-ICE] The flight plan and in particular the route and trajectory is acceptable without the need for modification. This should mean that if the flight plan were to be filed, it would be accepted. [FF-ICE] The flight plan does not comply with published airspace/route availability or published restrictions and would result in a rejection or an unacceptable status if the flight plan were to be filed. [FF-ICE] The flight plan and in particular the route and trajectory is acceptable and would be accepted if filed. However the trajectory determined by the eASP has included additional constraints and/or has applied ATM configuration factors such as runway-in-use or Met data which may have resulted in a different trajectory. The operator is expected to assess the feedback and determine whether or not it wishes to amend it's Desired trajectory. [FF-ICE] The minimum set of flight information request types required by FF-ICE. [FF-ICE] Used to request the latest submitted flight plan. [FF-ICE] Used to request the latest status (Planning or Filing) from an eASP. [FF-ICE] Used to request the latest submitted search and rescue information. [FF-ICE] Type of participant, FF-ICE or NON_FF-ICE [FIXM] An ASP that is capable of providing FF-ICE services. [FF-ICE] An ASP that is unable to provide FF-ICE services. [FF-ICE] Possible values of a submission status (ACK, REJECT or MANUAL) [FF-ICE] An 'acknowledge' (ACK) response indicates that the message received can be processed by the eASP and will be acted upon. [FF-ICE] A 'manual' (MAN) response indicates that the message has been queued for manual processing. [FF-ICE] A 'rejected' (REJ) response indicates that the message received could not be processed. The message has therefore not been processed or acted upon by the eASP and none of the data has been retained. [FF-ICE] A Unit involved in performing Air Traffic Management responsibilities as introduced in the PANS-ATM. [FF-ICE] An extension hook for attaching extension (non-core) classes. Identification information and associated communication address(es) for an ATM service provider. [FF-ICE] Type of participant, FF-ICE or NON_FF-ICE [FIXM] A base class for all AtmServiceProvider class extensions. A discrete unit of communication, expressed electronically, and intended by the source for consumption by some recipient or group of recipients. [FF-ICE] An extension hook for attaching extension (non-core) classes. The status of the filed flight plan with respect to the eASP. [FF-ICE] A flight associated with the message. Indicates what information about the flight is being requested. [FF-ICE] A unique identifier for the latest version of a flight plan submitted by an Operator (Airspace User). A flight plan version should be operationally usable for verification that the pilot or operator and ATM personnel are using the same information for the flight. [adapted from ICAO Draft FF-ICE Implementation Guidance]. The identifier should begin at one and increase by one with each revision. Sender of the message [adapted from ICAO Draft FF-ICE Implementation Guidance] The status of the preliminary flight plan with respect to the eASP. [FF-ICE] The one or more intended recipients of the flight information. [adapted from ICAO Draft FF-ICE Implementation Guidance] The unique message identifier of the message being responded to. [FIXM] An ATM Service Provider whose airspace is entered by the flight plan route of flight or along the possible route of flight described in filed routing to a revised destination, and therefore should receive a flight plan from the operator of the flight. [FF-ICE] A status indicating if a message could be processed and acted on. [adapted from ICAO Draft FF-ICE Implementation Guidance] The time and date that the communication was sent. [FIXM] Identifies the provider that has been requested to translate and forward the message to identified translation recipients. [FF-ICE] The one or more intended recipients of the translation and forwarding service. [FF-ICE] Represents the type of message. [FIXM] A unique message identifier for FIXM messages. [FIXM] A base class for all FficeMessage class extensions. The Filing Status provides information concerning the status of the route and trajectory, as submitted. [adapted from ICAO Draft FF-ICE Implementation Guidance ] A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation Guidance] An extension hook for attaching extension (non-core) classes. Possible values of an operational filing status (ACCEPTABLE, NOT_ACCEPTABLE). [FF-ICE] A base class for all FilingStatusExtension class extensions. The Planning Status provides information concerning the status of the route and trajectory, as submitted.[adapted from ICAO Draft FF-ICE Implementation Guidance ] Textual explanation of the operational acceptability returned. [ICAO Draft FF-ICE Implementation Guidance] An extension hook for attaching extension (non-core) classes. The applicable planning status values (CONCUR, NON_CONCUR, NEGOTIATE) of the route and trajectory, as submitted. [FF-ICE] A base class for all PlanningStatus class extensions. Indicates what information about the flight is being requested. [FF-ICE] Used to represent any custom types established by a flight data request service. [FF-ICE] Indicates the type of information being requested. [FF-ICE] A status indicating if a message could be processed and acted on. [adapted from ICAO Draft FF-ICE Implementation Guidance] A textual description of the reason a message was rejected. [ICAO Draft FF-ICE Implementation Guidance] An extension hook for attaching extension (non-core) classes. Possible values of a submission status (ACK, REJECT or MANUAL) [FF-ICE] A base class for all SubmissionStatus class extensions.