Aerospace & Defense CCMS

The structural problem

Source-of-truth content scattered across the supply chain

The same authoritative paragraph travels across many audiences and formats. A safety procedure ends up in a maintenance manual, a training pack, an operator handbook and a regulator submission, sometimes in three languages and two classification levels.

When the source lives in documents rather than components, every downstream variant is a separate maintenance liability. The cost stays invisible until a regulator notes the inconsistency, or an operator reads the wrong version.

Regulatory landscape by region

The standards differ by jurisdiction. The expectation is the same

When content moves between a defense prime and its subcontractors, between a regulator and the operators it oversees, or between national authorities and NATO allies, the provenance has to move with it. The frameworks below differ on what they prescribe; all assume content can be tracked at the fragment level.

North America

US · Canada

ITAR, International Traffic in Arms Regulations. US export control over defense articles and technical data, with implications for who can access content and where it is stored.
MIL-STD publications: DoD military standards covering documentation, materials, processes, and contract deliverables.
DFARS, Defense Federal Acquisition Regulation Supplement. Contract clauses prescribing data-handling and reporting requirements for DoD suppliers.
NIST SP 800-171, Controlled Unclassified Information handling. Required for any DoD-adjacent contractor or sub-tier supplier.
FAA Part 25 / Part 23, civil aviation airworthiness standards for transport and small-airplane categories.

Western Europe

EU institutions · FR · BE · NL · IT · ES · PT

EASA Easy Access Rules, European aviation regulatory framework. Published from DitaExchange since February 2018.
EDA capability frameworks, European Defence Agency coordination of capability development across member states.
EU Defense Fund, cooperative research and capability projects across member-state defense ministries.
National defense frameworks: French DGA, Dutch MoD, Italian Difesa, Spanish DGAM. Each maintains national procurement and documentation standards alongside EU-level coordination.

DACH

Germany · Austria · Switzerland

BAAINBw, German Federal Office of Bundeswehr Equipment, Information Technology and In-Service Support. Central procurement and lifecycle-support authority.
armasuisse, Swiss Federal Office for Defence Procurement. Independent of EU/NATO frameworks but interoperable with both.
BAFA, German Federal Office for Economic Affairs and Export Control. Defense-related export licensing.
LBA / FOCA, German Luftfahrt-Bundesamt and Swiss Federal Office of Civil Aviation. National civil-aviation authorities coordinating with EASA.

UK & Nordics

UK · DK · NO · SE · FI

UK MoD JSP, Joint Service Publications. UK Ministry of Defence procedural and documentation standards.
NATO STANAG, Standardization Agreements. Widely adopted across UK and Nordic NATO members (NO, DK, FI, SE, all five in the alliance since Sweden joined in March 2024).
NORDEFCO, Nordic Defense Cooperation. Coordination framework across Nordic defense ministries.
UK CAA, UK Civil Aviation Authority. Post-Brexit divergence from EASA on some airworthiness paths; broadly aligned on technical standards.

How DitaExchange addresses it

Component control across the supply chain

DitaExchange manages content as DITA components inside Microsoft SharePoint: SharePoint Online in your Microsoft 365 subscription, or SharePoint Server on-premise. The specialist authors who quietly abandon XML editors after eighteen months apply as much to S1000D author populations as to anyone else, which is why the Word-as-authoring-surface choice is load-bearing.

What changes	How
The authoritative paragraph becomes the unit of management	Each approved fragment carries its own version and approval record, independent of the manuals, packs and submissions that reference it.
Downstream variants stop being separate liabilities	Conditional profiling emits airframe, operator, language and classification variants at publish time from one approved source.
Engineers and regulatory specialists stay in Microsoft Word	Structure is applied behind the scenes. No new authoring tool, and no second classification environment to accept.
Controlled language is enforced, not retrofitted	ASD-STE100 and equivalent rule sets run inside the editor via DxChecker, so defects are caught at authoring rather than in review.
ITAR, DFARS and NATO classification stay where IT already handles them	The SharePoint substrate carries data residency, classification and access control with the controls the customer's IT department already operates.

In production

The content domains already running on Dx5

The content domains DitaExchange has handled in production with aerospace and defense customers, from regulator rule corpora to supplier statements of work.

Regulatory rule sets

Airworthiness rules and the consolidated formats built from them are published by the regulators who own them, and consumed downstream by the primes and operators who have to comply. The publishing side of that chain sits under government and regulators.

Aerospace technical documentation

Maintenance manuals, training documentation, operator handbooks. Component-level reuse across airframe variants and operator configurations.

Continuing airworthiness records

Service bulletins, airworthiness directives, type-certificate data sheets. Long-lifecycle records reused across the operator base.

Defense-procurement specifications

Capability documents, requirement statements, supplier statements of work. Versioned and traceable across multi-year programs.

Cross-agency capability frameworks

Coordination documents shared across member-state defense ministries, with classification and access control enforced at the SharePoint layer.

No parallel infrastructure decision, and no second classification regime to maintain.

By function

Who this lands on in a prime, an agency or a regulator

Technical Publications

Owns the manual portfolio and the translation budget. Reuse rate sits in front of every term in that equation.

Regulatory Affairs

Answers to EASA, national authorities and customer airworthiness audits. Component-level approval makes the compliance trail a query rather than a reconstruction.

Quality & QMS

AS9100 derivatives, NATO STANAG quality clauses and MIL-STD documentation requirements, with change-control at the fragment.

CIO & IT leadership

SharePoint handles data residency, classification and air-gapped deployment with controls IT already operates.

A rule corpus or a manual family usually touches all four. The component model is what lets them work from the same approved source.

In production with

Lockheed Martin

US defense prime contractor; new DitaExchange customer (2025).

GKN Fokker

GKN Aerospace division (Netherlands). Technical documentation across the aerospace supply chain.

Frequently asked questions

UK Ministry of Defence Joint Service Publications and NATO STANAG quality clauses both bite on documentation. Which one decides the tooling?

Neither. JSPs set procedural and documentation standards, STANAG clauses set the interoperability bar, and both leave the system open. What they assume is that provenance travels with the content as it moves between a prime, its subcontractors and the customer nation. The deciding question is therefore the granularity of the approval record, not which badge the platform carries.

A capability document is agreed across member states and each adds national annexes. Where does that content sit?

In one approved core, with the national material profiled onto it, so shared text is not maintained five times over. The European Defence Agency coordinates capability work of this shape on the platform. What matters in a multi-nation program is not the publishing step. It is that a change to the shared text cannot quietly miss one nation's version.

NIST SP 800-171 governs how we handle controlled unclassified information. Does a content layer widen the assessment?

It should not add a platform to it. Components live in the SharePoint estate that has already been assessed, so the controls being evidenced are the ones in force there and no second accreditation perimeter is stood up. What does change is how many people hold access to fragments of a technical data package, which is an access review on an estate you already govern rather than a new platform decision.

A subcontractor has to work from our approved maintenance content but will not sit inside our systems. What do they get?

The deliverable, not the repository. Approved components publish as Word, HTML or XML outputs, so the supplier receives the artifact the contract calls for while the source stays under the controls that govern it. When the content changes, the change is made once, on the component the deliverable was built from, and the next issue carries it without a reconciliation pass.

Our contractual deliverable is S1000D. Is a DITA CCMS the right purchase?

Be precise about the requirement. Where the deliverable is governed by S1000D, Contiem notusCSDB is purpose-built for that standard and is the honest recommendation. DitaExchange is DITA-native. Where the content is DITA-based airworthiness, technical-manual or procurement material and the priority is keeping it inside an existing Microsoft estate, it fits, and Lockheed Martin and GKN Fokker run it on the manufacturing side. Strictly S1000D, weight Contiem.

What to read next

Industries

A regulation is a content product. Treat it like one