Video tutorials, guides, and deep dives into SWIM implementation
Step-by-step video guides demonstrating how to deploy, configure, and explore the SWIM Developer components on Kubernetes.
How to install and configure the SWIM Kubernetes Operator
Step-by-step guide to deploy the Consumer Validator on your Kubernetes cluster
Walkthrough of the Consumer Validator component that simulates an AISP provider
How to deploy and configure the DNOTAM Consumer module
Walkthrough of the Consumer module that processes DNOTAM events
How to deploy and configure the DNOTAM Provider module
Walkthrough of the Provider module that publishes DNOTAM events
How to deploy and configure the Provider Validator for testing
End-to-end test demonstrating the complete DNOTAM flow
SWIM represents a paradigm shift from point-to-point connections to a service-oriented ecosystem where aviation information flows seamlessly between all stakeholders.
The International Civil Aviation Organization mandates SWIM adoption by 2026. All Air Navigation Service Providers must implement standardized data exchange.
SWIM covers multiple domains: Aeronautical (DNOTAM, AIFS, AMAP), Meteorological (IWXXM), Flight (FIXM), and Surveillance.
SWIM mandates strong security with EACP PKI certificates, mutual TLS (mTLS), and comprehensive audit logging for all transactions.
Standardized protocols (AMQP, REST) and data models (AIXM, FIXM, IWXXM) ensure seamless communication between disparate systems globally.
SWIM implementation requires expertise across multiple technology domains. Our components handle this complexity so you can focus on your mission.
SWIM is fundamentally SOA-based. Services are published, discovered, and consumed through standardized interfaces. Our components implement proper service boundaries, contract-first design, and loose coupling. Request/Reply patterns use REST with OpenAPI specifications, compliant endpoints with proper content negotiation, error handling, and patterns as defined by the SWIM-TI Yellow Profile (EUROCONTROL SPEC-170).
EACP (European Aviation Common PKI) mandates X.509 certificates for authentication. We handle certificate lifecycle, full certificate chain validation (not just CA trust), and mutual TLS configuration with automated rotation.
The Yellow Profile mandates AMQP 1.0 for publish/subscribe patterns with external SWIM network. Kafka handles internal event streaming and module integration. We provide pre-configured brokers, topic management, subscription lifecycle, and delivery guarantees with proper security bindings.
Aviation data uses complex XML schemas (AIXM 5.1.1, Event, GML). We provide JAXB bindings, XSD validation, and pluggable business rules engines (Schematron, SBVR-based, or equivalent). JSON is supported for lightweight integrations.
Cloud-native design with containerized microservices. Each component is independently deployable, scalable, and observable. Native images for minimal footprint and fast startup. Day-2 operations automated through Kubernetes Operators. Deploy complex SWIM stacks with a single Custom Resource. Reconciliation ensures desired state is maintained.
Aviation demands reliability. Our components implement circuit breakers, retry policies, dead letter queues, idempotent consumers, and graceful degradation for mission-critical operations. Full observability stack: Prometheus metrics, distributed tracing with OpenTelemetry, and centralized logging. Pre-built Grafana dashboards for operational visibility.
Check out our open source projects or dive into the framework architecture