Open-source reference implementation of SWIM (System Wide Information Management) services for aviation, built on Red Hat OpenShift.

SWIM is a global ICAO mandate (EU Regulation 2021/116, CP1) requiring Air Navigation Service Providers to adopt standardized, service-oriented data exchange. This project provides production-ready components so that ANSPs, AISPs, integrators, regulators, and developers can deploy compliant SWIM services without vendor lock-in.

A framework, not a monolith. swim-developer is organized around a central idea: the infrastructure that every SWIM service needs (subscription lifecycle, AMQP messaging, heartbeat monitoring, self-healing) should be written once and shared, so that each new service only implements what is unique to its domain.

Six working services that demonstrate both sides of the SWIM exchange, Consumer and Provider, for three real-world use cases:

• DNOTAM (Digital NOTAM), aeronautical information using AIXM 5.1.1
• ED-254 (Arrival Sequence / AMAN), arrival management using FIXM 4.3
• FF-ICE (Flight Filing), flight and flow information using FIXM 4.3

Compliance validators that exercise the full AMQP subscription lifecycle against running instances, verifying SPEC-170 conformance.

Data models (AIXM 5.1.1, FIXM 4.3, FIXM FF-ICE) generated from the official XSD schemas, ready to use.

Maven archetypes that scaffold new consumer, provider, and data model projects in minutes.

Open standards deserve open implementations.

Visit swim-developer.github.io for full documentation, architecture details, and step-by-step tutorials.

This project implements the following standards. Each one shaped concrete design decisions, not aspirational references, but constraints the code was built to satisfy.

swim-developer follows Hexagonal Architecture (Ports and Adapters). The domain core defines contracts through SPIs; infrastructure adapters handle protocol-specific concerns without leaking into domain logic. This separation is what makes the framework reusable: a new SWIM service implements a small set of SPIs, and the framework provides everything else.

                    +----------------------------------+
                    |          Domain Core             |
                    |                                  |
                    |   SPIs (Ports):                  |
   Driving          |   . SwimEventExtractor<T>        |         Driven
   Adapters ------> |   . SwimOutboxRouter             | <------ Adapters
   (REST API,       |   . SwimPayloadValidator         |         (AMQP, Kafka,
    Scheduler)      |   . SwimSubscription<E>          |          MongoDB, PostgreSQL)
                    |   . SwimIngressHandler           |
                    |                                  |
                    +----------------------------------+

   Dependency Rule: Adapters depend on Core. Core depends on nothing.

For C4 diagrams, sequence diagrams, and architecture decision records, see the architecture documentation.

Consumer and Provider are separate products for different customers.

A Provider (AISP role) publishes aviation data to the SWIM network. A Consumer (ANSP role) subscribes to external providers to receive that data. They share the same framework, but they serve different organizations with different operational needs.

An ANSP's Consumer connects to external Providers (EUROCONTROL, Austro Control, LFV, and others). It never connects to its own Provider. This reflects the real-world architecture of SWIM, where data flows between organizations, not within them.

The framework supports multi-provider connections: a single Consumer can maintain simultaneous AMQP subscriptions to multiple external Providers.

The repositories are organized in layers. Build order matters: each layer depends on the ones above it.

JAXB bindings generated from official XSD schemas. Required by the services that use each standard.

Reusable infrastructure extracted from production services.

Six services across three SWIM use cases.

Test counterparts for each service. Consumer validators simulate external providers. Provider validators run conformance scenarios against live providers.

Scaffold new SWIM services in minutes.

Clone and install the shared dependencies first, then build the service you need.

Linux / macOS:

# 1. Parent POM
git clone https://github.com/swim-developer/swim-developer-root.git
cd swim-developer-root && ./mvnw clean install -DskipTests && cd ..

# 2. Data Models
git clone https://github.com/swim-developer/swim-aixm-model.git
cd swim-aixm-model && ./mvnw clean install -DskipTests && cd ..

git clone https://github.com/swim-developer/swim-fixm-model-ed254.git
cd swim-fixm-model-ed254 && ./mvnw clean install -DskipTests && cd ..

git clone https://github.com/swim-developer/swim-fixm-ffice-model.git
cd swim-fixm-ffice-model && ./mvnw clean install -DskipTests && cd ..

# 3. Framework
git clone https://github.com/swim-developer/swim-developer-framework.git
cd swim-developer-framework && ./mvnw clean install -DskipTests && cd ..

# 4. Extensions
git clone https://github.com/swim-developer/swim-developer-extensions.git
cd swim-developer-extensions && ./mvnw clean install -DskipTests && cd ..

# 5. Validators
git clone https://github.com/swim-developer/swim-developer-validators.git
cd swim-developer-validators && ./mvnw clean install -DskipTests && cd ..

# 6. Build the service you need (example: DNOTAM Consumer)
git clone https://github.com/swim-developer/swim-digital-notam-consumer.git
cd swim-digital-notam-consumer && mvn clean package -DskipTests

Windows (CMD or PowerShell):

rem 1. Parent POM
git clone https://github.com/swim-developer/swim-developer-root.git
cd swim-developer-root && mvnw.cmd clean install -DskipTests && cd ..

rem 2. Data Models
git clone https://github.com/swim-developer/swim-aixm-model.git
cd swim-aixm-model && mvnw.cmd clean install -DskipTests && cd ..

git clone https://github.com/swim-developer/swim-fixm-model-ed254.git
cd swim-fixm-model-ed254 && mvnw.cmd clean install -DskipTests && cd ..

git clone https://github.com/swim-developer/swim-fixm-ffice-model.git
cd swim-fixm-ffice-model && mvnw.cmd clean install -DskipTests && cd ..

rem 3. Framework
git clone https://github.com/swim-developer/swim-developer-framework.git
cd swim-developer-framework && mvnw.cmd clean install -DskipTests && cd ..

rem 4. Extensions
git clone https://github.com/swim-developer/swim-developer-extensions.git
cd swim-developer-extensions && mvnw.cmd clean install -DskipTests && cd ..

rem 5. Validators
git clone https://github.com/swim-developer/swim-developer-validators.git
cd swim-developer-validators && mvnw.cmd clean install -DskipTests && cd ..

rem 6. Build the service you need (example: DNOTAM Consumer)
git clone https://github.com/swim-developer/swim-digital-notam-consumer.git
cd swim-digital-notam-consumer && mvn clean package -DskipTests

Use the Maven archetypes to scaffold a complete project with hexagonal architecture. The Create Consumer and Create Provider tutorials walk through the full process step by step.

See the deployment tutorials for guided instructions covering OpenShift, Kubernetes, Minikube, OpenShift Local, Podman, and Java/binary deployments.

This project is an open invitation to the SWIM development community. Whether you are an ANSP evaluating SWIM adoption, a system integrator building SWIM services, a regulator assessing compliance, or a developer interested in aviation data exchange, contributions, feedback, and collaboration are welcome.

The framework was designed to be extended. If you are building a new SWIM service, the SPIs define the contracts your service needs to implement. The framework handles the rest.

All repositories are licensed under Apache License 2.0.