care/asas action plan - eurocontrol.int · care/asas action plan asas in care account various...

CARE/ASAS Action Plan ASAS in CARE

Co-operative Actions of R&D in EUROCONTROL Action on

Airborne Separation Assistance System

CARE/ASAS Action Plan

Executive summary

Following the decision of the EUROCONTROL R&D Review Group, CARE/ASAS started in September 1999. The action was selected for inclusion in CARE because it was suitable for a co-operative approach, requiring a diversity of competences; it was focused on improvement steps defined in the EUROCONTROL ATM 2000+ strategy; and it was aimed at reducing overall R&D costs and avoiding duplication of efforts.

The main purpose of CARE/ASAS was to drive the establishment of a common view of ASAS applications and to support their validation.

The action was managed by a CARE/ASAS manager assisted by a Management Board composed of European ASAS experts from the EUROCONTROL agency, R&D centres, ATS providers and Universities. The Management Board members did not have necessarily to represent the views of their organisation. Observers from the European Commission, the airline industry, the aircraft industry and the certification authorities were also invited.

Periodic meetings were organised to review the progress of the CARE/ASAS activities and to take well-argued decisions based on several perspectives. Full transparency was provided related to the progress of the action and the deliverables which were produced. The CARE/ASAS website (http://www.eurocontrol.int/care) and the organisation of dissemination forums were the tools for the dissemination of the information.

CARE/ASAS has successfully delivered and is going to conclude in December 2004. The main achievements of CARE/ASAS are:

o CARE/ASAS was instrumental to build an ASAS R&D community speaking the same language, able to discuss controversial topics and ready to work together. Through the ASAS Thematic Network, the ASAS community was enlarged to include aircraft operators, aircraft and avionics industry, ATM industry, pilot and controller professional associations.

o CARE/ASAS activities, and the associated projects which were launched through call for tenders, initiated and carried out significant work for the definition of ASAS applications, for their validation, for their safe design and for their safety assessment.

o Within the context of Action Plan 1 of the FAA/EUROCONTROL R&D Committee, CARE/ASAS provided European expertise for the development of two reference documents called: ‘Principles of Operation for the use of ASAS’ and ‘Safety and ASAS applications’.

o CARE/ASAS proposed the grouping of ASAS applications into packages which includes also ground surveillance applications known as ‘Package I’. This approach got international recognition and was presented and endorsed at the Eleventh ICAO Air Navigation Conference in September 2003.

Finally, CARE/ASAS has demonstrated that it is possible to build a consensus in Europe as soon as partners speak the truth and trust each other.

CARE-ASAS/EUROCONTROL/99-001 - Version 5.1 - November 29, 2004 page 1

http://www.eurocontrol.int/care

ASAS in CARE CARE/ASAS Action Plan

CARE-ASAS/EUROCONTROL/99-001 - Version 5.1 - November 29, 2004


Co-operative Actions of R&D in EUROCONTROL Action on

Airborne Separation Assistance System

CARE/ASAS Action Plan

This paper describes the action on Airborne Separation Assistance System (ASAS) within the Co-operative Actions of R&D in EUROCONTROL (CARE).

CARE/ASAS started in September 1999. The Action Plan document was central for the management of the action. It was updated periodically during the project to reflect the progress.

As CARE/ASAS is going to conclude in December 2004, this version is the last version of the Action Plan. It differs from the previous versions as this version is focused on the CARE/ASAS achievements and deliverables.



1. Background

In 1998, an inventory of potential ASAS applications was performed in work package 5 of the EMERALD project funded by the European Commission DG TREN. This project made an initial, but comprehensive, assessment of operational and technical capabilities to support ASAS applications and concluded positively to feasibility. It also produced recommendations for further R&D on the subject.

A proposal for a CARE action (CARE/ASAS) was presented during the fifth EUROCONTROL R&D Review Group meeting in April 1999. The proposal received support from the Group. A strong need for a co-ordinated European action was identified. Members of the Group expressed the intention from their organisation to support this action with effort and budget. A business view approach was recommended, starting with a small amount of effort to see whether it is worth pursuing, and if so continue in a step-wise approach.

CARE/ASAS was selected for inclusion in CARE, because: • It would prevent or reduce waste of efforts in the current uncoordinated work: producing added

value out of its co-operation, aiming at reducing overall R&D costs compared to non co-operative actions and avoiding duplication of other European activities;

• It was focused on improvement steps defined in the ATM 2000+ and addresses real European-wide issues; it aims at a European solution with world-wide benefits; and

• It was suitable for a co-operative approach: requiring a diversity of competence (complementary), and allowing a wide participation of stakeholders.

One of the objectives of the action was to better assess the potential gains of ASAS applications. The basic expectations were: • Safety: enhanced cockpit situation awareness, with possibility to better understand surrounding

traffic; this would complement visual acquisition and avoid erroneous visual acquisition; this is not to replace Short Term Conflict Alert and/or ACAS, but can help to avoid being in situations where those safety nets would be useful by reducing exposure to risk of judgement error in planning traffic situation.

• Capacity & flight efficiency: ASAS applications should reduce controller workload (e.g. long monitoring situations). Depending on traffic conditions, airspace constraints, and controller’s options, can be converted into capacity and/or flight efficiency. These gains are sensitive to many factors. Pilot awareness may also help him to avoid flight plan changes that would be denied due to traffic, thereby also reducing controller workload.

• Cost reductions: cost reduction may come from reduced delays attached to capacity/flight efficiency gains. It is not anticipated that this would lead to a reduction of ATC infrastructure costs in the timescale under consideration. Nevertheless, one might imagine reducing the need for controllers at night or at very low traffic density times.

The EUROCONTROL ATM Strategy for 2000+ identifies a strategic line of action on progressive, limited transfer of separation responsibility to cockpit. It indicates that operational improvements in En-route and Terminal ATC could be achieved by transfer of separation responsibility with ASAS as an enabler. A possible operational use is anticipated from 2008 onwards for simple applications, to 2015 onwards for more complex applications.

The main purpose of CARE/ASAS was to support the validation of this strategic line of action, in particular by driving the establishment of a common view of ASAS applications. The main issues included the feasibility and conditions of applicability of the concept. The action dealt with the operational aspects, not with the supporting technologies (i.e. ADS-B, Traffic Information Service, Traffic Information Service - Broadcast, air-to-air data-link).

In 2001, under the auspices of the FAA/EUROCONTROL R&D Committee, Action Plan 1 developed a document called ‘Principles of Operation for the use of ASAS’ (PO-ASAS). Taking into



account various considerations (conceptual, operational procedures, human factors, aircraft systems, enabling technologies, users’ perspectives and implementation), four ASAS application categories have been defined:

o Airborne Traffic Situational Awareness applications; o Airborne Spacing applications; o Airborne Separation applications; and o Airborne Self-separation applications.

These categories are now used in almost any work related of ASAS.

Following the ADS-B Symposium in Rome (12-14 March 2002), a Joint Co-ordination Board (JCB), involving the European Commission and EUROCONTROL, was created to co-ordinate research, development and validation work performed by the European Commission ADS-B projects and to expedite implementation.

In 2002, under the leadership of CARE/ASAS and with the involvement of all stakeholders, the description of a first package of Ground Surveillance / Airborne Surveillance (GS/AS) applications was developed. Known as ‘Package I’, the main objective of this document was to identify operational applications suitable for early (5-10 years) implementation in Europe. ADS-B is recognised as a key enabler for GS/AS applications and ‘Package I’ is focused on the operational use of ADS-B data to improve the ATM system. The ASAS applications which were selected belongs to the first two categories defined in the PO-ASAS document. The document CARE/ASAS/EUROCONTROL/02-040 (version 2.2) was endorsed at the third JCB meeting on 30 September 2002.

At the ICAO Air Navigation Conference (ANConf/11) in September 2003, ‘Package I’ was presented by EUROCONTROL (AN-Conf/11-WP/86) and it was supported by the FAA (AN-Conf/11-WP/41). The ANConf/11 recommendation 1/7 on ‘Ground and airborne automatic dependent surveillance-broadcast (ADS-B) applications for global interoperability’ states:

That ICAO and States:

a) Recognise ADS-B as an enabler of the global ATM operational concept bringing substantial safety and capacity benefits;

b) Support the cost-effective early implementation of packages of ground and airborne ADS-B applications, noting the early achievable benefits from new ATM applications; and

c) Ensure that implementation of ADS-B is harmonized, compatible and interoperable with respect to operational procedures, supporting data link and ATM applications.

During the 17th EUROCONTROL CNS/ATM Consultancy Group meeting (September 2002), the formation of a multidisciplinary implementation programme for ADS-B was supported by the members. In 2004, the EUROCONTROL CASCADE (Co-operative ATS through Surveillance and Communication Applications Deployed in ECAC) programme was created. The programme is in charge of the validation and implementation of most of the ‘Package I’ applications in addition to other datalink applications. The first CASCADE programme steering group meeting took place on 8 September 2004 in Haren.

Longer-term ASAS applications which are not included in the CASCADE programme charter are the responsibility of the EUROCONTROL ATS and CSM domains.

The European Commission 6th Framework Programme is mainly base on large integrated projects. One integrated project is called ‘Co-operative ATM’ and is more relevant to short-term and medium-term ASAS applications. Another potential integrated project is called ‘Advanced Airborne Applications’ is more relevant to medium-term and long-term ASAS applications and to the reduction of separation standards.



2. Management of CARE/ASAS

2.1. CARE/ASAS manager

EUROCONTROL Agency nominated Francis Casaux (CENA) as manager for CARE/ASAS.

Mick Van Gool (EUROCONTROL SD/ESC), who is the CARE manager, was responsible for administrative matters related to CARE/ASAS.

The CARE manager facilitated the coordination between CARE/ASAS and other CARE actions (e.g. CARE/INTEGRA; CARE/Innovative). The CARE/ASAS manager informed regularly the managers of the other CARE actions and organised specific meetings when necessary.

2.2. CARE/ASAS Management Board

The Management Board was established to assist the CARE/ASAS manager to initiate, to follow the progress, and to evaluate the work conducted within CARE/ASAS. The Management Board was composed of ASAS experts, which did not necessarily have to represent the views of their organisation.

Periodic meetings were organised to review the progress of the CARE/ASAS activities and to update the Action Plan, which is the current document.

The following table provides the names of the CARE/ASAS Management Board members valid in November 2004 and the names of the observers representing their organisation who were invited to attend CARE/ASAS Management Board meetings. The third column of the table provides the names of former members or observers.



Name Organisation and Role Former members

Luc Angerand JAA, Observer

None LFV, Member Jörgen Bevonius, Billy Josefsson, Gunnar Frisk, Rune Lundberg

Jean-François Bousquié AIRBUS, Observer

Ken Carpenter QinetiQ, Member

Francis Casaux CENA, CARE/ASAS manager

Soren Dissing EUROCONTROL DAS/ATS, Member

Colin Goodchild Glasgow University, Member

Mick van Gool EUROCONTROL SD/ESC, CARE manager

Juan Alberto Herreria Garcia ISDEFE, Member

Eric Hoffman EEC, Member

Heribert Lafferton DFS, Member

Jean-Marc Loscos CENA, Member

Jean-Luc Marchand European Commission DG Research, Observer

Khoen Liem, Jonas Forsman

Giorgio Matrella ENAV, Member Giancarlo Ferrara

Christopher North

European Commission DG TREN, Observer

Robert Graham, Patrick Bernard

Christos Rekkas EUROCONTROL DAP/SPR, Member

Rob Ruigrok NLR, Member Ronald Van Gent

Claudio Vaccaro SICTA, Member Alessandro Boschiero

Mark Watson NATS, Member Richard Pugh, Fiona Harrison/Macfarlane, Kat Richmond

None

IATA, Observer Nicolas Zveguintzoff, Steve Zerkowitz



2.3. Working Methods

2.3.1. CARE/ASAS Management Board meetings

Eighteen CARE/ASAS Management Board meetings were organised (three to four meetings per year). After approval by the Management Board member, the notes of the meetings were made available through the CARE website.

Meeting Number Dates Notes of the Meeting

First Meeting October 4, 1999 CARE/ASAS/EUROCONTROL/99-002

Second Meeting December 7, 1999 CARE/ASAS/EUROCONTROL/99-005

Third Meeting March 27, 2000 CARE/ASAS/EUROCONTROL/00-006

Fourth Meeting July 13, 2000 CARE/ASAS/EUROCONTROL/00-007

Fifth Meeting October 13, 2000 CARE/ASAS/EUROCONTROL/00-011

Sixth Meeting December 20, 2000 CARE/ASAS/EUROCONTROL/00-014

Seventh Meeting March 22, 2001 CARE/ASAS/EUROCONTROL/01-023

Eighth Meeting June 27, 2001 CARE/ASAS/EUROCONTROL/01-025

Ninth Meeting October 24, 2001 CARE/ASAS/EUROCONTROL/01-027

Tenth Meeting January 30, 2002 CARE/ASAS/EUROCONTROL/02-038

Eleventh Meeting June 6, 2002 CARE/ASAS/EUROCONTROL/02-043

Twelfth Meeting October 11, 2002 CARE/ASAS/EUROCONTROL/02-045

Thirteenth Meeting January 28, 2003 CARE/ASAS/EUROCONTROL/03-046

Fourteenth Meeting May 9, 2003 CARE/ASAS/EUROCONTROL/03-052

Fifteenth Meeting September 26, 2003 CARE/ASAS/ EUROCONTROL/03-054

Sixteenth Meeting January 15, 2004 CARE/ASAS/ EUROCONTROL/04-062

Seventeenth Meeting July 9, 2004 CARE/ASAS/ EUROCONTROL/04-063

Eighteenth Meeting November 26, 2004 CARE/ASAS/ EUROCONTROL/04-066

2.3.2. CARE/ASAS Workshops As a starting point, the CARE actions were presented during a CARE Briefing Session organised on 21 January 2000 in Haren (Belgium). This event was well attended with representatives from R&D Establishments, Universities and Industry but none from Airlines. A call for interest was issued.

Three years after the start of CARE/ASAS, a workshop was held on 27-28 January 2003 at EEC. The objective was to discuss the next objectives of the action taking into account the latest developments (e.g. Package I, ASAS-TN). The notes of the workshop are available under the following reference CARE/ASAS/EUROCONTROL/03-047 (version 1.2 - February 21, 2003).

2.3.3. CARE/ASAS reference documents

In addition to the Action Plan, two other important documents were maintained:

• CARE/ASAS Reference Document List - CARE/ASAS/EUROCONTROL/00-010. The Reference Document List provides the references of all CARE/ASAS deliverables.

• CARE/ASAS Point of Contact Lists - CARE/ASAS/EUROCONTROL/01-026. A previous version of the document included specific lists for each CARE/ASAS Activities. Two lists are maintained in the current version of the document



o The first one for the CARE/ASAS Management Board members and observers; and

o The second one for the CARE/ASAS interested people which includes also the CARE/ASAS Management Board members and observers.

2.3.4. The CARE Website

The CARE website http://www.eurocontrol.int/care was essential to the success of the CARE/ASAS. It was updated on a regular basis.

The CARE website was accessible to the public without any restriction allowing for example students to have access to the information.

All CARE/ASAS deliverables produced by the various activities are available in an electronic format. The general idea on intellectual property rights was that all deliverables produced by CARE/ASAS should be available in the public domain.

The CARE website was also used to publicise the calls for tender which were issued by CARE/ASAS.

2.3.5. Exchange/Co-operation/Collaboration within CARE/ASAS

Within CARE/ASAS, three levels of cooperation were defined:

• Level 1 – Exchange: At this level, organisations exchanged information on R&D work through for example workshops or the establishment of an R&D network. The objective was to establish direct contact between people at the working level. Each organisation ran its own projects independently. Level 1 was used for all communication activities. Most of the events were hosted by EEC or EUROCONTROL in Haren (Belgium) but CENA and NLR organised also specific meetings. There was no CARE/ASAS funding. All organisations supported the travelling costs incurred by their staff to attend the events.

• Level 2 – Cooperation: At this level, organisations used the results of R&D work conducted by other organisations. The objective was to avoid duplication of work and more efficient use of the existing resources within each organisation. The projects run by the organisations were inter-related. Level 2 was used at the start of the CARE/ASAS Activities 2 and 3. Calls for Interest were issued to define the work to be performed and to identify which organisations were ready to sponsor and to support the work. There was no CARE/ASAS funding. Several important CARE/ASAS deliverables were produced under level 2.

• Level 3 – Collaboration: At this level, organisations were working together on the same R&D project. A common funding was necessary. Level 3 was use for CARE/ASAS Activities 1, 2, 3 and 4. The work to be performed was defined and agreed at the CARE/ASAS Management Board level and Calls for tender were issued following the standard EUROCONTROL procedure. To comply with the collaborative principle of CARE/ASAS, responses to these calls were to come from consortiums of organisations with one clearly identified leader. The projects were to be structured in work-packages with associated deliverables and timescale. The average duration of the projects was one-year. All deliverables were to be public domain and each project concluded with a dissemination event.




2.4. CARE/ASAS and EATM programmes

CARE/ASAS was conducting R&D activities related to ASAS. It was not an implementation programme. Nevertheless, the deliverables produced by the CARE/ASAS activities were of particular interest for EATM programmes and domains.

CARE/ASAS provided support to fulfil the R&D needs of the EATM programmes and domains:

• CASCADE programme is responsible for the validation and implementation of most of the ‘Package I’ applications in addition to other datalink applications;

• ACAS programme: ACAS and ASAS are two airborne systems which require careful integration;

• ATS domain is responsible for ‘Package I’ applications not addressed by the CASCADE programme and for the definition and validation of the future packages;

• CSM domain is responsible for the ADS-B datalink technologies which could be required for the future packages; and

• Other programmes could be interested because for example some ASAS applications will impact Airspace Organisation & Management, Navigation, and Airport Operations.

The CARE/ASAS manager informed regularly EATM programme/domain managers and organised specific meetings when necessary.

For early information and coordination with the EATM domains/programmes, the following EUROCONTROL people received the draft version of the notes of the CARE/ASAS Management Board meetings:

• Ed Bailey, DAS/AFN ;

• Christos Rekkas, DAP/SPR;

• John Law, DAP/SAF;

• Bernard Miaillier, SD/ESC; and

• José Roca, DAP/SPR.



2.5. CARE/ASAS and Certification Authorities, standardisation bodies and industry

When in operation, ASAS applications will have an impact on aircraft operations and on airborne equipment. JAA has developed a position paper on ASAS and has started R&D activity on ASAS. EUROCAE is standardizing technologies and equipment relevant to ASAS in co-operation with RTCA. The aircraft industry is involved in several project related to ASAS applications.

The activities conducted within CARE/ASAS needed to take into account these perspectives. They could also contribute to the work in progress. It was thus important for the CARE/ASAS manager to maintain close relationship with the above-mentioned bodies and organisations.

As mentioned is section 2.2, JAA and AIRBUS were invited to attend CARE/ASAS Management Board meetings as observers.

2.6. CARE/ASAS and projects sponsored by the Commission of European Communities

Although CARE/ASAS was conducting R&D activities related to ASAS, it could not be considered as an R&D project on ASAS. The main goal of CARE/ASAS was to help the organisations working on ASAS R&D, to speak the same language and to work together.

The deliverables produced by the various CARE/ASAS activities were of particular interest for the European Commission as these activities were selected because they addressed issues that were not currently tackled.

CARE/ASAS was also interested to be involved as observer or adviser in the projects related to ASAS which were sponsored by the European Commission. This allowed CARE/ASAS to use and to maintain its expertise and to help projects to identify and solve the ASAS issues.

CARE/ASAS contributed actively to:

• The Mediterranean Free Flight (MFF) project. This was particularly true during the first year of the project where CARE/ASAS helped to focus the project on five applications (i.e. Free-route and four ASAS applications).

• The Master ATM European Validation Plan (MAEVA) project. Close relationship was maintained during the Validation Framework project (see section 3.5) conducted under CARE/ASAS Activity 3. CARE/ASAS provided information and attended workshops organised by the MAEVA project.

• The NEAN Update Programme (NUP II). CARE/ASAS provided expertise during NUP II meetings. This was particularly important during the definition of ‘Package I’ (see section 3.8).

The CARE/ASAS manager informed regularly the European Commission experts and organised specific meetings when necessary. As mentioned in section 2.2, DG TREN and DG Research were invited to attend CARE/ASAS Management Board meetings as observers. The CARE/ASAS manager attended the JCB meetings chaired by DG TREN.



2.7. CARE/ASAS and Action Plan 1 of the FAA-EUROCONTROL R&D committee

In 1999, Action Plan 1 of the FAA-EUROCONTROL R&D committee was redefined to be focused on ASAS. Its objectives were:

• To promote a mutual understanding of the United States and European visions of future operational concepts for the use and integration of airborne avionics with ATM decision support systems and operations.

• To identify areas for practical co-operation on the development of Airborne Separation Assistance Systems (ASAS).

• To examine the longer term issues relating to the advanced capabilities of air and ground equipment to support the ASAS concept in a future collaborative decision-making ATM environment.

The CARE/ASAS manager who was also the EUROCONTROL Point of Contact for Action Plan 1 maintained a strong co-ordination between the two actions.

Two main deliverables were developed by Action Plan 1:

• Principles of Operation for the Use of ASAS (PO-ASAS) document. Work started in March 2000. Four meetings were held: two meetings in Europe and two meetings in the USA. The document was delivered in June 2001 at the FAA/EUROCONTROL R&D Committee meeting (RDCom19) and was approved for further dissemination.

• Safety and ASAS applications (SAF-ASAS) document. Work started in January 2002. Eight meetings were held: four meetings in Europe and four meetings in the USA. The document was delivered in March 2004 at the FAA/EUROCONTROL R&D Committee meeting (RDCom28) and was approved for further dissemination.

For these developments, CARE/ASAS provided the European ASAS expertise and sponsored partially efforts and travel costs.

During the FAA/EUROCONTROL R&D Committee meeting (RDCom28) on 10 March 2004 in Miami (USA), it was decided to merge Action Plan 1 (AP1 – Airborne Separation Assistance System (ASAS) applications) and Action Plan 10 (AP10 – Automatic Dependent Surveillance (ADS)) to form a new action plan (AP18 – ADS-B and ASAS Applications).

The first planned deliverables of AP18 are:

• D03 - Develop a document ‘ASAS concept of use’ (CoU-ASAS). It is a key missing document and the objective is to describe how ASAS applications, integrated in the current/future operations, can contribute to a better ATM system.

• D04: Contribution to and participation in the Requirement Focus Group (RFG). The objective of the RFG is to support the operational implementation of ‘Package I’ through the harmonisation of the applications and the establishment of safety/performance/interoperability requirements.

The kick-off meeting for the CoU-ASAS took place on 17-18 June 2004 at CENA in Toulouse (France).

The CARE/ASAS manager was the European Co-chair of RFG and CARE/ASAS developed several working papers to support the RFG work (see section 3.7 for details).



3. CARE/ASAS Activities

3.1. Rationale for the selection of Activities

After due consideration of the needs and the various studies underway, either to define the applications or to experiment some of the aspects of ASAS, it was possible to identify a few important issues which were not currently or properly tackled and which required a co-operative approach because they were central to forging the conditions of the use of ASAS applications by the aviation community.

CARE/ASAS comprised initially five activities, which were inter-related. During the course of CARE/ASAS, the definitions of the activities were reviewed and were amended. A fifth activity was added.

The general description of each activity is given in the following section.

3.2. List of CARE/ASAS Activities

Six activities were conducted within the context of CARE/ASAS with the following objectives:

• Activity 0 – Communications: This activity was a base-line activity that encouraged exchange of information between organisations. It was expected that if individuals had a better understanding of the work currently undertaken by the organisations, the co-operation or collaboration process which was essential for running CARE/ASAS, would be much easier to establish. The objective was to create direct contact between people at the working level. Dissemination of the results of R&D work out-side the R&D community was also very important.

• Activity 1 – Problem dimensions: It had been observed that individual R&D actions tended to consider some aspects of ASAS applications without a clear strategy. Issues were addressed with no specific order. This led to partial and disconnected results, difficult to link to the fundamental issues. This activity was aimed at structuring the issues and evaluating the level of validation of each of them, so as to make a more efficient use of experience acquired, to record pending issues and to orient further work.

• Activity 2 – Validation framework: This activity was key to allow for comparability and consolidation of results. Various studies make use of different scenarios to check and demonstrate their developments, e.g. conflict detection and resolution algorithms. The assumptions made for traffic sample density, pattern etc. may have a strong impact on the result. Since this topic was still in its infancy and involved key issues for future ATM, it was the right opportunity to install a proper validation framework/process.

• Activity 3 – Safety: This is a fundamental topic with multiple aspects. Initially, this activity was named ‘Airborne Separation Minima’ however other safety aspects had also to be studied as part of the topic. This was reflected in the new title of the activity. ASAS applications are going to be implemented only if it can be demonstrated that they are safe. The four ASAS applications categories are associated with different safety issues. For example Traffic Situational Awareness applications could lead to dangerous situation if erroneous information is presented to the flight crew. For Airborne Spacing applications, another example is the spacing values used by the controller in his instruction should be selected so as to maintain the controller intervention capability to maintain ground separation minima. For Airborne Separation applications and for Airborne Self-separation applications, one major safety issue is the determination of the airborne separation minima. Many studies are based on assumptions about the achievable separation minima. Optimistic views are that they could be much smaller than radar separation and contributed to the publicity of autonomous separation. Other views are much more reserved and warn that minima might even be much larger. Due to the expected complexity of the issue, the work was phased so as to keep control of progress. Phase 1 was aimed at obtaining early information to re-orient as appropriate the expectations, the operational scenarios, the selection of ASAS applications and their separation minima assumptions. Phase 2 should consist in defining the suitable safety



methodologies and elaborating the safety standards (e.g. performances, spacing values, airborne separation minima) for ASAS applications.

• Activity 4 – ASAS application definition: The EMERALD project and RTCA/SC186 identified a large number of possible ASAS applications. It was necessary to define and assess them in more detail, in particular to describe the conditions for responsibility delegation (how it starts, finishes; how it may be impacted by surrounding traffic and flight conditions), the operational benefits, the procedures, fall-back modes and transition issues. The PO-ASAS document identifies four ASAS application categories and the associated issues. The activity should identify and select those applications, which are appropriate for the European traffic environment and contribute to describe the corresponding operational requirements and benefits. An ICAO approach should be favoured (i.e. a similar ASAS application envisaged in Europe and outside Europe should be based on the same procedures and systems). Due to the complexity and to the number of potential ASAS applications, the work was phased so as to keep control of progress. Phase 1 was aimed at resolving the separation delegation issue and at selecting ASAS applications. Phase 2 should study a limited number of selected ASAS applications.

• Activity 5 – ASAS application implementation: Making the assumption that the CARE/ASAS activities on definition, validation and safety are conducted successfully, selected ASAS applications should be implemented in the ECAC area within the framework of EATM. This activity should:

1) Support the definition of packages of ASAS applications; 2) Support the implementation of the first package of ASAS applications; 3) Plan the RTD (Research and Technical Development Plan) work necessary for achieving successful implementation of the next packages of ASAS applications.

The following sections provide for each activity what was actually achieved during the course of CARE/ASAS. It should be noted that:

o CARE/ASAS was not a project or a programme; it was a networking activity.

o Particular attention was paid to avoid work duplication with EUROCONTROL programmes/domains and with European Commission funded projects.

o CARE/ASAS budget allowed sponsoring a single main project per year.



3.3. Achievement of Activity 0 - Communications

Reporting: Reports of the progress of CARE/ASAS were made on a regular basis within EUROCONTROL (e.g. R&D Review Group, Operational Requirements and ATM Data Processing Team, ODIAC) and outside EUROCONTROL (e.g. SCRS panel).

Dissemination: The deliverables produced by the CARE/ASAS activities were disseminated through working papers, mail or Internet as appropriate. All CARE/ASAS deliverables produced by the various activities are available in an electronic format on the CARE website http://www.eurocontrol.int/care which was updated on a regular basis. The CARE website is accessible to the public without any restriction.

A Technical Interchange Meeting on ASAS was organised on 14-16 November 2000 in Brétigny (France) in cooperation with Action Plan 1 of the FAA-EUROCONTROL R&D committee. The slides from this technical interchange meeting are available on the FAA/EUROCONTROL website: http://www.eurocontrol.int/faa-euro .

CARE/ASAS CD-Rom was delivered in November 2000. This CD-Rom is a collection of documents relevant to ASAS, sorted, classified, and indexed for reference use.

Rules for the dissemination of CARE/ASAS results are defined (CARE/ASAS/EUROCONTROL/ 01-024 – Dissemination of CARE/ASAS Results – version 1.1 – June 22, 2001). These rules were distributed to the CARE/ASAS community in July 2001 through Internet.

A proposal for an ASAS Thematic Network (ASAS-TN) was submitted to the European Commission (DG Research) in September 2001. On behalf of EEC, CARE/ASAS built this proposal, which was approved by the EC early 2002. The ASAS-TN kick-off meeting took place on 19-20 November 2002. It is a two-year project. The main objective of the ASAS-TN is to accelerate the implementation of ASAS applications in the European Airspace taking global applicability in order to increase airspace capacity and safety. The ASAS-TN consortium is composed of EEC as the Co-ordinator of the project, six Principal Contractors (THALES Avionics, BAE SYSTEMS, ENAV SpA, LFV, NLR, and THALES ATM) and a body of Members linked to EEC.

The ASAS-TN project was divided into four work-packages:

o WP0 - ASAS-TN Management: WP0 is the management of the Thematic Network;

o WP1 - ASAS-TN Workshops and Seminars: WP1 will organised two-day events on ASAS topics for the R&D community but also for the ATM stakeholders;

o WP2 - ASAS-TN Internet and Document Repository: WP2 implements forums of discussions and ASAS related documents will be made publicly available. In addition to its own objectives, WP2 can support other work-packages through the creation of dedicated WP forums; and

o WP3 - ASAS Implementation Strategy and Reports: WP3 is focus on delivering guideline and recommendations on the required operational and technical standards for ASAS applications and also on further activities and projects required on ASAS.

The ASAS-TN project starting, Activity 0 was reduced to its minimum. The ASAS-TN provided a larger range of networking activities with an increased participation of the industry and all stakeholders.

The CARE website hosted the documents (i.e. programme, presentations and report) of the three ASAS-TN workshops and the final seminar:

o Rome – 28-30 April 2003 – First workshop – “ASAS Operational improvements – Dream or Reality?”

o Malmö – 6-8 October 2003 – Second workshop – “ASAS what does it mean operationally?”

o Toulouse -19-21 April 2004 – Third workshop – “ASAS Making it happen (Airborne and Ground Functions for ASAS Implementation)”



http://www.eurocontrol.int/faa-euro


o Brighton - 11-13 October 2004 – Final seminar - “ASAS Time for Decisions – The Way Forward”

The following website provides detailed information on ASAS-TN: http://www.asas-tn.org/ .

During the ATC Maastricht exhibition (18-20 February 2003), the CARE/ASAS manager presented ‘Package I’ on the European Commission stand. For that purpose, a set of slides (89 slides) was developed and is available with the following reference CARE/ASAS/EURONTROL/03-048 – First Package of Operational Applications enabled by ADS-B (version 1.2 – February 13, 2003).

The 5th EUROCONTROL/FAA ATM R&D Seminar took place in Budapest (Hungary) on 23-27 June 2003. An outline of the papers related to ASAS can be found under the following reference CARE/ASAS/EUROCONTROL/03-053 (version 1.1, July 8, 2003).

The ICAO Eleventh Air Navigation Conference (ANConf/11) took place in Montreal (Canada) on 22 September to 3 October 2003. The document CARE/ASAS/ EUROCONTROL/ 04-064 (version 1.1, May 10, 2004) - Information from ANConf/11 related to ADS-B, ASAS and ACAS – provides an overview of the papers related to ADS-B, ASAS and ACAS that were presented at ANConf/11 with the associated recommendations. This document does not replace the ANConf/11 report which is the only official reference nevertheless it has the objective to help the community working on ADS-B, ASAS and ACAS to better understand the way forward as decided by ANConf/11.

An ASAS-TN2 Co-ordination Action proposal was submitted under Call 2A of the 6th Framework Programme on 31 March 2004. The project was selected by the European Commission in June 2004 and ASAS-TN2 is planned to start early 2005.

The ASAS-TN2 consortium is composed of EEC as the Co-ordinator of the project, six Participants (THALES Avionics, BAE Systems, ENAV SpA, LFV, NLR, and THALES ATM). A body of Members is also identified. The Co-ordinator, the Participants and the Members (called ASAS-TN2 Partners) are entitled the same benefits with regards to the use of the ASAS-TN2.

The ASAS-TN2 project is divided into four work-packages:

• WP0 - ASAS-TN2 Management: WP0 is the management of the Co-ordination Action;

• WP1 - ASAS-TN2 Workshops and Seminar: WP1 will organised two-day events on ASAS/ADS-B topics for the R&D community but also for the ATM stakeholders;

• WP2 - ASAS-TN2 Internet and Document Repository: WP2 implements forums of discussions and ASAS/ADS-B related documents will be made publicly available. In addition to its own objectives, WP2 can support other work-packages through the creation of dedicated WP forums; and

• WP3 – ASAS-TN2 ‘Tableau de Bord’ and Reports: WP3 is focus on delivering a yearly status of the progress towards the implementation of ASAS/ADS-B applications (‘Tableau de Bord’) and the production of reports.

The main ASAS-TN2 outputs concern the sharing of current knowledge on ASAS/ADS-B between all European stakeholders and in recommendations for future activities required to reach the operational use of ASAS/ADS-B applications. It is expected that these results will be of use to guide European actions. The expectation is also that the shared knowledge and the agreed upon recommendations will allow European industry to optimally plan and focus their new products development strategy.

A specific meeting was organised on 26 November 2004 in Haren between the EUROCONTROL EATM programmes/domains, the European Commission and the CARE/ASAS Management Board. The purpose of the meeting was to transfer the CARE/ASAS knowledge and experience to the people now in charge of ASAS applications in Europe.


http://www.asas-tn.org/


3.4. Achievements of Activity 1: Problem dimensions / evaluation of past studies

A call for tender was issued in February 2000. The contract was awarded to a consortium of nine organisations lead by NLR.

The work started in May 2000. The final workshop was held on Monday 2 October 2000 in Haren.

The Activity 1 final report was delivered in November 2000 during the ASAS Technical Interchange Meeting. This report is referenced as CARE/ASAS/NLR/00-012 - CARE/ASAS Activity One: Problem Dimensions / Evaluation of Past Studies (European ASAS literature and Study Review) – Version 2.0 – 23 December 2000.

This report reviews past studies on ASAS performed by European organisations. On going studies are also briefly described. There are at least two ways to take advantage of this work:

- First, a general reading gives an overview of ASAS studies in Europe, the associated issues, which issues were or were not addressed. This view is important at the management level to decide on future activities and projects. The CARE/ASAS Management Board took note of the three recommendations made by the consortium when defining new CARE/ASAS Activities.

- Second, the report provides useful references for more in-depth studies on ASAS applications. It should be considered as a reference document by R&D people. Most references can be found in the CD-Rom produces by CARE/ASAS.

The report was disseminated in April 2001 through mail and Internet as part of Activity 0.



3.5. Achievements of Activity 2: Validation framework for ASAS applications including scenarios

The work started mid-March 2000. EEC (Eric Hoffman) was the leader of this activity for the cooperative work. Several workshops and audio-conferences were organised. The result was the definition of a detailed Activity 2 work plan (ref.: CARE/ASAS/EEC/00-008).

The activity was split into two phases: • Phase 1: Definition of scenarios and metrics. The output was limited to a report. This phase was

initially anticipated to run over a 6 month period and would require about 12 man months of effort.

• Phase 2: Supporting tools. The second phase was optional and conditional on the successful completion of the first one. The joint development/enhancement of supporting tools was envisaged.

WP1.1: Review of Draft Template

WP1.2: Past Experiments Review

WP1.3: Dimension definitionfor ASAS reference scenario

WP1.4: Reference Scenario

WP 1.5 Scenario Repository

WP 1.6 Scenario Report

WP 1: Scenario

WP 2.1: Validation Methodology

WP 2.2: Metrics Review

WP 2.3: Population

WP 2.4: Recommended Measurementsper tool/application

WP 2.5 Validation Report

WP 2: Validation Framework WP 3: Tools (Phase 2)

CARE ASAS Activity 2

Work started on the cooperative mode of CARE/ASAS on the first work-packages (WP1.1, WP1.2, WP2.1 and WP2.2) defined in the above activity work plan. The main contributors were EUROCONTROL Experimental Centre, CENA and University of Glasgow. The result was a report CARE/ASAS/EEC/01-020 - CARE/ASAS Activity 2 - Towards a validation framework for ASAS applications – Version 1.0 - June 12, 2001.

This report was disseminated in September 2001 through Internet as part of Activity 0.

Due to the difficulties to progress the work in the cooperative mode (i.e. lack of resources and other priorities within organisations), it was decided to move to the collaborative mode. Activity 2 participants defined the work to be further progress under the form of a draft technical annex.

On the basis of this technical annex, the CARE/ASAS Management Board decided to launch a call for tender in July 2001. In October 2001, the contract was awarded to a consortium lead by NATS involving AENA, Isdefe, NLR and QinetiQ. The project was called CARE/ASAS Validation Framework (VF) project. The Kick-off meeting was held on 7 November 2001 in London. The objective of the project was to develop firm recommendations for a feasible generic validation framework, comprising standards for scenarios and metrics, and to provide guidance materials and case study examples for its application. The work completed under this project includes the task on operational scenarios, work on the metrics (system and human performance) and the final phase where the framework is applied to the ASAS categories. This work addresses the development of guidance materials and case study examples together with the development of a Research and Development plan for ASAS/ADS-B based concepts. The task has involved consolidating previous work from related projects including ASAS, the EUROCONTROL ‘Validation Data Repository’



(VDR), ‘Master ATM European Validation Plan’ project (MAEVA), INTEGRA and previous human factors work.

The results of the project were presented at a dissemination forum on 10 October 2002 at the EUROCONTROL Experimental Centre, Brétigny. The attendees covered a range of organisations and interests within the ASAS community. There was general agreement that the approach presented was reasonable, however a number of areas that would benefit from further work were discussed.

The main deliverables produced by the VF project are the following:

o CARE/ASAS/Isdefe/02-030 - Initial Framework and Scenario Report (D1);

o CARE/ASAS/Isdefe/02-031 - ASAS Scenario Repository (D2);

o CARE/ASAS/QinetiQ/02-033 - System Performance Metrics Report (D4);

o CARE/ASAS/NLR/02-034 - Human Performance Metrics Report (D5);

o CARE/ASAS/NATS/02-035 - Guideline for Application of VF Report (D6 – two volumes); and

o CARE/ASAS/NATS/02-036 - Final Report (D7).

The VF project report was disseminated in March 2003 through Internet with an introductory message as part of Activity 0.

During the 14th CARE/ASAS Management Board meeting (9 May 2003), it was decided to put CARE/ASAS Activity 2 in standby for two main reasons:

o Validation activities of ASAS applications were taking place in Europe through several projects like NUP II, MFF, Co-Space project, MA-AFAS and Gate-to-Gate; and

o The EUROCONTROL ADS programme had set-up a ‘Validation Plan Drafting Group’ to address the validation of the operational applications included in ‘Package I.



3.6. Achievements of Activity 3: Safety assessment of ASAS applications

The work started mid-March 2000. NLR (Mariken Everdij and Bart Klein-Obbink) was the leader of this activity for the cooperative work. Several workshops and audio-conferences were organised. The result was the definition of a detailed Activity 3 work plan (ref.: CARE/ASAS/NLR/00-009):

Work started on the first work-package (WP1) on the cooperative mode of CARE/ASAS and the document ‘CARE/ASAS/Glasgow University/01-019 - CARE/ASAS Activity 3: Investigation of Experience in Modelling and Determining Separation Minima – version 1.8 – February 22, 2001’ was developed. The main contributors were University of Glasgow, CENA and NLR.

The CARE/ASAS Management Board approved the dissemination of the document after some modifications leading to version 2.0 (June 29, 2001).

This report was disseminated in September 2001 through Internet as part of Activity 0. It was also proposed as an information paper for the ICAO ‘Separation and Airspace Safety Panel’ meeting, which was held in November 2001 in Montreal (Canada).

Because this activity is seen as central to ASAS studies and to accelerate the Activity 3 progress, the CARE/ASAS Management Board decided to move to the collaborative mode. A call for tender was issued in August 2000 for the work-packages 2, 3 & 4 defined in the activity work plan. In October 2000, the contract was awarded to a consortium of organisations composed of Sofréavia (leader), NLR, and EEC and with the participation of CENA and the University of Glasgow. This project was called Airborne Separation Minima (ASM) project. The kick-off meeting was held on 27 November 2000 in Brétigny. The project consisted of the investigation of safety influencing factors that may affect airborne separation minima, and of a first attempt of quantification. A stepwise approach was favoured using recognised methodologies, tailored to meet the objectives of the CARE-ASAS Activity 3. The first two steps, i.e. Operational Service and Environment Description (OSED) and identification of hazards (Operational Hazard Analysis - OHA), were derived from the RTCA/SC189-EUROCAE/WG53 guidance. For the other steps, i.e. the risk estimation and evaluation of airborne separation minima, the ‘Traffic Organization and Perturbation AnalyZer’ methodology was used.

The results of the project were presented at a dissemination forum on 19 December 2001 at the EUROCONTROL Experimental Centre, Brétigny. Forty people attended this event.

The main deliverables produced by the ASM project are the following:

WP0: Management and further detailing CARE-ASAS activity 3 phase 1 work plan

WP1: Investigation of experience in modeling and determining separation minima

WP2: Identification of ASAS operational scenarios

WP3: Identification of factors influencing safety

WP4: Initial model for safe separation

o CARE/ASAS/Sofreavia/01-015 - WP1 Technical Results (D1). This document provides the OSEDs for the autonomous aircraft application and the time-based sequencing application;

o CARE/ASAS/Sofreavia/01-016 – WP2 Technical Results (D2). This document provides the OHAs for the autonomous aircraft application and the time-based sequencing application;



o CARE/ASAS/NLR/01-017 – Estimating Safe Separation Criteria (D3). This document provides the results of a brainstorming session on additional hazards, safety-separation curves based on ‘Traffic Organization and Perturbation AnalyZer’ and an uncertainty analysis of the safety influencing factors. This work is restricted to the autonomous aircraft application; and

o CARE/ASAS/Sofreavia/01-018 – ASM project Final Report (D4).

These documents are available on the CARE/ASAS website.

End of 2001, the CARE/ASAS Management Board agreed to launch a small study (2 to 3 man-months) following the ASM project to gather the lessons learned during the ASM project and to propose recommendations on the safety methodology. The kick-off meeting of the ASM project extension study took place on 18 March 2002.

The final version of the report was delivered on 17 September 2002: CA-02-041 - Lessons learnt from the OSED/OHA activities and hazard brainstorm. The recommendations from this study are the following:

‘On the basis of the overall work performed during the CARE-ASAS ASM study, the following recommendations need to be considered to support future work related to Operational Safety Assessment of ASAS applications:

o RTCA/EUROCAE Operational Safety Assessment (OSA) guidelines should be adapted to better address the characteristics of ASAS applications;

o Guidelines should be developed to support an iterative development of the OSED of an ASAS application along its development life cycle and safety assessment; and

o Guidelines should be developed to support an iterative OHA process combining both top-down (or deductive) and bottom-up (or inductive) approach, as well as severity and frequency assessment.’

The main results of the work were presented during a EUROCAE/WG51 meeting on 9 July 2002. A specific one-day meeting was then organised by EUROCAE/WG51 on 2 December 2002 at EEC to discuss the detailed results and the possible impact on the OSA methodology promoted by EUROCAE.

The ASM project report and the extension study report were disseminated in March 2003 through Internet with an introductory message as part of Activity 0.

During the 14th CARE/ASAS Management Board meeting (9 May 2003), it was decided to put CARE/ASAS Activity 3 in standby because several activities are taking place:

o The ADS programme launched the ‘Airborne Surveillance Functional Architecture’ project involving two consortia. The final report was delivered in September 2003;

o The ACAS programme launched the ‘Implications on ACAS performances due to ASAS implementation’ project (2003-2005);

o The ADS programme launched a safety analysis project on six or seven ‘Package I‘ applications;

o The ADS programme launched recently a project on the definition of separation minima using ADS-B; and

o The MFF project has released some safety work and an internal technical workshop is planned in the near future.



3.7. Achievement of Activity 4: Support to the definition and the validation of selected ASAS applications

The CARE/ASAS Management Board decided to start this activity in October 2001. The work started in the cooperative mode and was going to involve mainly the Management Board members.

Actions were taken to see how CARE/ASAS could contribute to the Cooperative ATS concept and the Airborne Traffic Situational Awareness applications studied by ODIAC.

Initial work on terminology ‘Applications versus Services’ started in October 2001. The document CARE/ASAS/EUROCONTROL/02-039 - Applications and Services was released in February 2002. The document gathers information on the use of the words ‘application’ and ‘service’ in current standard documentation. The main lesson is that the words ‘application’ and ‘service’ are used differently if the approach is system oriented, application oriented or user oriented. To avoid misunderstanding, there is a need to qualify these words when they are used.

In October 2001, it was also decided to develop a document gathering information on ASAS applications studied within European projects. In December 2001, CENA accepted the task as a co-operative contribution to CARE/ASAS Activity 4. The document CARE/ASAS/CENA/02-037 - Review of ASAS Applications studied in Europe was delivered early February 2002. The document provides a description of thirty four ASAS applications studied by some European projects, EUROCONTROL activities and R&D organisations. The analysis of these application resulted in the identification of actually fourteen different ASAS applications.

This CARE/ASAS document was presented to EUROCAE/WG51 (11 February 2002), ODIAC/36 (6-7 March 2002) and SCRSP/WGA (11-15 March 2002) (ref. SCRSP/WGA/WP/A/3-90).

Under the leadership of the EUROCONTROL ADS programme, an OSED Drafting Group was created in December 2002. The objective was to pull the European resources from programmes and projects to define and harmonise Airborne Surveillance and Ground Surveillance applications through the development of OSEDs. CARE/ASAS supported this group for the development of OSEDs for AS applications.

During the 13th CARE/ASAS Management Board meeting (28 January 2003), it was decided to launch a collaborative project addressing ‘The operational benefits and applicability of Package I airborne surveillance applications’. The technical specifications of the project were developed and coordinated with the ADS programme and the AGC programme. The call for tender was issue on 8 April 2003 and the deadline for replies was 5 May 2003. In June 2003, the contract was awarded to a consortium lead by Sofréavia. This consortium involved Sofréavia, CENA, DFS, NATS, University of Glasgow and the participation of EEC, Air-France, British Airways and Lufthansa. The kick-off meeting of the FALBALA project (First Assessment of the operational Limitations, Benefits & Applicability for a List of ‘Package I’ AS applications) took place on 15 July 2003.

The main objective of the FALBALA Project was to perform a first assessment of the operational applicability and the benefits associated with three Airborne Surveillance applications included in ‘Package I’. This first assessment was based on sound and validated data. It considered two perspectives: an airspace perspective and an aircraft perspective. Both qualitative and quantitative assessments of the circumstances, in which, and the frequencies, with which, the applications can be used, and the operational benefits that would accrue, were performed.

The results of the project were presented at a dissemination forum on 8 July 2004 at the EUROCONTROL in Haren (Belgium).

The main deliverables produced by the FALBALA project are the following:

o CARE/ASAS/SOF/04-057 - WP1 - Analysis of the current situation in the Paris, London and Frankfurt TMA;

o CARE/ASAS/CENA/04-058 - WP2 - Airborne perspective analysis report;

o CARE/ASAS/EEC/04-059 - WP3 - Operational benefit report;

o CARE/ASAS/NATS/04-060 - WP4 - Operational workshop and operational interview report; and

o CARE/ASAS/SOF/04-061 - WP5 - Final report of the FALBALA project.



These documents are available on the CARE/ASAS website.

Early 2003, the Requirement Focus Group (RFG) was created as a EUROCONTROL, FAA, EUROCAE and RTCA initiative. The RFG objective is to support the operational implementation of ‘Package I’ through the harmonisation of the applications and the establishment of safety/performance/interoperability requirements. CARE/ASAS supported the RFG work:

• The CARE/ASAS manager acted as European co-chair for three RFG meetings: RFG/2 (June 2003, Haren, Belgium), RFG/3 (December 2003, Washington, USA) and RFG/4 (June 2004, Toulouse, France).

• Participation to the activities of the Application Definition sub-group and the Safety and Performance Requirement sub-group and development of working papers:

o CARE/ASAS/ EUROCONTROL/04-064 (version 1.1, May 10, 2004) - Information from ANConf/11 related to ADS-B, ASAS and ACAS – provides an overview of the papers related to ADS-B, ASAS and ACAS that were presented at ANConf/11 with the associated recommendations; and

o CARE/ASAS/ EUROCONTROL/04-065 (version 1.1, June 18, 2004) - RFG Deliverables and ICAO Standards – explains the relationship between RFG deliverables and the ICAO standards.



3.8. Achievement of Activity 5: Support to the implementation of ASAS applications

CARE/ASAS participated to the IATA/Europe and NLR initiative. The first meeting of the ‘Free Flight Working Group – Operational’ was held on 28 September 2001. The objective of this group was to deliver two documents: An end-goal state document and a transition path document.

Since November 2001, the CARE/ASAS manager was involved in EUROCAE/WG51 work. To help the industry to develop a coherent set of standards, the idea of packaging 'ASAS applications' emerged. The idea was discussed by EUROCAE/WG51 and within EUROCONTROL. It was presented to EUROCAE/WG51 and RTCA/SC186 joint meeting (11-13 February 2002), at ODIAC/36 (6-7 March 2002) and at the ADS-B Symposium in Rome (12-14 March 2002). The idea received strong support and it appeared clearly that CARE/ASAS could assist in building a consensus amongst the various stakeholders.

In February 2002, a small group of experts was created under the leadership of the CARE/ASAS manager to develop this consensus. Several versions of the document were produced and coordinated (e.g. EUROCONTROL, ODIAC, ADS programme steering group, EC projects, IATA and AEA (‘Joint User Requirements Group’ - ADS Fast Track Initiative), EUROCAE and JCB). A mature version 2.0 was delivered at JCB/2 (4 July 2002). During the summer period, a formal commenting process was established. During JCB/3 (30 September 2002), version 2.2 was endorsed. The document is reference as CARE/ASAS/EUROCONTROL/02-040 – Description of a first package of GS/AS applications. The main objective of the document is to describe a first package of operational applications suitable for an early implementation. ADS-B is recognised as a key enabler for GS/AS applications and the proposal is focused on the operational use of ADS-B data to improve the ATM system. The main considerations taken into account for this work are:

o It is focused on operational applications suited for core European high-density traffic areas without excluding other areas, in line with the ATM2000+ strategy and the expected Operational Improvements. Global applicability is also a key consideration;

o The operational needs of airborne and ground users are considered; and

o It seeks to facilitate the elaboration of operational and technical standards required for the implementation of these operational applications.

At JCB/2 (4 July 2002) and on behalf of CARE/ASAS, Eric Hoffman (EEC) was tasked to map the operational applications of ‘Package I’ and the applications studied in the JCB projects. The document is referenced CARE/ASAS/EUROCONTROL/02-044 - Joint Coordination Board (JCB) Projects mapping to ‘Package I’ Applications. The A draft version was presented at JCB/3 (30 September 2002). After the review by the CARE/ASAS Management Board members, the final version was delivered at JCB/4 (6 February 2003).

In parallel to the definition of ‘Package I’ and on behalf of CARE/ASAS, another small group of experts was created under the leadership of Christos Rekkas (EUROCONTROL) with the objective to develop a deliverable called CARE/ASAS/EUROCONTROL/02-042 - Proposal for working arrangements to develop ‘Package I’ of AS/GS applications. The objective of this document was to contribute to the definition of the Master Plan and Working Arrangements between the various involved parties in the area of ‘Package I’ Airborne Surveillance/Ground Surveillance (AS/GS) applications. The document was reviewed during the consultation process with various stakeholder fora: i.e. EUROCAE/WG51, ADS programme steering group, ODIAC, JCB and IATA/AEA. The document focuses on the following areas:

o List of required deliverables (“WHAT”);

o Interdependencies between the deliverables and overall process (“HOW”);

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

o Master Plan (“WHEN”).

The document was delivered to JCB through Internet with an introductory message on 11 July 2003.



4. Termination of CARE/ASAS

CARE is an initiative to define co-operative R&D actions, which address issues of high priority. CARE actions were defined individually with a limited time duration, clear objectives and well defined deliverables.

Started in 1999, CARE/ASAS has successfully delivered. The CARE/ASAS Management Board meetings brought together European ASAS experts three to four times a year. Communications between the R&D organisations was improved and decisions were taken taking account the various perspectives.

CARE/ASAS proposed the grouping of ASAS applications into packages which includes also ground surveillance applications. This approach got international recognition and was presented and endorsed at the ICAO Air Navigation Conference (ANConf/11) in September 2003.

Now, within the EUROCONTROL agency, EATM programmes and domains are in charge of ASAS applications and therefore CARE/ASAS is not funded beyond 2004. Within EATM, the current status is:

• ‘Package I’ is the responsibility of the CASCADE programme; and

• ‘Package II and III’ are the responsibility of the ATS and CSM domains.

The three packages cannot be considered independent and good coordination should be established between the CASCADE programme and the ATS and CSM domains.

To support CARE/ASAS Activity 0 on Communications, the ASAS-TN project, sponsored by the European Commission, was set-up. Beyond the R&D community, there was a need to communicate with all stakeholders (i.e. airlines, ANS providers, pilots and controllers associations, ATM industry, Aircraft industry and Avionics industry). The project has achieved its objectives and ends in mid-November 2004.

An ASAS-TN2 proposal was submitted under Call 2A of the 6th Framework Programme on 31 March 2004. The project was selected by the European Commission in June 2004 and ASAS-TN2 is planned to start early 2005. It is essential to maintain a communication activity on ASAS/ADS-B applications.



Acronyms

ACAS Airborne Collision Avoidance System

ADS Automatic Dependent Surveillance

ADS-B Automatic Dependent Surveillance - Broadcast

AEA Association of European Airlines

AGC Air/Ground Cooperative ATS (EATM programme)

ANConf/11 11th ICAO Air Navigation Conference

AS Airborne Surveillance

ASAS Airborne Separation Assistance Systems

ASAS-TN ASAS Thematic Network

ASM Airborne Separation Minima (CARE/ASAS Activity 3 project)

ATC Air Traffic Control

ATM Air Traffic Management

CARE Co-operative Actions of R&D in EUROCONTROL

CASCADE Co-operative ATS through Surveillance and Communication Applications Deployed in ECAC (EATM programme)

CENA Centre d’Etudes de la Navigation Aérienne

CNS Communication, Navigation, Surveillance

CoU-ASAS ASAS concept of use document (Action Plan 1 of FAA/EUROCONTROL R&D Committee)

CSM EATM domain

DAP/SAF Directorate ATM programmes / Safety Enhancement

DAP/SPR Directorate ATM programmes / Sector Productivity

DAS/AFN Directorate ATM Strategies / Airspace Flow management & Navigation

DAS/ATS Directorate ATM Strategies / Air Traffic Services

DFS Deutsche Flug Sicherung

DG Research Directorate General Research

DG TREN Directorate General - Transport

EATM EUROCONTROL Air Traffic Management (programme)

EC European Commission

ECAC European Civil Aviation Conference

EEC EUROCONTROL Experimental Centre

EMERALD EMErging RTD Activities of reLevance for ATM concept Definition

ENAV Ente Nazionale di Assistenza al Volo

EUROCAE European Organisation for Civil Aviation Electronics

EUROCAE/WG51 EUROCAE Working Group 51

FAA Federal Aviation Administration



FALBALA First Assessment of the operational Limitations, Benefits & Applicability for a List of ‘Package I’ AS applications (CARE/ASAS Activity 4 project)

GS Ground Surveillance

IATA International Air Transport Association

ICAO International Civil Aviation Organisation

INTEGRA Advanced ATM Tool Integration Project (CARE Action)

ISDEFE Ingeniera de Systemas

JAA Joint Airworthiness Authority

JCB Joint Coordination Board

LFV Luftfartsverket (Swedish Civil Aviation Administration)

MA-AFAS More Autonomous Aircraft in the Future ATM System (project)

MFF Mediterranean Free Flight (project)

NATS National Air Traffic Services

NLR Nationaal Lucht en Ruimtevaartlaboratorium

NUP NEAN Update Program

ODIAC Operational Development of Integrated surveillance and Air/ground Data Communication

OHA Operational Hazard Analysis

OSA Operational Safety Analysis

OSED Operational Service and Environment Description

PO-ASAS Principles of Operation for the Use of ASAS document (Action Plan 1 of FAA/EUROCONTROL R&D Committee)

R&D Research and Development

RDCom FAA/EUROCONTROL R&D Committee

RFG Requirement Focus Group

RTCA Radio Technical Commission for Aeronautics

RTCA/SC186 RTCA Special Committee 186

RTD Research and Technical Development

SAF-ASAS Safety and ASAS applications document (Action Plan 1 of FAA/EUROCONTROL R&D Committee)

SCRSP/WGA Surveillance and Conflict Resolution System Panel (former ICAO SICASP) / Working Group A

SD/ESC Senior Directorate / European ATM System and Convergence

SICTA Sistemi Innovativi per il Controllo del Traffico Aereo

VF Validation Framework (CARE/ASAS Activity 2 project)

WP Work-package


care/asas action plan - eurocontrol.int · care/asas action plan asas in care account various...

Documents