SP108-000200-01_Programmatic_Addendum_Letter_signed.pdf
PDF 439 KB Posted
- Attached to
- B25_2027 SMART SCALE - INTERSECTION IMPROVEMENTS
- Solicitation number
- IFB-129943
- Issued by
- Middlesex County, Virginia
About this file
This is a programmatic addendum letter issued by the Virginia Department of Transportation (VDOT) on October 16, 2026, relating to specifications for lane closure coordination and implementation activities. The addendum directs all holders of bid proposals to remove the outdated specification SP801-000100-01 Lane Closure Coordination and replace it with the updated specification SP108-000200-01 Lane Closure Coordination in their bid preparation materials. The updated specification will be incorporated into the final executed contract. Bids are scheduled for October 28, 2026, and November 18, 2026.
The specification SP108-000200-01 establishes requirements for coordinating and communicating lane closure operations through local Traffic Operations Centers. Contractors must designate trained individuals who can speak, understand, read, and write English to input work-zone information into VDOT's Lane Closure Coordination and Lane Closure Implementation system on a weekly basis, with required completion of an online training course prior to the Notice to Proceed date. Lane closures must be entered into the system no later than 8 AM on Thursday of the week prior to planned closure, with final approval issued by the Engineer. The specification details a conflict resolution process with defined priority levels—including emergency work, lower priority delayed work, urgent work, contractual obligated work, weather dependent work, and routine maintenance work—and requires contractors to notify the District Traffic Operations Center no later than 15 minutes before implementation and within 15 minutes after lane reopening. Lane closure coordination costs are not separately measured or paid but shall be included in the price of other contract items.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| B25_124093.pdf | ||
| B25 124093.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DEPARTMENT OF TRANSPORTATION
Stephen C. Brich, P.E. 1221 East Broad Street Commissioner Richmond, Virginia 23219
VirginiaDOT.org
WE KEEP VIRGINIA MOVING
October 16, 2026
Order No.: All
Project: All
FHWA: All
District: All
County: All
Route: All
Bids: October 28, 2026, November 18, 2026
To Holders of Bid Proposals:
Please make the following changes in your copy of any bid proposal currently advertised as of today’s date.
BID PROPOSAL
Please remove specification SP801-000100-01 Lane Closure Coordination and utilize the updated specification SP108-00200-01 Lane Closure Coordination in your bid preparation accordingly. The updated specification will be reflected in the final executed contract.
Sincerely, James L. Swanson, P.E.
State Contract Engineer
Construction Division
Enclosures
VirginiaDOT.org
WE KEEP VIRGINIA MOVING
SP108-000200-01 June 26, 2026
VIRGINIA DEPARTMENT OF TRANSPORTATION
SPECIAL PROVISION FOR
LANE CLOSURE COORDINATION (LCC) and LANE CLOSURE IMPLEMENTATION (LCI)
I. General Requirements
This work shall consist of coordinating and communicating lane closure operations through the local Traffic Operations Centers (TOC’s). The Contractor shall coordinate lane closures in accordance with this Special Provision, and only implement lane closures with approval from the Department.
II. Training
The Contractor shall have individuals trained to input work-zone information into the Department’s current LCC and LCI system on a weekly basis and to update as needed. These individuals shall be able to speak, understand, read, and write English, and be able to operate a computer. No advanced computer skills are needed to use the LCC and LCI system. The Contractor shall have a computer with internet connectivity and email capability.
The Contractor shall contact the Engineer to coordinate system access. The Department requires the Contractor’s designated individuals to complete the online LCC and LCI course prior to the Notice to Proceed date.
III. Lane Closure Process
1. Lane Closure Coordination Process. All lane closures shall be entered as precisely as possible into the LCC and LCI System no later than 8 AM on Thursday of the week prior to the planned lane closure, and updated as needed. For the purposes of this Special Provision, a week starts on Sunday. If this submission deadline changes (e.g. for weeks involving a holiday), the Engineer will notify the Contractor at least one week in advance. Final approval for the lane closure will be issued by the Engineer. All fields in the LCC and LCI system must be properly filled out.
A. Point of Contact. The data fields labeled ”Primary Contact” shall contain the name, phone number, and email address of the person physically entering the request into the LCC and LCI system.
B. Conflict Resolution. The LCC and LCI system will identify and flag most conflicts, and will automatically assign priority as first-come, first-serve. The Contractor has the right to contact the higher-priority party and attempt resolution with them, provided the Contractor submits the final resolution to the Engineer no later than 5 PM on Thursday of the week prior to the planned lane closure. The Engineer will handle all unresolved conflicts between requests and other events according to the priorities listed below, with the highest priority item first. If some or all requests involved in the conflict are the same priority level, conflict resolution will be on a first-come, first-serve basis.
(1) Emergency Work. Work that if not done “will result” in damage to a motorist vehicle or infrastructure, or danger to public health and safety.
(2) Lower Priority Items Previously Delayed. Work that while considered a lower priority, if perpetually delayed could result in severe consequences.
(3) Urgent Work. Work that if not done “may result” in damage to the motorist vehicle or infrastructure, or danger to public health and safety.
(4) Contractual Obligated Work. Work that is expected to be accomplished “on-time, on-budget”.
https://covgov.sharepoint.com/sites/TM-VDOT-SC-Specifications-External/2016_Standard_Specifications/SP801-000100-01.docx
(5) Weather Dependent Work. Work that is dependent on the temperature and clear or dry conditions.
(6) Routine Maintenance Work. Work that is routine in nature that can be rescheduled and moved around, within limits, without undue risk.
C. The request shall be supported by the Schedule of Record, and the Engineer may deny requests which are not. The Contractor will be allowed to request lane closures to accommodate potential weather delays.
D. The Contractor may revise their entries in the LCC and LCI system after the Thursday deadline subject to the approval of the Engineer and the conflict resolution requirements herein.
2. Lane Closure Implementation Process. The Contractor shall notify the District TOC no later than 15 minutes, but no earlier than 45 minutes, prior to installing the lane closure, or no later than 15 minutes prior to scheduled start time if lane closure is delayed or canceled. The Contractor shall notify the TOC of any changes in lane-closure impact during the execution of work. The Contractor shall notify the TOC no later than 15 minutes after the lane is reopened to traffic.
3. Emergency Lane Closure. If an Emergency Lane Closure is required, the Contractor shall coordinate directly with the TOC regarding the lane closure as soon as the location and size of the lane closure is known. An Emergency Lane Closure is defined as road work which could not have been anticipated and is required to protect the public from immediate, severe harm, and has a priority as defined by Section III-1B(1).
IV. Measurement and Payment
Lane closure coordination will not be measured or paid for separately, but the cost thereof shall be included in the price of other items.
| 2026-10-16T08:28:39-0400 | |
| Swanson James P.E. wre26532 |
File details come from the government source that posted it. Updated .