Exchange Requirement: Guardrail
Name
Guardrail
Identifier
er_guardrail
Change Log
| Date (yyyy-mm-dd) | Action | Author (email) |
|---|---|---|
| 2025-12-09 | Initial draft | AI Generated |
Project Stage
Select the applicable project stage(s); remove rows that do not apply.
| Code | Stage |
|---|---|
| 0 | Portfolio requirements |
| 1 | Conception of need |
| 2 | Outline feasibility |
| 3 | Substantive feasibility |
| 4 | Outline conceptual design |
| 5 | Full conceptual design |
| 6 | Coordinated design and procurement |
| 7 | Production information |
| 8 | Construction |
| 9 | Operation and maintenance |
| 10 | Disposal |
Overview
Provide a textual overview of the exchange requirement under the headings Scope, General Description and Information Description. Keep it non-technical and aimed at an executive audience.
Scope
The scope of this exchange requirement is to enable the exchange of comprehensive guardrail information including identification, spatial location (alignment-based and coordinate-based), type classification (w-beam, thrie-beam, cable), test level ratings, terminal treatments, and structural properties necessary for roadside safety design.
General Description
Guardrails are longitudinal barrier systems that provide edge protection and prevent vehicles from leaving the roadway in hazardous locations such as embankments, bridge approaches, and roadside obstacles. This exchange requirement captures both the geometric definition and the engineering properties necessary for design coordination, crash testing compliance (MASH test levels), quantity takeoff, and construction documentation. The information model supports referencing guardrails to highway alignments using stationing and offset data, as well as absolute positioning using state plane coordinates, GPS coordinates, and LRS data.
Information Description
The information exchanged through this requirement includes the following parts:
- Identification
- Alignment Data Linear
- State Plane Coordinates Linear
- LRS Data Linear
- GPS Coordinates Linear
- Guardrail Features
- Guardrail Layout
- Pay Item Information
Information Requirements
Preconditions
Before exchanging guardrail information, the following information must be available: Alignment and corridor geometry must be established (see Exchange Requirement: Horizontal Alignment, Exchange Requirement: Vertical Alignment, Exchange Requirement: Corridor). Project coordinate system must be defined. Roadside safety analysis and warrant determination must be completed. Applicable guardrail design standards and MASH test level requirements must be identified.
Parts
A part is a set of information that achieves a specific purpose or function within this exchange requirement (for example: Select Object, Assign To Group, Associate Library Reference). An exchange requirement is expected to consist of many parts.
Repeat the following block for each part.
Part: Identification
- Purpose: Uniquely identify each Guardrail element for database management, field verification, and asset tracking.
Concept: Assign Unique Identifiers
- Purpose: Establish unique identification for each Guardrail instance to support data management and asset tracking.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Object ID | Unique ID assigned to each asset in database (Type: STRING, Cardinality: R) |
| Feature ID | Specific point, linear, and surface designation (Type: STRING, Cardinality: O) |
| Feature Description | Specific point, linear, and surface detailed description (Type: STRING, Cardinality: O) |
| Survey Feature Code | Short abbreviation surveyors use in the field to identify and describe physical features and data points encountered (Type: STRING, Cardinality: O) |
Part: Alignment Data Linear
- Purpose: Reference the Guardrail location to the project alignment and corridor system using stationing and offset measurements.
Concept: Reference to Alignment System
- Purpose: Establish the relationship between Guardrail elements and the roadway alignment/corridor framework.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Alignment ID Reference | Alignment ID that is referenced for element layout (Type: STRING, Cardinality: R) |
| Corridor ID Reference | Corridor ID that is referenced for element layout (Type: STRING, Cardinality: R) |
| Station Begin | Station of linear location - begin (Type: REAL, Units: Stationing, Cardinality: R) |
| Station Offset Begin | Offset of linear location - begin (Type: REAL, Units: Feet, Cardinality: R) |
| Station End | Station of linear location - end (Type: REAL, Units: Stationing, Cardinality: R) |
| Station Offset End | Offset of linear location - end (Type: REAL, Units: Feet, Cardinality: R) |
| Reference Point Location | Placement of point for offset (i.e. gutterline for traffic barrier feature) (Type: STRING, Cardinality: R) |
Part: State Plane Coordinates Linear
- Purpose: Provide absolute positioning using state plane coordinate system for survey control and GIS integration.
Concept: Absolute Coordinate Positioning
- Purpose: Define Guardrail location using state plane coordinates independent of alignment references.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Northing Begin | The “Y” values of coordinates represented on a plane coordinate system - Begin (Linear) (Type: REAL, Units: Feet, Cardinality: R) |
| Easting Begin | The “X” values of coordinates represented on a plane coordinate system - Begin (Linear) (Type: REAL, Units: Feet, Cardinality: R) |
| Northing End | The “Y” values of coordinates represented on a plane coordinate system - End (Linear) (Type: REAL, Units: Feet, Cardinality: R) |
| Easting End | The “X” values of coordinates represented on a plane coordinate system - End (Linear) (Type: REAL, Units: Feet, Cardinality: R) |
Part: LRS Data Linear
- Purpose: Support integration with Linear Reference Systems (LRS) for asset management and maintenance operations.
Concept: LRS Integration
- Purpose: Enable referencing of Guardrail assets within agency LRS databases.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Postmile Begin | Mile post of point location - begin (Type: REAL, Units: Mile, Cardinality: O) |
| LRS Offset Begin | Linear Reference System offset of point location - begin (Type: REAL, Units: Feet, Cardinality: O) |
| Postmile End | Mile post of point location - end (Type: REAL, Units: Mile, Cardinality: O) |
| LRS Offset End | Linear Reference System offset of point location - end (Type: REAL, Units: Feet, Cardinality: O) |
Part: GPS Coordinates Linear
- Purpose: Provide GPS-based location data for field verification and mobile data collection.
Concept: GPS Positioning
- Purpose: Support field crews with GPS coordinates for location verification.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Latitude Begin | Latitude of linear location - begin (Type: REAL, Cardinality: O) |
| Longitude Begin | Longitude of point location - begin (Type: REAL, Cardinality: O) |
| Latitude End | Latitude of linear location - end (Type: REAL, Cardinality: O) |
| Longitude End | Longitude of point location - end (Type: REAL, Cardinality: O) |
| Control Points Benchmarks | Reference points with known coordinates and/or elevations, used to create a consistent horizontal and vertical datums for accurate coordination of highway right of way and private property boundaries and existing features for construction projects. (Type: STRING, Cardinality: O) |
| GPS Notes | Notes referring to GPS location data (Type: STRING, Cardinality: O) |
Part: Guardrail Features
- Purpose: Define guardrail type classification, test level rating, and structural properties for roadside safety design compliance.
Concept: Guardrail Type and Safety Performance
- Purpose: Specify guardrail system and MASH test level to ensure compliance with safety standards.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Guardrail Type | Permanent guardrail type including Midwest Guardrail System (MGS), Concrete, and High Tension Cable Barrier (HTCB) (Type: STRING, Cardinality: R) |
| Guardrail Test Level | MASH test level designation (Type: STRING, Cardinality: R) |
Part: Guardrail Layout
- Purpose: Define geometric dimensions, terminal treatments, and transition details for guardrail installation and clash detection.
Concept: Guardrail Geometric Definition
- Purpose: Provide dimensional data for guardrail geometry to support 3D modeling and construction layout.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Guardrail Width | Total guardrail width at widest section (Type: REAL, Units: Feet, Cardinality: R) |
| Guardrail Height | Guardrail Height measured from gutterline (Type: REAL, Units: Feet, Cardinality: R) |
| Transition Start Station | Location of start of transition (Back to Ahead Stations) (Type: REAL, Units: Stationing, Cardinality: R) |
| Transition Start Section | Guardrail section designation at start (Type: STRING, Cardinality: R) |
| Transition End Section | Guardrail section designation at end (Type: STRING, Cardinality: R) |
| Length of Transition | Length of guardrail transition (in plan) (Type: REAL, Units: Feet, Cardinality: R) |
Part: Pay Item Information
- Purpose: Provide construction contract administration data for cost estimation and payment processing.
Concept: Contract Pay Items
- Purpose: Define pay items associated with Guardrail construction for quantity tracking and contractor payment.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
No information requirements defined for this concept.