ifps update - icao.int meetings seminars and... · training . 3 field 10a ... (eobd/eobt) i.e....

47
IFPS Update Kim Breivik 2012 Project Manager & EUR Task Force Chairman Operational Specifications & Requirements CFMU © EUROCONTROL2010 Central Flow Management Unit FPL 2012 Implementation Workshop Georgia 20-22 September 2011

Upload: others

Post on 13-Jul-2020

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

IFPS Update

Kim Breivik

2012 Project Manager & EUR Task Force Chairman

Operational Specifications & Requirements

CFMU

© EUROCONTROL2010 – Central Flow Management Unit

FPL 2012 Implementation Workshop

Georgia 20-22 September 2011

Page 2: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

2

Content

● Detailed Syntax & Semantic Checks

● ‘European Compromise’

● Translation

● DOF Usage

● Transition

● Submission & IFPS Addressing

● Training

Page 3: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

3

Field 10a – NAV/COM Equipment and Capability

Syntax:

● Description: The descriptor "N" or one or more of the listed

descriptors without repetition, therefore a theoretical limit of 64

characters

● No longer accepted: E, P, M, J, Q.

● New: Letter & Digit combinations

Semantics:

If ‘R’ present PBN/ expected in F18

If ‘Z’ present at least one of COM/, DAT/, NAV expected in F18

Page 4: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

4

Field 10b – SUR Equipment and Capability

Syntax:

● Description: The descriptor 'N'

or, either one or more of the descriptors ‘I’, ‘P’, ‘X’, ‘A’, ‘C’ with ‘I’, ‘P’, ‘X’ being mutually exclusive i.e. only one may be present

or, one or more of the descriptors ‘A’, ‘C’, ‘E’, ‘H’, ‘L’, ‘S’ Plus optionally, one or more of the descriptors ‘B1’, ‘B2’, ‘D1’, ‘G1’, ‘U1’, ‘U2’, ‘V1’, ‘V2’ without repetition. A total limit of 20 characters shall be applied

● No longer accepted: D

● New: Letter&Digit combinations

Semantics:

None

Page 5: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

5

Field 18 – Duplicate Indicators

● If duplicates of the following are found they will be concatenated into a single entity with a space inserted between data streams: STS/, NAV/, COM/, DAT/, SUR/, EET/, TYP/, DLE/, ALTN/, RALT/, TALT/, RMK/

Eg. STS/HEAD STS/ATFMX STS/HEAD ATFMX

● If duplicates of the following are found an error shall be raised:

DEP/, DEST/, DOF/, OPR/, RVR/, SEL/, REG/, PBN/, CODE/, ORGN/, PER/, RFP/

Page 6: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

6

Syntax - Field 18 Indicators

● Field 18 Indicators – IFPS Syntax STS - one or more of the listed descriptors only

RMK - no limit

RVR - 1 to 3 digits

DAT - up to 50 chars

SUR - up to 50 chars

NAV - up to 50 chars

COM - up to 50 chars

TYP - up to 60 chars

ORGN - up to 30 chars

REG - up to 50 chars

DEP - aerodrome name – up to 50 chars - optionally lat & long or reference point

DEST - as for Dep.

RALT - up to 100 chars

TALT - up to 100 chars

ALTN - up to 100 chars

DLE - up to 11 chars followed by 4 digits

PER - one of the listed chars (A, B, C, D, E, H)

RFP - „Q‟ followed by a single digit from 1 to 9

Page 7: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

7

Syntax - Field 18 Indicators

● PBN

one to eight of the listed descriptors, a total of 16 chars

● If present the descriptor "R" shall be present in Field 10a

● If any of the indicators B1, B2, C1, C2, D1, D2, O1 or O2 are filed, then a “G” must be present in Field 10a.

● If any of the indicators B1, B3, C1, C3, D1, D3, O1 or O3 are filed, then a “D” must be present in Field 10a.

● If either of the indicators B1 or B4 is filed, then either an “O” or “S” must be present and a “D” must also be present in Field 10a.

● If any of the indicators B1, B5, C1, C4, D1, D4, O1 or O4 are filed, then an “I” must be present in Field 10a.

● If any of the indicators C1, C4, D1, D4, O1 or O4 are filed, then a “D” must be present in Field 10a

Page 8: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

8

Content

● Detailed Syntax & Semantic Checks

● ‘European Compromise’

● Translation

● DOF Usage

● Transition

● Submission & IFPS Addressing

● Training

Page 9: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

9

European Compromise [1]

● Use of RVR/ and RFP/ in Field 18

Currently defined in Doc.7030

Not included in Amendment 1

Will be retained in Doc 7030, used in Field 18 and output by

IFPS in the following order:

STS/, PBN/, NAV/, COM/, DAT/, SUR/, DEP/, DEST/, DOF/, REG/,

EET/, SEL/, TYP/, CODE/, RVR/, DLE/, OPR/, ORGN/, PER/,

ALTN/, RALT/, TALT/, SRC/, RIF/, RMK/, RFP/

● Indication of security-related flights

Currently implemented via the use of STS/

Not permitted under Amendment 1

Will be implemented via EUR/PROTECTED and only permitted

for FPLs submitted directly to IFPS

● Will not be received by ATC units

Page 10: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

10

European Compromise [2]

● Indication of exemptions to RNAV, CPDLC and 8.33kHz

requirements

Currently defined in Doc. 7030 via the use of STS/

Not included in Amendment 1

Will be removed from Doc. 7030

Will be implemented via Fields 10 & 18 as follows:

● Field 10 to include „Z‟

● Field 18 to include, as appropriate:

COM/EXM833

NAV/RNAVX, NAV/RNAVINOP

DAT/CPDLCX

Page 11: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

11

Unresolved Issues

● Some outstanding issues:

Use of RMK/, an unstructured field containing „Other Information‟, to provide significant operational data is unacceptable for automated processing systems

How to extract a non-specified reason for special handling from within a free text RMK field i.e. to identify some significant unspecified text from within other text!

How to implement new data requirements without requiring a coordinated worldwide modification of FDPSs for every new requirement

How to indicate the regional applicability of exemption indications

How to address regional requirements in a manner that will not unduly impact other regions

Page 12: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

12

Content

● Detailed Syntax & Semantic Checks

● ‘European Compromise’

● Translation

● DOF Usage

● Transition

● Submission & IFPS Addressing

● Training

Page 13: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

13

IFPS Translation Function

● IFPS will offer a Translation Function from New FPL to

Present FPL

To enable AOs to migrate early

To provide flexibility and mitigation for ANSPs in case of difficulties

Translation is only New to Present (not Present to New)

For Safety and Legal reasons, the proposed translation tables

ensure that no information is lost, it is moved to where it can logically

belong and syntactically fits

Page 14: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

14

Field 18 [1]

Page 15: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

15

Field 18 [2]

Page 16: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

16

Field 10a [1]

Page 17: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

17

Field 10a [2]

Page 18: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

18

Field 10a [3]

[3] The translation

shall result in the

removal of the „Z‟ if

no other data is

present within either

of the COM/ or NAV/

indicators

[4] The NEW

definition of DAT/

allows free text, the

OLD definition does

not. If the NEW DAT/

is compliant with the

OLD definition it shall

be retained within

DAT/ and a „J‟ added

in Field 10a, if the

NEW DAT/ contains

free text it shall be

translated into COM/.

Page 19: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

19

Field 10b [1]

Page 20: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

20

Content

● Detailed Syntax & Semantic Checks

● ‘European Compromise’

● Translation

● DOF Usage

● Transition

● Submission & IFPS Addressing

● Training

Page 21: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

21

Example Use of DOF/

FPL contains: F18 = STS/HOSP DOF/130104 PBN/B3

F13b = 2230

We need to indicate a delay until 0200 i.e. a delay over midnight:

(DLA-ABC123-EBBR0200-EDDF-DOF/130104) - change of DOF is implicit

or

(CHG-ABC123-EBBR2230-EDDF-DOF/130104-13/EBBR0200 18/STS/HOSP PBN/B3 DOF/130105) - change of DOF is explicit

Note 1: The DOF (or Off Block Date) as provided in Field 18 shall always refer to the

last Off Block Date & Time (EOBD/EOBT) i.e. prior to the processing of the

current message.

Note 2: A modification to F18, via Field 22, must contain the complete F18

information, otherwise the missing data will be removed from the FPL.

Note 3: It is highly recommended that a change of EOBT over midnight is notified

via CHG message.

Page 22: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

22

Example Use of DOF/ cont.

FPL contains: F18 = STS/HOSP DOF/100304 PBN/B3

F13b = 2230

Flight is delayed until 0200 i.e. a delay over midnight.

(DLA-ABC123-EBBR0200-EDDF-DOF/100304)

OR

(CHG-ABC123-EBBR2230-EDDF-DOF/100304-13/EBBR0200 18/STS/HOSP DOF/100305 PBN/B3)

A further delay until 0400 is required:

(DLA-ABC123-EBBR0400-EDDF-DOF/100305)

As previously

Page 23: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

23

DOF and Delays over Midnight

● ICAO has indicated that a delay over midnight should

be notified via a CHG message

● A DLA message that delays a flight over midnight is

accepted by IFPS and results in an update of both

EOBT and DOF

Page 24: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

24

Content

● Detailed Syntax & Semantic Checks

● ‘European Compromise’

● Translation

● DOF Usage

● Transition

● Submission & IFPS Addressing

● Training

Page 25: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

25 © EUROCONTROL2009 - Central Flow Management Unit

Deployment / Transition – Principal

„Published‟

Result

Ideal /

‟Proposed‟

„Proposed‟

Result

„Published‟

Old Content New Content

00:00

15/11/2012

Page 26: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

26

Mixed Mode - Considerations

(FPL-AZA123-I/S

-A334/H-B2RSYW/S1

-LIRF1800

-N0460F380…….

-VIDP0750 VIDD

-PBN/B2 DOF/121114

Old format

New format

Aircraft Operator

Departure

ACC 1

ACC 2

ACC 3

Destination

(DEP-AZA123-LIRF1830-VIDP-DOF/121115)

?

?

?

(ARR-AZA123-LIRF-VIDP0110)

„New‟

„New‟

„Old‟

„Old‟

„Old‟

Page 27: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

27

Mixed Mode - Recommendations

● An ATC unit should accept both Old and New format

messages for the same FPD provided the end result is

either consistently Old or consistently New

● Transmitting in Old format prior to 15 Nov can never be

wrong

Page 28: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

28

EUR Region Deployment Policy

Objective: All FPLs in New format from 15/11

● AOs and CFSPs should submit FPLs in New format from 00:00UTC on 12 Nov 2012 onwards

AROs, IFPS, ATC systems should accept New from 12/11

● FPLs should NOT be submitted in Old format after 00:00UTC on 15 Nov 2012

IFPS will not accept FPLs with EOBT more than 24hrs in advance during the period 12-15 Nov 2012

FPLs with EOBT on 15 Nov should be filed in New format. If necessary the AO should wait until after midnight to submit the FPL

RPLs for Winter ’12-’13 should be submitted in New format

Page 29: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

29

IFPS Deployment

„Switch 1‟ = IFPS Ops acceptance of „Old‟ & „New‟, output of “Old only‟ or „Old + New‟ (ENV attribute)

„Switch 2‟ = IFPS Ops acceptance of „New‟ only, output of “Old only‟ or „New only‟ (ENV attribute)

„Switch 3‟ = IFPS Ops acceptance of „New‟ only, output of „New‟ only

15 Nov

2012

„Switch 2‟

Apr/May

2012

CFMU 16

„Switch 1‟ „Switch 3‟

CFMU 15

March

2011

CFMU

Implementation

IFPUV

with „Old‟

+ „New‟

June

2011

Implementation

Date

Dec.

2013

© EUROCONTROL2009 - Central Flow Management Unit

Page 30: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

30

EUR Deployment + IFPS

● Flight Plans…

May be submitted to IFPS in New format from May 2012

May be submitted in Old format until 15/11

Should be submitted in New format from 12/11

Shall be submitted in New format from 15/11

Page 31: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

31 © EUROCONTROL2009 - Central Flow Management Unit

Transition – IFPS ANSPs

00:00

15/11/2012

Reception of Old by

ANSPs

Reception of New by

ANSPs

IFPS Translation from

New to Old

Possible transition for an

IFPS State without a period

of mixed reception of Old

and New

ENV Parameter per ANU

(ICAO_2012_READY_DATE)

Default = 12:00UTC on 16/11/2012

- 72 hrs + 36 hrs

*Applicable only for

IFR/GAT FPLs !

Page 32: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

32 © EUROCONTROL2009 - Central Flow Management Unit

Transition – IFPS ANSPs

00:00 UTC

15/11/2012

Reception of Old by

IFPS

IFPS Translation from New to Old

Early transition for an IFPS

State with a period of mixed

reception of Old and New

Reception of both New & Old by

ANSP

- 72 hrs

*Applicable only for

IFR/GAT FPLs !

ENV Parameter per ANU (ICAO_2012_READY_DATE)

Set to = 00:00UTC on 15/11/2012

Page 33: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

33

All Flights concerning States outside IFPS Zone

& VFR and OAT Flights concerning States inside IFPS Zone

8/11 9/11 10/11 11/11 12/11 13/11 14/11 15/11 16/11 17/11 18/11

All AOs requested to

start to send New FPLs All AOs shall only send

New FPLs

Some AOs may

send New FPLs

ANSPs able to process New FPLs likely to

receive a mixture of Present and New

ANSPs unable to process

New FPLs should only

receive Present FPLs

ANSPs only

receive New

FPLs

Page 34: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

34

For IFR GAT Flights in States in IFPS Zone only

10/11 11/11 12/11 13/11 14/11 15/11 16/11 17/11 18/11

All AOs requested to

start to send New FPLs

All AOs shall only send

New FPLs

Some AOs may

send New FPLs

ANSPs able to process New

FPLs only receive New

IFPS accepts both New and

Present FPLs.

IFPS only accepts New FPLs.

IFPS accepts both New and

Present FPLs.

IFPS only accepts FPL

24H before EOBT.

IFPS accepts FPLs up to 120H

before EOBT.

1. IFPS distributes New FPLs to ANSPs able to process New.

2. IFPS translates New FPLs into Present FPLs for ANSPs unable to process New.

ANSPs unable to process New FPLs should only receive Present FPLs

ANSPs able to process New FPLs likely to

receive a mixture of Present and New

Page 35: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

35

Roll-Over Period [1]

● Change from Old to New at 00:00UTC on 15 Nov 2012 is a

software switch therefore:

Messages processed after 00:00UTC are expected in New format i.e.

the reference is the reception time, not the EOBT or FPL creation time

For a long haul flight the time period between FPL submission and

flight arrival at destination can be 18 hours

FPLs today are not normally sent more than 6 hours in advance to

ATC units

Page 36: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

36

Roll-Over Period [2]

● Example 1: A flight departs Singapore at 20:00 on 14th with destination London,

arrival on 15th at 08:00

FPL is submitted in Old format at 14th/14:00

At 14th/14:00 FPL is transmitted in Old format to Asian addressees

At 15th/02:00 FPL is transmitted to European addressees, in Old format !

● Example 2: A flight departs Singapore at 20:00 on 14th with destination London,

arrival on 15th at 08:00

FPL is submitted in Old format at 14th/14:00

Flight is delayed until after midnight, therefore all subsequent messages must be in New format.

If a change of equipment needs to be indicated the CHG will probably need to convert the FPL from Old to New

Page 37: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

37

Roll-Over Period - Analysis [3]

● Technical

An ATC unit may expect to receive some, legitimately submitted, Old

format messages on 15 Nov

An ATC unit may expect to receive both Old and New format

messages for the same flight

● Procedural Recommendation

If any part of a flight is planned to take place on the 15th the FPL and

all subsequent messages should be submitted in New format

Page 38: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

38

Content

● Detailed Syntax & Semantic Checks

● ‘European Compromise’

● Translation

● DOF Usage

● Transition

● Submission & IFPS Addressing

● Training

Page 39: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

39

Re-Addressing by IFPS

FF EUCHZMFP EUCBZMFP

250920 EGLLZPZX

AD ADDRESS1, ADDRESS2

(FPL-ABC123-I/S

...

...)

Aircraft Operator

IFPS

AD Line Addressing

Page 40: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

40

Re-Addressing & 2012 Transition

● ‘Unknown’ AD Line addressees

Receive Old format prior to 15 Nov

Receive New format after 15 Nov

● ‘Known’ AD Line addressees

Receive Old/New in accordance with ENV parameters for the unit

concerned

Page 41: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

41

AO - FPL Submission Scenarios

1. Entirely within IFPZ

a) May be submitted to IFPS

in New format from May 2012

b) May be submitted in Old

format until 15/11

c) Should be submitted in New

format from 12/11

d) Shall be submitted in New

format from 15/11

2. Departing to outside IFPZ

Same as for 1. and may inc.

AD line addresses in each of

the cases a) to d)

3. Departing from outside IFPZ

a) Should be submitted to

ARO at ADEP in accordance

with State requirements

Page 42: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

42

IFPS Default Addressing Scenarios

AD UKKKZQZQ UUEEZQZX UURRZQZX

(FPL-AZA123-I/S

-A334/H-B2RSYW/S1

-LIRF1800

-N0460F380…….

-VIDP0750 VIDD

-PBN/B2 DOF/121114

Normal - Old format

Copy - Old format

„AD‟ - Old format

Normal - New format

Copy - New format

„AD‟ - New format

Page 43: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

43

ANSP - FPL Addressing Scenarios

AD UKDDZQZX UUEEZQZX UURRZQZX

(FPL-AZA123-I/S

-A334/H-B2RSYW/S

-LIRF1800

-N0460F380…….

-VIDP0750 VIDD

-PBN/B2 DOF/121115

Normal - Old format

Copy - Old format

„AD‟ - Old format

Normal - New format

Copy - New format

„AD‟ - New format

Page 44: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

44

ANSP - FPL Addressing Scenarios

AD UKDDZQZX UUEEZQZX UURRZQZX

(FPL-AZA123-I/S

-A334/H-B2RSYW/S

-LIRF1800

-N0460F380…….

-VIDP0750 VIDD

-PBN/B2 DOF/121116

Normal - Old format

Copy - Old format

„AD‟ - Old format

Normal - New format

Copy - New format

„AD‟ - New format

Page 45: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

45

Content

● Detailed Syntax & Semantic Checks

● ‘European Compromise’

● Translation

● DOF Usage

● Transition

● Submission & IFPS Addressing

● Training

Page 46: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

46

Training

● Who & What

Controllers

● Should know – Background, Actual Changes (PBN) etc.

● Must know – impact for his/her operations, new procedures, LoA, MMI

ARO / Flight Plan Originators / Dispatchers

● Detailed changes, local & regional requirements, other regions requirements

● Aircraft capabilities / Crew qualifications

● How

CBT

● CFMU, Australia, (FAA?)

Classroom

● Detail impact / local or company implications

● When

CFMU CBT available at latest Spring 2012

● Where

CFMU website „Courses & Training‟

http://www.cfmu.eurocontrol.int/cfmu/public/subsite_homepage/homepage.html

Page 47: IFPS Update - icao.int Meetings Seminars and... · Training . 3 Field 10a ... (EOBD/EOBT) i.e. prior to the processing of the current message. Note 2: A modification to F18, via Field

47