ecip œ years 2002 to 2006 - level 2 · pdf fileecip œ years 2002 to 2006 - level 2...

ECIP � YEARS 2002 TO 2006 - LEVEL 2

i

DOCUMENT IDENTIFICATION SHEET

TITLE

European Convergence and Implementation Plan for the years2002 to 2006 - Level 2

EATMP Infocentre Reference: 010627-2Document Identifier Edition: 1.1

Edition Date: October 2001Abstract

The European Convergence and Implementation Plan (ECIP) is a central element in theoverall planning process for European ATM. Its purpose is to provide a Europe-wide, high-level implementation plan driven by performance requirements. These performancerequirements reflect the strategic principles and objectives set out in the ATM 2000+ Strategy,as well as the overall performance and safety objectives developed by the PerformanceReview Commission (PRC) and Safety Regulation Commission (SRC).The ECIP document is in two volumes - Level 1 and Level 2.Level 1 provides an overview and context for performance target setting together with detailsof the main implementation objectives to meet the targets.Level 2 - this document - sets out the performance targets that need to be achieved by States,and more detailed descriptions of the Implementation Objectives and Stakeholder Lines ofAction (SLoA) for each of the aviation stakeholders. The SLoA describe the actions that eachstakeholder must take to help realise the performance objectives and meet the performancetargets.

KeywordsEUROCONTROL EATMP ECIP ATM performance

planningContact Person(s) Tel Unit

R. Stewart 3695 DSA/PPMB. Miaillier 3309 SDE/SCS

STATUS, AUDIENCE AND ACCESSIBILITYStatus Intended for Accessible via:

Working Draft � General Public � Intranet �

Draft � EATMP stakeholders � Extranet (not yet implemented)Proposed Issue � Restricted audience � Internet �

Released Issue �

ELECTRONIC SOURCEPath: P:\Ecip\ECIP years 2002-2006\ECIP Level 2\ECIP L2 Ed_1_1

Host System: Software: Size:Windows_NT Microsoft Word 8.0b 2164 KB


ii

DOCUMENT HANDLING

Document copies :

Hard and soft copies of the document can be obtained from the EATMP Infocentre.

EUROCONTROLEATMP Infocentre

96 Rue de la Fusée, B-1130 BRUSSELSTel: +32 (0)2 729 5151, Fax: +32 (0)2 729 9984Open 08:00h - 15:00h UTC Monday-Thursday.

[email protected]

DOCUMENT CHANGE RECORD

The following table records the complete history of the successive editions of the presentdocument.

EDITION DATE INFOCENTREREFERENCE

REASON FOR CHANGE PAGESAFFECTED

N/A 19/04/2001 N/A New/revised objectives circulated to ACG Sections 4and 5

N/A 31/05/2001 N/A New/revised objectives circulated to ACGand PC

Sections 4and 5

1.0 18/07/2001 010627-2 Document revised and upgraded toReleased Issue

All

1.1 10/10/01 010627-2 Insertion of minor changes to ObjectivesStates and SloAs timescales

Sections 4and 5


iii

TABLE OF CONTENTS

DOCUMENT IDENTIFICATION SHEET............................................................................................ iDOCUMENT CHANGE RECORD .................................................................................................... iiTABLE OF CONTENTS .................................................................................................................. iiiLIST OF IMPLEMENTATION OBJECTIVES IN THE ECIP 2002-2006.......................................... ivLIST OF IMPLEMENTATION OBJECTIVES RANKED BY PLANNED ACHIEVEMENT DATE.... vEXECUTIVE SUMMARY ................................................................................................................ vii

1. PURPOSE..................................................................................................... 1-1

1.1 Purpose of the ECIP...........................................................................................................................1-11.2 Structure and intended audience .......................................................................................................1-21.3 Planning horizon ................................................................................................................................1-21.4 Geographical scope.............................................................................................................................1-21.5 Former CIP Objectives .......................................................................................................................1-21.6 Update cycle ........................................................................................................................................1-31.7 Consultation and approval .................................................................................................................1-41.8 Roles and responsibilities ...................................................................................................................1-61.9 The ECIP 2002-2006 Document .......................................................................................................1-7

2. FROM STRATEGY TO PERFORMANCE DELIVERY................................ 2-1

2.1 Improving ATM performance ............................................................................................................2-12.2 Identifying Performance Targets .......................................................................................................2-12.3 Identifying the ATM changes needed to meet the Performance Requirements ...............................2-22.4 Defining the Implementation Objectives and identifying Programmes............................................2-32.5 Types of Objectives .............................................................................................................................2-32.6 Status of Implementation Objectives..................................................................................................2-32.7 Local planning and implementation ..................................................................................................2-52.8 The LCIP Documents .........................................................................................................................2-52.9 Monitoring progress and status reporting .........................................................................................2-62.10 Planning overview ..............................................................................................................................2-6

3. PERFORMANCE TARGETS ........................................................................ 3-1

3.1 General................................................................................................................................................3-13.2 How capacity targets are set ...............................................................................................................3-13.3 Capacity Targets in the ECIP 2002-2006 ..........................................................................................3-3

4. OBJECTIVES AND STAKEHOLDER LINES OF ACTION........................... 4-1

4.1 Implementation Objectives and SLoA................................................................................................4-14.2 Key to the Implementation Objective template ..................................................................................4-14.3 Key to the SLoA template ...................................................................................................................4-3

5. LINES OF ACTION GROUPED BY STAKEHOLDERS ............................... 5-1

ANNEX A � TRACEABILITY OF ECIP OBJECTIVES TO FORMER CIP OBJECTIVES .. A-1

ANNEX B - ACRONYMS & ABBREVIATIONS ........................................................... B-1

ANNEX C- REFERENCES .......................................................................................... C-1


iv

LIST OF IMPLEMENTATION OBJECTIVES IN THE ECIP 2002-2006Colour code: Pan-European Multi-National Harmonisation

Id. Objective Title Status SupportingProgramme

Page

AOM01 Implement Reduced Vertical Separation Minimum Confirmed RVSM 4.7

AOM02 Implement Free Routes Airspace in Eight States Airspace Tentative FRAP 4.9

AOM04 Implement ATS Route Network (ARN) - Version 4 Confirmed AOM 4.13AOM05 Optimise airspace sectorisation Confirmed AOM 4.15AOM06 Implement Flexible Use of Airspace (FUA) concept Confirmed AOM 4.17AOM07 Implement collaborative civil-military airspace planning at national level Tentative AOM 4.19AOM08 Optimise terminal airspace structure Agreed AOM 4.21AOM09 Implement re-organisation of ECAC airspace to ensure the application of a

common ICAO ATS classification above a common agreed levelTentative AOM 4.23

AOM10 Implement ATS Route Network (ARN) � Version 5 Tentative AOM 4.27AOP01 Implement runway capacity enhancement guidelines Tentative AOP 4.29AOP02 Implement use of the Commonly Agreed Methodology for Airport Airside

Capacity Assessment (CAMACA) ToolTentative AOP 4.31

ATC01 Implement Airborne Collision Avoidance System (ACAS) II Confirmed ACAS 4.33ATC02 Implement ground based safety nets Confirmed ASA 4.39ATC03 Implement advanced automated ground-ground co-ordination Confirmed ASA 4.41ATC04 Achieve required radar separation minima Confirmed N/A 4.43ATC05 Improve procedure through Mode S Elementary Surveillance information Confirmed Mode S 4.45ATC06 Implement ATC Air-Ground Data Link services (Phase 1) Confirmed Link2000+ 4.47ATC07 Implement arrival management tools Proposed ASA 4.51COM02 Extension of the use of 8.33 kHz VHF frequency channels Agreed 8.33 kHz 4.53DPS01 Implement flight data processing (FDP) core functionality Confirmed N/A 4.57FAC01 Implement ATS Provision in the upper airspace of the Central European

(CEATS) StatesConfirmed N/A 4.61

FCM01 Implement Enhanced Traffic Flow Management Services Confirmed ATFM 4.63

FCM02 Initial capacity management Agreed OCM 4.67

FCM03 Implement collaborative flight planning Confirmed ATFM 4.69

HUM01 Timely availability of controllers Confirmed HRS 4.73HUM02 Implement harmonised selection, recruitment and training of ATM staff Confirmed HRS 4.75HUM03 Implement the full integration of human factors into the lifecycle of ATM

systemsProposed HRS 4.79

INF01 Implement the European Aeronautical Information Services (AIS) Database Confirmed EAD 4.81INF02 Implement ISO 9001:2000 in aeronautical information Confirmed AIS AHEAD 4.85INF03 Implement improved aeronautical information Proposed AIS AHEAD 4.87MIS01 Improve the management and optimise the operational use of the

aeronautical frequency assignments in allocated radio bandsConfirmed N/A 4.91

MIS02 Implement contingency planning and procedures Confirmed N/A 4.93

NAV01 Assure Satellite-Based augmentation systems (SBAS) navigation service foraviation needs

Proposed GNSS 4.95

NAV02 Assure ground-based augmentation systems (GBAS) Cat 1 � based precisionapproach service for aviation needs

Proposed GNSS 4.99

NAV03 Implement Precision Area Navigation (P-RNAV) as an interim towardsRequired Navigational Performance (RNP) RNAV

Agreed NAV 4.103

NAV04 Implement approach procedures using Area Navigation (RNAV) with verticalguidance (ICAO APV1)

Agreed NAV 4.109

SAF01 Implement a safety management system for ATM Service Providers Confirmed ESARR3 4.113SRC02 Implement ESARR2 on reporting and analysis of safety occurrences in ATM Confirmed ESARR2 4.115SRC03 Implement ESARR3 on the use of safety management systems by ATM

Service ProvidersConfirmed ESARR3 4.119

SRC04 Implement ESARR4 on risk assessment and mitigation in ATM Confirmed ESARR4 4.123SRC05 Implement ESARR5 on ATM services� personnel Confirmed ESARR5 4.127SUR01 Implement Dual Secondary Surveillance Radar (SSR) coverage Confirmed N/A 4.131SUR02 Implement Mode S Surveillance Confirmed Mode S 4.135SUR03 Implement Radar Data Processing and Distribution Systems Tentative N/A 4.137


v

IMPLEMENTATION OBJECTIVES SORTED BY PLANNED ACHIEVEMENT DATEColour code: Pan-European Multi-National Harmonisation

Only Implementation Objectives with a planned achievement date are listed below.

Id. Objective Title Status Achievementdate

Page

MIS02 Implement contingency planning and procedures Confirmed 12/2000 4.93ATC02 Implement ground based safety nets Confirmed 12/2001 4.39DPS01 Implement flight data processing (FDP) core functionality Confirmed 12/2001 4.57

AOM01 Implement Reduced Vertical Separation Minimum Confirmed 01/2002 4.7SRC02 Implement ESARR2 on reporting and analysis of safety occurrences in ATM Confirmed 01/2002 4.115AOM04 Implement ATS Route Network (ARN) - Version 4 Proposed 04/2002 4.13COM02 Extension of the use of 8.33 kHz VHF frequency channels Agreed 10/2002 4.53AOM09 Implement re-organisation of ECAC airspace to ensure the application of a

common ICAO ATS classification above a common agreed levelTentative 04/2003 4.23

SAF01 Implement a safety management system for ATM Service Providers Confirmed 07/2003 4.113SRC03 Implement ESARR3 on the use of safety management systems by ATM

Service ProvidersConfirmed 07/2003 4.119

SRC05 Implement ESARR5 on ATM Services� personnel Confirmed 11/2003 4.127INF02 Implement ISO 9001:2000 in aeronautical information Confirmed 12/2003 4.85SRC04 Implement ESARR4 on risk assessment and mitigation in ATM Confirmed 04/2004 4.123AOM10 Implement ATS Route Network (ARN) � Version 5 Tentative 06/2004 4.27INF03 Implement approved Aeronautical Information Proposed 12/2004 4.87

ATC01 Implement Airborne Collision Avoidance System (ACAS) II Confirmed 01/2005 4.33

NAV01 Assure Satellite-Based augmentation systems (SBAS) navigation service foraviation needs

Proposed 01/2005 4.95

NAV04 Implementation of approach procedures using RNAV with Vertical Guidance(ICAO APV1)

Agreed 01/2005 4.109

FCM03 Implement Collaborative Flight Planning Confirmed 12/2005 4.69

MIS01 Improve the management and optimise the operational use of theaeronautical frequency assignments in allocated radio bands

Confirmed 12/2005 4.91

FAC01 Implement ATS Provision in the upper airspace of the Central European(CEATS) States

Confirmed 10/2007 4.61

HUM01 Timely availability of controllers Confirmed 12/2007 4.73HUM02 Implement harmonised selection, recruitment and training of ATM staff Confirmed 12/2007 4.75HUM03 Implement the full integration of human factors into the lifecycle of ATM

systemsProposed 12/2007 4.79

IMPLEMENTATION OBJECTIVES ACHIEVED IN 2000(and no longer included in the ECIP document)

Colour code: Pan-European Multi-National Harmonisation

AOM03 Implement ATS Route Network (ARN) Version 3 Confirmed 12/1999 N/A

COM01 Implement 8.33 kHz VHF frequency spacing Confirmed 10/1999 N/A


vi

Page left intentionally blank


vii

EXECUTIVE SUMMARY

The European Convergence and Implementation Plan (ECIP) is a commonplanning and implementation document for improving European ATM, andtakes as its foundation the need to set and realise specific quantifiable andmeasurable ATM Performance Targets for the ECAC States in the key ATMperformance areas.

These targets are aligned with the strategic principles and high-levelobjectives set out in the EUROCONTROL ATM 2000+ Strategy, and reflectthe recommendations of the Safety Regulation and Performance ReviewCommissions and Civil Military Interface Committee. They are derived throughan iterative strategic planning and Strategy Review and Update process thatexpands and translates the top-level EUROCONTROL ATM 2000+ Strategyobjectives and operational changes into a manageable and consolidated setof Operational Improvements through time that will satisfy the ATMperformance requirements.

Mature Operational Improvements generate ECIP ImplementationObjectives that set out the actions needed to apply the operational changes inATM processes and systems. In turn, Implementation Objectives lead toEuropean Air Traffic Management Programme (EATMP) programmes thatwill realise the objectives and deliver the performance benefits needed torealise the Performance Targets.

The Implementation Objectives and SLoA cascade down to, and provide thefoundations for building, the national Local Convergence and ImplementationPlans (LCIPs).

The ECIP document is divided into Level 1 and Level 2.

� Level 1 describes briefly the overall planning and target setting processes andsummarises the Implementation objectives needed to achieve the OperationalImprovements and realise the Performance Targets

� Level 2 - this document - gives Performance Targets for the mainEUROCONTROL ATM 2000+ Strategy strategic objectives and provides moredetailed descriptions of the ECIP Implementation Objectives and their associatedStakeholders Lines of Action (SLoA)

The LCIPs - one for each ECAC State - describe the national actions that flowdown from the ECIP, and set out States' national plans describing how theywill meet their national performance targets.


viii


ECIP � YEARS 2002 TO 2006 - LEVEL 2 PURPOSE

1-1

1. PURPOSE

1.1 Purpose of the ECIPThe European Convergence and Implementation Plan (ECIP) is a keyelement in the overall European Air Traffic Management (ATM) planningprocess. Its purpose is to provide a Europe-wide, Implementation Plan forimproving ATM performance that is driven by clearly defined requirements andPerformance Targets for the key ATM performance areas, in line with the top-level EUROCONTROL ATM Strategy for the years 2000+ (ATM 2000+Strategy)1 principles and objectives.

The ECIP represents the common ATM plan for the EUROCONTROL Statesand ECAC States participating in the European Air Traffic ManagementProgramme (EATMP).

The ECIP document sets out indicative Performance Targets for theEuropean ATM network that are needed to satisfy the forecast traffic demand,together with the most current set of Implementation Objectives aimed atmeeting those targets. The targets and objectives provide the basis for co-operative planning amongst the aviation stakeholders based on commonlyagreed actions and activities aimed at improving the European ATM systemand services in line with the forecast increase in air traffic demand.

The ECIP Implementation Objectives are derived from an elaborated andcohesive set of Operational Improvements generated by the StrategicPerformance Framework (SPF) and Representation of Overall ATMDevelopment (ROAD) activities that form part of the ATM 2000 + StrategyReview and Update process.

Each Implementation Objective is broken down into a set of relatedStakeholder Lines of Action (SLoA) that describe the generic activities thateach of the different stakeholders categories will need to take to ensure thesuccessful completion of the objective, together with the time scales involved.

The results of this work cascade down into Local CIP (LCIP) documents,which set out States' capacity plans and implementation activities intended tomeet national Performance Targets derived from the network targets.

1.2 Structure and intended audienceThe ECIP comprises 2 documents:

Level 1 is aimed at senior managers. It describes briefly how PerformanceTargets and Implementation Objectives are derived, and gives a top-leveldescription of the Implementation Objectives included in the ECIP Level 2document.

Level 2 - this document - is aimed at the planning and working levels of thedifferent aviation stakeholders2. It explains briefly the ECIP purpose and how

1 ATM Strategy for the Years 2000+; Volumes 1 & 2, dated January 20002 Stakeholder categories are defined in the EATMP Stakeholder Segmentation Model. However, for ease of reference, MilitaryAuthorities are identified as a separate single stakeholder category in the ECIP rather than as belonging to a number of differentstakeholder categories in their various functions as aircraft operators, service providers, regulatory authorities, etc.


1-2

targets and Implementation Objectives are derived, lists nationalPerformance Targets for the ATM key performance areas, and providesdetailed descriptions for each European-level Implementation Objectivegiven in the ECIP Level 1, together with those of the associated SLoAs. Forease of reference, it also provides top-level lists of all of the SLoA applicableto each stakeholder category.

The overall format of Level 2 is as follows:

Chapter 1 - sets out the purpose and scope of the ECIP and ECIP document

Chapter 2 - explains briefly how Implementation Objectives and SLoA arederived

Chapter 3 - lists the agreed targets for each of the key ATM performanceareas3

Chapter 4 - provides descriptions of the Implementation Objectives and theirSLoA

Chapter 5 - groups and lists the SLoA by individual stakeholder categories

Chapters 1 to 4 are contained in the white pages, and Chapter 5 in colourcoded pages according to Stakeholder category (see page 5-1 for the colourconvention used).

The ECIP Level 2 is a stand-alone, 'expert-level� document intended to assistplanning staffs in developing their national ATM plans. It expands on some ofthe information given in the ECIP Level 1 document to provide context and aidunderstanding of the process and activities involved, but does not repeat all ofthe Level 1 content or information. Readers wishing to have a completeoverview of the ECIP process should therefore also consult the Level 1document.

1.3 Planning horizonThe ECIP is part of a continuous planning process. It has an initial rolling 'lookahead' planning horizon of 5 years, but fits within the framework of theStrategy Review and Update process and associated Strategic PerformanceFramework (SPF), which encompasses planning out to 20 years ahead.However, the time horizon used in the ECIP document may be expanded inlater editions to include outline details of other potential longer-termoperational improvements, to help provide a more complete picture of likelychanges in the European ATM network over the next 15 to 20 years.

This second ECIP edition covers the calendar years from 2002 to 2006.

1.4 Geographical scopeThe ECIP includes the Air Traffic Control units within the EUROCONTROLStates as well as other ECAC States participating in the EATMP.

1.5 Former CIP Objectives

Objectives and actions outstanding from the former Convergence andImplementation Programme4 have been mapped to the new ECIP

3 At present only capacity targets for each of the European Air traffic Control Centres (ACCs) are included. Performance targetsfor the other key ATM performance areas will be added at a later date once they become available.


1-3

Implementation Objectives to reflect the decision taken by the ECACTransport Ministers at their MATSE/6 meeting that States should completethese as soon as possible. The relationship of the new ImplementationObjectives to the old CIP objectives is given in Annex A.

1.6 Update cycleThe ECIP is an iterative document that reflects actual and forecast events,and both the Level 1 and Level 2 documents will be updated each year toreflect the progress made towards improving the European ATM system.

The ECIP/LCIP development follows a yearly cycle with activities split into fourmain parts:

• The day-to-day management of the available capacity within a timehorizon of one year;

• Performance planning5 and implementation planning through theECIP/LCIP process covering the following 5 years;

• Monitoring activities to assess past performance;• The analysis of planned improvements to identify potential capacity

shortfalls early in the process.

The development cycle starts with the analysis of the traffic evolution andcapacity increase achieved for the Summer period (year N), leading to arefinement of the national short-term capacity targets for the next Summerseason (year N+1). This refinement may require some actions planned forimplementation prior to the next Summer season by States and ANS providersto be adapted, or lead to additional short term improvements. This part of thecycle is managed through the CFMU working arrangements involving theEAG, Directors' of Operations Meeting, etc, and activities are aimed atoptimising the use of the available capacity.

The review of the past Summer period leads also to a revision of the medium-term capacity targets for the additional four years (years N+2 to N+5) fornational Air Traffic Control Centres (ACCs), and to the definition of newPerformance targets for the fifth year of the planning process (N+6). (Capacitytarget setting activities are described in greater detail in Chapter 3)

In parallel with the target setting activities, ECIP Implementation Objectivesand SLOAs are reviewed to reflect the progress made in the associatedprogrammes or Domain activities towards implementation and realisation ofthe objectives. The revision and update of the ECIP ImplementationObjectives is progressed in consultation with the Domain Teams andProgramme Steering Groups, and also takes into account changes generatedthrough the Strategy update process.

Following consultation with stakeholders and agreement by the ACG to thenational targets and objectives for years (N+2 to N+6), the ECIP Level 1 andLevel 2 Documents are updated and circulated.

Circulation of the revised ECIP documents allows States to start work onrevising their plans and LCIP documents (for years N+2 to N+6).

4 CIP, Edition 3.2.5 Initially only capacity planning is included.


1-4

The yearly cycle is completed with the publication of the Status Report in earlySpring summarising the overall performance of the European ATM system,and the progress made towards realising the ECIP objectives and SLOA, inthe past year, together with forecasts of the likely capacity situation at ACCsbased on States' plans as set out in their LCIP documents.

This overall update cycle is shown in the ECIP/LCIP Update Cycle diagrambelow.

ECIP/LCIP update cycle

1.7 Consultation and approvalPerformance Targets and Implementation Objectives are endorsed by theEUROCONTROL Provisional Council based on the agreement of theATM/CNS Consultancy Group (ACG) and, where appropriate, the EuropeanATFM Group (EAG) and Civil Military Interface Committee (CMIC), as well asrecommendations stemming from the Safety Regulation and PerformanceReview Commissions (SRC and PRC).

The endorsement stage is reached following an extensive and iterativeconsultation process embodied in the EATMP working arrangements. These

Year N+1Year NQ1 Q2 Q3 Q4 Q1Q4 Q2 Q3

Capacity management

Refinetarget Year

N

Short termmngt. Year

N

Summerreview

Year N

Refinetarget Year

N+1

Short termmngt Year

N+1

Summerreview

YearN+1Monitoring

ECIPStatusReport

ECIPStatusReport

Planning of following years

Review targetYears N +2 to

N+4

Review targetYears N +3 to

N+5

ECIPYears N-1

to N+5

ECIPYears N-2

to N+6

LCIPD'sYears N-1 to N+5

Update Objectives &SloA's

Update Objectives &SloA's

LCIPD'sYears N-2 to N+6


1-5

arrangements involve the Domain Teams, financial groups, ProgrammeSteering Groups, States Focal Points, stakeholder representatives, etc.

The consultation and change process ranges from investigation work at expertteam level to policy and priority setting by Senior Managers and takes intoaccount:

� The strategic fit with short, medium and longer term plans includingtimings and priorities based on the performance of the overall ATMnetwork carried out by the EATMP Strategy, Concept and Systems (SCS)Unit and Team (SCST);

� Programme proposals based on mature ideas and sub-strategiesemanating from the Domains and Domain Teams;

� Actual progress of the programmes;

� The implementation progress made by the States and various stakeholdergroups;

� Budget priorities, needs and volumes.

Each change is subjected to consultation and approval at the appropriatelevels:

New Objectives

New objectives' descriptions and detailed SLoA are developed by theDomains in agreement with the Domain Teams. The objective descriptionsand high-level lists of SLoA will then be passed to the ACG, or EuropeanATFM Group (EAG), as appropriate for their agreement. Once this agreementhas been obtained, a high-level objective description is circulated to theEUROCONTROL Provisional Council for their endorsement for the objectivesto be included in the ECIP.

Existing Objectives

Changes to existing objectives and SLoA are processed and agreed by theDomain Teams or Programme Steering Groups as appropriate6, and will notnormally be notified to the ACG unless this is considered advisable by theTeam or Steering Group members concerned. The exception is where thereis a significant change to an objective (the description, scope, or an extensivedelay in agreed milestones, etc) when the objective will be re-submitted to theACG/EAG and, their advice sought as to whether or not the objective shouldalso be re-submitted to the Provisional Council for re-endorsement.

Once this process has been completed, the changes are included in the ECIPLevel 1 document and reflected in the Level 2 content in line with the updatecycle set out in paragraph 1.6.

An overview of the approval levels and information concerned is shown below.

6 Changes to the status of an objective (ie: Tenative, Confirmed, etc) are linked to the programme life cycle (see Chapter 2,paragraph 2.6). and are a reflection of the progress of activities. Approval of such changes is part of the normal PSG/Domainworking arrangements, and are not usually notified separately to the ACG or Provisional Council.


1-6

TITLE - SCOPE -TIMESCALE

APPLICABLE AREA

IMPLEMENTATIONOBJECTIVE

FRONT PAGE DESCRIPTIONDefinition

Relationship to EATMPPerformance benefits

Main resource requirementsList of SLoAs & timescales

SLoA DESCRIPTIONDefinition

StakeholderApplicability

Achievement criteria

CREATION OF ANEW OBJECTIVE

CHANGE TO ANEXISTING OBJECTIVE

ProvisionalCouncil

A C G

Teams and PSGs

(ACG if consideredappropriate by Teams /

PSGs)

ProvisionalCouncil

Teams andPSGs

Approval levels for Implementation Objectives

1.8 Roles and responsibilitiesRoles and responsibilities in relation to the ECIP stem from the earlyimplementation of certain provisions in the revised EUROCONTROLConvention, and the full recognition of the EUROCONTROL Agency's role asthe managing agent of the EUROCONTROL Organisation's tasks.

The national targets published in the ECIP are intended primarily as an aid toplanning by identifying potential problems and allowing solutions to bedeveloped and put in place in good time. Nevertheless, the overallperformance planning approach using the ECIP and LCIP documentation andprocedures has been accepted by the EATMP stakeholders as the basis todefine the necessary planning actions, and stakeholders' signature of LCIPdocuments indicates their agreement that they will apply their bestendeavours to complete their agreed actions within the time scales set.

Role of the EUROCONTROL Agency:

Within the framework of the overall performance-driven planning, the role ofthe Agency is to:

� Assess past performance, forecast demand and set Performance Targetsfor the key ATM performance areas in co-operation with States;


1-7

� Identify the mature set of Operational Improvements needed to improvethe performance of the European ATM and meet the PerformanceTargets;

� Identify, and monitor the progress in implementing, the ImplementationObjectives, SLoA and supporting programmes needed to realise theOperational Improvements;

� Maintain, update and publish yearly the ECIP as the European ATMcommon medium term plan;

� Support the national stakeholders in developing plan and undertaking theappropriate actions to meet their assigned Performance Targets throughthe medium of their LCIP documents;

� Confirm the alignment of States plans with overall ECIP activities by co-signature of States' LCIP Level 1 documents;

� Monitor and report on plans, implementation and actual performancethrough the yearly Status Report.

Role of States and National Stakeholders:

In addition to their role in the consultation and decision-making processes ofthe EUROCONTROL Organisation, States are responsible for consulting withtheir ANS providers and other relevant national stakeholders (eg: militaryauthorities, airports, airlines, etc), on the actions necessary to achieve thePerformance Targets for their ATM units, in line with the ImplementationObjectives of the ECIP.

These plans, and the actual progress in implementation and performanceenhancement, will be documented in the LCIP for each State. In this context,all involved stakeholders (military authorities, airports, aircraft operators, etc)are also encouraged to participate in the national planning processes and,where appropriate, to develop their own planning documents to reflect theiragreed involvement.

1.9 The ECIP 2002-2006 DocumentA consolidated set of Operational Improvements to enhance the EuropeanATM network in the longer term is being developed within the StrategicPerformance Framework but is not yet available. Additionally, many of theOperational Improvements require Research and Development work beforethe potential benefits that they offer can be quantified and prioritised, and theappropriate Implementation Objectives derived.

This second edition of the ECIP is therefore still limited in scope to providingindicative Performance Targets for capacity for en-route Air TrafficControl units for each of the ECAC States, together with a limited set ofSafety and Capacity related Implementation Objectives. Additional targetsand objectives for other key performance areas will be added in subsequenteditions.

The current document includes a number of new Implementation Objectivesand associated SLoAs in addition to those published in the ECIP for the years2000-2005. The period covered has also been re-aligned to reflect thechanges to the ECIP/LCIP development cycle requested by the ACGmembers to better align with States' planning timetables, and the document


1-8

designated ECIP for the years 2002 to 2006 to reflect the planning periodnow covered by the current document. Subsequent yearly documents will betitled in sequence from the present designation (i.e.: ECIP 2003-2007, ECIP2004-2008, etc).

ECIP � YEARS 2002 TO 2006 - LEVEL 2 FROM STRATEGY TO PERFORMANCE DELIVERY

2-1

2. FROM STRATEGY TO PERFORMANCE DELIVERY

2.1 Improving ATM performance

The primary goal of the ATM community is to ensure that the Air NavigationServices (ANS) it provides can meet its customers' requirements.

To achieve this goal Performance Targets, and the means to achieve thosetargets, are set and adopted on a yearly basis for the following key ATMperformance areas:

� Safety

� Capacity

� Cost-effectiveness

� Environment

This is done within a top-down, performance-driven and iterative processwhich uses as its foundations the high-level strategic objectives and roadmapof change set out in the EUROCONTROL ATM 2000+ Strategy.

2.2 Identifying Performance RequirementsThe Strategic Performance Framework (SPF) is a rolling yearly planningprocess with a look-ahead time of approximately 20 years7. It defines thefuture performance requirements for the European ATM system based on therelevant top-level strategic objectives derived from the EUROCONTROL ATM2000+ Strategy which can be quantified, the forecast traffic demand, and thestrategic Performance Targets set by the Safety Regulation Commission andPerformance Review Commission and approved by the EUROCONTROLProvisional Council. The strategic objectives are:

SAFETY To improve safety levels by ensuring that the number ofATM induced accidents and serious or risk bearingincidents is reduced in real terms.

CAPACITY To provide sufficient capacity to accommodate the demandin typical busy hour periods without imposing significantoperational, economic or environmental penalties undernormal circumstances.To enable airports to make the best use of potentialcapacity, as determined by the infrastructure in place(landside and airside), political and environmentalrestrictions, and the economic handling of the trafficdemand.

COST-EFFECTIVENESS

To reduce the total Air Navigation Service costs per unit ofaircraft operations.

ENVIRONMENT To work with ICAO and its member States to obtainimprovements in ATM, in particular the acceleratedimplementation of ATM/CNS concepts that help to mitigatethe impact of aviation on the environment.

7 The time horizon for implementation planning has to extend beyond that considered for performance planning (initially 5years); in particular, a firm commitment must be made early for programmes with a lead time of 7 years or more (e.g. whenairborne implementation is involved and all aircraft need to be equipped).


2-2

Performance Targets will be consistent with the policies set by theEUROCONTROL Provisional Council, and balanced across the ATM keyperformance areas (including safety, capacity, costs, and environment).

The SPF links the system requirements to the contributions expected from theOperational Improvements for the period up to 2020, to help identify and drivethe initiation of Research and Development (R&D) for ImplementationObjectives and programmes.

It also identifies any shortfalls between the future system requirements andthe proposed set of operational improvements, as well as the need to prioritiseor accelerate specific improvements to meet future system needs.

2.3 Identifying the ATM changes needed to meet the PerformanceRequirements

The EUROCONTROL ATM 2000+ Strategy sets out the general orientationfor change in ATM based on stepped operational improvements in the coreATM and supporting processes. These provide a starting point for improvingATM performance but they require expansion and validation to determine thelevel of benefits they offer and under what circumstances and conditions theycan best be applied.

The high-level operational changes set out in the EUROCONTROL ATM2000+ Strategy, together with those emanating from the Domain sub-strategies, are validated and their potential benefits quantified through R&Dand simulation work. This is done as part of an iterative Strategy Review andUpdate process.

The aim of these activities is to elaborate the EUROCONTROL ATM 2000 +Strategy, and provide a series of clear and cohesive change steps thatensure a balanced evolution of a uniform European ATM that will meet theagreed performance requirements. They provide the link between theEUROCONTROL ATM 2000+ Strategy and the Domain8 activities and sub-strategies, and through them the work of the EATMP Domain Teams.

The results of the Strategic Review and Update work are used to select thoseimprovements that are likely to offer the best solutions for meeting thePerformance Targets, and to produce a manageable and cohesive set - a'Roadmap' - of Operational Improvements over time.

Planning follows an iterative process to refine Performance Targets (seeChapter 3) and future plans based on the actual performance results achievedover time, and supports the prioritisation of programmes within the EATMPportfolio. This allows the acceleration of those programmes and measures thatwill bring early benefits in the ATM key performance areas.

The top-down approach helps to define a consolidated set of OperationalImprovements that will progressively improve the European ATM network overtime in line with the forecast performance.

8 Domain is an organisational term used to describe a functional sub-division of the ATM system that undertakes preparatorywork for programmes and services. The sum of all Domains equals ATM. Each Domain develops a sub-strategy (eg: AirspaceStrategy, Communications Strategy, Airport Operations Strategy, etc.) based on relevant Operational Improvements stemmingfrom the Strategic Performance Framework.


2-3

2.4 Defining the Implementation Objectives and identifyingProgrammesOnce an Operational Improvement is sufficiently developed, ECIPImplementation Objective(s) are derived and the supporting programme(s)needed to realise the objective(s) are identified and included in the EATMPportfolio9.

An Implementation Objective may be supported by more than oneprogramme depending on the scope of the improvement to be applied. Otherobjectives may not require a specific EATMP programme to be generated,and can be achieved through local implementation actions (e.g: applying acommon Safety policy).

These supporting programmes provide the practical means of applying theOperational Improvements to the national ATM systems so as to realise theImplementation Objective and improve the performance of the ATM networkas a whole. It is the implementation of these programmes at national levelthat delivers the performance benefits to the ATM network.

2.5 Types of Objectives

ECIP Implementation Objectives fall within one of three types depending onthe strategic aim to be met and the nature of the objective:

� Pan-European � objective to be applied in all ECAC States (eg: ReducedVertical Separation Minimum - RVSM) within a common time scale (ie: thesame date or a commonly agreed and co-ordinated deployment by acommon target date);

� Multi-national � objective to be applied in some ECAC States (eg: FreeRoutes Airspace - FRAP) within a common time scale (i.e.: the same dateor a commonly agreed and co-ordinated deployment by a common targetdate);

� Harmonisation10 � objective to be applied at individual State or ATCunit level as appropriate to achieve their performance targets (eg: ArrivalManagement Tools). The ECIP will define the date from whichimplementation of the objective will deliver initial benefits. In someinstances, it may also be possible to define a date by which fulldeployment on a voluntary basis might be possible. The decision whetheror not to adopt a harmonisation will depend on local circumstances andwill be made by the relevant State authorities.

2.6 Status of Implementation Objectives

The status of an ECIP Implementation Objective varies over time in relationto the lifecycle of the programme that supports it. An overview of thisrelationship is given in the diagram below.

9 An Operational Improvement may generate more than one objective and programme depending on its scope.10 The possibility of adopting a regional (multi-national) approach to the implementation of a Harmonisation objectives adoptedby 2 or more adjacent States is under investigation.


2-4

When an Implementation Objective is supported by an EATMP programmes,its status corresponds to the planning of the programme work and its results,while the decision points denote the transition from one programme phase11 tothe next. The status of the objective will change accordingly at theappropriate points in the programme lifecycle.

Agreement Feasibility Development Approval �Go��No Go� Acceptance Start

OperationsLocalImplement-

ation.

Implemen-tation

PlanningPre-

OperationalDevelopmentFeasibilityPlanningInitiation

Go / No goDecision

CIPObjectiveStatus

Life-cyclePhases

AchievedConfirmedAgreedProposedTentative

Programme lifecycle and objective status

The types of ECIP implementation Objectives status are:

� Tentative � the feasibility of the operational improvement and associatedprogramme is still being studied, and the objective is included in the ECIPto provide advanced warning of the likely scope and associated actions.The timings given for the activities involved may also change dependingon the outcome of the detailed feasibility work;

� Proposed � the feasibility of the objective has been confirmed butdevelopment work is still required. Nevertheless the objective can be usedfor advanced planning work at national level. The timings given for theactivities involved may also change depending on the outcome of thedetailed development work;

� Agreed � development work has been completed, the programme(s)associated with the objective has been approved, and implementationplanning is now being progressed;

� Confirmed � planning is now being translated into implementation actionswithin the associated programme(s), such as procurement anddeployment and implementation is being progressed at national level;

� Achieved � the objective has been successfully realised and theassociated programme(s) completed.

The types of decisions associated with the programme lifecycle, and by whenand at what management level they are taken are set out in the EATMPManagement Handbook. Agreement for moving from one programme cycle tothe next involves a number of different and inter-related processes, such asthe development of cost-benefit and business cases, consultation andcanvassing of continued stakeholder support, approval of plans, costs,resource effort, etc. Changes to the status of the objective are a naturalconsequence of completion of the appropriate programme cycle together with

11 The lifecycle of an EATMP programme covering all of the phases from its initial development to eventual realisation isexplained in detail in the EATMP Management Handbook; Edition 2.0 dated December 1999.


2-5

the appropriate level of agreement to progress to the next. These decisionswill be taken by the relevant bodies as part of the EATMP workingarrangements (eg: Domain Teams/PSGs, etc, and will be notified to thebodies such as the ACG, etc, if appropriate through the normal course ofprogramme activities and reporting.

2.7 Local planning and implementationImplementation Objectives are broken down into generic SLoA in the ECIPLevel 2 document. These SLoA detail the individual activities that are neededto satisfy the relevant ECIP Implementation Objective by each of the mainaviation stakeholder groups and by when they need to be started and, or,completed. This information then cascades down into the States' LCIPdocuments - one for each State.

The LCIP documents reflect the national plans and implementation actionsneeded to realise the objectives, and signify the intent of each involvedstakeholder to apply their best endeavours to progress their part in thoseplans to meet the Performance Targets.

Improvements to ATM and the realisation of the benefits brought about by theoperational change stem from the combined effects of the localimplementation of:

� Pan-European and multi-national objectives in the framework of thecorresponding EATMP programmes;

� Harmonisation objectives within the framework of national plans andprojects which use or make reference to the deliverables of thecorresponding EATMP Programmes (e.g. Guidelines, Standards, etc);

� Other National Plans � the various programmes and projects, as well asnational contributions to pan-European and multi-National programmes,are reflected in the LCIP for each participating State.

2.8 The LCIP DocumentsThe Performance Targets, Implementation Objectives and SLoA are floweddown into the LCIP documents12, which constitute the medium-term plan forthe national stakeholders13 for realising the Performance Targets.

The LCIP document is also split into two levels.

� Level 1 constitutes the national summary plan and addresses the high-level Implementation Objectives defined in the ECIP document that arepart of the State�s intended implementation activities. The scope of thisplan includes all elements of the Air Navigation System and the variousstakeholders who have a role to play in the execution of the plan. Itsummarises the national plans to meet the Performance Targets using therelevant Implementation Objectives. Also, it outlines the Multinationalprojects that are necessary to implement the Pan-European, Multinationaland Harmonisation programmes at national level, and identifies theexpected performance benefits.

12 The EUROCONTROL Agency�s actions in terms of SLoA are contained in the relevant Programme documentation, and not ina separate LCIP document.13 The national stakeholders include the organisations whose activities are centred on the particular State for provision ofservices or regulation.


2-6

� Level 2 identifies the specific contributions of the national stakeholderswithin the State that are needed to achieve the performance andimplementation objectives assigned to them.

LCIP documents will be updated yearly on the basis of progress achieved andactual traffic evolution. This updating process is initiated and monitored by theEUROCONTROL Agency following the publication of the latest ECIPdocuments. The appropriate State authorities then approve the changesneeded to the LCIP.

The EUROCOTROL Agency has nominated one CIP Contact Person for eachEATMP participating State. The development of the national LCIP is effectedthrough the combined efforts of the Agency CIP Contact Person and thenational Focal Point, who is responsible for co-ordinating national stakeholderinputs.

2.9 Monitoring progress and status reporting

The EUROCONTROL Agency, in co-ordination with the ATM/CNS FocalPoints of the States, produces a Status Report each year. The Status Reportincludes data on actual performance improvements, and information about theprogress of work in implementing the Implementation Objectives and theirlines of actions, or alternative solutions.

The yearly Status Report is used to identify any deviation from agreed plans,and to discuss and decide possible remedial actions. It thus plays a centraland important role in meeting the Agency's monitoring responsibilities.

2.10 Planning overviewAn overview of the steps in the planning, together with the appropriate leaddocuments involved, is given below.

Performance Planning

ATM 2000+ STRATEGY

SPF

SPF & ROADMAP

ECIP LEVELS 1 & 2

LCIPs

STRATEGIC OBJECTIVES

PERFORMANCEREQUIREMENTS

OPERATIONALIMPROVEMENTS SETS

IMPLEMENTATIONOBJECTIVES

PROGRAMMES

NATIONAL ACTIONS

NATIONAL PLANS

PERFORMANCEDELIVERY

REPORT

PROGRAMME DOCUMENTSEWPD

PROCESSES DOCUMENTS

ECIP STATUS

StrategicPlanning

European Planning

Local Planning and

Implementation

ECIP � YEARS 2002 TO 2006 - LEVEL 2 PERFORMANCE TARGETS

3-1

3. PERFORMANCE TARGETS

Work on developing ATM Performance Targets for the ATM key performanceareas is on-going. At present, only targets for capacity are available andincluded in the ECIP 2002-2006 document.

3.1 General

Short and medium term Performance Targets are set for individual ATCUnits and form the basis for implementation planning at local (national) level.Medium-term targets (years 2 to 5), once approved by the EUROCONTROLProvisional Council, are included in the European Convergence andImplementation Plan. The targets reflect decisions made by theEUROCONTROL Provisional Council based on policies or strategies thatoriginate from outside of ATM (e.g.: environment).

Short term ATM Performance Targets are derived from the medium-termtargets, with appropriate adjustment to take account of the actual operationalachievements during the last season, and form the basis for planning for thenext summer season.

3.2 How capacity targets are set

Capacity targets for the short and medium-term are derived on the basis of thehigh-level capacity objective of the EUROCONTROL ATM 2000+ Strategy�to provide sufficient capacity to accommodate the demand in typical busyhour periods without imposing significant operational, economic orenvironmental penalties under normal circumstances.�

The forecast of the air traffic demand to be accommodated is based on ananalysis of past capacity performance using empirical data from the CentralFlow Management Unit (CFMU), forecasts of air traffic demand from theEATMP Statistical Forecasting service and Expert Panel (STATFOR), and theresults of the simulation of traffic flows from the Future ATM Profile (FAP)model.

The criteria for deciding the level of penalties to be considered significantare set by the EUROCONTROL Provisional Council based on therecommendations of the Performance Review Commission - usuallyexpressed as a target level of delay - and the EUROCONTROL Agency, afterdiscussion and co-ordination with the organisations concerned (in particular inthe ATM/CNS Consultative Group).

The capacity targets are indicative of the capacity that needs to be providedeach year to accommodate the forecast demand, and take into account anylocal traffic variations and constraints. They are the basis on whichperformance planning must be established.

The actual setting of capacity targets at the level of individual ATC units is anextensive process that starts with the analysis of the current traffic situationand forecast evolution, and ends with an evaluation consultation and approvalprocess.


3-2

An overview of this process is shown below:

Capacity planning process

In summary, the capacity target setting process is as follows14:

The baseline capacity represents the effective capacity offered by the ACC ina typical peak period; it is determined from an analysis of ATFM delays andtraffic15 or, for ACCs not generating ATFM delays, from an analysis of sectordeclared capacities.

The future capacity target level, for each centre, is based on the forecastdemand, taking in account the complete gate-to-gate network, the ATS routenetwork evolution and utilisation and known airports capacity plans. The targetACC capacity values are determined by FAP based on the high-level policyapplicable, (i.e. the overall ATFM delay target).

The capacity targets given in the ECIP for each ACC must cover both:

• the forecast traffic increase ;

• the current capacity shortfall, i.e. the difference between the current(optimum) target capacity level and the actual capacity (baseline).

14 For more details see �ATC Capacity Targets � A User Guide� V0.5 dated 21.02.01.15 For that purpose FAP uses the CFMU Computer Aided Slot Allocation (CASA) model.

Currenttraffic analysis

Traffic forecast

ACC capacitytargets setting

Consultation +approval process

Capacity planning

Implementationoperations

Economic forecastUser demandAirport plans

Route network

Policy oncapacity

Traffic statisticsDelay statisticsACC capacityassessment

Overall growthACC demandforecast

Proposed ACCcapacity targets

Agreed ACCcapacity targets(ECIP)

Capacity plansImpact


3-3

3.3 Capacity Targets in the ECIP 2002-2006

The ATM Performance Targets included in the ECIP for the 2002-2006period were derived as described above, based on the following criteriaagreed by the EUROCONTROL Provisional Council 16, on the understandingthat the associated capacity targets were to be used as the basis for �co-operative planning and provision of capacity�:

• Medium traffic growth forecast, corresponding to the STATFORbaseline scenario (overall average growth rate: 4.6% p.a);

• Optimum flight profiles, i.e. shortest routes available on the ATS RouteNetwork (ARN) new version (V4) with unconstrained vertical profiles;

• Optimum17 delay target of one minute average ATFM en-route delay perflight.

The aim is to achieve this optimum by Summer 2006, by progressivelyreducing ATFM delays and accommodating optimum routes and flight profiles.

The list of the related capacity targets for air traffic control centres (ACCs) foreach State is attached at Table 1; this indicates:

• the 2000 capacity baseline corresponding to the traffic flow (flights/hour)which could enter the en-route ATC units area of responsibility withoutcausing ATFM delays during a typical peak period;

• the capacity levels (flights/hour) and cumulated percentage capacityincreases to be achieved each year from 2001 to 2006;

• the 2001 targets corresponding to the short-term ATFM (en-route) delaytarget of 2.8 min/flight previously agreed by PC/9;

• the 2006 targets corresponding to the 1 min (en-route) delay targetagreed by PC/11;

• the intermediate yearly capacity targets ensuring a smooth transition outto 2006.

The targets refer to flights operating to pre-notified flight plans in regulated airspaceand receiving the appropriate levels of Air Traffic Services. States will need also toaccommodate other flights that fall outside of those parameters that require access toregulated airspace.

16 Provisional Council 10th Meeting 5 April 2001.17 The optimum corresponds to the balance between the cost of providing extra ATM capacity and the cost of remaining ATFMdelays. This gives an average of about 1 minute en-route ATFM delay per flight.


3-4

Table 1 - Capacity Targets for ACCs (2001-2006)(GAT IFR Movements/hour + % increase with respect to 2000 baseline)

Not assessed 0-20% 21-40% 40% +

2001 targets (EEC Note 15/00 refers) correspond to PC 9 decision to aim for an en-route delay of 2.8 min.2006 targets correspond to PC 11 decision to aim for an en-route delay of 1min.

State ACC Code Baseline Targets2000 2001 2002 2003 2004 2005 2006

Albania Tirana LAAA 22 22 0% 26 16% 29 33% 31 41% 33 50% 35 58%

Armenia Yerevan UGEE 16

Austria Vienna LOVV 130 130 0% 140 8% 150 16% 159 22% 167 29% 176 35%

Belgium Brussels EBBU 137 138 0% 138 0% 140 2% 143 4% 146 6% 150 9%

Sofia LBSR 82 82 0% 82 0% 82 0% 82 0% 82 0% 82 0%Bulgaria

Varna LBWR 53 53 0% 53 0% 53 0% 53 0% 53 0% 53 0%

Croatia Zagreb LDZO 58 60 2% 72 24% 84 44% 97 66% 109 87% 121 108%

Cyprus Nicosia LCCC 51 51 1% 52 3% 53 4% 54 8% 56 11% 58 14%

Czech Rep Prague LKAA 70 77 10% 84 20% 91 30% 98 35% 105 50% 112 60%

Denmark Copenhagen EKDK 128 128 0% 128 0% 128 0% 128 0% 128 0% 128 0%

Estonia Tallin EETT 30

Eurocontrol Maastricht EDYY 226 246 9% 266 18% 286 26% 306 35% 326 44% 346 53%

Rovaniemi EFPS 25 25 0% 25 0% 25 0% 25 0% 25 0% 25 0%Finland

Tampere EFES 71 71 0% 71 0% 71 0% 71 0% 71 0% 71 0%

Aix/Marseille LFMM 180 194 7% 203 13% 213 18% 223 23% 233 29% 243 35%

Bordeaux LFBB 147 151 3% 156 6% 161 10% 167 14% 174 19% 180 23%

Brest LFRR 144 150 4% 174 21% 184 28% 197 37% 207 44% 212 47%

Paris LFFF 221 232 5% 235 6% 238 7% 242 9% 247 12% 252 14%

France

Reims LFEE 130 140 7% 153 17% 165 27% 178 37% 190 46% 203 55%

FYROM Skopje LWSS 28 29 5% 37 34% 45 62% 49 75% 52 87% 56 100%

Berlin EDBB 110 110 0% 118 7% 126 14% 134 22% 142 29% 150 37%

Dusseldorf EDLL 118 118 0% 118 0% 121 2% 125 6% 128 9% 132 12%

Frankfurt EDFF 165 168 2% 174 6% 180 9% 186 13% 192 17% 199 21%

Bremen EDWW 138 139 1% 139 1% 139 1% 139 1% 139 1% 139 1%

Karlsruhe EDUU 173 186 7% 206 19% 227 31% 247 42% 256 48% 265 53%

Germany

Munchen EDMM 190 196 3% 205 8% 214 13% 224 18% 234 23% 243 28%

Athens LGGG 87 92 5% 94 8% 96 10% 104 19% 111 28% 119 36%Greece

Macedonia LGMD 50 52 4% 60 19% 67 35% 74 49% 81 63% 88 77%

Hungary Budapest LHCC 97 99 3% 103 7% 106 10% 109 13% 112 16% 115 19%

Dublin EIDW 44 44 1% 47 6% 49 12% 52 17% 54 22% 56 28%Ireland

Shannon EISN 90 90 0% 90 0% 98 9% 102 13% 106 18% 110 22%

Brindisi LIBB 58 60 4% 60 4% 61 5% 63 8% 65 11% 67 15%

Milan LIMM 127 134 6% 140 11% 147 15% 153 21% 160 26% 166 31%

Padua LIPP 98 109 11% 125 27% 138 40% 147 49% 156 58% 165 67%

Italy

Roma LIRR 182 187 3% 204 12% 221 22% 232 28% 242 34% 253 39%


3-5

State ACC Code Baseline Targets2000 2001 2002 2003 2004 2005 2006

Latvia Riga EVRR 49 49 0% 49 0% 49 0% 49 0% 49 0% 49 0%

Lithuania Vilnius EYVC 39 39 0% 39 0% 39 0% 39 0% 39 0% 39 0%

Malta Malta LMMM 31 31 0% 31 0% 31 0% 31 0% 31 0% 31 0%

Moldova Kishinau LUKK 16

Netherlands Amsterdam EHAA 124 126 2% 129 4% 132 7% 135 9% 139 12% 142 15%

Bodo ENBD 44 44 0% 44 0% 44 0% 44 0% 44 0% 44 0%

Oslo ENOS 80 80 1% 80 1% 80 1% 80 1% 80 1% 80 1%

Stavanger ENSV 39 39 0% 39 1% 40 2% 40 2% 40 3% 40 3%

Norway

Trondheim ENTR 34 34 0% 34 0% 34 1% 34 1% 34 1% 34 1%

Poland Warsaw EPWW 58 59 2% 66 14% 73 27% 78 35% 83 43% 87 51%

Portugal Lisbon LPPC 67 68 3% 74 11% 79 18% 83 24% 87 30% 91 36%

Arad LRAR 99 99 0% 99 0% 99 0% 99 0% 99 0% 99 0%

Bucaresti LRBB 138 138 0% 138 0% 138 0% 138 0% 138 0% 138 0%

Bacau LRBC 54 54 0% 54 0% 54 0% 54 0% 54 0% 54 0%

Cluj LRCL 51 51 0% 51 0% 51 1% 51 1% 51 1% 51 1%

Romania

Constanta LRCK 57 57 0% 57 0% 57 1% 57 1% 57 1% 57 1%

Slovakia* Bratislava LZBB 56 56 0% 57 1% 57 1% 58 4% 60 7% 62 10%

Slovenia Ljubljana LJLA 55 55 0% 61 11% 68 24% 75 37% 82 50% 88 61%

Barcelona LECB 123 130 5% 137 11% 144 17% 152 23% 160 30% 167 36%

Canarias GCCC 54 55 0% 57 4% 59 8% 62 13% 64 18% 67 23%

Madrid LECM 135 149 10% 161 20% 173 29% 181 34% 189 40% 197 46%

Palma LECP 61 62 2% 67 10% 72 18% 76 25% 80 31% 84 38%

Spain

Sevilla LECS 63 66 6% 70 12% 75 19% 78 25% 82 30% 85 36%

Malmo ESMM 150 150 0% 150 0% 150 0% 150 0% 150 0% 150 0%

Stockholm ESOS 121 121 0% 121 0% 121 0% 121 0% 121 0% 121 0%

Sweden

Sundsvall ESUN 41 41 0% 41 0% 41 0% 41 0% 41 0% 41 0%

Geneva LSAG 109 121 10% 135 23% 148 36% 156 43% 164 50% 172 57%Switzerland

Zurich LSAZ 146 159 10% 170 17% 180 24% 188 29% 196 35% 204 40%

Ankara LTAA 64 64 0% 64 1% 65 1% 68 6% 71 11% 75 17%Turkey

Istanbulc LTBB 80 80 0% 80 0% 84 5% 88 11% 93 16% 97 21%

London EGTT 323 351 9% 372 15% 400 24% 424 31% 440 36% 456 41%

Manchester EGCC 107 107 0% 109 3% 112 5% 117 10% 123 15% 128 21%

UnitedKingdom

Scottish EGPX 119 121 2% 124 4% 127 7% 132 11% 137 15% 142 19%

*Capacity figures for Slovakia are under discussion and not yet finalised.


3-6

Page left intentionally Blank

ECIP � YEARS 2002 TO 2006 - LEVEL 2 OBJECTIVES AND STAKEHOLDER LINES OF ACTION

4-1

4. OBJECTIVES AND STAKEHOLDER LINES OF ACTION

4.1 Implementation Objectives and SLoAThis chapter describes the ECIP Implementation Objectives and their SLoA thatcomprise the ECIP.

An Implementation Objective defines the implementation activity needed to realise anOperational Improvement and apply it to the European ATM network.

SLoA represent the actions and activities that have to be completed by the variousstakeholders within the given time scales, either as individual stakeholders, or incollaboration and co-operation with other stakeholder groups, to achieve theImplementation Objectives and realise the Performance Targets.

Each Implementation Objective and SLoA is set out in an agreed template in thefollowing pages.

In the ECIP Level 2, the Implementation Objectives are listed in the alphabeticorder of their designators to ease the search for specific objective descriptions. Eachobjective description is followed by a summary of its associated Stakeholder Linesof Action shown directly beneath the objective template on the same page. TheStakeholder Lines of Action are then expanded in the pages directly following theobjective to provide greater detail.

4.2 Key to the Implementation Objective template18

The Implementation objective template contains the following fields and information:ECIP designator: ABCXY

� where ABC is the acronym of one of the ATM Domains/areas of work shown inthe table below.

� and XY is the serial number for the Implementation Objective in the domain/areaof work it covers.

AOM = Airspace Organisationand Management

HUM = Human Resources

AOP = Airport Operations INF = Information ManagementATC = Air Traffic Control MIS = MiscellaneousCOM = Communications NAV = NavigationDPS = Data Processing Systems SAF = Safety ManagementFAC = Facilities SRC = Safety RegulationFCM = Flow and Capacity

ManagementSUR = Surveillance

Title:The objective title is a short text reference to the implementation goal.Status:The status gives the degree of decision passed for the objective. It will vary over timein relation to the to programme lifecycle. (see also Chapter 2; paragraph 2.6)

18 Note that not all fields in the template may be completed for objectives classed as Tentative or Proposed because feasibilityand development activities have yet to be completed.


4-2

Tentative = the feasibility of the operational improvement and associated programme isstill being studied, and the objective is included in the ECIP to provideadvanced warning of the likely scope and associated actions. The timingsgiven for the activities involved may also change depending on the outcomeof the detailed feasibility work

Proposed = the feasibility of the objective has been confirmed but development work isstill required. Nevertheless the objective can be used for advance planningwork at national level. The timings given for the activities involved may alsochange depending on the outcome of the detailed development work

Agreed = development work has been completed, the programme(s) associated withthe objective has been approved, and implementation planning is now beingprogressed

Confirmed = planning is now being translated into implementation actions within theassociated programme(s), such as procurement and deployment andimplementation is being progressed at national level

Achieved = the objective has been successfully realised and the associatedprogramme(s) completed.

Definition:Provides a short textual description of the objective.

Scope:The scope of the objectives varies according to the strategic aim being met and thenature of the objectives:

PE = Pan European - to be applied in all ECAC States (e.g.: Reduced VerticalSeparation Minimum - RVSM) within a common time scale (i.e.: the samedate or a commonly agreed and co-ordinated deployment by a commontarget date)

MN = Multi-National - to be applied in some ECAC States (e.g. Free RoutesAirspace programme - FRAP) within a common time scale (i.e.: the samedate or a commonly agreed and co-ordinated deployment by a commontarget date)

H = Harmonisation - to be applied at individual State or ATC unit level asappropriate to achieve their performance targets (e.g.: Arrival ManagementTools). The ECIP will define the date from which the implementation willdeliver initial benefits. In some instances, it may also be possible to definea date by which full deployment on a voluntary basis may be possible

Applicability area:

The organisation or geographical area to which the Objective is applicable.

Time scale:

This entry includes two fields 'From' and 'By'. Depending on the objective scope andstatus, none, one, or both of the fields may be populated.

The field 'From' stipulates the start date of the activities to realise the objective.

The field 'By' stipulates the date by which the objective should be achieved (for Pan-European and Multi-National objectives). In those instances where all participatingstakeholders have achieved all SLoAs they have adopted, the whole objective isnoted as "ACHIEVED", and its description removed from the ECIP Level 2.Approval reference:

Defines the level of approval of the objective and the date at which approval was


4-3

obtained. In most instances approval will be at the level of the EUROCONTROLProvisional Council.

Traceability information:Provides cross-referencing for the ECIP database and traceability of the objective tothe Strategic Performance Framework and EUROCONTROL ATM 2000+ Strategytop-level objectives and principles.

SupportingProgramme

= The front-end EATMP Programme that supports the objective.Other EATMP Programmes may contribute to the objectiveachievement, but are mentioned only if considered useful, and atSLoA level

Strategic fit = The associated strategic objective or principles defined within theEUROCONTROL ATM 2000+ Strategy or other strategic source

OperationalImprovement

= The Operational Improvement to which the objective is contributingas defined within the Strategic Performance Framework managedby the Strategy, Concept and Systems (SCS) Unit

Performance benefits:

Generic description of the benefits expected from the achievement of the objective inthe ATM key performance areas:

Safety = Benefits that improve safety levels by ensuring that the number ofATM induced accidents and serious or risk bearing incidents isreduced in real terms

Capacity = Benefits that provide sufficient capacity to accommodate thedemand in typical busy hour periods without imposing significantoperational, economic or environmental penalties under normalcircumstancesBenefits that enable airports to make the best use of potentialcapacity, as determined by the infrastructure in place (landside andairside), political and environmental restrictions, and the economichandling of the traffic demand

CostEffectiveness

= Benefits that reduce the total Air Navigation Service costs per unitof aircraft operations

Environment = Benefits that help to mitigate the impact of aviation on theenvironment

Objective as enabler for:

Other objectives or activities that the objective supports or is a pre-requisite.

Main resource requirements:

The main stakeholder resources (systems, people, etc) which are impacted by theobjectives. Requirements for Agency resources are not stipulated here, and aredescribed in the supporting Programme documentation.

4.3 Key to the SLoA template

The SLoA template contains the following fields and information

Stakeholder Line of Action (SLoA) designator: ABCXY - ZZZ00 where:

� ABCXY is the designator of the Implementation Objective associated with theSLoA (see 4.2 above)


4-4

� ZZZ is the acronym of the stakeholder category (see below)

� and 00 is the serial number of the SLoA within the stakeholder category it covers.

AGY = EUROCONTROL AgencyAPO = Airport OperatorsASP = Air Navigation Service Providers (ANSP)19

MIL = Military AuthoritiesREG = Regulatory Authorities20

SUP = Support IndustryUSE = Airspace Users

For consistency reasons the SLoAs are listed in the following order in allImplementation Objectives descriptions: USE, MIL, ASP, APO, REG, AGY, SUP.

The symbol � alongside the SLoA description on the Objective front description pageindicates that the SLoA is applicable both to civil and military (or joint civil/military)units. A MIL SLoA is raised only when the action needed by the military is not coveredby the generic SLoA

Title:

The text title of the SLoA.

Action by:

The stakeholders who have to progress the actions described in the SLoA. Thecategories used in this field are derived from the EATMP Stakeholder SegmentationModel, except that Military Authorities are shown a separate stakeholder category.

Airspace Users = All types of airspace users (but see Military Authorities)MilitaryAuthorities

= Defence/security organisations that, depending on nationalconsiderations of each State, can encompass Airport Operators, AirNavigation Service Providers, Airspace Users andRegulatory/Certification Authorities

Air NavigationService Providers

= The various providers of air navigation services with the exception ofthe airside airport aspects21

Airport Operators = Authorities involved in airport operations, including the airsidenavigation services

RegulatoryAuthorities

= Stakeholders in charge of rule making and regulation, certification ofequipment and procedures, establishment of legal responsibilities, etc.It includes typically the regulatory role of States through their officialservices, as well as the JAA activities. This category also includesinternational organisations such as ICAO, ITU, etc

EUROCONTROLAgency

= Executive body of the EUROCONTROL Organisation. Is mentioned asstakeholder where the realisation of a central function or facility is asignificant element of the objectiveFor operational services provided by the EUROCONTROL Agency,the Agency Regulation Unit (ASR) acts as the regulatory authority

EATMP = The appropriate Unit(s), Programme(s) and Domain(s) that are part ofthe Agency's EATMP organisation

CFMU = The Central Flow Management UnitSupport Industry = Manufacturing industry: airframes, avionics, CNS equipment, ATC

equipment, software, etc

19 The term ATM Service Providers is used instead of Air Navigation Service Providers in all objectives with the designationSAF, and for SRC to reflect the terminology contained within the relevant ESARR document.20 The designation REG in SRC objectives is also used to denote bodies such as Aircraft Accident Investigators, etc.21 See also footnote 21.


4-5

Definition:

Provides a short textual description of the SLoA activity.

Timescale:

This entry includes two fields 'From' and 'By'. Depending on the objective scope andmaturity, none, one or both fields may be populated.

The field 'From' stipulates the implementation start date if needed.

The field 'By' stipulates the date by which the SLoA should be achieved if needed toensure the timely objective achievement (for Pan-European and Multi-Nationalobjectives), or to ensure delivery of initial benefits (for Harmonisation objectives). In thelatter case, the completion date may also be stipulated.

In those instances where enough stakeholders have completed the SLoA to ensure theobjective achievement, the SLoA is noted "ACHIEVED" in the front-page objectivedescription, and the detailed description of the SLoA is removed from the ECIP Level 2.

Applicability:The organisation and, or, geographical area to which the SLoA is applicable.

Particular criteria to assess the achievement of the SLoAEvidence that the SLoA is achieved, specified in such a way that its progress can bemonitored and reported.


4-6


ECIP � YEARS 2002 TO 2006 - LEVEL 2 AOM01

4-7

AOM01 Implement Reduced Vertical SeparationMinimum

Confirmed

Definition:Provide 6 additional Flight Levels by implementing 1000ft vertical separation minimumbetween Flight Levels 290 and 410.

Scope:Pan European

Applicable area:ECAC/EUR Region RVSM

Airspace, FL290-FL410

Timescale:From: By: 01/2002

Approval reference: Provisional Council - 07/2000

Supporting Programme:RVSM

Strategic fit:ATM 2000+, Vol.2 para.7.1.3 and 8.2; Airspace

Strategy, step 1D

OperationalImprovement:

Reduced VerticalSeparation (RVSM)

Performance benefitsSafety: Some improvement from restructuring of traffic flows

and reduction of conflict points

Capacity: Increase in upper airspace capacity; the additionalFlight Levels will allow better structuring of traffic flowsand reduction in conflict points and controller workload

Cost-effectiveness: Reduction in fuel consumption from more optimumtrajectories

Environment: Reduction in emissions

Enabler for: Implementation of airspace sector improvements

Main resource requirements: Equipment for aircraft; ATC ground systemenhancement; training for controllers

Stakeholder Lines of Action:

AOM01-USE01 Modify aircraft and train crews From: By: 12/2001 �AOM01-ASP01 Prepare and validate ground ATC systems From: By: 08/2001 �AOM01-ASP02 Agree procedures between adjacent States From: By: 09/2001 �AOM01-ASP03 Train ATC staff From: By: 11/2001 �AOM01-REG01 Regulatory measures for RVSM operations From: By: 10/2001 �AOM01-REG02 Safety assurance for RVSM ACHIEVEDAOM01-REG03 Certify equipment and verify airborne

equipment performanceFrom: By: 09/2001 �

AOM01-REG04 Approval of material for aircraft modificationand ATC procedures

ACHIEVED

AOM01-AGY01 Amend IFPS for RVSM ACHIEVEDAOM01-AGY02 Implement height monitoring structure ACHIEVEDAOM01-AGY03 Safety analysis for RVSM From: By: 07/2001AOM01-SUP01 Provide altimetry systems ACHIEVED


4-8

AOM01 - Detailed Stakeholder Lines of Action Description

AOM01-USE01 Modify aircraft and train crews

Definition: All aircraft intending to operate in EUR RVSM airspace, except State aircraft,shall obtain an RVSM approval issued by the appropriate authority of the State in whichthe operator is based or registered.Applicability: All aircraft flying at FL290 and above with the exception of exempted Stateaircraft.Particular criteria to assess the achievement of the Line of Action: All aircraft intending tofly in RVSM airspace have obtained approval or, in the case of State aircraft, theappropriate exemption.

Action by:Airspace UsersFrom: By: 12/2001

AOM01-ASP01 Prepare and validate ground ATC systems

Definition: Prepare ground ATC systems to use RVSM, validate and approve systemmodifications and associated procedures.Applicability: ECAC/EUR Region RVSM airspaceParticular criteria to assess the achievement of the Line of Action: Availability of RVSMadapted systems and procedures.

Action by:ANS ProvidersFrom: By: 08/2001

AOM01-ASP02 Agree procedures between adjacent States

Definition: Define and implement procedures for the use of RVSM through Letters ofAgreement and other bilateral/regional agreements.Applicability: ECAC/EUR Region RVSM airspaceParticular criteria to assess the achievement of the Line of Action: Approved Letters ofAgreement or other medium.


AOM01-ASP03 Train ATC staff

Definition: Train controllers and support staff in preparation for the implementation ofRVSM.Applicability: ECAC/EUR Region RVSM airspaceParticular criteria to assess the achievement of the Line of Action: All relevant staff trainedin RVSM procedures and operations.


AOM01-REG01 Regulatory measures for RVSM operations

Definition: Amend AIP and National regulations/legislation to conform with the operationalprocedures and technical requirements for the implementation of RVSM.Applicability: ECAC/EUR Region RVSM airspaceParticular criteria to assess the achievement of the Line of Action: Completion ofamendments to AIP and National regulations/legislation

Action by:National RegulatoryAuthorityFrom: By: 10/2001

AOM01-REG03 Certify equipment and verify airborne equipment performance

Definition: Conduct certification and verification of airborne equipment and performance inaccordance with agreed standards and procedures.Applicability: GlobalParticular criteria to assess the achievement of the Line of Action: Equipment of all aircraftintending to fly in RVSM airspace has been certified and validated or, in the case of Stateaircraft, the appropriate exemption obtained.

Action by:National RegulatoryAuthorityFrom: By: 09/2001

AOM01-AGY03 Safety analysis for RVSM

Definition: Conduct overall safety assessment and hazard analysis for RVSM airspacebefore implementation.

Applicability: ECAC/EUR Region RVSM airspaceParticular criteria to assess the achievement of the Line of Action: Completion of safetyassessment and hazard analysis.

Action by:EATMPFrom: By: 07/2001


4-9

AOM02 Implement Free Routes airspace in eightstates airspace

Tentative

Definition:Implement procedures and system changes to allow airspace users to freely plan andfly their preferred routes, between an entry point and an exit point without reference tothe pre-defined ATS route network, in the Upper airspace of the 8 participating States.Initial implementation to start in 2003 in one or more States and progressively extended.

Scope:Multi-National

Applicable area:BE, DE, DK, LU, NL, NO,

SE, FI (incl. Maastricht UAC)

Timescale:From: 04/2003By:

Approval reference: Provisional Council - 07/2000 Phase 1 Feasibility

Supporting Programme:FRAP

Strategic fit:ATM 2000+ Vol.2, para.7.1.4 and 8.2; Airspace

Strategy, step 2C


Free Routes in UpperAirspace

Performance benefitsSafety: Safety levels maintained or improved if traffic de-

confliction is supported by advanced ATC tools

Capacity: Increase through reduction in conflict points

Cost-effectiveness: Fuel cost reduction through optimised trajectories

Environment: Emissions reduced through shorter flight times and useof more optimum Flight Levels

Enabler for: Pilot for development of Free Routes airspace in all ECAC States

Main resource requirements: System enhancements; training for ATC and airspaceuser staff


AOM02-USE01 Adapt flight planning procedures and traincrews

From: 01/2003 By: �

AOM02-ASP01 Implement airspace changes From: 01/2003 By: �AOM02-ASP02 Safety assurance for Free Routes operations From: 01/2003 By: �AOM02-ASP03 Prepare ground systems From: 01/2003 By: �AOM02-ASP04 Implement Operational Procedures From: 01/2003 By: �AOM02-ASP05 Train ATC Staff From: 01/2003 By: �AOM02-ASP06 Conclude agreements From: 01/2003 By: �AOM02-REG01 Approve regulatory material From: By: 03/2003 �AOM02-REG02 Amend ICAO EUR Plan and other ICAO

documentsFrom: By: 04/2003

AOM02-AGY01 Define common procedures for Free Routesairspace operations

From: By: 01/2003

AOM02-AGY02 Adapt IFPS for Free Routes operations From: By: 12/2002AOM02-AGY03 Overall safety assessment for Free Routes

operationsFrom: By: 12/2002

AOM02-AGY04 Adapt ATFM to Free Routes operations From: By: 12/2002AOM02-AGY05 Implement monitoring structure From: By: 04/2003AOM02-SUP01 Provide data processing systems and support

toolsFrom: By: 04/2003


4-10


AOM02-USE01 Adapt flight planning procedures and train crewsDefinition: Adapt flight planning procedures for use of Free Routes and train crews in theiruse.Applicability: All airspace users flying in Free Route airspaceParticular criteria to assess the achievement of the Line of Action:1. Completion of changes.2. Percentage of trained crew.

Action by:Airspace UsersFrom: 01/2003By:

AOM02-ASP01 Implement airspace changesDefinition: Implement changes to airspace organisation to accommodate Free Routes andamend AIPs in accordance with the AIRAC cycleApplicability: Participating StatesParticular criteria to assess the achievement of the Line of Action: Publication of airspacechanges.

Action by:ANS ProvidersFrom: 01/2003By:

AOM02-ASP02 Safety assurance for Free Routes operationsDefinition: Conduct national safety assessment for Free Routes operations in compliancewith national requirements.Applicability: Participating statesParticular criteria to assess the achievement of the Line of Action: Approval of safety case.


AOM02-ASP03 Prepare ground systemsDefinition: Prepare ground ATC systems, validate and implement system modifications andassociated procedures.Applicability: Participating StatesParticular criteria to assess the achievement of the Line of Action: System modificationscompleted.


AOM02-ASP04 Implement Operational ProceduresDefinition: Define, validate and implement operatonal procedures for Free Routesoperations.Applicability: Participating StatesParticular criteria to assess the achievement of the Line of Action: Publication ofprocedures.


AOM02-ASP05 Train ATC StaffDefinition: Train ATC staff in Free Routes procedures.Applicability: Participating statesParticular criteria to assess the achievement of the Line of Action: All staff trained in newprocedures.


AOM02-ASP06 Conclude agreementsDefinition: Conclude Letters of Agreement and other regional agreements as needed toimplement Free Routes airspace and operationsApplicability: Participating StatesParticular criteria to assess the achievement of the Line of Action: Letters of Agreementand other regional agreements required in place



4-11

AOM02-REG01 Approve regulatory materialDefinition: Enact regulatory material for implementation of Free Routes.Applicability: Participating statesParticular criteria to assess the achievement of the Line of Action: National publicationsupdated

Action by:National RegulatoryAuthoritiesFrom: By: 03/2003

AOM02-REG02 Amend ICAO EUR Plan and other ICAO documentsDefinition: Amend ICAO EUR Plan and other ICAO documents.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: ICAO EUR Plan andICAO documents amended

Action by:ICAOFrom: By: 04/2003

AOM02-AGY01 Define common procedures for Free Routes airspace operationsDefinition: Define common procedures and prepare guidance for regulatory material forFree Routes airspace operations.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Approval of commonprocedures


AOM02-AGY02 Adapt IFPS for Free Routes operationsDefinition: Adapt the IFPS system and procedures to take account of Free Routes airspaceand operations in participating States.Applicability: Participating statesParticular criteria to assess the achievement of the Line of Action: IFPS changescompleted and procedures available

Action by:CFMUFrom: By: 12/2002

AOM02-AGY03 Overall safety assessment for Free Routes operationsDefinition: Conduct overall safety assessment for Free Routes operations.Applicability: Participating statesParticular criteria to assess the achievement of the Line of Action: Completion of safetyassessment.


AOM02-AGY04 Adapt ATFM to Free Routes operationsDefinition: Analyse the way that traffic demand and capacity can best be managed, anddefine procedures to accommodate Free Route airspace and operationsApplicability: Participating statesParticular criteria to assess the achievement of the Line of Action: Procedures defined andavailable


AOM02-AGY05 Implement monitoring structureDefinition: Establish management structure to monitor extension of Free Routes airspace.Applicability: Participating statesParticular criteria to assess the achievement of the Line of Action: Management structureestablished and functioning


AOM02-SUP01 Provide data processing systems and support toolsDefinition: Provide data processing systems capable of processing Free Routesinformation together with controller support tools to assist Free Routes operationsApplicability: Participating statesParticular criteria to assess the achievement of the Line of Action: Data processing systemand controller support tools available

Action by:Support IndustryFrom: By: 04/2003


4-12



4-13

AOM04 Implement ATS Route Network (ARN) -Version 4

Confirmed

Definition:Implement ARN Version 4 to accommodate RVSM operations, further optimise routestructures across airspace boundaries between States and better align routes andsectors with traffic flows. Implementation in 3 phases (03/2001, 11/2001, 04/2002).

Scope:

Pan EuropeanApplicable area:

ECAC StatesTimescale:

From: 03/2001By: 04/2002


Supporting Programme:AOM

Strategic fit:ATM 2000+, Vol.2 para.7.1.2 and 8.2; Airspace

Strategy V1.0 para 6.2.6


Continuous En-routeStructure Optimisation

Performance benefitsSafety: Levels will be maintained, no appreciable increase

Capacity: Minor increases in some States through reduction inconflict points and changes in sector configuration toreduce workload. Main benefits allocated to RVSMimplementation

Cost-effectiveness: Minor savings in route distances in some States

Environment: Minor reductions in emissions

Enabler for: Not applicable

Main resource requirements: Changes to route structures and airspace sectors


AOM04-USE01 Adapt Flight Planning From: By: 04/2002 �AOM04-ASP01 Implement national route structure changes From: 03/2001 By: 04/2002 �AOM04-REG01 Amend EUR Regional Plan From: By: 12/2001AOM04-AGY01 Develop and validate ARN V4 From: By: 12/2001


4-14


AOM04-USE01 Adapt Flight PlanningDefinition: Adapt flight planning procedures and systems to take account of ARN Version 4route structure (3 phases: 03/2001, 11/2001, 04/2002)Applicability: All airspace usersParticular criteria to assess the achievement of the Line of Action: Changes to flightplanning systems and procedures and to FMS completed.


AOM04-ASP01 Implement national route structure changesDefinition: Implement route modifications, and where necessary sector changes, toaccommodate ARN Version 4 route structure, amend supporting systems amend andpublish route changes in accordance to AIRAC requirements, and train Staff in newroute/sector configurations. (3 phases: 03/2001, 11/2001, 04/2002.)Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Amendments ot AIPs,etc.

Action by:ANS ProvidersFrom: 03/2001By: 04/2002

AOM04-REG01 Amend EUR Regional PlanDefinition: Gain States endorsement of route changes and amend ICAO EUR RegionalPlan to reflect ARN Version 4 route structures.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: ICAO Plan amended.

Action by:ICAO EUR RegionFrom: By: 12/2001

AOM04-AGY01 Develop and validate ARN V4Definition: Develop and validate ARN Version 4 route structure.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Completion of simulation validation activities.2. Agreement of States to proposed changes.



4-15

AOM05 Optimise airspace sectorisation Confirmed

Definition:Implement optimised airspace sector structures and procedures (traditional sectorsplitting and flexible configuration of sectors) to provide a more balanced capacity andreflect variations in the needs of airspace users.

Scope:

HarmonisationApplicable area:


From: 01/2000By:



Strategic fit:ATM 2000+ Strategy, Vol. 2,para.7.1.1 and 8.2; Airspace

Strategy steps 1F, 2F, 3Fand 4F


Airspace StructureOptimisation and FUA

Performance benefitsSafety: Safety levels maintained

Capacity: Increase through reduction in sector complexity andcontroller workload

Cost-effectiveness: Fuel cost reduction through availability of moreoptimised trajectories

Environment: Emissions reduced through shorter flight times and useof optimum flight levels


Main resource requirements: System enhancements


AOM05-ASP01 Re-organise airspace sector structures From: 01/2000 By: �AOM05-ASP02 Prepare ground ATC systems From: 01/2000 By: �AOM05-ASP03 Implement revised operational procedures From: 01/2000 By: �AOM05-ASP04 Train ATC Staff From: 01/2000 By: �AOM05-AGY01 Adapt ATFM processes and procedures From: 01/2000 By:


4-16


AOM05-ASP01 Re-organise airspace sector structuresDefinition: Re-organise sector structures to reduce sector complexity and workload torealise sector productivity gains.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Promulgation ofairspace sector changes.


AOM05-ASP02 Prepare ground ATC systemsDefinition: Prepare ground ATC systems, validate and implement system modifications andassociated procedures.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Completion of systemmodifications.


AOM05-ASP03 Implement revised operational proceduresDefinition: Define, validate and implement operational procedures to reflect sectorchanges.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Promulgation ofoperational procedures.


AOM05-ASP04 Train ATC StaffDefinition: Train ATC staff in new sector configurations and procedures.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: All staff trained in newprocedures.


AOM05-AGY01 Adapt ATFM processes and proceduresDefinition: Adapt ATFM processes and procedures to take account of airspace sectorchanges.Applicability: For ECAC States airspaceParticular criteria to assess the achievement of the Line of Action: ATFM processes andprocedures developed and applied

Action by:CFMUFrom: 01/2000By:


4-17

AOM06 Implement Flexible Use of Airspace (FUA)Concept

Confirmed

Definition:Implement Flexible Use of Airspace (FUA) concept in all ECAC States, and extend theapplication to include the lower airspace. Implementation in all ECAC States shouldhave been completed in 1998, but is not yet fully achieved. Extension to the lowerairspace is expected to start in 2005.Note: This objective is in the process of being revised and will address only the existing FUA requirements.A new objective is being raised to address the implementation of FUA in the lower airspace, and will beincluded in the next ECIP edition.

Scope:



From: 12/1996By:



Strategic fit:ATM 2000+, Vol.2, para.

7.1.1.2; Airspace Strategysteps 1B, 2B, 3B and 4B


Airspace StructureOptimisation and FUA

Performance benefitsSafety: Some gains through improved availability of more

optimum routes/trajectories

Capacity: Increased through better utilisation of airspaceresources

Cost-effectiveness: Potential cost reduction through availability of moreoptimum routes/trajectories

Environment: Emissions reduced through more optimumroutes/trajectories


Main resource requirements: System enhancements


AOM06-ASP01 Implement FUA concept From: By: 12/2000 �AOM06-ASP02 Implement FUA in lower airspace From: 01/2005 By: �AOM06-ASP03 Prepare ground ATC systems From: By: 12/2004 �AOM06-REG01 Amend Regional Plan From: By: 12/2004AOM06-AGY01 Define common procedures and

guidelinesFrom: By: 12/2004


4-18


AOM06-ASP01 Implement FUA conceptDefinition: Implement fully the FUA concept in all ECAC States.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: FUA adopted in allStates


AOM06-ASP02 Implement FUA in lower airspaceDefinition: Apply FUA to the lower airspace and define and apply additional nationalprocedures as necessary to meet local requirements.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Progress ofimplementation against set milestones.


AOM06-ASP03 Prepare ground ATC systemsDefinition: Prepare ground ATC systems, validate and implement system modifications andassociated procedures for the extension of FUA to the lower airspace.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Completion ofmodifications.


AOM06-REG01 Amend Regional PlanDefinition: Amend ICAO Regional Plan to reflect application of FUA in lower airspace.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: ICAO EUR Planamended

Action by:ICAO EUR RegionFrom: By: 12/2004

AOM06-AGY01 Define common procedures and guidelinesDefinition: Define common procedures and guidelines for application of FUA in lowerairspace.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Approval of proceduresand guidelines.



4-19

AOM07 Implement collaborative civil-militaryairspace planning at national level

Tentative

Definition:Implement collaborative civil-military airspace planning for the planning and use ofnational airspace.Note: this objective is currently being reviewed to address collaborative planning for the establishment,allocation and use of national airspace and cross-border structures. A revised objective will be included inthe next ECIP Edition.

Scope:



From: 01/2003By:



Strategic fit:ATM 2000+, Vol.2 para.

7.1.1.2 and 8.2


Collaborative NationalAirspace Planning

Performance benefitsSafety: Some gains through improved availability of more

optimum routes/trajectories

Capacity: Increase through better utilisation of airspace resources

Cost-effectiveness: Potential cost reduction through avaiability of moreoptimum routes/trajectories

Environment: Emissions reduced through more optimumroutes/trajectories

Enabler for: Implement Collaborative Civil-Military Airspace Planning at EuropeanLevel

Main resource requirements: System enhancement and common data procedures


AOM07-ASP01 Apply common procedures and guidelines From: By: 01/2003 �AOM07-AGY01 Define common procedures and guidelines From: By: 12/2002


4-20


AOM07-ASP01 Apply common procedures and guidelinesDefinition: Apply common procedures and guidelines for national civil-military airspaceplanning. Define and develop additional procedures to match local organisation, ifnecessary.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Working arrangementestablished; procedures published.


AOM07-AGY01 Define common procedures and guidelinesDefinition: Define common procedures and guidelines for civil-military airspace planning atnational level.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Approval of proceduresand guidelines.



4-21

AOM08 Optimise Terminal Airspace structure Agreed

Definition:Enhance Terminal Airspace capacity by optimising all or any of the following aspects asappropriate:1. Placement of SIDs/STARs and Instrument Approach Procedures (as regards

distance flown, flight profile, time, cost and flexibility to all users) and exploiting theuse of RNAV to those ends;

2. Design of Terminal Airspace structures and ATC Sectorisation with a view to evenlydistributing ATC and Flight Crew workload;

3. Minimising adverse ATM-related environmental impact.These measures should follow the guidelines contained in the Terminal AirspaceDesign Guidelines for Operational Methodology (ASM ET1 ST06 � EATCHIP). This anon-going phased implementation

Scope: Harmonisation

Applicable area:Terminal Airspaces in ECAC


Approval reference: Provisional Council - 13/07/2000


Strategic fit:ATM 2000+, Vol.2, para. 8.2


Terminal Airspace Re-organisation

Performance benefitsSafety: Improved by minimising conflict points thereby

balancing ATC and flight crew workload

Capacity: Increase through improved route structures based onRNAV (where appropriate), improved airspace designand ATC Sectorisation

Cost-effectiveness: Reduction in fuel cost by use of optimised trajectories,shorter routes and reduced holdings (whereappropriate)

Environment: Reduced emissions and noise nuisance by use ofoptimal flight procedures and routings

Enabler for: Not Applicable

Main resource requirements: Generally � Methodological approach to terminalairspace evaluation and design; Specifically: Correct application of Precision RNAV (P-RNAV) as an interim step towards RNP RNAV, where appropriate.


4-22


AOM08-ASP01 Implement RNAV SIDs and STARs DELETED22

AOM08-ASP02 Identify shortcomings of existing TerminalAirspace structure, SIDs/STARs; ATCSectorisation and ATC sequencing techniques

From: 01/2001 By: 12/2003 �

AOM08-ASP03 Redesign and implement improved TerminalAirspace structure, SIDs/STARs; ATCSectorisation and ATC sequencing techniquesfollowing the guidelines contained in TerminalAirspace Design Guidelines for an OperationalMethodology (ASM ET1 ST06)

From: 12/2001 By: 12/2005 �

AOM08-AGY01 Develop Terminal Airspace Design Guidelinesfor an Operational Methodology , 2nd Edition(ASM ET1 ST06)

By: 12/2002

22 This SLoA is already incorporated in AOM08-ASP03 and has been deleted.


4-23

AOM08 � Detailed Stakeholder Lines of Action Description

AOM08-ASP02 Identify shortcomings of existing Terminal Airspace structure,SIDs/STARs; ATC Sectorisation and ATC sequencing techniquesDefinition: Identify shortcoming of existing Terminal Airspace structure, SID/STARplacement, ATC Sectorisation and ATC sequencing techniques with due regard forenvironmental concerns so as to improve capacity and efficiency, while maintaining theoverall level of safety. Shortcomings can be identified by following the Terminal Airspaceevaluation methodology contained in the document entitled Terminal Airspace DesignGuidelines for an Operational Methodology, ASM ET1 ST06 [EATCHIP]. Use can be madeof airspace modeller SAAM as developed by AMN and fast- or real-time simulations tovalidate selected options. This will be done as needed on an on-going basis.Applicability: Selected Terminal Airspaces in ECAC StatesParticular criteria to assess the achievement of the Line of Action: Shortcomings identified.


AOM08-ASP03 Redesign and implement improved Terminal Airspace structure,SIDs/STARs; ATC Sectorisation and ATC sequencing techniquesfollowing the guidelines contained in Terminal Airspace DesignGuidelines for an Operational Methodology (ASM ET1 ST06)Definition : Redesign and implement improved Terminal Airspace Structure, SIDs/STARs,ATC Sectorisation and ATC Sequencing techniques based upon the guidelines containedin Terminal Airspace Design Guidelines for an Operational Methodology, ASM ET1 ST06with a view to accommodating new generation aircraft with enhanced navigation andperformance characteristics. Where appropriate, RNAV-based SIDs/STARs may be usedto provide structured traffic flows within the Terminal Airspace. This will be done as neededon an on-going basis.Applicability: Selected Terminal Airspaces in ECAC airspaceParticular criteria to assess the achievement of the Line of Action: Implementation ofTerminal Airspace Structure, SIDs/STARs, ATC Sectorisation and ATC Sequencingtechniques as appropriate.


AOM08-AGY01 Develop Terminal Airspace Design Guidelines for an OperationalMethodology , 2nd Edition (ASM ET1 ST06)Definition: Develop guidelines Terminal Airspace Design Guidelines for an OperationalMethodology(ASM/ET1/ST16). 1st Edition is already available. Second Edition underdevelopment.Applicability: Selected TERMINAL AIRSPACEs in all ECAC StatesParticular criteria to assess the achievement of the Line of Action: Guidelines available.



4-24



4-25

AOM09 Implement re-organisation of ECAC airspace to ensurethe application of a common ICAO ATS classification

above a common agreed level

Tentative

Definition:

In accordance with the EUROCONTROL Airspace Strategy for ECAC States, there is arequirement to re-organise the airspace in each ECAC States to ensure the application ofcommon ICAO Air Traffic Services classification above a commonly agreed level (FlightLevel 'x' - to be decided) to provide a known traffic and known intentions environment (Class'N' airspace).

This is the first of 5 objectives that set out stepped airspace changes in the ECAC Statesthat will be introduced progressively over the next 14 years, and are intended to simplifyairspace organisation and structure and lead to uniform and simplified airspace divisionsand classifications to support the provision of seamless ATS across national boundaries.

Note: The completion dates given in this objective are provisional at this stage, and final dates are dependent ofthe outcome of development work and agreement with States.

Scope:Pan-European

Applicable Area:ECAC States

Timescale:From:By: 04/2003

Approval Reference: Provisional Council - 07/2001


Strategic Fit:ATM2000+ , Vol 2, para 7.1.1.1and Airspace Strategy; Edition

1.0, action 1A


Simplification of airspaceorganisation

Performance BenefitsSafety: Improved through simplification of airspace organisation and

uniform ATS leading to reduced co-ordination errors

Capacity: Potential increase through reduction in co-ordinationworkload. Better facilitation of delegation of ATS across Stateboundaries

Cost-effectiveness: Increased in terms of quality of service

Environment:Enabler for: FUA application in a uniform airspace organisation

Main resource requirements: Adaptation of systems; training of staff; changes toprocedures


AOM09-USE01 Train crews and adapt airborne systems as required From: By: 03/2003 �AOM09-ASP01 Train ATC staff in new procedures From: By: 03/2003 �AOM09-ASP02 Adapt ground systems as necessary From: By: 03/2003 �AOM09-ASP03 Adapt national airspace organisation as necessary From: By: 04/2003 �AOM09-REG01 Amend ICAO EUR document From: By: 03/2003AOM09-REG02 Revise national legislation as required From: By: 03/2003 �AOM09-AGY01 Develop and validate proposals From: By: 12/2001AOM09-AGY02 Develop initial ECAC Airspace Guidance document From: By: 12/2001


4-26


AOM09-USE01 Train crews and adapt airborne systems, as requiredDefinition: Train crews and adapt airborne systems to new proceduresApplicability: All airspace users flying in the Upper ECAC airspaceParticular criteria to assess the achievement of the Line of Action:1. Progress in staff training2. Completion of airborne system modifications


AOM09-ASP01 Train ATC staff in new proceduresDefinition: Train ATC staff in new procedures as necessaryApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: All ATC staff trained innew procedures


AOM09-ASP02 Adapt ground systems as necessaryDefinition: Adapt ground systems to support new airspace organisational change asnecessaryApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Completion of changesto ground systems


AOM09-ASP03 Adapt national airspace organisation as necessaryDefinition: Adapt national airspace organisation where needed within the framework of theinitial ECAC Airspace guidance document

Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Airspace organisationalchanges completed


AOM09-REG01 Amend ICAO EUR DocumentsDefinition: Amend the ICAO EUR document as necessary to reflect airspace organisationalchangesApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Completion ofamendments


AOM09-REG02 Revise national legislation as requiredDefinition: Enact regulatory material where needed for implementation of new principles,rules and procedures to reflect airspace organisational changesApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Regulation and nationalpublications completed


AOM09-AGY01 Develop and validate proposalsDefinition: Develop and validate proposals for airspace organisational changes and definean agreed uniform upper level in co-operation with affected stakeholdersApplicability: ECAC States.Particular criteria to assess the achievement of the Line of Action: Proposals validated andagreed by the ANT


AOM09-AGY02 Develop initial ECAC Airspace Guidance documentDefinition: Develop an initial ECAC Airspace Guidance document for use by the ECACStates providing guidance material on airspace organisational issues

Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:Completion and adoption of the document by the ANT



4-27


Tentative

Definition:Implement ARN Version 5 to further optimise route structures across airspace boundariesbetween States and better align routes and sectors with traffic flows.

Scope:



From: 03/2002By: 06/2004



Strategic fit:ATM 2000+, Vol.2 para.7.1.2 and 8.2; AirspaceStrategy V1.0


Continuous En-routeStructure Optimisation


Capacity: Increased through reduction in conflict points, andspecialisation of routes and sectors to enhanceproductivity and reduce controller workload

Cost-effectiveness: Minor savings in route distances in some States

Environment: Some reduction in emissions


Main resource requirements: Procedural changes and training


AOM10-USE01 Adapt Flight Planning From: 06/2003 By: 06/2004 �AOM10-ASP01 Implement National Route structure changes From: 06/2003 By: 06/2004 �AOM10-REG01 Amend EUR Regional Plan From: By: 01/2004AOM10-AGY01 Develop and validate ARN V5 From: 03/2002 By: 06/2004AOM10-AGY02 Adapt ATFM processes and procedures From: By: 06/2004


4-28


AOM10-USE01 Adapt flight planningDefinition: Adapt flight planning procedures and systems to take account of ARN Version 5route structure.Applicability: All airspace usersParticular criteria to assess the achievement of the Line of Action: Changes to flightplanning systems and procedures and to FMS completed.

Action by:Airspace UsersFrom: 06/2003By: 06/2004

AOM10-ASP01 Implement national route structure changesDefinition: Implement route modifications, and where necessary sector changes, toaccommodate ARN Version 5 route structure, amend supporting systems, amend andpublish route changes in accordance to AIRAC requirements, and train staff in newroute/sector configurations.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Amendments ot AIPs,etc.


AOM10-REG01 Amend EUR Regional PlanDefinition: Gain States endorsement of route changes and amend ICAO EUR RegionalPlan to reflect ARN Version 5 route structures.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: ICAO Plan amended.


AOM10-AGY01 Develop and validate ARN V5Definition: Develop and validate ARN Version 5 route structure.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Completion of simulation validation activities.2. Agreement of States to proposed changes (via the ANT and RNDSG).

Action by:EATMPFrom: 03/2002By: 06/2004

AMO10-AGY02 Adapt ATFM processes and proceduresDefinition: Adapt ATFM processes and procedures as necessary to accommodate ARN V5route structure.Applicability: For ECAC States' airspace.Particular criteria to assess the achievement of the Line of Action: Completion of changes.


ECIP � YEARS 2002 TO 2006 - LEVEL 2 AOP01

4-29

AOP01 Implement runway capacity enhancementguidelines

Tentative

Definition:To increase the handling capacity of airports' runway systems, runway occupancy times(ROT) need to be reduced to the lowest safe and practicable value. The runwaycapacity enhancement guidelines provide advice to aviation stakeholders on the bestand recommended practices used in the industry to achieve this. The guidelines providethe stakeholders with a range of measures from which they can select those that arebest suited for local operations.

Scope:


All airports in the ECAC areaTimescale:

From: 01/2002By:


Supporting Programme:AOP

Strategic fit:ATM 2000+ Strategy Vol.2,

para 7.4.1 and AirportOperations Strategy Vol. 2

DfC 4, OI 4.1


Surface Management

Performance benefitsSafety: Safer operations due to more predictable behaviour of

aircraft on the runway

Capacity: Increase in overall capacity if airport airsidecomponents (taxiways, aprons, gates/stands) are ableto manage the increased throughput

Cost-effectiveness: Savings on costs through more efficient surfaceoperations. However if new rapid exit taxiways (RETs)have to be built the return on investments will take timeto materialise

Environment: Indirect benefit from less taxi and holding time forindividual aircraft, so less noise and fuel burn

Enabler for: Airport airside capacity enhancement

Main resource requirements: Special measuring equipment, and performance trainingfor users and providers. Construction of new or additional RETs at some airports


AOP01-USE01 Train aircrew in the application of guidelines From: 06/2002 By: �AOP01-ASP01 Train airport controllers in application of

guidelinesFrom: 06/2002 By:

AOP01-APO01 Apply runway capacity enhancementguidelines depending on local circumstances

From: 01/2002 By:

AOP01-APO02AOP01-APO03

Measure ROTs.Construct new or additional RETs as required

From: 01/2002From: 01/2002

By: By:

AOP01-AGY01 Develop ATC procedures for newdevelopments

From: By:


4-30

AOP01 - Detailed Stakeholder Lines of Action Description

AOP01-USE01 Train aircrew in the application of guidelinesDefinition: Train aircrew in the application of guidelines.Applicability: Aircraft Operators operating from capacity constrained airports in the ECACarea.Particular criteria to assess the achievement of the Line of Action: Number of aircraftoperators providing pilot training on the application of the guidelines.


AOP01-ASP01 Train airport controllers in the application of guidelinesDefinition: Train aerodrome controllers in the application of guidelines.Applicability: Capacity constrained airports in the ECAC area.Particular criteria to assess the achievement of the Line of Action: Number of airportshaving introduced the guidelines and having low average ROTs.


AOP01-APO01 Apply runway capacity enhancement guidelinesDefinition: Apply the runway capacity enhancement guidelines depending on localcircumstances.Applicability: All airports in the ECAC area.Particular criteria to assess the achievement of the Line of Action: Number of airportsapplying guidelines.

Action by:Airport OperatorsFrom: 01/2002By:

AOP01-APO02 Measure ROTsDefinition: The ROTs of landing and departing aircraft shall be monitored and airspaceusers notified of fleet performance.

Applicability: Coordinated and capacity constrained airports in the ECAC area.Particular criteria to assess the achievement of the Line of Action: Number of airportsapplying the guidelines.


AOP01-APO03 Construct new or additional RETs as requiredDefinition: Additional or new RETs to be constructed where the location of existing RETsdo not meet the needs of typical aircraft performances.Applicability: Capacity constrained airports in the ECAC area.Particular criteria to assess the achievement of the Line of Action: Number of airportshaving consistently low ROTs.


AOP01-AGY01 Develop ATC procedures for new developmentsDefinition: develop ATC procedures in relation to new developmentsApplicability: Agency through EATMP/ANT/APDSGParticular criteria to assess the achievement of the Line of Action: Existence of applicableATC procedures.

Action by:EATMPFrom: By:


4-31

AOP02 Implement use of the Commonly AgreedMethodology for Airport Airside Capacity

Assessment (CAMACA) Tool

Tentative

Definition:Implement a commonly agreed methodology for airport airside capacity assessment byintroducing the use of the Airport Airside Capacity Assessment (CAMACA) tool as ameans to assist in optimising available airport capacity. The tool will be available to allairports, but the priority will be its application by capacity constrained and co-ordinatedairports.

Scope:Harmonisation

Applicable area:All airports in the ECAC

States.



Supporting Programme:AOP

Strategic fit:ATM 2000+ Strategy Vol.2

paras 7.4.3 and 8.2.


Surface Management

Performance benefitsSafety: Some safety gains through a more precise capacity

assessment avoiding overloading of airport systems

Capacity: Capacity improvement where studies indicate that theavailable capacity is under-utilised and the associatedsensitivity analysis identifies potential opportunities forenhancement

Cost-effectiveness: Improved efficiency leading to more cost-effectiveairside operations

Environment: No direct affect

Enabler for: Application of Council Regulation (EC) 95/93; Aircraft Operators� twiceyearly slot co-ordination

Main resource requirements: Computer facilities to access tool and training of staff


AOP02-USE01 Use �declared capacity� in combination withcapacity as calculated by CAMACA tool as aninput to schedule planning

From: 02/2003 By:

AOP02-ASP01 Use �declared capacity� in combination withcapacity as calculated by CAMACA tool as aninput to operational planning

From: 02/2003 By:

AOP02-APO01 Introduce CAMACA tool and train staff in itsapplication

From: 12/2002 By:

AOP02-APO02 Use �declared capacity� in combination withcapacity as calculated by CAMACA tool as aninput to operational planning

From: 02/2003 By:

AOP02-REG01 National co-ordinators use �declared capacity�for slot allocation and schedule planning

From: 02/2003 By:

AOP02-AGY01 Develop and make available the CAMACA tool From: By: 01/2003AOP02-AGY02 Maintain model as required From: 02/2003 By:


4-32

AOP02 - Detailed Stakeholder Lines of Action Description

AOP02-USE01 Use �declared capacity� in combination with capacity as calculatedby CAMACA tool as an input to schedule planningDefinition: Airspace users to use �declared capacity� in combination with capacity ascalculated by CAMACA tool as input for operational planning for the next half-yearschedule.Applicability: Airspace users at co-ordinated airports in the ECAC area.Particular criteria to assess the achievement of the Line of Action: Number of airspaceusers making regular use of the CAMACA tool results.


AOP02-ASP01 Use �declared capacity� in combination with capacity as calculatedusing the CAMACA tool as an input to operational planningDefinition: Airports to use �declared capacity� in combination with capacity as calculated byCAMACA tool as input for operational planning for the following half-year schedule.Applicability: Airports in the ECAC areaParticular criteria to assess the achievement of the Line of Action: Number of airportsmaking regular use of the CAMACA tool.


AOP02-APO01 Introduce CAMACA tool and train staff in its applicationDefinition: Train airport staff in the application and use of the CAMACA tool.Applicability: Airports in the ECAC areaParticular criteria to assess the achievement of the Line of Action: All staff trained in theuse of the CAMACA tool.

Action by:AirportsFrom: 12/2002By:

AOP02-APO02 Use �declared capacity� in combination with capacity as calculatedusing the CAMACA tool as an input to operational planningDefinition: Airports to use �declared capacity� in combination with capacity as calculated byCAMACA tool as input for operational planning for the following half-year schedule.Applicability: Airports in the ECAC areaParticular criteria to assess the achievement of the Line of Action: Number of airportsmaking regular use of the CAMACA tool.

Action by:AirportsFrom: 02/2003By:

AOP02-REG01 National Co-ordinators use �declared capacity� for slot allocationand schedule planningDefinition: National slot co-ordinators to use �declared capacity� in combination withcapacity as calculated by CAMACA tool as an input to operational planning for the nexthalf-year scheduleApplicability: National co-ordinators for their national coordinated airports in the ECACarea.Particular criteria to assess the achievement of the Line of Action: Majority of national slotco-ordinators making regular use of the CAMACA tool results.

Action by:National slot co-ordinatorsFrom: 02/2003By:

AOP02-AGY01 Develop and make available the CAMACA toolDefinition: Develop the CAMACA tool and make available via the InternetApplicability: Airports in the ECAC areaParticular criteria to assess the achievement of the Line of Action: Avalaibility of theCAMACA tool on the Internet


AOP02-AGY02 Maintain model as requiredDefinition: Regularly test the model for operational relevance and update as necessaryusing Internet facilities.Applicability: Users of the CAMACA tool.Particular criteria to assess the achievement of the Line of Action: Regular updates.

Action by:EATMPFrom: 02/2003By:

ECIP � YEARS 2002 TO 2006 - LEVEL 2 ATC01

4-33

ATC01 Implement Airborne Collision AvoidanceSystem (ACAS) II

Confirmed

Definition:Implement the safe operation of Airborne Collision Avoidance Systems (ACAS) II (Phase 1 in2000 and Phase 2 in 2005).

Scope:



From: 01/2000By: 01/2005

Approval reference: Provisional Council - 07/2000 MATSE/4 and MATSE/5

Supporting Programme:ACAS

Strategic fit:ATM 2000+, Vol,2 para 7.3.8

and 8.2


Safety Nets

Performance benefitsSafety: Airborne collision risk reduced by up to a factor of 6

Capacity: Not applicable

Cost-effectiveness: Not applicable

Environment: Not applicable


Main resource requirements: Equipment for concerned aircraft; training for controllers andflight crews; legal amendments and regulatory provisions

Stakeholder Lines of Action:ATC01-USE01 Install ACAS II in aircraft subject to ACAS II

mandate (Phase 1)From: By: 01/2000

ATC01-USE02 Install ACAS II in aircraft subject to ACAS IImandate (Phase 2)

From: By: 01/2005

ATC01-USE03 Train aircrews in ACAS II From: By: 01/2000 �ATC01-USE04 Provide pilot reports to EEC Brétigny From: 01/1995 By: 01/2000 �ATC01-MIL01 Install ACAS II in transport aircraft From: By: 01/2005ATC01-ASP01 Train controllers in ACAS II From: By: 01/2000 �ATC01-ASP02 Establish ACAS II performance monitoring From: 01/1995 By: 01/2000 �ATC01-REG01 Establish national legal provisions for ACAS II From: By: 06/1998 �ATC01-REG02 Adapt JAR-OPS provisions into national legal

proceduresFrom: By: 07/1999

ATC01-REG03 Implement changes to controller / pilot legalresponsibilities for ACAS II

From: By: 06/1998 �

ATC01-REG04 Approval of ACAS II training and operationalmaterial and courses for controllers andaircrew

From: By: 01/2000 �

ATC01-REG05 Amend related ICAO documentation From: By: 01/2005ATC01-REG06 Certify ACAS II compliant equipment From: By: 01/2005 �ATC01-REG07 Amend TCAS MOPS DELETEDATC01-AGY01 Develop means to analyse ACAS events

occurring within the ECAC AirspaceACHIEVED

ATC01-AGY02 Develop means to collect and analyse studyresults in support of decisions to be made onACAS implementation

ACHIEVED

ATC01-AGY03 Develop means to ensure successfulintroduction of TCAS II Version 7.0 software

ACHIEVED

ATC01-AGY04 Develop means to handle exemptions duringthe implementation period

ACHIEVED

ATC01-SUP01 Produce and install ACAS II compliantequipment

From: By: 01/2005


4-34

ATC01 - Detailed Stakeholder Lines of Action Description

ATC01-USE01 Install ACAS II in aircraft subject to ACAS II mandate (Phase 1)Definition: All civil fixed-wing turbine engined aircraft having a maximum certificated takeoff mass exceeding 15,000 kg or a passenger seating configuration of more than 30 shallbe equipped with ACAS II.This Line of Action is currently subject to an Exceptional Exemption period process.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action:1. Achieved: When all local civil aircraft (to which the mandate for Phase I applies) are

fitted with ACAS II SARPS compliant equipment.2. Late: when some local civil aircraft are still not equiped with ACAS II SARPS

compliant equipment.

Note: the aforementioned criteria enable an assessment of the local status of the SLOA ina specific ECAC State. However, when establishing the overall status of the SLOA, it willbe necessary to take into account, in addition, all non-ECAC civil aircraft foreseen to enterthe ECAC airspace.


ATC01-USE02 Install ACAS II in aircraft subject to ACAS II mandate (Phase 2)Definition: All civil fixed-wing turbine engined aircraft having a maximum certificated takeoff mass exceeding 5,700 kg or a passenger seating configuration of more than 19 shall beequipped with ACAS II.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:For a reporting date before 01/01/2005:1. Achieved: When all local civil aircraft (to which the mandate for Phase II applies) are

equipped with ACAS II SARPS compliant equipment.2. Not Achieved: When some local civil aircraft are still not equipped with ACAS II

SARPS compliant equipment.3. On time otherwise.• For a reporting date after 01/01/2005:Achieved: See point 1 above• Late otherwise

Note: the aforementioned criteria enable an assessment of the local status of the SLOA ina specific ECAC State. However, when establishing the overall status of the SLOA, it willbe necessary to take into account, in addition, all non-ECAC civil aircraft foreseen to enterthe ECAC airspace.


ATC01-USE03 Train aircrews in ACAS IIDefinition: Train aircrews in ACAS II.Note: ongoing action (training has to be continued and ab initio training has to be instigatedas required)Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Achieved: When the local Regulatory Authority is satisfied that the Local Airspace

Users have trained all current aircrew members by applying training material andmethods approved in ATC01-REG04, AND when the Local Military Authorities declarethat all their own aircrew members have been trained using the same criteria.

2. Late otherwise

Note: the aforementioned criteria enable an assessment of the local status of this SLOA ina specific ECAC State. However, when establishing the overall status of the SLOA, it willbe necessary to take into account, in addition, the ACAS training of all non-ECAC aircrewwho enter the ECAC airspace.



4-35

ATC01-USE04 Provide pilot reports to EEC BrétignyDefinition: Participate in an ACAS II performance monitoring programme, to ensure ACASII performance integrity in the ECAC airspace environment, and to ensure operational andtechnical feedback.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Achieved: When the local Regulatory Authority and the local Military Authorities

ensure that pilot reports are sent to Bretigny (for example, if it is made mandatorythrough national legislation, or if a process has been put in place), OR when therelevant service in Bretigny reports that there is no likely problem regarding thesending of such reports from the Local Airspace Users.

2. Late otherwise


ATC01-MIL01 Install ACAS II in transport aircraftDefinition: Commitment to install ACAS II in military transport aircraftApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:For a reporting date before 01/01/2005:1. Achieved: When Military Authorities declare that all their local transport aircraft (with

a maximum take-off mass or seating capacity which fulfills the criteria for the Phase 1ACAS II mandate) are fitted with ACAS II SARPS compliant equipment or equivalent.

2. Not Achieved: When some local Military transport aircraft are still not fitted withACAS II SARPS compliant equipment or equivalent.

For a reporting date after 01/01/2005:1. Achieved: See point 1 above2. Late otherwise

Note: the aforementioned criteria enable an assessment of the local status of this SLOA ina specific ECAC State. However, when establishing the overall status of the SLOA, itmight be necessary to take into account, in addition, all non-ECAC military transportaircraft foreseen to enter the ECAC airspace.

Action by:Military AuthoritiesFrom: By: 01/2005

ATC01-ASP01 Train controllers in ACAS IIDefinition: Train controllers to ACAS II. This is an ongoing action; training to be continuedand ab initio training to be carried out as requiredApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Achieved: When the local ATS Provider demonstrates that all controllers have been

trained by utilising the training material and methods approved in ATC01-REG04,AND when the local Military Authorities demonstrate the same, applying similartraining methods.

2. Late otherwise


ATC01-ASP02 Establish ACAS II performance monitoringDefinition: Establish an ACAS II performance monitoring programme, to ensure ACAS IIperformance integrity in the ECAC airspace environment, and to ensure operational andtechnical feedbackApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Achieved: When the local ATS Provider and local Military Authorities ensure that

Controller ACAS Reports and other relevant data (i.e. radar data, etc.) aresystematically sent to Bretigny (i.e. if it is made mandatory, or if a process has beenput in place), OR when the relevant service in Bretigny reports that there is no likelyproblem regarding the sending of reports from Local Controllers, OR when LocalACAS performance monitoring has been established and operates in collaborationwith Bretigny.

2. Late otherwise



4-36

ATC01-REG01 Establish national legal provisions for ACAS IIDefinition: Establish national legal provisions for carriage and operation of ACAS II.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Achieved: When the local Regulatory Authority has published AIC(s), in accord with

the ACAS II mandate, covering ACAS policy, implementation and monitoring, in linewith the specimen AIC released by the ACAS programme, and/or, as appropriate, hasamended the national AIP, and all relevant regulatory material necessary to establishthe legal framework for ACAS within the State, AND when the Local MilitaryAuthorities declare that all their relevant military regulatory material has also beenamended � where applicable.

2. Late otherwise


ATC01-REG02 Adapt JAR-OPS provisions into national legal proceduresDefinition: Adapt JAR-OPS provisions into national legal proceduresApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Achieved: When the Local Regulatory Authority demonstrates it has adopted JAR-

OPS provisions into the national legal procedures.2. Late otherwise


ATC01-REG03 Implement changes to controller / pilot legal responsibilities forACAS IIDefintion: Implement established controller and pilot legal responsibilities during ACAS IIoperational events in national airspaceApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Achieved: When the local Regulatory Authority and Military Authorities have agreed

the responsibilities and they are suitably promulgated.2. Late otherwise


ATC01-REG04 Approval of ACAS II training and operational material and coursesfor controllers and aircrewDefinition: Approve the ACAS II training and operational material and courses to be givento aircrew and controllers. Approve amendments to flight operations manuals. (ongoingaction)Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Achieved: When the Local Regulatory Authority (assisted by the ATS Provider) has

approved controller and aircrew training courses and material AND Military Authoritieshave gone through the same process.

2. Late otherwise


ATC01-REG05 Amend related ICAO documentationDefinition: Amend ACAS and Mode S SARPs and other ICAO documentation.Applicability: GlobalParticular criteria to assess the achievement of the Line of Action:1. Achieved: When ICAO amends the required documentation as a result of inputs from

States and recommendations from its own Panel groups.2. Not Achieved otherwise


ATC01-REG06 Certify ACAS II compliant equipmentDefinition: Certify TCAS II Version 7.0 equipment, compliant with ACAS II SARPs, and theappropriate TCAS II Minimum Operational Performance Specifications (MOPS) andTechnical Standards Orders (TSO).Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Achieved: When the Local Regulatory Authority demonstrates it has approved

local certification procedures and standards for the equipage of its national fleet(where applicable).

2. Not Achieved otherwise



4-37

ATC01-SUP01 Produce and install ACAS II compliant equipmentDefinition: Produce certified ACAS II compliant equipment, including the authentication ofSupplementary Type Certificates (STCs), Service Bulletins and the like (as applicable).(ongoing action)Applicability: Support IndustryParticular criteria to assess the achievement of the Line of Action:1. Achieved: When ACAS II compliant equipment is ready to be installed in local

aircraft.2. Not achieved otherwise

Action by:AvionicsManufacturers &Original EquipmentManufacturersFrom: By: 01/2005


4-38



4-39

ATC02 Implement ground based safety nets Confirmed

Definition:Implement ground based safety tools such as Short Term Conflict Alert (STCA),Airborne Proximity Warning (APW), and Minimum Safe Altitude Warning (MSAW).Note: This Objective is the continuation of former CIP Objectives 5.10.1 to 5.10.4., confirmed by MATSE 6(01/2000)

Scope:Harmonisation

Applicable area:ECAC States


Approval reference: Provisional Council - (07/2000)

Supporting Programme:ASA

Strategic fit:ATM 2000+, Vol.2, paras

7.3.8 and 8.2; ODP StrategyVol.2 para. 3.6 (to bereplaced by ATC DataProcessing Strategy

Document by end 2001)


Enhanced Safety Nets -Some Units

Performance benefitsSafety: Contribution to resolution of critical events and recovery

from incidents

Capacity: Indirect through increased controller confidence as acapacity enabler

Cost-effectiveness: Contributing element to the prevention of collisions is animportant cost saver



Main resource requirements: Enhancements to systems


ATC02-ASP01 Implement Short Term Conflict Alert (STCA) From: By: 12/1998 �ATC02-ASP02 Implement Area Proximity Warning (APW) From: By: 12/1998 �ATC02-ASP03 Implement Minimum Safe Altitude Warning

(MSAW) for ACCs and TMAsFrom: By: 12/1998

ATC02-ASP04 Implement Minimum Safe Altitude Warning(MSAW) for Final Approach in TMAs with cat. 1airports (Approach Path Monitoring)

From: By: 12/2001


4-40


ATC02-ASP01 Implement Short Term Conflict Alert (STCA)Definition: Implementation of an STCA Function in Terminal Control Areas (TMAs). andArea Control Centres (ACCs). This system provides a warning to the controller wheneverthe safe vertical and/or horizontal separation between aircraft is predicted to be violatedApplicability: ACCs and TMAs

Particular criteria to assess the achievement of the Line of Action: Function isimplemented, documented and in operational use


ATC02-ASP02 Implement Area Proximity Warning (APW)Definition:Implementation of an APW Function in ACCs and TMAs. This system provides awarning to the controller whenever a violation (horizontal or vertical) of a permanent ortemporary restricted area is predicted in the near future (e.g. within 2 minutes), or isalready taking place.Applicability: ACCs and TMAs



ATC02-ASP03 Implement Minimum Safe Altitude Warning (MSAW) for ACCs andTMAsDefinition:Implement Minimum Safe Altitude Warning (MSAW) function in TMAs andACCs. This system provides a warning to the controller when an aircraft descends belowminimum safe altitude (defined to avoid collision with the terrain) down to and including the"final approach" fix altitude (for en-route).Applicability: ACCs and TMAs



ATC02-ASP04 Implement Minimum Safe Altitude Warning (MSAW) for FinalApproach in TMAs with cat. 1 airports (Approach Path Monitoring)Definition: Implement Minimum Safe Altitude Warning (MSAW) function in TMAs with cat. 1airports (Approach Path Monitoring). This system provides a warning to the controller whenan aircraft descends below minimum safe altitude (defined to avoid collision with theterrain) during the "final approach" down to ground level.Applicability: TMAs




4-41

ATC03 Implement advanced automated ground-ground co-ordination

Confirmed

Definition:Implement advanced ground-ground data exchange and automated co-ordinationprocedures to reduce controller workload (SYSCO).Note: This Objective is the continuation of former CIP Objectives 3.5.3, 3.5.6, 5.3.5, 5.3.6 and 5.3.8,confirmed by MATSE 6 (01/2000)

Scope:



From: 12/1998By:



Strategic fit:ATM2000+, Vol.2, para 8.2;

ODP Strategy Vol.2 para. 7.3(to be replaced by ATC DataProcessing Strategy by end

2001)


Use of AutomatedCommunications toReduce ControllerWorkload

Performance benefitsSafety: Reduction of human error

Capacity: Flight data consistency will enable further optimisationof flexible use of airspace and improvement of planning

Cost-effectiveness: More efficient planning and operational decision making



Main resource requirements: Enhancements to systems; staff training


ATC03-ASP01 Provide advanced co-ordination supportbetween ATC units

From: 12/1998 By:

ATC03-ASP02 Provide transfer to communication betweenATC units

From: 12/1998 By:

ATC03-ASP03 Provide advanced co-ordination supportbetween civil and ATC military units

From: 12/1998 By: �

ATC03-ASP04 Provide advanced co-ordination supportbetween ATC and Airport Services

From: 12/1998 By:

ATC03-ASP05 Provide very advanced co-ordination supportbetween ATC and Airport Systems

From: 12/2001 By:

ATC03-APO01 Provide advanced co-ordination supportbetween ATC and Airport Services

From: 12/1998 By:

ATC03-APO02 Provide very advanced co-ordination supportbetween ATC and Airport Systems

From: 12/2001 By:


4-42


ATC03-ASP01 Provide advanced co-ordination support between ATC unitsDefinition: Implementation and operational use of co-ordination messages between TMAand en-route centres, based on SYSCO level 1.Applicability: Pairs of ACCs/APPs



ATC03-ASP02 Provide transfer to communication between ATC unitsDefinion :Implementation and operational use of a facility for transfer of communciation foruse between TMA and en-route centres (ACCs), based on SYSCO level 1.Applicability: Pairs of ACCs/APPs



ATC03-ASP03 Provide advanced co-ordination support between civil and ATCmilitary unitsDefinition:Processing and display of exchanged flight data information between civil andmilitary ATC units, and system support for the crossing of areas controlled by civil unitsand by flights controlled by military units.Applicability: All applicable ACCs/APPs and military ATC units



ATC03-ASP04 Provide advanced co-ordination support between ATC and AirportServicesDefinition: Implementation and operational use of automatic co-ordination between theATC TMA system and the Airport Services - e.g. by providing Airport Services with aterminal of the ATC systemApplicability: All TMAs containing capacity constrained airports



ATC03-ASP05 Provide very advanced co-ordination support between ATC andAirport SystemsDefinition: Implementation and operational use of automatic co-ordination between theATC TMA system and the Airport system.Applicability: All TMAs containing capacity constrained airports



ATC03-APO01 Provide advanced co-ordination support between ATC and AirportServicesDefinition: Implementation and operational use of automatic co-ordination between theATC TMA system and the Airport Services- e.g. by providing airport services with aterminal of the ATC systemApplicability: Busy Airports



ATC03-APO02 Provide very advanced co-ordination support between ATC andAirport SystemsDefinition: Implementation and operational use of automatic co-ordination between theATC TMA system and the Airport SystemApplicability: Busy airports




4-43

ATC04 Achieve required radar separation minima Confirmed

Definition:Apply radar separation minima commensurate with traffic needs.Note: This Objective is the continuation of former CIP Objectives 3.4.1 to 3.4.7, confirmed by MATSE 6(01/2000)

Scope:Harmonisation




Supporting Programme:Not applicable

Strategic fit:ECAC En-Route Strategy for

the 90's


Not applicable


Capacity: Improved through use of optimum spacing

Cost-effectiveness: Under investigation

Environment: Under investigation


Main resource requirements: Not applicable


ATC04-ASP01 Radar separation within one en-route sector From: By: 12/1995ATC04-ASP02 Radar separation for verbal transfer between

en-route sectors, in the same ACCFrom: By: 12/1995

ATC04-ASP03 Radar separation for verbal transfer betweenACCs

From: By: 12/1995

ATC04-ASP04 Silent radar transfer between en-route sectorsin the same ACC

From: By: 12/1995

ATC04-ASP05 Silent radar transfer between ACCs From: By: 12/1998ATC04-ASP06 Implement 3 NM radar separation within High

complexity TMAsFrom: By: 06/1999

ATC04-ASP07 Implement 2.5 NM radar separation on FinalApproach at Category 1 Airports

From: By: 12/1999


4-44

ATC04 - Detailed Stakeholder Lines of Action DescriptionATC04-ASP01 Radar separation within one en-route sector

Definition: A radar separation minimum of 5 NM/10 NM may be applied between aircraftunder the responsibility of one controller, throughout the area of jurisdiction.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: To be defined


ATC04-ASP02 Radar separation for verbal transfer between en-route sectors, inthe same ACCDefinition: A radar separation minimum of 5 NM/ 10 NM may be applied at the time oftransfer of control between adjacent en-route sectors, in the same ACC, provided thatverbal cordination is effected between the transferring and accepting controllers.Applicability: ECAC States



ATC04-ASP03 Radar separation for verbal transfer between ACCsDefinition: A radar separation minimum of 5NM/10NM may be applied at the time oftransfer of control between adjacent ACCs, provided that verbal co-ordination is effectedbetween the transferring and accepting controllersApplicability: ECAC (Pair of ACCs of whole ECAC area)



ATC04-ASP04 Silent radar transfer between en-route sectors in the same ACCDefinition: A radar separation minimum of 10 NM/15NM may be applied between aircraft atthe time of transfer of control between en-route sectors in the same ACC, withoug verbalco-ordination being effected between the transferring and the accepting controllers.Applicability: ACC of whole ECAC area



ATC04-ASP05 Silent radar transfer between ACCsDefinition: A radar separation minimum of 10NM/15NM may be applied between aircraft atthe time of transfer of control between adjacent ACCs without verbal co-ordination beingeffected between the transferring and the accepting controllers.Applicability: Pair of ACCs of whole ECAC area



ATC04-ASP06 Implement 3 NM radar separation within High Complexity TMAsDefinition: A radar separation of 3NM may be applied between aircraft throughout the TMAarea of jursidiction. Controllers are permitted to apply this separation minima, taking duenotice of relevant safety, technical, operational and other circumstances. Two-way direct,instantaneous controller to controller voice communication facilities are mandatory whenthe separation Is applied between aircraft under the responsibility of different controllers.Applicability: High complexity TMAs

Particular criteria to assess the achievement of the Line of Action:To be defined


ATC04-ASP07 Implement 2.5 NM radar separation on Final Approach at Category1 AirportsDefinition: A radar separation of 2.5 NM may be applied between succeeding aircraftestablished on the final approach track within 10 NM o fthe landing threshold, proivdedprescribed procedures are respected. The controller is permitted to apply this requiredseparation minima, taking due notice of relevant safety, technical, operational and othercircumstances.Applicability: High complexity TMAs




4-45

ATC05 Improve procedures through Mode Selementary surveillance information

Confirmed

Definition:Implement improved procedures using Mode S elementary surveillance information.

Scope:Multi National

Applicable area:GB, FR, DE, BE, LU, NL, CH


Approval reference: Provisional Council � 07/2000 ; Permanent CommissionRecommendation � 11/2000

Supporting Programme:Mode S

Strategic fit:ATM 2000+ Strategy, Vol.2,para. 7.3.3.; ODP Strategy

Version 0.5, para. 7.3 & 7.4;Surveillance Strategy


Improved proceduresthrough Mode Selementary surveillanceinformation

Performance benefitsSafety: Higher data integrity & unambiguous identification

provides better air picture & reduction of effects ofcode/flight plan correlation errors

Capacity: Alleviates Mode A code shortage effects on capacity

Cost-effectiveness: Greater than 10:1 Benefits to cost ratio



Main resource requirements: System upgrade & staff training


ATC05-ASP01 Upgrade ground ATC systems From: 03/2003 By: �ATC05-REG01 Issue AIC and mandate carriage of avionics From: By: 01/2001 �ATC05-REG02 Define certification for Mode S equipment (SI

codes and a/c identification)ACHIEVED

ATC05-REG03 Approve operational procedures forelementary surveillance

From: By: 03/2003 �

ATC05-AGY01 Produce specimen AIC ACHIEVEDATC05-AGY02 Produce operational requirements for

transition to SSR Mode SFrom: By: 06/2002

ATC05-AGY03 Set up European-wide procedures forinterrogator codes (IC) allocation

From: By: 06/2002

ATC05-AGY04 Define operational procedures for use ofelementary surveillance data

From: By: 06/2002

ATC05-AGY05 Define requirements for adaptation of FDPS,RDPS and IFPS to Mode S surveillance.

From: By: 09/2001

ATC05-AGY06 Modify IFPS environment From: By: 03/2003


4-46


ATC05-ASP01 Upgrade ground ATC systemsDefinition: Upgrade ground ATC systems (FDPS, RDPS, IFPS) for processing and displayof Mode S elementary surveillance data; controller trainingApplicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Use by operational ATCof tested & verified upgraded systems


ATC05-REG01 Issue AIC and mandate carriage of avionicsDefinition: Issue AIC and mandate carriage of Mode S elementary surveillance avionicsincluding SI codes and down link of aircraft identity.Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: State AIC issued


ATC05-REG03 Approve operational procedures for elementary surveillanceDefinition: Approve operational procedures for elementary surveillance.Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Availability ofOperational Procedures


ATC05-AGY02 Produce operational requirements for transition to SSR Mode SDefinition: Revise manual on transition to Mode S. Produce operational requirements fortransition to SSR Mode S and associated data processing.Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Availability of transitionmanual


ATC05-AGY03 Set up European-wide procedures for interrogator codes (IC)allocationDefinition: Set up European-wide operational procedures for interrogator codes (IC)allocation.Applicability: States implementing Mode S sensors

Particular criteria to assess the achievement of the Line of Action: Procedures & terms ofreference of a code allocation unit approved by Provisional Council


ATC05-AGY04 Define operational procedures for use of elementary surveillancedataDefinition: Define operational procedures for use of elementary surveillance dataApplicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Availability of revisedprocedures accepted by ANS Ps


ATC05-AGY05 Define requirements for adaptation of FDPS, RDPS and IFPS toMode S surveillanceDefinition: Define operational requirements for adaptation of FDPS, RDPS and IFPS tooperations of Mode S surveillance.Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Availability of thefunctional requirements document


ATC05-AGY06 Modify IFPS environmentDefinition: Modify IFPS environment to take account of Mode S codesApplicability: Participating States

Particular criteria to assess the achievement of the Line of Action: ATC procedures +institutional arrangements in place



4-47

ATC06 Implement ATC air-ground data link services(Phase 1)

Confirmed

Definition:Implement the first set of non-time critical ATC air-ground data link services for basedon the voluntary carriage of data link by aircraft. Implementation will start at airportsand at ACCs from 2003.

Scope:Harmonisation

Applicable area:RO, CZ, IE, GB, FR, ES, CH,DE, NL, BE, AT, SI , IT, CY

SE, PT


Approval reference: Provisional Council - 13/07/2000

Supporting Programme:LINK2000+


7.3.6 and 8.2


Use of AutomatedCommunications toReduce ControllerWorkload

Performance benefitsSafety: Reduction of communication errors and pilot and

controller fatigue

Capacity: Increased capacity through both reduction of voicecongestion and increase in controller efficiency(capacity gain expected is from 3.4% if 25% ofequipped aicraft up to 11% if 75% of equipped aicraft)

Cost-effectiveness: Reduction of flight costs generated by ATM delays, andof Airlines communication costs

Environment: Marginal improvement could be obtained thanks tooptimized flight profile and ATM delay reduction


Main resource requirements: Upgrade of avionics, com infrastructure, FDPS & HMIEquipment for aircraft and ground systems; training of pilots, controllers and technicalstaff


ATC06-USE01 Fit aircraft with air-ground data link equipmentand services and train crews.

From: 12/2002 By: �

ATC06-ASP01 Upgrade ground ATC systems From: 12/2002 By: �ATC06-ASP02 Integrate ATN/VDL-Mode 2 communication

infrastructure to handle air-ground data linkservices

From: 12/2002 By: �

ATC06-ASP03 Train controllers to use air-ground data linkservices

From: 07/2002 By: �

ATC06-REG01 Provide guidance material for the certificationof aircraft and the approval of operations

From: By: 06/2001

ATC06-REG02 Approve the operational use of air-ground datalink services

From: By: 06/2003 �

ATC06-REG03 Amend ICAO documentation on air-grounddata link services

From: By: 12/2001


4-48

ATC06-REG04 Produce industry standards for data linkservices

From: By: 12/2001

ATC06-AGY01 Define and validate the data link services From: 12/2001 By: ATC06-AGY02 Define operational scenario, procedures, HMI,

transition guidelines and training planFrom: By: 06/2002

ATC06-AGY03 Design network and plan capacity From: By: 05/2002ATC06-AGY04 Define safety assessment methodology and

certification planFrom: By: 02/2002

ATC06-SUP01 Provide avionics and ground systems for datalink services

From: 12/2002 By:

ATC06-SUP02 Deploy communication infrastructure to handleair-ground data link services

From: 12/2002


4-49


ATC06-USE01 Fit aircraft with air-ground data link equipment and services andtrain crewsDefinition: Fit aircraft with air-ground data link equipment and services, and obtainoperational approval; train crews.Applicability: Aircraft that will use the services.

Particular criteria to assess the achievement of the Line of Action: 25% of aicraft areequipped

Action by:Airpace UsersFrom: 12/2002By:

ATC06-ASP01 Upgrade ground ATC systemsDefinition: Implement data link equipment and services in their ATC data processing,controller HMI and communication systems. (available from 1/1/2003 at airports and1/1/2005 at ACCs)Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Data link services areimplemented in 10 ACCs/Airports


ATC06-ASP02 Integrate ATN/VDL-Mode 2 communication infrastructure to handleair-ground data link servicesDefinition: Integrate ATN/VDL-Mode 2 communication infrastructure deployed byCommunication service provides with existing communication infrastructure of ATM/CNSproviders. This will be based on a. service level agreements between communicationservice providers and ATM/CNS providers.. (available from 1/1/2003 at airports and1/1/2005 at ACCs)Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: ATN/VDL-Mode 2Infrastructure integrated in 10 ACCs/Airports communication infrastructure


ATC06-ASP03 Train controllers to use air-ground data link servicesDefinition: Train controllers to use air-ground data link services. (starting from 1/7/2002 atairports and 1/7/2004 at ACCs).Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Training achieved


ATC06-REG01 Provide guidance material for the certification of aircraft and theapproval of operationsDefinition: Provide guidance material for the certification of aircraft and the approval ofoperations.Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: 1. Appropriate TGLspublished.

Action by:JAAFrom: By: 06/2001

ATC06-REG02 Approve the operational use of air-ground data link servicesDefinition: Approve the operational use of air/ground data link services to enable ATC tosafely handle aircraft by using air-ground data link services and approve national airspaceusers of operations.Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Operational useapproved


ATC06-REG03 Amend ICAO documentation on air-ground data link servicesDefinition: Amend ICAO documentation on air-ground data link services.Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: ICAO documentationpublisheded



4-50

ATC06-REG04 Produce industry standards for data link servicesDefinition: Produce industry standards for data link services.Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Industry Standardspublished

Action by:EUROCAE, RTCAFrom: By: 12/2001

ATC06-AGY01 Define and validate the data link servicesDefinition: Define and validate the data link services, perform pre-operational tests, assesssafety and cost-efficiency (through PETAL and National Trials)Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Validation reportsavailable

Action by:EATMPFrom: 12/2001By:

ATC06-AGY02 Define operational scenario, procedures, HMI , transition guidelinesand training planDefinition: Define operational scenario, operational procedures and transition guidelinesApplicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Documents available


ATC06-AGY03 Design network and plan capacityDefinition: Co-ordinate the design of the required communication infrastructure networkand plan the communication capacity neededApplicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Commitment frominvolved stakeholders to implement


ATC06-AGY04 Define safety assessment methodology and certification planDefinition: Define the safety assessment methodology and certification planApplicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Methodology and Plansavailable


ATC06- SUP01 Provide avionics and ground systems for data link servicesDefinition: Develop, supply and install, in sufficient quantities, airborne and groundequipment for data link services compliant with RTCA/EUROCAE end-to-endinteroperability, safety and performance specifications.Applicability: Participating States

Particular criteria to assess the achievement of the Line of Action: Equipment available

Action by:AvionicsManufacturersand ATC Systemsand AircraftManufacturersFrom:

By: 02/2002

ATC06- SUP02 Deploy communication infrastructure to handle air-ground data linkservicesDefinition: Deploy ATN/VDL-Mode 2 infrastructure. Prepare service level agreements withATS providers and airspace users. (available from 1/1/2003 at airports and 1/1/2005 atACCs)Applicability: Participating Communication Service providers

Particular criteria to assess the achievement of the Line of Action: ATN/VDL-Mode 2Infrastructure in the 10 ACCs/Airports planning to use the service

Action by:

CommunicationService ProvidersFrom: 12/2002

By:


4-51

ATC07 Implement Arrival Management tools Proposed

Definition:Implement Arrival Manager (AMAN) tools to improve sequencing and metering ofarrival aircraft in selected TMAs and airports.

Scope:Harmonisation

Applicable area:Selected airports and TMAs

(and surrounding ACCs)




Strategic fit:ATM 2000+, Vol.2, para 8.2;ODP Strategy, Vol 2, para.

6.3


Use of automated toolsto support arrivalsmanagement

Performance benefitsSafety: Maintained or improved

Capacity: Improved airport/TMA capacity

Cost-effectiveness: Reduced costs through reduction in delays


Enabler for: Area Navigation Routes Implementation in TMA

Main resource requirements: ATC systems enhancements


ATC07-ASP01 Implement initial arrival management tools From: 12/1998 By: ATC07-ASP02 Define AMAN procedures From: By: 12/2003ATC07-ASP03 Adapt TMA organisation to accommodate use

of AMANFrom: By: 12/2003

ATC07-ASP04 Prepare and adapt ATC systems to supportAMAN functions

From: By: 12/2003

ATC07-REG01 Approve AMAN procedures From: By: 12/2003ATC07-AGY01 Define common AMAN Operational

RequirementsACHIEVED

ATC07-AGY02 Validation, safety assessment and CBA forAMAN

From: By: 12/2003

ATC07-SUP01 Supply AMAN tools From: By: 12/2003


4-52


ATC07-ASP01 Implement initial arrival management toolsDefinition: Implement initial arrival management tools (CIP obj. 5.11.1, pre-AMAN tools).Applicability: High intensity airports/TMAs



ATC07-ASP02 Define AMAN proceduresDefinition: Define, validate and implement ATC procedures for operational use of AMANtools.Applicability: High intensity airports/TMAs

Particular criteria to assess the achievement of the Line of Action: Procedures areimplemented, documented and in operational use


ATC07-ASP03 Adapt TMA organisation to accommodate use of AMANDefinition: Adapt TMA organisation, where necessary, to accommodate the use of AMAN.Applicability: High intensity airports/TMAs

Particular criteria to assess the achievement of the Line of Action: TMA organisation isalready compliant to AMAN use, or has been adapted accordingly.


ATC07-ASP04 Prepare and adapt ATC systems to support AMAN functionsPrepare and adapt ground ATC systems to support AMAN functions.Applicability: high intensity airports/TMAs and surrounding ACCs

Particular criteria to assess the achievement of the Line of Action: ATC systems arealready compliant to AMAN use, or have been adapted accordingly.


ATC07-REG01 Approve AMAN proceduresDefinition: Approve AMAN procedures and amend ICAO documentationApplicability: High intensity airports/TMAs

Particular criteria to assess the achievement of the Line of Action: Formal approval andamended ICAO documentation available, received by Agency


ATC07-AGY02 Validation, safety assessment and CBA for AMANDefinition: Conduct validation, safety assessment and CBA for AMAN requirements.Applicability: High intensity airports/TMAs

Particular criteria to assess the achievement of the Line of Action: Released versions ofvalidation, safety assessment and CBA reports available and circulated to States


ATC07-SUP01 Supply AMAN toolsDefinition: Develop and provide AMAN tools according to common OperationalRequirements and implementable in ground ATC systems)Applicability: High intensity airports/TMAs

Particular criteria to assess the achievement of the Line of Action: AMAN tools areavailable and can be purchased by ANS Providers and Airports.

Action by:ATC SystemsManufacturesFrom: By: 12/2003

ECIP � YEARS 2002 TO 2006 - LEVEL 2 COM02

4-53

COM02 Extension of the use of 8.33 kHz VHFfrequency channels

Agreed

Definition:Horizontal extension of use of 8.33 kHz VHF frequency channels beyond the initial areaand above flight level 245. Retrofit of concerned aircraft is to be completed by 10/2002and the gradual operational use of 8.33 frequencies will span from 10/2002 to 12/2003.

Scope:Harmonisation




Supporting Programme:8.33 kHz Horizontal

Extension Programme

Strategic fit:ATM 2000+, Vol.2 para. 8.2


Airspace structureoptimisation and FUA

Performance benefitsSafety: Not Applicable

Capacity: Enabler for airspace optimisation

Cost-effectiveness: Not Appicable

Environment: Not Applicable

Enabler for: Airspace optimisation

Main resource requirements: Equipment for concerned aircraft; equipment for ANSproviders; training of pilots and controllers


COM02-USE01 Retrofit of aircraft for 8.33 kHz extension From: By: 10/2002COM02-MIL01 Retrofit of military aircraft not exempted From: By: 10/2002COM02-ASP01 Prepare ground ATC systems From: By: 10/2002COM02-ASP02 UHF coverage of 8.33 kHz airspace From: By: 10/2002 �COM02-REG01 Approve regulatory measures and safety

analysis for 8.33 kHzFrom: By: 10/2002 �

COM02-REG02 Publication of official documentation From: By: 10/2002 �COM02-REG03 Issue proposed 25kHz to 8.33 kHz

conversionFrom: By: 05/2000

COM02-AGY01 Update 8.33 Users Guide From: By: 10/2001COM02-AGY02 Implement advanced IFPS message for

8.33 KHzFrom: By: 04/2002

COM02-SUP01 Provide certified 8.33/25kHz mixedenvironment radio systems

By: 08/2002


4-54

COM02 - Detailed Stakeholder Lines of Action Description

COM02-USE01 Retrofit of aircraft for 8.33 kHz extensionDefinition: Retrofit of aircraft and training of staff to ensure 8.33 kHz compliance inextended 8.33 kHz airspace.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Retrofit and trainingachieved

Action by:Airspace UsersFrom:

By: 10/2002

COM02-MIL01 Retrofit of military aircraft not exemptedDefinition: Retrofit of military aircraft not exempted.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Retrofit achieved

Action by:Military AuthoritiesFrom:

By: 10/2002

COM02-ASP01 Prepare ground ATC systemsDefinition: Prepare the ground ATC systems to operate in an 8.33kHz environment..Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Ground systemsupdated to cope with 8.33 frequencies

Action by:ANS ProvidersFrom:

By: 10/2002

COM02-ASP02 UHF coverage of 8.33 kHz airspaceDefinition: UHF coverage of 8.33 airspace.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: UHF coverage available

Action by:ANS ProvidersFrom:By: 10/2002

COM02-REG01 Approve regulatory measures and safety analysis for 8.33 kHzDefinition: Approval of regulatory measures for 8.33 kHz and performance of nationalsafety analysis for 8.33 kHz...Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Regulatory measuresready

Action by:National RegulatoryAuthoritiesFrom:

By: 10/2002

COM02-REG02 Publication of official documentationDefinition: Publication of official documentation relating to 8.33 kHzApplicability: ICAO EUR RegionParticular criteria to assess the achievement of the Line of Action: AIP published


By: 10/2002

COM02-REG03 Issue proposed 25kHz to 8.33 kHz conversionDefinition: The States should have a list of candidate conversions, which can then beassessed by Eurocontrol and coordinated with other States/ICAO as necessary, via normalFMG methods (ad-hoc and block planning)Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Proposed conversionsendorsed by ICAO planning procedures

Action by:

ICAOFrom:

By: 05/2000

COM02-AGY01 Update 8.33 Users guideDefinition: The User�s guide must be updated to take into account the need for horizontalextensionApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Updated User guideavailable

Action by:EATMPFrom:

By: 10/2001

COM02-AGY02 Implement advanced IFPS message for 8.33 kHzDefinition: The IFPS must be updated to be able to process flight plans who will beimpacted by the 8.33 programme extensionApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: IFPS updated

Action by:CFMUFrom:

By: 04/2002


4-55

COM02-SUP01 Provide certified 8.33/25kHz mixed environment radio systemsDefinition: Provide certified 8.33/25kHz mixed environment radio systems (including retrofitkits)Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Equipment available

Action by:IndustryFrom:

By: 08/2002


4-56


ECIP � YEARS 2002 TO 2006 - LEVEL 2 DPS01

4-57

DPS01 Implement Flight Data Processing (FDP) corefunctionality

Confirmed

Definition:Implement Flight Data Processing (FDP) core functionality to attain a comparable levelof operational system performance throughout the ECAC area, including ground-groundcoordination (OLDI).Note: This Objective is the continuation of most former CIP Objectives of the DPS Domain, not achievedyet but confirmed by MATSE 6 (01/2000).

Scope:Harmonisation





Strategic fit:Continuation of Objective 4

of the ECAC Strategy for the90's


Initial automation oftasks

Performance benefitsSafety: Enhanced through reduction of human error

Capacity: Reduction of controller workload

Cost-effectiveness: Supports more efficient planning and operationaldecision making


Enabler for: Implementation of ATC objectives and related procedures

Main resource requirements: System upgrades to implement new functions


DPS01-ASP01 Provide Flight Plan/Track Correlation From: 01/1995 By: DPS01-ASP02 Automatic assignment and management of

SSR codes according to ORCAMFrom: By: 12/1995

DPS01-ASP03 Flight data update From: 01/1995 By: DPS01-ASP04 Flight data distribution From: 01/1995 By: DPS01-ASP05 Internal ATC unit co-ordination From: 01/1995 By: DPS01-ASP06 Route processing From: 01/1995 By: 12/2001DPS01-ASP07 Flight Profile Calculation From: 01/1995 By: DPS01-ASP08 Airspace data processing and distribution From: 01/1995 By: DPS01-ASP09 Met data processing and distribution From: 01/1995 By: DPS01-ASP10 Operational Human Machine Interface From: 01/1995 By: DPS01-ASP11 Configuration Management From: 01/1995 By: DPS01-ASP12 Recording and Replay From: 01/1995 By: DPS01-ASP13 Implement communication support for flight

data exchangeFrom: By: 12/1998 �

DPS01-ASP14 Provide basic co-ordination support within ATCunits

DELETED23

DPS01-ASP15 Provide basic co-ordination support betweenATC units

From: By: 12/1998

DPS01-ASP16 Provide advanced co-ordination supportbetween civil and military ATC units

From: 12/1998 By: �

23 This SLoA is a duplicate of DPS-ASP05 and has been deleted.


4-58

DPS01 - Detailed Stakeholder Lines of Action Description

DPS01-ASP01 Provide flight plan/track correlationDefinition: Implementation of a system which is automatically performing flight plan/trackcorrelation on the basis of correspondence of SSR Mode 3/A code in the track andassigned SSR mode 3/A code in the flight Plan, in addition the route information from theflight plan and the position of the track are taken into account to resolve ambiguoussituations.Applicability: ECAC States



DPS01-ASP02 Automatic assignment and management of SSR codes according toORCAMDefinition: Implement a system which is capable of automatically assigning SSR codes to aflight plans and of performing code management, both according to ORCAM. In addition,optimised code protection rules are applied in order to allow earlier reassignment of codesApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: SSR codes areassigned and managed following ORCAM


DPS01-ASP03 Flight data updateDefinition: Implement a system which is capable of processing flight data updates enteredmanually, or automatically initiating flight data updates through processing of surveillancedata and advanced boundary, activate, revision and preliminary activate messagesreceived from other units.Applicability: ECAC States



DPS01-ASP04 Flight data distributionDefinition: Implement a system which is capable of distributing automatically updated flightdata between ACC, APP, TWR and other subjacent ATC units to meet locally definedoperational needs.Applicability: ECAC States



DPS01-ASP05 Internal ATC unit co-ordinationDefinition: Implement a system which supports internal coordination between sectors;proposals/counter proposals are exchanged by data communication and facilities areprovided for the transfer of communications/ control of flights.Applicability: ECAC States



DPS01-ASP06 Route processingDefinition: The system processes the route information (e.g. from field 15 of the ICAO flightplan). It takes into account general information on published routes, airspace status, etc.,to produce a standard route description. It handles flights on defined ATS routes as well asflights direct from pre-defined point to pre-defined point and from random point to randompoint (including lat/ long and fix radial distance).In addition the system shall have the capability to dynamically re-calculate in real-time anew route, modified by system or controller input.Applicability: ECAC States




4-59

DPS01-ASP07 Flight profile calculationDefinition: Implement a system which performs the flight profile calculation and timeestimation (ETOs) along the route using simple 'aircraft performance' tables. This functionis directly linked with the route processing function. The system will also take into accountsurveillance information, meteorological information, airspace data, ATC operationalconstraints. The process includes the determination of the sector list for the flight.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Function isimplemented, documented and in operational use


DPS01-ASP08 Airspace data processing and distributionDefinition: Implement a system which is able to provide up-to-date, accurate andconsistent aeronautical data (airspace data, sectorisation data, ATM constraints, aircraftperformance data - may include system parameters) to all system functions and operatorsthat require it. An environment data processing and distribution function maintains anddistributes aeronautical data in a suitable format to most system functions and workingpositions as required. It primarily relies on manual inputs, but may provide an automatedinterface with some environment data sources.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Operational use of thefunction


DPS01-ASP09 Met data processing and distributionDefinition: Implement a system which is able to provide up-to-date, accurate andconsistent meteorological data (now and forecasts from international, national and localsources) to all system functions and operators that require it. An environment dataprocessing and distribution function maintains and distributes meteorological data in asuitable format to most system functions and working positions as required. It primarilyrelies on manual inputs, but may provide an automated interface with some environmentdata sources.Applicability: ECAC States



DPS01-ASP10 Operational human machine interfaceDefinition: Implement a system which is capable of presenting to the controller fullsurveillance display data, as defined in the EUROCONTROL Standard for RadarSurveillance in En-route Airspace and Major Terminal Areas. Electronic display of flightplan data, with automatic updates following inputs from controllers of the system. Paperstrips may still be provided.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Function isimplemented, documented and in operational use


DPS01-ASP11 Configuration managementDefinition: Implement a system which is able to be dynamically reconfigured by thesuperviser(s) to cope with traffic demand, failures, maintenance and training requirements.Applicability: ECAC States



DPS01-ASP12 Recording and replayDefinition: All system level operational data which is necessary to accurately reconstruct ahistoric situation exists in electronic form. The system has the ability to perform computer-assisted analysis and replay.Applicability: ECAC States




4-60

DPS01-ASP13 Implement communication support for flight data exchangeDefinition: Implementation of adequate communications to support the automatic exchangeof flight plan data and of coordination data between en-route centres (ACCs) and betweenTMAs and ACCs.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Communicationprocedures are implemented, documented and in operational use


DPS01-ASP15 Provide basic co-ordination support between ATC unitsDefinition: Implementation and operational use of coodination messages between TMAand ACCs, based on the OLDI Standard. ACT and ABI messages are implemented. Othermessages (e.g. PAC, REV, MAC) may be added when bilaterally agreedApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Coordination isimplemented, documented and in operational use


DPS01-ASP16 Provide advanced co-ordination support between civil and militaryATC unitsDefinition: Processing and display of exchanged flight data information between civil andmilitary ATC units and system support for the crossing of areas controlled by civil/militaryunits by flights controlled by military/civil units.Applicability: All (applicable) ACCs, High Complexity TMAs and military ATC units

Particular criteria to assess the achievement of the Line of Action: Coordination isimplemented, documented and in operational use


ECIP � YEARS 2002 TO 2006 - LEVEL 2 FAC01

4-61

FAC01 Implement ATS provision in the UpperAirspace of the Central European (CEATS)

States

Confirmed

Definition:Implement the provision of common ATS in the Upper Airspace of 8 Central EuropeanStates

Scope:Multi-National

Applicable area:AT, BA, HR, CZ, HU, SK, SI,

IT

Timescale:From: 10/2007 (Initialoperation)By: 12/2010 (fulloperation)


Supporting Programme:CEATS

Strategic fit:ATM 2000+ Strategy, Vol.2,

para. 7


Multiple OIs asapplicable


Capacity: Increase through realisation of a unified airspace acrossseveral States

Cost-effectiveness: Infrastructure cost reduced

Environment: Reduced emissions through more efficient airspaceorganisation

Enabler for: This objective is related to, and supports, a number of OperationalImprovements

Main resource requirements: New infrastructure, systems and staff


FAC01-ASP01 Transition to CEATS From: 10/2007 By: 12/2010 �FAC01-ASP02 Start CEATS operations From: 10/2007 By: 12/2010 �FAC01-ASP03 Harmonise investment and operational plans From: 06/2001 By: 12/2010 �FAC01-REG01 Approve delegation of ATS to CEATS UACC From: By: 10/2007 �FAC01-REG02 Amend EUR Regional Plan From: By: 10/2007FAC01-AGY01 Define CEATS operational concept From: By: 10/2005FAC01-AGY02 Develop CEATS infrastructure From: By: 12/2006

ECIP � YEARS 2002 TO 2006 - LEVEL 2 FAC01

4-62

FAC01 - Detailed Stakeholder Lines of Action Description

FAC01-ASP01 Transition to CEATSDefinition: Prepare transition to CEATS ATS provision by defining, developing andimplementing airspace organisation and management changes, operational procedures,letters of agreement and staff requirements and transfer to the CEATS Centre.Applicability: States participating in CEATS

Particular criteria to assess the achievement of the Line of Action:1. Promulgation of transition plan and operating procedures.2. Completion of staff training and transfer

Action by:ANS ProvidersFrom: 10/2007(initial operations)By: 12/2010 (fulloperations)

FAC01-ASP02 Start CEATS operationsDefinition: Complete the human, operational and system transition to CEATS facilities andcommence provision of ATS from the CEATS Centre.Applicability: CEATS States


Action by:ANS ProvidersFrom: 10/2007(initial operations)By: 12/2010 (fulloperations)

FAC01-ASP03 Harmonise investment and operational plansDefinition: harmonise, with the support of EUROCONTROL, investment and operationalplans to achieve early benefits until such time as the CEATS UAC is operationalApplicability: CEATS States

Particular criteria to assess the achievement of the Line of Action: start of operations forCEATS UAC


FAC01-REG01 Approve delegation of ATS to CEATS UACCDefinition: Approve the delegation of specified air traffic services to CEATS UACC andenact any necessary national legislation and regulationApplicability: CEATS States

Particular criteria to assess the achievement of the Line of Action: Formal delegation ofATS by all concerned States


FAC01-REG02 Amend EUR Regional PlanDefinition: Amend the EUR Regional Plan to reflect CEATS UACC operations.Applicability: CEATS StatesParticular criteria to assess the achievement of the Line of Action: EUR Plan amended


FAC01-AGY01 Define CEATS operational conceptDefinition: Define operational requirements; develop and validate CEATS operationalconcept and procedures including HMI.Applicability: CEATS States



FAC01-AGY02 Develop CEATS infrastructureDefinition: Define and monitor the development of CEATS operational and maintenancesystems and infrastructure, including building and servicesApplicability: CEATS States

Particular criteria to assess the achievement of the Line of Action: Adherence to plan


ECIP � YEARS 2002 TO 2006 - LEVEL 2 FCM01

4-63

FCM01 Implement enhanced traffic flowmanagement services

Confirmed

Definition:Implement enhanced tactical flow management services based on the introduction ofreal-time aircraft position and meteorological data to adjust flow regulation.

Scope:Pan European




Supporting Programme:ATFM

Strategic fit:ATM 2000+, Vol.2, para

7.2.2 & 8.2; CFMU Dev. Plan2.0


Enhancement toTactical ATFM - Step 1

Performance benefitsSafety: Reduced unexpected overload situations

Capacity: Reduced wasted capacity; reduced delays

Cost-effectiveness: Reduction of costs induced by delays



Main resource requirements: Additional interface from ANS Providers to CFMU


FCM01-ASP01 Supply ETFMS with basic correlated positiondata

From: 08/2001 By: 12/2004

FCM01-ASP02 Supply ETFMS with Standard CorrelatedPosition Data

From: 08/2001 By: 12/2006

FCM01-ASP03 Receive and process ATFM data from theCFMU

From: 03/1995 By: 12/2001 �

FCM01-ASP04 Inform CFMU of flight activations and estimatesfor ATFM purposes

From: 03/1995 By: 12/1999

FCM01-ASP05 Inform CFMU of flight activations and additionalestimate updates for ATFM purposes

From: 03/2001 By: 12/2006

FCM01-ASP06 Inform CFMU of re-routings inside FDPA forATFM purposes

From: 03/2001 By: 12/2006

FCM01-ASP07 Inform CFMU of aircraft holding for ATFMpurposes

From: 03/2003 By: 12/2006

FCM01-ASP08 Supply CFMU with Departure PlanningInformation (DPI)

From: 12/2002 By:

FCM01-AGY01 Implement ETFMS Phase 1A From: 01/2000 By: 12/2001FCM01-AGY02 Implement ETFMS Phase 1B From: By: 03/2002FCM01-AGY03 Implement ETFMS Phase 1C From: By: 03/2003FCM01-AGY04 Implement ETFMS Phase 2 From: By: 03/2004


4-64

FCM01 - Detailed Stakeholder Lines of Action Description

FCM01-ASP01 Supply ETFMS with basic correlated position dataDefinition: Provide ETFMS with correlated Position Data for all airborne flights inside itsFlight Data Processing Area. For the initial implementation of ETFMS, the CFMU accepts alimited number of existing message formats.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of CPRs byCFMU


FCM01-ASP02 Supply ETFMS with Standard Correlated Position DataDefinition: Provide ETFMS with correlated Position Data for all airborne flights inside itsFlight Data Processing Area in Asterix Category 062 format.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of CPRs inASTERIX Category 062 format by CFMU


FCM01-ASP03 Receive and process ATFM data from the CFMUDefinition: All ATFM messages received from the CFMU are automatically correlated to theATC Flight Plan data. The ATFM data is automatically presented o the Air TrafficControllers (as a minimum to the TWR Controllers) on strips or on electronic displays.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Automatic presentationof the ATFM data correlated to flight data to at least TWR controllers. The SloA can beconsidered as not applicable or completed if the amount of GAT/ IFR traffic does notjustify automation


FCM01-ASP04 Inform CFMU of flight activations and estimates for ATFM purposesDefinition: As evidence of flight activations in the local ATC system, a First Systemactivation (FSA) message is sent to the CFMU. The FSA informs the CFMU of the actualposition of the aircraft (ie: the actual time of departure or the time and flight level at theFDPA entry co-ordination point).Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of FSAmessages by CFMU


FCM01-ASP05 Inform CFMU of flight activations and additional estimate updatesfor ATFM purposesDefinition: Send an FSA message for flights of which the estimated times have beenmodified by more than 5 minutes. This is only required for Flight Data Processing Areas(FDPAs) from which no Correlated Position (surveillance) Data is received.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of FSAmessages by the CFMU for time updates


FCM01-ASP06 Inform CFMU of re-routings inside FDPA for ATFM purposesDefinition: Send an FSA message for flights for a route change which does not affect theexit point and when this information has not already been sent by an AFP message.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of FSAmessages by the CFMU for route changes



4-65

FCM01-ASP07 Inform CFMU of aircraft holding for ATFM purposesDefinition: Send an FSA to inform the CFMU that the flight is holding.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of FSAmessages by the CFMU for holding of flights


FCM01-ASP08 Supply CFMU with Departure Planning Information (DPI)

Definition: Supply the CFMU/ETFMS with flight plan related updates that are only availableshortly before departure. The DPI is used, for example, to supply the CFMU with a moreaccurate Take-Off Time and last minute changes to the flight plan (route) such as, forexample, the SID.Applicability: Airports that can provide DPI data with the required accuracy, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of the DPImessages by CFMU ; No "By-data" is specified because implementation is linked to theimplementation of departure management related procedures and tools which are currentlybeing specified ;


FCM01-AGY01 Implement ETFMS Phase 1ADefinition: Integrate correlated position data in TACT profiles and use it for slot allocation;implement entry node communication; perform operational evaluationApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Reception of firstcorrelated position data on the ETFMS operational system

Action by:CFMUFrom: 01/2000By: 12/2001

FCM01-AGY02 Implement ETFMS Phase 1BDefinition: Integrate METEO data in TACT profile calculation.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Successful installation ofCFMU 8.0 release


FCM01-AGY03 Implement ETFMS Phase 1CDefinition: Improve route extrapolation, additional counts and other improvements.Applicability: ECAC States



FCM01-AGY04 Implement ETFMS Phase 2Definition: Redistribution of ETFMS data to Service Providers. This may include thetransmission of the Flight Update Message (FUM) to ANSPs.

Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Transmission of ETFMSdata by the ETFMS operational system to the first ANSP



4-66



4-67

FCM02 Initial capacity management Agreed

Definition:Improve ATFM pre-tactical planning to support collaboration between the CFMU, AirTraffic Control (ATC) and Flow Management Positions (FMPs).

Scope:Pan European




Supporting Programme:OCM


7.2.3 and 8.2; CFMU Dev.Plan 2.0


Enhancement toTactical ATFM - Step 1

Performance benefitsSafety: No affect

Capacity: Capacity offered is better suited to demand


Environment: No affect

Enabler for: Free routings (extended); optimised flexible sectorisation



FCM02-AGY01 Implement PREDICT system From: By: 05/2000FCM02-AGY02 Give access to the PREDICT system to FMPs From: By: 03/2001FCM02-AGY03 Develop "what-if" functions to optimise capacity

managementFrom: By: 03/2001


4-68


FCM02-AGY01 Implement PREDICT systemDefinition: Improve pre-tactical planning by implementing the dedicated PREDICT system.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Successful installationof the operational PREDICT system


FCM02-AGY02 Give access to the PREDICT system to FMPsDefinition: Improve pre-tactical planning by giving access to the PREDICT systems toFMPs.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: The ability of FMPs toaccess the PREDICT system


FCM02-AGY03 Develop "what-if" functions to optimise capacity managementDefinition: Improve pre-tactical planning by developing what-if functions to optimisecapacity management.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: What-if functionalityavailable



4-69

FCM03 Implement collaborative flight planning Confirmed

Definition:Improve the collaboration between the CFMU, ANS providers, Airports and AirspaceUsers in flight plan filing, in particular to assist Airspace Users in filing their flight plansand in re-routings according to the airspace availability and ATFM situation. Improveflight plan distribution to increase consistency of flight plan data amongst all partiesinvolved (CFMU IFPS/ETFMS, ANS Providers, etc).

Scope:



From: 01/2000By: 12/2005


Supporting Programme:ATFM


7.2.1. and 8.2; CFMU Dev.Plan 2.0


Enhanced Re-RoutingFacilities

Performance benefitsSafety: Prevention of overloads

Capacity: Better use of the available network capacity


Environment: No affect

Enabler for: Improved Air Traffic Flow Management



FCM03-ASP01 Provide flight plan message processing inICAO format

From: 03/1995 By: 12/1995

FCM03-ASP02 Automatically process FPLs derived from RPLs From: 03/1995 By: 12/1995FCM03-ASP03 Provide flight plan message processing in

ADEXP formatFrom: 12/1997 By: 12/2001

FCM03-ASP04 Processing of APL and ACH messages From: 12/1997 By: 12/1999FCM03-ASP05 Provide AFP for missing flight plans From: 03/1998 By: 12/1999FCM03-ASP06 Provide AFP message for change of route From: 03/2002 By: 12/2005FCM03-ASP07 Provide AFP message for a diversion From: 03/2002 By: 12/2005FCM03-ASP08 Provide AFP message for a change of flight

rules or flight typeFrom: 03/2002 By: 12/2005

FCM03-ASP09 Provide AFP message for a change of en-routecruising level

From: 03/2002 By: 12/2005

FCM03-ASP10 Provide AFP messages in ADEXP format From: 03/1998 By: 12/2005FCM03-ASP11 Use IFPLID in all messages to TACT/ETFMS From: 03/2002 By: 12/2006 �

FCM03-ASP12 Use IFPLID in exchange of route-charge data From: 03/2002 By: 12/2006 �

FCM03-ASP13 Provide AFP message for a change of aircrafttype or aircraft equipment

From : 03/2002 By: 12/2005


4-70


FCM03-ASP01 Provide flight plan message processing in ICAO formatDefinition: The ability to receive and automatically process IFPS outputs of all ICAO-defined flight plan messages for input into the local ATC systems This excludes FPLsderived from RPLs (see also FCM03-ASP02).Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Processing of IFPSoutput without manual intervention; The SloA can be considered as not applicable or ascompleted if the amount of GAT/IFR traffic does not justify automation


FCM03-ASP02 Automatically process FPLs derived from RPLsDefinition: The ability to receive and automatically process IFPS derived from RPL tosuppress the need for RPL bulk-output from IFPS.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: No longer requiring RPLbulk-output or transmission of FPLs derived from RPLs by the CFMU ; The SloA can beconsidered as not applicable or as completed if the amount of GAT/IFR traffic does notjustify automation


FCM03-ASP03 Provide flight plan message processing in ADEXP formatDefinition: The ability to receive and automatically process IFPS output of all defined flightplan messages for input into local ATC systems in ADEXP format. This includes FPLsderived from RPL, all ICAO-defined flight plan messages, and APL and ACH messages.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Transmission if IFPSoutput in ADEXP format by the CFMU; The SloA can be considered as not applicable oras completed if the amount of GAT/IFR traffic does not justify automation


FCM03-ASP04 Processing of APL and ACH messagesDefinition: Process automatically, in the local ATC systems, real time updates to flight planinformation as provided by IFPS via APL and ACH messagesApplicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Processing of APL andACH messages by the ANSP; The SloA can be considered as not applicable or ascompleted if the amount of GAT/IFR traffic does not justify automation


FCM03-ASP05 Provide AFP for missing flight plansDefinition: Provide IFPS with updated flight plan information on airborne flights by meansof AFP message. Provide the AFP in case an IFR-GAT flight exists but no IFPL has beenreceived from IFPS.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of AFPmessages by CFMU


FCM03-ASP06 Provide AFP message for change of routeDefinition: Provide IFPS with updated flight plan information on airborne flights by meansof AFP message; provide the AFP in case of a change of route where the exit point fromthe flight data processing area (FDPA) has changed.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Transmission of AFPmessages for route changes by the ANSP



4-71

FCM03-ASP07 Provide AFP message for a diversionDefinition: Provide IFPS with updated flight plan information on airborne flights by meansof AFP message; provide the AFP in case of a diversion.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Transmission of AFPmessges for diversions by the ANSP


FCM03-ASP08 Provide AFP message for a change of flight rules or flight type

Definition: Provide IFPS with updated flight plan information on airborne flights by meansof AFP message; provide the AFP in case of a change of flight rules from VFR to IFR, orIFR to VFR, or a change of flight type from OAT to GAT, or GAT to OAT.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Transmission of AFPmessges for changes of flight rules and flight types by the ANSP


FCM03-ASP09 Provide AFP message for a change of en-route cruising levelDefinition Provide IFPS with updated flight plan information on airborne flights by means ofAFP message. Provide the AFP in case of a change of en-route cruising level (ECL).Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Transmission of AFPmessges for changes of en-route cruising level by the ANSP


FCM03-ASP10 Provide AFP messages in ADEXP formatDefinition: Provide IFPS with updated flight plan information on airborne flights by meansof AFP messages in ADEXP format instead of ICAO format. This is relevant for any triggerevent.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of AFPmessages in ADEXP format by the CFMU


FCM03-ASP11 Use IFPLID in all messages to TACT/ETFMSDefinition: Use the IFPLID as provided by IFPS in all messages to TACT/ETFMS. TheIFPLID shall only be used for system generated/formatted messages. It is not the intentionto enter the IFPLID manually. The use of the IFPLID will simplify the correlation ofincoming flight plan messages with locally stored flight plan data at the CFMU.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of messagesby CFMU/TACT that include the IFPLID ; The SloA can be considered as not applicable oras completed if the amount of GAT/IFR traffic does not justify automation


FCM03-ASP12 Use IFPLID in exchange of route-charge dataDefinition: Use the IFPLID as provided by IFPS in the storage and exchange of route-charge data to the national route-charge offices and between route charge-offices and theCRCO. The use of IFPLID in flight data exchange will simplify the match of archived flightplan data comming from different sources. In the case of the CRCO, the Route-by-State-Overflown (RSO) system matches the CFMU flight plan data with data from the nationalRoute Charges Offices. The use of the IFPLID/EOBD would increase the fully automaticmatching and lead to a more accurate billing and to a reduction in route claims.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Reception of CRCOdata that include the IFPLID by the CRCO ; The SloA can be considered as not applicableor as completed if the amount of GAT/IFR traffic does not justify automation



4-72

FCM03-ASP13 Provide AFP message for change of aircraft type or equipmentDefinition: Provide IFPS with updated Flight Plan information on airbourne flights by meansof AFP message. Provide the AFP in case of a change of aircraft type or aircraftequipment.Applicability: ECAC States, GAT only

Particular criteria to assess the achievement of the Line of Action: Transmission of AFPmessages for changes of aircraft type and aircraft equipment by ANSP


ECIP � YEARS 2002 TO 2006 - LEVEL 2 HUM01

4-73

HUM01 Timely availability of controllers Confirmed

Definition:Plan and provide timely availability of controllers at all units and in all associatedfunctions in order to match the changing requirements of ATM operations, in particularin terms of capacity.

Scope:Harmonisation


Timescale:From: 12/2000By: 12/2007


Supporting Programme:HRS


and Vol 2, para 8.2


Timely availability ofsuitable ATM staff (OI-HUM01)

Performance benefitsSafety: Significant increase through availability of adequate

staff numbers

Capacity: Significant increase through availability of adequatestaff numbers

Cost-effectiveness: Reduction of delays.Improved predictability and reliability of recruitment andtraining costs on medium to long-term but increase insalary related costs.


Enabler for: All objectives

Main resource requirements: Staff resources


HUM01-ASP01 Application of guidelines and tools for controllermanpower planning

From: 02/2000 By: 12/2007 �

HUM01-ASP02 Application of guidelines and tools for staffingand rostering

From: 02/2000 By: 12/2007

HUM01-ASP03 Provision of sufficient number of controllers From: 02/2000 By: 12/2007HUM01-AGY01 Development and provision of advanced

manpower planning methods and toolsFrom: 01/2000 By: 12/2002


4-74

HUM01 � Detailed Stakeholder Lines of Action Description

HUM01-ASP01 Application of guidelines and tools for controller manpowerplanningDefinition: Implementation of best practice guidelines and tools for ATCO manpowerplanning to ensure that the appropriate number of qualified controllers is available at theright time and in all work locations to cover operational requirements and the requirementfor qualified controllers in their functionsApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Effective use ofavailable deliverables or equivalent means of compliance.


HUM01-ASP02 Application of guidelines and tools for staffing and rosteringDefinition: Implementation of best practices and tools for ATCO staffing and rostering toensure that the number of qualified controllers available for day-to-day duties in operationsmeets the operational requirements at all times.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Effective use ofavailable deliverables or equivalent means of compliance.


HUM01-ASP03 Availability of sufficient number of controllersDefinition: Availability of a sufficient number of appropriately trained controllers in all ATCunits and in all functions as appropriate for the provision of ATS.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Appropriate staffinglevel in line with Operational Requirements


HUM01-AGY01 Development and provision of advanced manpower planningmethods and toolsDefinition: Development and provision of advanced strategic and tactical manpowerplanning methods and tools for the current and future ATM system enabling customisedimplementation and application.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Availability ofDeliverables



4-75

HUM02 Implement harmonised selection,recruitment and training of ATM staff

Confirmed

Definition:Improve the recruitment, selection, training and development of staff in order to providesufficient numbers of appropriately skilled people in time, to maintain and enhance thequality of performance in terms of abilities, skills, knowledge and experience and toprepare for harmonised licensing.

Scope:Harmonisation






and Vol 2, para 8.2


Timely availability ofsuitable ATM staff (OI-HUM01)

Performance benefitsCapacity: Advanced recruitment, selection, training and

development methods and tools ensure the timelyavailability of suitable ATM staff in adequate numbers.Advanced training tools contribute to ensure the timelyintroduction of advanced ATM systems

Safety: Harmonised staff profiles, harmonised quality of service,teamwork based safety measures

Cost-effectiveness: Increased effectiveness through advanced selection,training and development tools and methods


Enabler for: All objectives

Main resource requirements:

Stakeholder Lines of Action:HUM02-ASP01 Consider use of First European ATCO

Selection Test packageFrom: 02/2003 By: 12/2007

HUM02-ASP02 Use common Training Syllabi and Plans From: 01/2001 By: 12/2007HUM02-ASP03 Use courseware based on new training

technologyFrom: 01/2001 By: 12/2007

HUM02-ASP04 Use continuation training syllabi and plans From: 07/2001 By: 12/2007HUM02-ASP05 Use common English language tests and

training modulesFrom: 01/2002 By: 12/2007

HUM02-ASP06 Use common training methods From: 10/2000 By: 12/2007HUM02-ASP07 Use advanced methods for personal/career

developmentFrom: 12/2000 By: 12/2007

HUM02-ASP08 Use common Team Resource Managementconcepts, methods and tools

From: 10/2000 By: 12/2007

HUM02-AGY01 First European ATCO Selection Test package From: 01/2000 By: 12/2002HUM02-AGY02 Common Training Syllabi and Plans From: 01/2000 By: 12/2002HUM02-AGY03 Courseware based on new training technology From: 01/2000 By: 12/2002HUM02-AGY04 Continuation Training Syllabi and Plans From: 03/2000 By: 12/2002HUM02-AGY05 English language tests and training modules From: 03/2000 By: 12/2002HUM02-AGY06 Training methods From: 01/2000 By: 12/2002HUM02-AGY07 Methods for personal/career development From: 01/2000 By: 12/2002HUM02-AGY08 Team Resource Management From: 04/2000 By: 12/2002


4-76

HUM02 - Detailed Stakeholder Lines of Action Description

HUM02-ASP01 Consider use of First European ATCO selection test packageDefinition: Consider use of the First European ATCO selection test package which reflectsfuture impacts and enables customised implementation and applicationApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Effective use ofdeliverables or equivalent means of compliance


HUM02-ASP02 Use common training syllabi and plansDefinition: Use common training syllabi and plans in line with current and future ATMpersonnel licensing requirementsApplicability: ECAC States



HUM02-ASP03 Use courseware based on new training technologyDefinition: Use common CBT training components based on validated new trainingtechnologyApplicability: ECAC States



HUM02-ASP04 Use continuation training syllabi and plansDefinition: Use continuation training syllabi and plans for ATM staffApplicability: ECAC States



HUM02-ASP05 Use common English language tests and training modulesDefinition: Use common English language tests and training modules for ATM personnelApplicability: ECAC States



HUM02-ASP06 Use common training methodsDefinition: Use results of customised emerging developments in training techniques fortheir integration in ATMApplicability: ECAC States



HUM02-ASP07 Use advanced methods for personal/career developmentDefinition: Use of advanced concepts, processes and methods for proactive developmentand use of ATM staff potential in the current and future ATM systeApplicability: ECAC States



HUM02-ASP08 Use common Team Resource Management concepts, methods andtoolsDefinition: Use advanced concepts, methods and tools for Team Resource ManagementApplicability: ECAC States




4-77

HUM02-AGY01 First European ATCO selection test packageDefinition: Provision of a European controller selection test package which reflects futureimpacts and enables customised implementation and applicationApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Availability ofdeliverables


HUM02-AGY02 Common training syllabi and plansDefinition: Develop common training syllabi and plans in line with current and future ATMpersonnel licensing requirementsApplicability: ECAC States



HUM02-AGY03 Courseware based on new training technologyDefinition: Develop common CBT training components and validate new trainingtechnologyApplicability: ECAC States



HUM02-AGY04 Continuation training syllabi and plansDefinition: Develop continuation training syllabi and plans for ATM staffApplicability: ECAC States



HUM02-AGY05 English language tests and training modulesDefinition: Develop common promotion of English language training for ATM personneApplicability: ECAC States



HUM02-AGY06 Training methodsDefinition: Test, evaluate and customise emerging developments in training techniques fortheir integration in ATMApplicability: ECAC States



HUM02-AGY07 Methods for personal/career developmentDefinition: Definition and provision of advanced personal and career developmentconcepts, processes and methods for proactive development and use of ATM staffpotential in the current and future ATM systemApplicability: ECAC States



HUM02-AGY08 Team Resource ManagementDefinition: Development of advanced concepts, methods and tools for Team ResourceManagementApplicability: ECAC States




4-78



4-79

HUM03 Implement the full integration of humanfactors into the lifecycle of ATM systems

Proposed

Definition:To develop and use methods, tools and guidance material that enable the integration ofhuman factors in the ATM system lifecycle, and the evaluation of the humancontribution to system performance in the introduction of computer-enhanced ATCsystems.

Scope:



From: 01/2000By: 12/2007



Strategic fit:ATM 2000+, Vol.1 para. 6.6

and Vol 2, para 8.2


Proactive Managementof Human Performance(OI-HUM02)

Performance benefitsSafety: Increased safety through more uniform quality of the

service provided by ATM staff

Capacity: Increases through increased acceptability and use ofevolving technology; and support to design of ATMworking positions, methods and systems to increasetraffic handling capability

Cost-effectiveness: Application of human factors principles to job designcontributes to implementing new ATM systems withinagreed costs and time





HUM03-ASP01 Application of human error managementmethods and tools

From: 06/2000 By: 12/2007

HUM03-ASP02 Human factors integration From: 11/2000 By: 12/2007HUM03-ASP03 Human contribution to system performance From: 10/2001 By: 12/2007HUM03-ASP04 Core requirements for ATM working positions From: 01/2001 By: 12/2007HUM03-AGY01 Human error management methods and tools From: 01/2000 By: 12/2002HUM03-AGY02 Human factors integration From: 01/2000 By: 12/2002HUM03-AGY03 Human contribution to system performance From: 03/2000 By: 12/2002HUM03-AGY04 Core requirements for ATM working positions From: 01/2000 By: 12/2002


4-80

HUM03 � Detailed Stakeholder Lines of Action Description

HUM03-ASP01 Application of human error management methods and toolsDefinition: Use enhanced methods and tools for human error management in ATMApplicability: ECAC States



HUM03-ASP02 Human factors integrationDefinition: Use material on integration of human factors into the ATM system lifecycleApplicability: ECAC States



HUM03-ASP03 Human contribution to system performanceDefinition: Use guidelines for the evaluation of the human contribution to systemperformance in the introduction of computer enhanced ATC systemsApplicability: ECAC States



HUM03-ASP04 Core requirements for ATM working positionsDefinition: Use consolidated requirements on capture, design and evaluation of ATMworking positionsApplicability: ECAC States



HUM03-AGY01 Human error management methods and toolsDefinition: Develop and demonstrate tools for enhanced methods and tools for humanerror management in ATMApplicability: ECAC States



HUM03-AGY02 Human factors integrationDefinition: Develop guidance material for the integration of human factors into the ATMsystem lifecycleApplicability: ECAC States



HUM03-AGY03 Human contribution to system performanceDefinition: Develop guidelines for the evaluation of the human contribution to systemperformance in the introduction of computer enhanced ATC systemsApplicability: ECAC States



HUM03-AGY04 Core requirements for ATM working positionsDefinition: Consolidate and disseminate the requirement capture, design and evaluation ofworking positions for European ATMApplicability: ECAC States



ECIP � YEARS 2002 TO 2006 - LEVEL 2 INF01

4-81

INF01 Implement the European AeronauticalInformation Services (AIS) Database

Confirmed

Definition:Implement and operate a preference data base of quality assured aeronauticalinformation for the ECAC area, and worldwide for the benefit of the aviation community.

Scope:Harmonisation



Approval Reference: Provisional Council - 07/2000

Supporting Programme:EAD

Strategic Fit:ATM 2000+ Vol.2 para.

7.5.1. and 8.2


AeronauticalInformation Services

Performance BenefitsSafety: Improved quality of information to pilots; integrity and

timely availability of the information


Cost-effectiveness: Removal of service duplication



Main resource requirements: Acquisition of central data base system and terminals;implementation of appropriate communication means; adaptation of the local data base


INF01-USE01 Migration of users to EAD From: 04/2003 By: �INF01-ASP01 Migration and transition of States to EAD From: 09/2002 By: �INF01-ASP02 Provision of data to EAD by States From: 12/2002 By: �INF01-AGY01 Provisional acceptance of the EAD System From: 07/1999 By: 03/2003INF01-AGY02 Start of tentative operation of the EAD Service From: 03/2003 By: 05/2003INF01-AGY03 Start of full operation of the EAD Service From: 06/2003 By: 05/2004INF01-SUP01 Develop and implement the EAD System From: 07/1999 By: 04/2004INF01-SUP02 Develop the EAD Service From: 05/2001 By: 05/2003INF01-SUP03 Implement the EAD Service From: 05/2003 By: 05/2004


4-82

INF01 - Detailed Stakeholder Lines of Action Description

INF01-USE01 Migration of users to EADDefinition: Users to become clients of EAD and progressively replace their access toindividual data sources by a single connection to EADApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Monthly rate ofconnections to EAD

Action by:AIS Data UsersFrom: 04/2003By:

INF01-ASP01 Migration and transition of States to EADDefinition: States to migrate in various steps to EAD by re-organising their AIS services tobecome clients of EAD; Step 1: 11 Pilot clients ( 5 National Administrations, 1 Military, 3Internal EC, 2 Commercials); Step 2: 12 Alpha Clients (National Administrations andMilitaries)Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Number of Statesformally registered as EAD Clients


INF01-ASP02 Provision of data to EAD by StatesDefinition: States to ensure the provision of all data necessary to EAD with the adequateformat and quality as part of an operational service. The data to be provided includeNOTAM and AIP data.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Percentage of ECACStates providing EAD with data at required quality level.


INF01-AGY01 Provisional acceptance of the EAD SystemDefinition: Based on the contract specification, the EUROCONTROL Agency will plan andsupervise the provisional acceptance of the EAD SystemApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Successful provisionalacceptance of the EAD System.


INF01-AGY02 Start of tentative operation of the EAD ServiceDefinition: Following provisional acceptance of the EAD System, the EUROCONTROLAgency will start the tentative operation of the EAD Service.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Successful provisionalacceptance of the EAD Service


INF01-AGY03 Start of full operation of the EAD ServiceDefinition: Following final acceptance of the EAD Service, the EUROCONTROL Agencywill start the full operation of the EAD Service.Applicability: ECAC States

333Particular criteria to assess the achievement of the Line of Action: Successful finalacceptance of the EAD Service


INF01-SUP01 Develop and implement the EAD SystemDefinition: Develop and implement the EAD System, including warranty period.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Successful finalacceptance of the EAD System

Action by:Selected SuppliersFrom: 07/1999By: 04/2004


4-83

INF01-SUP02 Develop the EAD ServiceDefinition: Develop the proposed EAD Service.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Successful provisionalacceptance of the EAD Service


INF01-SUP03 Implement the EAD ServiceDefinition: Delivery of the tentative EAD Service in view of final acceptanceApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Successful finalacceptance of the EAD Service



4-84



4-85

INF02 Implement ISO 9001:2000 in AIS Confirmed

Definition:Implement ISO 9000 Quality Management System in Aeronautical Information Servicesand achieve ISO 9001:2000 certification by the end of 2003.ICAO Annex 15 specifies the introduction of a Quality Management System andrecommends the ISO 9000 Series. This ECIP objective specifies the use of the ISO9001:2000 Standard with a target date of 31/12/2003 for all ECAC States.

Scope:

HarmonisationApplicable Area:


From: 06/1999By: 12/2003

Approval Reference: Provisional Council � 07/2001

Supporting Programme:AIS AHEAD

Strategic Fit:ATM 2000+ Vol.1 para 6.5.2,5.2.7 and Vol. 2 para 7.5.1.1


ATM 2000+ Strategyobjective

Performance BenefitsSafety: Improved data control and traceability


Cost-effectiveness: Improved treatment of all processes and avoidance ofambiguities and inconsistencies resulting in improvedservice levels, increased productivity and reliability


Enabler for: Improve Aeronautical Information (INF03); EAD (INF01) and otherobjectives dependent on high quality aeronautical informationMain resource requirements: Implementation of harmonised AIS Static DataProcedures; implementation of ISO Standards and achievement of certification;continuous quality auditing and certification resources


INF02-ASP01 Reference and/or implement SDP in localprocedures

From: 10/2001 By: 12/2003

INF02-ASP02 Implement ISO QMS and achieve certification From: 06/2000 By: 12/2003INF02-AGY01 Develop and provide Awareness campaign From: 06/1999 By: 12/2001INF02-AGY02 Develop and provide AIS Static Data

Procedures (SDP)From: 01/1999 By: 10/2001

INF02-AGY03 Facilitate ISO implementation From: 01/2000 By: 12/2003


4-86

INF02 - Detailed Stakeholder Lines of action Description

INF02-ASP01 Reference and/or implement SDP in States� proceduresDefinition: Reference and/or implement the AIS Static Data procedures in the relevantstates� working proceduresApplicability: : ECAC States

Particular criteria to assess the achievement of the Line of Action: Comparativeassessment of States� procedures against the SDP�s

Action by:States AISFrom: 10/2001By: 12/2003

INF02-ASP02 Implement ISO QMS and achieve certificationDefinition: Implement ISO 9001:2000 Quality Management System and achieve ISOcertification for AIS covering the totality of the integrated aeronautical information packageApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Achieved certification.AIS QA Manager Forum meetings with regular progress reports are applied

Action by:States AISFrom: 06/2000By: 12/2003

INF02-AGY01 Develop and provide Awareness campaignDefinition: Develop and provide an awareness campaign through provision of a series ofworkshopsApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Participation inworkshops will be recorded. Requirements for additional workshops will be addressed viathe AIS QA Managers Forum


INF02-AGY02 Develop Static Data ProceduresDefinition: Develop, deliver and validate harmonised AIS Static Data Procedures (SDP)serving as benchmark/guidance material for implementation in or adaptation of States�working proceduresApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: The set of draft SDPdeveloped by the SDP Task Force are validated by ECAC States.


INF02-AGY03 Facilitation of ISO implementationDefinition: Develop and provide facilitation of ISO implementation by continuing andrepeating the workshops as required and setting up the AIS QA Managers Forum toprovide focus for facilitation activitiesApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: AIS QA Manager Forummeetings with regular structured progress reporting



4-87

INF03 Implement Improved AeronauticalInformation

Proposed

Definition:

Improve Aeronautical Information in terms of integrity, timeliness and data contentassisted by electronic publication and dissemination of data and the implementation ofstandardised service levels.

Scope:Harmonisation



Approval Reference: Provisional Council � 07/2001

Supporting Programme:AIS AHEAD

Strategic Fit:ATM 2000+ Vol.1 para 6.5.2

and Vol. 2 para 7.5.1


ATM 2000+ Strategyobjective

Performance BenefitsSafety: Improved consistency, reliability and integrity

Capacity: On-time delivery of correct aeronautical informationensures timely implementation of overall capacityenhancements

Cost-effectiveness: Avoidance of repair, correction and re-work activities atdata provider and data user level


Enabler for: All objectives dependent on timely, reliable and consistent aeronauticalinformation

Main resource requirements: A combination of Agency's development costs and Stateimplementation costs

Stakeholder Lines of Action:INF03-ASP01 Implement the Data Integrity Tool (DIT) From: 10/2003 By: 12/2004INF03-ASP02 Adhere to AIRAC rules and guidance material From: 06/2000 By: 12/2004INF03-ASP03 Implement data content guidelines From: 09/2003 By: 12/2004INF03-ASP04 Implement and provide the eAIP From: 03/2002 By: 12/2004INF03-ASP05 Assess AIS against the performance criteria

and improve AIS Service LevelsFrom: 03/2002 By: 12/2004

INF03-REG01 Enforce the conformance to AIRAC From: 06/2000 By:INF03-AGY01 Develop a Data Integrity Tool (DIT) From: 12/2000 By: 10/2003INF03-AGY02 Develop DIT implementation guidance material From: 07/2002 By: 10/2003INF03-AGY03 Develop AIRAC Awareness campaign and

guidance materialFrom: 06/2000 By: 10/2001

INF03-AGY04 Develop data content guidelines From: 06/2000 By: 09/2003INF03-AGY05 Develop a specification and guidance material

for implementation of an eAIPFrom: 06/2000 By: 03/2002

INF03-AGY06 Develop a concept and performance criteria forstandardised AIS Service Levels

From: 06/2000 By: 03/2002

INF03-AGY07 Develop a framework to measure developmentand implementation progress

From: 06/2000 By: 12/2004


4-88

INF03 - Detailed Stakeholder Lines of action Description

INF03- ASP01 Implement the Data Integrity Tool (DIT)Definition: Implement the Data Integrity Tool and reference/implement the guidancematerial in local working procedures.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Regular overallmonitoring to be based on progress through the lifecycle and the number of Statesachieving implementation.

Action by:StatesFrom: 10/2003By: 12/2004

INF03- ASP02 Adhere to AIRAC rules and guidance materialDefinition: Adhere to AIRAC rules and guidance material.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Regular overallmonitoring to be based on progress through the lifecycle and the number of Statesachieving implementation.


INF03- ASP03 Implement data content guidelinesDefinition: Implement data content guidelines and reference them in local workingprocedures.Applicability: ECAC States



INF03- ASP04 Implement and provide the eAIPDefinition: Implement and provide an electronic AIP based on specification and guidancematerial.Applicability: ECAC States



INF03- ASP05 Assess AIS against the performance criteria for AIS Service LevelsDefinition: Assess AIS against the performance criteria and improve AIS according thestandardised Service Levels.Applicability: ECAC States



INF03- REG01 Enforce the conformance to AIRACDefinition: Enforce conformance of all involved stakeholders to AIRAC rules and publishedguidance material.Applicability: ECAC States


Action by:States RegulatorFrom: 06/2000By:

INF03-AGY01 Develop a Data Integrity Tool (DIT)Definition: Develop a data integrity tool (DIT).Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: By deliverable



4-89

INF03-AGY02 Develop DIT implementation guidance materialDefinition: Develop DIT implementation guidance material and prepare support materialfollowing a pilot study phase to support the implementation in States. Perform DIT pilotclient study and installation. Specify the software distribution concept.Applicability: ECAC States



INF03- AGY03 Develop AIRAC Awareness campaign and guidance materialDefinition: Develop an AIRAC awareness campaign and guidance material for advanceduse of publication procedures and information technology.

Action by:EATMP

Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: By deliverableFrom: 06/2000By: 10/2001

INF03- AGY04 Develop data content guidelinesDefinition: Develop data content guidelines to improve the data content.Applicability: ECAC States



INF03- AGY05 Develop specification and guidance material for implementation ofan eAIPDefinition: Develop a specification and guidance material for implementation andapplication of an electronic AIP.Applicability: ECAC States



INF03- AGY06 Develop a concept and performance criteria for standardised AISDefinition: Develop a concept and performance criteria for standardised AIS ServiceLevels.Applicability: ECAC States



INF03- AGY07 Develop a framework to measure development and implementationDefinition: Develop a framework to measure development and implementation progressper SloA.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Regular reporting perSloA is applied



4-90


ECIP � YEARS 2002 TO 2006 - LEVEL 2 MIS01

4-91

MIS01 Improve the management and optimise theoperational use of the aeronauticalfrequency assignments in allocated radiobands

Confirmed

Definition:Improve the management and optimise the operational use of the aeronauticalfrequency assignments in radio bands allocated to aviation to enable improvements toATS and implementation of ECIP objectives conditioned by availability of radiofrequency resource.

Scope:Pan European






7.7.3


No OI assigned

Performance benefitsSafety: Not applicable

Capacity: Poor management, short term planning andoperationally underused frequencies, lack of audit offrequency operational use at national level result ininefficient use of the aeronautical spectrum at Europeanlevel. This constitutes a capacity barriers in the shortterm and the long term

Cost-effectiveness: Improved through management of scarce and criticalspectrum resource


Enabler for: CNS infrastructure objectives

Main resource requirements: Additional human resources from State regulators (forAviation Frequency management and regulation activities at national level and forcoordination and study activities at international level)


MIS01-REG01 Implement the currently available and improvedfrequency management mechanisms and tools

From: 01/2001 By: 12/2005 �

MIS01-AGY01 Define, for VHF Com band, mechanisms and toolsto improve frequency management and to optimiseoperational use of frequency assignments

ACHIEVED

MIS01-AGY02 Define improved and centralised mechanisms andtools to improve frequency management and tooptimise operational use of frequency assignmentsfor all aviation bands

From: By: 06/2002


4-92

MIS01 - Detailed Stakeholder Lines of Action Description

MIS01-REG01 Implement the currently available and improved frequencymanagement mechanisms and toolsDefinition: Implement and use the currently available and improved frequencymanagement mechanisms and toolsApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Compliance to tools andprocedures verified by the EUROCONTROL Agency

Action by:National RegulatoryAuthoritiesFrom: 01/2001

By: 12/2005

MIS01-AGY02 Define improved and centralised mechanisms and tools to improvefrequency management and to optimise operational use offrequency assignments for all aviation bandsDefinition: Define improved and centralised mechanisms and tools to improve frequencymanagement and to optimise operational use of frequency assignments and prepare adeployment plan for the ECAC area for all aviation bandsApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Document endorsed byProvisional Council

Action by:

EATMPFrom: By: 06/2002


4-93

MIS02 Implement contingency planning andprocedures

Confirmed

Definition:Implement contingency planning and procedures to cope with disruptions to theprovision of Air Traffic Services (ATS). This reflects the ATM2000+ principle forairspace users to have maximum operational freedom and services of adequate qualityand nature.

Scope:



From: 12/1999By: 12/2000



Strategic fit:ATM 2000+, Vol.1 para.

4.2.4


No OI assigned


Capacity: Increase through reduction of effects of disruptions

Cost-effectiveness: Savings in reduction of delays





MIS02-ASP01 Develop and implement contingency planningand procedures for technical failures

From: By: 12/2000

MIS02-ASP02 Develop and implement ATS contingencyplanning and procedures for industrial action

From: By: 12/2000

MIS02-REG01 Enact regulation for application of contingencyplans

From: By: 12/2000

MIS02-AGY01 Define a common policy, planning templateand guidelines for contingency plans

From: By: 10/2000


4-94

MIS02 - Detailed Stakeholder Lines of Action Description

MIS02-ASP01 Develop and implement contingency planning and procedures fortechnical failuresDefinition: Develop national plan for implementation of a common methodology for ATSContingency planning and procedures for major technical failures in part of the ATMsystem (En-route, TMA, airports)Applicability: All ACCs, TMAs and Airports at which ATS Services are providedParticular criteria to assess the achievement of the Line of Action: Promulgation of nationalplan


By: 12/2000

MIS02-ASP02 Develop and implement ATS contingency planning and proceduresfor industrial actionDefinition: Develop national plan for implementation of a common methodology for ATSContingency planning and procedures for industrial action in part of the ATM system (En-route, TMA, airports)Applicability: All ACCs, TMAs and Airports at which ATS Services are providedParticular criteria to assess the achievement of the Line of Action: Promulgation of nationalplan


By: 12/2000

MIS02-REG01 Enact regulation for application of contingency plansDefinition: Define, develop and enact regulation for application of contingency plansApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: To be defined


By: 12/2000

MIS02-AGY01 Define a common policy, planning template and guidelines forcontingency plansDefinition: Define a common policy for contingency planning and application, and developa template for contingency plans together with guidelines for their developmentApplicability: All ACCs, TMAs and Airports at which ATS Services are providedParticular criteria to assess the achievement of the Line of Action: Promulgation oftemplate and guidelines

Action by:EATMPCFMUFrom:

By: 10/2000

ECIP � YEARS 2002 TO 2006 - LEVEL 2 NAV01

4-95

NAV01 Assure Satellite-Based augmentationsystems (SBAS) navigation service for

aviation needs

Proposed

Definition:Realise the conditions to enable safe and cost-effective use of SBAS navigation servicefor aviation needs in ECAC, addressing all phases of flight down to and includingCategory I precision approach. Provide and maintain more flexible and efficient flightprocedures in terminal areas (SID/STAR) as well as instrument approaches (NPA, APV-I, APV II, CAT I) in ECAC in a harmonised manner within the corresponding CNS/ATMenvironment.

Scope:



From: By: 01/2005


Supporting Programme:GNSS

Strategic fit:MATSE/4 decisions; ATM

2000+ Vol. 2, para 8.2;Navigation Strategy para

5.12, TPINS para13


No OI assigned

Performance benefitsSafety: Contributes to harmonisation of safety policy and

procedures, and enables precision approach capabilityat most runway-ends in Europe

Capacity: Enables increase in flights able to follow preferredtrajectories

Cost-effectiveness: Contributes to rationalisation of the navigationinfrastructure

Environment: Reduces fuel burn which in turn will help to reduceemissions (particularly NOx) through a reduction in flighttime because of improved navigation accuracy, andreduces in noise pollution by avoiding noise-sensitiveareas

Enabler for: Navigation applications, airspace design improvements



NAV01-USE01 Fit aircraft with SBAS From: 01/2004 By: �NAV01-REG01 Approve standards for SBAS From: 01/2000 By: 03/2003NAV01-REG02 Define common certification and operational

approval criteria for SBAS airborne equipmentFrom: 08/2000 By: 06/2002

NAV01-REG03 Certify aircraft for SBAS operation From: 03/2003 By: �NAV01-AGY01 Real-time SAPPHIRE performance monitoring From: 01/2002 By: 12/2003NAV01-AGY02 SBAS safety assessments From: 07/1999 By: 06/2004NAV01-AGY03 SBAS operational validation From: 01/2000 By: 10/2004NAV01-AGY04 SBAS business case ACHIEVEDNAV01-AGY05 Develop operational procedures and standards

for SBASFrom: 01/2000 By: 01/2005


4-96

NAV01-SUP01 Provide airborne equipment and retrofit kits forSBAS

From: 04/2003 By: 01/2005

NAV01-SUP02 Implementation of SBAS infrastructure From: 11/2003 By: 09/2004


4-97

NAV01 - Detailed Stakeholder Lines of Action Description

NAV01-USE01 Fit aircraft with SBASDefinition: Fit aircraft with SBAS capability for use of corresponding advantagesApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Number of aircraftequipped will guide deployment. The availability and implementation of the Multi-ModeReceiver are critical. JAA Guidance on Airworthiness and Approval Criteria will berequired. In particular, the development of TGL material for RNAV systems using inputsfrom GPS augmented by SBAS is vital

Action by:Airspace UsersFrom: 01/2004

By:

NAV01-REG01 Approve standards for SBASDefinition: Approve standards for SBAS.1. ICAO SARPs: Fall 20012. Upgraded MOPS:December 20023. JAA TGL-Cat. 1: March 2003Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Availability of Standards

Action by:ICAO, JAA,EUROCAEFrom: 01/2000

By: 03/2003

NAV01-REG02 Define common certification and operational approval criteria forSBAS airborne equipmentDefinition: Define common certification criteria for SBAS airborne equipmentApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Availability of Notice ofProposed Amendment (NPA) and subsequent modifications to existing Joint AviationRequirements (JAR)

Action by:

JAAFrom: 08/2000

By: 06/2002

NAV01-REG03 Certify aircraft for SBAS airborne operationDefinition: Certify SBAS airborne equipment and where appropriate provide operationalapprovalApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Percentage of aircraftwith SBAS Approval

Action by:

National RegulatoryAuthoritiesFrom: 03/2003

By:

NAV01-AGY01 Real-time SAPPHIRE performance monitoringDefinition: Provide SAPPHIRE (Satellite and Aircraft Database Project for System IntegrityResearch) data analysis tool to States for harmonised assessment of long termperformance of SBAS and for research into key contributors to performance. This could bescaled down with the provision of the prototype processing tool called PEGASUSApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Number of ATM/CNS providers using SAPPHIRE/PEGASUS2. Number and quality of research results and their influence on regulations

Action by:EATMPFrom: 01/2002

By: 12/2003

NAV01-AGY02 SBAS safety assessmentsDefinition:1. Support the EOIG to develop the SBAS Safety Case and Guidance Material for theimplementation of the SBAS Safety Case into National ATS Safety Regulation (07/99 to06/04)2. Provide a harmonised approach to operational approval throughout ECACApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Deliverable available.However SBAS Safety Case requires the output from the operational validation activities


By: 06/2004


4-98

NAV01-AGY03 SBAS operational validationDefinition: SBAS operational demonstration and validation using ground and flight testing(by 10/2004). Early trials programme to be carried out using the SBAS System TestBed(s)Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: To be defined.However, factors external to SBAS, such as availability of high integrity databases andsophisticated Flight Management Systems may jeopardise the operational validation


By: 10/2004

NAV01-AGY05 Develop operational procedures and standards for SBASDefinition: Contribute to the development of relevant material for the design procedures(flight, flight inspection), to the definition of AIS requirements for GNSS and to thedevelopment of guidance material for ATCApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Deliverables available.However, not under the direct control of the Agency (e.g. OCP)


By: 01/2005

NAV01-SUP01 Provide airborne equipment and retrofit kits for SBASDefinition: Provide, in sufficient quantities, certified airborne equipment and retrofit kits forSBASApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: To be defined

Action by:

AvionicsManufacturersFrom: 04/2003

By: 01/2005

NAV01-SUP02 Implementation of SBAS infrastructureDefinition: Implementation of SBAS infrastructureApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Full infrastructurerequired for aviation in place. Depends on the date SBAS system will be ready for hand-over to the SBAS operating bodies.

Action by:

ESA, EuropeanCommission andEOIG StatesFrom: 11/2003

By: 09/2004


4-99

NAV02 Assure GBAS Cat. I-based precisionapproach service for aviation needs

Proposed

Definition:To enable European civil aviation to proceed with a robust, safe and cost-effectiveGBAS operational implementation to support CAT-I precision approach operations.

Scope:



From: 01/2004By:


Supporting Programme:GNSS

Strategic fit:ATM 2000+ Vol. 2, para 8.2;

Navigation Strategy para5.12, TPINS para 13


No OI assigned

Performance benefitsSafety: Contributes to harmonisation of safety policy and

procedures (uniformity), and permits aircraft to fly to lowDH/DA and land in low visibility conditions

Capacity: Supports increased capacity level and operationalefficiency during low visibility conditions. Enables Cat. Icapability and to maintain the capability where ILS-supported operations cannot be maintained due to ILSlimitations (VHF interference, multi-path)

Cost-effectiveness: Contributes to rationalisation of the navigationinfrastructure


Enabler for: Navigation applications, airspace design improvements


Stakeholder Lines of Action:NAV02-USE01 Fit aircraft with GBAS From: 04/2003 By: �NAV02-ASP01 Implement GBAS Category I infrastructure From: 04/2003 By: �NAV02-ASP02 Design and implement Category I approach

proceduresFrom: 10/2002 By: �

NAV02-APO01 Implement GBAS Cat.I infrastructure From: 04/2003 By: �NAV02-REG01 Approve standards for GBAS From: 01/2000 By: 03/2003NAV02-REG02 Define common certification criteria for GBAS

airborne equipmentFrom: 01/2001 By: 06/2002

NAV02-REG03 Certify GBAS airborne equipment From: 03/2003 By: NAV02-REG04 Enact regulation for GBAS operational

proceduresFrom: By: 03/2003 �

NAV02-REG05 Approve use of GBAS equipment From: By: 03/2003 �NAV02-AGY01 Real-time performance monitoring From: 12/2002 By: NAV02-AGY02 GBAS safety assessments From: 01/2001 By: 12/2003NAV02-AGY03 GBAS operational validation From: 01/2001 By: 12/2003NAV02-AGY04 GBAS business case From: By: 03/2003NAV02-AGY05 Develop operational procedures and standards

for GBASFrom: 01/2001 By: 10/2002

NAV02-AGY06 Identify operational needs for GBAS. From: 01/2001 By: 06/2001NAV02-SUP01 Provide airborne equipment and retrofit kits From: 04/2003 By: NAV02-SUP02 Provide GBAS equipment From: 04/2003 By:


4-100


NAV02- USE01 Fit aircraft with GBASDefinition: Fit aircraft with GBAS Cat. I capability for use of corresponding advantagesApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Number of aircraftequipped will guide deployment of GBAS. Due to the interoperability between Region andStates, the ultimate need for a Multi-Mode Receiver should be acknowledged.

Action by:Airspace UsersFrom: 04/2003

By:

NAV02- ASP01 Implement GBAS Cat. I infrastructureDefinition: Implement GBAS Cat.I infrastructure where economically and safety beneficialApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Number of airportsequipped as indicator of deployment range. SLoA AGY-04 should acknowledge the needfor an harmonised implementation.

Action by:ANS ProvidersFrom: 04/2003

By:

NAV02- ASP02 Design and implement Category I approach proceduresDefinition: To adapt current procedure design guidance material to the use of GBAS bytaking GBAS specific advantages (e.g. �linear� error characteristic) into consideration, andto estimate possible contribution of GBAS to procedures other than Precision Approach.To be done where economically and safety beneficial.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Procedures arepublished in AIP. Depends on activities that are conducted within the ICAO ObstacleClearance Panel (OCP) in order to provide criteria for the design of flight procedures.

Action by:ANS ProvidersFrom: 10/2002

By:

NAV02-APO01 Implement GBAS Cat.1 infrastructureDefinition: Implement GBAS Cat.1 infrastructure where economically and safety beneficial.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Number of airportsequipped as indicator of deployment range. SLoA AGY-04 should acknowledge the needfor an harmonised implementation.

Action by:Airport ATM ServiceProvidersFrom: 04/2003

By:

NAV02- REG01 Approve standards for GBASDefinition: Approve standards for GBAS Cat.1.1. ICAO SARPs: Fall 20012. Upgraded MOPS: December 20023. JAA TGL-Cat. 1: March 2003Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Availability of Standards

Action by:ICAO, JAA,EUROCAEFrom: 01/2000

By: 03/2003

NAV02- REG02 Define common certification criteria for GBAS airborne equipmentDefinition: Define common certification criteria for GBAS Cat. 1 airborne equipmentApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Availability of Notice ofProposed Amendment (NPA) and subsequent modifications to existing Joint AviationRequirements (JAR)

Action by:

JAAFrom: 01/2001

By: 06/2002

NAV02- REG03 Certify GBAS airborne equipmentDefinition: Certify GBAS Cat. 1 airborne equipmentApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Percentage of aircraftwith GBAS Approval

Action by:

National RegulatoryAuthoritiesFrom: 03/2003

By:


4-101

NAV02- REG04 Enact regulation for GBAS operational proceduresDefinition: Enact regulation for GBAS cat. I operational proceduresApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: To be defined

Action by:

National RegulatoryAuthoritiesFrom:

By: 03/2003

NAV02- REG05 Approve use of GBAS equipmentDefinition: Approve use of GBAS Cat. 1 equipment following successful check of theinstallations, performance and environment.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: To be defined

Action by:

National RegulatoryAuthoritiesFrom:

By: 03/2003NAV02- AGY01 Real-time performance monitoring

Definition: Provide data analysis tool to States for harmonised assessment of long termperformance of GBAS Cat. 1 (e.g. collision risk modelling) and for research into keycontributors to performanceApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:1. Number of ATM/CNS providers using data analysis tools.2. Number and quality of research results and their influence on regulations.


By:

NAV02- AGY02 GBAS safety assessmentsDefinition: Demonstrate GBAS safety by producing safety assessments for GBAS Cat.1.The Safety Assessment shall comply with the EUROCONTROL Safety RegulatoryRequirements (ESARRs) and will apply the guidelines contained in the EATMP AirNavigation System Safety Assessment Methodology. It will in particular provide anApproval Plan that will be the basis for the initial agreements between GBAS ServiceProviders and the regulatory authorities.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Deliverables availableand recommendations from the Safety Regulation Commission (SRC) passed on toNational Regulatory Authorities.


By: 12/2003

NAV02- AGY03 GBAS operational validationDefinition: To validate that reliable operations can be achieved under varying operationalenvironment and over extended periods of time. To propose suitable validationprocedures for the operational validation of the use of GBAS for Cat. 1 precisionapproaches.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: To be defined.However, the use of a GBAS Test Bed will be critical to the successful completion of thetask and the lack of availability of GBAS receivers approved for carriage on commercialaircraft would delay a significant portion of the Test Bed same valid for the availability ofapprovable ground stations.


By: 12/2003

NAV02- AGY04 GBAS business caseDefinition: Support Air Navigation Service Providers and Airport Authorities indemonstrating that the business case for the introduction of GBAS Cat. 1 benefits bothservice providers and airspace users.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Deliverables available.

Action by:EATMPFrom:

By: 03/2003


4-102

NAV02- AGY05 Develop operational procedures and standards for GBASDefinition: Contribute to the development of relevant material for the design procedures(flight, flight inspection), to the definition of AIS requirements for GNSS and to thedevelopment of guidance material for ATC.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Deliverables available.However, not under the direct control of the Agency (e.g. ICAO OCP)


By: 10/2002

NAV02- AGY06 Identify operational needs for GBASDefinition: To ensure that airspace users and air navigation service providers reachagreement on the operational need for GBAS Cat. 1 in line with more efficient operationsand reduction in costs.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: To be defined


By: 06/2001

NAV02- SUP01 Provide airborne equipment and retrofit kitsDefinition: Provide, in sufficient quantities, certified airborne equipment and retrofit kits forGBAS Cat. 1Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: To be defined

Action by:

AvionicsManufacturersFrom: 04/2003

By:

NAV02- SUP02 Provide GBAS equipmentDefinition: Provide, in sufficient quantities, GBAS Cat. 1 equipment compliant withstandards and performance requirementsApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: To be defined

Action by:

Ground SystemManufacturersFrom: 04/2003

By:


4-103

NAV03 Implementation of Precision RNAV (P-RNAV)as an interim towards RNP RNAV Agreed

Definition:

Implement P-RNAV procedures, designed in accordance with the EUROCONTROLGuidance material, to capitalise on the high performance of RNAV equipped aircraft,approved in accordance with JAA TGL 10, and derive operational benefit whilstenhancing system capacity.This is an interim objective towards the Navigation Strategy's target, - a global RNAVenvironment based on the RNP concept and the decommissioning of point sourcenavigation aids - which will require to use RNAV equipment meeting RNP RNAV .The present navigation requirement, carriage of BRNAV, does not fully supportoperations based on RNAV procedures in Terminal Airspace due to the limitedfunctionality of the simpler systems used to meet the requirement. However, manyaircraft provide a far greater capability and certification and operational approvalmaterial for Precision RNAV system (P-RNAV) have been developed by JAA (TGL 10)to enable the benefits to be derived from such systems.Since this is an interim objective, those operators who need to re-equip their aircraft tomeet the P-RNAV requirements are encouraged to fit RNP RNAV equipment that willenable them to proceed through this interim stage into the full RNAV implementation.

Scope:



From: 01/2001By: Phasedimplementation

Approval Reference: PC07 � 07/2001

Supporting Programme:NAV

Strategic fitATM 2000+ Vol. 2, para 8.2;Navigation Strategy para 5.2

and 5.10


Airspace Structure

Performance benefitsSafety: Increase safety of flight operations by increased

situational awareness and indirect benefit to both ATCand pilot through reduction of workload during RNAVoperations

Capacity: Indirect benefit by enabling optimisation of en-route andterminal airspace

Cost-effectiveness: Fuel cost reduction through optimised routes and TMAprocedures

Environment: Emissions and noise nuisance reduced by use ofoptimal flight procedures and routings

Enabler for: Airspace design improvements



4-104


NAV03-USE01 Where operators wish to upgrade their RNAVcapability they are encouraged to equip theiraircraft with systems that have an RNP -RNAVcapability to ensure long term benefits areobtained.

From: 01/2001 By: 12/2010 �

NAV03-USE02 Train aircrews in RNAV TMA procedures From: 01/2001 By: 01/2005 �

NAV03-USE03 Ensure correctness of data before use From: 01/2001 By: 01/2005 �

NAV03-ASP01 Develop and implement RNAV arrival anddeparture procedures

From: 01/2001 By: 01/2005 �

NAV03-ASP02 Provide appropriate terrestrial navigationinfrastructure to support RNAV operations

From: 01/2001 By: 01/2005 �

NAV03-ASP03 Train Air Traffic Controllers in RNAVprocedures From: 01/2001 By: 01/2003 �

NAV03-ASP04 Train procedure designers in RNAV capabilities From: 01/2001 By: 01/2003 �

NAV03-ASP05 Implement P-RNAV routes where identified asproviding benefit

From: 01/2001 By: 01/2005 �

NAV03-ASP06 Publish in AIPS all co-ordinate data in WGS-84to accuracy and integrity specified in Annex 15

From: 01/2001 By: 01/2005 �

NAV03-ASP07 Define all RNAV procedures to be for P-RNAVapproved aircraft and designed in accordancewith the EUROCONTROL guidelines and ICAOPANS OPS

From: 03/2002 By: 03/2003 �

NAV03-REG01 Ensure suppliers of navigation databases areaccredited

From: 01/ 2001 By: 01/2005

NAV03-REG02 Ensure quality of published Navigation Data From: 01/2001 By: 01/2005NAV03-AGY01 Identify applicability of P-RNAV routes to en-

route applicationsFrom: 01/2001 By: 01/2003

NAV03-AGY02 Investigate the requirements for additional R/Tphraseology and Flight Planning Methodologyfor RNAV operations in Terminal Airspace anddevelop as necessary

From: 06/2001 By: 01/2002

NAV03-AGY03 Produce and maintain guidelines for theapplication and design of RNAV procedures

Initial VersionComplete

Update asnecessary to2010

NAV03-SUP01 Ensure that data is meets specification of ED77 and is managed according to ED76.

From: 01/2001 By: 01/2005

NAV03-SUP02 Ensure that the Navigation Database cannot becorrupted when installed

From: 01/2001 By: 01/2005


4-105


NAV03-USE01 Where operators wish to upgrade their RNAV capability they areencouraged to equip their aircraft with systems that have an RNPRNAV capability to ensure long term benefits are obtainedDefinition: New aircraft can be equipped for RNP- RNAV, however, older types which areequipped with a B-RNAV capability may not meet the requirements for P-RNAV (JAATGL10). Operators who wish to upgrade should consider equipping with RNP - RNAVsystems to ensure the long-term benefits are obtained, and not upgrade to P-RNAVcapabilityApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: All civil transport aircraftoperating in ECAC states are capable of P-RNAV operations


NAV03-USE02 Train aircrews in RNAV TMA proceduresDefinition: Aircrew need to be trained in the application of RNAV TMA proceduresApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Pilots trained in theapplication of RNAV procedures


NAV03-USE03 Ensure correctness of data before useDefinition: Aircraft operators must ensure correctness of data before useApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Correctness checked byAirspace Users


NAV03-ASP01 Develop and implement RNAV arrival and departure proceduresDefinition: RNAV arrival and departure procedures, and Continuous Descent Approachesoffer potential operational and environmental benefits, and enhance safetyApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: All RNAV arrivals anddepartures implemented in ECAC states in accordance with EUROCONTROL GuidanceMaterial for the design of terminal procedures and requiring system performance inaccordance with JAA TGL 10


NAV03-ASP02 Provide appropriate terrestrial navigation infrastructure to supportRNAV operationsDefinition: P-RNAV can be achieved using basic GNSS (i.e. standalone GPS withoutground or space based augmentations with Receiver Autonmous Integrity monitoring(RAIM) and possibly also with Inertial Augmentation) or DME/DME modes of navigation.However, RNAV procedures are dependent upon sufficient DME transponders beingdistributed geographically to allow for DME/DME navigation in the absence of onboardGNSS equipment or GNSS failure. This requirement may mean new DME stations and/orthe relocation of existing stations.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Infrastructure assessedand modified if required to meet the requirements for DME/DME procedures


NAV03-ASP03 Train Air Traffic Controllers in RNAV proceduresDefinition: RNAV procedures could reduce the need for radar vectors up to the FAP. ATCneed to be trained in RNAV capabilities and new methods of managing TMA traffic toensure safe and expeditious operationsApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: The necessary traininggiven to controllers responsible for the operation of RNAV terminal Procedures



4-106

NAV03-ASP04 Train procedure designers in RNAV capabilitiesDefinition: RNAV procedures require a more comprehensive understanding of aircraftperformance, database coding, and certification. Tools have been developed to help theprocedure designer in his/her task. Training is necessary to ensure the procedure designis safe and executable by the onboard systems.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: The necessary traininggiven to procedure designers responsible for the design of RNAV terminal Procedures


NAV03-ASP05 Implement P-RNAV routes where identified as providing benefitDefinition: States will implement P-RNAV routes where such implementation on can bedemonstrated to provide additional capacity and where the implementation of such routescan be identified as operationally acceptableApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: P- RNAV routesimplemented in ECAC states in accordance with criteria developed under NAV03-AGY 1below


NAV03-ASP06 Publish in AIPs all co-ordinate data in WGS-84 in accordance withICAO Annex 15 requirementsDefinition: It is an essential requirement for RNAV procedures that all co-ordinate datapublished in AIPs, e.g. Runway Thresholds, Navigation Aids, Waypoints, etc., aresurveyed with reference to the WGS84 standard. Following survey which must beundertaken in accordance with the Eurocontrol standard for WGS 84 survey (EurocontrolStandard 006), the data must be maintained with adequate integrityApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: AIPS updatedaccordingly


NAV03-ASP07 Define all RNAV procedures to be for P-RNAV approved aircraftand designed in accordance with the EUROCONTROL guidelinesand ICAO PANS OPSDefinition: RNAV procedures must be designed in accordance with ICAO PANS OPS andamplified in the EUROCONTROL guidelinesApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: RNAV proceduresdesigned in accordance with EUROCONTROL guidelines and ICAO PANS OPS


NAV03-REG01 Ensure suppliers of navigation databases are accreditedDefinition: Navigation databases should only be available from accredited suppliers withsuitable quality assurance procedures in placeApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Suppliers are accredited

Action by:RegulatorsFrom: 01/2001By: 01/2005

NAV03-REG02 Ensure quality of published Navigation DataDefinition: Ensure quality of published Navigation DataApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Quality checked byregulators

Action by:RegulatorsFrom: 01/2001By: 01/2005


4-107

NAV03-AGY01 Identify applicability of P-RNAV routes to en-route applicationsDefinition: The main motivation for P-RNAV application will be the need to provide RNAVoperations in terminal airspace. The Agency will evaluate the operational benefits of usingP-RNAV in the en-route environment and TMA/en-route interfaceApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Guidance material of theimplementation of P-RNAV routes developed and approved

Action by:EurocontrolFrom: 01/2001By: 01/2003

NAV03-AGY02 Investigate the requirements for additional R/T phraseology andFlight Planning Methodology for RNAV operations in TerminalAirspace and develop as necessaryDefinition: New RNAV procedures for arrival and departure will require an investigation ofexisting R/T phraseology to ensure safe and efficient communicationsApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: RNAV arrivals anddepartures implemented in ECAC states

Action by:EurocontrolFrom: 06/2001By: 01/2002

NAV03-AGY03 Produce and maintain guidelines for the application and design ofRNAV proceduresDefinition: Guidelines for the application and design of RNAV procedures must beproduced and maintainedApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Guidelines available

Action by:EurocontrolFrom: Update asrequired until 2010

NAV03- SUP01 Ensure that data meets specification of ED77 and is managedaccording to ED76Definition: Database suppliers must ensure that data is encoded in accordance with ED76and ED77Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Conformance to ED76and ED77 verified

Action by:Suppliers IndustryFrom: 01/2001By: 01/2005

NAV03- SUP02 Ensure that the Navigation Database is not corrupted wheninstalledDefinition: Ensure that the Navigation Database is not corrupted when installedApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: FMS navigationdatabase is correct and cannot be modified

Action by:Suppliers IndustryFrom: 01/2001By: 01/2005


4-108



4-109

NAV04 Implement approach procedures using RNAVwith vertical guidance (ICAO APV I)

Agreed

Definition:The majority of Controlled Flight into Terrain (CFIT) accidents occur during non-precision approaches where step-down descents are in operation (dive and drive).APVI as defined by ICAO provides criteria for procedure designers to design approachprocedures using the LNAV capabilities provided by RNAV (Basic GNSS ( ie: GPS withairborne augmentation such as RAIM and AAIM), SBAS or DME/DME), and stabiliseddescent profiles using Baro-VNAV.

These criteria need to be introduced with a high priority to reduce the number of CFIToccurrences, and to provide safe approach procedures in mountainous terrain. With thepotential for lower minima APV I will provide economic advantages.

Note: The ICAO OCP has developed criteria for APV I approach design based on RNAV/VNAV approachcriteria and is moving towards development of near CAT-I Precision Approach criteria. At present there is areview being undertaken as to the operational requirements for APV II. This review requires input from bothICAO GNSSP and OCP and once the issue has been clarified work on APV II will be included in this CIPobjective. Criteria for precision approaches using GBAS are under development and the work of NAV04 willbe extended to link the provision of service under NAV01 to the operational application in the terms of APVII once OCP has developed the associated procedure criteria.

Scope:Harmonisation



Approval Reference: PC07 � 07/2001

Supporting Programme:NAV

Strategic fit:ATM 2000+ Vol. 2, para 8.2;Navigation Strategy para 5.2

and 5.10


Airport Capacity

Performance benefitsSafety: Reduction in CFIT occurrences

Capacity: Optimised use of terminal airspace

Cost-effectiveness: Fuel cost reduction through optimised TMA procedures.Lower operational minima for runways without precisionguidance facilities

Environment: Emissions and noise nuisance reduced by use ofoptimal flight procedures and routings

Enabler for: Airspace design improvements

Main resource requirements: Training of aircrews and procedure designers


4-110


NAV04-USE01 Train aircrew in APV1 procedures From 01/2001 By: 01/ 2005 � NAV04-USE02 Ensure correctness of data before use From: 01/2001 By: 01/2005 � NAV04-ASP01 Develop & Implement RNAV approaches with

vertical guidance (APV1) proceduresFrom: 01/2001 By: 01/2005 �


From: 01/2001 By: 01/2005 �

NAV04-ASP03 Train Air Traffic Controllers in RNAV andContinuous Descent procedures

From: 01/2001 By: 01/2005 �

NAV04-ASP04 Train procedure designers in RNAVprocedures

From: 01/2001 By: 01/2005 �

NAV04-ASP05 Publish in AIPs all co-ordinate data in WGS-84in accordance with ICAO Annex 15

From: 01/2001 By: 01/ 2005 �

NAV04-ASP06 Design APV procedures in accordance withICAO PANS OPS as elaborated in theEUROCONTROL guidelines

From: 01/2001 By: 01/2005 �

NAV04-REG01 Develop and Issue TGL for APV1 Operations From : 01/2001 By: 06/2001NAV04-REG02 Ensure suppliers of navigation databases are

accreditedFrom: 01/2001 By: 01/2005

NAV04-AGY01 Develop Guidance Material for implementationof APV

From: 01/2001 By: 01/2002


From: 01/2001 By: 01/ 2005

NAV04-SUP01 Ensure that data is encoded in accordance withED76 and ED77

From: 01/2001 By: 01/2005

NAV04-SUP02 Ensure that the Navigation Database is notcorrupted when installed

From: 01/ 2001 By: 01/2005


4-111


NAV04-USE01 Train aircrews in APV1 proceduresDefinition: Aircrew need to be trained in the application of APV1 proceduresApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Training provided toAircrew

Action by:Airspace Users

From: 01/2001By: 01/2005

NAV04-USE02 Ensure correctness of data before useDefinition: Aircraft operators must ensure correctness of data before useApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Correctness checked byAirspace Users

Action by:Airspace Users

From: 01/2001By: 01/2005

NAV04-ASP01 Develop & Implement RNAV approaches with vertical guidance(APV1) proceduresDefinition: ICAO PANS-OPS have developed criteria for APV1 operations using RNAV(DME/DME, basic GNSS (stand alone GPS with RAIM and possibly also inertialaugmentation) as well as SBAS) aided by Baro-VNAV to provide descent profiles to enablestabilised approaches in a NPA environment. RNAV Approach Procedures have to bedeveloped to these criteria and then implemented to enhance safety.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: APV Proceduresimplemented in ECAC states in accordance with Guidance material


NAV04-ASP02 Provide appropriate terrestrial navigation infrastructure to supportRNAV operationsDefinition: RNAV approaches can be achieved using basic GNSS (see above), SBAS orDME/DME modes of navigation. However, RNAV procedures are dependent uponsufficient DME transponders being distributed in a manner that optimises accuracy toenable DME/DME navigation in the absence of onboard GNSS equipment or in the eventof GNSS failure. This requirement may mean new DME stations and/or the relocation ofexisting stations.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Infrastructure modifiedto enable APV Procedures to be implemented in ECAC states


NAV04-ASP03 Train Air Traffic Controllers in RNAV and continuous descentproceduresDefinition: RNAV procedures reduce the need for radar vectors up to the FAP. ATC needto be trained in RNAV capabilities and new methods of managing TMA traffic to ensuresafe and expeditious operationsApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Controllers trained in theapplication of APV1


NAV04-ASP04 Train procedure designers in RNAV proceduresDefinition: APV1 procedures require a more comprehensive understanding of aircraftperformance, database coding, and certification. Tools have been developed to help theprocedure designer in his/her task. Training is necessary to ensure the procedure designis safe and executable by the onboard systems.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Procedure designerstrained in the application of APV procedures in accordance with guidance material



4-112

NAV04-ASP05 Publish in AIPS all co-ordinate data in WGS-84 in accordance withICAO Annex 15Definition: It is an essential requirement for RNAV procedures that all co-ordinate datapublished in AIPs, e.g. Runway Thresholds, Navigation Aids, Waypoints, etc., aresurveyed with reference to the WGS84 standardApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: AIPS updatedaccordingly

Action by:

ANS ProvidersFrom: 01/2001By: 01/2005

NAV04-ASP06 Design APV procedures in accordance with the EUROCONTROLguidelines and ICAO PANS OPSDefinition: APV procedures must be designed in accordance with the EUROCONTROLguidelines and ICAO PANS OPSApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: RNAV proceduresdesigned in accordance with EUROCONTROL guidelines and ICOA PANS OPS

Action by:

ANS ProvidersFrom: 01/2001By: 01/2005

NAV04-REG01 Develop and Issue TGL for APV1 OperationsDefinition: JAA to develop and issue TGLApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: TGL approved forapplication

Action by:

Regulatory Bodies

From: 01/2001By: 06/2001

NAV04-REG02 Ensure suppliers of navigation databases are accreditedDefinition: Navigation databases should only be available from accredited suppliers withsuitable quality assurance procedures in placeApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Suppliers are accredited

Action by:

Regulators

From: 01/2001By: 01/2005

NAV04-AGY01 Develop Guidance Material for implementation of APVDefinition: Development of Guidance material to be used by ATM/CNS service providersand users in the definition of the concept of operations and in the provision of training andimplementation of APV procedures.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Guidance Materialapproved for application

Action by:

EUROCONTROLAgency

From: 01/2001By: 01/2002

NAV04-AGY02 Produce and maintain guidelines for the application and design ofRNAV proceduresDefinition: Guidelines for the application and design of RNAV procedures must beproduced and maintainedApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Guidelines available

Action by:

EUROCONTROLAgency

From: 01/2001By: 01/2005

NAV04-SUP01 Ensure correctness of data before useDefinition: Database suppliers must ensure that data is encoded in accordance with ED76and ED77Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action:Conformance to ED76 and ED77 verified

Action by:

Suppliers Industry

From: 01/2001By: 01/2005

NAV04-SUP02 Ensure that the Navigation Database is not corrupted wheninstalledDefinition: FMS providers must ensure that the Navigation Database is not corrupted wheninstalledApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: FMS navigationdatabase is correct

Action by:

Suppliers Industry

From: 01/2001By: 01/2005

ECIP � YEARS 2002 TO 2006 - LEVEL 2 SAF01

4-113

SAF01 Implement a Safety Management System forATM Service Providers Confirmed

Definition:Implement a Safety Management System which meets as a minimum ICAO provisionand EUROCONTROL Safety Regulatory Requirements.

Scope:Pan-European

Applicable area:All ECAC States


Approval reference: Provisional Council � 07/2001

Supporting Programme:Support for ESARR3

Implementation

Strategic fit:ATM 2000+ Strategy,

Volume 2 (Objective 4.2)


Contributes to ATM2000+ Strategy Safetyobjectives

Performance benefitsSafety: The use of systematic safety management is expected

to contribute to safety improvement. Safetymanagement aims to ensure that all safety issues in theprovision of ATM Services are properly addressed andmanaged




Enabler for: Implementation of ESARR 3 on the Use of Safety Management Systemsby ATM Service Providers. SAF01 provides one possible way to comply with ESARR 3

Main resource requirements: Dedicated staff


SAF01-ASP01 Establish or update the Organisation Safety Policy From: 01/2001 By: 08/2001 �SAF01-ASP02 Establish an action plan for implementing the Safety

PolicyFrom: 06/2001 By: 12/2001 �

SAF01-ASP03 Implement the policy principles From: 01/2002 By: 07/2003 �SAF01-AGY01 Update the EATMP Safety Policy according to

ESARR 3From: 02/2001 By 06/2001

SAF01-AGY02 Provide guidance to perform a survey on currentsafety management processes

From: 06/2001 By: 10/2001

SAF01-AGY03 Develop additional guidance material on new EATMPSafety Policy principles

From: 08/2001 By 12/2002

ECIP � YEARS 2002 TO 2006 - LEVEL 2 SAF01

4-114

SAF01 - Detailed Stakeholder Lines of Action Description

SAF01-ASP01 Establish or update the organisation Safety PolicyDefinition:1. Develop organisation's Safety Policy2. Approve the organisation's Safety Policy3. Communicate the Safety Policy to all personnelApplicability: All ECAC States.

Particular criteria to assess the achievement of the Line of Action: Availability of a releasedorganisation safety policy

Action by:ATM ServiceProvidersFrom: 01/2001By: 08/2001

SAF01-ASP02 Establish an action plan for implementing the Safety PolicyDefinition :1. Conduct a survey of current Safety Management practices2. Analyse the survey results and set priorities for implementation3. Develop the organisation's Action Plan for the implementation of Safety ManagementApplicability: All ECAC States.

Particular criteria to assess the achievement of the Line of Action: Availability of anImplementation Plan


SAF01-ASP03 Implement the policy principlesDefinition:1. Develop individual procedure for the implementation of each principle2. Train personnel responsible for their implementation3. Communicate the procedure implementationApplicability: All ECAC States.

Particular criteria to assess the achievement of the Line of Action: Availability of a SafetyManual


SAF01-AGY01 Update the EATMP Safety Policy according to ESARR 3Definition:1. Update EATMP Safety Policy to integrate ESARR3 elements2. Review the updated Safety Policy with the Safety Group3. Have the updated Safety Policy approved by the CEO Standing ConferenceApplicability: All ECAC States.

Particular criteria to assess the achievement of the Line of Action: Availability of anapproved EATMP Safety Policy


SAF01-AGY02 Provide guidance to perform a survey on current safetymanagement processesDefinition:1. Update existing guidance material for the survey of existing practices2. Review the updated guidance material with the Safety GroupApplicability: All ECAC States.

Particular criteria to assess the achievement of the Line of Action: Availability of guidancematerial


SAF01-AGY03 Develop additional guidance material on new EATMP Safety PolicyprinciplesDefinition:1. Review existing guidance material and identify areas of improvement2. Develop additional guidance material for the following principles: risk management,

safety surveys, external services, safety records3. Review new guidance material with the Safety GroupApplicability: All ECAC States.

Particular criteria to assess the achievement of the Line of Action: Availability of additionalguidance material


ECIP � YEARS 2002 TO 2006 - LEVEL 2 SRC02

4-115

SRC02 Implement ESARR 2 on Reporting andAnalysis of safety occurrences in ATM

Confirmed

Definition:Implement the safety regulatory requirements laid down in EUROCONTROL SafetyRegulatory Requirements � �Reporting and Analysis of safety occurrences in ATM� -ESARR 2, for all States (including organisations and personnel involved in the reportingand analysis of ATM related safety occurrences in ATM) across the ECAC area.

Scope:Pan European



Approval reference: EUROCONTROL Permanent Commission Decision24

No 80/12.11.1999

Supporting Programme:ESARR 2 Implementation

(SRC) Programme

Strategic fit:ATM 2000+ Strategy Volume

2 (4.2.1, 4.2.2, 4.2.4. and4.2.5)


Contributes to ATM2000+ Strategy SafetyObjectives

Performance benefitsSafety: The application of EUROCONTROL safety regulatory

requirements in the area of �Reporting and Analysis ofsafety occurrences in ATM� will lead to a moresystematic visibility of safety occurrences and theircauses, and will allow identification of appropriatecorrective actions as well as areas where flight safetycould be improved by changes to the ATM system




Enabler for: Application of ESARR 3

Main resource requirements: National ATM Safety Regulators, National AircraftAccident Investigators, ATM Service Providers and airlines flying in the ECAC airspace


SRC02-REG01 Identify/Set-up national institutionalarrangements to implement ESARR 2

From: 11/1999 By: 11/2000 �

SRC02-REG02 Assess national regulations vs. ESARR 2 From: 11/1999 By: 11/2001 �SRC02-REG03 Document and address the differences identified

in SRC02-REG02From: 11/1999 By: 12/2001 �

SRC02-REG04 Draft new regulation to set-up the ESARR 2national framework

From: 11/1999 By: 11/2001 �

SRC02-REG05 Publish new regulation compliant with ESARR 2 From: 11/2001 By: 12/2001 �SRC02-REG06 Notify differences to ICAO From: 12/2001 By: 01/2002 �SRC02-REG07 Implement ESARR 2 Requirements for Accidents

and ATM incidents with risk of Collision (Phase 1)From: 11/1999 By: 01/2000 �

24 Decision 80 of EUROCONTROL Permanent Commission has approved the introduction of ESARR 2 within the nationalregulatory framework


4-116

SRC02-REG08 Implement ESARR 2 Requirements for ATMincidents with potential for risk of Collision

From: 11/1999 By: 01/2001 �

SRC02-REG09 Implement ESARR 2 Requirements for ATMspecific occurrences (Phase 3)

From: 11/1999 By: 01/2002 �

SRC02-REG10 Implement the mechanism to verify compliancewith new/modified regulations

From: 11/1999 By: 01/2001 �

SRC02-REG11 Verify that new regulation is applied From 01/2001 By 01/2002 �


4-117

SRC02 - Detailed Stakeholder Lines of Action Description

SRC02-REG01 Identify/Set-up national institutional arrangements to implementESARR 2Definition: In order to implement ESARR 2, appropriate national institutional arrangementsare to be identified/set-up. Part of this process will be allocated to identify theresponsibilities within State and part to identify the appropriate legislation to beused/changed or adapted.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action:1. Existence of a legislation allowing ESARR 2 enactment at national level2. Existence of a legislation ensuring �non punitive � environment

Action by:National RegulatoryAuthoritiesFrom: 11/1999By: 11/2001

SRC02-REG02 Assess national regulations vs. ESARR 2Definition: Perform comparison between the ESARR 2 requirements and the appropriatenational regulations. This comparison shall address:- existing national requirements bearing on providers of ATM Services vs. ESARR 2

requirements (and associated GM1/2-ESARR 4)- existing national requirements bearing on Aircraft accident investigators vs. ESARR 2

requirements (and associated GM1/2-ESARR 4)- existing national requirements bearing on Airlines flying in the national airspace vs.

ESARR 2 requirements (and associated GM1/2-ESARR 4).Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Notification ofdifferences to ESARR 2

Action by:National RegulatoryAuthoritiesAircraft AccidentInvestigatorsFrom: 11/1999By: 11/2001

SRC02-REG03 Document and address the differences identified in SRC02-REG02Definition: Differences detected during the assessment performed in SRC-2-REG02 haveto be documented, addressed and corrective measures are to be envisaged in order toensure compliance with ESARR2Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: New national set ofdraft regulatory requirements in the area covered by ESARR 2


SRC02-REG04 Draft new regulation to set-up the ESARR 2 national frameworkDefinition: Following consultation with industry, national regulator shall draft the newnational regulation, compliant with ESARR 2Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: New national nationalregulation in the area covered by ESARR 2


SRC02-REG05 Publish new regulation compliant with ESARR 2Definition: Following a period of conversion between old and new regulation, the newnational requirements compliant with ESARR 2 shall be published.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Official promulgation ofthe new regulation


SRC02-REG06 Notify differences to ICAODefinition: Notify to ICAO those differences from ICAO SARPS � Annexes 13 and 11 �following ESARR 2 implementationApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Letter to ICAO



4-118

SRC02-REG07 Implement ESARR 2 Requirements for accidents and ATM incidentswith risk of Collision (Phase 1)Definition: Implement Requirements to be applied as they are laid down in therequirements of ESARR 2 section 5.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action:1. Internal sets of procedures to report and analyse safety occurrences in ATM2. Aeronautical Information Publication.

Action by:National RegulatoryAuthoritiesATM ServiceProvidersAircraft AccidentInvestigatorsFrom: 11/1999By: 01/2000

SRC02-REG08 Implement ESARR 2 Requirements for ATM incidents with potentialfor risk of Collision (Phase 2)Definition: Implement Requirements to be applied by providers and users of ATM Servicesas they are laid down in the requirements of ESARR 2 section 5.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action:1. Internal sets of procedures to report and analyse safety occurrences in ATM2. Aeronautical Information Publication.


SRC02-REG09 Implement ESARR 2 Requirements for ATM specific occurrences(Phase 3)Definition: Implement Requirements for Aircraft Accident Investigators to be applied asthey are laid down in the requirements of ESARR 2 section 5.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action:1. Internal sets of procedures to report and analyse safety occurrences in ATM2. Aeronautical Information Publication


SRC02-REG10 Implement the mechanism to verify compliance with new/modifiedregulationsDefinition: National Regulatory Authorities shall implement the mechanism allowing toverify compliance with the new/modified regulations.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Set of auditingprocedures and trained staff


SRC02-REG11 Verify that new regulation is appliedDefinition: Implement the oversight function to verify if new regulation is appliedApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Audit reports, regulatorystatements on acceptability of proposed changes to the ATM System, as well as existenceof corrective measures.



4-119

SRC03 Implement ESARR 3 on the use of SafetyManagement Systems by ATM Service

Providers

Confirmed

Definition:Implement the safety regulatory requirements laid down in EUROCONTROL SafetyRegulatory Requirements � Use of Safety Management Systems by ATM ServiceProviders - ESARR 3, in order to ensure that all safety issues within the provision ofATM services are addressed by ATM Service Providers in a satisfactory mannerthrough the use of safety management systems.

Scope:Pan European




No 84/13.07.2000


(SRC) Programme

Strategic fit:ATM 2000+ Strategy,

Volume 2 (Objective 4.2)


Contributes to ATM2000+ Strategy safetyobjectives


requirements in the area of Safety ManagementSystems aims to ultimately ensure that all safety issueswithin the provision of an ATM service are addressed byATM Service Providers in a satisfactory manner, and toa satisfactory conclusion, through the use of systematicsafety management





Main resource requirements: National ATM Safety Regulators, ATM ServiceProviders including all stakeholders in the provision and use of such Service


SRC03-ASP01 Implement ESARR 3 requirements From: 07/2000 By: 07/2003 �SRC03-REG01 Identify/Set-up national institutional arrangements to

implement ESARR 3From: 07/2000 By: 10/2001 �

SRC03-REG02 Assess national regulations vs. ESARR 3 From: 07/2000 By: 10/2001 �SRC03-REG03 Document and address the differences identified in

SRC03-REG02From:10/2001 By: 01/2002 �

SRC03-REG04 Draft new regulation to set-up the ESARR 3 nationalframework

From: 07/2000 By: 12/2002 �

SRC03-REG05 Publish new regulation compliant with ESARR 3 From: 10/2001 By: 12/2002 �

25 Decision 84 of EUROCONTROL Permanent Commission has approved the introduction of ESARR 3 within the nationalregulatory framework


4-120

SRC03-REG06 Notify differences to ICAO From: 12/2002 By: 07/2003 �SRC03-REG07 Implement the mechanism to verify compliance with

new/modified regulationsFrom: 07/2000 By: 01/2003 �

SRC03-REG08 Verify that new regulation is applied From: 01/2003 By: 07/2003 �


4-121


SRC03-ASP01 Implement ESARR 3 RequirementsDefinition: Implement Requirements as they are laid down in ESARR 3 section 5 andrelated appendices.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: The implementation andeffective operation, within the service-provider�s organisation, of procedures andorganisational arrangements forming a complete safety management system that coversthe minimum features defined by ESARR 3


SRC03-REG01 Identify/Set-up national institutional arrangements to implementESARR 3Definition: In order to implement ESARR 3, appropriate national institutional arrangementsare to be identified/set-up. Part of this process will be allocated to identify the respon-sibilities within State and part to identify the appropriate legislation to be used/changed oradapted.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Existence of alegislation allowing ESARR 3 enactment at national level.


SRC03-REG02 Assess national regulations vs. ESARR 3Definition: Perform comparison between the ESARR 3 requirements and the appropriatenational regulations. This comparison shall address: Existing requirements vs. ESARR 3requirementsApplicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Notification ofdifferences to ESARR 3


SRC03-REG03 Document and address the differences identified in SRC03-REG02Definition: Differences detected during the assessment performed in SRC03-REG02 haveto be documented, addressed and corrective measures are to be envisaged in order toensure compliance with ESARR3Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: New national set of draftregulatory requirements in the area covered by ESARR 3



Particular criteria to assess the achievement of the Line of Action: New national regulationin the area covered by ESARR 3 requiring service-providers to implement and operateSafety Management Systems in accordance with ESARR 3


SRC03-REG05 Publish new regulation compliant with ESARR 3Definition: Following a period of conversion between old and new regulation, the newnational requirements compliant with ESARR 3 shall be published.Applicability: ECAC StatesParticular criteria to assess the achievement of the Line of Action: Official promulgation ofthe new regulation



4-122

SRC03-REG06 Notify differences to ICAODefinition: Notify to ICAO those differences from ICAO SARPS � Annex 11 � Air TrafficServices - following ESARR 3 implementationApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action:Letter to ICAO


SRC03-REG07 Implement the mechanism to verify compliance with new/modifiedregulationsDefinition: National Regulatory Authorities shall implement the mechanisms and resourcesto verify compliance with the new/modified regulations.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Set of auditingprocedures, availability of human and material resources to verify compliance, staffappropriately trained to verify compliance.


SRC03-REG08 Verify that new regulation is appliedDefinition: Implement the oversight function to verify if new regulation is appliedApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Audit reports, regulatorystatements on the acceptability of safety management systems implemented by service-providers to meet the requirements, documentation of evidence and findings on whichthose statements are based, existence of corrective measures and their systematic followup.



4-123

SRC04 Implement ESARR 4 on Risk Assessmentand Mitigation in ATM

Confirmed

Definition:Implement the safety regulatory requirements laid down in EUROCONTROL SafetyRegulatory Requirements � Risk Assessment and Mitigation in ATM - ESARR 4 - fororganisations planning changes to the ATM System to assess and control the safetyimpact that those proposed changes may have on aviation safety.

Scope:Pan European




No 87/05.04.2001


(SRC) Programme


2 (4.2.1, 4.2.2, 4.2.4. and4.2.5)


Contributes to ATM2000+ Strategy SafetyObjectives


requirements in the area of ATM Risk Assessment andMitigation aims to ultimately ensures that the risksassociated with hazards in the ATM System aresystematically and formally identified, assessed andmanaged within safety levels, which as a minimum, meetthose approved by the appropriate safety regulatory body





Main resource requirements: National ATM Safety Regulators, ATM ServiceProviders including all stakeholders in the provision and use of such Service

Stakeholder Lines of Action:SRC04-ASP01 Implement ESARR 4 requirements From: 04/2001 By: 04/2004 �SRC04-REG01 Identify/Set-up national institutional

arrangements to implement ESARR 4From: 04/2001 By: 02/2002 �


in SRC04-REG02From: 02/2002 By: 05/2002 �


From: 04/2001 By: 05/2003 �

SRC04-REG05 Publish new regulation compliant with ESARR 4 From: 04/2002 By: 05/2003 �SRC04-REG06 Notify differences to ICAO From: 05/2003 By: 04/2004 �SRC04-REG07 Implement the mechanism to verify compliance

with new/modified regulationsFrom: 04/2001 By: 09/2003 �


26 Decision 87 of EUROCONTROL Permanent Commission approved the introduction of ESARR 4 within the national regulatoryframework


4-124


SRC04-ASP01 Implement ESARR 4 RequirementsDefinition: Implement Requirements as they are laid down in ESARR 4 section 5 andrelated appendices.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Internal set ofprocedures to conduct Risk Assessment and Mitigation



Particular criteria to assess the achievement of the Line of Action: Existence of alegislation allowing ESARR 4 enactment at national level.


SRC04-REG02 Assess national regulations vs. ESARR 4Definition: Perform comparison between the ESARR 4 requirements and the appropriatenational regulations. This comparison shall address: Existing requirements vs. ESARR 4requirementsApplicability: ECAC States



SRC04-REG03 Document and address the differences identified in SRC04-REG02Definition: Differences detected during the assessment performed in SRC-4-REG02 haveto be documented, addressed and corrective measures are to be envisaged in order toensure compliance with ESARR4Applicability: ECAC States




Particular criteria to assess the achievement of the Line of Action: New national regulationin the area covered by ESARR 4 and including national safety minima for ATM.



Particular criteria to assess the achievement of the Line of Action: Official promulgation ofthe new regulation


SRC04-REG06 Notify differences to ICAODefinition: Notify to ICAO those differences from ICAO SARPS � Annex 11 � Air TrafficServices - following ESARR 4 implementationApplicability: ECAC States




4-125

SRC04-REG07 Implement the mechanism to verify compliance with new/modifiedregulationsDefinition: National Regulatory Authorities shall implement the mechanism and resourcesallowing to verify compliance with the new/modified regulations.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Set of auditingprocedures and trained staff


SRC04-REG08 Verify that new regulation is appliedDefinition :Implement the oversight function to verify if new regulation is appliedApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Audit reports, regulatorystatements on acceptability of proposed changes to the ATM System, as well as existenceof corrective measures.



4-126



4-127

SRC05 Implement ESARR 5 on ATM Services'personnel

Confirmed

Definition:Implement the safety regulatory requirements laid down in EUROCONTROL SafetyRegulatory Requirements � ATM Services� Personnel ESARR 5 (Edition 1.0,dated10/11/2000) for all ATM services� personnel undertaking safety related taskswithin the provision of ATM Services across the ECAC area, and the specific safetyrequirements for air traffic controllers.Note: The timescales associated with the SLoAs are recommended only. The Stakeholders can stipulatedates according to their own timetables, provided that the objective itself is achieved by 11/2003.

Scope:Pan European


Timescale:By: 11/2003


No85/10.11.2000 (ESARR 5, Edition 1.0 dated 10/11/2000)


(SRC) Programme


2 (4.2.1, 4.2.2. and 4.2.5)


Contributes to ATM2000+ Strategy Safetyobjectives


requirements in the area of ATM Services� personnelaims to establish harmonised minimum levels ofcompetency and proficiency for staff having specificATM safety responsibilities





Main resource requirements: National ATM Safety Regulators, ATM ServiceProviders including all ATM Services� personnel undertaking safety-related tasks


SRC05-ASP01 Implement requirements for Air TrafficControllers to be applied by providers of air trafficservices

From: 11/2000 By: 11/2003 �

SRC05-ASP02 Implement requirements for Air TrafficControllers to be applied by individual personnel

From: 11/2000 By: 11/2003 �


From: 11/2000 By: 09/2001 �

SRC05-REG02 Assess national regulations vs. ESARR 5 From: 11/2000 By: 11/2001 �

SRC05-REG03 Document and address the differences identifiedin SRC05-REG02

From: 11/2000 By: 12/2001 �

27 Decision 85 of EUROCONTROL Permanent Commission approved the introduction of ESARR 5 (Edition 1.0, dated10.11.2000) within the national regulatory framework.


4-128


From: 11/2000 By: 09/2002 �

SRC05-REG05 Publish new regulation compliant with ESARR 5 From: 11/2000 By:04/2003 �

SRC05-REG06 Notify differences to ICAO From: 11/2002 By:11/2003 �

SRC05-REG07 Implement requirements for Air TrafficControllers to be applied by DesignatedAuthorities

From: 11/2000 By: 11/2003 �


From: 11/2000 By: 11/2003 �



4-129


SRC05-ASP01 Implement Requirements for Air Traffic Controllers to be applied byproviders of air traffic servicesDefinition: Implement Requirements for Air Traffic Controllers to be applied by individualpersonnel as they are laid down in the 13 requirements of ESARR 5 section 5.2.2.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: ATM Service Providersinternal set of procedures to apply ESARR 5 requirements


SRC05-ASP02 Implement Requirements for Air Traffic Controllers to be applied byindividual personnelDefinition: Implement Requirements for Air Traffic Controllers to be applied by individualpersonnel as they are laid down in the requirements of ESARR 5 section 5.2.3.1 forlicensed/certified Air Traffic Controllers and in section 5.2.3.2 for Student Air TrafficControllersApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: ATM Service Providersinternal set of procedures to facilitate ESARR 5 requirements application to individualpersonnel

Action by:Individual PersonnelFrom: 11/2000By: 11/2003


Particular criteria to assess the achievement of the Line of Action: Existence of alegislation allowing ESARR 5 enactment at national level


SRC05-REG02 Assess national regulations vs. ESARR 5Definition: Perform comparison between the ESARR 5 requirements and the appropriatenational regulations. This comparison shall address:1. existing national competency schemes vs. ESARR 5 requirements2. existing national training requirements vs. ESARR 5 requirements3. existing approved college courses vs. Common Core Content (ESARR 5

requirements)4. existing medical; requirements vs. ESARR 5 requirementsApplicability: ECAC States



SRC05-REG03 Document and address the differences identified in SRC05-REG02Definition: Differences detected during the assessment performed in SLoA SRC-5-REG02have to be documented, addressed and corrective measures are to be envisaged in orderto ensure compliance with ESARR5Applicability: ECAC States




4-130


Particular criteria to assess the achievement of the Line of Action: New national regulationin the area covered by ESARR 5



Particular criteria to assess the achievement of the Line of Action: Official promulgation ofnew regulation


SRC05-REG06 Notify differences to ICAODefinition: Notify to ICAO those differences from ICAO SARPS � Annex 1 � PersonnelLicensing - following ESARR 5 implementationApplicability: ECAC States



SRC05-REG07 Implement Requirements for Air Traffic Controllers to be applied byDesignated AuthoritiesDefinition: Implement Requirements for Air Traffic Controllers to be applied by DesignatedAuthorities as they are laid down in the 17 requirements of ESARR 5 section 5.2.1.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Designated Authoritiesinternal set of procedures to apply ESARR 5 requirements


SRC05-REG08 Implement the mechanism to verify compliance with new/modifiedregulationsDefinition: National Regulatory Authorities shall implement the mechanism allowing toverify compliance with the new/modified regulations.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Set of auditingprocedurea and trained staff


SRC05-REG09 Verify that new regulation is appliedDefinition: Implement the oversight function to verify if new regulation is applied by allaffectedApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Audit reports, regulatorystatements on acceptability of proposed changes to the ATM system, as well asexistenceof corrective measures


ECIP � YEARS 2002 TO 2006 - LEVEL 2 SUR01

4-131

SUR01 Implement dual Secondary SurveillanceRadar (SSR) Coverage

Confirmed

Definition:Implement dual SSR coverage of airspace with a specified quality.Note: This Objective is a continuation of former CIP Objectives of the Surveillance Domain, confirmed byMATSE 6 (01/2000)

Scope:



From: 12/1998By:



Strategic fit:Not Applicable


Previous CIP objectives

Performance benefitsSafety: Improved through enhanced radar coverage

Capacity: Indirect benefit via use of reduced separation minima



Enabler for: Achievement of required radar separation minima

Main resource requirements: Systems and procedures


SUR01-ASP01 Provide radar coverage at sensor level for en-route surveillance

From: By: 12/1995

SUR01-ASP02 Provide radar coverage for high complexityTMAs

From: By: 12/1995

SUR01-ASP03 Implement the means to support a harmonisedEuropean Radar Surveillance InfrastructurePerformance Analysis Programme

From: By: 12/1999

SUR01-ASP04 Provide communication support for radarrelated data exchange

From: By: 12/1998

SUR01-ASP05 Provide continuous radar coverage ofconsistent performance at sensor level for en-route surveillance

From: By: 12/1998


From: By: 12/2000

SUR01-ASP07 Provide radar data processing From: By: 12/1998SUR01-ASP08 Provide vertical tracking From: By: 12/1998


4-132

SUR01 - Detailed Stakeholder Lines of Action Description

SUR01-ASP01 Provide radar coverage at sensor level for en-route surveillanceDefinition: Radar coverage for en-route surveillance at sensor level has to be provided inaccordance with the coverage requirements as defined in the EUROCONTROL standardfor Radar Surveillance in en-route airspace and major terminal areas and in conformitywith the basic sensor performance reference level.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Provision of appropriateSASS-C measurement results for commissioned radars in their operational configuration


SUR01-ASP02 Provide radar coverage for high complexity TMAsDefinition: Radar coverage for High Complexity TMAs at sensor level has to be provided inaccordance with the EUROCONTROL standard for radar surveillance in en-route airspaceand major terminal areas and in conformity with the following performance reference levelsBasic level : Compliance with the detection and availability requirements of the abovestandard.Applicability: High Complexity TMAs

Particular criteria to assess the achievement of the Line of Action: Provision of appropriateSASS-C measurement results for commissioned radars (PSR & SSR) in their operationalconfiguration


SUR01-ASP03 Implement the means to support a harmonised European RadarSurveillance Infrastructure Performance Analysis ProgrammeDefinition: Performance verification of the various elements of the radar chain(transponder, sensor, radar data processing) shall be made, using procedures andanalysis methods as defined in the EUROCONTROL Standard on Radar Data Analysis,together with EUROCONTROL developed radar data analysis tools.Advanced level : means to verify the quality performance requirementsApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Availability of SASS-Cmeasurements applied & validated


SUR01-ASP04 Provide communication support for radar related data exchangeDefinition: Radar related data will be transmitted between radar sensors and radar dataprocessing systems (RDPSs) and between RDPSs over point-to-point dedicated circuits orover application in dependent data networks. Such transmission concerns also exchangesof radar related data between adjacent ATS Units (inter and intra State). Radar relateddata exchanges shall use the ASTERIX message structureApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Availability of radar datain the ASTERIX format at ATC centers


SUR01-ASP05 Provide continuous radar coverage of consistent performance atsensor level for en-route surveillanceDefinition: Radar coverage for en-route surveillance at sensor level has to be provided inaccordance with the quality requirements as defined in the EUROCONTROL Standard forradar surveillance in en-route airspace and major terminal areas and in conformity with theadvanced sensor performance reference level : - compliance with the detection, availabilityand quality requirements of the above standardApplicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Provision of advancedSASS-C measurement results for commissioned radars in their operational configuration

Action by:

ANS ProvidersFrom: By: 12/1998


4-133

SUR01-ASP06 Provide radar coverage for high complexity TMAsDefinition: Radar coverage for High Complexity TMAs at sensor level has to be provided inaccordance with the EUROCONTROL Standard for Radar Surveillance in en-routeairspace and major terminal areas and in conformity with the following performancereference levels :Advanced level: compliance with the detection, availability and quality requirements of theabove standard.Applicability: High Complexity TMA

Particular criteria to assess the achievement of the Line of Action: Provision of appropriateSASS-C measurement results for commissioned radars (PSR & SSR) in their operationalconfiguration


SUR01-ASP07 Provide radar data processingDefinition: Radar data processing for en-route surveillance at centre level has to beprovided in accordance with the requirements as defined in the EUROCONTROL Standardfor radar surveillance in en-route airspace and major terminal areas and in conformity withthe following functional performance level : the system selects (e.g. mosaic), or combineswith simple algorithms (e.g. direct averaging), the radar tracks and/or plots from more thanone radar station to a system track.Applicability: ECAC States

Particular criteria to assess the achievement of the Line of Action: Operational use ofmultiradar tracking systems


SUR01-ASP08 Provide vertical trackingDefinition: Vertical tracking has to be provided in accordance with the Eurocontrol standardfor radar surveillance in en-route airspace and major terminal areas, using SSR Mode Cinformation.Applicability: ACC & APP - High complexity

Particular criteria to assess the achievement of the Line of Action: Operational use ofvertical tracking



4-134



4-135

SUR02 Implement Mode S elementary surveillance Confirmed

Definition:Implement Mode S elementary Secondary Surveillance Radar (SSR) in specifiedairspace.Note: This Objective is a continuation of former CIP Objectives 1.2.1, confirmed by MATSE 6 (01/2000)

Scope:

Muli-NationalApplicable area:

GB, FR, DE, BE, NL, LU, CHTimescale:

From: 01/2001By:

Approval reference: Provisional Council - 13/07/2000 ; Permanent CommissionRecommendation � 11/2000

Supporting Programme:Mode S

Strategic fit:ATM 2000+, Vol.2 para. 8.2;

Surveillance Strategy


Previous CIP objective


Capacity: Improved through effects of removal of radarlimitations(garbling, fruit, number of targets, codeswaps, etc)

Cost-effectiveness: Greater than 10:1 Benefits to cost ratio

Environment: Reduction of RF pollution

Enabler for: Improve procedures through Mode S elementary surveillance information

Main resource requirements: Aircraft systems upgrade, Mode S sensor and SDPDsystem infrastructure deployment, staff training


SUR02-USE01 Install/retrofit Mode S in aircraft (SI codescompliance)

From: By: 03/2003 �

SUR02-ASP01 Implement ground Mode S sensors. From: 06/2002 By: �SUR02-REG01 Issue AIC and mandate carriage of Mode S

transponder (with SI codes)From: By: 01/2001 �

SUR02-REG02 Regulate the operations of Mode S SSR From: 06/2002 By: �SUR02-SUP01 Supply airborne & ground Mode S equipment From: 01/2001 By:


4-136


SUR02-USE01 Install/retrofit Mode S in aircraft (SI codes compliance)Definition: Install or retrofit Mode S transponders compliant to SI codes requirements in allaircraft intending to operate in Mode S airspace. Train crews to use of Mode S equipment.Applicability: Aircraft to operate in Mode S airspace

Particular criteria to assess the achievement of the Line of Action: ICAO Annex 10Amendment 73 & Flight Identity (FLID) compliant transponder installed


SUR02-ASP01 Implement ground Mode S sensorsDefinition: Implement ground Mode S interrogators.Applicability: States implementing Mode S sensors

Particular criteria to assess the achievement of the Line of Action: Mode S sensors inoperational service using Mode S select to interrogate equipped aircraft


SUR02-REG01 Issue AIC and mandate carriage of Mode S transponder (with SIcodes)Definition: Issue AIC and mandate carriage of Mode S transponder (with SI codes)Applicability: States implementing Mode S sensors

Particular criteria to assess the achievement of the Line of Action: Availability of publishedAIC

Action by:National RegulatoryAuthoritiesFrom: 01/2001By:

SUR02-REG02 Regulate the operations of Mode S SSRDefinition: Approve regulatory measures for operation of Mode S in national airspaceincluding ground infrastructure and code allocation.Applicability: States implementing Mode S

Particular criteria to assess the achievement of the Line of Action: Mode S operationsnationally approved

Action by:National RegulatoryAuthoritiesFrom: 06/2002By:

SUR02-SUP01 Supply Mode S equipmentDefinition: Supply airborne & ground Mode S equipment in accordance with definedspecifications, including the EUROCONTROL common functionnal specification for ModeS sensors and ICAO Annex 10 Amendment 73 transponders.Applicability: Mode S equipment Manufacturers

Particular criteria to assess the achievement of the Line of Action: Offer for sale equipmenttested & verified to meet approved specifications.

Action by:EquipmentManufacturersFrom: 01/2001By:


4-137

SUR03 Implement radar data processing anddistribution systems

Tentative

Definition:Implement radar data processing and distribution systems based on radar servertechnologyNote : This Objective is a continuation of former CIP Objective 1.3.7, confirmed by MATSE 6 (01/2000)

Scope:



From: 12/2003By:



Strategic fit:ATM 2000+ Strategy; Vol. 2,

para 7.7.2


Previous CIP Objective

Performance benefitsSafety: Under investigation

Capacity: Under investigation

Cost-effectiveness: Under investigation



Main resource requirements: Systems and procedures


SUR03-ASP01 Provide multi radar surveillance dataprocessing and distribution

From: By: 12/2003


4-138


SUR03-ASP01 Provide multi radar surveillance data processing and distributionDefinition: Provide Multi-radar surveillance data processing and distribution (SDPD) atACC level in accordance with requirements defined in the EUROCONTROL standard forradar surveillance in en-route airspace and major terminal areas, the operational conceptdocument for the EATCHIP Phase III system generation and in conformity with thefollowing functional performance level: The system processes, with advanced algorithms(real 3D multi-radar tracking), all relevant radar data to a system track. Provide for flexiblesurveillance data distribution, track and service continuity and contingency.Applicability: ECAC States



ECIP � YEARS 2002 TO 2006 - LEVEL 2 LINES OF ACTION GROUPED BY STAKEHOLDERS

5-1

5. LINES OF ACTION GROUPED BY STAKEHOLDERS

5.1 Stakeholders Lines of ActionThis chapter lists the summarised descriptions of the SLoA given in Chapter 4 byImplementation Objective and groups them according to the individual stakeholdercategories by alphabetical order in the following order:

� Airspace Users (Blue)........................................................................... 5.3� Military Authorities (Pink)....................................................................... 5.7� ANS Providers (Light Yellow)��.................................... 5.9� Airport Operators (Green)..................................................................... 5.19� Regulatory Bodies (Orange)................................................................. 5.21� EUROCONTROL Agency (Mauve)...................................................... 5.27� Supplier Industry (Dark Yellow)............................................................ 5.35

It does not include any additional information, and is intended only as an easyreference for stakeholders to allow them to identify the totality of the SLoA that applyto their particular stakeholder category.

ECIP � YEARS 2002 TO 2006 - LEVEL 2 LINES OF ACTION GROUPED BY STAKEHOLDERS

5-2


ECIP � YEARS 2002 TO 2006 - LEVEL 2 AIRSPACE USERS

5-3

5.2 AIRSPACE USERS


Confirmed

By: 01/2002 Pan European

AOM01-USE01 Modify aircraft and train crews From: By: 12/2001 �

AOM02 Implement Free Routes Airspace in eightstates airspace

Tentative

From: 04/2003 Multi national

AOM02-USE01 Adapt flight planning procedures and traincrews

From: 01/2003 By: �


Confirmed

From: 03/2001 By: 04/2002 Pan European

AOM04-USE01 Adapt Flight Planning From: By: 04/2002 �

AOM09 Implement re-organisation of ECAC airspace toensure the application of a common ICAO ATS

classification above a common agreed level

Tentative


AOM09-USE01 Train crews and adapt airborne systems asrequired

From: By: 03/2003 �


Tentative


AOM10-USE01 Adapt Flight Planning From: 06/2003 By: 06/2004 �


Tentative

From: 01/2002 Harmonisation

AOP01-USE01 Train aircrew in the application of guidelines From: 06/2002 By: �


5-4



Tentative


AOP02-USE01 Use �declared capacity� in combination withcapacity as calculated by CAMACA tool as aninput to schedule planning

From: 02/2003 By:


Confirmed



From: By: 01/2000


From: By: 01/2005

ATC01-USE03 Train aircrews in ACAS II From: By: 01/2000 �ATC01-USE04 Provide pilot reports to EEC Brétigny From: 01/1995 By: 01/2000 �


Confirmed


ATC06-USE01 Fit aircraft with air-ground data link equipmentand services and train crews.

From: 12/2002 By: �


Agreed

By: 10/2002 Harmonisation

COM02-USE01 Retrofit of aircraft for 8.33 kHz extension From: By: 10/2002


Confirmed


INF01-USE01 Migration of users to EAD From: 04/2003 By: �


aviation needs

Proposed


NAV01-USE01 Fit aircraft with SBAS From: 01/2004 By: �


Proposed


NAV02-USE01 Fit aircraft with GBAS From: 04/2003 By: �


5-5


From: 01/2001Harmonisation

NAV03-USE01 Where operators wish to upgrade their RNAVcapability they are encouraged to equip theiraircraft with systems that have an RNP -RNAVcapability to ensure long term benefits areobtained.

From: 01/2001 By 12/2010 �

NAV03-USE02 Train aircrews in RNAV TMA procedures From: 01/2001 By: 01/2005 �NAV03-USE03 Ensure correctness of data before use From: 01/2001 By: 01/2005 �


Agreed

From: 01/2001 By: 01/2005 Harmonisation

NAV04-USE01 Train aircrew in APV1 procedures From: 01/2001 By: 01/2005 �NAV04-USE02 Ensure correctness of data before use From: 01/2001 By: 01/2005 �



SUR02-USE01 Install/retrofit Mode S in aircraft (SI codescompliance)

From: By: 03/2003 �


5-6


ECIP � YEARS 2002 TO 2006 - LEVEL 2 MILITARY AUTHORITIES

5-7

5.3 MILITARY AUTHORITIES


Confirmed

From: 01/2000 By:01/2005 Pan European

ATC01-MIL01 Install ACAS II in transport aircraft From: By: 01/2005


Agreed


COM02-MIL01 Retrofit of military aircraft not exempted From: By: 10/2002

ECIP � YEARS 2002 TO 2006 - LEVEL 2 MILITARY AUTHORITIES

5-8


ECIP � YEARS 2002 TO 2006 - LEVEL 2 ANS PROVIDERS

5-9

5.4 ANS PROVIDERS


Confirmed


AOM01-ASP01 Prepare and validate ground ATC systems From: By: 08/2001 �AOM01-ASP02 Agree procedures between adjacent States From: By: 09/2001 �AOM01-ASP03 Train ATC staff From: By: 11/2001 �


Tentative


AOM02-ASP01 Implement airspace changes From: 01/2003 By: �AOM02-ASP02 Safety assurance for Free Routes operations From: 01/2003 By: �AOM02-ASP03 Prepare ground systems From: 01/2003 By: �AOM02-ASP04 Implement Operational Procedures From: 01/2003 By: �AOM02-ASP05 Train ATC Staff From: 01/2003 By: �AOM02-ASP06 Conclude agreements From: 01/2003 By: �


Confirmed


AOM04-ASP01 Implement national route structure changes From: 03/2001 By: 04/2002 �



AOM05-ASP01 Re-organise airspace sector structures From: 01/2000 By: �AOM05-ASP02 Prepare ground ATC systems From: 01/2000 By: �AOM05-ASP03 Implement revised operational procedures From: 01/2000 By: �AOM05-ASP04 Train ATC Staff From: 01/2000 By: �


Confirmed


AOM06-ASP01 Implement FUA concept From: By: 12/2000 �AOM06-ASP02 Implement FUA in lower airspace From: 01/2005 By: �AOM06-ASP03 Prepare ground ATC systems From: By: 12/2004 �


5-10


Tentative


AOM07-ASP01 Apply common procedures and guidelines From: By: 01/2003 �



AOM08-ASP02 Identify shortcomings of existing TerminalAirspace structure, SIDs/STARs; ATCSectorisation and ATC sequencing techniques

From: 01/2001 By: 12/2003 �

AOM08-ASP03 Redesign and implement improved TerminalAirspace structure, SIDs/STARs; ATCSectorisation and ATC sequencing techniquesfollowing the guidelines contained in TerminalAirspace Design Guidelines for an OperationalMethodology (ASM ET1 ST06)

From: 12/2001 By: 12/2005 �



Tentative


AOM09-ASP01 Train ATC staff in new procedures From: By: 03/2003 �AOM09-ASP02 Adapt ground systems as necessary From: By: 03/2003 �AOM09-ASP03 Adapt national airspace organisation as necessary From: By: 04/2003 �


Tentative


AOM10-ASP01 Implement National Route structure changes From: 06/2003 By: 06/2004 �


Tentative


AOP01-ASP01 Train airport controllers in application ofguidelines

From: 06/2002 By:



Tentative


AOP02-ASP01 Use �declared capacity� in combination withcapacity as calculated by CAMACA tool as aninput to operational planning

From: 02/2003 By:


5-11


Confirmed


ATC01-ASP01 Train controllers in ACAS II From: By: 01/2000 �ATC01-ASP02 Establish ACAS II performance monitoring From: 01/1995 By: 01/2000 �

ATC02 Implement ground based safety nets Confirmed


ATC02-ASP01 Implement Short Term Conflict Alert (STCA) From: By: 12/1998 �ATC02-ASP02 Implement Area Proximity Warning (APW) From: By: 12/1998 �ATC02-ASP03 Implement Minimum Safe Altitude Warning

(MSAW) for ACCs and TMAsFrom: By: 12/1998

ATC02-ASP04 Implement Minimum Safe Altitude Warning(MSAW) for Final Approach in TMAs with cat. 1airports (Approach Path Monitoring)

From: By: 12/2001


Confirmed


ATC03-ASP01 Provide advanced co-ordination supportbetween ATC units

From: 12/1998 By:

ATC03-ASP02 Provide transfer to communication betweenATC units

From: 12/1998 By:

ATC03-ASP03 Provide advanced co-ordination supportbetween civil and ATC military units

From: 12/1998 By: �

ATC03-ASP04 Provide advanced co-ordination supportbetween ATC and Airport Services

From: 12/1998 By:

ATC03-ASP05 Provide very advanced co-ordination supportbetween ATC and Airport Systems

From: 12/2001 By:

ATC04 Achieve required radar separation minima Confirmed


ATC04-ASP01 Radar separation within one en-route sector From: By: 12/1995ATC04-ASP02 Radar separation for verbal transfer between

en-route sectors, in the same ACCFrom: By: 12/1995

ATC04-ASP03 Radar separation for verbal transfer betweenACCs

From: By: 12/1995

ATC04-ASP04 Silent radar transfer between en-route sectorsin the same ACC

From: By: 12/1995

ATC04-ASP05 Silent radar transfer between ACCs From: By: 12/1998ATC04-ASP06 Implement 3 NM radar separation within High

complexity TMAsFrom: By: 06/1999

ATC04-ASP07 Implement 2.5 NM radar separation on FinalApproach at Category 1 Airports

From: By: 12/1999


Confirmed


ATC05-ASP01 Upgrade ground ATC systems From: 03/2003 By: �


5-12


Confirmed


ATC06-ASP01 Upgrade ground ATC systems From: 12/2002 By: �ATC06-ASP02 Integrate ATN/VDL-Mode 2 communication

infrastructure to handle air-ground data linkservices

From: 12/2002 By: �

ATC06-ASP03 Train controllers to use air-ground data linkservices

From: 07/2002 By: �



ATC07-ASP01 Implement initial arrival management tools From: 12/1998 By: ATC07-ASP02 Define AMAN procedures From: By: 12/2003ATC07-ASP03 Adapt TMA organisation to accommodate use

of AMANFrom: By: 12/2003

ATC07-ASP04 Prepare and adapt ATC systems to supportAMAN functions

From: By: 12/2003


Agreed


COM02-ASP01 Prepare ground ATC systems From: By: 10/2002COM02-ASP02 UHF coverage of 8.33 kHz airspace From: By: 10/2002 �

DPS01 Implement Flight Data Processing (FDP) corefunctionality

Confirmed


DPS01-ASP01 Provide Flight Plan/Track Correlation From: 01/1995 By: DPS01-ASP02 Automatic assignment and management of

SSR codes according to ORCAMFrom: By: 12/1995

DPS01-ASP03 Flight data update From: 01/1995 By: DPS01-ASP04 Flight data distribution From: 01/1995 By: DPS01-ASP05 Internal ATC unit co-ordination From: 01/1995 By: DPS01-ASP06 Route processing From: 01/1995 By: 12/2001DPS01-ASP07 Flight Profile Calculation From: 01/1995 By: DPS01-ASP08 Airspace data processing and distribution From: 01/1995 By: DPS01-ASP09 Met data processing and distribution From: 01/1995 By: DPS01-ASP10 Operational Human Machine Interface From: 01/1995 By: DPS01-ASP11 Configuration Management From: 01/1995 By: DPS01-ASP12 Recording and Replay From: 01/1995 By: DPS01-ASP13 Implement communication support for flight

data exchangeFrom: By: 12/1998 �

DPS01-ASP14 Provide basic co-ordination support within ATCunits

From: By: 12/1998

DPS01-ASP15 Provide basic co-ordination support betweenATC units

From: By: 12/1998

DPS01-ASP16 Provide advanced co-ordination supportbetween civil and military ATC units

From: 12/1998 By: �


5-13


States

Confirmed

From: 10/2007 By: 10/2010 Multi national

FAC01-ASP01 Transition to CEATS From: 10/2007 By: 12/2010 �FAC01-ASP02 Start CEATS operations From: 10/2007 By: 12/2010 �FAC01-ASP03 Harmonise investment and operational plans From: 06/2001 By: 12/2010 �


Confirmed

From: 08/2001 Pan European

FCM01-ASP01 Supply ETFMS with basic correlated positiondata

From: 08/2001 By: 12/2004

FCM01-ASP02 Supply ETFMS with Standard CorrelatedPosition Data

From: 08/2001 By: 12/2006

FCM01-ASP03 Receive and process ATFM data from theCFMU

From: 03/1995 By: 12/2001 �

FCM01-ASP04 Inform CFMU of flight activations andestimates for ATFM purposes

From: 03/1995 By: 12/1999

FCM01-ASP05 Inform CFMU of flight activations andadditional estimate updates for ATFMpurposes

From: 03/2001 By: 12/2006

FCM01-ASP06 Inform CFMU of re-routings inside FDPA forATFM purposes

From: 03/2001 By: 12/2006

FCM01-ASP07 Inform CFMU of aircraft holding for ATFMpurposes

From: 03/2003 By: 12/2006

FCM01-ASP08 Supply CFMU with Departure PlanningInformation (DPI)

From: 12/2002 By:

FCM03 Implement collaborative flight planning Confirmed


FCM03-ASP01 Provide flight plan message processing inICAO format

From: 03/1995 By: 12/1995

FCM03-ASP02 Automatically process FPLs derived fromRPLs

From: 03/1995 By: 12/1995

FCM03-ASP03 Provide flight plan message processing inADEXP format

From: 12/1997 By: 12/2001

FCM03-ASP04 Processing of APL and ACH messages From: 12/1997 By: 12/1999FCM03-ASP05 Provide AFP for missing flight plans From: 03/1998 By: 12/1999FCM03-ASP06 Provide AFP message for change of route From: 03/2002 By: 12/2005FCM03-ASP07 Provide AFP message for a diversion From: 03/2002 By: 12/2005FCM03-ASP08 Provide AFP message for a change of flight

rules or flight typeFrom: 03/2002 By: 12/2005

FCM03-ASP09 Provide AFP message for a change of en-route cruising level

From: 03/2002 By: 12/2005

FCM03-ASP10 Provide AFP messages in ADEXP format From: 03/1998 By: 12/2005FCM03-ASP11 Use IFPLID in all messages to TACT/ETFMS From: 03/2002 By: 12/2006 �FCM03-ASP12 Use IFPLID in exchange of route-charge data From: 03/2002 By: 12/2006 �FCM03-ASP13 Provide AFP message for a change of aircraft

type or aircraft equipmentFrom : 03/2002 By: 12/2005


5-14



HUM01-ASP01 Application of guidelines and tools for controllermanpower planning

From: 02/2000 By: 12/2007 �

HUM01-ASP02 Application of guidelines and tools for staffingand rostering

From: 02/2000 By: 12/2007

HUM01-ASP03 Provision of sufficient number of controllers From: 02/2000 By: 12/2007


Confirmed


HUM02-ASP01 Consider use of First European ATCOSelection Test package

From: 02/2003 By: 12/2007

HUM02-ASP02 Use common Training Syllabi and Plans From: 01/2001 By: 12/2007HUM02-ASP03 Use courseware based on new training

technologyFrom: 01/2001 By: 12/2007

HUM02-ASP04 Use continuation training syllabi and plans From: 07/2001 By: 12/2007HUM02-ASP05 Use common English language tests and

training modulesFrom: 01/2002 By: 12/2007

HUM02-ASP06 Use common training methods From: 10/2000 By: 12/2007HUM02-ASP07 Use advanced methods for personal/career

developmentFrom: 12/2000 By: 12/2007

HUM02-ASP08 Use common Team Resource Managementconcepts, methods and tools

From: 10/2000 By: 12/2007


Proposed


HUM03-ASP01 Application of human error managementmethods and tools

From: 06/2000 By: 12/2007

HUM03-ASP02 Human factors integration From: 11/2000 By: 12/2007HUM03-ASP03 Human contribution to system performance From: 10/2001 By: 12/2007HUM03-ASP04 Core requirements for ATM working positions From: 01/2001 By: 12/2007


Confirmed


INF01-ASP01 Migration and transition of States to EAD From: 09/2002 By: �INF01-ASP02 Provision of data to EAD by States From: 12/2002 By: �



INF02-ASP01 Reference and/or implement SDP in localprocedures

From: 10/2001 By: 12/2003

INF02-ASP02 Implement ISO QMS and achieve certification From: 06/2000 By: 12/2003


5-15


Proposed


INF03-ASP01 Implement the Data Integrity Tool (DIT) From: 10/2003 By: 12/2004INF03-ASP02 Adhere to AIRAC rules and guidance material From: 06/2000 By: 12/2004INF03-ASP03 Implement data content guidelines From: 09/2003 By: 12/2004INF03-ASP04 Implement and provide the eAIP From: 03/2002 By: 12/2004INF03-ASP05 Assess AIS against the performance criteria

and improve AIS Service LevelsFrom: 03/2002 By: 12/2004


Confirmed


MIS02-ASP01 Develop and implement contingency planningand procedures for technical failures

From: By: 12/2000

MIS02-ASP02 Develop and implement ATS contingencyplanning and procedures for industrial action

From: By: 12/2000


Proposed


NAV02-ASP01 Implement GBAS Category I infrastructure From: 04/2003 By: �NAV02-ASP02 Design and implement Category I approach

proceduresFrom: 10/2002 By: �



NAV03-ASP01 Develop and implement RNAV arrival anddeparture procedures

From: 01/2001 By: 01/2005 �


From: 01/2001 By: 01/2005 �

NAV03-ASP03 Train Air Traffic Controllers in RNAVprocedures

From: 01/2001 By: 01/2003 �

NAV03-ASP04 Train procedure designers in RNAV capabilities From: 01/2001 By: 01/2003 �NAV03-ASP05 Implement P-RNAV routes where identified as

providing benefitFrom: 01/2001 By: 01/2005 �

NAV03-ASP06 Publish in AIPS all co-ordinate data in WGS-84to accuracy and integrity specified in Annex 15

From: 01/2001 By: 01/2005�

NAV03-ASP07 Define all RNAV procedures to be for P-RNAVapproved aircraft and designed in accordancewith the EUROCONTROL guidelines and ICAOPANS OPS

From: 03/2002 By: 03/2003�


5-16


Agreed


NAV04-ASP01 Develop & Implement RNAV approaches withvertical guidance (APV1) procedures

From: 01/2001 By: 01/2005 �NAV04-ASP02 Provide appropriate terrestrial navigation

infrastructure to support RNAV operationsFrom: 01/2001 By: 01/2005 �

NAV04-ASP03 Train Air Traffic Controllers in RNAV andContinuous Descent procedures

From: 01/2001 By: 01/2005 �NAV04-ASP04 Train procedure designers in RNAV capabilities From: 01/2001 By: 06/2001 �NAV04-ASP05 Publish in AIPs all co-ordinate data in WGS-84

in accordance with ICAO Annex 15From: 01/2001 By: 01/ 2005 �

NAV04-ASP06 Design APV procedures in accordance withICAO PANS OPS as elaborated in theEUROCONTROL guidelines

From: 01/2001 By: 01/2005 �



SAF01-ASP01 Establish or update the Organisation Safety From: 01/2001 By: 08/2001 �SAF01-ASP02 Establish an action plan for implementing the

Safety PolicyFrom: 06/2001 By: 12/2001 �

SAF01-ASP03 Implement the policy principles From: 01/2002 By: 07/2003 �


Providers

Confirmed


SRC03-ASP01 Implement ESARR 3 requirements From: 07/2000 By: 07/2003 �


Confirmed


SRC04-ASP01 Implement ESARR 4 requirements From: 04/2001 By: 04/2004 �

SRC05 Implement ESARR 5 on ATM Services'personnel28

Confirmed


SRC05-ASP01 Implement requirements for Air TrafficControllers to be applied by providers of airtraffic services

From: 11/2000 By: 11/2003 �

SRC05-ASP02 Implement requirements for Air TrafficControllers to be applied by individualpersonnel

From: 11/2000 By: 11/2003 �

28 Refers to ESARR 5 (Edition 1.0 dated 10.11.2000)


5-17

SUR01 Implement dual Secondary SurveillanceRadar (SSR) coverage

Confirmed

Form: 12/1998 Harmonisation

SUR01-ASP01 Provide radar coverage at sensor level for en-route surveillance

From: By: 12/1995


From: By: 12/1995

SUR01-ASP03 Implement the means to support a harmonisedEuropean Radar Surveillance InfrastructurePerformance Analysis Programme

From: By: 12/1999

SUR01-ASP04 Provide communication support for radarrelated data exchange

From: By: 12/1998

SUR01-ASP05 Provide continuous radar coverage ofconsistent performance at sensor level for en-route surveillance

From: By: 12/1998


From: By: 12/2000

SUR01-ASP07 Provide radar data processing From: By: 12/1998SUR01-ASP08 Provide vertical tracking From: By: 12/1998



SUR02-ASP01 Implement ground Mode S sensors. From: 06/2002 By: 03/2003 �

SUR03 Implement radar data processing anddistribution systems

Tentative


SUR03-ASP01 Provide multi radar surveillance dataprocessing and distribution

From: By: 12/2003


5-18


ECIP � YEARS 2002 TO 2006 - LEVEL 2 AIRPORT OPERATORS

5-19

5.5 AIRPORT OPERATORS


Tentative


AOP01-APO01 Apply runway capacity enhancementguidelines depending on local circumstances

From: 01/2002 By:

AOP01-APO02AOP01-APO03

Measure ROTs.Construct new or additional RETs as required

From: 01/2002From: 01/2002

By: By:



Tentative


AOP02-APO01 Introduce CAMACA tool and train staff in itsapplication

From: 12/2002 By:

AOP02-APO02 Use �declared capacity� in combination withcapacity as calculated by CAMACA tool as aninput to operational planning

From: 02/2003 By:


Confirmed


ATC03-APO01 Provide advanced co-ordination supportbetween ATC and Airport Services

From: 12/1998 By:

ATC03-APO02 Provide very advanced co-ordination supportbetween ATC and Airport Systems

From: 12/2001 By:


Proposed


NAV02-APO01 Implement GBAS Cat.I infrastructure From: 04/2003 By: �

ECIP � YEARS 2002 TO 2006 - LEVEL 2 AIRPORT OPERATORS

5-20


ECIP � YEARS 2002 TO 2006 - LEVEL 2 REGULATORY BODIES

5-21

5.6 REGULATORY BODIES


Confirmed


AOM01-REG01 Regulatory measures for RVSM operations From: By: 10/2001 �AOM01-REG02 Safety assurance for RVSM ACHIEVEDAOM01-REG03 Certify equipment and verify airborne

equipment performanceFrom: By: 09/2001 �

AOM01-REG04 Approval of material for aircraft modificationand ATC procedures

ACHIEVED


Tentative


AOM02-REG01 Approve regulatory material From: By: 03/2003 �AOM02-REG02 Amend ICAO EUR Plan and other ICAO

documentsFrom: By: 04/2003


Confirmed


AOM04-REG01 Amend EUR Regional Plan From: By: 12/2001


Confirmed


AOM06-REG01 Amend Regional Plan From: By: 12/2004



Tentative


AOM09-REG01 Amend ICAO EUR document From: By: 03/2003AOM09-REG02 Revise national legislation as required From: By: 03/2003 �


Tentative


AOM10-REG01 Amend EUR Regional Plan From: By: 01/2004


5-22



Tentative


AOP02-REG01 National co-ordinators use �declared capacity�for slot allocation and schedule planning

From: 02/2003 By:


Confirmed


ATC01-REG01 Establish national legal provisions for ACAS II From: By: 06/1998 �ATC01-REG02 Adapt JAR-OPS provisions into national legal

proceduresFrom: By: 07/1999

ATC01-REG03 Implement changes to controller / pilot legalresponsibilities for ACAS II

From: By: 06/1998 �

ATC01-REG04 Approval of ACAS II training and operationalmaterial and courses for controllers andaircrew

From: By: 01/2000 �

ATC01-REG05 Amend related ICAO documentation From: By: 01/2005ATC01-REG06 Certify ACAS II compliant equipment From: By: 01/2005 �


Confirmed


ATC05-REG01 Issue AIC and mandate carriage of avionics From: By: 01/2001 �ATC05-REG02 Define certification for Mode S equipment (SI

codes and a/c identification)ACHIEVED

ATC05-REG03 Approve operational procedures for elementarysurveillance

From: By: 03/2003 �


Confirmed


ATC06-REG01 Provide guidance material for the certificationof aircraft and the approval of operations

From: By: 06/2001

ATC06-REG02 Approve the operational use of air-ground datalink services

From: By: 06/2003 �

ATC06-REG03 Amend ICAO documentation on air-grounddata link services

From: By: 12/2001

ATC06-REG04 Produce industry standards for data linkservices

From: By: 12/2001



ATC07-REG01 Approve AMAN procedures From: By: 12/2003


5-23


Agreed


COM02-REG01 Approve regulatory measures and safetyanalysis for 8.33 kHz

From: By: 10/2002 �

COM02-REG02 Publication of official documentation From: By: 10/2002 �COM02-REG03 Issue proposed 25kHz to 8.33 kHz

conversionFrom: By: 05/2000


States

Confirmed


FAC01-REG01 Approve delegation of ATS to CEATS UACC From: By: 10/2007 �FAC01-REG02 Amend EUR Regional Plan From: By: 10/2007


Proposed


INF03-REG01 Enforce the conformance to AIRAC From: 06/2000 By:

MIS01 Improve the management and optimise theoperational use of the aeronautical

frequency assignments in allocated radiobands

Confirmed


MIS01-REG01 Implement the currently available and improvedfrequency management mechanisms and tools

From: 01/2001 By: 12/2005 �


Confirmed


MIS02-REG01 Enact regulation for application of contingencyplans

From: By: 12/2000


aviation needs

Proposed


NAV01-REG01 Approve standards for SBAS From: 01/2000 By: 03/2003NAV01-REG02 Define common certification and operational

approval criteria for SBAS airborne equipmentFrom: 08/2000 By: 06/2002

NAV01-REG03 Certify aircraft for SBAS operation From: 03/2003 By: �


5-24


Proposed


NAV02-REG01 Approve standards for GBAS From: 01/2000 By: 03/2003NAV02-REG02 Define common certification criteria for GBAS

airborne equipmentFrom: 01/2001 By: 06/2002

NAV02-REG03 Certify GBAS airborne equipment From: 03/2003 By: �NAV02-REG04 Enact regulation for GBAS operational

proceduresFrom: By: 03/2003 �

NAV02-REG05 Approve use of GBAS equipment From: By: 03/2003 �



NAV03-REG01 Ensure suppliers of navigation databases areaccredited

From: 01/ 2001 By: 01/2005

NAV03-REG02 Ensure quality of published Navigation Data From: 01/2001 By: 01/2005


Agreed


NAV04-REG01 Develop and Issue TGL for APV1 Operations From : 01/2001 By: 06/2001NAV04-REG02 Ensure suppliers of navigation databases are

accreditedFrom: 01/2001 By: 01/2005

SRC02 Implement ESARR 2 on Reporting andAnalysis of safety occurrences in ATM

Confirmed


SRC02-REG01 Identify/Set-up national institutional arrangementsto implement ESARR 2

From: 11/1999 By: 11/2000 �


in SRC02-REG02From: 11/1999 By: 12/2001 �


From: 11/1999 By: 11/2001 �

SRC02-REG05 Publish new regulation compliant with ESARR 2 From: 11/2001 By: 12/2001 �SRC02-REG06 Notify differences to ICAO From: 12/2001 By: 01/2002 �SRC02-REG07 Implement ESARR 2 Requirements for Accidents

and ATM incidents with risk of Collision (Phase 1)From: 11/1999 By: 01/2000 �

SRC02-REG08 Implement ESARR 2 Requirements for ATMincidents with potential for risk of Collision(Phase 2)

From: 11/1999 By: 01/2001 �

SRC02-REG09 Implement ESARR 2 Requirements for ATMspecific occurrences (Phase 3)

From: 11/1999 By: 01/2002 �


From: 11/1999 By: 01/2001 �

SRC02-REG11 Verify that new regulation is applied by all affected From 01/2001 By 01/2002 �


5-25


Providers

Confirmed


SRC03-REG01 Identify/Set-up national institutional arrangementsto implement ESARR 3

From: 07/2000 By: 10/2001 �


in SRC03-REG02From:10/2001 By: 01/2002 �


From: 07/2000 By: 12/2002 �





Confirmed



From: 04/2001 By: 02/2002 �


in SRC04-REG02From: 02/2002 By: 05/2002 �


From: 04/2001 By: 05/2003 �




SRC05 Implement ESARR 5 on ATM Services'personnel29

Confirmed



From: 11/2000 By: 09/2001 �


in SRC05-REG02From: 11/2000 By: 12/2001 �


From: 11/2000 By: 09/2002 �

SRC05-REG05 Publish new regulation compliant with ESARR 5 From: 11/2000 By:04/2003 �SRC05-REG06 Notify differences to ICAO From: 11/2002 By:11/2003 �SRC05-REG07 Implement requirements for Air Traffic

Controllers to be applied by DesignatedAuthorities

From: 11/2000 By: 11/2003 �


From: 11/2000 By: 11/2003 �


29 Refers to ESARR 5, Edition 1.0 dated 10.11.2000


5-26



SUR02-REG01 Issue AIC and mandate carriage of Mode Stransponder (with SI codes)

From: By: 01/2001 �

SUR02-REG02 Regulate the operations of Mode S SSR From: 06/2002 By: �

ECIP � YEARS 2002 TO 2006 - LEVEL 2 EUROCONTROL AGENCY

5-27

5.7 EUROCONTROL AGENCY


Confirmed


AOM01-AGY01 Amend IFPS for RVSM ACHIEVEDAOM01-AGY02 Implement height monitoring structure ACHIEVEDAOM01-AGY03 Safety analysis for RVSM From: By: 07/2001


Tentative


AOM02-AGY01 Define common procedures for Free Routesairspace operations

From: By: 01/2003

AOM02-AGY02 Adapt IFPS for Free Routes operations From: By: 12/2002AOM02-AGY03 Overall safety assessment for Free Routes

operationsFrom: By: 12/2002

AOM02-AGY04 Adapt ATFM to Free Routes operations From: By: 12/2002AOM02-AGY05 Implement monitoring structure From: By: 04/2003


Confirmed


AOM04-AGY01 Develop and validate ARN V4 From: By: 12/2001



AOM05-AGY01 Adapt ATFM processes and procedures From: 01/2000 By:


Confirmed


AOM06-AGY01 Define common procedures andguidelines

From: By: 12/2004


Tentative


AOM07-AGY01 Define common procedures and guidelines From: By: 12/2002


5-28



AOM08-AGY01 Develop Terminal Airspace Design Guidelines foran Operational Methodology , 2nd Edition (ASM ET1ST06)

By: 12/2002



Tentative


AOM09-AGY01 Develop and validate proposals From: By: 12/2001AOM09-AGY02 Develop initial ECAC Airspace Guidance document From: By: 12/2001


Tentative


AOM10-AGY01 Develop and validate ARN V5 From: 03/2002 By: 06/2004AOM10-AGY02 Adapt ATFM processes and procedures From: By: 06/2004


Tentative


AOP01-AGY01 Develop ATC procedures for new developments From: By:



Tentative


AOP02-AGY01 Develop and make available the CAMACA tool From: By: 01/2003AOP02-AGY02 Maintain model as required From: 02/2003 By:


Confirmed


ATC01-AGY01 Develop means to analyse ACAS events occurringwithin the ECAC Airspace

ACHIEVED

ATC01-AGY02 Develop means to collect and analyse studyresults in support of decisions to be made onACAS implementation

ACHIEVED

ATC01-AGY03 Develop means to ensure successful introductionof TCAS II Version 7.0 software

ACHIEVED

ATC01-AGY04 Develop means to handle exemptions during theimplementation period

ACHIEVED


5-29


Confirmed


ATC05-AGY01 Produce specimen AIC ACHIEVEDATC05-AGY02 Produce operational requirements for transition to

SSR Mode SFrom: By: 06/2002

ATC05-AGY03 Set up European-wide procedures for interrogatorcodes (IC) allocation

From: By:06/2002

ATC05-AGY04 Define operational procedures for use ofelementary surveillance data

From: By: 06/2002

ATC05-AGY05 Define requirements for adaptation of FDPS,RDPS and IFPS to Mode S surveillance.

From: By: 09/2001

ATC05-AGY06 Modify IFPS environment From: By: 03/2003


Confirmed


ATC06-AGY01 Define and validate the data link services From: 12/2001 By: ATC06-AGY02 Define operational scenario, procedures, HMI,

transition guidelines and training planFrom: By: 06/2002

ATC06-AGY03 Design network and plan capacity From: By: 05/2002ATC06-AGY04 Define safety assessment methodology and

certification planFrom: By: 02/2002



ATC07-AGY01 Define common AMAN Operational Requirements ACHIEVEDATC07-AGY02 Validation, safety assessment and CBA for AMAN From: By: 12/2003


Agreed

By : 10/2002 Harmonisation

COM02-AGY01 Update 8.33 Users Guide From: By: 10/2001COM02-AGY02 Implement advanced IFPS message for 8.33 KHz From: By: 04/2002


States

Confirmed


FAC01-AGY01 Define CEATS operational concept From: By: 10/2005FAC01-AGY02 Develop CEATS infrastructure From: By: 12/2006


5-30


Confirmed


FCM01-AGY01 Implement ETFMS Phase 1A From: 01/2000 By: 12/2001FCM01-AGY02 Implement ETFMS Phase 1B From: By: 03/2002FCM01-AGY03 Implement ETFMS Phase 1C From: By: 03/2003FCM01-AGY04 Implement ETFMS Phase 2 From: By: 03/2004

FCM02 Initial capacity management Agreed


FCM02-AGY01 Implement PREDICT system From: By: 05/2000FCM02-AGY02 Give access to the PREDICT system to FMPs From: By: 03/2001FCM02-AGY03 Develop "what-if" functions to optimise capacity

managementFrom: By: 03/2001



HUM01-AGY01 Development and provision of advancedmanpower planning methods and tools

From: 01/2000 By: 12/2002


Confirmed


HUM02-AGY01 First European ATCO Selection Test package From: 01/2000 By: 12/2002HUM02-AGY02 Common Training Syllabi and Plans From: 01/2000 By: 12/2002HUM02-AGY03 Courseware based on new training technology From: 01/2000 By: 12/2002HUM02-AGY04 Continuation Training Syllabi and Plans From: 03/2000 By: 12/2002HUM02-AGY05 English language tests and training modules From: 03/2000 By: 12/2002HUM02-AGY06 Training methods From: 01/2000 By: 12/2002HUM02-AGY07 Methods for personal/career development From: 01/2000 By: 12/2002HUM02-AGY08 Team Resource Management From: 04/2000 By: 12/2002


Proposed


HUM03-AGY01 Human error management methods and tools From: 01/2000 By: 12/2002HUM03-AGY02 Human factors integration From: 01/2000 By: 12/2002HUM03-AGY03 Human contribution to system performance From: 03/2000 By: 12/2002HUM03-AGY04 Core requirements for ATM working positions From: 01/2000 By: 12/2002


Confirmed


INF01-AGY01 Provisional acceptance of the EAD System From: 07/1999 By: 03/2003INF01-AGY02 Start of tentative operation of the EAD Service From: 03/2003 By: 05/2003INF01-AGY03 Start of full operation of the EAD Service From: 06/2003 By: 05/2004


5-31



INF02-AGY01 Develop and provide Awareness campaign From: 06/1999 By: 12/2001INF02-AGY02 Develop and provide AIS Static Data

Procedures (SDP)From: 01/1999 By: 10/2001

INF02-AGY03 Facilitate ISO implementation From: 01/2000 By: 12/2003


Proposed


INF03-AGY01 Develop a Data Integrity Tool (DIT) From: 12/2000 By: 10/2003INF03-AGY02 Develop DIT implementation guidance material From: 07/2002 By: 10/2003INF03-AGY03 Develop AIRAC Awareness campaign and

guidance materialFrom: 06/2000 By: 10/2001

INF03-AGY04 Develop data content guidelines From: 06/2000 By: 09/2003INF03-AGY05 Develop a specification and guidance material

for implementation of an eAIPFrom: 06/2000 By: 03/2002

INF03-AGY06 Develop a concept and performance criteria forstandardised AIS Service Levels

From: 06/2000 By: 03/2002

INF03-AGY07 Develop a framework to measure developmentand implementation progress

From: 06/2000 By: 12/2004

MIS01 Improve the management and optimise theoperational use of the aeronautical

frequency assignments in allocated radiobands

Confirmed


MIS01-AGY01 Define, for VHF Com band, mechanisms andtools to improve frequency management andto optimise operational use of frequencyassignments

ACHIEVED

MIS01-AGY02 Define improved and centralised mechanismsand tools to improve frequency managementand to optimise operational use of frequencyassignments for all aviation bands

From: By: 06/2002


Confirmed


MIS02-AGY01 Define a common policy, planning templateand guidelines for contingency plans

From: By: 10/2000


5-32


aviation needs

Proposed


NAV01-AGY01 Real-time SAPPHIRE performance monitoring From: 01/2002 By: 12/2003NAV01-AGY02 SBAS safety assessments From: 07/1999 By: 06/2004NAV01-AGY03 SBAS operational validation From: 01/2000 By: 10/2004NAV01-AGY04 SBAS business case ACHIEVEDNAV01-AGY05 Develop operational procedures and standards

for SBAS From: 01/2000 By: 01/2005


Proposed


NAV02-AGY01 Real-time performance monitoring From: 12/2002 By: NAV02-AGY02 GBAS safety assessments From: 01/2001 By: 12/2003NAV02-AGY03 GBAS operational validation From: 01/2001 By: 12/2003NAV02-AGY04 GBAS business case From: By: 03/2003NAV02-AGY05 Develop operational procedures and standards

for GBASFrom: 01/2001 By: 10/2002

NAV02-AGY06 Identify operational needs for GBAS. From: 01/2001 By: 06/2001



NAV03-AGY01 Identify applicability of P-RNAV routes to en-route applications

From: 01/2001 By: 01/2003

NAV03-AGY02 Investigate the requirements for additionalR/T phraseology and Flight PlanningMethodology for RNAV operations inTerminal Airspace and develop as necessary

From 06/2001 By: 01/2002


Initial VersionComplete

Update asnecessary to2010


Agreed


NAV04-AGY01 Develop Guidance Material forimplementation of APV

From: 01/2001 By: 01/2002


From: 01/2001 By: 01/ 2005


5-33



SAF01-AGY01 Update the EATMP Safety Policy according toESARR 3

From: 02/2001 By 06/2001

SAF01-AGY02 Provide guidance to perform a survey on currentsafety management processes

From: 06/2001 By: 10/2001

SAF01-AGY03 Develop additional guidance material on new EATMPSafety Policy principles

From: 08/2001 By 12/2002


5-34


ECIP � YEARS 2002 TO 2006 - LEVEL 2 SUPPLIER INDUSTRY

5-35

5.8 SUPPLIER INDUSTRY


Confirmed


AOM01-SUP01 Provide altimetry systems ACHIEVED


Tentative


AOM02-SUP01 Provide data processing systems and supporttools

From: By: 04/2003


Confirmed


ATC01-SUP01 Produce and install ACAS II compliantequipment

From: By: 01/2005


Confirmed


ATC06-SUP01 Provide avionics and ground systems for datalink services

From: 12/2002 By:

ATC06-SUP02 Deploy communication infrastructure to handleair-ground data link services

From: 12/2002



ATC07-SUP01 Supply AMAN tools From: By: 12/2003


Agreed


COM02-SUP01 Provide certified 8.33/25kHz mixedenvironment radio systems

By: 08/2002

ECIP � YEARS 2002 TO 2006 - LEVEL 2 SUPPLIER INDUSTRY

5-36


Confirmed


INF01-SUP01 Develop and implement the EAD System From: 07/1999 By: 04/2004INF01-SUP02 Develop the EAD Service From: 05/2001 By: 05/2003INF01-SUP03 Implement the EAD Service From: 05/2003 By: 05/2004


aviation needs

Proposed


NAV01-SUP01 Provide airborne equipment and retrofit kits forSBAS

From: 04/2003 By: 01/2005

NAV01-SUP02 Implementation of SBAS infrastructure From: 11/2003 By: 09/2004


Proposed


NAV02-SUP01 Provide airborne equipment and retrofit kits From: 04/2003 By:NAV02-SUP02 Provide GBAS equipment From: 04/2003 By:



NAV03-SUP01 Ensure that data is meets specification of ED 77and is managed according to ED76.

From: 01/2001 By 01/2005

NAV03-SUP02 Ensure that the Navigation Database cannot becorrupted when installed

From: 01/2001 By 01/2005


Agreed


NAV04-SUP01 Ensure that data is encoded in accordance withED76 and ED77

From: 01/2001 By: 01/2005

NAV04-SUP02 Ensure that the Navigation Database is notcorrupted when installed

From: 01/ 2001 By: 01/2005



SUR02-SUP01 Supply airborne & ground Mode S equipment From: 01/2001 By:

ECIP � YEARS 2002 TO 2006 - LEVEL 2 ANNEX A

A-1

ANNEX A � TRACEABILITY OF ECIP OBJECTIVES TO FORMER CIP OBJECTIVES

The following table shows the relationship between the current ECIP objectives and StakeholderLines of Action (SLoA) (ECIP Level 2 Years 2002 to 2006) and the objectives contained in the CIPPart 1 (Edition 3.2). It should be noted that the table will not be included in future versions of theECIP document (ie: ECIP 2003-2007 or later documents).

ECIPObjective

/ SLoA

ECIP Objective or SLoA title Objectivedesignation

in CIPDPart 1

CIP Objective title

AOM01-ASP02

Agree procedures between adjacent States 3.6.5 Promulgate ATC Procedures for Transitionbetween RVSM and non-RVSM Airspace

AOM01-REG01

Regulatory measures for RVSM operations 3.6.4

7.4.1

Promulgate ATC Procedures for non-MAPScomplying State aircraft operating in RVSM

Implement regional air navigational agreementfor 1000 feet vertical separation minimumabove FL 290

AOM06-ASP01

Implement FUA concept 3.3.2

3.3.3

3.5.5

3.5.6

- Implement Phase 1 of Flexible Use ofAirspace Concept- Implement Phase 2 of Flexible Use ofAirspace Concept- Civil-Military Co-ordination for Phase 1 ofFlexible Use of Airspace- Civil-Military Co-ordination for Phase 2 ofFlexible Use of Airspace

ATC01-ASP01

Train controllers to ACAS II 14.1.4 Establish and approve appropriate aircrew andcontroller ACAS II training / familiarisationprogrammes

ATC01-ASP02

Establish ACAS II performance monitoring 14.1.3 Establish an ACAS II Performance monitoringprogramme

ATC01-REG01

Establish national legal provisions forACAS II

14.1.1 Establish national legal provisions for thecarriage and operation of ACAS II inaccordance with the endorsed ECAC ACASStrategy and the adopted ACAS IIImplementation Schedule

ATC01-REG03

Implement changes to controller / pilot legalresponsibilities for ACAC II

14.1.2 Implement established controller and pilotlegal responsibilities during ACAS IIoperational procedures in national airspace

ATC01-REG04

Approval of ACAS II training and operationalmaterial and courses for controllers andaircrew

14.1.4 Establish and approve appropriate aircrew andcontroller ACAS II training / familiarisationprogrammes

ATC01-USE03

Train aircrews in ACAS II 14.1.4 Establish and approve appropriate aircrew andcontroller ACAS II training / familiarisationprogrammes

ATC01-USE04

Provide pilots reports to EEC Bretigny 14.1.3 Establish an ACAS II Performance monitoringprogramme

ATC02-ASP01

Implement Short Term Conflict Alert (STCA) 5.10.1 Provide STCA

ATC02-ASP02

Implement Area Proximity Warning (APW) 5.10.2 Provide Area Proximity Warning

ATC02-ASP03

Implement Minimum Safe Altitude Warning(MSAW) for ACCs and TMAs

5.10.3 Provide MSAW (En-route)

ATC02-ASP04

Implement Minimum Safe Altitude Warning(MSAW) for Final Approach in TMAs withcat. 1 airports (Approach Path Monitoring)

5.10.4 Provide MSAW (Final Approach)

ATC03-APO01

Provide advanced co-ordination supportbetween ATC and Airport Services

5.3.5 Adv Provide co-ordination support between ATCand Airport Services

ATC03-APO02

Provide very advanced co-ordination supportbetween ATC and Airport Services

5.3.5Very Adv

Provide co-ordination support between ATCand Airport Services

ATC03-ASP01

Provide advanced co-ordination supportbetween ATC units

3.5.3

5.3.4 Adv

Co-ordination between ATC units supported bydialogue facilities

Provide external ATC units co-ordinationsupport - advanced level (SYSCO)

ATC03-ASP02

Provide transfer to communication betweenATC units

5.3.8 Co-ordination between ATC units supported bydialogue facilities

ATC03-ASP03

Provide advanced co-ordination supportbetween civil and ATC military units

3.5.6

5.3.6 Adv

Civil-Military Co-ordination for Phase 2 ofFlexible Use of Airspace

Provide Civil-Military Co-ordination Support -advanced level


A-2

ECIPObjective

/ SLoA


in CIPDPart 1

CIP Objective title

ATC03-ASP04

Provide advanced co-ordination supportbetween ATC and Airport Services

5.3.5 Adv Provide co-ordination support between ATCand Airport Services

ATC03-ASP05

Provide very advanced co-ordination supportbetween ATC and airport services

5.3.5 VeryAdv

Provide co-ordination support between ATCand Airport Services

ATC04-ASP01

Radar separation within one en-route sector 3.4.1 Basic+ Adv

Radar separation within one En-route sector

ATC04-ASP02

Radar separation for verbal transfer betweenen-route sectors, in the same ACC

3.4.2 Basic+ Adv

Radar separation for 'verbal' transfer betweenEn-route sectors, in the same ACC

ATC04-ASP03

Radar separation for verbal transfer betweenACCs

3.4.3 Basic+ Adv

Radar separation for 'verbal' transfer betweenACCs

ATC04-ASP04

Silent radar transfer between en-routesectors in the same ACC

3.4.4 Basic+ Adv

Silent radar transfer between En-route sectors,in the same ACC

ATC04-ASP05

Silent radar transfer between ACCs 3.4.5 Basic+ Adv

Silent radar transfer between ACCs

ATC04-ASP06

Implement 3 NM radar separation withinHigh complexity TMAs

3.4.6 Implement 3 NM Radar Separation within HighComplexity TMAs

ATC04-ASP07

Implement 2.5 NM radar separation on FinalApproach at Category 1 Airports

3.4.7 Implement 2.5 NM Radar Separation on FinalApproach at Category 1 Airports

ATC05-ASP01

Upgrade ground ATC systems 1.3.8 Provide Surveillance Data Processing andDistribution incl. Mode S EnhancedSurveillance

ATC06-ASP01

Upgrade ground ATC systems 2.1.5

5.5.2

5.5.3

5.5.4

Implement Air/Ground CommunicationServices for early Air/Ground Data Linkservices - Interim Step based on non-ATN(ACARS) Services

Provide (Pre-)Departure Clearance Delivery

Provide Automatic Terminal InformationService Delivery

Provide relay and delivery of operationalmessages

ATC07-ASP01

Implement initial arrival management tools 5.11.1 Adv Provide arrival sequencing and metering

DPS01-ASP01

Provide Flight Plan/Track Correlation 5.1.1 Basic+ Adv

Provide Flight Plan / Track Correlation

DPS01-ASP02

Automatic assignment and management ofSSR codes according to ORCAM

5.1.2 Basic+Adv

Provide automated assignment andmanagement of SSR codes according toORCAM

DPS01-ASP03

Flight data update 5.3.1 Basic+ Adv

Provide flight data update

DPS01-ASP04

Flight data distribution 5.3.2 Provide flight data distribution

DPS01-ASP05

Internal ATC unit co-ordination 3.5.73.5.8

5.3.3 Basic

Co-ordination with automated support withinATC units

Provide internal ATC units co-ordinationsupport

DPS01-ASP06

Route processing 5.4.1Basic+Adv

Provide route processing

DPS01-ASP07

Flight Profile Calculation 5.4.2 Basic+Adv

Provide flight profile calculation

DPS01-ASP08

Airspace data processing and distribution 5.6.1 Basic+ Adv

Provide airspace data processing anddistribution

DPS01-ASP09

Met data processing and distribution 5.7.1 Basic Provide MET data processing and distribution

DPS01-ASP10

Operational Human Machine Interface 5.16.3 Basic+ Adv +Very Adv

Provide operational HMI

DPS01-ASP11

Configuration Management 5.17.2 Provide configuration management

DPS01-ASP12

Recording and Replay 5.17.3 Basic+ Adv

Provide recording and replay

DPS01-ASP13

Implement communication support for flightdata exchange

2.3.2 Provide Communication Support for flight dataexchange

DPS01-ASP14

Provide basic co-ordination support withinATC units

3.5.73.5.85.3.3 Basic

Co-ordination with automated support withinATC units


A-3

ECIPObjective

/ SLoA


in CIPDPart 1

CIP Objective title

DPS01-ASP15

Provide basic co-ordination support betweenATC units

3.5.93.5.10

5.3.4 Basic

- Co-ordination between ATC units

- Provide external ATC units co-ordinationsupport - basic level

DPS01-ASP16

Provide basic co-ordination support betweencivil and military ATC units

3.5.5

5.3.6 Basic

- Civil-Military Co-ordination for Phase 1 ofFlexible Use of Airspace- Provide Civil-Military Co-ordination Supportbasic level

FCM01-ASP03

Receive and process ATFM data from theCFMU

15.1.3 Adv Receive and process ATFM data from theCFMU

FCM01-ASP04

Inform CFMU of flight activations andestimates for ATFM purposes

15.1.4Basic

Inform CFMU of flight activations andintentions for ATFM purposes

FCM01-ASP05

Inform CFMU of flight activations andadditional estimates for ATFM purposes

15.1.4Adv 1


FCM01-ASP06

Inform CFMU of re-routings inside FDPA forATFM purposes

15.1.4Adv 2


FCM01-ASP07

Inform CFMU of aircraft holding for ATFMpurposes

15.1.4Adv 3


FCM03-ASP01

Provide flight plan message processing inICAO format

15.1.1basic 1

Provide flight plan message processing (forATFM)

FCM03-ASP02

Automatically process FLPs derived fromRPLs

15.1.1Basic 2


FCM03-ASP03

Provide flight plan message processing inADEXP format

15.1.1Adv


FCM03-ASP04

Processing of APL and ACH messages 15.1.2Adv 1

Implement processing of updates to activeflight plan information

FCM03-ASP05

Provide AFP for missing flight plans 15.1.2Adv 2


FCM03-ASP10

Provide AFP messages in ADEXP format 15.1.2Adv 3


HUM01-ASP01

Application of guidelines and tools forcontroller manpower planning

6.4.1 Application of Guidelines for WorkOrganisation, Staffing and Manpower Planning

HUM01-ASP02

Application of guidelines and tools forstaffing and rostering

6.4.1 Application of Guidelines for WorkOrganisation, Staffing and Manpower Planning

HUM02-ASP01

Consider use of First European ATCOSelection Test package

6.3.1 Application of Guidance Material for SelectionProcedures and Tests

HUM02-ASP02

Use common Training Syllabi and Plans 6.1.1Phase 1 & 2

6.1.2

6.1.4

6.2.1

Guidelines for Common Core Training(ATCOs) - Phase 1 (Fundamental), Phase 2(Rating)

Guidelines for Common Core Training of otherthan ATCO Operational Staff (incl. AIS andATFM Staff) - AIS Staff

Advanced Training Methods and TrainingTools

Application of common Standards forPersonnel Licensing, ATCOs

HUM02-ASP03

Use courseware based on new trainingtechnology

6.1.5 ATS Illustrative Courses and Related TrainingCourseware

HUM02-ASP05

Use common English language tests andtraining modules

6.1.3 English Language Proficiency Tests (ATCOs)

HUM02-ASP06

Use common training methods 6.1.1 Phase1 & 2

6.1.2

6.1.4

Guidelines for Common Core Training(ATCOs) - Phase 1 (Fundamental), Phase 2(Rating)

Guidelines for Common Core Training of otherthan ATCO Operational Staff (incl. AIS andATFM Staff) - AIS Staff

Advanced Training Methods and TrainingTools

HUM02-ASP07

Use common methods for personal/careerdevelopment

6.4.2 Application of Guidelines for Development andImplementation of a Human ResourcesDevelopment Programme (ATCOs)

HUM02-ASP08

Use common Team Resource Managementconcepts, methods and tools

6.5.1 Application of Guidelines for Development andImplementation of Team ResourceManagement (TRM)


A-4

ECIPObjective

/ SLoA


in CIPDPart 1

CIP Objective title

INF01-USE01

Migration of users to EAD 13.1.5 Full participation in the EAD

INF01-ASP01

Migration and transition of States to EAD 13.1.5 Full participation in the EAD

INF01-ASP02

Provision of data to EAD by States 13.1.5 Full participation in the EAD

INF02-ASP01

Reference and/or implement SDP in localprocedures

13.1.3 Quality assured aeronautical informationsystem

INF02-ASP02

Implement ISO QMS and achievecertification

13.1.3 Quality assured aeronautical informationsystem

MIS01-REG01

Use current and improved common co-ordination mechanisms and tools

2.1.6

2.1.7

Optimise the management of AeronauticalFrequencies - Implement Common

Frequency Management Tools andProcedures

MIS02-ASP01

Contingency Planning and Procedures fortechnical failures

8.1.1 Implementation of Guidelines for ATSContingency Planning in the event of LongTerm Technical/ Catastrophic Failure

MIS02-ASP02

Implement ATS Contingency Planning andprocedures for industrial action

8.1.2 Establish and Implement Arrangements forATS Contingency Planning in the event ofIndustrial Action

MIS02-REG01

Enact regulation for application ofcontingency plans

8.1.1

8.1.2

Implementation of Guidelines for ATSContingency Planning in the event of LongTerm Technical/ Catastrophic Failure

Establish and Implement Arrangements forATS Contingency Planning in the event ofIndustrial Action

SAF01-ASP01

Establish or update the Organisation SafetyPolicy

10.1.1 Implement a safety management programme

SAF01-ASP02

Establish an action plan for implementing theSafety Policy

10.1.1 Implement a safety management programme

SAF01-ASP03

Implement the policy principles 10.1.1 Implement a safety management programme

SUR01-ASP01

Provide radar coverage at sensor level foren-route surveillance

1.1.1 Basic Provide radar coverage at sensor level for En-route Surveillance

SUR01-ASP02

Provide radar coverage for High ComplexityTMAs

1.1.2 Basic Provide radar coverage for High ComplexityTMAs - basic level

SUR01-ASP03

Implement the means to support aharmonised European Radar SurveillanceInfrastructure Performance AnalysisProgramme

1.1.3 Basic+ Adv

Implement the means to support a harmonisedEuropean Radar Surveillance InfrastructurePerformance Analysis Programme

SUR01-ASP04

Provide communication support for radarrelated data exchange

2.3.5 Stage1

Provide Communication Support for radarrelated data exchange � Stage 1

SUR01-ASP05

Provide continuous radar coverage ofconsistent performance at sensor level foren-route surveillance

1.1.4 Adv Provide continuous radar coverage ofconsistent performance at sensor level for En-route Surveillance

SUR01-ASP06

Provide radar coverage for high complexityTMAs

1.1.2 Adv Provide radar coverage for High ComplexityTMAs - advanced level

SUR01-ASP07

Provide radar data processing 1.3.1 Basic+ Adv

Provide Radar Data Processing

SUR01-ASP08

Provide vertical tracking 1.3.4 Provide vertical tracking

SUR02-ASP01

Implement ground Mode S interrogators. 1.2.1

2.3.5 Stage2

Provide coverage at sensor level for the initialimplementation of Mode S EnhancedSurveillance

Provide Communication Support for radarrelated data exchange � Stage 2 (Initial ModeS Area)

SUR03-ASP01

Provide multi radar surveillance dataprocessing and distribution

1.3.7 Provide Multi-Radar Surveillance DataProcessing and Distribution

ECIP � YEARS 2002 TO 2006 - LEVEL 2 ANNEX B

B-1

ANNEX B - ACRONYMS & ABBREVIATIONS

ACC Area Control CentreACAS Airborne Collision Avoidance SystemACG ATM CNS Consultancy Group (EUROCONTROL)ADEXP ATS Data Exchange PresentationAEA Association of European AirlinesAIC Aeronautical Information CircularAIP Aeronautical Information PublicationAIS Aeronautical Information ServicesAMAN Arrival ManagerANS Air Navigation ServicesARINC Aeronautical Radio Incorporated (US)A-SMGCS Advanced Surface Movement Guidance and Control SystemASAS Airborne Separation Assurance SystemASM Airspace ManagementATC Air Traffic ControlATCC Air Traffic Control CentreATCO Air Traffic ControllerATFM Air Traffic Flow ManagementATM Air Traffic ManagementATS Air Traffic ServicesAUW All Up WeightB-RNAV Basic - Area NavigationCAMOS Centralised ARTAS Maintenance and Operational SupportCDM Collaborative Decision-MakingCEAC Committee for European Airspace Co-ordinationCEATS Central European Air Traffic ServicesCFMU Central Flow Management UnitCIP Convergence and Implementation ProgrammeCNS Communications, Navigation and SurveillanceCODA Central Office of Delay AnalysisCOG Programme Co-ordinating Group of the ICAO European Air Navigation Planning

GroupCRCO Central Routes Charges OfficeDMAN Departure ManagerEAD European AIS Data baseEAG European ATFM GroupEANPG FMG European Air Navigation Planning Group Frequency Management GroupEATCHIP European Air Traffic Control Harmonisation and Integration ProgrammeEATMP European Air Traffic Management ProgrammeEC European CommissionECAC European Civil Aviation ConferenceECIP European Convergence and Implementation PlanEFDP European Flight Data ProcessingENPRM European Notice of Proposed Rule-MakingESARR EUROCONTROL Safety Regulatory RequirementETFMS Enhanced Tactical Flow Management SystemEUR European RegionEWP European Air Traffic Management Programme Work ProgrammeFAP Future ATM ProfileFDPS Flight Data Processing SystemFIR Flight Information RegionFL Flight LevelFMP Flow Management PositionFMS Flight Management SystemFUA Flexible Use of Airspace(Concept)GAT General Air TrafficGBAS Ground Based Augmentation SystemGNSS Global Navigation Satellite SystemHMI Human Machine InterfaceHRM Human Resources ManagementICAO International Civil Aviation OrganisationILS Instrument Landing SystemISO International Organisation for StandardisationITU International Telecommunications UnionJAA Joint Aviation Authorities

ECIP � YEARS 2002 TO 2006 - LEVEL 2 ANNEX B

B-2

MATSE ECAC Transport Ministers� meeting on the Air Traffic System in EuropeMASP Minimum Aviation Specification PerformanceMET MeteorologyMSSR Monopulse Secondary Surveillance RadarNAV NavigationNATO North Atlantic Treaty OrganisationOAT Operational Air TrafficOJT On the Job TrainingORCAM Originating Region Code Assignment MethodPRC Performance Review CommissionPRU Performance Review UnitR&D Research and DevelopmentRDPS Radar Data Processing SystemRET Rapid Exit Taxi WayROAD Representation of Overall ATM DevelopmentROT Runway Occupancy TimeRNAV Area NavigationRNP Required Navigational PerformanceRVSM Reduced Vertical Separation MinimaSARPs Standards and Recommended PracticesSATCOM Satellite CommunicationsSBAS Satellite Based Augmentation SystemSI Selective IdentificationSMAN Surface Management SystemSMGCS Surface Movement Guidance and Control SystemSPF Strategic Performance FrameworkSRC Safety Regulation CommissionSRU Safety Regulation UnitSSR Secondary Surveillance RadarSTCA Short-Term Conflict AlertTCAS Traffic Alert and Collision-Avoidance SystemTMA Terminal Control AreaUAC Upper Area Control CentreVHF Very High FrequencyWRC World Radio Conference

ECIP � YEARS 2002 TO 2006 - LEVEL ANNEX C

C-1

ANNEX C - REFERENCES

Reference documents relevant to both Level 1 and 2 are as follows:

1. EUROCONTROL Revised Convention;

2. ATM Strategy for the years 2000+ (ATM Strategy 2000+) - Volumes 1 & 2, datedJanuary 2000;

3. EATMS Operational Concept Document (OCD) - Issue 1.1; dated 04 January 1999;

4. Stakeholder Relations Plan for Sectors, Programmes and Accounts,(EUROCONTROL Document: SMI.SPA.PLN-1.0) - Edition 1.0 dated 29 June 1999;

5. EATMP Management Handbook; released effective date 01 January 1998;

6. Index of EATMP Working Arrangements (EUROCONTROL Document: 001201-1) -Edition 1.0, dated 21 August 2000;

7. ATC Capacity Targets � A User Guide � Version 0.5 dated 21 February 2001.

EUROPEAN IMPLEMENTATION AND CONVERGENCE PLAN � YEARS 2002-2006 � LEVEL 2Edition 1.1 - Dated October 2001

EATMP Information Centre Reference: 010627-2