GJB 6600 Explained: Four Parts, Coding, Schema and Data Dictionary
GJB 6600 is a Chinese military standard for interactive electronic technical manuals. This guide explains its four-part structure and how projects should verify the adopted edition, coding rules, schema and data dictionary.
How are the four parts organized?
| Part | Focus | Project question |
|---|---|---|
| Part 1: General rules | Scope, functions, content, presentation and data requirements. | What does the IETM project need to deliver? |
| Part 2: Coding | Data Module Codes, Information Control Codes and SNS code segments. | How are objects and system positions identified? |
| Part 3: Schema | Common layer, information layer and information models. | How must modules be structured? |
| Part 4: Data dictionary | Element meanings, attributes, formats and relationships. | What does each element mean and how is it populated? |
A practical project sequence
- Confirm the applicable edition and contract requirements.
- Build the project scope and acceptance matrix from Part 1.
- Define DMC, ICN and the three SNS code segments from Part 2.
- Implement the approved module structure and information models from Part 3.
- Map element meanings, attributes and allowed values using Part 4.
- Validate representative modules, references, media, security and delivery outputs.
How does it relate to S1000D?
GJB 6600 and S1000D both use structured technical information and modular content ideas, but they are separate standards. A project should not copy fields or compliance claims from one standard into the other without an approved mapping and project rule set.
GJB 6600.2 coding
DMC, ICN and SNS code-segment relationships.
Read the guide →S1000D vs GJB 6600
Side-by-side scope and implementation comparison.
Compare the standards →Frequently asked questions
Are GJB 6600 and S1000D the same standard?
No. They share some structured-information concepts but are separate standards with different formal requirements.
Can the four GJB 6600 parts be implemented independently?
They should be read as a connected standard family; project scope and acceptance criteria determine the implementation detail for each part.