S1000D Data Modules: Structure, Identity, Status and Content
A Data Module is a controlled technical-information unit with identity, status and content. Its boundary should be clear enough to review, reuse, version and publish independently.
What is inside a Data Module?
| Area | Purpose | Typical project question |
|---|---|---|
| Identification | DMC and title-related identity information. | Can the module be uniquely located and referenced? |
| Status and management | Version, state, security, applicability and lifecycle information. | Which revision is approved for which configuration? |
| Common structure | Shared metadata and reusable structural elements. | Does the module follow the adopted Schema and rules? |
| Information content | Description, procedure, fault isolation, parts or other information. | Is the technical information complete and executable? |
Choose the boundary by information purpose
A procedure should contain a coherent task and its prerequisites, warnings, tools and completion checks. A fault-isolation module should preserve the diagnostic path and reference the repair action. A description module should explain a stable technical subject that can be reused without copying it into every task.
Data Module review checklist
- Identity matches the approved DMC and title.
- Status, version and applicability are complete.
- References, media and code values resolve correctly.
- Schema and BREX checks pass.
- Technical reviewers confirm safety, sequence and terminology.
Continue with DMC, CSDB and validation to connect module content with project control.
Frequently asked questions
Is a Data Module the same as a whole manual?
No. A Data Module is a controlled unit that can be reused and assembled into one or more publications.
Are Data Module tags identical in every project?
No. The adopted Issue, module type, schemas, data dictionary and project rules determine the permitted structure.