Technical manuals
MIL-STD-3031 Army S1000D business rules
MIL-STD-3031 sets Army business rules for S1000D. Current Revision B with Change 1, July 31, 2025, supports Issue 4.2.
Nov 10, 20266 min read5 sources
Why it matters
An Army S1000D delivery needs the correct specification issue, Army rules, and project decisions to meet its publication requirements.
The short version
- 1MIL-STD-3031B with Change 1, dated July 31, 2025, is the active edition listed by ASSIST.
- 2Current Revision B supports S1000D Issue 4.2; original Revision A supported Issues 4.0 and 4.0.1.
- 3Project business rules and BREX modules extend the Army rules without contradicting them.
MIL-STD-3031 is the Army's business rules standard for technical publications prepared using S1000D. It specifies content, style, format, and functionality for page-oriented and interactive publications.
The active edition is Revision B with Change 1, dated July 31, 2025. ASSIST lists that edition. (MIL-STD-3031 ASSIST record)
The supported S1000D issue is 4.2. That issue number matters as much as the military standard's revision letter.
What are Army S1000D business rules?
Army business rules settle how the Army applies S1000D to its publications. They also identify choices that each project must make.
S1000D is the international specification for technical publications using a common source database. It defines data modules, their identification and status information, and their technical content. (About S1000D)
MIL-STD-3031 supplies the Army requirements within that framework. Projects add their own decisions, but cannot contradict higher-level requirements or modify the S1000D schemas. (MIL-STD-3031B Change 1, paragraphs 5.2.1.1 through 5.2.1.4)
| Layer | Question it answers |
|---|---|
| S1000D issue | What structures and specification rules are available? |
| MIL-STD-3031 revision and change | Which Army requirements apply within that issue? |
| Project business rules | Which remaining options does this publication project use? |
| Project deliverables | Which data, publications, and supporting files must be delivered? |
A requirement saying only “use S1000D” leaves these decisions unresolved. Record the issue, Army standard, and project rules together.
For the underlying publication model, see what S1000D is.
What is the current MIL-STD-3031 revision?
The current edition is MIL-STD-3031B with Change 1. Revision B was issued September 30, 2024; Change 1 followed July 31, 2025. (ASSIST revision history)
| Edition | Date | Place in the revision history |
|---|---|---|
| Revision A | March 25, 2011 | Earlier Army rules |
| Revision A with Change 1 | June 15, 2016 | Updated A edition |
| Revision B | September 30, 2024 | Replacement revision |
| Revision B with Change 1 | July 31, 2025 | Active edition listed by ASSIST |
Use the incorporated Change 1 document when evaluating the current B requirements. The cover identifies the September 30, 2024 edition as superseded. The change summary separates technical changes from editorial corrections. (MIL-STD-3031B Change 1, cover and Change summary)
For an existing project, first identify the edition named in its requirements. A new download and an agreed project change are separate actions.
MIL-STD-3031A vs 3031B
The original Revision A used S1000D Issues 4.0 and 4.0.1; current Revision B uses Issue 4.2. Compare the edition's scope before reusing its schemas, examples, or validation rules.
| Comparison | Original Revision A | Revision B with Change 1 |
|---|---|---|
| S1000D issue | 4.0 and 4.0.1 | 4.2 |
| Publication output | Page-oriented and interactive | Page-oriented and interactive |
| Content selection | Army content selection matrices | Army content selection matrices |
| Project tailoring | Acquiring activity selects applicable requirements | Project decisions operate within Army and S1000D requirements |
These comparisons come from the editions themselves. (MIL-STD-3031A, paragraphs 1.1 and 4.1 through 4.4, MIL-STD-3031B Change 1, paragraphs 4.1 through 4.4)
Changing A to B is therefore more than updating a cover reference. Check the selected S1000D schemas, rules files, module coding, and project decisions against the new requirements.
The Army's historical sample-data guide illustrates this dependency. It identifies MIL-STD-3031A and uses Issue 4.0 schemas for its sample files. Treat those files as examples of that earlier implementation. (S1000D Army Sample Data User's Guide, References and section 1)
What does MIL-STD-3031 specify?
It specifies the supported issue, required content, coding choices, and rules for preparing and presenting the data.
A Business Rule Decision Point (BRDP) identifies a choice that must be resolved. The standard answers many choices at Army level and leaves others to the project. Change 1 explicitly distinguishes content requirements from rules governing S1000D structures. (MIL-STD-3031B Change 1, section 1.9)
| Area | What the standard establishes |
|---|---|
| S1000D issue | Issue 4.2 |
| Publication content | Army content selection matrices and information sets |
| Schemas | Project selection within the specification; supplied schemas remain unchanged |
| Module identification | Required information names and Joint Service information codes |
| Optional features | Decisions about optional elements, attributes, and delivery arrangements |
| Business rules | Written project rules and a project Business Rules EXchange (BREX) module |
The Army matrices are substantive requirements. Paragraph 5.5.1.1 says the example information sets in S1000D do not sufficiently define Army content depth and breadth. Use the Army content requirements when preparing Army manuals. (MIL-STD-3031B Change 1, paragraphs 5.4 and 5.5)
Which data module types are used?
Use the data module type that matches the information, then apply the Army and project rules.
S1000D distinguishes descriptive, procedural, fault, crew, illustrated parts, schedules, wiring, process, and business rules information. A data module has identification and status information plus a content section. (About S1000D, Principal concepts)
| Information to publish | Relevant module family |
|---|---|
| Equipment description or theory | Descriptive |
| Maintenance procedure | Procedural |
| Fault isolation | Fault |
| Operator or crew activity | Crew |
| Repair parts information | Illustrated parts data |
| Machine-checkable business rules | BREX |
This table is a starting point for selecting a structure. It is not a complete list of required project deliverables.
MIL-STD-3031 leaves schema selection by information set as a project decision. It requires the Joint Service information codes and names. Record both choices before authors start producing modules. (MIL-STD-3031B Change 1, paragraphs 5.4.2.3 and 5.19.1.2)
How does the Army BREX work?
The BREX module carries machine-verifiable decisions in Extensible Markup Language (XML). The project BREX extends the Army BREX and cannot unilaterally contradict Army rules. For legacy conversion programs, paragraph 1.9.1 provides an LDAC approval process for deviations and a project-specific deviation BREX. (MIL-STD-3031B Change 1, paragraphs 1.9.1, 3.3.15, and 5.19.1.24)
The Army sample-data guide demonstrates the layers: its project BREX references the Army BREX, which references the S1000D default BREX. The guide requires checking modules against all applicable layers. (S1000D Army Sample Data User's Guide, section 3)
A practical review sequence is:
- Match the XML to the required S1000D issue.
- Identify the Army and project BREX files.
- Check every applicable BREX layer.
- Resolve findings and repeat the checks.
- Review written content requirements alongside the automated results.
See what a BREX data module contains for the distinction between written rules and machine checks.
MIL-STD-3031 vs MIL-STD-40051 and S1000D
MIL-STD-3031 applies Army rules to S1000D. MIL-STD-40051 is the Army technical manual preparation standard with its own publication requirements.
MIL-STD-40051E covers both page-based and interactive output. Therefore, choosing between these standards is not simply choosing paper or a screen. (MIL-STD-40051 ASSIST record)
S1000D's download site currently identifies Issue 7 as its current issue. That package includes schemas, a default BREX, sample data, and business-rules resources. It does not change the Issue 4.2 requirement in MIL-STD-3031B. (S1000D Issue 7 download, MIL-STD-3031 ASSIST record)
For other service requirements, use the comparison of U.S. technical manual standards.
What to do next
- Record the required MIL-STD-3031 revision and incorporated change.
- Match the S1000D issue, schemas, and rules files.
- Complete the applicable Army content selection matrices.
- Document project decisions before authoring begins.
- Check modules against the full BREX chain and the written content requirements.
Azcuna's TRACE is one offline viewer for S1000D, MIL-STD-3001 XML, and PDF technical manuals. It keeps the source location and the markings of everything it shows and never modifies the source. It was proposed to NAVAIR under Navy SBIR Phase I topic DON26BZ05-NV078, and the proposal was submitted on September 23, 2026.
Questions people ask
What is MIL-STD-3031?
MIL-STD-3031 is Army Business Rules for S1000D. It establishes technical content, style, format, and functionality requirements for publications using the specified S1000D issue. The standard covers page-oriented and interactive publications, including operation and maintenance information through depot-level work.
What is the current revision of MIL-STD-3031?
ASSIST lists Revision B with Change 1, dated July 31, 2025, as active. Revision B itself was issued September 30, 2024. Use the incorporated change document when assessing current requirements, while separately identifying the edition required by an existing project.
What is the difference between MIL-STD-3031A and 3031B?
The original March 25, 2011 Revision A specifies S1000D Issues 4.0 and 4.0.1. Revision B with Change 1 specifies Issue 4.2. Both cover page-oriented and interactive publications. A transition therefore requires reviewing schemas, business rules, and project decisions, rather than changing only the standard's revision letter.
Does MIL-STD-3031B support S1000D Issue 7?
MIL-STD-3031B with Change 1 explicitly identifies S1000D Issue 4.2. The availability of Issue 7 on the S1000D download site does not replace that requirement. A project must align its specification issue, Army standard, schemas, and validation rules with its agreed requirements.
Does an Army S1000D project need its own BREX?
Yes. Paragraph 5.19.1.24 of MIL-STD-3031B with Change 1 requires project-specific business rules and a project BREX data module. The project BREX extends the Army BREX through layered rules. Project rules cannot unilaterally supersede or contradict the Army business rules. Paragraph 1.9.1 provides an LDAC approval process for deviations needed by legacy conversion programs.
Sources
- 1MIL-STD-3031, Army Business Rules for S1000D, Revisions A and B with Change 1 (ASSIST-QuickSearch Document Details) · Defense Logistics Agency, ASSIST-QuickSearch
- 2About S1000D · S1000D Council and Steering Committee
- 3S1000D Army Sample Data User's Guide · U.S. Army
- 4MIL-STD-40051, Preparation of Digital Technical Information for Technical Manuals (TMs) · Defense Logistics Agency, ASSIST-QuickSearch
- 5Download - Issue 7 · S1000D Council and Steering Committee
Where this shows up in our work
- TRACE, the offline S1000D and IETM viewer opens S1000D, MIL-STD-3001 and PDF technical manuals on a tablet with every marking intact.
- ELLMENT, the offline LLM for E-2D crews answers a crew's question from the aircraft's own manuals and cites the page, with no network.