Exchange Requirement: Barrier
Name
Barrier
Identifier
er_barrier
Change Log
| Date (yyyy-mm-dd) | Action | Author (email) |
|---|---|---|
| 2025-12-09 | Initial draft | example@wsp.com |
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 barrier information including identification, spatial location (alignment-based and coordinate-based), geometric properties, structural characteristics, safety performance (MASH test levels), and construction details such as joints and reinforcement.
General Description
Traffic barriers are critical safety features designed to prevent vehicles from leaving the roadway or crossing into opposing traffic lanes. This exchange requirement captures both the geometric definition and the engineering properties necessary for design coordination, quantity takeoff, construction documentation, and long-term asset management. The information model supports referencing barriers to highway alignments and corridors using stationing and offset data, as well as absolute positioning using state plane coordinates, GPS coordinates, and linear reference system (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
- Barrier Features
- Barrier Layout
- Joint
- Reinforcement
- Pay Item Information
Information Requirements
Preconditions
Before exchanging barrier information, the following information must be available: Alignment and corridor geometry must be established to support stationing and offset references (see Exchange Requirement: Horizontal Alignment, Exchange Requirement: Vertical Alignment). Project coordinate system and datum must be defined. Applicable barrier 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 barrier element for database management, field verification, and asset tracking throughout the project lifecycle.
Concept: Assign Unique Identifiers
- Purpose: Establish unique identification for each barrier 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 barrier location to the project alignment and corridor system using stationing and offset measurements for linear referencing and construction layout.
Concept: Reference to Alignment System
- Purpose: Establish the relationship between barrier elements and the roadway alignment/corridor framework for design coordination and construction staking.
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 of barrier endpoints using state plane coordinate system for survey control, GIS integration, and construction layout verification.
Concept: Absolute Coordinate Positioning
- Purpose: Define barrier location using state plane coordinates independent of alignment references, supporting survey workflows and geospatial data integration.
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) used by transportation agencies for asset management and maintenance operations.
Concept: LRS Integration
- Purpose: Enable referencing of barrier assets within agency LRS databases for long-term asset management and GIS integration.
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, mobile data collection, and integration with GPS/GNSS survey workflows.
Concept: GPS Positioning
- Purpose: Support field crews with GPS coordinates for barrier location verification and enable mobile device integration for asset inspection.
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: Barrier Features
- Purpose: Define the type and safety performance characteristics of the barrier system for design compliance verification and construction specification.
Concept: Barrier Type and Safety Classification
- Purpose: Specify barrier type and MASH test level to ensure compliance with safety standards and design requirements.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Barrier Type | Rigid barrier type usually referencing state-specific standards (Type: STRING, Cardinality: R) |
| Barrier Test Level | MASH test level designation (Type: STRING, Cardinality: R) |
Part: Barrier Layout
- Purpose: Define geometric dimensions and transition details necessary for barrier construction and clash detection in BIM workflows.
Concept: Geometric Definition and Transitions
- Purpose: Provide dimensional data for barrier geometry and transition zones to support 3D modeling, quantity calculations, and construction layout.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Barrier Width | Total barrier width at widest section (Type: REAL, Units: Feet, Cardinality: R) |
| Barrier Height | Barrier 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 | Barrier section designation at start (Type: STRING, Cardinality: R) |
| Transition End Section | Barrier section designation at end (Type: STRING, Cardinality: R) |
| Length of Transition | Length of barrier transition (in plan) (Type: REAL, Units: Feet, Cardinality: R) |
Part: Joint
- Purpose: Specify joint requirements for concrete barriers to control cracking and accommodate movement, ensuring structural performance and longevity.
Concept: Joint Design Requirements
- Purpose: Define joint types and spacing to meet structural requirements and prevent uncontrolled cracking.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Joint Type | The classification of joints formed where two sections of pavement or structural material meet, based on their shape, size, and functional purpose. Common types include contraction joints, expansion joints, and construction joints, which help control cracking and accommodate movement. (Type: STRING, Cardinality: O) |
| Maximum Joint Interval | The greatest permissible spacing between consecutive pavement joints, as specified by design standards, to control cracking and accommodate material movement. (Type: REAL, Units: Feet, Cardinality: O) |
Part: Reinforcement
- Purpose: Indicate whether reinforcement is required for the barrier system to meet structural and safety performance requirements.
Concept: Reinforcement Requirements
- Purpose: Document reinforcement requirements for barriers based on design standards and structural analysis.
Provide a table with the set of information requirements for each concept. Extend the table as needed.
| Idea | Explanation |
|---|---|
| Reinforcement | The indication of whether an object includes reinforcement. (Type: BOOLEAN, Cardinality: O) |
Part: Pay Item Information
- Purpose: Provide construction contract administration data including pay item codes, quantities, and specification references for cost estimation and payment processing.
Concept: Contract Pay Items
- Purpose: Define pay items associated with barrier 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.