Terms like “standoff,” “penetration,” and “clear gap” drive acceptance for HVM bollard designs and crash-rated reviews. Hover tooltips link to full definitions, with preferred synonyms to keep specs consistent. Cross-links to standards (412–414) and selection guides (432–435) ensure language matches certificates (431) and submittals (938). Request new terms as you spot gaps. Include one-sentence context that naturally links upward to the parent hubs (this section and the chapter hub). Link installation pages only if helpful: What to Expect and Installation Guide.
117.1 Tooltip behavior across pages
Hover tooltips give first-use definitions and link to 117.*. They reduce disputes in HVM bollard reviews and align crash rated bollard terms (412).
On first mention in a paragraph, apply a concise tooltip (≤120 chars) and a link to the glossary anchor. Example: stand-off distance, penetration (P-value), and clear-gap. Keep to one or two tooltips per paragraph to preserve readability.
Tooltips are additive, not argumentative: the goal is to prevent misunderstandings before they escalate into comments or NCRs. If a term lacks a canonical entry, add a temporary tooltip and submit it for inclusion (see 117.5) so future pages can reference the same anchor.
When quoting certificates, mirror the term used on the document and add a tooltip to the preferred house term if different. This keeps evidence intact while guiding readers toward consistent usage.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash standards overview (411) |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
117.2 How terms link to full definitions
Every tooltip opens a canonical entry with examples and related pages (232, 413). This helps HVM bollard acceptance and crash rated bollard certificate reading (431).
Each glossary entry should contain: (a) a short definition, (b) a practical example (e.g., array spacing or certificate note), (c) “see also” links to sibling terms, and (d) links to procedure pages such as 232 Spacing rules and 413 How to read ratings.
When a term appears in multiple contexts (e.g., vehicle penetration vs P-value class), the canonical page clarifies scope and points to the right acceptance criterion (e.g., P1–P4).
117.3 Synonyms and preferred terms
We normalize language (e.g., “clear gap” over “free gap”). Use the preferred term in HVM bollard specs and crash rated bollard submittals to match standards (411–413).
Maintain a “preferred term → also known as” map in the glossary. For instance, prefer clear-gap instead of “free gap”; prefer Vehicle Dynamics Assessment (VDA) over “vehicle speed study.” This reduces friction in reviews and prevents disputes about equivalence.
When the certificate uses a legacy label (e.g., K-rating), keep it in quotes and add a pointer to the current standard on page 411.
117.4 Abbreviations and symbols
Define EFO, PLC, ULS/SLS, P-values. This speeds HVM bollard commissioning (631–639) and crash rated bollard acceptance checks (414, 431).
Use established anchors for known abbreviations—e.g., EFO and PLC. For structural design states, add ULS and SLS so field teams share the same interpretation as designers.
When citing penetration classes, use the exact notation (e.g., P1–P4) and link to Penetration classes. Avoid inventing symbols that aren’t present in the standard.
117.5 How to request a new term
Submit the page code and draft wording. Prioritize terms blocking HVM bollard approvals (717) or crash rated bollard claims (414). Changes appear in 118.
Include: (a) proposed term, (b) one-sentence tooltip (≤120 chars), (c) 1–3 sentence definition, (d) at least two “see also” entries, and (e) the pages where it first appears (e.g., 232, 413). Use the Google Sheets slug formula to generate a stable anchor.
Reviewers will (1) check conflicts with existing terms, (2) assess standards alignment, and (3) publish the entry with version/date stamps (see 117.7 and 118 Change Log).
117.6 How definitions are sourced
Sourced from standards (411–416) and field practice (631–639). This grounds HVM bollard usage and crash rated bollard terminology.
Where standards differ in phrasing (e.g., ASTM F2656 vs IWA 14-1), the glossary presents a neutral house definition and then notes standard-specific nuances. Each entry lists the primary reference (411–416) and relevant procedure pages (e.g., commissioning 631–638) so readers can verify usage in context.
117.7 Versioning of definitions
Entries carry dates and diffs (115, 118). Cite versions in HVM bollard reports and crash rated bollard packs (938).
Include a “Last updated” date and a short change note (what changed and why). When a definition affects acceptance criteria (e.g., rating string or acceptance band), cross-reference the impacted pages and note any backward-compatibility considerations.
117.8 Cross-links to standards
Each term links to 411–416 and acceptance (431). Use these to defend HVM bollard decisions and interpret a crash rated bollard rating.
Examples: 411 Crash standards overview, 412 Standards & Terminology, and 431 Documentation & certificates. For equivalency or mixed evidence, refer to 414 Standards equivalency.
117.9 Examples of correct usage
Short snippets show terms inside spacing calcs (322) or certificate notes (413). Copy them into HVM bollard specs and crash rated bollard submissions.
Example A — Spacing: “Set clear-gap ≤ 120 mm along public-side frontages; verify turning clearance against emergency vehicle templates (see 322 Clear-Gap Calculations).”
Example B — Certificate note: “Rating string per ASTM F2656 indicates V/50 @ 90°, P1; ensure foundation detail matches the tested system (see 413 and 330 Foundations & Loads).”
Related
External resources
- BSI — Impact test specifications for VSB systems
- ASTM F2656 — Crash testing for perimeter barriers
- NPSA — Hostile Vehicle Mitigation guidance
