Traffic Signal Controller Software: A Mixed-Fleet Configuration Checklist

One fleet. Different controllers. Where do you start?

When a team works across different traffic signal controllers, choosing a configuration tool is not simply a matter of finding the longest feature list. You need to know which equipment it supports, which tasks it handles, and how it fits your team's approved way of working.

A useful evaluation starts with a clear picture of the fleet and the jobs technicians need to complete. This checklist helps prepare that conversation without assuming every controller or configuration is interchangeable.

First, separate the three kinds of software

The phrase 'traffic signal controller software' can mean different things:

• Controller software or firmware associated with the controller itself.
• A central traffic management platform used for network-level operations.
• A field configuration tool used by technicians working with controllers.

Make sure the product being evaluated matches the problem. Fenyx is a tablet-based field configuration system. Aria is a central traffic management platform. Neither should be described as the same thing as controller firmware.

A successful demonstration on one controller is a starting point, not proof of compatibility across your entire fleet.

1. Build a practical fleet inventory

List the controller manufacturer, model, firmware version and relevant interfaces for the equipment your team maintains. Include unusual or customized installations rather than assuming they will behave like the rest of the fleet.

A useful inventory also identifies which equipment is common and which appears at only a few sites. That helps the team decide what to demonstrate first and what needs a separate compatibility check.

2. Identify the tasks you need to evaluate

Write down the configuration workflows your technicians actually use. Ask the supplier to explain which tasks are supported for each relevant equipment combination and where exceptions apply.

Keep the evaluation at the level of requirements and approved demonstrations. This checklist is not an instruction to change settings on a live intersection. Any field work should follow the agency's authorized procedures and be carried out by qualified personnel.

3. Clarify setup and ongoing use

Ask what needs to be installed or connected before the tool can be used, and how that differs from a technician's day-to-day workflow.

For Fenyx, discuss the tablet interface, the Nest connection and the equipment information needed for a compatibility review. Confirm the initial setup requirements rather than assuming that wireless use means no installation or cabinet access is ever required.

4. Ask what offline operation means for your work

'Works offline' is a useful starting point, but the important question is which tasks can be completed under the conditions your team encounters.

Ask what must be prepared in advance, which connections are still required, and what happens to records or updates afterward. Review those answers against real agency scenarios rather than assuming offline operation removes every dependency.

5. Review access, records and training

Discuss who should be able to use the tool and what access each role requires. Ask how the proposed workflow fits the agency's existing approval, verification and record-keeping procedures.

Include training in the evaluation. A consistent interface may be attractive, but the amount of training needed depends on the team, the work and the equipment. Ask for a demonstration using representative tasks instead of assuming that a new interface means no training is necessary.

6. Record what is confirmed and what is still open

For each equipment group, record:

• Controller make, model and firmware.
• Tasks the team needs to perform.
• Compatibility evidence provided.
• Setup and connection requirements.
• Workflow or access questions still unresolved.
• The next approved validation step.

This creates a useful handover between operations, engineering and the supplier. It also helps prevent a successful demonstration on one controller from being mistaken for validation of the entire fleet.

Explore Fenyx for field configuration

If your priority is making field configuration more consistent across the equipment you maintain, start with the Fenyx product page and discuss your fleet with Fortran. Ask the team to confirm supported combinations and the scope of the proposed setup.

Explore Fenyx

If your priority is central monitoring and network management, explore Aria instead:

Explore Aria