NORSOK Z-DP-002 Coding Explained.

NORSOK Z-DP-002 is the reference designation system for Norwegian offshore oil and gas projects. It governs how every system, equipment item, instrument, and signal is named on engineering documents that pass through the Norwegian Continental Shelf. The standard is structurally aligned with IEC 81346 but written for the offshore operating environment, with system codes and conventions that reflect the way platforms, FPSOs, and subsea developments are actually built.

This is a working reference for engineers reading or producing NORSOK-coded drawings.

Why a Norwegian-specific standard exists

NORSOK is the body of standards developed by the Norwegian petroleum industry to harmonize specifications across operators, contractors, and the regulator. Before NORSOK, every operator had its own coding manual. The result was that an EPC working for two different operators in the same basin needed two complete sets of coding rules. Z-DP-002 collapsed that to one structure with operator-specific extensions where genuinely needed.

The standard is published by Standards Norway and reviewed periodically. It is referenced by operator project specifications rather than directly by regulation, but on the NCS the practical effect is that compliance is required for any project that will be handed to a Norwegian operator.

The structural anatomy

A complete NORSOK reference designation has up to four parts.

In practice, the function and location aspects do most of the work. The product aspect appears on commercial documents and equipment lists. The document aspect mostly appears in cross-document references.

A real designation might look like =20-FT-1234+M01.W.04, which reads as functional system 20, export gas, for example, instrument FT-1234 within that system, located on module M01, deck W, position 04.

System numbers

The system number is the entry point to every NORSOK tag. The numbering is hierarchical and the project coding manual lists all valid system numbers for the development. A condensed sample of the offshore convention.

The exact numbering is project-specific. Two NCS developments may use slightly different numbers within these ranges depending on operator preference and field complexity. The project coding manual is the authority.

The function position

Inside a system, individual functions are numbered. For instruments, the function position carries an ISA 5.1-style letter code plus a serial number. So 20-FT-1234 is read as system 20, flow transmitter, serial 1234. For valves, the function letters come from the valve table, -XV- for shutdown valves, -PV- for pressure control valves, -BDV- for blowdown valves, and so on.

For non-instrument equipment, the function letters come from a separate table. Pumps are P, vessels are V or T depending on service, heat exchangers are E or H, compressors are C, and so on.

The location aspect

Location codes describe physical position on the facility. The granularity is operator-dependent but typically goes module, deck, area. So +M01.W.04 means module 1, weather deck, position 04. For subsea equipment, the location aspect identifies the template, manifold, or well slot rather than topside coordinates.

The location aspect does serious work on facility-management documents. Once the platform is operational, maintenance jobs, lifting plans, and shutdown isolation are organized by location, and the location codes have to be machine-readable.

Worked examples

Topsides instrument. =20-PT-2105+M02.M.03 is pressure transmitter 2105 in system 20, located on module 2, mezzanine deck, position 03.

Process valve. =21-XV-3001+M02.W.07 is shutdown valve 3001 in system 21, oil treatment, for example, located on module 2 weather deck.

Subsea instrument. =92-PT-101+T01.WH.05 is pressure transmitter 101 in system 92, located on template 1, well 05's wellhead.

Utility equipment. =30-P-1101A+M03.W.02 is the A pump of the redundant pair 1101 in system 30, utility, on module 3.

The internal grammar is consistent. Once you know what system covers what process, the rest of the tag decodes itself.

How NORSOK interacts with other standards

IEC 81346. Z-DP-002 is essentially a NORSOK application of IEC 81346 principles. Aspect prefixes, hierarchical decomposition, and cross-discipline coverage all come from the international document. A reader fluent in IEC 81346 can read NORSOK with maybe an hour of orientation.

ISA 5.1. The instrument function letters come from ISA 5.1. NORSOK does not redefine them, it embeds them in its own structure.

API and ISO standards. Equipment specifications reference API and ISO standards, API 6A for wellhead, API 17 family for subsea, ISO 13628 for subsea hardware. The tags identify the equipment, the standards specify what it must do.

Operator standards. Equinor, Aker BP, Vår Energi, and other NCS operators publish supplementary coding manuals that customize Z-DP-002 for their portfolio. The NORSOK document is the floor, not the ceiling.

Common errors decoding NORSOK tags

A handful of patterns cause repeated trouble.

• Treating the system number as a free-text prefix. It is not. Two-digit system numbers are structured. Stripping the leading zero on system 09 breaks any downstream tooling that expects two digits.
• Confusing function code with equipment number. XV-3001 is not equipment 3001 with function XV. It is shutdown valve, serial number 3001 within the relevant system. The function code is part of the identifier, not a separate field.
• Dropping the aspect prefix. Stripping = and + to save column width breaks parseability. Tooling has to either keep the prefixes or store the aspects in separate columns.
• Mixing module-numbering conventions across drawings. Different EPCs working different parts of the same development sometimes start module numbers at different bases. The project coding manual is supposed to prevent this, but late-stage scope additions sometimes create gaps.

Documents on NORSOK projects

A NORSOK-governed project produces a defined set of document types tied to the coding system. The instrumentation-relevant ones include.

• System block diagrams
• P&IDs, P-diagrams in NORSOK terminology
• Instrument index
• Loop diagrams
• Cable schedule
• Junction box termination drawings
• Cause and effect matrices for safety functions
• Layout drawings showing location codes

Each of these references the same tag identifiers, so consistency across the document set is enforced by tooling rather than by manual review. The instrument index is usually the master, and every other document is generated or validated against it.

Cause and effect on NORSOK projects

NORSOK projects lean heavily on cause and effect, C&E matrices for safety logic. Every tag that participates in a safety function appears in the matrix with its cause inputs, typically discrete inputs from sensors, transmitters at trip thresholds, fire and gas detectors and its effect outputs, shutdown valves, blowdown valves, deluge systems. The matrix is the bridge between the P&IDs, the safety narrative, and the SIS configuration.

Tag identification consistency matters more on C&E matrices than almost anywhere else. A tag that does not match across P&ID, instrument index, and matrix is a safety-system commissioning failure waiting to happen.

NORSOK projects move fast and document early. The coding system is dense enough that tooling has to handle it natively, and the cross-document consistency requirement means that any tag mismatch propagates to several other documents within hours. Treating the standard as a serious data structure rather than a labeling convention is the single thing that separates a smooth NORSOK delivery from a re-numbering exercise at 80 percent design. For how to structure the instrument index that sits at the master of those cross-document cross-references, the instrument index master class guide covers column layout, lifecycle gating, and revision-control conventions.

Further reading

• NORSOK Z-DP-002 Coding system
• NORSOK Z-001 Documentation for operation
• NORSOK I-002 Safety and automation system
• NORSOK U-001 Subsea production systems
• IEC 81346-1 Industrial systems. Structuring principles
• IEC 81346-2 Classification of objects and codes for classes