Conflict monitoring in traffic signal systems is a safety function that sits between the signal controller and the lamp drivers, watching for any combination of active phases that would put conflicting traffic movements on green at the same time. If a conflict is detected, the monitor cuts power to the field equipment and forces the intersection into a safe, all-red or flashing-red state. It doesn't log the event and wait. It acts immediately.
Most engineers working on signalised intersections will know the term. Fewer will be familiar with exactly what triggers a conflict, what the monitor's hardware architecture looks like, and what distinguishes a compliant installation from one that looks right on paper but creates a gap in practice.
What counts as a conflict
A conflict occurs when two or more signal phases that allow incompatible movements are active at the same time. The clearest example is simultaneous green aspects on opposing through movements and turning movements at a four-leg intersection. But conflicts also include less obvious combinations: a pedestrian green crossing a path that a vehicle phase is also permitting, or a right-turn arrow displaying while the opposing through phase is still green.
Signal controllers use a phase conflict table, sometimes called an incompatibility matrix, to define which combinations are forbidden. The conflict monitor reads the controller's output states and compares them against this table continuously. Every scan cycle, which is typically in the range of 10 to 30 milliseconds depending on the monitor unit, the monitor checks whether any prohibited pairing is simultaneously active in the load switches feeding the lamps.
It's the "in the load switches" part that matters. A controller can be functioning correctly while a downstream wiring fault or failed relay creates a conflict at the lamp level. Monitoring only the controller outputs would miss that entirely.
Hardware architecture of a conflict monitor
Most conflict monitor units installed in Australian traffic cabinets are standalone modules that sit between the controller and the field wiring. They're not part of the controller firmware. This separation is deliberate: it means the monitor can detect a controller malfunction, not just field faults.
The monitor reads actual voltage on the load switch outputs, not digital signals from the controller's internal bus. Each monitored channel connects to a lamp output terminal. The monitor's logic compares every active channel against the conflict table programmed into it during commissioning. The table is typically set in hardware via DIP switches or a protected configuration interface, so it can't be overwritten by a software update to the controller.
When a conflict is detected, the monitor de-energises a relay that disconnects power to the intersection's field terminals. The intersection then displays either all-red or a flashing-yellow indication, depending on how the cabinet is configured. The monitor also latches the fault state. Resetting requires a deliberate maintenance action, usually a physical reset at the cabinet, after the fault is identified and cleared.
Some units provide a fault log with a timestamp of the conflict event and the channel combination that triggered it. This is valuable for post-incident analysis, particularly when a conflict trip occurs without an obvious cause. Understanding what was active at the moment of the trip is the starting point for fault diagnosis. This kind of detailed diagnostic data feeds directly into the fail-safe design principles that underpin modern traffic signal engineering.
Conflict monitor standards in Australia
In Australia, conflict monitoring requirements for traffic signal equipment are governed primarily by Standards Australia and the relevant state road authority specifications. AS 2578 covers traffic signal controllers and includes requirements for conflict monitoring functionality. State specifications from transport authorities in New South Wales, Victoria, and Queensland all mandate conflict monitors in signalised intersection cabinets, typically requiring them to be independently powered and independently certified.
Independent power matters. A conflict monitor that draws its operating voltage from the same supply rail as the controller can fail silently if that rail degrades. The monitor appears operational but may not respond to a real conflict. Separate supply rails or a watchdog circuit that detects monitor inactivity are the standard mitigation for this failure mode.
Certification requirements also apply to the conflict table itself. The table must reflect the actual signal phasing at that specific intersection. A generic table loaded from a previous site is a commissioning defect. Verifying the conflict table against the site-specific phase and turning movement data is part of the functional acceptance test for any new or modified installation.
Common failure modes and maintenance considerations
Conflict monitors are passive monitors most of the time. They sit in the cabinet, scanning continuously, and only act when something goes wrong. That passivity creates a maintenance risk: a unit can develop a fault that prevents it from tripping when it should, without producing any visible indication during normal operation.
Three failure modes are worth checking during routine maintenance visits. First, a failed relay within the monitor can prevent it from cutting power even when a conflict is detected internally. Second, a misconfigured or corrupted conflict table can allow a prohibited phase combination without triggering a trip. Third, wiring errors that leave some lamp outputs unmonitored mean the monitor is operating with incomplete visibility.
Functional testing of the conflict monitor, rather than just inspecting it visually, requires deliberately activating a conflicting phase combination under controlled conditions and confirming the monitor trips within its specified response time. Most maintenance contracts specify this test at commissioning and at periodic intervals, typically annually. It's also a required check after any modification to the signal phasing or timing plan, since a phase change can introduce new conflict combinations that the existing table doesn't cover.
Signal timing plan changes are more common than most asset managers assume. Intersection geometry changes, new turning movements, and updated pedestrian phases all affect which combinations are compatible. Whenever a signal phase and timing plan is updated, the conflict table should be reviewed alongside it, not treated as a separate maintenance item.
Integration with modern signal controller platforms
Newer signal controller platforms communicate conflict monitor status back to the traffic management centre via the communication link. Rather than waiting for a field technician to discover a trip during a site visit, the management centre receives an immediate alarm when the monitor activates. This closes the response time gap significantly.
Some platforms also transmit periodic "heartbeat" confirmations from the monitor, so a silent monitor failure doesn't go undetected until the next maintenance visit. The heartbeat approach treats monitor availability as a continuously monitored asset state rather than a commissioning checkpoint.
As Australian cities add more signalised intersections to adaptive and network-coordinated systems, the volume of conflict monitor events reaching traffic management centres will increase. Integrating monitor alarms into the fault management workflow, and distinguishing between a genuine conflict trip and a nuisance trip caused by lamp flicker or voltage transients, requires clear alarm categorisation in the traffic management system. Getting that configuration right at deployment is worth the effort. A nuisance trip that generates a low-priority alarm teaches operators to ignore conflict monitor events generally, which is exactly the wrong outcome.
Conflict monitoring is a compact piece of hardware that rarely makes news when it works. When it fails, or when it's misconfigured, the consequences are immediate and serious. Treating it as a critical safety system rather than a standard cabinet component, and testing it as such, is the only defensible approach.