732.1 Tagging scheme

Define unique IDs for bollards, panels, sensors (523). Tags make HVM bollard assets auditable.

Adopt a readable, scalable tag convention such as SITE–AREA–ASSETTYPE–SEQUENCE (e.g., DXB-T1-BLD-003). Reserve ranges for future devices and paired equipment (e.g., dual loops, redundant panels). Keep the tag naming convention human-friendly, printable on labels, and searchable in your CMMS. Mirror the tag in drawings (731) and in the I/O list (523) so field teams can trace faults quickly.

Encode role (e.g., lane set, stewarded gate) and function (active/passive) only if it’s stable; avoid burying volatile details inside the tag. Use QR/1D barcodes as carriers for the same canonical tag string and place them where technicians can scan safely.

For automatic systems, map tags to the modes of operation and interlocks so alarms and status messages clearly reference the physical device a person can find on site.

732.2 Location referencing

Use grid coordinates and what3words if needed. Referencing speeds crash rated bollard dispatch.

Record XY grid from the project control network and an intuitive wayfinding reference (e.g., “North Plaza, Gate A”). Add level/elevation and nearest benchmark (612). For linear arrays, store the array centreline chainage and a photo pair using the wide→detail photo set convention. This makes dispatch and troubleshooting faster for both security and maintenance teams.

Where emergency responders or FM teams rely on smartphone navigation, include a what3words location and a door/gate identifier that matches site signage (348). For airside/rail assets, keep both public-facing and operational references to respect security protocols.

732.3 Attributes captured

Model, rating, height, sleeve, foundation (125, 415, 332). Attributes protect HVM bollard equivalence (414).

Capture the attributes that prove a bollard is the right product in the right footing: product model, rating string (standard, vehicle class, speed, penetration), head/sleeve type, foundation type, and finish. Include dependencies (421) that are rating-critical—for example, minimum concrete strength or specific anchor layout—so substitutions trigger review.

For automatic bollards, add drive type (512/513), control platform (521–523), counters/health IDs, and safety devices. This attribute set enables apples-to-apples replacement decisions and faster approvals when components are refreshed under warranty (854).

732.4 Serial & certificate links

Tie serials to certificates (431). Links prove crash rated bollard pedigree.

Store serial numbers for bollard cores, sleeves, panels, HPUs/drives, and safety devices. Link them to certificate records (431) and to the submission pack index (938). Where available, include report numbers and the certificate authenticity statement so reviewers can validate lineage during audits or authority approvals.

Record as-installed serials during SAT/snags (638–639) and track replacements; when a panel or drive is swapped, keep both the outgoing and incoming serials tied to the same asset tag with dates and reasons. This preserves auditability and supports warranty claims.

732.5 Spare parts mapping

Map parts to asset IDs (854). Mapping reduces HVM bollard downtime.

Build a spares BOM per asset type: consumables (seals, filters), wear items (rollers, sleeves), and strategic spares (drive units, loop detectors). Cross-reference each spare to the asset tag(s) it fits and the supplier part number. Align stocking levels with Warranty & Spares Policy (854) and site availability targets (738).

Flag rating-critical spares that could alter certified performance (e.g., sleeves that affect capture height). Gate these with approvals to avoid accidental downgrade (435).

732.6 Maintenance classes

Classify service levels and intervals (734). Classes stabilize crash rated bollard uptime.

Define maintenance classes (A/B/C) that bundle tasks and intervals based on duty and environment. For example: A = safety checks & lubrication (monthly), B = functional tests & adjustments (quarterly), C = deep service including hydraulic/drive inspections (annually). Link classes to a Preventive Maintenance Plan (734) and to counters/alerts (541–542) so scheduling can be usage-based, not just calendar-based.

Store evidence requirements per class (716)—photos, checklists, torque sheets—so every task is auditable and repeatable. This structure keeps arrays available and reduces nuisance faults.

732.7 KPIs data hooks

Expose counters/health IDs (541–542). Hooks enable HVM bollard reporting.

For automatic assets, capture the data hooks that feed dashboards: ops/hour, cycle time, fault codes, oil temperature, health pings and missed-ping thresholds (541), KPI alert thresholds (542), and any dashboard URLs. Store the tag of each signal in the register so engineers can trace a bad metric back to a device.

For passive assets, note inspection KPIs (paint condition, sleeve damage, clear-gap drift) and when each should be measured. Consistent hooks make availability (738) measurable rather than anecdotal.

732.8 Ownership & access

Define who updates what (131). Ownership keeps crash rated bollard data current.

Assign a named asset register owner and define edit vs. view roles via RACI (131). Use change control (718/537) for tag edits and serial changes; require evidence (716) for every change request. Provide mobile-friendly read access for field teams with offline capability and a simple process to submit corrections from site.

If SIRA approval or authority audits apply, keep an immutable snapshot PDF of the register inside the Handover Pack Index (736) and note when the live register supersedes it.

732.9 Export formats

CSV/CMMS import templates. Exports integrate HVM bollard registers with FM tools.

Standardize CSV exports with stable column names (Tag, Asset Type, Location, Serial, Certificate ID, Maintenance Class, Last Service Date, Next Due, KPI Hook, Notes). Keep a CMMS mapping sheet that shows how each column maps to your target platform (e.g., Asset, Component, Work Order). Include a version and date in file properties and filenames (911) so downstream users can reconcile updates.

When exporting sensitive data (keys, IPs), scrub fields or split into public and restricted datasets. Always test imports in a sandbox and archive the “import pack” (CSV + log + approvals) under the project’s File Index & Naming Rules (911).

732 Asset Register & Serials — FAQ