What certificates look like and what to verify.
Certificates are proof, not marketing—treat them that way. This page lists essential fields, verifies test house identity, and highlights the test article description, foundation details, and evidence media that reviewers expect. We call out limitations/conditions, validity periods, and traceability requirements. Pair this with terminology/rating pages (412–413), equivalence rules (414), and submission guidance (717, 938) to close approvals for HVM bollard installations quickly. Include one-sentence context that naturally links upward to the parent hubs (this section and the chapter hub). Add SIRA context with a link to SIRA Bollards (UAE) when relevant. Link installation pages only if helpful: What to Expect and Installation Guide.
Important: This is a general guide. For live projects we develop a tailored
Method Statement & Risk Assessment (MS/RA) and align with authority approvals (e.g., SIRA) where in scope.
431.1 Essential certificate fields
Include standard, vehicle/speed, penetration, test orientation, foundation, article description, date/validity, and test house. These fields let an HVM bollard design map cleanly to a certified crash rated bollard (413, 415).
Start by confirming the referenced standard (412)—e.g., IWA 14-1, PAS 68, or ASTM F2656—then check the vehicle mass and speed band, the measured penetration (P-value), and the tested orientation. Ensure foundation class and socket depth are explicitly stated so the installed system can match the certified configuration (see 421 — rating-critical dependencies).
Record the certificate date, validity/renewal notes, and unique identifiers that you will cite in submittals (717, 938). Where a manufacturer claims a family rating, cross-check the 415 — product families & variants page to confirm your exact variant sits inside the allowable window.
| Aspect | What matters | Where to verify |
|---|---|---|
| Standard & result | Rating string, P-value, orientation | 413 — How to read ratings |
| System scope | Bollard + foundation = tested system | 421 — Dependencies |
| Traceability | Certificate IDs, dates, lab identity | 444 — Evidence & documentation |
431.2 Test house identity
Use accredited labs with traceable reports. Identity checks prevent weak evidence from undermining HVM bollard approvals (444).
Confirm the laboratory’s accreditation (e.g., ISO/IEC 17025) and that the scope covers vehicle impact testing for VSB systems. Look for a report number, issue date, and contact details on the letterhead, plus signatures. If a distributor re-brands a report, require the original lab certificate in the submittal pack (see 717 — Authority Submittals and 938 — Submission-Pack Guidance).
For UAE jobs, note any authority preferences (e.g., SIRA) and include the lab credentials inside the “Reader guide (submission)” cover so reviewers can verify quickly.
431.3 Test article description
Height, diameter, sleeve, foundation, and accessories must match. Article detail ensures the installed crash rated bollard reflects the test (421).
Describe the tested bollard precisely: nominal height, effective height above finished level, tube OD and thickness, core construction, and sleeve/finish. Include accessories affecting behavior (e.g., link bars, keepered covers). If your variant differs, confirm it’s within the certificate scope or supported by addendum evidence (415).
431.4 Foundation details
Record base depth, reinforcement, and concrete class. Foundation fidelity keeps HVM bollard penetration within the certified range (331–333).
Capture the tested foundation class and geometry (deep socket vs shallow rail), socket depth/diameter, rebar cage, cover, and concrete grade. Note curing requirements and any grout bed or levelling details that affect base rotation. Cross-reference 331, 332, and 333. If groundwater or soil creates buoyancy/drainage risks, link to 423 and 334.
431.5 Photos/video evidence
Provide approach, impact, and post-test views. Visuals help reviewers trust the crash rated bollard in your HVM bollard layout (444).
Include a wide→detail photo set, annotated before/after frames, and links to unedited test footage. Add stills that mark the penetration line and the measured P-value. Place filenames and timestamps in the Photo/Redline Logbook (937) so reviewers can trace evidence quickly.
431.6 Limitations & conditions
Note angle limits, soil notes, and array constraints. Limits protect HVM bollard decisions from over-claim (414, 421).
Document orientation dependency, allowable array patterns, maximum clear gaps, and any soil/foundation comparability notes. If proposing “equivalence” (different standard or base), apply the 414 — Standards equivalency guidance and add an explicit equivalence clause.
431.7 Validity period
Track retest or renewal dates (118). Valid evidence prevents a stale crash rated bollard claim.
Record the certificate issue date, any sunset/retest requirements, and links to the 118 — Change Log. For product family changes, include a Release ID and show whether earlier editions are superseded.
431.8 Serial/traceability
Tie site units to certificates via labels and logs (115). Traceability preserves HVM bollard assurance.
Maintain an Asset Register (732) that links site serials and heat numbers to certificate IDs. Add labels to HPU/panels and bollard bases; capture them in the 937 — photo log and the 939 — archive.
431.9 Reviewer acceptance checklist
Short list: fields complete, lab accredited, article match, base match, photos, limits, validity. Checklist accelerates crash rated bollard approvals (938).
Before submission, perform a quick pass using 938 — Submission-Pack Guidance and attach your Submission index. For UAE projects, add a brief SIRA cover note and include the relevant certificates in Arabic/English per your bilingual policy.
Related
External resources
- BSI — Impact test specifications for VSB systems
- ASTM F2656 — Standard test method for vehicle impact testing
- NPSA — Hostile Vehicle Mitigation guidance
431 Documentation & certificates for Crash-Rated Bollards — FAQ
What documents must be in a valid HVM bollard certificate pack?
Include the certificate/report with rating string and orientation, the tested article and foundation description, accredited lab identity, date/validity notes, and supporting photos/video. Add traceability IDs and a submission index so reviewers can cross-check quickly.
How do I verify the test laboratory is legitimate?
Check accreditation (e.g., ISO/IEC 17025) and that the scope covers VSB impact testing. Confirm report numbers, signatures, and contact details on the lab letterhead. For re-branded reports, request the original lab certificate as part of the submittal.
Do photos and video matter if I have the certificate?
Yes. Approach/impact/post-test visuals build confidence, show where penetration is measured, and reveal article/foundation details. Provide unedited footage links and labelled stills that mark the defend line and the measured P-value.
How long is a certificate valid?
Validity depends on the issuing body and any retest requirements. Record issue dates, renewal windows, and product release links; flag superseded versions. If in doubt, ask for a current edition or addendum confirming no material changes.