The figure below depicts the Level 3 implementation progress for reference year 2018 as described in the Progress report 2019. A detailed analysis of each objective is provided in the Implementation Objectives (Monitoring) section.
The 2019 report (showing the situation at the end of 2018) is based on the Master Plan Level 3 2018 Implementation Plan that included 48 active implementation objectives, monitored at national/local level.
Overall, the implementation progress of the Master Plan Level 3 at ECAC level is steady, with advances in implementation recorded all across the ECAC area and the ATM domains. For 32 objectives, at least one State/Airport has finalised completion in 2018 while the implementation of one objective (Short Term ATFCM Measures – Phase 1) has been completed.
25% of implementation objectives progress on-time, planning the full achievement within prescribed dates. There are around 35% of Level 3 implementation objectives that are either already beyond the initially planned completion dates, or are planned to be delayed while for 7% there is a risk of delay.
These need to be closely followed by appropriate authorities and mitigation measures need to be put in place. This is particularly important for the items that are identified as important pre-requisites or enablers for the PCP. Without the pre-requisites deployed, there is a risk that major SESAR functionalities will be delayed for implementation (e.g. a delayed deployment of A-SMGCS Surveillance will impact the deployment of more advanced A-SMGCS functionalities. Delays in the implementation of objectives related to the aviation infrastructure will affect the introduction of new operational concepts).
For 31% of the objectives an estimated completion date cannot be defined at this time. This is mostly because the implementation of these objectives is still in very early planning phases and it is therefore premature to establish implementation trends and fully reliable estimated achievement dates. This 31% also includes the Five (5) “Local” Objectives. These “Local” Objectives are addressing solutions considered beneficial for specific operating environments, therefore for which a clear widespread commitment for implementation has not been expressed yet. Typically this is the case for local deployments which may include selected main/core operating environments, subject to positive business cases at local level. As such, these Objectives do not have an associated completion date, nor a predefined applicability area, therefore there is no baseline to assess the estimated achievement date.