Home / Standards

Standards

Standards give everyone the same dictionary. Equipment, failures and parts are named the same way on every site, so the data compares and the method can be repeated by your own people after we leave.

StandardWhat it governsWhere we apply it
ISO 14224Equipment taxonomy, boundaries, and reliability and maintenance dataHierarchy levels, equipment classes, failure modes, causes and mechanisms
IEC 60812Failure modes and effects analysis, including criticalityFMECA method, severity, occurrence and detection scoring
SAE JA1011 / JA1012What qualifies as an RCM process, and guidance for applying itTask selection logic and full RCM where risk justifies it
NORSOK Z-008:2024Risk-based maintenance and consequence classificationCriticality where no company matrix exists, especially offshore
Noun-modifier namingStructured descriptions: noun, modifier, then attributesEquipment descriptions, materials master, BOMs and spares

ISO 14224

Our language for equipment and failures.

ISO 14224 began in petroleum and gas but its data principles hold in any asset-heavy industry. It defines a nine-level taxonomy from industry down to part, sets clear boundaries for each equipment class, and gives a common vocabulary for failure modes and causes.

  • Comparable data: MTBF, MTTR and bad-actor lists mean the same thing at every site
  • Clear boundaries: work and failures roll up to the right equipment without overlap
  • Faster onboarding: new technicians meet the same classes and codes everywhere

Where your site needs a code the standard does not provide, we leave the field blank and agree an addition with you, rather than stretching the nearest match.

Noun-modifier naming

Our language for descriptions and parts.

Descriptions lead with the noun, then the modifier, then attributes: VALVE, BALL rather than "Ball valve 2in SS". The same rule applies to the equipment register and the materials master.

  • Duplicates surface on sight, which cleans up stock
  • Planners and technicians find the right item faster
  • Like-for-like parts roll up correctly across sites
  • Descriptions fit CMMS field limits, such as SAP's 40 characters, without losing meaning

Start with one area

Most clients begin with a single line or system: register, criticality and FMECA for that scope. It shows you how we work before you commit to the rest of the site.