The data model
AIXM, and what AWM does with it
AIXM is the exchange model aeronautical information is published in — an agreed structure for aerodrome features and, critically, for how they change over time. A runway is not just a polygon; it is a polygon with a history, a baseline state and a set of temporary deviations from it.
That temporal model is the part that matters for works. A closure is not an edit to the map. It is a time-bounded deviation recorded against the feature it affects, which is why the same record can drive the map, the NOTAM and the audit trail without being retyped into three systems.
AWM holds that dataset and operates on it. What it does not do is become the airport's system of record for everything else — the boundary below is where that line sits.
One feature · TWY A
sequence 1 → 2 · one temporary change
- BASELINE 1.0 NORMAL · no centre line lighting
- PERMDELTA · closes 1.0, opens 2.0 — centre line lighting installed
- BASELINE 2.0 NORMAL · centre line lighting
- TEMPDELTA CLOSED
Snapshot at view time
SNAPSHOT = BASELINE + active TEMPDELTAs
| operationalStatus | NORMAL | BASELINE 1.0 |
| centreLineLighting | not installed | BASELINE 1.0 |
| operationalStatus | NORMAL | BASELINE 2.0 |
| centreLineLighting | installed | BASELINE 2.0 |
| operationalStatus | CLOSED | TEMPDELTA |
| centreLineLighting | installed | BASELINE 2.0 |
Illustration — not real UI
Who owns the data
How your map gets built
Three routes to the same dataset. Which one fits depends on what your GIS already does, not on how much of AWM you want.
-
Data as a Service
We build it. You get a total solution.
- Source of truth
- Maestranza
We survey, author and maintain your airside dataset. You get a working map and keep it current through us.
- Maestranza does
- Survey, authoring, maintenance and currency of the dataset.
- You do
- Supplies source material and approves changes.
Let's discuss whether AIXM compliance is required for your operation.
-
GIS-Driven Airport
You already have the GIS. Send it straight through.
- Source of truth
- The airport's GIS
Keep your GIS as source of truth and push the map to AWM through our seamless GIS plugin.
- Maestranza does
- Provides and supports the GIS plugin and the ingest.
- You do
- Maintains its GIS as it does today; changes flow through.
-
Full Self-Authoring
You own the whole chain. We give you the tools.
- Source of truth
- The airport
Build your own map and database with our GIS plugin and Data Originator — AIXM compliant end to end.
- Maestranza does
- Licenses the GIS plugin and Data Originator, and certifies output.
- You do
- Authors and maintains the dataset itself, end to end.
End to end
Source to output
The same dataset drives everything downstream. Nothing on the right is retyped from anything on the left.
Source data
- Survey
- CAD and design
- Airport GIS
- AIP and AIS
Airside Works Manager
Airside dataset — AIXM, with temporal history
Outputs
- Live operational map
- Digital NOTAM
- Works programme
- Evidence and audit export
Illustration — not real UI
Integration
Integration
What connects, in which direction, and how often. Anything not confirmed is marked rather than described plausibly.
- GIS plugin
- To confirm supported GIS platforms and versions
- Data Originator
- To confirm scope, licensing and certification model
- Supported inputs
- To confirm formats accepted, and by which route
- Supported outputs
- To confirm export formats, including the AIXM profile produced
- Refresh model
- To confirm push or pull, frequency, and conflict handling
- Identity
- To confirm SSO and access control integration