The question behind the question
When regulators and industry partners ask whether a Discovery and Synchronisation Service (DSS) can be certified, they are rarely asking about a single software component. They are asking whether federated airspace data exchange — the backbone that lets U-space Service Providers find each other, share flight intentions, and stay synchronised in real time — can be trusted at the level of safety criticality that ATM has taken for granted for decades.
Certification applies to systems, not acronyms
There is no certificate labelled "DSS". What can be certified is a system built and operated to a defined intended use, with a documented development process, verifiable requirements, and evidence that the artefact does what it claims. In practice that means:
- Requirements traceability — from operational concept through software requirements to test evidence, modelled on DO-178C-style objectives proportionate to the assurance level
- Interface control — unambiguous ICDs for the discovery and synchronisation protocols, aligned with ASTM F3411/F3548 and the U-space regulatory framework (EU 2021/664 and its implementing regulations)
- Deterministic behaviour under failure — documented fault detection, latency bounds, and integrity guarantees for cross-USSP data exchange
- Validation in representative conditions — not just unit tests, but multi-USSP scenarios, degraded modes, and near-operational trials
What the framework already gives us
The U-space package does not certify services directly — it requires Member States and the competent authorities to accept service providers against a compliance framework. But the direction of travel is clear: authorities expect evidence of software integrity, interoperability conformity, and robust information security (increasingly, Part-IS style expectations). Standards such as ASTM F3411 (Remote ID), F3548 (strategic conflict management) and the EUROCONTROL SWIM guidance give us the normative anchors to build against.
Our position
At PANKA we develop the DSS with certification readiness from day one: a V-model development process, controlled requirements and interface baselines, and validation milestones that mirror how safety-critical ATM software is qualified. Federated architecture makes this easier, not harder — bounded responsibilities per instance, clear contracts between nodes, and failure domains that can be reasoned about.
So — can DSS be certified? The honest answer: a DSS can be built certifiable, and the infrastructure to assess it is maturing fast. The organisations that start collecting development and validation evidence now will be the ones whose services authorities accept first.
Working on U-space infrastructure and thinking about assurance? We are open to collaboration on validation and interoperability — reach out at info@panka.pl.