- SESAR 2020
- SESAR 1
- ATM Master Plan
- ATM Architecture & Information Management
- Building the future Network
- Future airport operations
- Future ATC operations & systems
- Long-term research & innovation
- Business Cases and Cost Benefit Analyses
- Civil-military coordination
- Validation infrastructure
- Research cooperation
- Remotely Piloted Aircraft System (RPAS)
In late 2004 EUROCONTROL launched the “Flight Object Interoperability Proposed Standard (FOIPS)” study with EUROCAE as lead contractor to define a UML model for the Flight Object.
The only architectural assumption made at the start of the FOIPS study was that the Flight Object concept would be supported by a network of “Flight Object Servers (FOS)”, and hence the FOIPS study was tasked with defining two interfaces: the interface between a FOS and its clients, and the interface between different instances of a FOS.
The FOIPS model defines the Flight Object. It is composed of two complementary models: an ‘analysis model’ and a ‘usability model’. The analysis model is a UML model of the flight object, defining a standard set of services that it must provide. The usability model defines a set of access rights that determine under what conditions each stakeholder can invoke the services defined in the analysis model. The usability model also defines a set of “distribution clusters” that define the sub-components of the Flight Object that will be distributed and under what conditions.
The main immediate clients for the FOIPS model have been the ITEC and Coflight Data Processing Development Projects. These two projects cooperate in an Interoperability Consultancy Group (ICOG) and have used the Flight Object concept and the FOIPS model as the basis for the interoperability between their systems.
The original Analysis model:
The usability model: