Explainer
S1000D Information Codes: The List, and How to Read Them

The Structure
Three Characters and a Variant
The information code is the segment of the data module code that says what kind of information a module contains. It is exactly three characters, uppercase letters or digits, followed by a one-character information code variant: in 520A, the code is 520 (Remove procedure) and the variant is A.
Read the three characters from the left. The first places the code in one of eleven primary groups; the second and third narrow it. So everything in the 500s is about disconnecting, removing, or disassembling, and 520 is the removal itself. Once the groups are familiar, an unfamiliar code is rarely a mystery: its first character already tells you the kind of task.
| Code | Official name |
|---|---|
| 000 | Function, data for plans and description |
| 100 | Operation |
| 200 | Servicing |
| 300 | Examinations, tests and checks |
| 400 | Fault reports and isolation procedures |
| 500 | Disconnect, remove and disassemble procedures |
| 600 | Repairs and locally make procedures and data |
| 700 | Assemble, install and connect procedures |
| 800 | Package, handling, storage, and transportation |
| 900 | Miscellaneous |
| C00 | Computer systems, software and data |
The Codes You Meet Most
A Working List
The full list is long. These are the ones most programs use, with the specification's own names, grouped by job rather than by number.
Front matter and general
- 001
- Title page
- 002
- List of pages or data modules
- 003
- Change record or highlights
- 005
- List of abbreviations
- 006
- List of terms
- 009
- Table of contents
- 010
- General data
- 012
- General warnings and cautions and related safety data
- 018
- Introduction
Description
- 040
- Description
- 041
- Description of how it is made
- 042
- Description of function
Procedures
- 310
- Visual examination
- 340
- Function test
- 420
- General fault isolation procedure
- 520
- Remove procedure
- 710
- Assemble procedure
- 720
- Install procedure
- 920
- Change = Remove and install
Parts and service bulletins
- 930
- Service bulletin
- 941
- Illustrated parts data
- 942
- Numerical index
Rules, applicability, and shared content
- 022
- Business rules exchange (the BREX)
- 024
- Business rules
- 00W
- Applicability Cross-reference Table (ACT)
- 00Q
- Conditions Cross-reference Table (CCT)
- 00P
- Products Cross-reference Table (PCT)
- 00G
- Parts common information repository
- 0A4
- Warnings common information repository
- 0A5
- Cautions common information repository
Names are quoted from the specification's default BREX data module, which carries the complete list and cites Chapter 8.4.1. The authoritative copy for your program is the one in the issue your contract cites.
The Rules Around Them
Variants, Project Codes, and Schemas
Variants. The variant letter distinguishes alternative data modules for the same information. A is the usual first variant; a second way of performing the same activity gets its own letter rather than a different code.
Project codes. The specification leaves room for projects: its default BREX marks specific ranges as project available, in general codes whose third character is a letter. The codes the specification itself defines can be restricted by a project, so a program can forbid codes it does not use, but not redefined. Both decisions belong in the project's business rules and BREX.
Codes and schemas. The information code mostly describes content rather than dictating its structure: which data module type a code is written in is largely a project and tooling decision. The exceptions are few and pointed: 022 must be a BREX data module, 024 a business rules document, and references to warnings and cautions must point at 012 modules or the 0A4 and 0A5 repositories.
Learning content. Training data modules add two optional segments after the information code, the learn code and learn event code, and they travel together: use one and the other is required.
Across Issues
What Changed Recently
Comparing the default BREX code lists issue by issue shows how stable the list is. Issue 4.2 added 024 for business rules. Issue 5.0 renamed 022 to Business rules exchange and 024 to Business rules, and added 025 (Export control policy), 026 (Regulatory policy), and 235 (Flush). Issue 6 added 0A6 (Hazards) and 0A7 (Terminology repository). Issue 7 adds no new information codes.
That stability is useful: a library's information codes rarely need rework when a program moves between issues, even when other parts of the migration do. To decode any code in context, paste it into our free DMC decoder.
FAQ
Questions We Hear
What does information code 040 mean in S1000D?
040 is Description: the general descriptive content for the item the data module covers. Its neighbors are 041, Description of how it is made, and 042, Description of function. All three sit in the 000 primary group, Function, data for plans and description.
What are information codes 520 and 720?
520 is Remove procedure and 720 is Install procedure, from the 500 group (Disconnect, remove and disassemble procedures) and the 700 group (Assemble, install and connect procedures). 920 is the combined case, Change = Remove and install.
What is information code 941?
941 is Illustrated parts data, the code carried by the data modules that make up an illustrated parts catalog. 942 is the Numerical index that accompanies it.
What is the information code variant?
The one character after the three-character information code, as in 520A. A is the usual first variant; further letters distinguish alternative data modules for the same information, such as two different ways of performing the same activity.
Can a project create its own information codes?
Yes, within limits. The specification's default BREX marks specific ranges as project available, in general codes whose third character is a letter within given ranges. The codes the specification defines can be restricted by a project's business rules, but not given new meanings.
Did S1000D Issue 7 add new information codes?
Comparing the default BREX code lists, Issue 7 adds no information codes to Issue 6. The recent additions came earlier: Issue 6 added 0A6 (Hazards) and 0A7 (Terminology repository), and Issue 5.0 added 025 (Export control policy), 026 (Regulatory policy), and 235 (Flush).
Get In Touch
Setting Up Your Code Rules?
Which information codes a program allows, and which project codes it adds, are business rules decisions. We help programs make them early and enforce them in the BREX.