Detailed working notes on Aeronautical Information Management (AIM). This folder expands the summary in topics/aim.md into per-aspect files so each can be read on its own.

Files in this folder#

• overview.md — what AIM is, the AIS-to-AIM transition, and where AIM sits in the GANP / ASBU framework.
• components.md — the products (AIP, NOTAM, AIC, charts), services, digital data sets, and the data quality framework.
• blocks.md — the AIM roadmap phases and Digital AIM (DAIM) maturity levels mapped to ASBU Blocks.
• threads.md — capability areas: data origination, validation, distribution, and integrated briefing.
• modules.md — anatomy of an AIM service (objective, procedure, technology, enablers, KPI links).
• enablers.md — AIXM, SWIM, IWXXM, training, regulation, certification, QMS, formal arrangements.
• performance_objectives.md — KPAs (data quality, integrity, timeliness) and KPIs.
• timeline.md — Annex 15 amendment history, AIM roadmap publication, PANS-AIM (Doc 10066) origin.
• references.md — consolidated ICAO and external references for everything in this folder.

Reading order#

Start with overview.md, then components.md for the inventory of what an AIM provider actually delivers. Move to blocks.md and threads.md for the roadmap and capability axes, then drill into modules.md, enablers.md, and performance_objectives.md. Use timeline.md for the regulatory chronology and references.md for citations.

Source basis#

Content is grounded in:

• ICAO Annex 15 — Aeronautical Information Services (16th edition, applicable from Amendment 40, 8 November 2018).
• ICAO Doc 10066 — PANS-AIM (Procedures for Air Navigation Services — Aeronautical Information Management), including Appendix 1 (Aeronautical Data Catalogue).
• ICAO Doc 8126 — Aeronautical Information Services Manual (current edition), including Part I on the AIS-to-AIM transition.
• ICAO Doc 9750 — Global Air Navigation Plan (GANP), 5th to 7th editions, where the DAIM thread is defined.
• ICAO Doc 9839 — Manual on the Quality Management System for Aeronautical Information Services / Management.
• ICAO Doc 9674 — World Geodetic System — 1984 (WGS-84) Manual.
• ICAO Doc 10039 — Manual on System Wide Information Management (SWIM) Concept.
• ICAO Doc 9881 — Guidelines for Electronic Terrain, Obstacle and Aerodrome Mapping Information.
• ICAO GANP Portal: https://ganpportal.icao.int/
• EUROCONTROL AIM specification and AIXM: https://www.aixm.aero/

What AIM is#

AIM stands for Aeronautical Information Management. ICAO Annex 15 and PANS-AIM (Doc 10066) define it as the dynamic, integrated management of aeronautical information through the provision and exchange of quality-assured digital aeronautical data in collaboration with all parties. AIM treats aeronautical data as a controlled asset, managed end-to-end from its originator through processing, publication, distribution, and use by the next intended user.

Two terms underpin the discipline:

• Aeronautical data — the formal representation of aeronautical facts, concepts, or instructions, suitable for communication, interpretation, or processing.
• Aeronautical information — the result of the assembly, analysis, and formatting of aeronautical data.

Both are managed entities whose accuracy, resolution, integrity, traceability, timeliness, completeness, and format must be preserved throughout the chain.

The AIS-to-AIM transition#

AIM is the successor to Aeronautical Information Services (AIS). AIS, as originally framed in early editions of Annex 15, was paper- and product- centred: the AIP was a printed publication, NOTAM was a teleprinter feed, and the recipient was assumed to be a pilot or briefer reading text.

AIM is data-centric and service-oriented. The same underlying facts about an aerodrome, navaid, route, or procedure are managed once as a quality-assured data record, then exposed to many consumers: cockpit navigation databases, electronic flight bags, ANSP automation, network managers, flow systems, drone operators, and chart publishers. Doc 8126 frames the migration as moving "from paper-based, product-centred aeronautical information services (AIS) to data-centric and digital aeronautical information management (AIM)."

The driver is the increasing dependence of RNAV, PBN, on-board navigation databases, data link, and Collaborative Decision Making on quality-assured digital data. State responsibilities do not change in principle, but the way they are discharged does: emphasis shifts to data distribution, data quality, formal arrangements with originators, and service-based delivery.

Where AIM sits in the GANP and ASBU framework#

In the Global Air Navigation Plan (Doc 9750), AIM is the information backbone alongside SWIM, FF-ICE, and AMET. The ASBU technical level expresses AIM modernization through the DAIM (Digital AIM) thread, with modules sequenced across Blocks 0 to 3:

• DAIM-B0 — quality-managed digital AIS data sets and electronic AIP.
• DAIM-B1 — full Digital AIM, AIXM 5 data products, integrated briefing.
• DAIM-B2/B3 — semantic interoperability, machine-readable NOTAM, trajectory-aware aeronautical information.

Doc 8126 cites "DAIM and SWIM elements of the ASBUs" as the drivers of the AIS-to-AIM transition. AIM is therefore not optional: it is the data foundation that PBN procedures, TBO, and network operations all rely on.

What AIM planners do#

For an AIS/AIM provider, an AIM-aligned plan answers four questions:

1. What aeronautical data does the State publish, who originates it, and what is its required quality (accuracy, resolution, integrity)?
2. What products and services must be delivered (AIP, NOTAM, AIC, charts, digital data sets, briefing services, SWIM services)?
3. What enablers must be in place (AIXM, SWIM-TI, QMS per Doc 9839, formal arrangements with originators, training, regulation)?
4. By when (alignment with Annex 15 SARPs, AIRAC cycle, regional roadmap) must each capability be operational?

Why AIM matters now#

Three external pressures make AIM modernization urgent:

• Performance-based navigation. RNP and RNP AR procedures cannot be flown safely from low-quality data; the integrity classification regime in PANS-AIM exists precisely to protect the FMS-loadable data chain.
• Trajectory-based operations. TBO depends on shared aeronautical reference data (airspace, routes, restrictions, procedures) being identical and current across air and ground.
• Drones and U-space. Unmanned operations need machine-readable, near-real-time aeronautical information at finer spatial granularity than legacy NOTAM provides.

AIM is delivered through a structured set of products, services, digital data sets, and quality controls. Annex 15 §1.1 defines an "aeronautical information product" as the umbrella term covering all of these.

1. Aeronautical Information Publication (AIP)#

The authoritative reference document published by or on behalf of a State, containing aeronautical information of a lasting character essential to air navigation. The AIP is structured in three parts:

• GEN — General. State authority, regulations, charges, abbreviations, units, services common to all aerodromes.
• ENR — En Route. Airspace, ATS routes, navigation aids, en-route warning and restricted areas, en-route MET.
• AD — Aerodromes. Per-aerodrome data: physical characteristics, declared distances, lighting, services, charts, instrument procedures.

AIP changes are issued as:

• AIP Amendments — permanent changes integrated into the AIP, generally on AIRAC effective dates for operationally significant content.
• AIP Supplements — temporary changes of long duration (three months or more) or short-duration changes containing extensive text or graphics.

2. NOTAM#

Notice distributed by means of telecommunication containing information concerning the establishment, condition, or change in any aeronautical facility, service, procedure, or hazard, the timely knowledge of which is essential to personnel concerned with flight operations. NOTAM is used for time-critical or short-duration information that the AIRAC cycle cannot accommodate.

PANS-AIM specifies NOTAM format (Q-line, A-E lines), origination criteria, distribution series, and lifecycle. The transition to digital NOTAM (structured per AIXM 5.1 Event schema) is one of the headline DAIM deliverables.

3. Aeronautical Information Circular (AIC)#

A notice containing information that does not qualify for inclusion in the AIP or NOTAM but relates to flight safety, air navigation, technical, administrative, or legislative matters. AICs are typically issued in coloured series (e.g. white, yellow, pink) by topic.

4. Charts#

Annex 4 — Aeronautical Charts — defines the chart series an AIS/AIM provider must publish. Common types referenced from AIM products:

• Aerodrome / Heliport Chart.
• Aircraft Parking / Docking Chart.
• Aerodrome Ground Movement Chart.
• Standard Instrument Departure (SID) Chart.
• Standard Instrument Arrival (STAR) Chart.
• Instrument Approach Chart (per procedure type).
• Visual Approach Chart.
• En-route Chart.
• Area Chart.
• Plotting Chart (for oceanic).
• World Aeronautical Chart (WAC) / Aeronautical Chart (1:500 000).

5. Pre-flight and post-flight information services#

• Pre-flight Information Bulletin (PIB) — a presentation of current NOTAM and other operationally significant information for a specified flight or area.
• Self-briefing services — increasingly delivered through web portals or APIs over SWIM, replacing dedicated briefing offices.
• Post-flight information — collection of bird-strike, ATS occurrence, and condition reports feeding back into the AIM data chain.

6. Digital data sets#

Annex 15 mandates a family of digital data sets, each with defined content, accuracy, resolution, and integrity:

• AIP data set — the AIP content in structured digital form.
• Terrain data set — eTOD Areas 1–4 around aerodromes.
• Obstacle data set — eTOD obstacles in Areas 1–4.
• Aerodrome mapping data set (AMDB) — runways, taxiways, aprons, stands, signage, lighting, service roads, per RTCA DO-272 / EUROCAE ED-99.
• Instrument flight procedure (IFP) data set — coded procedure data suitable for FMS database production, per ARINC 424 / EUROCAE ED-77.

These data sets are exchanged using AIXM 5 (Aeronautical Information Exchange Model) wherever practicable.

7. Services (the AIM service layer)#

Beyond products, AIM provides services to internal and external consumers:

• Origination intake — receiving raw data from accredited originators.
• Validation and verification — checks against PANS-AIM Appendix 1 Aeronautical Data Catalogue requirements.
• Distribution services — AIP publishing, NOTAM distribution (AFTN / AMHS / SWIM), digital data set delivery.
• Briefing services — PIB and equivalents.
• SWIM services — operational AIM information services exposed on the SWIM technical infrastructure with defined QoS and access policy.

8. Data quality framework#

Annex 15 §1.1 defines data quality as the degree of confidence that data meet user requirements in terms of accuracy, resolution, integrity (or equivalent assurance level), traceability, timeliness, completeness, and format. Three quantitative attributes drive operational use:

• Accuracy — degree of conformance between estimated/measured and true value, expressed as a 95 % confidence interval for positional data.
• Resolution — number of units or digits to which a value is expressed and used.
• Integrity classification — risk-based class assigned per data element in the Aeronautical Data Catalogue:
  • Routine: 1 x 10^-3 probability of corruption.
  • Essential: 1 x 10^-5.
  • Critical: 1 x 10^-8 (e.g. runway thresholds, ILS reference points, obstacles in critical areas).

PANS-AIM Chapter 2 mandates verification, validation, traceability of automated processing, and continuous data integrity monitoring. A formal Quality Management System per ISO 9000, supported by Doc 9839, is a SARP requirement for the AIS/AIM provider.

9. Aeronautical Data Catalogue#

PANS-AIM Appendix 1 lists each data element, its sub-properties, the originator type, and the required accuracy, resolution, and integrity class. The Catalogue is the authoritative reference for formal arrangements between AIS/AIM and originators (aerodromes, ATS, procedure designers, airspace planners, MET, surveying authorities).

The AIS-to-AIM transition is conventionally described in three phases defined in the original ICAO AIS-AIM Study Group roadmap and subsequently embedded in the ASBU Digital AIM (DAIM) thread of the GANP. Together with the four ASBU Block availability windows, they give a planner two complementary axes for sequencing AIM modernization.

The three AIS-to-AIM transition phases#

ICAO's AIS-AIM Roadmap (originally published 2008 and refined under the AIS-AIMSG) sets out three phases. Each is cumulative; later phases assume the earlier phases are in place.

Phase 1 — Consolidation#

Theme. Bring legacy AIS up to the quality and digital baseline that later phases assume.

Representative deliverables:

• AIP fully maintained electronically; eAIP available.
• WGS-84 conformance of all published coordinates (per Doc 9674).
• Quality Management System certified per ISO 9001 / Doc 9839.
• Formal arrangements with all data originators, anchored in the Aeronautical Data Catalogue.
• AIRAC discipline observed for all operationally significant changes.
• eTOD Area 1 (and Area 2 around international aerodromes) published.
• Initial digital data sets: AIP data set, basic obstacle data.

Phase 2 — Going Digital#

Theme. Move from "digital documents" to "digital data". The same underlying data record drives the AIP, the navigation database, the chart, and the NOTAM.

Representative deliverables:

• AIXM 5.x adopted as the exchange model for static and dynamic data.
• Aerodrome Mapping Data Base (AMDB) published per DO-272 / ED-99.
• Instrument flight procedure (IFP) data set published per coded format.
• Full eTOD coverage Areas 1–4 around aerodromes serving international IFR operations.
• Digital NOTAM trials (event-based, AIXM 5.1 Event schema).
• Database-driven publishing toolchain; chart, AIP, and data set generation from a single data store.

Phase 3 — Information Management#

Theme. AIM as a service-oriented capability inside SWIM. Aeronautical information is consumed by automated systems via well-governed services, not by humans reading documents.

Representative deliverables:

• AIM information services published on SWIM with QoS, access policy, and lifecycle governance per Doc 10039.
• Digital NOTAM operational; legacy text NOTAM phased down.
• Integrated briefing combining AIM, MET (IWXXM), and flow information.
• Trajectory-aware aeronautical information consumed directly by ground automation and FMS.
• Cross-State and cross-region semantic interoperability validated through reference implementations.

Mapping to ASBU Blocks#

The DAIM thread maps each transition phase to ASBU Block availability:

These dates are notional global availability dates, not deadlines for States. A State's national AIM roadmap must express its own milestones against these reference points.

DAIM maturity levels#

Many regional plans (notably the EUROCONTROL AIM specification and the APAC Seamless ATM Plan) score AIM provider maturity on a five-level scale. A common rendering:

• Level 1 — Paper AIS. Paper AIP, teleprinter NOTAM, no QMS.
• Level 2 — Electronic AIS. eAIP, partial QMS, basic digital data.
• Level 3 — Digital AIS. WGS-84 conformant, ISO-9001 QMS, AIXM 4/5 for AIP data set, eTOD Areas 1–2.
• Level 4 — Initial AIM. AIXM 5 for static and dynamic data, AMDB, IFP data set, digital NOTAM trials, integrated AIM tooling.
• Level 5 — Full AIM in SWIM. AIM services on SWIM, digital NOTAM operational, integrated briefing, semantic interoperability.

Levels 1–3 correspond to Transition Phase 1 / ASBU Block 0; Level 4 to Phase 2 / Block 1; Level 5 to Phase 3 / Blocks 2–3.

How a State sequences the roadmap#

A typical national AIM implementation plan sequences as follows:

1. Close residual Phase 1 gaps: complete WGS-84 conversion, certify QMS, document formal arrangements with all originators, publish eTOD Areas 1–2.
2. Stand up Phase 2 capability: AIXM 5 publishing toolchain, AMDB for at least the international aerodromes, IFP data set, full eTOD.
3. Move to Phase 3: connect to a SWIM technical infrastructure, trial digital NOTAM with neighbouring States, expose AIM services with documented QoS.
4. Treat DAIM-B3 as horizon planning, especially the trajectory and semantic-interoperability deliverables that depend on TBO maturity.

Skipping phases is rarely viable: a State that exposes "AIM services on SWIM" before WGS-84 and integrity-classified data are in place merely distributes poor-quality data faster.

Where ASBU uses Threads as columns of its matrix, AIM is best understood through four capability areas that span the full data lifecycle: from the moment a fact about the National Airspace is observed, to the moment a flight crew or automation system uses it. These are the AIM analogues of ASBU Threads.

The four capability areas are:

1. Data origination — getting authoritative data into the AIM chain.
2. Data validation and processing — turning raw data into quality-assured information.
3. Data distribution — getting the right information to the right user in the right form at the right time.
4. Integrated briefing and consumption — supporting operational decision-making at the user end.

Each is governed by Annex 15 SARPs and PANS-AIM procedures, with supporting guidance in Doc 8126.

1. Data origination#

Scope. Identification of data originators, formal arrangements with each originator, intake interfaces, and traceability of every data element back to its authoritative source.

Key elements:

• Originators — aerodrome operators (physical characteristics, AMDB, obstacles), ATS authority (airspace, routes, separation), procedure designers (SID/STAR/IAP), MET authority (climatology), surveying authorities (geodesy, terrain), the State (regulations, charges).
• Formal arrangements (PANS-AIM §2.1.1 and Doc 9839) — written agreements covering responsibilities, data scope, quality requirements per the Aeronautical Data Catalogue, timeliness, change-notification protocols, and dispute resolution.
• Originator metadata — every data element carries its originator identifier, the date and time of origination, and the chain of custody up to publication.
• Aeronautical Data Catalogue (PANS-AIM Appendix 1) — the authoritative dictionary that all originators and AIS/AIM share.

Common gaps: originators outside the AIS/AIM provider's organisation (e.g. private aerodrome operators) without contractually anchored quality obligations; informal email-based intake; missing originator metadata.

2. Data validation and processing#

Scope. All steps between intake and publication: verification against the Catalogue, validation against operational constraints, formatting, encoding, integrity protection, and pre-publication review.

Key elements:

• Verification — confirms that received data conform to the Catalogue requirements (accuracy, resolution, integrity class, format).
• Validation — confirms that data are operationally correct and internally consistent (e.g. a published procedure uses navaids that exist; a runway threshold elevation is consistent with the runway profile).
• Cyclic Redundancy Check (CRC) — PANS-AIM mandates CRC protection for data classified Essential and Critical, end-to-end across the publishing chain.
• Traceability — every automated transformation is logged so that any downstream data record can be traced back to its inputs.
• Continuous data integrity monitoring — sample-based checking that published data still match the originator record; corrective action workflows for drift.
• Quality Management System — PANS-AIM Chapter 3 and Doc 9839 require an ISO-9001-aligned QMS covering all AIM processes.

3. Data distribution#

Scope. Publication and dissemination of products, services, and data sets to internal and external consumers, on agreed schedules and through agreed channels.

Key elements:

• AIRAC discipline — operationally significant changes published on common 28-day effective dates per the ICAO AIRAC schedule, with at least 42 days between distribution and effective date (target 56 for major changes).
• Publication channels — AIP and amendments (paper and eAIP), Supplements, AICs, charts (Annex 4 series), digital data sets.
• NOTAM distribution — AFTN / AMHS legacy; transition to digital NOTAM over SWIM.
• Distribution lists and series — series codes, addressee lists, international NOTAM Office (NOF) responsibilities.
• SWIM services — published with documented service description, QoS, semantic conformance, security policy.
• Open standards — AIXM 5 for aeronautical exchange; ARINC 424 / EUROCAE ED-77 for IFP coded data; DO-272 / ED-99 for AMDB.

Common gaps: AIRAC slippage; mismatch between AIP and chart series; NOTAM issued on AIRAC-eligible content (a procedural error); absence of SWIM service description even when the service is technically available.

4. Integrated briefing and consumption#

Scope. Pre-flight and in-flight information delivery to the end user: flight crew, dispatchers, ATC, network manager, drone operators, chart and FMS database vendors.

Key elements:

• Pre-flight Information Bulletin (PIB) — current NOTAM and operationally significant information presented for a specified flight or area.
• Self-briefing portals — web/API delivery, increasingly SWIM-backed, replacing manned briefing offices.
• Integrated AIM/MET briefing — combining aeronautical (AIXM) and meteorological (IWXXM) information in a single decision view.
• FMS database production — AIM IFP data set feeds the worldwide navigation database supply chain (typically via DO-200B / ED-76A data process assurance).
• Charting supply chain — chart publishers (commercial and State) consume AIM data sets to produce printed and electronic charts.
• Drone and U-space consumption — finer-grained, near-real-time airspace and obstacle data for unmanned operations.

Cross-thread dependencies#

• Distribution depends on validation and processing: you can only distribute what has been quality-assured.
• Validation and processing depends on origination: data quality starts at the originator; downstream checks cannot recover from systematically poor input.
• Integrated briefing depends on all three upstream threads, plus on the SWIM and IWXXM enablers (see enablers.md).

This is why AIM modernization cannot be done by a single project. It is a coordinated programme across the data lifecycle, with the AIS/AIM provider acting as the integration authority.

What an AIM "module" is#

In ASBU terms, an AIM module is a cell at the intersection of the DAIM thread and one Block. In the operational language of the AIS/AIM provider, the unit of delivery is more naturally an AIM service — a coherent capability such as "publish the AIP", "issue NOTAM", "distribute the IFP data set", "expose an AIM SWIM service". The two views are aligned: each AIM service realises one or more DAIM modules.

This file describes the anatomy that a planner should fill in for each AIM service, mirroring the ASBU module template.

Service identifier convention#

The DAIM thread uses ASBU module identifiers:

DAIM-B<n>/<sequence>

Examples:
  DAIM-B0/1   - Quality-managed digital AIS data sets and electronic AIP
  DAIM-B1/1   - Full Digital AIM, AIXM 5 data products
  DAIM-B2/1   - SWIM-distributed AIM and digital NOTAM

Internally, an AIS/AIM provider typically also names services by function (AIP-Pub, NOTAM-Origination, IFP-DataSet, AIM-SWIM-Service, PIB-Service, etc.) and links each to one or more DAIM modules.

Anatomy of an AIM service#

1. Title and identifier#

For example: DAIM-B1/1 — Full Digital AIM, AIXM 5 data products or internally IFP-DataSet — Coded Instrument Flight Procedure data set.

2. Operational improvement description#

A plain-language statement of what changes for the user. For DAIM-B1/1: a single AIXM 5 data store drives the AIP, charts, NOTAM, and FMS data feed; consumers receive coherent, integrity-classified, machine-readable information.

3. Performance objective and applicable KPAs#

The "why". KPAs primarily improved by AIM services:

• Safety — through higher data integrity, especially for Critical data (1 x 10^-8) used in PBN procedures.
• Predictability — through AIRAC discipline and timeliness.
• Interoperability — through standard exchange models (AIXM, IWXXM) and SWIM.
• Cost-effectiveness — through automation and elimination of duplicate data processing.

4. Procedure element#

The procedural changes required, drawing on:

• PANS-AIM (Doc 10066) — Chapters 2–7 covering information management, QMS, content scope, products, AIRAC, distribution, and data quality; Appendix 1 Aeronautical Data Catalogue.
• Annex 15 amendments — most recently Amendment 40 (8 November 2018) restructuring Annex 15 around AIM.
• State AIP General (GEN) sections — describing local procedures.
• Letters of agreement — with neighbouring NOFs and originators.

5. Technology element#

The systems that must be deployed for an AIM service:

• AIM database (often a relational + spatial store, structured per AIXM feature types).
• AIXM 5 import / export tooling.
• AIRAC scheduling and publishing toolchain.
• NOTAM origination, distribution, and (for digital NOTAM) AIXM 5.1 Event handling.
• eAIP generation (XML-based per EUROCONTROL Specification).
• AMDB editor and DO-272 / ED-99 export.
• IFP coding tooling and ARINC 424 / ED-77 export.
• SWIM technical infrastructure adaptors and service registry entries.
• Identity, access, and audit logging across the chain.

6. Human performance element#

• AIM officer training (Annex 1 endorsement frameworks where applied).
• Procedure designer training (Doc 9906, Doc 8168).
• Surveyor and originator training on Catalogue requirements.
• Briefer transition to integrated AIM/MET tooling.
• Controller awareness of digital NOTAM workflows.

7. Standards basis#

Annex 15 (AIS), Annex 4 (Charts), Annex 11 (ATS for airspace data), Annex 14 (Aerodromes for AMDB), Annex 19 (SMS), Doc 9613 (PBN), Doc 9881 (eTOD), Doc 9674 (WGS-84), Doc 9839 (QMS for AIM), Doc 10066 (PANS-AIM), Doc 10039 (SWIM), DO-200B / ED-76A (data process assurance), DO-272 / ED-99 (AMDB), DO-201A / ED-77 (aeronautical information data).

8. Enablers#

See enablers.md. Headline enablers for AIM: AIXM, SWIM, IWXXM, training, regulation, certification, QMS, formal arrangements with originators.

9. Dependencies#

Other DAIM modules and other ASBU modules that must be in place first. Examples:

• DAIM-B1 depends on DAIM-B0 (digital AIS baseline, WGS-84 conformance, QMS in place).
• DAIM-B2 depends on DAIM-B1 (AIXM 5 data products) and SWIM-B1 (operational SWIM services).
• TBO-B2 (in the Operational threads) depends in turn on DAIM-B1 to ensure consistent reference data air-and-ground.

10. KPI linkage#

Quantitative measures (see performance_objectives.md):

• AIRAC publication on time (% of changes meeting the 42- or 56-day pre-effective deadline).
• AIP amendment cycle conformance.
• Data integrity event rate (corruption, mismatch).
• NOTAM accuracy (originator-confirmed correct on issue).
• Digital NOTAM share of total NOTAM.
• Time-to-publish for safety-significant changes.

11. Region applicability#

Most AIM services are universally applicable: Annex 15 SARPs apply to every Contracting State. Regional plans add specifics (cross-border NOTAM exchange, regional eTOD priorities).

12. Implementation guidance#

• Doc 8126 — AIS Manual.
• ICAO AIM Roadmap (originally AIS-AIMSG output).
• EUROCONTROL AIM specification and AIXM tooling.
• APAC Seamless ATM Plan AIM section.
• IATA / industry training (DO-200B data process assurance).

Worked examples#

Example 1 — DAIM-B0/1 Quality-managed digital AIS data sets#

• Operational improvement. AIP, basic eTOD, and core navigation data published from a quality-managed digital store; WGS-84 conformant; QMS certified.
• KPAs. Safety, interoperability, cost-effectiveness.
• Procedure. Annex 15 chapters on AIP, AIRAC, data quality; Doc 9839 QMS implementation; formal arrangements per PANS-AIM §2.1.1.
• Technology. Digital AIM database, eAIP toolchain, eTOD store.
• Enablers. Trained AIM officers; certified QMS; agreements with all originators.
• Dependencies. None upstream; baseline for DAIM-B1.
• KPIs. WGS-84 conformance %, AIRAC compliance %, QMS audit pass.

Example 2 — DAIM-B1/1 Full Digital AIM, AIXM 5#

• Operational improvement. AIXM 5 data products available for AIP, airspace, routes, navaids, procedures; AMDB and IFP data sets published; integrity-classified data with CRC protection end-to-end.
• KPAs. Safety, interoperability, predictability, cost-effectiveness.
• Procedure. PANS-AIM Chapters 2–7 fully implemented; integrated publishing process; data integrity monitoring.
• Technology. AIXM 5 store; AMDB editor (DO-272/ED-99); IFP coding tool (ARINC 424 / ED-77); CRC pipeline.
• Enablers. Trained data designers; DO-200B / ED-76A process assurance for the FMS data supply.
• Dependencies. DAIM-B0; alignment with PBN procedure design.
• KPIs. AIXM 5 product completeness; AMDB coverage of international aerodromes; Critical-data integrity event rate.

Example 3 — DAIM-B2/1 SWIM-distributed AIM and digital NOTAM#

• Operational improvement. AIM information services exposed on SWIM with documented service description and QoS; digital NOTAM exchanged with adjacent States; integrated AIM/MET briefing.
• KPAs. Interoperability, predictability, efficiency.
• Procedure. Doc 10039 service governance; bilateral SWIM agreements; digital NOTAM operational procedures.
• Technology. SWIM-TI adaptors; service registry; AIXM 5.1 Event; IWXXM gateway for joint briefing.
• Enablers. SWIM connectivity (ATN/IPS, IPv6); identity and access framework; security accreditation.
• Dependencies. DAIM-B1, SWIM-B1, AMET-B1.
• KPIs. SWIM service availability and latency; digital NOTAM share; cross-State semantic conformance rate.

What an AIM enabler is#

An enabler is a supporting element without which an AIM service cannot deliver its intended benefit. Enablers are not themselves the operational improvement; they are prerequisites that must be in place before AIM services can be safely deployed.

AIM enablers fall into seven categories.

1. Exchange models and information standards#

The data substrate of AIM:

• AIXM (Aeronautical Information Exchange Model). UML- and XML/GML-based exchange model for aeronautical information. AIXM 5.x is the version aligned with current Annex 15 and PANS-AIM. AIXM 5.1 introduces the temporality model used for digital NOTAM. Maintained jointly by EUROCONTROL and the FAA. Reference: https://www.aixm.aero/
• ARINC 424 / EUROCAE ED-77 / RTCA DO-201A. Coded data formats for FMS-loadable navigation databases and the underlying data process.
• DO-272 / EUROCAE ED-99. Aerodrome Mapping Data Base (AMDB) content and format.
• DO-200B / EUROCAE ED-76A. Standards for processing aeronautical data — the assurance regime for the data chain from originator to end user.
• WGS-84 (Doc 9674). Common geodetic reference for all published coordinates.
• ISO 19101 / 19115 / 19131 — geographic information, geographic metadata, and data product specifications. Underpin AIXM data product engineering.

2. SWIM (System Wide Information Management)#

The service-oriented backbone for AIM in Block 2 and beyond:

• Doc 10039 — Manual on the SWIM Concept. Defines services, governance, security, quality of service, and registry concepts.
• SWIM Technical Infrastructure (SWIM-TI) — message-oriented middleware, service registries, identity and access management, monitoring.
• Information services — AIM, MET (IWXXM), flight (FIXM/FF-ICE), flow (FIXM-flow), surveillance information.
• Network underlay — ATN/IPS, IPv6, regional networks (PENS / NewPENS in Europe; APAC equivalents).
• Service description and QoS — every published AIM service has a documented service description, semantic profile, and QoS contract.

3. IWXXM and AMET#

AIM and MET converge at the user — the integrated briefing — so AMET is a partner enabler for full AIM:

• IWXXM (ICAO Meteorological Information Exchange Model). XML/GML model for METAR, TAF, SIGMET, AIRMET, volcanic ash advisories, tropical cyclone advisories, space weather.
• PANS-MET (Doc 10157). MET procedures aligned with IWXXM and SWIM.
• Annex 3. SARPs for meteorological service for international air navigation.

4. Quality Management System and process assurance#

• Doc 9839 — Manual on the Quality Management System for AIM. Implementation guidance for the QMS required by Annex 15.
• ISO 9000 / 9001. Generic QMS standard underlying Doc 9839.
• Continuous data integrity monitoring per PANS-AIM Chapter 2.
• DO-200B / ED-76A data process assurance for any data flowing into FMS-loadable navigation databases. Sets the contractual frame between AIS/AIM, the data house, and the avionics OEM.

5. Training and human resources#

• AIM officer training. Curriculum covering the Catalogue, PANS-AIM procedures, AIXM, AIRAC, NOTAM origination, integrity classification, QMS, data integrity monitoring.
• Procedure designer training (Doc 9906, Doc 8168). Designers produce the highest-integrity data in the chain.
• Surveyor training (Doc 9881, Doc 9674). Field surveyors must understand the accuracy and integrity classes for the points they capture.
• Briefer training. Transition from manual PIB to self-briefing portals and integrated AIM/MET tools.
• Controller awareness. Digital NOTAM consumption and trajectory-aware aeronautical data.

6. Regulation, certification, and oversight#

• State-level regulation. Designation of the AIS/AIM provider; integration with the State Safety Programme (Annex 19); oversight by the CAA.
• Annex 15 SARPs implementation in national regulation.
• Formal arrangements with originators — contractually anchored obligations on quality, timeliness, and traceability per the Aeronautical Data Catalogue.
• Certification of digital data products — particularly IFP and AMDB destined for navigation databases, aligned with DO-200B / ED-76A.
• Cybersecurity regulation for SWIM-connected systems; Annex 17 references where information sharing introduces security considerations.
• Charging policy (Doc 9082, Doc 9587). Cost-recovery for AIM services delivered to operators.

7. Institutional and inter-State#

• International NOTAM Office (NOF) arrangements. Bilateral agreements on series, addressing, and content with neighbouring States.
• Regional planning fora. APANPIRG (APAC), MIDANPIRG (MID), EANPG (EUR), GREPECAS (CAR/SAM), AFI Planning and Implementation Regional Group — endorse harmonised AIM roadmaps.
• Regional roadmaps. APAC Seamless ATM Plan AIM section; MID Air Navigation Strategy; European ATM Master Plan AIM/SWIM elements.
• Cross-border data exchange agreements. SWIM service exchange, digital NOTAM bilateral readiness, joint AIRAC release coordination.

How enablers are managed in practice#

For each AIM service, the planner records the enablers, their owner, their current status, and the date by which each is required. A service is not considered fully implemented until all declared enablers are in place — the headline AIM technology cannot stand alone.

This is why AIM modernization is rarely a single procurement: it is a coordinated programme spanning ICAO standards adoption, regulation, training, formal arrangements with originators, supplier qualification, QMS certification, and SWIM network connectivity. A State that procures an AIXM 5 publishing system without QMS certification, formal originator arrangements, and DO-200B-compliant downstream processing will publish prettier — but not safer — aeronautical data.

The performance lens of AIM#

AIM is a performance-based discipline: every service is justified by the quality, timeliness, and operational utility of the information it delivers, and progress is measured against defined Key Performance Indicators. Annex 15 §1.1 enumerates the seven attributes that frame AIM data quality — accuracy, resolution, integrity, traceability, timeliness, completeness, and format — and PANS-AIM Chapters 2 and 7 operationalise them.

The chain is the same as for ASBU:

KPA  --(measured by)-->  KPI  <--(targeted by)--  Performance Objective  --(achieved by)-->  AIM service / DAIM module

Key Performance Areas most directly affected by AIM#

Of the eleven Doc 9854 / Doc 9883 KPAs, AIM principally drives:

• Safety — through end-to-end data integrity, especially for Critical data feeding PBN procedures and FMS databases.
• Predictability — through AIRAC discipline and timeliness.
• Interoperability — through standard exchange models (AIXM, IWXXM) and SWIM service governance.
• Cost-effectiveness — through automation, single-source data, and elimination of duplicate processing.
• Capacity and flight efficiency — indirectly, by enabling operational threads (PBN, TBO, FRTO, CDO) that depend on quality-assured aeronautical information.

AIM-specific data quality attributes#

Annex 15 names seven attributes; AIM performance objectives map to each:

• Accuracy — degree of conformance with the true value, expressed as 95 % confidence for positional data.
• Resolution — units / digits in which a value is expressed.
• Integrity — protection against corruption, by class:
  • Routine: 1 x 10^-3 corruption probability.
  • Essential: 1 x 10^-5.
  • Critical: 1 x 10^-8.
• Traceability — chain of custody from originator to publication.
• Timeliness — currency of published data; adherence to AIRAC and NOTAM cycles.
• Completeness — all required attributes per the Catalogue populated.
• Format — conformance to the published schema (AIXM, ARINC 424, DO-272, etc.).

Performance Objectives#

A Performance Objective (PO) is a stated, measurable improvement in one or more KPAs that an AIM service commits to pursue. Examples (illustrative, in the GANP Portal style):

• PO — Improve aeronautical data integrity. Measured by the rate of data integrity events per 10^6 records, by class. Delivered by DAIM-B0 (QMS, CRC), DAIM-B1 (AIXM 5 with integrity classification), DO-200B-compliant downstream processing.
• PO — Improve aeronautical data timeliness. Measured by AIRAC on-time publication, time-to-publish for safety-significant changes, NOTAM lead time. Delivered by digital publishing toolchains (DAIM-B1) and digital NOTAM (DAIM-B2).
• PO — Improve cross-State interoperability of AIM data. Measured by AIXM semantic conformance, share of SWIM-distributed AIM, number of bilateral digital NOTAM exchanges active. Delivered by DAIM-B1/B2 with SWIM-B1.
• PO — Reduce cost per published change. Measured by cost per AIRAC amendment; share of changes published from a single data store without manual re-keying. Delivered by integrated AIM publishing (DAIM-B1).
• PO — Improve briefing utility. Measured by completeness of PIB content, share of integrated AIM/MET briefing in self-briefing, user-survey scores. Delivered by integrated AIM/MET services (DAIM-B2 with AMET-B1).

Key Performance Indicators#

KPIs that an AIS/AIM provider should track:

Data quality KPIs#

• WGS-84 conformance percentage of all published coordinates.
• Catalogue completeness percentage (data elements with all required attributes populated).
• Critical-data integrity event rate per 10^6 records, with target consistent with the 1 x 10^-8 corruption probability.
• CRC coverage of Essential and Critical data through the chain.
• Originator-confirmed correctness rate at issue (NOTAM and AIP).

Timeliness KPIs#

• AIRAC on-time publication rate.
• Median and 95th-percentile time-to-publish for safety-significant changes.
• NOTAM lead time distribution (issue time vs. event start time).
• Median age of published data per dataset.

Distribution KPIs#

• AIP availability (electronic and paper, percentage of intended recipients reached on time).
• SWIM AIM service availability and latency.
• Digital NOTAM share of total NOTAM issued.
• Number of SWIM AIM consumers (internal and external).

Process and compliance KPIs#

• QMS audit pass rate; non-conformity closure time.
• Number of formal arrangements active with originators; coverage of Catalogue elements by formal arrangement.
• DO-200B / ED-76A process compliance for FMS data supply.
• Cyber security incidents on AIM services per period.

User experience KPIs#

• PIB integrated AIM/MET share.
• User-survey scores for briefing services and self-briefing portals.
• Time spent per pre-flight briefing (efficiency proxy).

How AIM performance is reported#

• Globally — through ICAO ASBU implementation monitoring under the GANP review cycle; AIS-AIM Implementation Task Force reports.
• Regionally — APAC (APANPIRG and the Seamless ATM Plan AIM section), MID (MIDANPIRG), EUR (EUROCONTROL Performance Review Body and LSSIP).
• Nationally — State Safety Programme reports for AIM-related occurrences; CAA oversight reports against Annex 15 / PANS-AIM compliance.

Why this matters for planning#

Tying every AIM service to a Performance Objective and KPIs keeps AIM modernization honest. It forces the question "what measurable problem does this fix?" — particularly important when AIM investment competes with more visible operational programmes. It also gives oversight bodies the language to confirm that a deployed AIM platform is delivering measurable improvement in data integrity, timeliness, and interoperability, not merely producing nicer-looking AIPs.

Three timelines to keep distinct#

When discussing AIM "dates", separate three things:

1. Annex 15 amendment timeline — when ICAO updated the SARPs that govern AIS/AIM.
2. AIM doctrine timeline — when the AIS-to-AIM concept and the PANS-AIM document were published.
3. DAIM (ASBU) availability timeline — the notional Block dates from which DAIM modules become globally implementable.

A State's own AIM implementation roadmap is a fourth, national timeline; it must be expressed against the regional plan's milestones (APAC Seamless ATM Plan, MID Air Navigation Strategy, European ATM Master Plan).

Annex 15 amendment history (selected)#

Annex 15 has been amended through approximately 41 amendments since its first edition. Highlights relevant to the AIS-to-AIM transition:

The 2018 split between Annex 15 and Doc 10066 is the inflection point. Before that, both SARPs and detailed procedures were in Annex 15; afterwards, Annex 15 carries the obligations and Doc 10066 carries the how-to.

AIM doctrine timeline#

DAIM availability timeline (ASBU Blocks)#

The DAIM thread maps to ASBU Block availability dates set in GANP 5th edition and carried forward:

DAIM-B0 ........ from 2013   Quality-managed digital AIS, electronic AIP
DAIM-B1 ........ from 2019   Full Digital AIM, AIXM 5 data products
DAIM-B2 ........ from 2025   SWIM-distributed AIM, digital NOTAM
DAIM-B3 ........ from 2031   Trajectory-aware, semantically interoperable AIM

Visualised:

2013 ----- 2019 ----- 2025 ----- 2031 ----- 2037
  |          |          |          |
  DAIM-B0    DAIM-B1    DAIM-B2    DAIM-B3
  Digital    Full AIM   SWIM AIM   Semantic
  AIS        AIXM 5     digital    interop,
  baseline              NOTAM      TBO-aware

These dates are not deadlines for States. They are notional global availability dates from which the SARPs, PANS, technology, and training material are mature enough that any State can implement.

Where APAC States typically sit on this timeline#

Indicative regional context (verify current status against the latest APANPIRG and ICAO APAC AIM reports — these change annually):

• DAIM-B0 — substantially complete or in late-stage closure across the region. Common gaps: WGS-84 closure at smaller aerodromes; partial QMS certification; eTOD beyond Areas 1–2.
• DAIM-B1 — active implementation. Priority items in APAC: AIXM 5 publishing toolchains, AMDB at international aerodromes, IFP coded data set, integrated digital publishing.
• DAIM-B2 — early implementation. Initial AIM SWIM services, digital NOTAM trials with partner States, integrated AIM/MET briefing.
• DAIM-B3 — horizon planning, contingent on TBO maturity in the region.

Implementation monitoring cadence#

• Global — ICAO publishes ASBU implementation status as input to the GANP review cycle (3-yearly, aligned with the ICAO Assembly). AIM implementation reported through the AIM Panel.
• APAC — the APAC Seamless ATM Plan AIM section is the regional roadmap; APANPIRG monitors progress annually.
• EUR — the LSSIP cycle reports annually against ICAO AIM and the European ATM Master Plan AIM/SWIM elements.
• National — typically a 3–5 year national AIM implementation plan, reviewed annually, expressed in DAIM module terms.

How to read a date in an AIM document#

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

• "Annex 15 Amendment 40, applicable 8 November 2018" — SARP applicability date (binding on Contracting States).
• "PANS-AIM applicable 8 November 2018" — procedure applicability date.
• "AIRAC effective date 12 February 2026" — operational change effective date on the global AIRAC calendar.
• "DAIM-B1 from 2019" — Block availability date (global notional earliest).
• "Implemented by 2027" — national or regional commitment.
• "GANP 7th edition (2022)" — ICAO publication date.

Mixing these up leads to false claims that a State is "behind" or "ahead" of AIM, when the only meaningful measure is the State's own implementation plan against its declared milestones.

Primary ICAO documents#

• Annex 15 — Aeronautical Information Services, 16th edition (incorporating Amendment 40, applicable 8 November 2018, and subsequent amendments). The SARPs that govern State responsibilities, AIS/AIM functions, data quality, scope of data, aeronautical information products, and AIRAC.
• Doc 10066 — PANS-AIM (Procedures for Air Navigation Services — Aeronautical Information Management), first edition published 2018. Specifies detailed procedures for collection, processing, quality control, distribution, data integrity monitoring, and assurance. Appendix 1 is the Aeronautical Data Catalogue.
• Doc 8126 — Aeronautical Information Services Manual (current edition). Guidance material explaining how to implement Annex 15 and PANS-AIM, organised in four parts covering the regulatory framework, processing aeronautical data, products and services, and the transition to a SWIM-enabled environment. Part I, Chapter 1 frames the AIS-to-AIM transition.
• Doc 9750 — Global Air Navigation Plan (GANP), 5th to 7th editions. Defines the DAIM thread within ASBU. 5th edition PDF (mirror): https://www.iata.org/contentassets/1be2bec28b3d45f9ae7780d6ebea7be9/icao_ganp_doc209750_5ed_en.pdf
• Doc 9854 — Global Air Traffic Management Operational Concept. Source of the eleven Key Performance Areas referenced by AIM performance objectives.
• Doc 9883 — Manual on Global Performance of the Air Navigation System. Performance management methodology used to justify and measure AIM modernization.
• Doc 9839 — Manual on the Quality Management System for Aeronautical Information Services / Management. ISO-9001-aligned QMS implementation guidance for AIS/AIM providers.
• Doc 9674 — World Geodetic System — 1984 (WGS-84) Manual. Common geodetic reference for all published coordinates.
• Doc 10039 — Manual on System Wide Information Management (SWIM) Concept. Defines services, governance, and security for SWIM-distributed AIM.
• Doc 9881 — Guidelines for Electronic Terrain, Obstacle and Aerodrome Mapping Information. Technical guidance for eTOD and AMDB.
• Doc 9906 — Quality Assurance Manual for Flight Procedure Design. Multi-volume; the flight-procedure-design end of the AIM data chain.
• Doc 8168 — PANS-OPS. Procedure design rules — the upstream originator for IFP data.
• Doc 4444 — PANS-ATM. Air traffic services procedures referencing AIRAC and NOTAM.
• Doc 10157 — PANS-MET. Meteorological information procedures aligned with IWXXM.
• Doc 9082 — Policies on Charges for Airports and Air Navigation Services. Charging-policy basis for AIM services to operators.

Annexes most touched by AIM#

• Annex 1 (Personnel Licensing) — AIM officer endorsements where applied.
• Annex 3 (Meteorological Service) — convergence point for integrated AIM/MET.
• Annex 4 (Aeronautical Charts) — chart series consuming AIM data.
• Annex 11 (Air Traffic Services) — airspace and route data originated for AIM.
• Annex 14 (Aerodromes) — aerodrome physical data, AMDB inputs.
• Annex 15 (Aeronautical Information Services) — primary SARP.
• Annex 17 (Security) — where information sharing introduces security considerations.
• Annex 19 (Safety Management) — SMS integration of AIM service provision.

Industry and regional standards#

• AIXM (Aeronautical Information Exchange Model) — joint EUROCONTROL / FAA reference: https://www.aixm.aero/
• EUROCAE ED-77 / RTCA DO-201A — Standards for aeronautical information data.
• EUROCAE ED-76A / RTCA DO-200B — Standards for processing aeronautical data (data process assurance for FMS data supply).
• EUROCAE ED-99 / RTCA DO-272 — Aerodrome Mapping Data Base.
• ARINC 424 — Navigation system database standard.
• ISO 9001 — generic Quality Management System (basis for Doc 9839).
• ISO 19101 / 19115 / 19131 — geographic information, metadata, and data product specifications.

Live and authoritative external sources#

• ICAO GANP Portal — https://ganpportal.icao.int/ — live home of the ASBU framework, including the DAIM thread.
• ICAO AIM information page — https://www.icao.int/safety/information-management
• ICAO eAIP Specification reference — EUROCONTROL eAIP specification: https://www.eurocontrol.int/publication/eurocontrol-specification-electronic-aeronautical-information-publication-eaip
• EUROCONTROL AIM portal — https://www.eurocontrol.int/aeronautical-information-management
• AIXM site — https://www.aixm.aero/
• AIXM 5.1 / 5.1.1 documentation — https://aixm.aero/page/aixm-51-and-511
• IWXXM — https://schemas.wmo.int/iwxxm/

Regional implementation references#

• APAC Seamless ATM Plan (ICAO Asia/Pacific Regional Office) — AIM section; monitored by APANPIRG.
• MID Air Navigation Strategy (ICAO MID Regional Office) — AIM and SWIM elements; monitored by MIDANPIRG.
• European ATM Master Plan (SESAR JU) and EUROCONTROL LSSIP cycle — European AIM/SWIM implementation reporting.
• EUROCONTROL European AIS Database (EAD) — https://www.eurocontrol.int/service/european-ais-database

Authoritative sources noted but not in the local library#

• ICAO AIS-to-AIM Roadmap, 2008 edition (authoritative source — not in local library).
• ICAO AIM Panel working papers on digital NOTAM and SWIM-based AIM (authoritative source — not in local library).
• EUROCONTROL Specification for Aeronautical Information Exchange Model (AIXM) data quality requirements (authoritative source — not in local library).
• FAA System Wide Information Management Implementation reports (authoritative source — not in local library).