NORSOK N-005 — condition monitoring on the NCS, explained.

1. What N-005 actually requires

NORSOK N-005 sets requirements for monitoring the integrity of load-bearing structures during operation: jackets, topsides, risers, subsea structures, FPSOs. Not the design (that's N-001, N-003, N-004). Not new-build construction (that's M-501 coatings, M-101 weldments). N-005 is the live-asset integrity story.

Practically it requires:

• A long-term inspection plan (LTIP) per asset, scoped to degradation mechanisms relevant to that structure type and operating environment.
• Documented inspection programs covering general visual, close visual, NDT, and special inspections as warranted by criticality.
• Condition assessment of findings with severity classification — actionable for engineering decisions, traceable for audit.
• Inspection records retained for the asset life-cycle with traceability back to source observations.
• Periodic review of the inspection plan — risk-based, with documented justification for any changes.

2. How N-005 differs from DNV-RP-C203 / F101

N-005 covers the integrity-management framework; DNV-RP-C203 covers fatigue analysis of offshore structures specifically; DNV-RP-F101 covers corroded pipelines. The three sit together: N-005 says “you must monitor condition”, DNV-RP-C203 / F101 provide the technical methods for specific damage modes.

A jacket inspection program will reference N-005 for the overall plan and DNV-RP-C203 for fatigue-life calculations on welded joints. Both. CoatingPassport carries applicable_standards as an array — N-005 + DNV-RP-C203 sit together for the same passport when the asset type warrants it.

3. PSA Norway enforcement

PSA Norway (now Havtil) regulates the NCS. Per the Petroleumsloven and downstream regulations, operators must establish + maintain inspection programs that meet recognized standards. PSA accepts NORSOK N-005 as the recognized standard for in-service condition monitoring. In practice this means an audit-grade inspection record traceable from operator assertion back to source observations is the de-facto requirement.

4. The structural problem with PDF inspection records

Most NCS inspection records still ship as PDF. PDF makes the content human-readable but not machine-readable. Drift across inspections is invisible until someone manually diffs two reports. Verifier ingest is impossible at fleet scale. The same problem the EU AI Act addresses on the AI side.

Hullproof CoatingPassport is the structured intermediate object an operator can ship to the engineering review, to the regulator audit, to the agentic data platform (Cognite Atlas AI, Equinor Echo) — same source object, multiple renderers.

5. CoatingPassport × N-005 alignment

• Severity classification: NORSOK N-005 language maps cleanly to CoatingPassport severity (minor / moderate / severe / critical). Severity calibration is per-domain (offshore jacket, pipeline, subsea structure each carry N-005-aligned thresholds in the domain definition).
• Audit-trail retention: Every passport is versioned; severity drift across inspections is observable in the history array. Source-frame references carry the visual evidence indefinitely.
• Applicable standards array: Per passport carries N-005 + DNV-RP-C203 + DNV-RP-F101 + PSA Norway §47 as relevant. Verifier knows what calibration to check against without per-customer translation.
• Long-term inspection plan integration: The passport is the inspection record; multi-passport history is the LTIP execution log.

6. What this means for NCS operators

The capex cycle starting now should already assume structured, schema-conformant inspection data as the baseline artifact. PDF-only workflows will become legacy faster than the regulatory ramp suggests — agentic data platforms (Atlas AI, Echo) are the internal customer pulling structured data into the operator stack, ahead of any external regulator forcing the change.