Об установлении детализированных правил для имплементации функций сетей при организации воздушного движения и о внесении изменений в Регламент (ЕС) 691/2010″ [рус., англ.] Часть 7

1   2   3   4   5   6   7

Annex III

THE TRANSPONDER CODE FUNCTION

Part A

Requirements for the Transponder Code Function

  1. The objectives of this function are:

(a) to improve the robustness of the code allocation process through allocation of clear roles and responsibilities to all involved stakeholders, with the overall network performance at the centre of code allocation determination;

(b) to provide increased transparency of code allocations and of the actual code usage enabling the better assessment of the overall network efficiency;

(c) through enshrinement in regulation, to provide the regulatory basis allowing better enforcement and oversight.

  1. SSR transponder codes shall be allocated through the Network Manager to the Member States and the air navigation service providers in a manner that optimises their safe and efficient distribution taking the following into account:

(a) the operational requirements of all operational stakeholders;

(b) the actual and predicted levels of air traffic;

(c) the required use of SSR transponder codes in compliance with relevant provisions of the ICAO Regional Air Navigation Plan, European Region, Facilities and Services Implementation Document and guidance material.

  1. An SSR transponder code allocation list that describes the complete and up-to-date allocation of SSR codes in the airspace laid down in Article 1(3) shall be made available to Member States, air navigation service providers and third countries at all times by the Network Manager.
  2. A formal process for establishing, assessing and coordinating the requirements for SSR transponder code allocations shall be implemented by the Network Manager, taking into account all required civil and military uses of SSR transponder codes.
  3. The formal process laid down in point 4 shall include, as a minimum, relevant agreed procedures, timescales and performance targets for the completion of the following activities:

(a) submission of applications for SSR transponder code allocations;

(b) assessments of applications for SSR transponder code allocations;

(c) coordination of proposed amendments to SSR code transponder allocations with Member States and third countries in accordance with the requirements laid down in Part B;

(d) periodic audit of the SSR code allocations and needs with a view to optimisation of the situation, including re-allocation of existing code allocations;

(e) periodic amendment, approval and distribution of the overall SSR code transponder allocation list laid down in point 3;

(f) notification, assessment and resolution of unplanned conflicts between assignments of SSR transponder codes;

(g) notification, assessment and resolution of wrong assignments of SSR transponder codes, detected at code retention checks;

(h) notification, assessment and resolution of unplanned shortfalls in allocations of SSR transponder codes;

(i) provision of data and information in accordance with the requirements laid down in Part C.

  1. Applications for SSR transponder code allocations received as part of the process laid down in point 4 shall be checked by the Network Manager for compliance with the requirements of the process for format and data conventions, completeness, accuracy, timeliness, and justification.
  2. Member States shall ensure that SSR transponder codes are assigned to aircraft in accordance with the SSR transponder code allocation list contained in point 3.
  3. A centralised SSR transponder code assignment and management system for the automatic assignment of SSR transponder codes to general air traffic may be operated by the Network Manager on behalf of the Member States and air navigation service providers.
  4. Procedures and tools for the regular evaluation and assessment of the actual use of SSR transponder codes by Member States and air navigation service providers shall be implemented by the Network Manager.
  5. Plans and procedures shall be agreed between the Network Manager, Member States and air navigation service providers to support the periodic analysis and identification of future SSR transponder code requirements. This analysis shall include the identification of potential performance impacts created by any predicted shortfalls in the allocations of SSR transponder codes.
  6. Operations manuals containing the necessary instructions and information to enable the network function to be conducted in accordance with the requirements of this Regulation shall be developed and maintained. These operations manuals shall be distributed and maintained in accordance with appropriate quality and documentation management processes.

 

Part B

Requirements for the specific consultation mechanism

  1. A dedicated mechanism for the coordination and consultation of detailed SSR transponder code allocation arrangements shall be established by the Network Manager, that:

(a) ensures the impact of the use of SSR transponder codes in third countries is taken into account through participation in the SSR transponder code management working arrangements set out in the relevant provisions of the ICAO Regional Air Navigation Plan, European Region, Facilities and Services Implementation Document;

(b) ensures the SSR transponder code allocation list laid down in point 3 of Part A is compatible with the code management plan set out in the relevant provisions of the ICAO Regional Air Navigation Plan, European Region, Facilities and Services Implementation Document;

(c) specifies requirements to ensure that appropriate consultation on new or amended SSR transponder code management arrangements is conducted with the Member States concerned;

(d) specifies requirements to ensure that appropriate consultation on new or amended SSR transponder code management arrangements is conducted by Member States with all stakeholders concerned at a national level;

(e) ensures coordination with third countries on the strategic and tactical use of SSR transponder codes is conducted through the SSR transponder code management working arrangements set out in the relevant provisions of the ICAO Regional Air Navigation Plan, European Region, Facilities and Services Implementation Document;

(f) specifies minimum timescales for the coordination and consultation of proposed new or amended SSR transponder code allocations;

(g) ensures changes to the SSR transponder code allocation list are subject to the approval of those Member States concerned by the change;

(h) specifies requirements to ensure that changes to the SSR transponder code allocation list are communicated to all stakeholders immediately after its approval, without prejudice to national procedures for the communication of information on the use of SSR transponder codes by military authorities.

  1. The Network Manager, in coordination with national military authorities, shall ensure that the necessary measures are taken to ascertain that the allocation and use of SSR transponder codes for military needs have no detrimental impact on the safety or efficient flow of general air traffic.

 

Part C

Requirements for the provision of data

  1. Applications submitted for new or amended allocations of SSR transponder codes shall comply with the format and data conventions, completeness, accuracy, timeliness, and justification requirements of the process laid down in point 4 of Part A.
  2. The following data and information shall be provided to the Network Manager by Member States, as required, within agreed timescales prescribed by the Network Manager to support the provision of the network function for SSR transponder codes:

(a) an up-to-date record of the allocation and use of all SSR transponder codes within their area of responsibility, subject to any security constraints concerning full disclosure of specific military code allocations not used for general air traffic;

(b) justification to demonstrate that existing and requested allocations of SSR transponder codes are the minimum necessary to meet operational requirements;

(c) details of any allocations of SSR transponder codes that are no longer operationally required and that can be released for re-allocation within the network;

(d) reports of any actual unplanned shortfall in SSR transponder code allocations;

(e) details of any change in the installation planning or in the operational status of systems or constituents that may impact on the assignment of SSR transponder codes to flights.

  1. The following data and information shall be provided to the Network Manager by air navigation service providers, as required, within agreed timescales prescribed by the Network Manager to support the provision of the network function for SSR transponder codes:

(a) Enhanced Tactical Flow Management System’s Correlated Position Reports containing SSR transponder code assignments for general air traffic conducting flights under instrument flight rules;

(b) reports of any actual unplanned conflict or hazard caused by an actual operational SSR transponder code assignment, including information of how the conflict was resolved.

  1. Responses by Member States and air navigation service providers to the coordination of proposed amendments to SSR code transponder allocations and updates of the SSR transponder code allocation list shall as a minimum:

(a) identify whether or not any conflict or hazard between SSR transponder code allocations is foreseen;

(b) confirm whether or not operational requirements or efficiency will be adversely affected;

(c) confirm that amendments to SSR transponder code allocations can be implemented in accordance with required timescales.

 

Annex IV

TEMPLATE FOR NETWORK STRATEGY PLAN

The Network Strategy Plan shall be based on the following structure:

  1. Introduction

1.1. Scope of the Network Strategy Plan (geographical and time period)

1.2. Preparation of the plan and validation process

 

  1. Overall context and requirements

2.1. Description of the current and planned network situation including ERND, ATFM, airports and scarce resources

2.2. Challenges and opportunities related to the time period of the plan (including traffic demand forecast and worldwide evolution)

2.3. Performance Objectives and business requirements as expressed by the different stakeholders and the Union-wide performance targets

 

  1. Strategic vision

3.1. Description of the strategic way the network will develop and progress to successfully respond to the performance targets and business requirements

3.2. Compliance with the performance scheme

3.3. Compliance with the European ATM master plan

 

  1. Strategic objectives

4.1. Description of the Network strategic objectives:

(a) including the cooperative aspects of the participating operational stakeholders in terms of roles and responsibilities;

(b) indicating how the strategic objectives will answer the requirements;

(c) identifying how progress towards these objectives will be measured;

(d) indicating how the strategic objectives will impact the industry and other concerned areas.

 

  1. Strategic planning

5.1. Description of the short/medium term planning:

(a) the priorities for each of the strategic objectives;

(b) the implementation of each of the strategic objectives in terms of required deployment of technology, architectural impact, human aspects, involved cost, benefits as well as the necessary governance, resources and regulation;

(c) the required operational stakeholder participation on each element of the plan including their roles and responsibilities;

(d) the agreed level of involvement of the Network Manager to support the implementation of each element of the plan for each individual function.

5.2. Description of the long term planning:

(a) the intent to reach each of the strategic objectives in terms of required technology and corresponding R & D aspects, architectural impact, human aspects, business case, governance required, and regulation required as well as the associated safety and economic justification for these investments;

(b) the required operational stakeholder participation on each element of the plan including their roles and responsibilities.

 

  1. Risk assessment

6.1. Description of the risks associated with the implementation of the plan

6.2. Description of the monitoring process (including potential deviation from initial objectives)

 

  1. Recommendations

7.1. Identification of the actions to be taken by the Union and Member States to support the implementation of the plan.

 

Annex V

TEMPLATE FOR NETWORK OPERATIONS PLAN

The Network Operations Plan shall be based on the following general structure (that will be tailored to the various individual functions and to the time horizon of the Network Operations Plan to reflect its rolling nature and its 3 to 5 year, annual, seasonal, weekly and daily periods):

 

  1. Introduction

1.1. Scope of the Network Operations Plan (geographical and time period)

1.2. Preparation of the plan and validation process

 

  1. Description of the Network Operations Plan, operational targets and objectives

— including the collaborative aspect of the participating operational stakeholders in terms of roles and responsibilities,

— indicating how the operational targets and objectives will be covered in the tactical, pre-tactical, short-term and medium-term phases of the Network Operations Plan and other performance targets set under the performance regulation,

— priorities set and resources needed for the planning period,

— indicating the impact on the ATM industry and other concerned areas.

 

  1. Overall network operations planning process

— description of the overall network operations planning process,

— description of the strategic way the Network Operations Plan will evolve and progress to successfully respond to the operational performance requirements and other performance targets set under the performance Regulation,

— description of tools and data used.

 

  1. Overall context and operational requirements

4.1. Summary description of the past network operational performance

4.2. Challenges and opportunities related to the time period of the plan

4.3. Network traffic forecast in accordance with Appendices 1 and 2, including:

— network forecast,

— air navigation service provider, functional airspace block and ACC forecast,

— main airports forecast,

— analysis of the traffic forecast, including a range of scenarios,

— analysis of special events impact.

4.4. Network operational performance requirements, including:

— overall network capacity requirements,

— air navigation service provider, functional airspace block and ACC capacity requirements,

— airport capacity,

— analysis of the capacity requirements,

— overall network environment/flight efficiency requirements,

— overall network safety requirements,

— contingency requirements and continuity of services affecting the network.

4.5. Operational needs as expressed by the different stakeholders, including military

 

  1. Network operational performance enhancement plans and actions at network level

— description of the plans and actions expected to be implemented at network level, including airspace, scarce resources and ATFM,

— description of the operational performance contributions of each of the plans and actions.

 

  1. Operational performance enhancement plans and actions at local level

— including description of each of the plans and actions expected to be implemented at local level,

— description of the operational performance contributions of each of the plans and actions,

— description of relations with third countries and work related to ICAO.

 

  1. Special events

— overview of special events with significant ATM impact,

— individual special events and their handling from an network perspective,

— major military exercises.

 

  1. Military airspace requirements

8.1. Military ATM service providers responsible for areas of reserved or segregated airspace shall exchange with the Network Manager, through the relevant Airspace Management Cell, the following information according to national rules:

— airspace availability: default days/times of availability of reserved airspace,

— ad hoc requests for unplanned use of reserved airspace,

— release of reserved airspace to civil use whenever not required, giving as much notice as possible.

 

  1. Consolidated forecast and analysis of the operational performance of the network

— network, air navigation service provider, functional airspace block and ACC ATM delay/capacity targets and forecast,

— airport operational performance,

— network environment/flight efficiency performance target and forecast,

— impact of special events,

— analysis of the operational performance targets and forecast.

 

  1. Identification of operational bottleneck areas and mitigation solutions at network and local level

— identification of operational (safety, capacity, flight efficiency) bottlenecks and potential bottlenecks, their causes and agreed solutions or mitigation actions, including options for demand capacity balancing (DCB).

 

Appendix 1

AREA CONTROL CENTRES (ACCS)

The Network Operations Plan shall give a detailed description ACC by ACC of all the areas describing their planned operational enhancement measures, the prospects for the period, the traffic forecast, the delay target and forecast, the significant events that may affect the traffic, operational contacts.

The Network Manager shall include for each ACC:

— traffic forecast,

— an analysis of current operational performance,

— a quantified evaluation of the achieved capacity (capacity baseline),

— a quantified evaluation of the required capacity for various traffic evolutions scenarios (required capacity profile),

— a quantified evaluation of the planned operational enhancement actions at ACC level, as agreed with the air navigation service providers,

— delay target and forecast,

— an analysis of expected operational performance (safety, capacity, environment).

Each air navigation service provider shall provide the Network Manager with the following information to be included in the individual ACC description:

— local delay target,

— assessment/confirmation of traffic forecast, taking into account local knowledge,

— number of available sectors: sector configuration/opening scheme per season/day of week/time of day,

— capacities/monitoring values for each sector/traffic volume per configuration/opening scheme,

— planned or known special events, including dates/times and associated impact on operational performance,

— details of operational enhancement measures planned, their implementation schedule and associated negative/positive impact on capacity and/or efficiency,

— details of proposed and confirmed changes to the airspace structure and utilisation,

— additional actions as agreed with the Network Manager,

— ACC operational contacts.

 

Appendix 2

AIRPORTS

The Network Operations Plan shall give a detailed description for main European airports of all the areas describing their planned operational enhancement measures, the prospects for the period, the traffic and delay forecast, the significant events that may affect the traffic, operational contacts.

The Network Manager shall include for each main airport:

— traffic forecast,

— an analysis of expected operational performance (safety, capacity, environment).

Each airport included in the Network Operations Plan shall provide the Network Manager with the following information to be included in the individual airport description:

— assessment/confirmation of traffic forecast, taking into account local knowledge,

— runway capacity for each runway configuration, current and projected arrivals and departures,

— a capacity specification for and duration of night period, where relevant,

— details of operational enhancement measures planned, their implementation schedule and associated negative/positive impact on capacity and/or efficiency,

— planned or known special events, including dates/times and associated impact on operational performance,

— other planned capacity enablers,

— additional actions as agreed with the Network Manager.

 

Annex VI

GENERAL REQUIREMENTS FOR NETWORK FUNCTIONS

  1. Organisational structure

The Network Manager shall set up and manage its organisation according to a structure that supports the safety of the network functions.

The organisational structure shall specify:

(a) the authority, duties and responsibilities of the nominated post holders, in particular of the management personnel in charge of safety, quality, security and human resources related functions;

(b) the relationship and reporting lines between different parts and processes of the organisation.

 

  1. Safety

The Network Manager shall have a safety management system which covers all the network functions it performs according to the following principles. It shall:

(a) describe the overall philosophies and principles of the organisation with regard to safety and in such a way as to meet the needs of relevant stakeholders as closely as possible, (hereinafter «the policy»);

(b) set up a compliance monitoring function that contains procedures designed to verify that all functions are being provided in accordance with applicable requirements, standards and procedures. Compliance monitoring shall include a feedback system of findings to the responsible management personnel to ensure effective and timely implementation of corrective actions as necessary;

(c) provide evidence of the functioning of the management system by means of manuals and monitoring documents;

(d) appoint management representatives to monitor compliance with, and adequacy of, procedures to ensure safe and efficient operational practices;

(e) perform reviews of the management system in place and take remedial actions, as appropriate;

(f) manage the safety of all network functions allocated to it. In doing so, it shall establish formal interfaces with all the relevant stakeholders to be able to identify the aviation safety hazards entailed by its activities, to evaluate them and to manage the associated risks as appropriated;

(g) contain procedures for managing the safety when introducing new functional systems or changing the existing functional systems.

 

  1. Security

The Network Manager shall have a security management system which covers all the network functions it performs according to the following principles. It shall:

(a) ensure the security of its facilities and personnel so as to prevent an unlawful interference that could impact the safety of the network functions it manages;

(b) ensure the security of operational data it receives or produces or otherwise employs, so that access to it is restricted only to those authorised;

(c) define the procedures relating to security risk assessment and mitigation, security monitoring and improvement, security reviews and lesson dissemination;

(d) define the means designed to detect security breaches and to alert personnel with appropriate security warnings;

(e) define the means of containing the effects of security breaches and to identify recovery action and mitigation procedures to prevent reoccurrence.

 

  1. Operations manuals

The Network Manager shall establish and keep up-to-date operations manuals relating to its operations, for the use and guidance of operations personnel. It shall ensure that:

(a) operations manuals contain instructions and information required by the operations personnel to perform their duties;

(b) relevant parts of the operations manuals are accessible to the personnel concerned;

(c) the operations personnel are expeditiously informed of the amendments to the operations manual applying to their duties as well as of their entry into force.

 

  1. Personnel requirements

The Network Manager shall employ appropriately skilled personnel to ensure that the network functions allocated to it are performed in a safe, efficient, continuous and sustainable manner. In this context, it shall establish policies for the training of personnel.

 

  1. Contingency plans

The Network Manager shall establish contingency plans for all the functions it provides in the case of events which result in significant degradation or interruption of its operations.

 

  1. Reporting requirements

In accordance with Article 20, the Network Manager shall provide an annual report of its activities. This report shall cover its operational performance, as well as significant activities and developments in particular in the area of safety.

The annual report shall include as a minimum:

— an assessment of the performance of the network functions it manages,

— the performance compared to the performance objectives established in the Network Strategy Plan, reconciling actual performance against the Network Operational plan by using the indicators of performance established in the Network Operational plan,

— provide an explanation for differences with the targets, and identify measures for closing any gaps during the Reference Period referred to in Article 11 of Regulation (EC) No 549/2004,

— developments in operations and infrastructure,

— information about the formal consultation process with the users and stakeholders,

— information about the human resources policy.

 

  1. Working methods and operating procedures

The Network Manager shall be able to demonstrate that its working methods and operating procedures are compliant with other Union legislation and in particular with Regulation (EU) No 255/2010.

1   2   3   4   5   6   7

Добавить комментарий

Ваш e-mail не будет опубликован.

*

code