The Object

1. Components

Components are the building blocks of a larger system - motors, valves, sensors, brackets, connectors, actuators, relays, etc. A component may consist of one part or multiple parts, and it exists from the early design stages all the way into operations. 

Typical identification needs:

• Functional designation 

• Classification by type 

• Traceability in a BOM 

• Cross‑references in drawings 

Components are often what engineers think of when discussing “tagging” or “naming,” but they are only one category in a much bigger structure. 

Example: a pump can be seen as a component system which contains many sub-components

2. Parts

A part is often the lowest level in a structure. It may be manufactured, purchased, or custom‑designed. Parts appear in BOMs, inventory systems, and maintenance planning. 

Typical identification needs:

• Part numbering and versioning 

• Revision control 

• Material / specification tracking 

While components describe “what it is,” parts often describe “how many” or “which exact variant.” 

3. CAD Assemblies

CAD assemblies represent hierarchical structures of parts and sub-assemblies. They define how physical items fit and function together in the digital design environment. 

Typical identification needs:

• Parent–child relationships 

• Versioning and configuration management 

• Structural naming aligned with product architecture 

A consistent assembly ID system ensures CAD, BOM, and documentation remain synchronized. 

Example: A CAD assembly may contain parts, sub-assemblies, and functional items.

4. Functions

A function is not a physical item - it is the purpose a system or component fulfills. Modern engineering practices increasingly use functional definitions to structure system architecture and align with MBSE philosophies. 

Typical identification needs:

• Functional designation 

• Mapping between function and physical architectures 

• System‑level traceability 

Functional tagging is widespread in automation, process engineering, and building systems - and is central to the 81346-standard series. 

5. Locations

Locations describe where something is installed or allocated - not just geographically but also in a structural or spatial hierarchy. Locations used to be only for locating the physical assets in the field, but locations references are increasingly needed for allocation requirements to zones, spaces, building environment etc. 

This includes: 

• zones 

• rooms 

• cabinets 

• racks 

• levels 

• spaces 

Typical identification needs:

• Zone codes and room numbers 

• Rack/row/level identifiers 

• Location hierarchy 

As systems become more integrated, location identification spans both physical placement and logical allocation. 

6. Equipment

Equipment refers to major units such as pumps, machines, panels, cabinets, instruments - typically standalone items that perform a function and often carry compliance requirements such as CE marking. 

Typical identification needs:

• Equipment IDs 

• Operational tags 

• Standard‑aligned naming (ISO, IEC, industry rules) 

Equipment often contains its own internal structure of components and parts. 

7. BOM Parts

BOM (Bill of Materials) parts appear in engineering and manufacturing documentation and guide procurement, production, and assembly processes. 

Typical identification needs:

• BOM line numbers 

• Quantity references 

• Supplier or material codes 

• Alignment with CAD assemblies 

Consistency between BOM data and CAD/PLM systems is essential for downstream accuracy. 

8. Assets

Assets are objects tracked through operation and maintenance. A component becomes an asset when it is procured, installed, and maintained. 

Typical identification needs:

• Asset ID 

• Serial number 

• Maintenance history 

• Location and ownership 

Assets live primarily in EAM or CMMS systems, but their identity must connect back to engineering data. 

9. Hardware Components

Hardware refers to small, often standardized physical items such as fasteners, fittings, connectors, clamps, and other tangible elements that support or assemble the system. 

Typical identification needs:

• Category‑based numbering 

• Supplier codes 

• Standard naming conventions 

Though small, hardware must still be managed and referenced with consistency. 

10. Drawings and Documentation

Drawings are not physical objects but hold essential engineering information. Without consistent identification, documentation quickly becomes fragmented. 

Typical identification needs:

• Drawing numbers 

• Revision codes 

• Sheet numbering 

• Reference designations to the objects depicted 

Drawing identity must stay stable across disciplines and updates.