Detailed working notes on the ICAO Asia/Pacific Seamless ATM Plan (now formally the "Asia/Pacific Seamless ANS Plan"). This folder expands the summary in topics/seamless_atm_plan.md into per-aspect files so each can be read on its own.

Files in this folder#

• overview.md — what the Seamless ATM/ANS Plan is, the regional realisation of GANP/ASBU for the APAC region, and the FIR-boundary problem it addresses.
• components.md — Plan structure: vision, performance framework, Priority Improvement Areas (PIAs), Preferred Aerodrome/Airspace and Route Specifications (PARS) and Preferred ANS Service Levels (PASL), implementation matrix.
• blocks.md — time horizons and Plan editions (V1.0 through V4.0), the three-year review cycle, and how Plan editions track GANP/ASBU Block windows.
• threads.md — priority improvement areas inside the Plan (Airspace/PBN, Surveillance, AIDC, ATFM, A-CDM, AIM/SWIM, MET, FF-ICE, CPDLC/Data Link, SAR, Contingency, Cybersecurity).
• modules.md — anatomy of a Plan element: objective, related ASBU module, KPIs, target dates, States of focus, reporting fields.
• enablers.md — APANPIRG sub-groups, the ICAO APAC Regional Office, States and ANSPs, harmonisation tools (Reporting Tool, PFF, RASGs).
• performance_objectives.md — Seamless ATM/ANS performance metrics, link to eANP Volume III, KPIs and reporting cadence.
• timeline.md — first edition through V4.0 (Nov 2024), major revision triggers, alignment with GANP review cycle.
• references.md — APAC Seamless ANS Plan publications, APANPIRG meeting reports, working papers, and related APAC frameworks.

Reading order#

Start with overview.md, then components.md, then blocks.md and threads.md, then drill into modules.md, enablers.md, and performance_objectives.md. Use timeline.md for edition context and references.md for citations.

Source basis#

Content is grounded in:

• Asia/Pacific Seamless ANS Plan, Version 4.0 (ICAO APAC, November 2024).
• Asia/Pacific Seamless ANS Plan, Version 3.0 (predecessor edition).
• APANPIRG meeting reports and working papers (notably APANPIRG/34 and APANPIRG/35, with WP/16 in both cycles).
• ICAO Doc 9750 (Global Air Navigation Plan, GANP) and the ASBU framework as the global parent.
• ICAO Doc 9673 (APAC eANP), Volume III (regional performance framework).
• ICAO Doc 9854 (Global ATM Operational Concept) and Doc 9883 (Manual on Global Performance of the Air Navigation System).
• ICAO APAC Regional Office portal: https://www.icao.int/APAC/Pages/Seamless-ATM-Plan.aspx
• ICAO APAC Seamless ANS Plan landing page: https://www.icao.int/APAC/asia-pacific-seamless-ans-plan

Companion folders in this workspace#

• topics_detailed/asbu/ — global ASBU framework that the Seamless ANS Plan localises for APAC.
• topics_detailed/air_navigation_plan/ — global / regional ANP structure (Doc 9750 / Doc 9673).
• topics_detailed/atfm/, topics_detailed/a_cdm/, topics_detailed/aim/, topics_detailed/aidc/, topics_detailed/ff_ice/ — individual priority threads called out by the Plan.

What the Plan is#

The Asia/Pacific Seamless ATM Plan — formally re-titled the Asia/Pacific Seamless ANS Plan in its current iterations — is the ICAO APAC region's master regional planning document for harmonised, boundary-transparent provision of Air Navigation Services (ANS) across adjacent Flight Information Regions (FIRs). It is the regional realisation of ICAO Doc 9750 (GANP) and the ASBU framework for the ICAO Asia and Pacific Region.

The word "seamless" is doing the work in the title. Operationally, an aircraft transiting multiple APAC FIRs from origin to destination should encounter:

• consistent navigation specifications (PBN minima, route designations);
• consistent surveillance performance (cooperative surveillance, cross- border data sharing);
• consistent ATS coordination procedures (AIDC, agreed letters of agreement);
• consistent flow management treatment (collaborative ATFM measures);
• consistent information services (AIM, MET, NOTAM, SWIM exchanges);
• consistent contingency arrangements;

with no avoidable operational discontinuity at FIR boundaries. The Plan exists because the APAC region has more international FIR boundaries crossed by long-haul flows than any other ICAO region, and those boundaries historically introduced procedural and equipment discontinuities that erased the per-State benefits of ASBU investment.

Where the Plan sits#

The Plan sits between the global GANP and national plans:

ICAO Doc 9750 (GANP) + ASBU framework        <- global
        |
APAC Seamless ANS Plan (this document)        <- regional
        |
APAC eANP Volume III performance framework    <- regional
        |
National Air Navigation Plans (per State)     <- national

Performance expectations and prioritised ASBU and non-ASBU elements from the Seamless ANS Plan are migrated into the APAC eANP Volume III (regional performance framework). In effect, the Seamless ANS Plan drives APAC regional performance objectives and Volume III records the formal regional commitments derived from it.

Scope#

The Plan covers the full ANS spectrum:

• ATS — air traffic services across continental, oceanic, and remote airspace.
• ATFM — collaborative flow management (linked to the APAC Framework for Collaborative ATFM).
• AIM — aeronautical information management transition (linked to the APAC Plan for Collaborative AIM).
• MET — operational meteorological information interface to ATM, including IWXXM exchange.
• SAR coordination — region-wide search and rescue arrangements.
• CNS infrastructure — the underlying communications, navigation, and surveillance enablers.

Within that scope, the Plan articulates regional performance expectations, target dates, and reporting obligations for States and ANSPs in the APAC region.

Why a separate regional plan#

ASBU is global and deliberately a "menu" rather than a mandate. Three APAC-specific characteristics make a regional plan necessary:

1. FIR density on long-haul flows. Many APAC city pairs cross five or more FIRs. Discontinuities multiply. Regional harmonisation has compounding benefit.
2. Heterogeneous CNS environment. Continental high-density TMAs coexist with very long oceanic and remote sectors (Pacific Ocean, Bay of Bengal, Indian Ocean entries). Different module mixes apply to different operating environments inside the same region.
3. Wide capability spread between States. APAC States range from highly capable hub States to small island and developing States; the Plan codifies the regional baseline so capacity-building support and No Country Left Behind activity can be targeted.

What planners use the Plan for#

For an APAC State, ANSP, or regional sub-group, the Seamless ANS Plan answers four questions:

1. What ASBU and non-ASBU elements are priority for APAC, by operating environment?
2. By when must each be implemented (target dates per Plan element)?
3. Against what is implementation measured (KPIs, eANP Vol III performance objectives)?
4. Through which governance line is progress reported (APANPIRG and sub-groups, the Seamless ANS Reporting Tool)?

The Plan does not replace national planning. It constrains and prioritises it for cross-FIR coherence.

The Plan is not a single artefact. It is a structured set of interlocking components that together describe what APAC States should deliver, when, why, and how progress is measured. The components are:

1. Vision and scope#

The opening of the Plan states the seamless-operations vision and the ANS scope (ATS, ATFM, AIM, MET interface, SAR coordination, CNS infrastructure). It establishes that the Plan is the regional translation of the GANP / ASBU framework for the APAC Region and is endorsed by APANPIRG.

2. Performance framework#

The Plan carries a regional performance framework that:

• declares the Key Performance Areas (KPAs) of focus for APAC (drawn from Doc 9854 / Doc 9883: safety, capacity, efficiency, environment, predictability, interoperability, cost-effectiveness);
• ties each priority element to one or more Performance Objectives;
• exposes the Key Performance Indicators (KPIs) used to measure progress;
• maps these performance objectives into the APAC eANP Volume III.

The performance framework is the "why" axis. Without it, the Plan would be an undifferentiated list of capabilities.

3. Priority Improvement Areas (PIAs)#

The Plan inherits the GANP PIA grouping (Airport Operations, Globally Interoperable Systems and Data, Optimum Capacity and Flexible Flights, Efficient Flight Path) but restates them in APAC-specific terms. These appear as priority threads in the Plan's matrix and are detailed in threads.md.

4. Preferred ANS Service Levels (PASL)#

The PASL construct is APAC-specific: a tabular declaration of the ANS service level that should be available in defined operating environments (continental high-density, continental medium-density, oceanic, remote, archipelagic, etc.). PASL fields typically capture:

• Communications (voice, data link, AIDC).
• Navigation (PBN specifications applicable).
• Surveillance (cooperative surveillance type and performance).
• Separation minima applicable.
• ATFM and arrival management coverage.
• AIM and MET service levels.
• Contingency and SAR coverage.

PASL says: "for this operating environment, this is the minimum service level the region commits to provide to a transiting aircraft."

5. Preferred Aerodrome/Airspace and Route Specifications (PARS)#

PARS is the airspace-side counterpart to PASL: a declaration of the airspace and procedure specifications that should apply at defined classes of aerodrome and along defined route structures. Typical PARS content:

• PBN specifications for SIDs, STARs, and en-route.
• RNP APCH at instrument runways; RNP AR where justified.
• Free Route Airspace (FRA) extent.
• Reduced separation applications (e.g. RLatSM, RLongSM in oceanic).
• Airspace classification harmonisation.

PARS and PASL together define what "seamless" means in concrete, auditable terms for any APAC route.

6. Priority elements and target dates#

Each priority element in the Plan carries:

• a regional priority statement;
• a target implementation date (often expressed in two tiers: regional expectation, and an extended date for States needing implementation support);
• the related ASBU module reference;
• the responsible APANPIRG sub-group (ATM/SG, CNS/SG, AIM/SG, MET/SG, AOP/SG);
• States of focus (e.g. all APAC States, States with oceanic FIRs, States with high-density TMAs).

This is the cell content of the Plan's implementation matrix.

7. Implementation matrix#

The canonical view of the Plan is a matrix:

                    Priority Thread
                    PBN  AIDC  ATFM  ACDM  AIM/SWIM  ...
  Continental
    high-density    ...
  Continental
    medium-density  ...
  Oceanic / remote  ...
  Archipelagic      ...

Each cell carries the priority element(s), target date, and reporting flag. The Seamless ANS Reporting Tool collects status into this matrix on a per-State basis.

8. Reporting framework#

The Plan is operationalised through:

• the Seamless ANS Reporting Tool, maintained by the ICAO APAC Office;
• the Performance Framework Form (PFF) entries used to feed the eANP Volume III performance framework;
• the annual reporting deadline (per WP/16, APANPIRG/35, 2024: 28 February) following an initial mid-year baseline.

Outputs feed APANPIRG dashboards, gap analyses, and No Country Left Behind targeted assistance prioritisation.

9. Linkages to other APAC frameworks#

The Plan is explicit about its relationships to other regional documents — it does not duplicate them. Linked frameworks include:

• APAC Plan for Collaborative AIM (AIM detail);
• APAC Framework for Collaborative ATFM (ATFM detail, including Distributed Multi-Nodal ATFM / DMNATFM);
• APAC PBN Plan (PBN implementation detail);
• APAC Regional ATM Contingency Plan (contingency procedures);
• APAC eANP Volumes I, II, III (formal regional ANP).

The Seamless ANS Plan calls these by reference rather than restating their content.

Where the global GANP organises modernisation into ASBU Blocks (time-phased availability windows: Block 0 from 2013, Block 1 from 2019, Block 2 from 2025, Block 3 from 2031), the APAC Seamless ATM/ANS Plan organises its time horizons through successive Plan editions. Each edition re-baselines target dates and priority elements against the prevailing GANP / ASBU baseline and the regional traffic and capability picture.

What an edition is#

An edition of the Seamless ANS Plan is the regional commitment at a point in time, endorsed by APANPIRG. It bundles:

• the current performance framework;
• the current PARS / PASL declarations;
• target implementation dates per priority element;
• States of focus and reporting cadence;
• references to the prevailing GANP / ASBU baseline and to companion APAC frameworks (ATFM, AIM, PBN, contingency).

Editions are reviewed on an approximately three-year cycle to stay aligned with the GANP review cadence; APANPIRG may direct earlier revisions if traffic or capability trends require it.

The four editions to date#

The version-numbering convention is APAC's own. It is not synchronised to GANP edition numbering, but each Plan edition references the prevailing GANP edition.

V1.0 — Establishing "seamless" (initial release)#

Theme. Define the seamless concept for APAC and put structure around the boundary problem.

Representative content.

• Initial PARS/PASL framework.
• Priority elements covering PBN, ATS surveillance (radar / Mode S era), AIDC, initial ATFM coordination, AIS and basic AIM.
• Initial APANPIRG governance: ATM/SG endorsement chain.

V2.0 — 2016 (APANPIRG/27 timeframe)#

Theme. Re-baseline against GANP 5th edition (2016). Strengthen the performance framework and extend priority elements to match Block 0 maturity and Block 1 onset.

Representative content.

• Expanded surveillance coverage including ADS-B and space-based ADS-B considerations for oceanic.
• AIDC priority extended across more FIR pairs.
• Initial collaborative ATFM elements (cross-FIR, multi-nodal).
• AIM transition under Doc 10066 / Annex 15.
• PBN coverage tightened (RNP routes, RNP APCH at instrument runways).

V3.0 — broadened from ATM to ANS#

Theme. Recognise that the seamless concept extends beyond ATM into the full ANS spectrum. Title becomes "Asia/Pacific Seamless ANS Plan".

Representative content.

• Explicit MET interface and IWXXM exchange priorities.
• AIM and SWIM priority elements aligned with the APAC Plan for Collaborative AIM.
• Strengthened ATFM linkage to the APAC Framework for Collaborative ATFM, including Distributed Multi-Nodal ATFM (DMNATFM).
• PFF entries explicitly linked to eANP Volume III.
• A-CDM at major aerodromes, with DPI/FUM exchange to ATFM.

V4.0 — November 2024 (current edition)#

Theme. Update against GANP 7th edition (2022) baseline. Reaffirm performance framework and reporting cadence. Push priority dates for Block 1 / Block 2 era capabilities.

Representative content.

• FF-ICE/1 readiness (Flight and Flow Information for the Collaborative Environment, planning information).
• CPDLC and data link priorities (FANS-1/A, ATN B1/B2 where applicable).
• Reduced separation applications: oceanic (RLatSM, RLongSM), TBS/WTC refinements where feasible.
• SAR coordination, AFTN/AMHS routing, alignment with APAC Regional ATM Contingency Plan.
• Cybersecurity and resilience of CNS/ATM systems.
• Annual reporting deadline confirmed at 28 February following an initial mid-year baseline (per WP/16, APANPIRG/35, 2024).

V4.0 is the prevailing edition at the time of writing. It is published by ICAO APAC and indexed from the APAC Seamless ANS Plan portal.

Edition cadence and the GANP cycle#

The three-year review cycle is intentional: the GANP itself is reviewed every three years (aligned with the ICAO Assembly cycle), and ASBU module catalogue updates flow continuously through the GANP Portal. The Seamless ANS Plan's three-year cadence ensures regional target dates and PARS/PASL declarations stay coherent with the global baseline.

Indicative national application of editions:

1. Track the prevailing edition as the regional commitment for target dates.
2. Where an earlier edition's target date has slipped, the new edition re-baselines and the new date governs.
3. Where a State has implemented ahead of the regional target, that capability counts toward APAC seamless conformance immediately — editions do not bar early implementation.
4. National plans are expressed in terms of the current edition's priority elements and target dates so that PFF reporting maps directly into eANP Volume III.

A priority thread in the Seamless ANS Plan is a feature area in which APAC States and ANSPs are expected to deliver harmonised, boundary-transparent capability. Threads are the columns of the Plan's implementation matrix; operating environments (continental high-density, continental medium-density, oceanic, remote, archipelagic) are the rows.

The threads below correspond to the Plan's priority elements, grouped into operational, information, and CNS-infrastructure families and expressed in APAC terms. They mirror the GANP / ASBU thread catalogue but are sequenced and dated for the APAC region.

Operational threads#

Airspace and PBN#

Performance-Based Navigation across the region: RNP routes, RNP APCH at instrument runways, PBN SIDs/STARs, advanced RNP where justified. Free Route Airspace (FRA) at upper levels where traffic and ATS support permit. Linked to the APAC PBN Plan.

ATS surveillance#

Cooperative surveillance with cross-border data sharing: ADS-B (including space-based ADS-B for oceanic and remote), multilateration, Mode S enhanced surveillance. The Plan emphasises consistent surveillance performance across adjacent FIRs to support reduced separation applications.

AIDC — ATS Interfacility Data Communication#

Automated coordination and transfer of control between adjacent ATS units, replacing voice-based estimate handover. AIDC is a Seamless ANS Plan headline because FIR-pair AIDC coverage is the most direct operational measure of "seamless" boundary handling.

ATFM — collaborative flow management#

Regional collaborative ATFM aligned to the APAC Framework for Collaborative ATFM, including multi-nodal Distributed Multi-Nodal ATFM (DMNATFM). The thread captures regulation harmonisation, slot allocation visibility, and DPI/FUM exchange with airports.

A-CDM — Airport Collaborative Decision Making#

A-CDM at major aerodromes with milestone-based turnaround, TOBT/TSAT, and DPI/FUM exchange to the regional ATFM network. The Plan prioritises A-CDM at hubs whose departure flows interact with multiple neighbouring FIRs.

Reduced separation applications#

• Oceanic — Reduced Lateral Separation Minima (RLatSM) and Reduced Longitudinal Separation Minima (RLongSM) on routes that support them; advanced PBN-based oceanic separation.
• Continental — Time-Based Separation (TBS) and revised Wake Turbulence Categorisation (RECAT) at airports where feasible.

Search and Rescue (SAR) coordination#

Regional SAR coordination, AFTN/AMHS routing arrangements, and contingency interfaces. Particularly important for the oceanic and remote operating environments.

Contingency#

Alignment with the Asia/Pacific Regional ATM Contingency Plan. Cross-FIR contingency procedures, including alternate routings, service degradations, and inter-State communication arrangements.

Information threads#

AIM and SWIM#

Digital AIM transition under Doc 10066 (PANS-AIM) and Annex 15; AIXM 5 for aeronautical data; FIXM for flight information; IWXXM for meteorological exchange; SWIM services and governance. Linked to the APAC Plan for Collaborative AIM.

FF-ICE — Flight and Flow Information for the Collaborative Environment#

Priority on FF-ICE/1 (planning information) readiness across the region, supporting flight planning and trajectory exchange. FF-ICE/2 (execution information) is signalled as a longer-horizon thread.

MET interface#

Operational meteorological information feeding ATM decisions: SIGMET / volcanic ash / tropical cyclone advisory exchange, IWXXM adoption, integration with ATFM and TBO planning.

CNS infrastructure threads#

CPDLC and data link#

Continental and oceanic data link services — FANS-1/A in oceanic and remote, ATN B1/B2 in continental where applicable, satcom data link where infrastructure justifies it. Underpins TBO and FF-ICE.

Air-ground communications#

Voice and data link infrastructure beyond CPDLC: VHF coverage harmonisation, HF for oceanic, satcom voice for remote, AeroMACS at airports where deployed.

Cybersecurity and resilience#

Cybersecurity of CNS/ATM systems, with explicit treatment in V4.0: resilience of SWIM-connected systems, identity and access management, contingency for cyber events.

Cross-thread dependencies (APAC application)#

The Plan exposes the same dependency principles as ASBU but tunes them for APAC operating environments:

• AIDC depends on ground-ground network (typically AFTN/AMHS or managed IP network) and is a prerequisite for cross-FIR ATFM and reduced separation applications.
• Reduced oceanic separation (RLatSM/RLongSM) depends on PBN fleet equipage, ADS-C / CPDLC carriage, and consistent FIR-pair surveillance.
• A-CDM with DPI/FUM exchange depends on regional ATFM nodes and AIDC for inter-FIR awareness.
• AIM/SWIM and IWXXM depend on Doc 10066 conformance and quality- managed digital data sets at the producing State.
• FF-ICE/1 depends on SWIM service infrastructure and FIXM-capable flight planning systems.

The Seamless ANS Reporting Tool flags these dependencies so that a State cannot claim a downstream priority complete unless its prerequisites are also reported in place.

States of focus#

Threads are not uniformly applicable. The Plan tags each thread with its States or operating-environment focus:

• All States — AIDC, AIM/SWIM, MET, contingency, cybersecurity.
• States with oceanic FIRs — RLatSM/RLongSM, space-based ADS-B, oceanic CPDLC/ADS-C, SAR coordination.
• States with high-density TMAs — A-CDM, TBS/RECAT, advanced PBN, ATFM CDM.
• States with remote/archipelagic operating environments — PBN approach coverage, ADS-B baseline, contingency communications.

This per-thread State scoping is what makes the Plan implementable in a region with very heterogeneous capability.

What a Plan element is#

A Plan element is the smallest unit of Seamless ANS Plan commitment. It corresponds to one priority capability in one operating environment and carries the regional commitment to deliver it by a target date, with reporting against defined indicators.

Where ASBU calls these units "modules" (<THREAD>-B<n>/<seq>, e.g. AIDC-B0/1), the Seamless ANS Plan typically presents them as rows in its priority-element table, each referencing the related ASBU module.

A Plan element is deliverable: a State or ANSP can plan, fund, procure, deploy, certify, train for, operate, and report against it as a coherent capability.

Anatomy of a Plan element#

The Plan exposes each element with the following structured fields, which are the data the Seamless ANS Reporting Tool collects.

1. Title and identifier#

A short title plus an identifier that ties the element back to the relevant priority thread, e.g. "AIDC implementation between adjacent FIR pairs".

2. Operational improvement description#

A plain-language statement of what changes operationally inside APAC when the element is in place — typically framed as the FIR-boundary benefit (reduced voice coordination workload, fewer estimate errors, faster transfer of control).

3. Related ASBU module#

Direct cross-reference to the global ASBU module the element realises, by mnemonic and Block. Examples:

• AIDC priority element → relates to ASBU FICE / cross-FIR coordination modules.
• A-CDM at hub aerodromes → relates to ACDM-B0 / ACDM-B1.
• Digital AIM and IWXXM → relate to DAIM-B0/B1 and AMET-B1.
• FF-ICE/1 readiness → relates to FICE-B1.
• Initial SWIM services → relate to SWIM-B1.
• Oceanic RLatSM/RLongSM → relate to OPFL/oceanic separation modules.

4. Performance objective and KPAs#

The Plan element is tagged with one or more Performance Objectives drawn from the Plan's regional performance framework, mapped to the KPAs the element improves (typically capacity, efficiency, environment, predictability, interoperability).

5. KPIs#

Quantitative indicators against which the element is measured. For APAC, common KPI families include:

• AIDC FIR-pair coverage percentage.
• A-CDM-equipped major aerodromes percentage.
• ADS-B coverage across FIR area.
• IWXXM adoption percentage.
• FF-ICE/1 readiness flag per State.
• ATFM regulation rate / minutes of ATFM delay per flight.

6. Target dates#

Each element typically carries:

• a regional target date (the seamless commitment);
• where applicable, an extended date for States needing implementation support (No Country Left Behind context).

Target dates are set against the prevailing Plan edition.

7. States of focus#

The States or operating-environment classes to which the element applies (all States; States with oceanic FIRs; States with high-density TMAs; States with remote/archipelagic environments). See threads.md.

8. Responsible APANPIRG sub-group#

The sub-group with technical lead for the element: ATM/SG, CNS/SG, AIM/SG, MET/SG, AOP/SG (and ad-hoc working arrangements as relevant). This determines the technical body that scrutinises reported status.

9. Procedure and standards basis#

Cross-references to ICAO PANS, Annexes, and APAC regional supplementary procedures (Doc 7030 APAC SUPPS): typically Doc 4444 (PANS-ATM), Doc 8168 (PANS-OPS), Doc 10066 (PANS-AIM), Doc 10157 (PANS-MET), Annex 10 (CNS), Annex 11 (ATS), Annex 14 (Aerodromes), Annex 15 (AIS).

10. Enablers#

Supporting CNS, procedure, regulatory, training, and institutional prerequisites. See enablers.md.

11. Reporting fields#

The Reporting Tool fields required from each State for the element: status (planned, in progress, implemented), evidence reference, target-date conformance flag, and free-text notes.

Worked examples#

Example 1 — AIDC between adjacent FIR pairs#

• Operational improvement. Automated coordination and transfer of control between adjacent ATS units, replacing voice-based estimate handover.
• Related ASBU. FICE-related coordination modules at Block 0 / 1.
• KPAs. Predictability, capacity, interoperability.
• KPIs. Number of AIDC-active FIR pairs vs. total FIR pairs; message delivery success rate.
• Target dates. Per current Plan edition; staged by region of FIR pair.
• States of focus. All APAC States with shared FIR boundaries.
• Sub-group. ATM/SG.
• Procedure / standards. Doc 4444 coordination provisions; APAC SUPPS; FIR-pair letters of agreement.
• Enablers. AFTN/AMHS or managed IP network; ATM systems with AIDC capability; bilateral letters of agreement.

Example 2 — A-CDM at major aerodromes with DPI/FUM exchange#

• Operational improvement. Milestone-based turnaround, TOBT/TSAT, and DPI/FUM exchange to the regional ATFM network.
• Related ASBU. ACDM-B0, ACDM-B1.
• KPAs. Predictability, capacity, environment, cost-effectiveness.
• KPIs. A-CDM-equipped airports percentage; DPI/FUM message exchange rate; off-block punctuality variance.
• Target dates. Per current Plan edition; tiered by airport category.
• States of focus. States with major aerodromes participating in long-haul flows.
• Sub-group. AOP/SG with ATM/SG.

Example 3 — IWXXM-based MET information exchange#

• Operational improvement. XML/GML model meteorological information exchanged through SWIM-style channels, replacing legacy text bulletins for many products.
• Related ASBU. AMET-B1.
• KPAs. Interoperability, efficiency, safety.
• KPIs. IWXXM-published product percentage by State; MET WATCH Office IWXXM conformance.
• Sub-group. MET/SG.

How Plan elements become a national plan#

A national ANS plan is produced by:

1. Selecting the Plan elements applicable to the State's operating environments (continental / oceanic / remote / archipelagic).
2. Sequencing them per the dependency chain visible in the Plan and ASBU portal.
3. Mapping each to the responsible national organisation, funding source, regulatory action, and milestone.
4. Reporting status into the Seamless ANS Reporting Tool against the regional target dates.
5. Feeding the corresponding PFF entries into the eANP Volume III performance framework.

What an enabler is here#

In Seamless ANS Plan terms, an enabler is the supporting machinery without which a Plan element cannot be implemented and reported across the region. The Plan distinguishes two senses of "enabler":

1. Technical/regulatory enablers — the same families as ASBU (CNS infrastructure, procedures, SARPs, avionics, regulation, training, institutional agreements). These are documented per priority element and largely covered in the ASBU detailed reference.
2. Regional governance and harmonisation enablers — the APAC-specific bodies, tools, and arrangements that operate the Plan itself. These are the focus of this file.

1. APANPIRG and its sub-groups#

The Plan is owned, maintained, and endorsed by APANPIRG — the Asia/Pacific Air Navigation Planning and Implementation Regional Group. APANPIRG endorses each new edition on the recommendation of its sub-groups and any ad-hoc Seamless ANS Plan working arrangements.

Sub-groups carrying technical responsibility for Plan threads:

• ATM/SG — Air Traffic Management Sub-Group. Lead for ATS, airspace, ATFM, AIDC, separation applications, contingency.
• CNS/SG — Communications, Navigation and Surveillance Sub-Group. Lead for surveillance (ADS-B, multilateration, space-based ADS-B), data link, voice, GNSS, and CNS infrastructure.
• AIM/SG — Aeronautical Information Management Sub-Group. Lead for the AIM transition, AIXM, digital data sets, NOTAM evolution.
• MET/SG — Meteorology Sub-Group. Lead for IWXXM adoption, SIGMET / volcanic ash / tropical cyclone advisory exchange, MET WATCH Office arrangements.
• AOP/SG — Aerodrome Operations Sub-Group. Lead for A-CDM, A-SMGCS, runway safety, aerodrome design topics relevant to ATM.

Each sub-group reports to APANPIRG and proposes Plan-element changes within its remit.

2. ICAO Asia and Pacific Regional Office (Bangkok)#

The ICAO APAC Regional Office in Bangkok provides:

• Plan secretariat — drafts, edits, and publishes editions; convenes sub-group and ad-hoc meetings; tracks endorsement.
• Custodian of the Seamless ANS Reporting Tool.
• Editorial responsibility for the APAC eANP (Doc 9673), into whose Volume III the Plan's PFF entries flow.
• No Country Left Behind (NCLB) coordination for APAC: identifying States needing assistance based on Plan reporting.
• Liaison to the ICAO Bureau of Air Navigation and adjacent regions (MID, NAT, AFI) for cross-region coherence on shared FIR boundaries.

3. States and ANSPs#

Implementation depends on State-side actors:

• CAAs as regulatory authorities: SARP transposition, operational authorisations, certification, oversight.
• ANSPs as service providers: procurement, deployment, training, procedures, FIR-pair coordination.
• Aerodrome operators for A-CDM, A-SMGCS, surface improvements.
• MET service providers for IWXXM and MET WATCH Office outputs.
• AIM service providers for digital AIM transition.

States report status into the Reporting Tool on the cadence described in performance_objectives.md.

4. Harmonisation tools#

Seamless ANS Reporting Tool#

The dedicated implementation-tracking tool maintained by ICAO APAC. Collects per-State, per-element status; exposes regional dashboards and gap analyses; feeds APANPIRG decision-making.

Performance Framework Form (PFF)#

Structured form entries that codify performance objectives and indicators for migration into eANP Volume III. The PFF is the bridge between the Plan (commitment) and the eANP (formal regional ANP).

eANP Volume III#

The performance framework volume of the APAC eANP. Records the formal regional commitments derived from the Seamless ANS Plan with target dates and KPIs. eANP Volumes I and II carry the constants (general planning, FASID).

Regional Aviation Safety Group — Asia/Pacific (RASG-APAC)#

Companion safety body whose performance work intersects with Plan priorities; provides safety-side context for KPAs that have safety components (e.g. SAR, contingency, separation applications).

Companion APAC frameworks#

• APAC Plan for Collaborative AIM — operational detail for the AIM/SWIM thread.
• APAC Framework for Collaborative ATFM — operational detail for the ATFM thread, including DMNATFM.
• APAC PBN Plan — operational detail for the PBN thread.
• APAC Regional ATM Contingency Plan — operational detail for the contingency thread.

5. Technical and regulatory enablers (per element)#

For each Plan element, the underlying technical/regulatory enablers follow the ASBU enabler families. In APAC the most often-cited prerequisites are:

• Networks — AFTN/AMHS or managed IP for AIDC and inter-FIR exchanges; SWIM-TI for SWIM services.
• Procedures — Doc 4444 (PANS-ATM), Doc 8168 (PANS-OPS), Doc 10066 (PANS-AIM), Doc 10157 (PANS-MET), Doc 7030 APAC SUPPS, AIP publication.
• Standards — Annex 10 (CNS), Annex 11 (ATS), Annex 14 (Aerodromes), Annex 15 (AIS), Annex 19 (SMS), as relevant per element.
• Avionics / fleet equipage — PBN equipage; ADS-B Out (1090ES); CPDLC (FANS-1/A or ATN B1/B2); ADS-C (oceanic).
• Regulation — operational authorisations under Annex 6; PBN approval frameworks; data link approvals; cybersecurity regimes.
• Human resources — controller and AIM/MET officer training; endorsements as required.
• Institutional — bilateral letters of agreement between adjacent ANSPs; FIR-pair AIDC arrangements; cross-border ATFM and XMAN MOUs.

6. How enablers are managed in practice#

Each Plan element's reporting record carries an "enablers in place" view. A State that reports an element implemented while its declared enablers are not in place is queried by the responsible sub-group at the next reporting cycle. This is the practical mechanism that prevents headline equipage from being claimed as full implementation without the procedural, regulatory, and institutional foundation.

The performance lens of the Plan#

The Seamless ANS Plan is a performance-based document. Every priority element is justified by the performance benefit it delivers across the APAC region, and progress is measured against KPIs that feed into the APAC eANP Volume III performance framework. The underlying terminology is the same as the global GANP: KPAs from Doc 9854 / Doc 9883.

The chain is:

KPA  --(measured by)-->  KPI  <--(targeted by)--  Performance Objective  --(achieved by)-->  Plan element / ASBU module

Key Performance Areas (KPAs) of focus for APAC#

The eleven canonical KPAs (Doc 9854 / Doc 9883) all apply, but the Seamless ANS Plan emphasises a subset most directly affected by FIR-boundary harmonisation:

1. Safety — accident and incident exposure, SAR responsiveness.
2. Capacity — sector / runway / network throughput, especially on long-haul flows crossing many FIRs.
3. Flight efficiency — track-mile and vertical efficiency on cross-FIR trajectories; oceanic flexibility.
4. Predictability — variance between planned and actual times, with specific attention to FIR-boundary handover punctuality.
5. Environmental impact — fuel and CO2 saved by free-route, CDO/CCO, and reduced separation gains.
6. Cost-effectiveness — unit cost of ANS service; harmonisation reducing duplicated investment.
7. Interoperability — the central KPA for a "seamless" plan; measured by AIDC coverage, IWXXM adoption, FF-ICE readiness, SWIM service availability.

(Security, flexibility, access and equity, participation are also present but treated as cross-cutting.)

Performance Objectives (illustrative)#

A Performance Objective (PO) is a measurable improvement the Plan commits to pursue. The Plan's PO catalogue is captured in PFF entries and migrated into eANP Volume III. Illustrative examples consistent with V3.0 / V4.0 structure:

• PO — Achieve full AIDC coverage across APAC FIR pairs. Measured by AIDC-active FIR pairs / total FIR pairs. Delivered by the AIDC priority element across continental and oceanic operating environments.
• PO — Reduce en-route flight inefficiency on APAC long-haul flows. Measured by KEA (actual vs. great-circle) and free-route airspace utilisation. Delivered by FRA expansion, oceanic RLatSM/RLongSM, and cross-FIR ATFM elements.
• PO — Improve arrival predictability into APAC hubs. Measured by variance between planned and actual landing time. Delivered by A-CDM, AMAN/XMAN, and ATFM CDM elements.
• PO — Reduce fuel burn and CO2 per APAC flight. Measured by fuel / CO2 per movement, vertical inefficiency. Delivered by CDO/CCO, optimum flight levels, oceanic reduced separation, and PBN.
• PO — Achieve IWXXM-based MET information exchange across APAC. Measured by IWXXM-published product percentage by State. Delivered by the MET thread.
• PO — Achieve FF-ICE/1 readiness for APAC States. Measured by FF-ICE/1 readiness flag per State. Delivered by the FF-ICE thread with SWIM and FIXM enablers.
• PO — Maintain robust regional contingency and SAR coverage. Measured by contingency-plan currency and SAR exercise outcomes.

Key Performance Indicators (KPIs)#

KPI families in the APAC reporting context:

Interoperability KPIs (the "seamless" centre of gravity)#

• AIDC-active FIR-pair percentage.
• IWXXM product percentage by State.
• FF-ICE/1 readiness flag per State.
• SWIM service availability and semantic conformance.
• ADS-B coverage (continental, oceanic with space-based ADS-B).

Capacity KPIs#

• Declared runway capacity at major aerodromes.
• Sustained sector throughput on cross-FIR flows.
• ATFM regulation rate; minutes of ATFM delay per flight.

Flight efficiency KPIs#

• KEP / KEA on APAC city-pair flows.
• Direct-routing percentage; FRA utilisation.
• Vertical efficiency vs. optimum cruise level.

Predictability KPIs#

• Variance / standard deviation between planned and actual off-block, airborne, landing times on APAC flights.
• ATFM slot adherence.

Environmental KPIs#

• Fuel burn / CO2 per APAC flight.
• Excess fuel per arrival (CDO conformance) at major aerodromes.

Safety KPIs#

• Loss-of-separation events per flight hour by FIR pair.
• SAR response time and exercise outcomes.

Cost-effectiveness KPIs#

• Unit cost of ANS per service unit (Doc 9082 charging principles).

Reporting cadence#

Per WP/16 at APANPIRG/35 (2024), the V4.0 reporting cadence is:

• An initial mid-year baseline when an edition is endorsed.
• An annual submission deadline of 28 February for status updates thereafter.
• Continuous updates encouraged when significant State-level milestones are achieved.

Reporting flows through the Seamless ANS Reporting Tool, with outputs feeding APANPIRG dashboards, gap analyses, and No Country Left Behind targeted assistance prioritisation.

How performance is consumed#

• Regionally — the APAC Office and APANPIRG sub-groups consume the Reporting Tool outputs; PFF entries feed eANP Volume III.
• Globally — APAC performance feeds the global GANP review cycle consolidated by ICAO HQ.
• Nationally — States use the same KPIs in their National Performance Plans (where they have one) so that national, regional, and global performance reporting use one language.

Why this matters for the Plan#

Tying every priority element to a Performance Objective and a KPI keeps the Plan honest. It prevents the document from drifting into a shopping list of capabilities and forces APANPIRG to ask, every cycle, whether deployed capability is producing the predicted regional benefit. That feedback loop is what turns "seamless" from a slogan into a measurable regional commitment.

Three timelines to keep distinct#

When discussing the Seamless ANS Plan in date terms, separate three things:

1. Plan edition timeline — when ICAO APAC published or endorsed each edition (V1.0, V2.0, V3.0, V4.0).
2. GANP / ASBU baseline timeline — the prevailing global framework version at the time of each Plan edition.
3. Plan-element target dates — the regional commitment dates carried inside each edition (which may be re-baselined between editions).

A State's own implementation roadmap is a fourth, national timeline, expressed in terms of the prevailing edition's element target dates.

Plan edition timeline#

V4.0 is the prevailing edition at the time of writing. The next edition is expected on the approximately three-year cycle aligned with the GANP review cadence.

GANP / ASBU baseline alignment#

Each Plan edition references the prevailing GANP edition. Indicative alignment:

GANP 4th ed. (2013) -- ASBU introduced (PIAs, Blocks 0-3)
       |
       |        APAC Seamless ATM Plan V1.0 (initial)
       v
GANP 5th ed. (2016) -- ASBU re-baselined to 2013/2019/2025/2031
       |
       |        APAC Seamless ATM Plan V2.0 (~2016)
       v
GANP 6th ed. (2019) -- multi-layer model; ASBU catalogue moves to portal
       |
       |        APAC Seamless ANS Plan V3.0 (renamed to ANS)
       v
GANP 7th ed. (2022) -- continued multi-layer model; performance + BBB
       |
       |        APAC Seamless ANS Plan V4.0 (Nov 2024)
       v
GANP next ed. (~2025-2026 expected)
       |
       |        Seamless ANS Plan next edition (expected ~2027)
       v

The three-year cadence is intentional: the Plan is reviewed alongside the GANP review cycle so regional commitments stay coherent with the global baseline.

Plan-element target dates#

Inside each edition, every priority element carries a regional target date, often tiered (regional expectation; extended date for States needing implementation support). Target dates are re-baselined between editions:

• Where an earlier edition's target slipped, the new edition's date governs.
• Where a State implemented ahead of the regional target, that capability counts toward seamless conformance immediately.
• Where ASBU module dates shifted (for example through GANP Portal catalogue updates), the Plan adjusts to keep regional and global expectations aligned.

The Reporting Tool record per element flags whether the State's status meets the prevailing edition's target date.

Where APAC States typically sit on the timeline#

Indicative regional context (verify current status against the latest APANPIRG and Reporting Tool outputs — these change annually):

• Block 0 baseline — substantially complete or in progress across the region. Common gaps remain in full PBN approach coverage at smaller airports, A-CDM beyond the largest hubs, and A-SMGCS at medium airports.
• Block 1 / Plan headline elements — active implementation across AIDC, ADS-B (including space-based for oceanic), Digital AIM (AIXM 5), IWXXM, FF-ICE/1 readiness, expanded FRA, ATFM CDM (including DMNATFM).
• Block 2 horizon — initial trials of TBO and ATN B2 data link; multi-constellation GNSS rollout planning; oceanic separation refinement.
• Block 3 — horizon planning and procurement strategy only.

Per V4.0 (2024), reporting is consolidated annually with a 28 February deadline.

Implementation monitoring cadence#

• Global — ICAO publishes ASBU implementation status as input to the GANP review cycle (3-yearly, aligned with the ICAO Assembly).
• Regional (APAC) — the Seamless ANS Plan is the regional implementation roadmap; APANPIRG monitors progress annually through the Seamless ANS Reporting Tool and feeds eANP Volume III via PFF entries.
• Sub-regional — APANPIRG sub-groups (ATM/SG, CNS/SG, AIM/SG, MET/SG, AOP/SG) review their thread's status at their own cycle, typically annual.
• National — typically a 3–5 year national air navigation plan, reviewed annually, expressed in Seamless ANS Plan element terms.

How to read a date in a Seamless ANS Plan document#

When a Plan document uses a date, check which kind of date it is:

• "V4.0 endorsed November 2024" — Plan edition publication date.
• "Element target date 2027" — regional commitment date for that element under the prevailing edition.
• "Block 1 from 2019" — global ASBU availability date, referenced for context.
• "28 February" — annual reporting deadline (V4.0).
• "Mid-year baseline" — initial reporting baseline at edition rollout.

Mixing these up leads to false claims that a State is "behind" or "ahead" of the Plan, when in fact the only meaningful measure is the State's reported status against the prevailing edition's target dates.

Primary Plan publications#

• Asia/Pacific Seamless ANS Plan, Version 4.0 (ICAO APAC, November 2024) — the prevailing edition. Defines the regional seamless ANS commitment, performance framework, PARS/PASL, priority elements, and reporting cadence (annual 28 February deadline following an initial mid-year baseline). https://www.icao.int/sites/default/files/APAC/Documents/Asia-Pacific-Seamless-ANS-Plan-Version-4.0.pdf
• Asia/Pacific Seamless ANS Plan, Version 3.0 — predecessor edition, retained for traceability of priority-element evolution from "ATM" to full "ANS" scope. https://www.icao.int/sites/default/files/APAC/Documents/Asia-Pacific-Seamless-ANS-Plan-Version-3.0.pdf
• Asia/Pacific Seamless ANS Plan portal (ICAO APAC) — landing page for current and archived editions. https://www.icao.int/APAC/asia-pacific-seamless-ans-plan
• ICAO APAC Seamless ATM Plan page (legacy entry point still cross-referenced). https://www.icao.int/APAC/Pages/Seamless-ATM-Plan.aspx

APANPIRG meeting reports and working papers#

• APANPIRG/35 WP/16 — Seamless ANS Plan Update (2024). Endorsement record for V4.0 of the Plan; confirms reporting cadence (28 February annual deadline; mid-year baseline). https://www.icao.int/sites/default/files/APAC/Meetings/APANPIRG/2024%20APANPIRG%2035/3-Working%20Papers/WP16-AI-3.0_REV-1-APAC-Seamless-ANS-Plan-Update.pdf
• APANPIRG/34 WP/16 — Updating the Asia/Pacific Seamless ANS Plan (2023). Interim endorsement and direction on updating the Plan toward V4.0. https://www.icao.int/sites/default/files/APAC/Meetings/APANPIRG/2023%20APANPIRG%2034/3-Working%20Papers/WP16-AI3.0_REV-2-Updating-the-Asia-Pacific-Seamless-ANS-Plan.pdf
• ATM/SG/12 WP/04 — Updating the Asia/Pacific Seamless ANS Plan (2024). Sub-group input feeding the V4.0 update. https://www.icao.int/sites/default/files/APAC/Meetings/2024/2024%20ATMSG-12/3-Working%20Papers/WP04-Updating-the-Asia-Pacific-Seamless-ANS-Plan.pdf
• CNS/SG/29 WP/16 — Seamless ANS Plan and reporting tool (2025). CNS sub-group treatment of the Plan and the Seamless ANS Reporting Tool. https://www.icao.int/sites/default/files/APAC/Meetings/2025/2025%20CNS%20SG29/3-Working%20Papers/WP16_ICAO-AI.10-Asia_Pacific-Seamless-ANS-Plan-and-reporting-tool.pdf

Companion APAC frameworks#

• Asia/Pacific Regional ATM Contingency Plan, V3.0. https://www.icao.int/sites/default/files/APAC/Documents/edocs/Regional-ATM-Contingency-Plan-Version-3.0.pdf
• APAC Plan for Collaborative AIM, V4.0. https://www.icao.int/sites/default/files/APAC/Documents/APAC-Plan-for-Collaborative-AIM-Version-4.0.pdf
• APAC Framework for Collaborative ATFM, V4.0 (October 2022). https://www.icao.int/sites/default/files/APAC/Documents/edocs/ATM/Asia-Pacific-Regional-Framework-for-Collaborative-ATFM-version-4.0-October-2022.pdf
• APAC PBN Plan (consult ICAO APAC portal for current version): https://www.icao.int/APAC/Pages/eDocs.aspx
• APAC eANP (Doc 9673), Volumes I, II, III — the regional Air Navigation Plan and performance framework into which Seamless ANS Plan PFF entries are migrated.

Global GANP / ASBU references#

• Doc 9750-AN/963 — Global Air Navigation Plan (GANP), current edition. Global parent framework for the Seamless ANS Plan.
• Doc 9854 — Global Air Traffic Management Operational Concept. Source of the eleven Key Performance Areas (KPAs).
• Doc 9883 — Manual on Global Performance of the Air Navigation System. Defines the performance management methodology used by the Plan's performance framework.
• ICAO GANP Portal — live home of the ASBU framework and module catalogue; the Plan references modules from this portal. https://ganpportal.icao.int/
• ICAO GANP overview page. https://www.icao.int/global-air-navigation-plan-ganp

ICAO PANS and Annex references most cited by the Plan#

• Doc 4444 — PANS-ATM. Air traffic services procedures for ATS, ATFM, AIDC, contingency.
• Doc 8168 — PANS-OPS. Procedure design rules for PBN, CDO/CCO.
• Doc 10066 — PANS-AIM. AIM transition, Aeronautical Data Catalogue, AIXM 5.
• Doc 10157 — PANS-MET. MET procedures, IWXXM exchange.
• Doc 7030 — Regional Supplementary Procedures (APAC SUPPS). Region-specific procedures including oceanic.
• Doc 9613 — Performance-Based Navigation (PBN) Manual.
• Doc 9082 — Policies on Charges for Airports and Air Navigation Services. Charging-policy basis for funding ANS modernisation.
• Annex 10 (CNS), Annex 11 (ATS), Annex 14 (Aerodromes), Annex 15 (AIS), Annex 19 (SMS) — the SARPs most often invoked by Plan elements.

Regional governance bodies referenced#

• APANPIRG — Asia/Pacific Air Navigation Planning and Implementation Regional Group. Endorses each Plan edition.
• APANPIRG sub-groups — ATM/SG, CNS/SG, AIM/SG, MET/SG, AOP/SG.
• ICAO Asia and Pacific Regional Office (Bangkok) — Plan secretariat and custodian of the Reporting Tool.
• RASG-APAC — Regional Aviation Safety Group, Asia/Pacific. Companion safety body whose work intersects with the Plan's safety KPAs.

Adjacent references in this workspace#

• topics_detailed/asbu/ — global ASBU framework that the Seamless ANS Plan localises for APAC.
• topics_detailed/air_navigation_plan/ — global / regional ANP structure (Doc 9750 / Doc 9673).
• topics_detailed/atfm/, topics_detailed/a_cdm/, topics_detailed/aim/, topics_detailed/aidc/, topics_detailed/ff_ice/, topics_detailed/aixm/ — individual priority threads called out by the Plan.
• topics/seamless_atm_plan.md — public summary in the workspace's citable layer.

Note on local library coverage#

The local ICAO Markdown library mirrors core SARPs, PANS, and selected manuals but does not host the APAC Seamless ANS Plan itself. The Plan and its companion APAC frameworks are obtained directly from the ICAO APAC Office portal (links above). Treat those URLs as authoritative; the local library is used for the underlying SARPs (Annex 10, Annex 11, Annex 14, Annex 15, etc.) and PANS (Doc 4444, Doc 8168, Doc 10066, Doc 10157) that the Plan elements reference.