Operational Standards & Structure

Why standardization matters

Critical infrastructure cannot rely on memory, informal naming or local habits alone. Operational work must be connected to clear identifiers, controlled documents, known systems and verifiable records.

A good documentation structure makes it easier to understand what asset is involved, where it is located, which system it belongs to, what procedure applies, and how the result should be verified.

This is especially important in environments where many disciplines interact: electrical systems, mechanical systems, control systems, fire safety, security, network infrastructure and building operations.

Client and national standards first

The correct standard is normally determined by the owner, client, country, project requirements and operational system landscape. A strong operational documentation model should therefore be adaptable, not locked to one private naming convention.

This means that an operational procedure should not invent asset names if the facility already has an approved naming, BIM, FDV, CMMS or asset register structure.

Norwegian reference model: NS-TFM

In Norwegian building and infrastructure projects, a common reference model is TFM — Tverrfaglig Merkesystem. TFM was developed by Statsbygg and has later been formalized through the NS 3457 series.

NS-TFM uses a structured identification principle where an asset can be described through location, system and component coding. This allows the same physical object to be referenced consistently in drawings, digital models, labels, procedures, maintenance systems and operational records.

In this example, the identifier expresses where the asset is located, which technical system it belongs to, and which component is being referenced.

Location, system and component logic

A structured asset identifier should help operations personnel answer three practical questions:

• Where is it? The location, building, area, floor or room.
• What system does it belong to? The technical system or functional group.
• What component is it? The specific equipment item, sensor, valve, panel, pump or unit.

The exact code format may vary, but the operational goal is the same: the identifier must be unique, understandable, maintainable and usable across disciplines.

Physical marking and digital traceability

Asset identification must work both in documents and in the physical environment. A procedure is only useful if the operator can identify the correct equipment in the field.

Physical labels should be visible, durable and placed so they remain meaningful during inspection, maintenance and fault response. Where appropriate, human-readable identifiers can be combined with QR codes or barcodes linked to asset registers, documentation systems or maintenance platforms.

Statsbygg’s PA-0803 gives guidance for ID numbering, physical marking and sign design, including the use of TFM as one ID-numbering system.

BIM, CMMS and FDV integration

The strongest operational structures connect the same asset identity across several systems:

• BIM models and digital building information
• FDV documentation and handover material
• CMMS or maintenance management systems
• Alarm and monitoring platforms
• SOP, MOP, EOP and risk documentation
• Maintenance history and incident records

When these systems use consistent identifiers, it becomes easier to find the correct document, verify the correct component, review past maintenance and understand the operational impact of a change.

Asset lifecycle philosophy

Asset identification should not be treated as a project-only activity. It must survive design, construction, commissioning, handover, operation, maintenance, replacement and eventual decommissioning.

A weak naming structure creates long-term friction. A strong structure reduces ambiguity, improves training, supports audits and helps operators make better decisions under pressure.

International adaptability

NS-TFM is a strong Norwegian reference model, but international projects may use other client, sector or country-specific standards. The operational documentation structure should therefore describe the principle, not force one national format into every environment.

Where no formal external standard exists, an internal asset structure may be used. It should still follow the same core logic: location, system, asset type and unique running number.

This internal format should be treated as a fallback model, not a replacement for approved client or national standards.

How this affects procedures

SOPs, MOPs and EOPs should reference assets using the approved identification structure. This avoids vague instructions such as “the UPS in electrical room 2” when several similar systems may exist.

A mature procedure should clearly state which system and component it applies to, which documents support it, and which records must be updated when the work is completed.