Use ITS Standards to achieve interchangeability and interoperability for Dynamic Message Signs.
Experience of nine agencies using Dynamic Message Signs built to NTCIP specifications.
Arizona,United States; Delaware,United States; Illinois,United States; Minnesota,United States; New York,United States; Pennsylvania,United States; Virginia,United States; Washington,United States
- Build on what others have learned. Building on what has been done and learned by others helps the agency get just what they need.
- Obtain references on DMS vendors. Use of vendors who already have installed NTCIP-based DMSs reduces risk. Agencies should research several DMS manufacturers and ask for their NTCIP specifications and timeframe for installation before selection. In Virginia, the Virginia Department of Transportation (VDOT) developed a prequalification test that the vendors were required to take and pass to be eligible to submit a bid.(1)
- Find expertise in specification writing and testing. If an agency does not have experience with NTCIP and DMS communications, they should hire someone who does.
- Specify desired NTCIP compliance provisions in the RFP. The Request for Proposal (RFP) should be very specific about DMS communications and other ITS standards that apply. The RFP should address the management and control of data. The RFP should specify not just "NTCIP" but the exact standards, even the DMSs and global objects that are wanted. The agency should not make any assumptions when developing specifications. All features and standards should be identified in the RFP. The RFP should be very specific about communications planned for the signs, and lay out specifications for fiber, phone lines, and data exchange rates. In Washington State, the process was loosely structured and the agency and the vendor worked well together; however, the Washington State Department of Transportation (WSDOT) did indicate that future specifications would be much more explicit and that the precise NTCIP requirements should be documented in the original contract and not as a change order.(2)
(1) NTCIP 9002 v01.04 Case Study Report Virginia DOT Statewide VMS Project.
(2) NTCIP 9003 v01.04 Case Study Report Washington State DOT NTCIP VMS Software Upgrade.
Author: Jerry Pittenger, Battelle
Published By: U.S. Department of Transportation Intelligent Transportation Systems Joint Program Office
Source Date: Spring 2001URL: http://www.standards.its.dot.gov/Documents/lessons2.pdf
Average User Rating
DMS, CMS, VMS, Changeable Message Signs, Variable Message Signs