GJB 6600.2 Coding: DMC, ICN and Three SNS Code Segments
GJB 6600.2 connects data-module coding, information-control coding and the system breakdown. The exact values and lengths must be taken from the applicable edition and project code tables.
What does Part 2 connect?
| Object | Role |
|---|---|
| Equipment or project identifier | Defines the product or project scope for controlled information. |
| ICN | Identifies controlled information objects such as graphics or media. |
| SNS code segments | Express system, subsystem or sub-subsystem, and unit or component breakdown as required by the project. |
| DMC | Identifies a data module using the approved coding structure. |
Coding checks
- Use the approved product, system and project code lists.
- Keep the three SNS segments mapped to the system breakdown.
- Ensure DMC and ICN values are unique and traceable.
- Record exceptions and changes in the project rules.
- Validate examples against the applicable schema and data dictionary.
See the GJB 6600 overview and the S1000D DMC guide for a standards-bound comparison.
Scope note: This page describes relationships for orientation; it is not a substitute for the formal coding tables or project-approved code lists.
Frequently asked questions
Does GJB 6600.2 define only one universal DMC format?
Project values and formal details depend on the applicable edition and approved code tables. Do not infer a universal template from an example.
What are the three SNS segments used for?
They represent the project system breakdown at the levels defined by the standard and its implementation rules.