EASA
EU Aviation Safety Agency
European aviation regulations published on DitaExchange since February 2018, the platform behind the eRules program and the Easy Access Rules format.
Customers
The platform behind some of the most documentation-intensive regulatory work in Europe
In continuous production since 2018 across regulators, primes, manufacturers and capital-markets infrastructure. Each program is separate proof that the same Microsoft-native model works across sectors.
See all customers
- 10
- Customers in production
- 5
- Sectors in production
- 6
- Roles served
- 2018
- In production since
Featured customer
EASA, European aviation regulations on DitaExchange since 2018
The European Union Aviation Safety Agency adopted DitaExchange to power eRules, the platform that produces the Easy Access Rules format now used across European aviation. The first deliverable, Initial Airworthiness, went live in February 2018. The platform has been in continuous production use ever since.
The structural choice that made the implementation work: rule authors continue to draft in Microsoft Word. The DITA components and the SharePoint storage layer work behind the scenes. There is no separate XML editor for regulatory specialists to learn, and no parallel toolchain to maintain alongside the regulator's existing Microsoft estate. Every change, every approval and every version is captured at the component level, ready to be re-published to whichever audience or format needs it next.
The Easy Access Rules format itself (the consolidated, navigable view of European aviation regulations that operators, training organizations and manufacturers rely on) is produced from the same component library that the rule authors maintain. One source of truth, many published outputs, reaching more than 20,000 stakeholder companies across European aviation.
Customer since
Feb 2018
Authoring tool
Microsoft Word
Content store
SharePoint
Downstream reach
20,000+ companies
Customers in production
The organizations running DitaExchange today
Canadian Nuclear Safety Commission
The same architecture across six regulated sectors
Regulators, defense primes, manufacturers, energy operators and capital-markets infrastructure. The content problem is the same in each: approved content that has to stay consistent and be provable on demand.
Life Sciences
Regulatory submissions, labeling and clinical documentation, where the answer needs to be ready before the regulator asks for it.
Financial Services
Disclosures, policy documents and controlled publishing, with governance enforced in the workflow rather than described in a process document.
Aerospace & Defense
Airworthiness rules, technical manuals and defense-procurement specifications, multi-variant publications where reuse is the entire point.
Government & Regulators
Rulemaking, statutory instruments, guidance and consolidated law, amended continuously and cited by everyone downstream.
Nuclear & Energy
Reactor manuals, plant safety cases and decommissioning records, where the audit trail is itself the deliverable.
Technical Documentation
Modular content for product portfolios, where each new variant draws from the validated pool so the work stays incremental instead of duplicated.
What these customers have in common
Not a sector. Content whose inconsistency carries a regulatory, legal or financial cost, and an IT estate already standardized on Microsoft 365.
- Approved content reused across many documents and markets
- An audit or inspection that asks who approved which wording, and when
- Subject matter experts who author in Word, not in an XML editor
- SharePoint already cleared by IT for data residency and audit
Every customer in production, and what each one publishes
Regulators writing the rules, primes and manufacturers proving they complied with them, and market infrastructure publishing what it is obliged to disclose. Inside each program the same content passes through authors, reviewers, approvers and quality teams.
CNSC
CNSC
Canadian Nuclear Safety Commission
Federal regulator for Canadian nuclear energy and materials. Publishes Canadian nuclear safety regulations on DitaExchange.
Lockheed Martin
US defense prime
Defense prime contractor across air, space, missile and sensor systems. New DitaExchange customer in 2025.
European Defence Agency
EU defense coordination
EU agency coordinating defense-capability development. Military aviation rules managed on DitaExchange and shared across 25 EU member states.
GKN Fokker
Aerospace, Netherlands
GKN Aerospace division in the Netherlands. Rules for parts and components of military aircraft managed on DitaExchange.
LSEG
London Stock Exchange Group
Global financial-markets infrastructure operator. Documentation across regulatory, market-data and post-trade businesses runs on DitaExchange.
Grundfos
Pumps and water technology, Denmark
Danish global manufacturer of pumps and water-technology products. Product documentation across many product families and languages runs on DitaExchange.
MagVenture
Medical devices, Denmark
Danish medical-device manufacturer specializing in transcranial magnetic stimulation. Product documentation across regulatory submissions.
Frequently asked questions
Which of these customers are public authorities, and which are suppliers?
EASA, the Canadian Nuclear Safety Commission and the European Defence Agency are public bodies that publish the rules other organizations have to comply with. Lockheed Martin, GKN Fokker, Grundfos and MagVenture are manufacturers documenting what they build. LSEG and ICBC sit in financial-markets infrastructure. The regulator writes the rule and the supplier has to prove it followed it. Both ends of that chain run on the same component model.
Do all of these programs run the same deployment?
No. The product line covers SharePoint Online inside the customer's own Microsoft 365 subscription, national-cloud Microsoft 365, SharePoint Server 2019 and Subscription Edition on-premise, hybrid topologies, and air-gapped installations. In this customer set sovereign and on-premise requirements are normal rather than exceptional, and they are the reason a SaaS-only vendor is often ruled out before anyone has seen a demo.
What did these programs start from?
Existing documents. Content that already lives in Word or HTML has to become components before any of the reuse mechanics apply. DxMigrationTool reads Word, HTML, Markdown and plain-text files, captures metadata, aligns styling to the target model, repairs links and cross-references, and componentizes the result into DITA topics. Which document set goes first, and what the topic model looks like, are human decisions; the tool applies them.
Several of these customers publish in many languages. How is that handled?
A component is translated once in its approved form, and every document that references it picks up the translation. Dx5 produces per-language translation packages, and the work goes to whichever translation supplier the customer already uses. On an estate like Grundfos product documentation, spread across product families and languages, the saving comes from not paying to translate the same paragraph again in every manual that contains it.
Do we need a program this size to start?
No. Implementations begin with one document set, one editorial team, one SharePoint site, and grow with the content program from there. EASA's first deliverable was Initial Airworthiness, live in February 2018; the rest of the rule estate followed over the years after it. If the first phase cannot be named in one sentence, it is not a first phase yet.
Looking for a customer reference?
Where customers will speak on the record, we can arrange a reference call for serious evaluations. Most prefer to talk under NDA once an evaluation is underway.
