The Need

How engineering objects are identified across disciplines, tools, and lifecycle stages

Once you know what must be identified (the Object Dimension), the next question is how it should be identified. The Need Dimension describes the actions, methods, and mechanisms engineers use to create clarity, structure, and traceability in complex systems. 

Across disciplines and tools, engineers use different methods to label, number, tag, classify, and reference objects. Understanding these methods - and how they differ - is essential for building a consistent, scalable identification system, especially in environments aligned with ISO/IEC 81346. 

Why the Need Dimension Matters 

Every engineering object requires a form of identification that matches its role, purpose, and context. 
Choosing the wrong method leads to: 

  • inconsistent documentation 

  • misaligned naming conventions 

  • confusion across teams and handovers 

  • errors during manufacturing, installation, or maintenance 

  • poor traceability across lifecycle stages 

  • costly rework 

The Need Dimension ensures each identifier serves its intended purpose and fits into a logical, unified structure. 

The Ten Identification Needs in Engineering

Below are the primary identification needs used across mechanical, electrical, architectural, and manufacturing disciplines. Together, they form the full landscape of “how” engineers identify objects. 

1. Identification

Identification is the broadest need: assigning a unique label to an object so it can be referenced without ambiguity. It ensures that the same item is recognized consistently in design, documentation, manufacturing, and operation. 

2. Numbering

Numbering originates from simple serial schemes, but modern systems must support far more than numeric sequences. Today, identifiers frequently combine numbers, letters, aspect codes, and symbols to represent structure, function, or hierarchy. 

Numbering remains essential but is no longer sufficient on its own. 

3. Classification

Classification assigns an object to a defined type, reducing synonyms and supporting searchability, harmonization, and catalog management. 
Effective classification systems include: 

  • clear definitions 

  • structured hierarchies 

  • agreed naming across disciplines 

Poorly defined classifications undermine all other identification efforts. 

4. Tagging

Tagging refers to assigning an identifier to an object in a way that is typically used operationally. The tag may be shown on a screen, in an asset list, or on a drawing. 

Importantly, a tag is not the physical label - it is the logical identifier that the label displays. 

5. Labelling

Labelling is the physical application of the identifier onto the real‑world item - plates, stickers, engravings, or printed markers. 

Good labelling ensures that the physical object can be reliably matched to its digital identity. 
Typical concerns include: 

  • durability 

  • readability 

  • visibility 

  • environmental resistance 

ISO/IEC 81346 provides the designation that appears on the label; the label itself is a separate need. 

Example: Labels contain the reference designation which is often the functional aspect

6. Naming Conventions

Naming conventions are the rules that govern how identifiers are formed. They ensure consistency across tools and disciplines. 

Examples of naming‑convention decisions include: 

  • allowed characters 

  • structure and separators 

  • sequence rules 

  • handling of revisions or variants 

The 81346 standard series provides general rules and the framework for constructing reference designations. 

7. Annotation

Annotation determines how identifiers appear in documentation - drawings, schematics, models, and manuals. It focuses on clear, consistent presentation of identifiers. 

Good annotation ensures that identifiers are easy to read, distinguish, and interpret across disciplines and versions. 

8. Designation

Designation is the technical term for the identity that follows an object through the lifecycle and across systems. It is more precise than “name” or “tag” and applies equally to digital and physical contexts. 

Designation provides the structural foundation that connects design, procurement, installation, and operation. 

9. Traceability

Traceability describes the ability to follow an object’s identity across lifecycle transitions: 

  • component → design 

  • design → BOM 

  • BOM → procurement 

  • procurement → asset 

  • asset → maintenance 

Traceability issues are typically the first symptom of an inconsistent identification system. 
Most organizations attempt to solve traceability with tools - but the real solution is a stable, structured identification method. 

10. Reference Designation

Reference designation is the formal, standardized method defined in ISO/IEC 81346. 
It assigns a clear, unambiguous code to an object within a system based on: 

  • aspect (function, product, location, type) 

  • hierarchy 

  • structure 

Reference designations provide the most complete and robust form of identification and underpin many modern engineering information models. 

The Role of the Need Dimension

The Need Dimension complements: 

Together, these three dimensions form a coherent structure for engineering identification systems and reflect how engineers search for, understand, and apply ISO/IEC 81346 in practice. 

Back to Why RDS 81346