Overview
Originating AIXM is hard to get right: changes must follow the AIXM temporality model, reference existing features correctly, carry precisely calculated geometry and often produce NOTAM text as well. The AIXM Origination Components package this knowledge into reusable parts. Your developers describe what to originate in templates and assemble the user interface from tested components; the components take care of how the AIXM is produced.
- Template-Driven: new scenarios and feature types are added as templates, not code.
- Modular: use only the engine, add the runtime, or build complete applications from the components.
- Host Independent: components fit into your application, your styling and your authentication.
- Same Results Everywhere: the engine produces identical AIXM in the browser and on the server.
See the use cases on the AIXM Software Development Kit page for typical combinations.
AIXM Origination Engine
Template-Driven AIXM Change Generator
The heart of the AIXM Origination Components. The AIXM Origination Engine takes an origination template and the user's inputs, evaluates them against the baseline dataset and produces a validated AIXM change set, ready to export as an AIXM message.
- Written in Kotlin Multiplatform: runs in the browser and on the JVM for server-side and batch generation
- Works as an extension of an AIXM Reader session: reads the baseline, evaluates the template and executes the change as one transaction
- Supports AIXM 5.1, 5.1.1 and 5.2 templates, including extensions such as the AIXM Event extension for Digital NOTAM
- Resolves derived inputs such as affected FIRs, identifiers and default values
- Generates new TimeSlices, replacements and cancellations according to the AIXM temporality rules
- Produces NOTAM and SNOWTAM content for Digital NOTAM events, including Item Q, Item D schedules and NOTAM numbering
- Detailed diagnostics for every input and every generated feature
- Event lifecycle support: updates, early end and cancellation of published events
- Templates verified against reference outputs to guarantee stable results
Origination Runtime
Headless Origination Logic
The runtime connects templates, data and the engine, without any user interface. Use it behind your own screens or together with the user interface components.
- Template catalogues: loading, filtering and selecting templates from versioned catalogues
- Input resolution: required and conditional inputs, derived values and readiness checks
- Dataset binding: reference lookups and feature data from the baseline through the standard Reader API
- Change generation: grouping of changes, materialisation of AIXM and XML download
- Event lifecycle and publication: proposal states, publication records and lifecycle operations for Digital NOTAM events
Form Components
Low-level React components for building input forms that understand AIXM. They are used inside the origination input form, and can equally be placed in your own forms.
AIXM Reference Lookup
Search and select referenced features such as airports, runways, airspaces or navaids from the baseline, with filtering, advanced lookup and automatic selection when only one feature matches.
Geometry Input
Typed entry of points, lines, polygons and circles in DD and DMS formats, with geodesic arcs, radii, state border segments, live validation and format help.
Schedule Entry
Entry of AIXM timesheet schedules as text or in a calendar view, including weekdays, holidays and sunrise or sunset times, rendered back as AIXM and readable text.
Derived Value Proposals
Present values proposed by the engine, such as affected FIRs or vertical limits, for the user to accept or override.
AIXM Value Editors
Field editors for values with units of measure, code lists including OTHER values, nil reasons, validity periods and translated notes.
Dataset and Effective Date Picker
Select the baseline dataset, airport and effective date that the origination works against.
Application Components
Higher-level components that combine the form components, the map and the runtime into complete building blocks of an origination application.
Origination Input Form
A complete form generated from any template: sections, required and conditional fields, references, geometry, schedules and derived value proposals, with validation messages shown in place.
Template Catalogue
A searchable catalogue of available templates, grouped by category, with detailed, compact and list views, favourites and a quick picker for the map toolbar.
Map Capture and Editing
Origination maps built on the map platform: baseline and workspace layers, drawing of points, lines, polygons and circles synchronised with the form, snapping, move, rotate and scale, undo and redo, selection of referenced features on the map, and assignment of imported GIS shapes to template fields.
Workspace Controls
Everything needed for project-based tools: creating, opening, saving and exchanging workspaces, workspace properties and menus, and a feature browser listing all changes in the workspace with their status.
NOTAM and SNOWTAM Preview
Formatted preview of the NOTAM and SNOWTAM messages generated for an event, with the NOTAM header, Q line and Items A to G, updated live as the form changes.
Event Components
Components for event-based applications such as Digital NOTAM: event list and calendar, time window and "active at" selection, proposal and approval workflow, publication dialog, lifecycle dialog for updating or cancelling events, and event history.
Advanced AIXM Editor
For expert users: direct editing of any AIXM feature and property, TimeSlice operations such as correction, cancellation and withdrawal, XML preview and comparison with the baseline.
Template Studio
Origination Template Editor
Template Studio is the authoring environment for origination templates. Use it to adapt our templates to local rules or to create templates for entirely new scenarios and feature types.
- Define template inputs, sections, conditions and validation rules
- Map inputs to AIXM features, properties and geometry
- Configure lifecycle forms and NOTAM production rules
- Preview the generated form and the resulting AIXM output side by side, using the engine
- Store expected outputs and validate whole template sets in batch, to catch regressions before deployment
- Publish versioned template catalogues that applications load without being rebuilt
Template Packages
Ready-made, versioned template catalogues give you a head start:
- Digital NOTAM: all EUROCONTROL Digital NOTAM Event Specification 2.0 scenarios, with simplified variants and SNOWTAM.
- AMDB: airports, runways and runway, taxiway and apron elements.
- AIP Data: navaids such as VOR, DME, NDB and ILS, designated points and route segments.
- Obstacles: point, line and polygon obstacles, including power lines.
Copyright
Annea s.r.o.