We plan, design, specify and integrate intelligent transport systems — adaptive signals, traffic management centres, tolling and enforcement, traveller information and the data platforms behind them — for city authorities, highway agencies, toll and bridge operators, public-transport operators and contractors. Design stays vendor-neutral; the software running it, we build in-house.
ITS turns hardware on poles into a system that sees the network, decides in seconds, and tells drivers and operators what to do next.
Intelligent transport systems link sensing, communications, control and information into one loop: detectors and cameras see what is happening on the network, a communications layer carries that data to a centre, control logic decides what to do — signal timing, ramp metering, tolling — and signs, apps and operators act on it. Fast-growing cities and highway networks need this loop because congestion, incident response, enforcement and toll leakage only get worse without it, not better.
We start with a concept of operations and an ISO 14813-style architecture, so separate procurement packages — signals, tolling, CCTV, communications — fit together instead of becoming five incompatible systems. Design favours open protocols such as NTCIP and DATEX II over proprietary lock-in, with factory and site acceptance testing before anything is handed over. We build the TMC software, dashboards, ANPR analytics and data warehouses ourselves, then keep tuning signal plans and reporting performance — so you are never locked to one hardware vendor.
Hardware on a pole is not a system. It becomes one when the data reaches a person who can act on it.— Qubit engineering team
From a single signal head to the data warehouse behind the whole network — and everything in between.
We design corridor and network signal timing — cycle, split, offset and phase plans — and apply SCATS- and SCOOT-class adaptive strategies where volumes justify them. Every scheme is modelled in VISSIM or Synchro before a single controller is touched, and we run retiming programmes to keep plans matched to real demand.
We plan the control room itself — layout, video wall, workstation ergonomics — and the software behind it: an ATMS integration platform, incident-management standard operating procedures, and dashboards operators actually use under pressure. Commissioning includes operator training and shadow-running before a centre goes fully live.
We design electronic toll collection — RFID and ANPR, multi-lane free-flow where the business case supports it — alongside weigh-in-motion and axle-load enforcement, and speed and red-light enforcement. Evidence chains are built in from day one: time-stamped, tamper-evident records that hold up in a dispute or in court.
Counting, classifying and watching the network: vehicle counts and classification, automatic incident detection, queue and occupancy monitoring, and CCTV feeds operators can actually search. ANPR gives us origin-destination patterns and journey times across the corridor, turning raw video into the numbers that justify the next intervention.
Variable message signs and journey-time displays that tell drivers something true and useful — plus apps and open data feeds for the same information on a phone. For BRT and MRT operators we add automatic vehicle location, real-time passenger information, and automated fare collection, so the corridor and the buses running on it are managed as one system.
The plumbing that makes everything above actually work together: an ISO 14813 reference architecture, NTCIP and DATEX II interfaces between subsystems and vendors, and a data warehouse that keeps every count, transaction and incident queryable. We add KPI dashboards and, where it earns its keep, a network digital twin.
Five stages from a traffic count to a system your operators trust.
We count traffic, run origin-destination surveys and journey-time drives, and write up the problem in plain terms — where delay, incidents and risk actually sit on the corridor, and what fixing them would be worth.
With stakeholders in the room, we agree what the system must do, who operates which part, and how the pieces talk to each other — then split the work into procurement packages.
Device layouts, communications and power design, civil works and the specifications and bills of quantities a contractor can actually price — coordinated with the road, drainage and structures design around it.
Factory and site acceptance testing, system integration testing, timing plans loaded and tuned, and TMC software brought online — so what gets handed over is a verified system, not a pile of boxes.
We track the KPIs that matter — delay, throughput, uptime — retime signals as demand shifts, mine the analytics for what's actually happening, and stay on as the support desk.
A corridor is only as good as its weakest cycle. We set detector-driven timing at each junction, layer in time-of-day plans with an adaptive fallback for the unpredictable days, and prove the whole scheme in microsimulation before a single second changes in the field. Retiming isn't a one-off: we come back on a quarterly cycle as volumes shift.
Free-flow only works if the back office can prove every transaction. We combine multi-lane free-flow RFID with ANPR as a fallback read, add weigh-in-motion for axle-load enforcement with a proper calibration regime, and wrap the whole chain in tamper-evident, time-stamped evidence records. Reconciliation dashboards show operators exactly where revenue is leaking, lane by lane, day by day.
Signals, CCTV, VMS, tolling and even weather feeds mean nothing scattered across five systems. We bring them into one map-based operating picture, with incident workflows that carry an SLA instead of a shrug, and open APIs — DATEX II, REST — so your own teams and future vendors can plug in. It's built by Qubit, but the code and the data are yours.
Every package is written to go straight into a tender — drawings, specifications and a bill of quantities a contractor can price, not a concept sketch. Interfaces follow open protocols such as NTCIP and DATEX II, so your next vendor can plug in without a rebuild. Software Qubit builds for you — TMC platforms, dashboards, ANPR analytics — comes with the source code, deployed on infrastructure you control.
Every recommendation traces back to a code, a standard or a protocol — never a brand.
The codes and reference architectures our designs are built to meet.
The modelling, GIS and analytics tools behind every design decision.
Interfaces and data formats so your systems can talk to everyone else's.
Across Qubit ITS engagements, 2021–2026. Illustrative until replaced with audited figures.
Six settings where sensing, control and information turn into fewer delays and safer roads.
Arterial corridors and CBD networks, where signal coordination, incident response and traveller information decide whether the morning commute is predictable or a daily gamble.
Interurban highways and expressways, where ramp metering, incident management and variable message signs keep long-distance traffic moving safely at speed.
Toll bridges and expressway plazas, where free-flow collection, weigh-in-motion and enforcement protect both revenue and the structure itself, day after day.
Bus rapid transit and metro corridors, where signal priority, automatic vehicle location and fare collection make the published timetable something passengers can plan around.
Port approach roads and freight corridors, where weigh-in-motion, ANPR and journey-time monitoring keep containers and cargo moving on a schedule the terminal can rely on.
University and business campuses, where smart parking, access control and wayfinding turn a sprawling site into one you can actually navigate.
Anonymised examples. We're happy to walk through the full story on a call.
A nine-junction urban corridor ran on fixed-time plans from a decade earlier, and journeys varied by the day of the week. We retimed the corridor with detector-driven, adaptive control, modelled the changes in VISSIM before touching a controller, and delivered a TMC dashboard so operators could see the corridor, not just nine separate junctions.
An eight-lane toll plaza needed to move from cash lanes to free-flow without losing revenue to leakage. We combined electronic toll collection with weigh-in-motion and ANPR as a fallback read, then built reconciliation dashboards that carefully check transactions against sensor and camera data, lane by lane and shift by shift.
Can't find your answer? Drop us a line — we usually reply within a day.
Talk to usUsually, yes. Most controllers speak NTCIP, and most toll and ANPR hardware exposes a standard interface, so we design around what you already have. Where something genuinely can't integrate or can't be secured properly, we say so early — better in the design phase than after installation.
We're vendor-neutral by design: we specify hardware that fits your budget — controllers, cameras, ETC readers, WIM sensors — rather than pushing one brand. The TMC platform, dashboards and analytics on top, we build ourselves, so you're never stuck waiting on one supplier for both.
Every design includes a fallback: controllers hold their last good timing plan or drop to a safe time-of-day plan if the network link drops, and critical sites get battery or UPS backup sized to your outage profile. We design and test the failure modes deliberately, rather than discovering them the first time the power actually goes.
We design retention periods, access control and anonymisation into the system from the start, and align with your jurisdiction's data protection rules rather than a generic default. Number plates and faces are typically held only as long as an operational or evidentiary need requires, with audit logs on who accessed what.
A corridor study and quick-win retiming can show measurable change within months — often the fastest return on an ITS budget. A full build, from architecture through commissioning, is realistically a multi-year programme, though we phase it so working pieces go live along the way, not all at once.
Yes. We work on signal priority for buses, automatic vehicle location, real-time passenger information, and automated fare collection — as its own project or folded into a wider corridor programme. It's one of the clearer places where our transport and software teams work side by side.
Tell us which junctions, corridors or tolling points are giving you trouble, and we'll come back with a scoped, vendor-neutral plan for fixing them.