Common Mistakes in Work Zone ITS Lessons Learned During 20 Years in This Field

Today, we would like to discuss common mistakes agencies make when including work zone ITS in a project. But we don’t want to scare anyone away or make this more difficult than it really is. Today, work zone ITS is easy to use, easy to contract, and easy to evaluate. So please dive in and learn your own lessons as you go along.

But with that said, there are a few bits of advice we can offer from our many years deploying these systems.

The first is simple enough. Before you specify a system in a project, identify and clearly state your agency’s goal for that system. Is it end-of-queue crash reduction? Is it diverting traffic onto alternate routes? Is it speed reduction? You and every other decision maker in your agency need to agree on the primary goal, and then communicate that goal to the system supplier through your specifications.

Second, don’t try to do too much with your system. Focus on that primary goal first. If the system supplied can also handle additional responsibilities, then add those that help you meet any secondary goals. For example, a queue detection system can also provide traffic data to meet the Federal Work Zone Safety & Mobility rule. But don’t add features that will just bombard you with data you can’t use. You will have plenty to work with as it is.

Once you have your goal for the project, you can begin designing your system. If the goal is reducing rear-end crashes in slow and stopped traffic, doplar radar is the best sensor to use. It works well at low speeds and is inexpensive. But if your goal is to replace a permanent system that measures speeds, counts and classifications, a side-fire radar such as Wavetronix or RTMS.

Next choose your sensor locations. For most systems you will space them about three-quarters of a mile apart. You may get away with as much as a mile or more in some situations, but more often you will want them between a half-mile and a mile apart. Once they are in place and collecting data, check that data to be sure it is what you need. Locations with a lot of concrete barrier sometimes result in radar echo giving you false results. Locations such as a gore point at the on-ramp from a truck scales will result in below-average speeds as trucks slowly speed up onto the mainline.

Budgets often force you to limit the scope of your system. If it comes down to a choice between cameras or more sensors, please consider maximizing the number of sensors. Better, richer data will result in a more responsive system, and one less susceptible to service interruptions. If you must have cameras, limit their use and the video frame-rate to keep your wireless expenses lower.

Your specifications should include the type and quantity of sensors, message signs, camera trailers and other devices. And consider including a line item for each type of device. In that way, you will have a price if you find you need to increase or decrease the quantity of devices.

Finally, dig into your data. Learn what makes the system work. When an incident happens, look at the data to learn how quickly it affected traffic upstream. And how quickly it clears once the cause has been corrected. This will give you a better sense of the capabilities of these systems and how best to use them on future projects.