Boiler, Lift and Pressure Vessel Certification in India: Tracking Expiry Before It Bites

Operational control map

Use this map when translating the guide into system configuration or procedure. Replace every placeholder and add jurisdiction-specific rows before approval.

Control area	Minimum requirement	Owner	Evidence
Scope and applicability	Confirm entity, jurisdiction, activity and effective date.	[ASSIGN]	[EVIDENCE LINK]
Authoritative requirement	Link the current source from the applicable authorities and current primary sources.	[ASSIGN]	[EVIDENCE LINK]
Master data	Define fields, identifiers and ownership.	[ASSIGN]	[EVIDENCE LINK]
Workflow control	Record submission, approval, rejection and correction states.	[ASSIGN]	[EVIDENCE LINK]
Evidence	Retain source documents, acknowledgements and versions.	[ASSIGN]	[EVIDENCE LINK]
Exception handling	Assign escalation, target and acceptance authority.	[ASSIGN]	[EVIDENCE LINK]
Periodic review	Set an owner and regulatory review date.	[ASSIGN]	[EVIDENCE LINK]

Treat this as a maintained record. Store source publication, internal approval and next review dates, and preserve prior versions whenever a rule or workflow changes.

Drift begins with ordinary work, not one dramatic failure

An asset register can be accurate at handover and unreliable two years later. A pump is replaced under emergency work but inherits the old serial number. A fit-out adds maintainable equipment without an asset-creation request. Technicians relocate a unit, projects rename rooms, finance capitalises a component at a different level and a contractor keeps the newest schedule in its own portal.

1. What maintainable assets are installed at this location?
2. What work is due before the warranty expires?
3. Which verified document, spare and supplier record belongs to this exact unit?

The resulting gap is gradual. Each local workaround looks harmless, but the combined register can no longer answer what exists, where it is, which work applies, what condition is known or which evidence belongs to the unit.

The scale and concurrency associated with NEOM and other Saudi giga-projects magnify ordinary handover defects: multiple design packages, joint ventures, suppliers with different classifications, phased occupation, temporary assets becoming permanent, systems commissioned months apart, and operators appointed after information requirements were written. This article does not claim a single NEOM-wide handover template—requirements are contract and asset specific. It sets out the owner-side controls needed on any comparable programme.

Saudi public-sector guidance already treats closeout as more than record submission. The Expenditure & Projects Efficiency Authority's National Manual for Project Management lists separate closeout material for facility and infrastructure handover, contractor project-record matrices, spare-parts handover, supplier information, spare-parts registers and operational training. The separation is important: each deliverable needs an owner, acceptance rule and destination.

Start with operational decisions

The owner should not ask for “all available asset data”. It should specify the information needed to operate, maintain, assure and eventually replace the asset. Every requested field must support a named purpose.

Operational purpose	Information required	Consumer
Identify and dispatch	Asset ID, functional location, system, physical location, tag and access notes	Helpdesk, operator, technician
Plan maintenance	Asset class, duty, manufacturer/model, maintainability, maintenance strategy, task and interval	Planner and reliability team
Execute safely	Isolation points, permits, hazards, method, drawings, access and lifting requirements	Technician and control room
Manage warranty	Serial number, supplier, installation and acceptance dates, warranty terms and claim route	Contract and maintenance teams
Manage spares	Part numbers, quantities, storage and preservation, BOM links, alternates and supplier lead time	Stores and procurement
Prove performance	Design duty, setpoints, commissioning and integrated-test results, acceptance criteria	Operator and assurance team
Meet compliance	Certificate, inspection basis, authority, expiry or renewal trigger	Compliance owner
Manage lifecycle	Criticality, replacement basis, expected service context, cost and decision history	Asset manager and finance

This becomes the asset information requirements: what information is needed, for which assets, at what level, in which format, when, from whom and against which acceptance test. ISO 19650 frames an information requirement as specifying what, when and for whom information is produced. ISO 19650-3:2020 applies that information-management process to the operational phase of assets.

The requirements must be ready before design and supply appointments. If serial number, warranty-start basis and serviceable-part BOM are first requested at practical completion, the party closest to the information may have demobilised, and the commercial leverage to correct it has weakened.

Define what counts as an asset

Design models contain objects. EAM systems contain assets, locations, systems, routes, spares and documents. They are related but not identical.

A project may model every diffuser, cable tray segment and pipe fitting. Registering every object as an EAM asset burdens operations with records that have no independent maintenance decision. The opposite error is loading one record for an entire chiller plant, hiding individual equipment histories and warranties.

Register an item as a maintainable asset where at least one is true:

• work, inspection or statutory evidence must be recorded independently;
• it can fail or be replaced independently;
• it has a distinct warranty, serial number or service obligation;
• it carries material safety, service or financial consequence;
• its condition or cost must be trended through life.

Use functional locations for the stable operating structure: development, district, facility, zone, system and maintainable position. Use asset identities for the equipment installed in those positions. A pump may be replaced; the duty position and its history remain. Conflating the two causes history to vanish during the first replacement.

Publish the maintainable-asset rules by asset class. A blanket instruction such as “all equipment over SAR 5,000” misses low-cost statutory devices and creates records for expensive furnishings with no maintenance requirement.

The minimum usable asset record

The exact schema varies by class, but a day-one asset record usually needs:

Identity and structure

• owner asset ID, tag and any project or contractor legacy IDs;
• functional location and parent system;
• asset class and subtype from the owner's controlled taxonomy;
• clear English and, where required, Arabic description;
• manufacturer, model and serial number;
• physical location, room, level, coordinates or linear reference as appropriate;
• maintainable status and operational responsibility.

Technical and operational attributes

• design duty, rating, capacity and units;
• installed configuration and critical setpoints;
• materials or environmental rating where relevant;
• upstream, downstream and redundancy relationships;
• isolation and access information;
• criticality and service consequence, where approved.

Lifecycle dates and parties

• manufacture, installation, testing, commissioning, acceptance and in-service dates;
• supplier, installer, commissioning authority and service contact;
• warranty start, end, conditions, exclusions and evidence;
• responsible operator and maintenance organisation.

Maintenance enablement

• maintenance strategy and initial job plans;
• task intervals and their trigger basis: calendar, runtime, starts, condition or statutory date;
• safety steps, competency and permit requirements;
• tools, consumables and spare parts;
• baseline readings and acceptable limits;
• preservation or seasonal requirements.

Evidence

• approved as-built drawing and model links;
• O&M manual sections linked at asset or class level;
• factory and site acceptance tests;
• pre-commissioning, commissioning and integrated systems test results;
• certificates, calibration and inspection reports;
• approved deviations, concessions and residual defects;
• photographs where they prove tag, installation or condition.

“Document attached” is not a sufficient field. Each link needs document type, number, revision, status and controlled repository location. Copying uncontrolled PDFs into the EAM creates another document system and another version problem.

Do not wait for the final asset register

Handover quality is cheapest to create progressively. Use information gates tied to project events.

Gate	What should be known	Acceptance focus
Design maturity	Proposed maintainable objects, functional locations, classifications, design attributes	Scope and schema conformity
Approved supplier	Manufacturer/model, supplier IDs, maintainability and expected spares	Product-data completeness and compatibility
Factory acceptance	Serialised units where available, FAT result, firmware and approved deviations	Unit identity and test evidence
Delivery	Received unit, serial number, preservation, storage location and condition	Match to approved product and purchase record
Installation	Installed location, tag, orientation, interfaces and as-installed deviations	Physical verification
Pre-commissioning	Checks, calibration, flushing, pressure or insulation tests as relevant	Test completeness and defect control
Commissioning	Setpoints, measured performance, baseline condition and functional result	Result against acceptance criteria
Integrated testing	System interactions, alarms, controls, failover and cause-and-effect	End-to-end operational proof
Operational acceptance	EAM load, job plans, spares, training, warranty and open-defect treatment	Day-one usability

Rejecting one million incomplete records at the end does not recover the information. Validate small batches at every gate, return failures to their source and measure first-pass acceptance by package and supplier.

Use stable identifiers early

An owner asset ID should be assigned early enough to connect model object, submittal, procurement line, factory test, delivery, installation, commissioning result, defect, spare and final EAM record. If every system generates its own unrelated number, handover becomes a sequence of fragile description matches.

Keep cross-references rather than forcing one identifier to serve every purpose:

• owner asset ID;
• functional-location code;
• physical tag;
• model object GUID;
• contractor tag;
• supplier equipment and serial numbers;
• document and test-pack references;
• ERP material or equipment number where applicable.

Identifiers need governance: format, issuing authority, uniqueness, retirement rule and treatment of temporary, packaged and replaced equipment. Never reuse an asset ID after a unit is removed.

QR or RFID tags can speed verification, but the code is not the asset register. The physical tag must resolve to an authoritative record and remain readable in the installed environment. Verify it in place rather than accepting a print list.

Classifications and attributes need controlled dictionaries

Free-text values turn one manufacturer's “AHU”, another's “Air Handling Unit” and a contractor's “FAHU-01” into different equipment classes. Publish controlled dictionaries for:

• asset and system classification;
• attribute names, definitions and units;
• allowed values and null reasons;
• location and system structures;
• document and test types;
• manufacturer and supplier names;
• failure, maintenance and condition codes.

Distinguish not applicable, not yet known, not provided and failed validation. Blank cannot carry four meanings.

Units must be part of the data definition. A value of 500 is unusable if it could be kW, W, L/s, Pa or rpm. Store a numeric value and controlled unit rather than embedding both in free text.

Where contractors use different authoring classifications, define a mapping to the owner's operational taxonomy and test it on representative packages. Mapping at final export is too late to discover that the source never distinguished maintainable equipment from model components.

BIM is a source, not the operational system of record

BIM can provide geometry, spatial relationships, system membership, design attributes and a persistent link to the graphical object. It does not automatically provide trustworthy serial numbers, actual warranty terms, repairable spares, accepted commissioning values or an executable maintenance programme.

Decide the authoritative source for every field. For example:

Field	Likely authoritative source
Designed capacity	Approved design or product submittal
Installed serial number	Physically verified installation record
Final setpoint	Accepted commissioning result
Warranty end	Contract or supplier warranty record based on agreed start event
Planned maintenance interval	Owner-approved maintenance strategy, informed by OEM requirements
Spatial location	Accepted as-built model or GIS
Purchase cost	ERP or commercial system
Document revision	Common data environment or document-management system

When sources disagree, the acceptance workflow must resolve the conflict. “Latest file wins” is not governance.

The asset information model is broader than a 3D model. It is the controlled combination of structured data, documents, geometry and relationships required for operational decisions. ISO 19650-3 is expressly concerned with information management during operation, not merely delivery of BIM files.

Commissioning data is the operating baseline

Commissioning should create structured baseline data, not only signed PDFs. The operator will later need to compare current performance with the accepted state.

For each applicable asset, capture:

• test method, instrument and calibration reference;
• date, operating conditions and responsible party;
• specified acceptance range;
• measured value with unit;
• pass, fail or accepted deviation;
• final setpoint and authority to change it;
• linked defect or concession;
• approver and acceptance date.

An air-handling unit's accepted flow and motor current, a pump's duty point and vibration, a transformer's test results, a valve's stroke time and a meter's calibration form different baselines. The schema must be asset-class specific.

Do not mark a record complete merely because a commissioning document exists. Validate that the tested asset ID and serial number match the installed unit, the result is accepted rather than preliminary, and any failed result has a controlled resolution.

Warranties fail at the boundary between project and operations

Warranty data often arrives as one date and a PDF. Operations needs the commercial logic:

• what event starts the warranty: delivery, installation, commissioning, taking-over or first use;
• duration and any extended cover;
• inclusions, exclusions and required preventive maintenance;
• notification route and response period;
• whether parts, labour, travel and consequential work are covered;
• supplier and subcontractor contacts;
• evidence needed for a claim;
• serialised assets and components covered;
• open defects and their effect on acceptance.

Create alerts before expiry, not on the expiry date. Review high-value or repeated failures while the claim window remains open. If proof of required maintenance is a warranty condition, the initial job plans must be active from the correct start date.

Spares handover needs both quantity and applicability

The national manual's separate guidance and registers for spare-parts handover and supplier data reflect a common failure: boxes are counted, signed over and stored without a reliable link to installed equipment.

For every handed-over spare, capture manufacturer part number, description, quantity, unit, supported asset/model, interchangeability, storage location, preservation, shelf life, warranty, supplier, certificate where required and whether it is consumable, repairable or insurance stock. Serialized repairables need individual identities.

Verify condition at receipt. Long project storage can consume shelf life or damage bearings, batteries, seals, motors and electronics. A transferred balance is not a serviceable balance until preservation and inspection are confirmed.

Load spares into the inventory system before they are needed and link them to the asset BOM. Keep commissioning consumables, construction surplus and operational spares separate; their ownership and disposition differ.

Training is an acceptance deliverable

Attendance sheets prove presence, not competence. Define training by operational role: operator, maintainer, control-room user, planner, stores team, safety role and administrator.

Each module needs objectives, prerequisites, equipment or system scope, language, materials, trainer competence, practical exercise, assessment and make-up plan. Record who is authorised to operate, isolate, reset, calibrate or administer the system after assessment.

Schedule training close enough to operation to be retained, but early enough for the operator to participate in commissioning and identify defects. Provide a training environment for software and controls; live systems should not become the classroom on opening week.

Define data acceptance separately from physical completion

One percentage cannot describe handover. Report at least:

• physical installation complete;
• tests performed and accepted;
• defects by severity and owner;
• required asset records submitted;
• records passing schema validation;
• records physically verified;
• required documents at accepted revision;
• EAM records loaded and reconciled;
• job plans active before due date;
• spares received, inspected and loaded;
• training completed and competence accepted.

Use hard and soft defects. A missing decorative finish may not block operation; an unverified isolation point, absent statutory certificate, failed cause-and-effect test or unknown fire-system responsibility should. Define the blocking rules before completion pressure arrives.

Sample inspection is appropriate only after automated validation and demonstrated supplier quality. Risk-based samples should concentrate on safety-critical systems, repeated data failures, inaccessible assets and packages with poor first-pass acceptance.

The 90-day operational-readiness sequence

The exact timeline varies, but ownership should transfer before day one.

Before operational acceptance

• freeze approved identifiers and operational hierarchy;
• reconcile installed, tested and registered asset populations;
• load accepted asset records and document links;
• activate statutory, warranty and initial maintenance work;
• receive and inspect operational spares;
• complete role-based training and access provisioning;
• agree residual defects, risk controls and accountable owners;
• test mobile work, alarms, integrations and reporting in the live operating process.

Day one

• operations controls access, permits, isolation and configuration changes;
• every service-affecting defect and intervention enters the EAM;
• warranties and supplier support routes are usable;
• the asset register has a controlled change process;
• project teams remain available through a defined stabilisation period.

First 90 days

• reconcile field discoveries and early replacements without overwriting history;
• review alarm floods, nuisance trips, repeated defects and missing job plans;
• test warranty claims end to end;
• audit sample assets from physical tag to record, test, manual, spare and work history;
• close handover exceptions with evidence;
• capture lessons into requirements for later phases and packages.

Phased giga-projects have an advantage if learning is formalised: the first operational zone can improve the information requirements for the next. Without versioned requirements and feedback, each package repeats the same defects at a larger scale.

Common handover failure modes

• Requirements arrive at closeout. Suppliers never priced or structured the data.
• The model is treated as the asset register. Design objects become thousands of non-maintainable records.
• Completion is measured by populated cells. Defaults, copied values and “N/A” pass without being true.
• Serial numbers are taken from submittals. Approved equipment is mistaken for installed equipment.
• PDFs substitute for data. Baselines and dates cannot trigger work or be analysed.
• Document copies proliferate. Operations cannot tell which revision is controlled.
• Tags are printed but not verified. Code, asset and location do not match in the field.
• Warranty starts silently. Cover expires before planned maintenance and claims are organised.
• Training is counted by attendance. Operators meet the system for the first time during an incident.
• Open defects lose owners. Project punch lists never become operational work and risk controls.
• The integrator fixes everything manually. Source errors recur in every subsequent delivery.

FAQ

Is COBie or an asset spreadsheet enough for handover? Only if it carries the owner's required information and passes operational acceptance. The format does not define asset scope, correct source, verification, maintenance strategy or system ownership.

Should every BIM object become an EAM asset? No. Register objects that require independent work, history, warranty, compliance, condition or lifecycle decisions. Retain other geometry and components in BIM with relationships to maintainable assets.

When should the operator join the project? Before asset information requirements and maintainability decisions are fixed. At minimum, operations should review design maintainability, supplier data, commissioning procedures, job plans, spares, training and acceptance.

Can incomplete records be loaded and fixed after opening? Some non-critical attributes can enter a controlled exception plan. Missing identities, locations, isolation information, required tests, statutory evidence, warranty data or safety-critical job plans should block acceptance for the affected scope.

Who owns asset data after handover? The asset owner should name an operational data owner and field-level stewards. Contractors can produce and correct data, but ownership, acceptance and post-handover change control cannot remain ambiguous.

Where a system helps

An EAM platform should be present before operational acceptance, not procured after it. It provides the target hierarchy and schema, validates staged deliveries, links assets to commissioning and warranty evidence, activates initial job plans, receives spares and turns residual defects into owned work. The payoff is simple: the first maintenance event starts with a trusted asset record rather than a search through project folders. See eAMS for asset management.

Related reading: What Is a CMMS? (KB-129), Spare Parts Inventory in Indian Manufacturing (KB-498), and The Work Order Lifecycle (KB-500).

Sources

• Expenditure & Projects Efficiency Authority, National Manual for Project Management: Closeout and Handover
• Saudi Building Code Center, Building Code 2024
• Saudi Building Code Application Law
• ISO 19650-3:2020, Information management using BIM: Operational phase of assets
• ISO 55001:2024, Asset management systems: Requirements