FR

What is S1000D?

The international specification for technical publications, in plain words: data modules, data module codes, the CSDB, BREX, and when a program needs it.

Short answer: S1000D is an international specification for producing technical publications, such as maintenance, operating and parts manuals, from small, reusable units of XML content called data modules. Every data module has a unique data module code and lives in a common source database (CSDB), from which publications are assembled for print, PDF or interactive viewers. Born in European military aerospace, it is now required on many aerospace and defense programs and used for land, sea and other complex equipment.

Where S1000D comes from

S1000D was started in the 1980s by the European aerospace industry association, today ASD, to manage the documentation of military aircraft. The first issue was published in 1989. It is now maintained by the S1000D Steering Committee, whose members include ASD, the Aerospace Industries Association (AIA) in the United States and the ATA e-Business Program of Airlines for America, alongside national defense and industry representatives.

The specification is published in numbered issues and can be downloaded free of charge from s1000d.org. Issue 7, the latest, came out in 2026, after Issue 6 in 2024 and Issue 5.0 in 2019. A program normally stays on the issue named in its contract, which is why Issue 4.x data is still common on long-running programs.

Data modules: write once, publish many times

A data module is the smallest self-contained unit of information in S1000D: the description of a hydraulic pump, the procedure to remove it, the list of its parts. It is written once and reused in every publication that needs it, so a change is made in one place.

S1000D defines a schema for each kind of information. The most common are:

A publication module then sets out which data modules make up a publication, and in what order.

How a data module code works

Every data module is identified by a data module code (DMC) that describes the product, the part of the product and the kind of information the module holds. An illustrative code for the removal procedure of a pump:

DMC-CP200-A-29-10-00-00A-520A-A

The segments of an S1000D data module code, with an illustrative example
Segment In the example What it says
Model identification codeCP200The product or project.
System difference codeAWhich variant of the system.
Standard numbering system29-10-00The system, subsystem and unit. Air vehicles often follow the ATA chapter numbering.
Disassembly code and variant00AThe level of breakdown of the item.
Information code and variant520AThe kind of information: 520 is a removal procedure, 720 an installation, 040 a description and 941 illustrated parts data.
Item location codeAWhere the work is done: A means the item is installed on the product.

CSDB, BREX, applicability and IETP

When S1000D is worth it

S1000D pays off when a contract requires it, when many product variants share the same content, and when the documentation must live as long as the equipment, often for decades. It takes real effort: business rules to define, a CSDB to run, authors to train and legacy manuals to convert.

That conversion is where most suppliers start. Their manuals exist in Word or PDF, with descriptions and procedures mixed on the same page. Splitting that content into data modules, coding it and checking it against the project BREX is where the expert hours go.

From PDF manuals to S1000D data modules with TwinWorks

TwinWorks imports existing PDF or Word manuals, drafts modular content linked to its sources, and exports descriptive and procedural S1000D data modules once your experts have approved them. It does not claim S1000D or BREX conformance: validate the exported modules against your project BREX with your own tools. See how S1000D data module export works.

Choosing between a full S1000D suite and a lighter route? Read TwinWorks vs PTC Arbortext and TwinWorks vs Cortona3D RapidAuthor.

FAQ

Is S1000D free?

Yes. The specification can be downloaded free of charge from s1000d.org. The software used to author, manage and publish S1000D content is sold separately.

What is the difference between S1000D and DITA?

Both are XML standards for modular content. DITA is a general-purpose topic architecture, widely used for software and product documentation. S1000D is a specification for the technical publications of complex equipment, with data module codes, applicability, a common source database and project business rules built in. Aerospace and defense contracts usually name S1000D.

What is a BREX in S1000D?

A business rules exchange (BREX) data module records a project’s S1000D business rules in machine-readable form, so data modules can be checked against them automatically before delivery.

Which S1000D issue should I use?

The one your contract or customer names. Programs usually stay on the issue they started with, while new programs often choose a recent issue. Check with your customer before converting any content.

Does TwinWorks export S1000D data modules?

Yes. TwinWorks exports descriptive and procedural S1000D data modules from content your experts have approved. It does not claim S1000D or BREX conformance, so validate the exported modules against your project BREX with your own tools.

Related terms and pages

Turn one manual chapter into data modules

Import a PDF or Word manual and see the modular draft TwinWorks prepares for your experts to review, approve and export.

Start free See S1000D data module export