BRAZIL PROJECT GUIDE
A practical gap-analysis checklist for manufacturers, system integrators and municipalities preparing an electronic traffic controller for a Brazilian project.
Published August 31, 2026 · GAOQIAO Traffic Technology
Start with the exact project requirement
ABNT NBR 16653:2017 covers electronic road traffic signal controllers in Brazil, but an OEM project cannot be defined from the standard title alone. The project team also needs the current licensed standard, the municipal tender or technical specification, the intended intersection design and the central-system interface requirements.
Brazilian public sources identify ABNT NBR 16653:2017 as the standard for electronic road traffic signal controllers. The Brazilian Traffic Signaling Manual, Volume V, is also a useful public reference for the wider signal-system context.
Build one compliance input package
| Input | What to collect | Why it matters |
|---|---|---|
| Normative basis | Licensed edition, amendments and tender references | Prevents testing against the wrong revision or scope |
| Intersection plan | Stages/phases, signal groups, detectors and pedestrian movements | Defines I/O count and timing logic |
| Electrical interface | Supply, grounding, output loads, protection and cabinet wiring | Defines hardware changes and test fixtures |
| Central system | Protocol, transport, commands, alarms and security rules | Defines firmware and documentation work |
| Evidence | Required reports, samples, laboratory status and acceptance criteria | Defines schedule and budget before tooling |
Separate hardware, firmware and evidence gaps
Review the existing controller against the target in three columns: current verified capability, required project capability and action needed. Hardware actions can include power-input changes, output-board configuration, protection, cabinet interfaces and service access. Firmware actions can include timing plans, safety logic, event logs, clock behavior, communications and operator language.
Evidence is a separate workstream. A feature shown in a brochure is not the same as a test result for the exact hardware and firmware configuration. Record the model, board revision, firmware build and options covered by every report.
Use a controlled pilot sequence
- Freeze the tender and standards input list.
- Create the bilingual requirement matrix in English and Portuguese.
- Complete the hardware and firmware gap review.
- Build one traceable engineering sample.
- Run internal verification before third-party or customer testing.
- Release the pilot only with approved drawings, protocol documents and version records.
What to request from an OEM manufacturer
Request a named engineering owner, controlled schematics, I/O maps, firmware release notes, a protocol specification, test procedures, serial-number traceability and a written change-control process. These deliverables make future municipal deployments supportable instead of tying the central platform to undocumented behavior.
Frequently asked questions
Does ABNT NBR 16653 alone define the complete OEM project?
No. It is a central controller reference, but the actual project also depends on the current tender, intersection design, cabinet interfaces, communications, local electrical requirements and the evidence requested by the contracting authority. Freeze those inputs before committing to hardware or firmware changes.
Should testing start before the firmware scope is frozen?
No. Freeze the safety logic, timing functions, communications, operator interface and hardware revision before formal testing. Otherwise a later firmware or board change can invalidate results, force a new sample build and make it unclear which configuration the report actually covers.
What is the first OEM deliverable for a Brazilian integrator?
Start with a bilingual compliance matrix. Each row should identify the source requirement, current controller evidence, gap, responsible party, verification method and target date. This document gives the manufacturer and Brazilian integrator one controlled view of scope, risk and acceptance status.
Related buyer resources
- Traffic Controller Communication Protocols
- Traffic Signal Controller Compatibility Checklist
- Traffic Signal Controller Cabinet Guide