Glossary
This page defines the key S1000D terms used across this site. Each term has one short definition. Use it as a quick reference while you read the other pages.
Codes such as the DMC and the SNS are made of several fields. Each field has a fixed meaning. The example codes on this page (for example DMC-1B-... or the SNS 29-10-05) are illustrative; real values come from your project's business rules.
Terms
| Term | Stands for | One-sentence definition |
|---|---|---|
| ACT | Applicability Cross-reference Table | A data module that defines the product attributes (such as model, series, and serial number) used to describe which product instances a piece of content applies to. |
| Applicability | — | The mechanism that controls which parts of the content apply to which product instances or conditions, so one source can serve many variants. |
| BREX | Business Rules EXchange | A data module that encodes a project's business rules in machine-checkable form; every data module must reference a BREX and is validated against it. |
| CSDB | Common Source Database | The single store that holds all information objects (data modules, illustrations, multimedia, publication modules, and management data); it can be a simple folder or enterprise software. |
| Data module (DM) | — | The atomic, self-contained, reusable XML information unit in S1000D, carrying identification and status metadata plus content, and stored in the CSDB. |
| DMC | Data Module Code | The unique identifier of a data module, built from system-related and content-related fields including the Model Identification Code, SNS, disassembly code, information code, and item location code. |
| ICN | Information Control Number | The unique identifier of a non-text object — an illustration sheet, a multimedia file, or attached data — in the CSDB, independent of the file format. |
| IETP / IETM | Interactive Electronic Technical Publication / Manual | An IETP is the interactive electronic delivery of S1000D content from the CSDB; an IETM is usually viewed as a single manual that forms part of an IETP. |
| Information code (IC) | — | The DMC field that states what kind of information a data module holds, grouped in primary families from 000 (function/description) to 900 (miscellaneous). |
| IPD | Illustrated Parts Data | A data module type that presents parts information together with illustrations, used to identify and order components. |
| Item location code | — | The DMC field that states where the work or information is located relative to the product (for example, on or off the equipment). |
| PM / PMC | Publication Module / Publication Module Code | A publication module assembles selected data modules into a deliverable publication; the PMC is its unique, structured identifier. |
| SNS | Standard Numbering System | The DMC field that places a data module in the product breakdown using system, subsystem, sub-subsystem, and assembly levels (for example, 29-10-05 = Hydraulics → Main system → Tank). |
| STE | Simplified Technical English (ASD-STE100) | A controlled language of writing rules and approved words that makes maintenance content clear and easy to read, including for non-native English readers. |
The DMC decoder breaks an example DMC into its labeled fields, and the SNS tree shows how the system numbering nests from a system down to a single assembly.
Information code families at a glance
The information code is one DMC field. Its first digit sets the primary family. This table shows the verified primary families.
| Code | Primary family |
|---|---|
000 | Function / description |
100 | Operation |
200 | Servicing |
300 | Examinations, tests, and checks |
400 | Fault reports and isolation |
500 | Disconnect, remove, disassemble |
600 | Repairs |
700 | Assemble, install, connect |
800 | Storage |
900 | Miscellaneous |
Applicability uses up to three cross-reference tables. The ACT defines product attributes. The CCT (Conditions Cross-reference Table) defines technical, operational, and environmental conditions. The PCT (Product Cross-reference Table) lists actual product instances and their values. If you create a PCT you must create an ACT, and vice versa; a CCT is optional.
Sources
- S1000D — Wikipedia — definitions of data module, DMC, CSDB, IETP/IETM, and scope
- S-Series official site — S1000D — the specification and its place in the S-Series IPS family
- ICN coding in S1000D — Pentecom — Information Control Number definition
- How to manage the ACT, PCT and CCT — SlideShare — applicability cross-reference tables