proposal for working arrangements to develop package i of … · 2004. 12. 28. · asas in care...

Proposal for working arrangements to develop Package I of AS/GS applications ASAS in CARE

CARE/ASAS/EUROCONTROL/02-042 - Version 2.1 - July 10, 2003 - CA-02-042(2.1).doc Page 1

CARE/ASAS Action

Activity 5Proposal for working arrangements to

develop Package I of AS/GS applications

Version 2.1 July 10, 2003

Executive SummaryThe objective of the present document is to contribute to the definition of the Master Plan andWorking Arrangements between the various involved parties in the area of Package IAirborne Surveillance/Ground Surveillance (AS/GS) applications. The document is, therefore,a proposed basis for the co-ordinated and harmonised work of the stakeholders for theDevelopment, Validation and Implementation of Package I applications. The document wasreviewed during the consultation process with various stakeholder fora: i.e. EUROCAE WG-51, ADS PSG, ODIAC, JCB and IATA/AEA.

The document focuses on the following areas:

● List of required deliverables (WHAT);

● Interdependencies between the deliverables and overall process (HOW);

● Fora responsible for the drafting, reviewing and approving of deliverables respectively(WHO); and

● Master Plan (WHEN).

The Package I related deliverables cover:

● Operational and technical documents;

● Development, Validation, Implementation Planning and Co-ordination phases; and

● Regional (e.g. European) as well as international (e.g. ICAO) activities.

The methodology proposed for the work towards Package I applications is EUROCAEED78A/RTCA DO-264, which is widely supported by the stakeholders and was also used forthe Data Link/CPDLC work.

For each deliverable the following groups are identified: a Drafting Group, Review Groupsand an Approving Group.

A Master Plan is also presented in the document, including all the activities towards PackageI implementation. The foreseen date for start of ECAC implementation is 2007.

Whilst the document focuses on Package I, it also reflects the need to continue the work onthe other Packages (e.g. Feasibility), in order to provide a longer-term view with respect toapplications, technology and corresponding investments. The Working Arrangements andMaster Plan proposed in this document are rather generic and can serve as an input for theactivities on the subsequent Packages as well.

ASAS in CARE Proposal for working arrangements to develop Package I of AS/GS applications

Page 2 CARE/ASAS/EUROCONTROL/02-042 - Version 2.1 - July 10, 2003 - CA-02-042(2.1).doc

The document will be provided to the relevant EUROCONTROL Programme leading thework towards implementation of Package I AS/GS applications. This Programme should beresponsible for the development, validation and implementation of Package I in ECAC, whilstensuring global interoperability. It should be supported by groups such as the so-calledRequirements Focus Group (RFG).

The present document should be seen as an important input for the elaboration of a moredetailed Edition of the Master Plan and the preparation of the Programme Managementbaseline documentation by the Package I related Programme. A list of remaining issues havebeen identified, one of them is to ensure the close involvement of all categories ofstakeholders as early as possible.



Table of contents1. Introduction ..............................................................................................................................................5

1.1. Background........................................................................................................................................51.2. Objectives and Scope of the Document ............................................................................................51.3. References..........................................................................................................................................6

2. List of Deliverables (“WHAT”) ..............................................................................................................72.1. Introduction .......................................................................................................................................72.2. Group 1: Strategy, Concept, and Operational Requirements..........................................................7

2.2.1. EUROCONTROL ATM 2000+ Strategy.......................................................................................72.2.2. Packages of GS/AS Applications ...................................................................................................72.2.3. Concept of Operations (CONOPS) ................................................................................................82.2.4. Operational Requirements..............................................................................................................8

2.3. Group 2: Determination of Co-ordinated Requirements.................................................................82.3.1. Application Descriptions (OSED)..................................................................................................82.3.2. SPR and INTEROP ........................................................................................................................8

2.4. Group 3: MASPS, MOPS, Systems and Products............................................................................82.4.1. ASA/GSA MASPS.........................................................................................................................82.4.2. System Architecture .......................................................................................................................82.4.3. ADS-B and TIS-B MASPS ............................................................................................................82.4.4. Sub-system Specifications..............................................................................................................82.4.5. Equipment MOPS...........................................................................................................................92.4.6. Ground System Standards ..............................................................................................................92.4.7. Ground and Airborne Products.......................................................................................................9

2.5. Group 4: Qualification, Implementation and General Deliverables ..............................................92.5.1. Master Plan.....................................................................................................................................92.5.2. Validation Deliverables..................................................................................................................92.5.3. Business Case .................................................................................................................................92.5.4. Safety Assessment of Services .......................................................................................................92.5.5. European Convergence and Implementation Plan (ECIP) .............................................................92.5.6. International Standards and Guidance Material ...........................................................................10

3. Interdependencies between the Deliverables (“HOW”) .....................................................................11

4. Responsible Fora per Deliverable (“WHO”).......................................................................................134.1. Principles .........................................................................................................................................134.2. Drafting, Reviewing and Approving Groups..................................................................................14

4.2.1. Introduction ..................................................................................................................................144.2.2. EUROCONTROL European ATM Systems and Convergence (ESC) Business Division ..........144.2.3. EUROCONTROL Package I Programme ....................................................................................144.2.4. Requirements Focus Group (RFG)...............................................................................................144.2.5. European Organisation for Civil Aviation Equipment (EUROCAE) ..........................................144.2.6. European Commission Joint Co-ordination Board (JCB)............................................................154.2.7. International Civil Aviation Organisation (ICAO).......................................................................154.2.8. Joint Airworthiness Authority (JAA)...........................................................................................154.2.9. European Telecommunications Standards Institute (ETSI) .........................................................15

4.3. Deliverables and corresponding Drafting, Reviewing and Approving Groups ............................154.3.1. Group 1: Deliverables related to Strategy, Concept, and Operational Requirements..................154.3.2. Group 2: Deliverables related to the Determination of Co-ordinated Requirements...................164.3.3. Group 3: Deliverables related to MASPS, MOPS, Systems and Products ..................................164.3.4. Group 4: Deliverables related to Qualification, Implementation and General Deliverables .......17



5. Master Plan (“WHEN”).........................................................................................................................185.1. Introduction .....................................................................................................................................185.2. Towards Implementation of Package I of AS/GS Applications ....................................................185.3. Beyond Implementation of Package I of AS/GS applications.......................................................195.4. Roadmap ..........................................................................................................................................19

6. Important issues .....................................................................................................................................206.1. Introduction .....................................................................................................................................206.2. Organisational issues ......................................................................................................................206.3. Package I issues...............................................................................................................................206.4. Implementation issues.....................................................................................................................20

7. Concluding remarks...............................................................................................................................21

Annex A Overview of EUROCAE ED78A/RTCA DO-264 Methodology.............................................23

Annex B Detailed Description of List of Deliverables (“WHAT”) ........................................................25B.1 ATM 2000+ Strategy incl. Operational Improvements enabled by AS/GS Package I.....................25B.2 Packages of GS/AS Applications......................................................................................................25B.3 Concept of Operations (CONOPS) ..................................................................................................25B.4 Operational Requirements ...............................................................................................................26B.5 Application Descriptions (OSED)....................................................................................................26B.6 SPR and INTEROP...........................................................................................................................26B.7 ASA/GSA MASPS .............................................................................................................................27B.8 System Architecture..........................................................................................................................27B.9 ADS-B and TIS-B MASPS ................................................................................................................27B.10 Sub-system Specifications ................................................................................................................27B.11 ARINC ..............................................................................................................................................27B.12 Equipment MOPS.............................................................................................................................28B.13 Ground System Standards ................................................................................................................28B.14 Master Plan ......................................................................................................................................28B.15 Validation Deliverables....................................................................................................................28B.16 Business Case ...................................................................................................................................28B.17 Safety Assessment of Services ..........................................................................................................29B.18 European Convergence and Implementation Plan (ECIP)..............................................................29B.19 International Standards and Guidance Material .............................................................................30B.20 JAA ...................................................................................................................................................32

Annex C Detailed Depiction of Interdependencies between the Deliverables (“HOW”)....................33

Annex D Detailed Master Plan for ASA/GSA Package I Implementation (“WHEN”).......................34

Annex E Acronyms ....................................................................................................................................36



CARE/ASAS Action

Activity 5Proposal for working arrangements to

develop Package I of AS/GS applications

Version 2.1 July 10, 2003

1. Introduction

1.1. Background

In parallel with the work on the description of Package I applications [3], a strong request wasexpressed by the stakeholders in various fora, including EUROCONTROL groups and the Joint Co-ordination Board (JCB) in particular, that a Master Plan and Working Arrangements between thevarious involved parties be developed. This would ensure a harmonised and efficient path towardsPackage I implementation and maximum synergy. CARE/ASAS was tasked to draft this documentand proceed to a wide consultation, involving various stakeholder groups, in order to achieveconsensus. The actual drafting work was performed by an ad-hoc drafting group of experts fromEUROCONTROL, ANSPs, industry, airspace Users etc. The document was reviewed during theconsultation process with various stakeholder fora: i.e. EUROCAE WG-51, ADS PSG, ODIAC, JCBand IATA/AEA.

1.2. Objectives and Scope of the Document

The objective of the present paper is to contribute to the definition of the Master Plan and WorkingArrangements between the various involved parties in the area of Package I AirborneSurveillance/Ground Surveillance (AS/GS) applications. In this way, duplication of activities will beavoided and overall efficiency will be increased.

The document focuses on the following areas:

● List of required Deliverables (WHAT);

● Interdependencies between the Deliverables and overall process (HOW);

● Fora responsible for the drafting, reviewing and approving of Deliverables (WHO); and

● Master Plan (WHEN).

The current Edition of the paper takes into account the comments which have been received so farby the review of previous Editions from a number of stakeholder groups such as:

i. EUROCAE WG-51;

ii. EUROCONTROL ADS Programme Steering Group;

iii. Operational Development of Integrated Surveillance and Air/Ground Data Communications(ODIAC) Group;

iv. Joint Co-ordination Board (JCB) of the European Commission funded ADS-B related projects;and

v. IATA/AEA.



It is noted that whilst the document is a proposal focusing on Package I, it should be viewed in thewider ATM/CNS context. This includes consideration of other relevant activities expected to takeplace within the same time horizon. The document reflects also the need to continue the work on theother Packages (e.g. Feasibility), in order to provide a longer-term view with respect to applications,technology and corresponding investments. It is noted that the Working Arrangements and MasterPlan, which are proposed in the paper, are rather generic and they could be used as input for thework on Package II and beyond.

1.3. References

[1] EUROCONTROL EATMP FCO.ET1.ST07.DEL02 ATM2000+ Strategy Edition 2003

[2] Principles of Operation for the Use of Airborne Separation Assurance Systems (PO-ASAS) Edition 7.1 June 19, 2001

[3] CARE/ASAS Activity 5 Description of a first Package of Ground Surveillance/AirborneSurveillance applications CARE/ASAS/EUROCONTROL/02-040 Version 2.2 September 30,2002 Package I CA-02-040(2.2).doc

[4] Guidelines for approval of the provision and use of Air Traffic Services supported by DataCommunications EUROCAE/78A-RTCA/DO-264 2000



2. List of Deliverables (“WHAT”)

2.1. Introduction

The clear vision towards AS/GS application and ADS-B implementation has as an essentialprerequisite the harmonisation of the required deliverables, i.e. the agreement of the stakeholders onthe list of required deliverables as well as on their content.

These deliverables cover:

● Operational and technical documents, as well as products;

● Development, Validation, Implementation Planning and Co-ordination phases; and

● Regional (e.g. European) as well as international (e.g. ICAO) activities.

In general, all deliverables (i.e. including the standards) before validation have the status of draft.Following validation, they are upgraded to final.

The deliverables, which have to be developed and harmonised, are listed and briefly introduced in thefollowing subsections. A more detailed description of each of the deliverables can be found in AnnexB. Note: In the following sub-sections, hyperlinks are inserted at the end of the first paragraph thatlead to the respective sub-sections in Annex B.

The deliverables have been clustered in four groups:

● Group 1: Deliverables related to the Strategy, the Concept, and the Operational Requirements.They provide the top-down inputs of the whole process.

● Group 2: Deliverables related to the determination of co-ordinated requirements. They are basedon the ED78A/DO-264 methodology.

● Group 3: Deliverables related to technical standards, systems and products. This includesMASPS, MOPS and other system documents, such as system functional architecture andspecifications.

● Group 4: Deliverables related to qualification (e.g. validation deliverables, CBA, Safetyassessment), implementation deliverables (e.g. ECIPs) and general deliverables, incl.international standards and guidance material (e.g. ICAO SARPs).

2.2. Group 1: Strategy, Concept, and Operational Requirements

2.2.1. EUROCONTROL ATM 2000+ Strategy The EUROCONTROL ATM 2000+ Strategy [1], incl. the Operational Improvements (OIs) Roadmap,as well as the Operational Concept document (OCD) are the baseline for an ECAC-wide consensuson the future ATM/CNS system in Europe. The ATM 2000+ Strategy (Edition 2003) is completed,whereas the OCD is currently being updated. [B.1]

In general, the GS/AS applications included in Package I are expected to contribute to the OIs and toachieve significant benefits in period 3 of the ATM 2000+ Roadmap and beyond.

2.2.2. Packages of GS/AS ApplicationsThis deliverable includes the list and description of Ground and Airborne Surveillance Applicationswhich are clustered to form packages of applications. [B.2]

The document, providing the definition of Package I applications [3], was reviewed and endorsed byall Review bodies (i.e. EUROCAE WG-51, ADS PSG, ODIAC, JCB, IATA/AEA) and was publishedwith cover note by the Joint Co-ordination Board.

The document will have to be updated:

● To reflect the results of harmonisation, validation incl. safety assessment and costs/benefitsanalysis of the Package I applications; and



● To include the list and description of Ground and Airborne Surveillance Applications foreseen inthe future packages.

2.2.3. Concept of Operations (CONOPS)The EUROCONTROL COOPATS document which is currently being updated will provide theConcept of Operations for Package I, covering both operational and technical aspects. The CONOPSwill (amongst others) place Package I in the wider ATM/CNS context. [B.3]

2.2.4. Operational RequirementsThis deliverable will define in particular the operational requirements for the data-link services whichare necessary to enable the operational applications of Package I. [B.4]

2.3. Group 2: Determination of Co-ordinated Requirements

2.3.1. Application Descriptions (OSED)The Operational Services and Environment Definition (OSED) is a key deliverable in the context ofthe Co-ordinated Requirements Determination of this methodology and is used to describe theforeseen applications, procedures and their environment. In a fully top-down approach, theOperational Requirements and Service Descriptions are expected to be used as an input to theOSED development. [B.5]

The EUROCAE ED 78A/RTCA DO-264 methodology [Annex A] is going to support this activity.

2.3.2. SPR and INTEROPThe Safety and Performance Requirements (SPR) as well as the Interoperability (INTEROP)documents are major inputs for the development, validation, as well as for airworthiness andoperational approval. As for the OSED, EUROCAE ED 78A/RTCA DO-264 methodology is expectedto be used in support of the development of these documents. [B.6]

2.4. Group 3: MASPS, MOPS, Systems and Products

2.4.1. ASA/GSA MASPSThe Minimum Aviation System Performance Standards (MASPS) for the Airborne Surveillance andGround Surveillance Applications (ASA/GSA) are based on the OSED, SPR and INTEROPdocuments, which could be included as an Appendix of this deliverable. The ASA/GSA MASPS willaddress the complete set of applications and will allow the grouping of applications for which differentcriteria exist. [B.7]

The ASA/GSA MASPS are, basically, requirement synthesis documents which will be used as inputfor regulatory and ICAO documents, for the co-ordination with relevant RTCA work and as input forthe work on future Packages of applications.

2.4.2. System ArchitectureThe work on overall System Architecture will focus on the functional aspects of the system. [B.8]

2.4.3. ADS-B and TIS-B MASPS The MASPS for ADS-B and TIS-B might be two documents providing performance requirementscorresponding to the characteristics of ADS-B and TIS-B respectively. It is in the EUROCAE remit todecide on whether ADS-B and/or TIS-B MASPS are going to be developed (or not). MASPS foradditional functions may be developed, if necessary. [B.9]

2.4.4. Sub-system SpecificationsThis set of deliverables will focus on the ground system and will include the Specifications of thevarious sub-systems. Airborne systems are considered to be covered through e.g. ARINC form andfit equipment characteristics. [B.10, B.11]



2.4.5. Equipment MOPS The Minimum Operational Performance Standards (MOPS) provide performance requirementscorresponding to particular equipment and is used to assess its capability to meet the definedrequirements. [B.12]

2.4.6. Ground System StandardsThese deliverables will cover the standardisation of ground sub-systems. [B.13]

2.4.7. Ground and Airborne Products

2.4.7.1. Ground ProductsThe ground products comprise components such as Ground Stations, Ground Networks,Surveillance Data Processing and Distribution Systems, TIS-B servers and upgraded ControllerWorking Positions.

2.4.7.2. Airborne ProductsThe airborne products comprise components such as data radios, airborne surveillance dataprocessing and distribution (Traffic Computer), and CDTI systems.

2.5. Group 4: Qualification, Implementation and General Deliverables

2.5.1. Master PlanThe Master Plan is described in the present document. [B.14]

2.5.2. Validation DeliverablesThe main deliverable is the report of the Operational and Technical Validation of Package Iapplications and enablers. It will (amongst others) include results with respect to capacity, efficiencyand other improvements from Package I, as well as the safety assessment. Other deliverables ofimportance are the Validation Strategy, Planning, Methods and Tools. [B.15]

2.5.3. Business CaseThis deliverable is important to support the business decisions with respect to Package I. It shouldinclude the cost and benefits elements related to the implementation of Package I Airborne andGround Surveillance applications so as to allow local or stakeholder specific business cases to bedeveloped, and be extended to cover other issues (strategic, institutional, etc.) [B.16]

2.5.4. Safety Assessment of ServicesTwo deliverables are foreseen in this context, i.e. the Safety Policy and the Safety Plan. The SafetyPolicy document for Package I will specify the policy statements and principles for a harmonisedapproach to Safety Management regarding the different stakeholders participating in Package I.Safety planning separates the regulatory aspects of the overall development process intomanageable tasks that can be accomplished in a logical and sequential manner. These twodocuments are expected to be used by the individual stakeholders as the foundation for their localsafety related work. [B.17]

2.5.5. European Convergence and Implementation Plan (ECIP)The ECIP related deliverables describe the commonly agreed actions to be taken by all stakeholders,in order to meet certain objectives. In this case, they will focus on the Implementation of Package IAS/GS applications and corresponding enablers. Tentative ECIP Objectives have already beendrafted for some of the Package I applications, and the consultation process for these Objectives hasbeen initiated. [B.18]



2.5.6. International Standards and Guidance Material The use of the applications on a worldwide basis requires the standardisation and guidance at aglobal level by ICAO (Standards and Recommended Practices, Manuals and Circulars) and JAAwhen airborne aspects are concerned (certification documents). The specific documents of JAA,which are applicable for Package I, include Temporary Guidance Leaflets and related AdvisoryCircular Joints. It should be noted that RFG documents could support the production of JAAdocuments. International standards are essential for achieving the requirement of globalinteroperability. [B.19, B.20]



3. Interdependencies between the Deliverables (“HOW”)The interdependencies between the groups of deliverables are primarily driven by the EUROCAEED78A/RTCA DO-264 methodology [Annex A], with some tailoring which is necessary in the case ofPackage I AS/GS applications.

The following remarks can be made in this respect:

i. The relationship between the groups of deliverables, as introduced in section 2.1, is shown inFig. 1.

Strategy, Concept andOperational Requirements

MASPS, MOPS,Systems and Products

OSED, SPR and INTEROP(Co-ordinated Requirements

Determination)

Feed forward flowFeed backward flow

Qualification, Implementationand General Deliverables

Fig. 1: Relationship between the groups of Deliverables

The OSED, SPR and INTEROP are documents that are produced after a number of iterations ofthe corresponding processes, with feedback between them. This means that the final OSED willbe produced only after the finalisation of the SPR and INTEROP processes and the inclusion ofthe relevant feedback information. For example, it could be foreseen that the initial Edition ofthese documents addresses only a subset of applications, whereas the intermediate Editioncovers a larger number of applications and the final Edition addresses the full set ofapplications. The role of industry, in particular, in the preparation of SPR and INTEROP isessential. This relationship of OSED, SPR and INTEROP is depicted in Annex A.

ii. The work on the applications requirements could be focussed/prioritised with respect to criteriasuch as most stringent applications, most mature applications or most available resources.

iii. The validation work has also an iterative character and provides feedback to the developmentwork and the update of the relevant deliverables.

iv. The ASA and GSA MASPS are mainly driven by the Co-ordinated Requirements documents(OSED, SPR, INTEROP), by grouping the Airborne and Ground Applications related materialrespectively.

v. The functions on which MASPS and Specifications will be produced (ADS-B, TIS-B etc.) will bedefined, following the work on the functional architecture.



vi. The MOPS have as main inputs the MASPS documents for the functions which are supportedby the corresponding equipment.

vii. In the process of preparation of the various deliverables, use will be made of the existingrelevant input documents from the various activities, in order to maximise efficiency.

viii. The co-ordination with international fora, including ICAO, FAA and RTCA, is essential in order toachieve the required global interoperability.



4. Responsible Fora per Deliverable (“WHO”)

4.1. Principles

The principles for the allocation of responsible working groups per deliverable are as follows:

i. The currently existing working arrangements will be used to the maximum possible extent, i.e.the creation of new groups/task forces etc. should be generally avoided.

ii. For each deliverable the following groups should be identified, preferably from within the existingworking arrangements:

– Drafting Group;

– Review Groups; and

– Approving Group.

iii. The Drafting Group and Approving Group should be unique per each Deliverable.

iv. The Drafting Groups should have an ad-hoc character and use as much as possible the e-mailfor the exchange of comments and other information. In general, they should be initiated and co-ordinated by a member of the Approving group.

v. More than one Review Group per Deliverable are necessary, in order to ensure the widestpossible consultation and consensus building. Ad-hoc joint meetings could be convened toenhance the review process.

Fig. 2 depicts the relationships between the Drafting, Review and Approving fora.

TOWARDS HARMONISATIONECAC & Global Consensus Building

DraftingGroup

Review Group 1

Review Group 2

Review Group n

Approving Group

Fig. 2: Consultation Process and Group Structure



4.2. Drafting, Reviewing and Approving Groups

4.2.1. IntroductionThe overview of the main Drafting, Review and Approving groups related to Package I AS/GSapplications is given below. Stakeholders are involved through their regular and well-establishedparticipation in the various groups.

It is acknowledged that the nature of the groups is heterogeneous (e.g. agencies, standardisationbodies, others). Nevertheless, they were identified as the key players for the successfulimplementation of Package I applications.

The respective roles of the various groups are detailed in section 4.3. It is essential that the groupswork together to achieve the common objective.

4.2.2. EUROCONTROL European ATM Systems and Convergence (ESC) Business DivisionThe objective of the EUROCONTROL European ATM Systems and Convergence (ESC) BusinessDivision (evolution of the Strategy, Concept and System SCS Unit) is to deliver and assess newconcepts and ideas that will feed the EUROCONTROL ATM 2000+ Strategy as well as to work onCapacity Enhancement and ECIP. This includes the Business Divisions work on the EATMPRoadmap, the R&D and validation co-ordination as well as the overall ATM/CNS architecturedefinition.

4.2.3. EUROCONTROL Package I ProgrammeIn the context of this document, the hypothesis has been taken that a EUROCONTROL Programmeoriented towards implementation of Package I is created. This Programme is called hereafter theEUROCONTROL Package I Programme.

The Package I related Programme of EUROCONTROL should be responsible for the development,validation and implementation of Package I applications and enablers in ECAC. A very importantobjective of this Programme is to ensure strong co-ordination and efficiency in the further requiredwork on Package I, as well as global interoperability.

The Programme should be in charge of the Master Plan and its implementation. It should be led by aProgramme Steering Group which will involve all categories of stakeholders, such as ANSPs,airspace users, and industry, also in order to get the required stakeholder buy-in.

4.2.4. Requirements Focus Group (RFG)The drafting of the Co-ordinated Requirements documents will be undertaken by the RequirementFocus Group (RFG) which will focus on the following deliverables:

● Operational Services and Environment Definition (OSEDs);

● Safety and Performance Requirements (SPR); and

● Interoperability (INTEROP).

This Group has a very important role with respect to the requirement for global interoperability. Itshould include experts from EUROCONTROL, EUROCAE, RTCA and FAA. The group will apply aCo-ordinated Requirements Determination approach in order to establish and allocate requirementsthat require co-ordination among the various stakeholders involved in the process towards theimplementation of the overall, highly integrated, Package I air-ground system.

The RFG group is essential for the development and allocation of these requirements; and hence hasbeen specifically established for this purpose. It is noted that the various stakeholders are includedthrough the above listed organisations.

4.2.5. European Organisation for Civil Aviation Equipment (EUROCAE)The European Organisation for Civil Aviation Equipment is responsible for the preparation andpublication of standards for aviation systems and equipment. These standards include MASPS,MOPS etc. The Working Group which is responsible for ADS-B and the Package I related activities is



WG-51, supported by its Sub-Groups. It should be noted that EUROCAE is working jointly with RTCAon the elaboration of Package I standards.

4.2.6. European Commission Joint Co-ordination Board (JCB) The Joint Co-ordination Board was created to co-ordinate research, development and validation workperformed by the European Commission funded ADS-B programmes and projects, and to contributeto expedited implementation.

4.2.7. International Civil Aviation Organisation (ICAO)The International Civil Aviation Organisation and its relevant panels (e.g. OPLINK, SCRSP) areresponsible for (amongst others) the development of standards and guidance material at internationallevel. These are essential with respect to the requirement of global interoperability.

4.2.8. Joint Airworthiness Authority (JAA)The Joint Airworthiness Authority is responsible for the development and implementation of commonsafety regulatory standards and procedures in Europe.

4.2.9. European Telecommunications Standards Institute (ETSI)The European Telecommunications Standards Institute has as its mission the production oftelecommunications standards which will be used in Europe and beyond.1

4.3. Deliverables and corresponding Drafting, Reviewing and Approving Groups

4.3.1. Group 1: Deliverables related to Strategy, Concept, and Operational Requirements

Deliverable Drafting Group Review Groups Approving Group

ATM 2000+ Strategy incl.Operational Improvements

OCD

EUROCONTROL(ESC Business Div.)

All Stakeholders EUROCONTROL(ESC Business Div.)

Packages of GS/ASApplications

CARE/ASAS JCBEUROCAEIATA/AEA

EUROCONTROL

Concept of Operations(CONOPS)

JCBIATA/AEA

EUROCONTROL

Operational Requirements

EUROCONTROL (Pack. I Progr.)

JCBEUROCAEIATA/AEA

EUROCONTROL


1 It is noted that ETSI has also established an aeronautical group (ERM TG25) which is concerned withElectromagnetic compatibility and Radio spectrum Matters (ERM).



4.3.2. Group 2: Deliverables related to the Determination of Co-ordinated Requirements


Application Descriptions(OSED)

SPR

INTEROP

RFG JCBEUROCAEIATA/AEA

EUROCONTROLJAA


EUROCAE

4.3.3. Group 3: Deliverables related to MASPS, MOPS, Systems and Products


ASA/GSA MASPS EUROCAE(WG51)

JCBIATA/AEA

EUROCONTROLEUROCAE

JAA

EUROCAE

System Architecture EUROCONTROL(ground - Pack. I

Progr.)EUROCAE(airborne)

JCBEUROCONTROL

EUROCAE

EUROCONTROL (ground - Pack. I

Progr.)EUROCAE (airborne)

ADS-B MASPS

TIS-B MASPS

EUROCAE(WG51)

JCBEUROCONTROL

EUROCAEJAA

EUROCAE

Sub-systems Specifications EUROCONTROLARINC

JCB (ground)EUROCONTROL

(ground)

EUROCONTROL(ground - Pack. I

Progr.)ARINC

(airborne)

Equipment MOPS EUROCAE(WG51)

JCBEUROCONTROL

EUROCAEJAA

EUROCAE

Ground System Standards EUROCONTROL(Pack. I Progr.)

ETSI

JCBEUROCONTROL

ETSI

EUROCONTROL(for ASTX)

ETSI (for EN)

Note: The ground and airborne systems are not listed in the Table as they are not to be describedfrom the perspective of drafting, reviewing and approving processes. It is considered that productionand certification is the business of industry, operators and regulators and, as such, is not seen as anissue for harmonisation among all stakeholders in the context of the Master Plan. The same appliesfor the end-to-end approval of the applications (ESARR4 process).



4.3.4. Group 4: Deliverables related to Qualification, Implementation and General Deliverables


Master Plan CARE/ASAS

Validation deliverables

Business Case for ECAC

JCBEUROCAEIATA/AEA

EUROCONTROL

Safety Policy

Safety Plan

EUROCAEEUROCONTROL

ECIP related documents

EUROCONTROL(Pack. I Progr.)

All stakeholders

EUROCONTROL(Pack. I Progr.)

ICAO Standards andGuidance Material

ICAO JCBIATA/AEAEUROCAE

EUROCONTROL

ICAO

JAA Documents JAA n/a JAA



5. Master Plan (“WHEN”)

5.1. Introduction

The Package I Master Plan as introduced in this section and further detailed in Annex D is built uponthe hypothesis of the availability of the required resources. This implies the risk that the planningmight be not achieved if these resources are not available.

5.2. Towards Implementation of Package I of AS/GS Applications

The proposed Master Plan for the implementation of Package I AS/GS Applications in ECAC,foresees the following phases:

● Development;

● Validation;

● Implementation Planning and Co-ordination; and

● Implementation.

This phasing is consistent with typical practices and is in line with the EATMP Lifecycle Model.

During the later part of Validation and in parallel with Implementation Planning & Co-ordinationphase, work on production and certification of the relevant ATM/CNS system elements will takeplace.

The start of implementation should be understood as the start of ECAC implementation of at least asubset of Package I applications using certified products. This means that implementation ofPackage I could take place in more than one step, by grouping subsets of the applications.

Early local implementation is also expected in local areas of ECAC, not necessarily following thecomplete top-down approach of development, validation and implementation planning and co-ordination for ECAC. In this phase, use could be made of local procedures.

For the elaboration of the more detailed Master Plan for Package I AS/GS applications, which will bepresented below, the following main characteristics have been considered:

i. The consistency with the EUROCONTROL ATM 2000+ Strategy and the EATMP ValidationMaster Plan has to be ensured.

ii. The deliverables are grouped in the four groups that have been presented above.

iii. The iterative character of the deliverables has been reflected. Two or three iterations have beenforeseen for most of the core documents such as the OSEDs, SPR, INTEROP, MASPS, MOPSetc.

iv. In general, a baseline draft version of relevant deliverables (including draft standards) should beready at the start of the validation phase. After validation, updates of all deliverables will beavailable, to take into account the validation results. These versions will generally be the finalones.

v. Separate planning is provided for ASA and GSA. Separate planning could be applied forsubsets of the AS/GS applications, in order to capture the possible prioritisation between theapplications. As explained above, this would allow to start work, e.g. on the most stringentapplications which determine the requirements first, while in parallel work could be continued onless demanding applications with less priority. Other prioritisation criteria could be based onmost mature applications or on most available resources.

vi. Currently, only ADS-B and TIS-B MASPS are included.

vii. Currently, only data-link MOPS are included. However other equipment MOPS may be required,as appropriate.

viii. The Plan includes some overlap between Development and Validation lifecycle phases.



The date derived in the Master Plan for the end of Validation and the start of ImplementationPlanning and Co-ordination is around mid-2005. The date derived for the start of Implementation is2007.

The fully detailed Master Plan is presented in Annex D.

5.3. Beyond Implementation of Package I of AS/GS applications

In parallel with the activities on Package I, work continues on Feasibility, Development etc. of theother Packages (Package II and beyond). This approach will provide a strategic view enablinginvestment decisions and will take into account the sizing requirements for subsequent Packages, asearly as possible.

5.4. Roadmap

The above principles are reflected in the Roadmap towards implementation of AS/GS applications,which is shown in Fig. 3. Although, the Roadmap presents fully separated EATMP lifecycle phases toallow a clearer overview, in practice overlap between the phases should be expected.

EATM POIRoadmap

Period 1 Period 2 Period 3 Period 4

2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013+

Development

Validation

ImplementationPlanning

ImplementationEarly Local

Implementations

Feasibility

Package I

Package II

SubsequentPackages

Fig. 3: Roadmap for the Implementation of Airborne Surveillance/Ground Surveillance Applications



6. Important issues

6.1. Introduction

During the development of this document, several important issues have been identified. They willhave to be addressed and resolved in the course of the application of the Working Arrangements andMaster Plan for Package I of Airborne and Ground based Surveillance applications.

These issues are grouped in the following sub-sections.

6.2. Organisational issues

Issue 1: The implementation of Package I application is a complex process and there is a strongneed to co-ordinate the various activities. The document works on the hypothesis that aEUROCONTROL Package I programme (see section 4.2.3) is created and is in charge of this co-ordination. This programme should be operational as soon as possible.

Issue 2: There is a need to ensure close involvement of all categories of stakeholders at an earlystage, in order to address their requirements, increase awareness and facilitate commitment whenrequired. This is particularly true for ANSPs, aircraft operators and the industry. The documentproposes the creation of a Programme Steering Group (see section 4.2.3) to involve all categories ofstakeholders.

Issue 3: Global interoperability is essential for the successful implementation of Package Iapplications. This requirement comes from the airlines and aircraft manufacturers. To facilitate thedevelopment of global operational and technical standards, the document makes the hypothesis ofthe success of the Requirement Focus Group. EUROCONTROL, FAA, EUROCAE and RTCA shouldcommit themselves to the development of the RFG deliverables.

6.3. Package I issues

Issue 4: The planning, as presented in the Master Plan, is based on the hypothesis of the availabilityof sufficient resources. Therefore the planning should be considered optimistic. The lack of resourceswill have the effect of delaying further the implementation of Package I applications.

Issue 5: Applications included in Package I do not have the same level of maturity. Theseapplications will need to be prioritised according to their levels of maturity (e.g. based on OSED andOperational Hazard Assessment). This may help to cope with limited resources without impacting toomuch on the implementation horizon.

6.4. Implementation issues

Issue 6: For safety purposes, Package I applications will need to be certified end-to-end. Therefore,it will be necessary to establish means of compliance for operational approval of AS/GS applications.The document is proposing the use of the EUROCAE ED78A/RTCA DO-264 methodology during thedevelopment process of the applications so as to facilitate later the operational approval of theseapplications by the appropriate authorities.



7. Concluding remarksThe present document is a proposed basis for the co-ordinated and harmonised work of thestakeholders on the Development, Validation and Implementation of Package I Airborne Surveillanceand Ground Surveillance applications.

The paper was reviewed during the consultation process with various stakeholder fora. At the end ofthe Review process, it will be provided to the relevant EUROCONTROL Programme, which will beresponsible for Package I, applications and enablers, as input for the elaboration of a more detailedEdition of the Master Plan and the preparation of the relevant Programme Management baselinedocumentation. Further detailing and refinement will be required and performed by the relevantEUROCONTROL Package I Programme.

Whilst the document focuses on Package I, it reflects the need to continue the work on the otherPackages as well, in order to provide a longer-term view with respect to applications, technology andcorresponding investments. Therefore, this document serves also as input for the activities onPackage II and beyond.



ANNEXES



Annex A Overview of EUROCAE ED78A/RTCA DO-264 MethodologyFollowing the introduction, by ICAO (International Civil Aviation Organisation), of the Communication,Navigation and Surveillance/Air Traffic Management (CNS/ATM) concept, it has been clearlyidentified that use of data communication will require an extensive co-ordination between the involvedstakeholders and appropriate authorities to perform the intended function, safely. Stakeholdersinclude ANSPs, airborne and ground equipment manufacturers, airframe manufacturers, and airlines.Furthermore, it was also identified that co-ordination was necessary to ensure compatibility betweenvarious national implementations. ED-78A/DO-264 Guidelines for approval of the provision and Useof Air Traffic Services supported by data communication was developed jointly by EUROCAE WG-53 and RTCA SC-189 to fulfil this need. As a matter of fact, application of this standard shouldensure that the process applied for co-ordinating implementation requirements and qualification fordifferent types of approvals is complete.

In addition, it provides means to establish the operational, safety, performance, and interoperabilityrequirements for ATS supported by data communications, to assess their validity, and to qualify therelated CNS/ATM system. The guidance material considers the allocations of the operational, safety,performance, and interoperability requirements to the elements of the CNS/ATM system. Theseinclude ground-based elements, operational procedures, including human elements, and aircraftequipage.

This section presents an overview of the ED-78A/DO-264 methodology for the development ofrequirements, which will be used to derive the appropriate standards.

The first step of the methodology consists in the development of an OSED (Operational Service andEnvironment Definition) that describes the environment (in terms of traffic and airspacecharacteristics) and the anticipated services along with the anticipated benefits and constraints. Fromthis document, three parallel and interactive processes will start (as shown in Fig. A1):

● The Operational Safety Assessment (OSA): during this sub-process, the safety objectives will beestablished taking into account the potential operational hazards and the severity of theirconsequences will allocated to various stakeholders and validated.

● The Operational Performance Assessment (OPA): as for the OSA, during the process, theperformance objectives to perform the intended functions will be defined, allocated and validated.

● The Interoperability Assessment (IA): which should define the minimum technical and functionalrequirements for ensuring compatibility among the various elements of the CNS/ATM systemusing a specific technique or technology.

Those three assessment processes will imply refinement of the initial OSED and end with the releaseof three major outputs:

● The final OSED;

● The SPR, which lists the Safety and Performance Requirements; and

● The Interoperability Document, which lists the interoperability requirements.

Those three documents will then be used to specify the equipment, derive the appropriate standardsand get the necessary approvals to operationally implement the new services.

It shall be noted that ED78-A/DO-264 is only a guidance material that does not have the force of law.It shall be considered as one means, resulting from a consensus reached within the aviationcommunity, to obtain approval, but not the only one.



Fig. Annex-1: Overview of Co-ordinated Requirements Determination



Annex B Detailed Description of List of Deliverables (“WHAT”)

B.1 ATM 2000+ Strategy incl. Operational Improvements enabled by AS/GSPackage IThe EUROCONTROL ATM 2000+ Strategy incl. the Operational Improvements (OIs) Roadmap,which has recently been updated, as well as the Operational Concept document (OCD), which iscurrently updated by EATMP, are the baseline for an ECAC-wide consensus on the future ATM/CNSsystem in Europe. The list of specific OIs, which are enabled, by the Package I AS/GS Applicationsand ADS-B were identified at an early stage of the work towards Package I. This will ensure theconsistency of the AS/GS Package I related work with the overall ATM/CNS packages, representedby the grouping of Operational Improvements of the ATM 2000+ Strategy and correspondingRoadmap.

The EUROCONTROL ATM 2000+ Strategy provides the packages of the OperationalImprovements in ECAC in the following four periods:

● Period 1: 2001-2004;

● Period 2: 2005-2007;

● Period 3: 2008-2011; and

● Period 4: 2012-2020.

The AS/GS Package I applications enable significant benefits in the Period 3 of the ATM 2000+Roadmap and beyond.

B.2 Packages of GS/AS ApplicationsThis deliverable includes the following:

● List of Ground Surveillance/Airborne Surveillance Applications which are included in Package I;

● Link of Package I applications to the specific ATM 2000+ Strategy OIs/Roadmap;

● Rationale for selection of Package I applications; and

● Application high-level description.

B.3 Concept of Operations (CONOPS)This deliverable will define the Concept of Operations for Package I AS/GS, covering bothoperational and technical aspects. These have to be analysed as a function of:

● Airspace types (as proposed in the Airspace Strategy); and

● Flight phases from gate-to-gate (TMA, En-Route and airport operations).

The operational aspects of the Concept should be based on the Co-operative ATS (COOPATS)Concept. It should (amongst others) fully clarify the complementary role of Package I applicationswith the other applications (e.g. flight plan co-ordination), which will be available in the sameRoadmap period, thus providing a holistic gate-to-gate view.

The technical aspects of the Concept will include the roles and relationships of ADS-B, TIS-B, ADS-C, classical radars, multilateration, processing and distribution systems, data-link services (such asCPDLC) and technologies etc. to enable the Package I applications.

The Concept of Operations should also show the transition path from the current situation to theenvironment with Package I applications. Moreover, the path towards the subsequent Packages ofapplications (i.e. Package II and beyond) should be described.



B.4 Operational RequirementsThis deliverable will define in particular the operational requirements for the data-link services whichare necessary to enable the operational applications of Package I. One defined data-link servicewhich is relevant for Package I Ground Surveillance applications is SAP (System AccessParameters).

A single data-link service could support a number of operational applications of Package I. Anexample of a new service which is currently analysed by ODIAC and will enable applications foreseenwithin Package I is the Air Traffic Situational Awareness (ATSAW) Service.

Depending on the agreed set of Applications, additional data-link service(s) will have to be described,to address issues such as:

● Procedures and phraseologies for nominal and abnormal cases; and

● Security and human factors operational requirements.

All these requirements have to be properly developed in order to ensure the operational acceptabilityof the system.

B.5 Application Descriptions (OSED)The development, validation and implementation work on Package I will be based on the EUROCAEED 78A/RTCA DO-264 methodology (Annex A). The Operational Services and EnvironmentDefinition (OSED) is a key deliverable in the context of the Co-ordinated Requirements Determinationof this methodology and is used to describe the foreseen applications and their environment.

The OSED document results from the so-called operational services and environment informationcapture (OSEIC). The document will include both application and enabler related information.

The OSED document should cover aspects such as:

● Operational Service Description:

– Expected Benefits, Constraints and Human Factors;

– Operating method with and without the proposed change;

– Scenarios; and

– Information Exchanges.

● Operational Environment.

It could be envisaged that the OSEDs consist of a core part which is common for a subset of theapplications (e.g. for all Ground Applications or respectively for all Airborne Applications), as well asspecific parts per application.

B.6 SPR and INTEROPThe Safety and Performance Requirements (SPR) as well as the Interoperability (INTEROP)documents are major inputs for the development, validation, as well as for airworthiness andoperational approval. These documents will be developed also utilising the EUROCAE ED 78A/RTCADO-264 methodology. They will capture the safety, performance and interoperability requirementsrelated to the implementation of the new surveillance application in a specific environment.

After the completion of initial OSEDs, three parallel processes begin for each OSED: These are theOperational Safety Assessment (OSA), the Operational Performance Assessment (OPA) and theInteroperability Assessment (IA), as described in Annex A.

Those processes may require updating the initial OSED. After several iterative assessmentsprocesses, two documents that provide the safety, performance and interoperability requirements willbe released: the SPR (Safety and Performance Requirements) and the Interoperability document[Annex A].

These documents are expected to be used as input to the local implementation activities.



B.7 ASA/GSA MASPSThe MASPS for the Airborne Surveillance and Ground Surveillance Applications (ASA/GSA MASPS)are based, amongst others, on the OSED, which could be included as an Appendix of thisdeliverable.

The ASA/GSA MASPS will address the complete set of applications.

From the OSED that will be released for every AS or GS application, various assessment processes(safety, performance and interoperability) will be performed, in accordance with ED-78A/DO-264, andwill lead to the development of SPR and INTEROP requirements. Such requirements shall then besynthesised and shall form the basis of the ASA/GSA MASPS. The ASA/GSA MASPS will gather theSPR and INTEROP requirements together with applicable assumptions on the environment cross-referenced from the OSED. This document will therefore contain the final result of the minimumconsolidated overall safety, performance and interoperability requirements for the implementationand usage of the applications.

B.8 System ArchitectureThe work on the overall System Architecture will focus on the functional aspects of the system andwill lead to two deliverables:

● Ground Functional Architecture; and

● Airborne Functional Architecture.

On the airborne side, the level of detail for the definition of the architecture will be defined at a laterstage of the work.

B.9 ADS-B and TIS-B MASPS The Minimum Aviation System Performance Standards (MASPS) of ADS-B and TIS-B will be twodocuments providing performance requirements corresponding to the characteristics of ADS-B andTIS-B respectively. They can be used to assess and ensure the feasibility of ADS-B and TIS-B tomeet the corresponding requirements.

The ADS-B and TIS-B MASPS will be derived from the operational documents defined aboveincluding the ASA/GSA MASPS, as well as already existing documentation on ADS-B and TIS-BTechnical Requirements.

MASPS for additional functions may be developed, if necessary.

B.10 Sub-system SpecificationsThis set of deliverables will focus on the ground system and will include the Specifications of thevarious sub-systems.

The level of detail of these documents will depend on the sub-system. In general, Specifications willbe at a level permitting the overall system requirements to be met. Therefore, for the majority of thefunctions, only Performance, Safety and Interoperability Requirements will be defined. However, Inthe case of some ground systems which are common European products, such as ARTAS andRMCDE, more detailed Specifications will be prepared.

B.11 ARINCThe specific documents of ARINC which are applicable for Package I include:

● ARINC AEEC documents detailing derived technical requirements for equipment e.g. for the databuses



B.12 Equipment MOPSThe Minimum Operational Performance Standards (MOPS) provide performance requirementscorresponding to particular equipment and is used to assess its capability to meet the definedrequirements.

MOPS documents should be defined for equipment, which will be used to support Package Iapplications, including

● All data-link technologies which are necessary to support the Package I; and

● Other equipment (to be defined at a later stage).

B.13 Ground System StandardsThese deliverables will cover the standardisation of ground aspects of the system. These include:

● Standards of data formats, such as the EUROCONTROL ASTERIX; and

● ETSI Euronorms.

B.14 Master PlanThe Master Plan for the development, validation and implementation of Package I of AirborneSurveillance/Ground Surveillance Applications will provide the necessary framework for the executionof the various tasks and the identification of complementary responsibilities.

The components of this Master Plan are included in the present document, namely the deliverables,responsible fora, Plan etc.

B.15 Validation DeliverablesThe main deliverable is the Report of the Operational and Technical Validation of Package Iapplications and enablers, as outlined above. It will (amongst others) include the results of the safetyassessment.

Other deliverables of importance, especially for avoidance of duplication of work, are the following:

● Validation Strategy;

● Validation Plan;

● Validation Methodology; and

● Validation Tools.

Widely accepted documents, methodologies and tools such as EATMP Validation methodology,MAEVA and VDR (Validation Data Repository) should be considered in this context.

B.16 Business CaseThis deliverable is important to support the business decisions with respect to Package I, and to allowlocal or stakeholder specific business cases to be developed.

It will include a Cost Benefit Analysis detailing the costs and benefits (or range of costs and benefits)achievable, in the applicable timeframe, through the implementation of Package I applications. In thiscontext, it will also take into consideration the potential for evolution towards future ASAS Packages.

As part of the Business Case, the Cost Benefit Analysis study should be complemented by atechnical analysis of the different ways to implement Package I, as well as a Safety assessment(reference Paragraph B.17).

The EUROCONTROL Business Case for Package I will be also used in support of the ECIP process(ref. paragraph B.18), with the objective to achieve commitment from Stakeholders on itsimplementation planning.



B.17 Safety Assessment of ServicesCompliance to EUROCONTROL Safety Regulatory Requirements [ESARR3]/[ESARR4] is not strictlyrequired since these requirements apply to ATS service providers. However, since these services areintended to be standardised and further integrated in ATS systems, compliance to the principlesestablished per ESARR3 and ESARR4 will be sought. Package I also elects to apply SRC (SafetyRegulation Commission) guidance material to demonstrate compliance.

Two deliverables are foreseen in this context:

● Safety Policy; and

● Safety Plan.

Safety Management for Package I will consider the whole service provision, encompassing not onlythe developmental issues such as the introduction of new equipment or ATC procedures, but alsoaddressing the continuing operations and the influence of the organisation upon safety. A templatewill be outlined in a Safety Policy document for Package I.

The Safety Policy document for Package I will specify the policy statements and principles for aharmonised approach to Safety Management in the different stakeholders participating in Package Iin order to support compliance to ESARR3 requirement.

The Safety Policy document for Package I will provide the basic SMS (Safety Management System)principles and methods to the Safety Plan document for Package I.

Safety planning separates the regulatory aspects of the overall development process intomanageable tasks that can be accomplished in a logical and sequential manner.

The Safety Plan for Package I aims to enable to determine:

● Safety content; and

● Significance of Project in terms of safety requirements.

The Safety Plan document for Package I will contain the following core information:

● Description of Safety Management System (SMS);

● Safety deliverables; and

● Milestone timetable.

It is noted that in the scope of this document, it is proposed to deliver templates for the Safety Planand Safety Policy of Package I services. However, this is not to be seen at the level ofimplementation of Package I services. Therefore, these documents will describe the activities andprocesses to deliver the SPR standard. They will also provide background information regarding thestandardisation activities undertaken for the co-ordination of requirements for Package I services. Fortheir specific implementation, individual ATS Service Providers will have to provide the necessarydocumentation according to ESARR regulations as well as to their own Safety Management System.

B.18 European Convergence and Implementation Plan (ECIP)The ECIP process defines Implementation Objectives as well as corresponding Stakeholder Lines ofAction, describing the specific actions to be taken by each of the aviation stakeholders and thecorresponding timescales. The results of this work cascade down into Local CIP (LCIP) documents.

In order to achieve implementation of Package I by the foreseen dates and achieve consensus by thestakeholders, the ECIP process has already started, to ensure inclusion of the correspondingImplementation Objectives in the Plan 2004-2008. The Objectives are initially identified with atentative status, as long as the concept has not been validated and is not supported by a full CBAand safety case. When the validation work and appropriate supporting cases will be completed onfor the ECAC wide area, then the objective gets an agreed status indicating the commitment fromevery stakeholder involved to implement the Stakeholder Lines of Action associated to the objective.Once the Stakeholder Lines of Action have been completed, the objective is achieved.

The ECIP Process provides flexibility to the stakeholders with respect to implementation ofapplications suitable to their particular environment.



The ECIP Stakeholder Lines of Action are elaborated, agreed, and progressed by the followingstakeholder categories: Airspace Users, Air Navigation Service Providers, Airport Operators, SupportIndustry (airframe, avionics, ATC equipment, etc.), Regulatory Authorities, Military Authorities andEUROCONTROL Agency.

B.19 International Standards and Guidance Material The use of the applications on a world-wide basis requires the standardisation and guidance at aglobal level by ICAO.

Standards and Recommended Practices (SARPs) are grouped in Annexes to the ChicagoConvention:

● Standard: Any specification for physical characteristics, configuration, material, performance,personnel or procedure, the uniform application of which is recognised as necessary for the safetyand regularity of international air navigation and to which Contracting States will conform inaccordance with the convention; in the event of impossibility of compliance, notification to theCouncil is compulsory under Article 38.

● Recommended Practice: Any specification for physical characteristics, configuration, material,performance, personnel or procedure, the uniform application of which is recognised as desirablein the interest of safety, regularity or efficiency of international air navigation, and to whichContracting States will endeavour to conform in accordance with the Convention.

● Guidance Material approved by the Council for publication in association with the Standards andRecommended Practices: Historical and explanatory material supporting the Standards andRecommended Practices.

During the process of standardisation of ICAO, Manuals and Circulars are also produced.

The following table gives an idea of the Annexes, Manuals and Circulars that are going to beimpacted (to a varying extent) by the introduction of GS/AS applications.

ICAO Document Purpose and relationship with GS/ASapplications

Manual on Airborne Separation AssistanceSystem (ASAS)

Manual defining ASAS and ASAS applications Currently under finalisation by SCRSP/WGA

Manual of Air Traffic Services Data LinkApplications (Doc 9694)

Manual including the definition of ADS-B as a datalink service (ADS-B Concept of Use andOperational Requirements for ADS-B) Underdevelopment by OPLINKP/WGA

Annex 1 Personnel Licensing Training related to the use of GS/AS applications

Annex 2 Rules of the Air Concept of use for GS/AS applications

Annex 3 Meteorological Service forInternational Air Navigation

Normally not impacted by GS/AS applications

Annex 4 Aeronautical Charts Normally not impacted by GS/AS applications

Annex 5 Units of Measurement to be Used inAir and Ground Operations


Annex 6 Operation of Aircraft GS/AS applications require new aircraftfunctionalities with an impact on operation ofaircraft

Annex 7 Aircraft Nationality and RegistrationMarks


Annex 8 Airworthiness of Aircraft Some AS applications may have an impact onairworthiness of aircraft (e.g. relative navigation toanother aircraft)



ICAO Document Purpose and relationship with GS/ASapplications

Annex 9 Facilitation

Annex 10 Aeronautical Telecommunications Standardisation of ASAS (e.g. display functions,conflict detection and Resolution functions, etc),ADS-B links and any CNS enablers

Annex 11 Air Traffic Services Procedures for GS/AS applications

PANS-ATM (Doc 4444) Detailed procedures for GS/AS applications forATS providers

Regional Supplementary Procedures (Doc 7030) Detailed procedures for GS/AS applications forATS providers can be defined on ICAO regionalbasis

PANS-OPS (Doc 8168) Detailed procedures for GS/AS applications foraircraft operators

ATS Planning Manual (Doc 9426) Guidance on the conditions governing thereduction of separation minima (required forPackage II and Package III)

Manual on Airspace Planning and Determinationof Separation Minima (Doc 9689)

Guidance material for the determination of airborneseparation minima (required for Package II andPackage III)

Annex 12 Search and Rescue Some AS applications could play a role in searchand rescue

Annex 13 Aircraft Accident and IncidentInvestigation

Normally not impacted by GS/AS applications.Could be relevant for Package III

Annex 14 Aerodromes Some GS/AS applications are related to aerodromeoperations

Annex 15 Aeronautical Information Services Normally not impacted by GS/AS applications

Annex 16 Environmental Protection Normally not impacted by GS/AS applications

Annex 17 Security: Safeguarding InternationalCivil Aviation Against Acts of UnlawfulInterference

GS/AS applications are using aircraft dependantsurveillance which could be subject to unlawfulinterference

Annex 18 The Safe Transport of DangerousGoods by Air


From an operational perspective, Package I is relatively less complex and does not involve anychanges in the current responsibility for separation provision which remains with the ground system.Therefore, the ICAO process supporting Package I is less demanding than in the case of PackageII and beyond.

Since both operational and technical standards are going to be impacted by the implementation ofGS/AS applications, a good co-ordination is essential between the various ICAO panels and thesections of the Air Navigation Bureau of ICAO.



B.20 JAAThe specific documents of JAA which are applicable for Package I include:

● JAA certification documents. A TGL (Temporary Guidance Leaflet) will provide guidance to solvethe issue of new services not fully covered by existing regulations. Since such TemporaryGuidance Material are not requirements, this TGL will have to evolve as an ACJ (Advisory CircularJoint).

It should be noted that RFG documents could support the production of JAA documents.



Annex C Detailed Depiction of Interdependencies between theDeliverables (“HOW”)

The interdependencies between all deliverables as introduced in section 2 and section 3 are shown inFig. Annex-2 .

Master Plan/ECIP

Develop

ment

Validat

ion

Approva

l

GSA/ASAPkg I Def

OperationalRequirements

ATM2000+

EATMP OIs CONOPS

GSA/ASAMASPS

FunctionalSystemArch

Sub-SystemSpec’s

ADS-B/etcMASPS

DatalinkMOPS

Gnd SystemStandards

OSED

SPR INTEROP

Business Case

ValidationEnvironment

InternationalStd’s/GM

Products

Fig. Annex-2: Interdependencies of Deliverables



Annex D Detailed Master Plan for ASA/GSA Package I Implementation(“WHEN”)

As discussed in section 5, the attached MS Project file presents the fully detailed Master Plan for theimplementation of Package I of AS and GS applications.

WA_MasterPlan_06.mpp

A summary view of the detailed Master Plan is presented in the following figure:


CARE/ASAS/EUROCONTROL/02-042 - Version 2.1 - July 10, 2003 - CA-02-042(2.1).doc page 35

ID Task Name1 DEVELOPMENT

2 VALIDATION

3 IMPLEMENTATION PLANNING

4 Start of Implementation

5

6 Produce MASTER PLAN

7

8 Strategy, Concept and Operational Requirements

9 Summary of Deliverables

10 ATM2000+ Strategy & Operational Improvements

11 Initial Package I GS/AS Applications

12 Final Package I GS/AS Applications

13 Initial CONOPS

14 Finial CONOPS

15 ASA Operational Requirements

16 GSA Operational Requirements

17 Final Deliverables Update (after Validation)

18 First Package of GS/AS Applications

23 CONOPS (for Package I)

28 Operational Requirements

33 OSED, SPR and INTEROP


35 Initial ASA and GSA OSED's

36 Intermediate ASA and GSA OSED's

37 Final ASA and GSA OSED's

38 Initial ASA/GSA SPR and INTEROP

39 Final ASA/GSA SPR and INTEROP


41 Operational Service and Environment Definition (OSED)

56 SPR and INTEROP

67 MASPS, MOPS and Systems


69 Initial ASA and GSA MASPS

70 Final ASA and GSA MASPS

71 Initial Ground + Airborne Functional System Architecture

72 Intermediate Ground + Airborne Functional System Architecture

73 Final Ground + Airborne Functional System Architecture

74 Intial ADS-B and TIS-B MASPS

75 Final ADS-B and TIS-B MASPS

76 Initial Sub-System Spec's

77 Final Sub-System Spec's

78 Final Datalink MOPS

79 Final ASTERIX Update


81 ASA/GSA MASPS

92 System Architecture

102 ADS-B and TIS-B MASPS

113 Sub-system Specifications

118 Datalink MOPS

121 Ground System Standards

129 Qualification and Other Activities


131 Validation Strategy

132 Validation Plan v1.0

133 Validation Plan v2.0

134 Final Validation Report

135 Initial CBA

136 Final CBA/Business Case

137 First ECIP Tentative Objective Publication

138 Last ECIP Tentative Objective Publication

139 (Last) ECIP Objective Provisional Council Decision

140 Validation Environment

155 International Standards and Guidance Material

187 Business Case

192 European Convergence and Implementation Plan (ECIP)

01/01

31/12

08/10

05/06

31/12

23/09

30/12

30/12

28/07

24/04

22/04

20/01

22/04

20/01

28/07

16/07

04/03

30/06

30/08

18/04

08/10

27/05

22/11

11/07

08/07

11/07

08/08

01/05

30/06

18/06

30/06

02/07

19/09

30/06

30/06

03/07

H2 H1 H2 H1 H2 H1 H2 H1 H2 H1 H2 H101 2002 2003 2004 2005 2006 20



Annex E Acronyms

ADS Automatic Dependent SurveillanceAEA Association of European AirlinesAEEC Airlines Electronic Engineering Committee AGC Air Ground Co-operative ATSANSP Air Navigation Service ProviderARINC Aeronautical Radio IncorporatedARTAS ATM Surveillance Tracker and ServerASA Airborne Surveillance ApplicationsASAS Airborne Separation Assistance SystemsATC Air Traffic ControlATM Air Traffic ManagementATS Air Traffic ServicesATSAW Air Traffic Situational AwarenessCARE Co-operative Actions of R&D in EUROCONTROL.CBA Cost Benefit AnalysisCDTI Cockpit Display of Traffic InformationCIP Convergence and Implementation PlanCNS Communications, Navigation and SurveillanceCONOPS Concept of OperationsCOOPATS Co-operative Air Traffic ServicesCPDLC Controller Pilot Data Link CommunicationsDG Drafting GroupEATMP European Air Traffic Management ProgrammeECAC European Civil Aviation ConferenceECIP European Convergence and Implementation PlanESARR EUROCONTROL Safety Regulatory RequirementsESC EUROCONTROL European ATM Systems and Convergence

(Business Division)

ETSI European Telecommunications Standards InstituteEUROCAE European Organisation for Civil Aviation EquipmentEUROCONTROL European Organisation for the Safety of Air Navigation FAA Federal Aviation AdministrationGSA Ground Surveillance Applications


CARE/ASAS/EUROCONTROL/02-042 - Version 2.1 - July 10, 2003 - CA-02-042(2.1).doc page 37

IA Interoperability AssessmentIATA International Air Transport AssociationICAO International Civil Aviation OrganisationINTEROP Interoperability documentJAA Joint Aviation AuthoritiesJCB Joint Co-ordination BoardJURG Joint User Requirements Group (of IATA/AEA)LCIP Local Convergence and Implementation PlanMASPS Minimum Aviation System Performance StandardsMOPS Minimum Operational Performance StandardsOCD Operational Concept DocumentODIAC Operational Development of Integrated surveillance and

Air/Ground Data Communications

OI Operational ImprovementsOPA Operational Performance AssessmentOPLINKP ICAO OPLINK PanelOSA Operational Safety AssessmentOSED Operational Services and Environment DefinitionOSEIC Operational Services and Environment Information CapturePSG Programme Steering GroupRFG Requirements Focus GroupRMCDE Radar Message Conversion and Distribution EquipmentSAP System Access ParametersSCRSP ICAO Surveillance and Conflict Resolution Systems Panel SPR Safety and Performance RequirementsRFG Requirements Focus GroupRTCA Radio Technical Commission for AeronauticsSURT Surveillance TeamVDR Validation Data RepositoryWG Working GroupTIS Traffic Information Services

IntroductionBackgroundObjectives and Scope of the DocumentReferences

List of Deliverables \(“WHAT”\)IntroductionGroup 1: Strategy, Concept, and Operational RequirementsEUROCONTROL ATM 2000+ StrategyPackages of GS/AS ApplicationsConcept of Operations (CONOPS)Operational Requirements

Group 2: Determination of Co-ordinated RequirementsApplication Descriptions (OSED)SPR and INTEROP

Group 3: MASPS, MOPS, Systems and ProductsASA/GSA MASPSSystem ArchitectureADS-B and TIS-B MASPSSub-system SpecificationsEquipment MOPSGround System StandardsGround and Airborne ProductsGround ProductsAirborne Products

Group 4: Qualification, Implementation and General DeliverablesMaster PlanValidation DeliverablesBusiness CaseSafety Assessment of ServicesEuropean Convergence and Implementation Plan (ECIP)International Standards and Guidance Material

Interdependencies between the Deliverables \(“HOResponsible Fora per Deliverable \(“WHO”\)PrinciplesDrafting, Reviewing and Approving GroupsIntroductionEUROCONTROL European ATM Systems and Convergence (ESC) Business DivisionEUROCONTROL Package I ProgrammeRequirements Focus Group (RFG)European Organisation for Civil Aviation Equipment (EUROCAE)European Commission Joint Co-ordination Board (JCB)International Civil Aviation Organisation (ICAO)Joint Airworthiness Authority (JAA)European Telecommunications Standards Institute (ETSI)

Deliverables and corresponding Drafting, Reviewing and Approving GroupsGroup 1: Deliverables related to Strategy, Concept, and Operational RequirementsGroup 2: Deliverables related to the Determination of Co-ordinated RequirementsGroup 3: Deliverables related to MASPS, MOPS, Systems and ProductsGroup 4: Deliverables related to Qualification, Implementation and General Deliverables

Master Plan \(“WHEN”\)IntroductionTowards Implementation of Package I of AS/GS ApplicationsBeyond Implementation of Package I of AS/GS applicationsRoadmap

Important issuesIntroductionOrganisational issuesPackage I issuesImplementation issues

Concluding remarks