Skip to content
Back

Controller Database Programming

We build and load the controller database for each intersection: phasing, detector assignments, overlaps, pedestrian intervals and every local convention your agency runs by. You get a configuration that matches the drawings, is checked before it leaves us, and is documented well enough that the next person can pick it up years from now.

Traffic signal controller database being programmed on a laptop

What this covers

  • Phasing, detector assignments, overlaps and pedestrian intervals, built per intersection
  • Your agency's local conventions, not a generic template
  • Checked against the drawings before it leaves us
  • Documented so the next person can pick it up years from now

The equipment this touches

What that looks like in practice

A build process, not an improvisation

Database development follows a documented eight-stage flow that our own technicians work to, so the twentieth intersection is built the same way as the first.

Local movements, not a template

The library includes databases built around dedicated bicycle movements and around rail and utility preemption, because those were the conditions on the ground.

The database is kept after it is loaded

Every database we develop stays in our library, so a rebuild or a controller swap years later starts from the configuration that was actually running.

Frequently asked questions

What goes into a controller database?
Phasing, detector assignments, overlaps, pedestrian intervals, and the local conventions your agency runs by. We build it per intersection rather than from a template, so it matches the drawings for that specific location.
Do you check the configuration before it ships?
Yes. Every database is checked against the intersection drawings before it leaves us, and it arrives documented well enough that somebody who was not involved can pick it up later.
Which controllers can you program?
The controllers Tacel supplies and supports: NEMA, ATC and 2070 platforms, and the software that runs on them. See the controllers and system software ranges for what that covers. Each database is built through the same documented eight-stage flow our technicians work to.
What happens to the database after you load it?
It stays in our library. A controller swap or a rebuild years later starts from the configuration that was actually running, rather than from a blank database. That library already includes databases built around dedicated bicycle movements and around rail and utility preemption.

Have a question about this service?

Ask us and we'll get back to you, in English or in French.

Ask a question

Talk to us about Controller Database Programming

Our team covers all of Canada from four offices, in English and in French. Tell us what you are working with and we will get back to you.