02.11.2014 Views

7754 Vol 2 Flyleaf - ICAO Public Maps

7754 Vol 2 Flyleaf - ICAO Public Maps

7754 Vol 2 Flyleaf - ICAO Public Maps

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

V.II-E1<br />

Attachment E<br />

CONSIDERATIONS RELEVANT TO THE USE OF<br />

AUTOMATED DIGITAL DATA INTERCHANGE (ADDI)<br />

FOR ATC COORDINATION<br />

(Paragraph 27, Part V.II — ATS of the EUR Basic ANP and<br />

Paragraph 23, Part V.II — ATS of the EUR FASID refer)<br />

GENERAL<br />

1. The messages used for the application of<br />

automated digital data interchange for ATC coordination<br />

procedures should, to the extent possible, be in accordance<br />

with those specified in Procedures for Air Navigation<br />

Services — Air Traffic Management (PANS-ATM, Doc<br />

4444) unless an alternative format has been bilaterally<br />

agreed. In any event, ATS systems shall support the<br />

construction of the messages based on the provisions<br />

specified in Doc 4444, Appendix 3.<br />

2. The application of computer-assisted coordination<br />

procedures in the EUR region shall be based on a<br />

step-by-step data distribution scheme comprising as a<br />

minimum the two phases NOTIFICATION and<br />

COORDINATION. Messages shall be automatically<br />

generated, exchanged and processed to obviate human<br />

intervention to the extent possible. Furthermore, messages<br />

shall provide the most recent information available on flight<br />

plan data at the time of transmission.<br />

3. The advanced boundary information (ABI) shall be<br />

used for notification, and the activation (ACT),<br />

pre-activation (PAC) and revision (REV) messages shall be<br />

used for coordination. All correctly processed messages<br />

shall be acknowledged by a logical acknowledgement<br />

message (LAM).<br />

4. There shall be bilateral agreement on the<br />

coordination point (COP) and transmission times for each<br />

route. Acceptance by the receiving ATC unit of the transfer<br />

conditions implied in the message shall be assumed, unless<br />

the receiving ATC unit initiates verbal coordination to<br />

amend the transfer conditions.<br />

5. In the event that the receiving ATC unit cannot<br />

correlate the data or that the data is incomprehensible or<br />

illogical, the appropriate ATC sector shall be warned if<br />

identifiable.<br />

6. For detailed information on how to implement, in<br />

the EUR region, the methods of application specified below,<br />

account shall be taken of the current document which<br />

specifies the use of automated digital data interchange for<br />

ATC coordination published by EUROCONTROL and<br />

updated from time to time.<br />

UNITS OF MEASUREMENT<br />

7. This section specifies the units of measurement to<br />

be used in <strong>ICAO</strong> messages. If other formats are used by<br />

bilateral agreement, they shall contain the same items of<br />

data but not necessarily in the same format.<br />

Time and date<br />

8. All times shall be expressed in UTC as four digits<br />

in the form HHMM with midnight expressed as 0000. Dates,<br />

when used, shall be in the form of YYMMDD.<br />

Geographic position information<br />

9. Geographic position information shall be in<br />

accordance with the provisions contained in Procedures for<br />

Air Navigation Services — Air Traffic Management<br />

(PANS-ATM, Doc 4444).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!