ERP X was an experiment on road pricing alternatives. This is a story of what we tried, and why we think this is a better way for government to build.
Published on 27 July 2026, 09:00 AM
12 – 15 min read
ERP X was an experiment we ran to see if ERP gantries could be replaced by high-tech cameras.
Over two years, we tested it on real roads with 403 citizen testers.
We found that it works.
ERP X cameras are accurate, affordable to implement, and well-liked by users.
The experiment at a glance
Accuracy
97.16%
SG-registered vehicles accurately recognised, across all conditions.
Cost
$2.2M/yr
Plus $2.7M upfront, to replace all 22 existing ERP sites.
Citizen feedback
8.58 / 10
Rating for overall experience by citizen testers.
ERP X will not be rolled out. But this was more than just experiment in camera-based road pricing. It was also an experiment to show how government can prototype national infrastructure safely, and test it with citizens before committing to build it.
This is a story of what we tried, what worked, what broke, and what we learnt along the way.
01.
What is ERP X?
ERP X is an experiment in
prototyping with citizens
For two years, 403 motorists went about Singapore on their daily journeys, just as they always had. Nothing in their cars had changed.
What changed was on the roads around them. A network of 63 cameras was quietly reading their licence plates as they passed, and an app on their phones “charged” them for Electronic Road Pricing (ERP) each time, as if the gantries had never been there at all.
These 403 motorists were our citizen testers, and participating in a live experiment set up by Open Government Products (OGP). They were helping us answer one question: what if there was a different way for ERP to work in Singapore?
A different way to build
Open Government Products (OGP) is an experimental team in government. We build technology for public good, and we build it differently.
In government, execution usually begins only after a plan has been detailed and run through layers of approval. This works well most of the time: we anticipate what could go wrong before it does, and avoid paying for fixes later.
But in technology, things move quickly, and assumptions made during planning don’t always survive contact with the real world. Teams get locked into decisions made before anyone knew better, and by the time something launches, the tech may already be obsolete.
OGP exists because we believe that there is a different way to build. We prefer quick prototypes, we adjust as we go, with citizens involved early, instead of building in isolation and launching all at once.
Why ERP X?
Each year at OGP’s hackathon, Hack for Public Good, we ask our officers to find real problems affecting citizens and spend the month building towards something that works.
ERP X emerged from one of these hackathons
Several of the original team members were drivers or riders themselves, and following announcements that the ERP gantries would be decommissioned, the future of road pricing was on their minds.
Automated Number Plate Recognition (ANPR) cameras were already in use in London, Bangkok, and in major cities across Sweden and Australia. We wondered whether this could also work in Singapore, as an answer to our ageing infrastructure.
LTA was already starting to roll out ERP 2.0, a $556 million project awarded in 2016, and we knew that the solution was unlikely to be dropped.
But that didn’t stop us from asking the question anyway:
“Is there a different way to do ERP in Singapore?”
We weren’t trying to replace ERP 2.0. We wanted to know if camera-based solutions could actually work in Singapore, as it could matter for whatever comes after ERP 2.0.
There was also the question of whether government could tackle national infrastructure problems differently. We wanted to see if we could use working prototypes to gather real evidence about whether a solution would work, well before we committed to building it out in full.
02.
How we built and tested
How do camera-based solutions work?
On the surface, pretty simple.
Cameras are installed next to roads.
Cameras recognise vehicles as they pass through, capturing their licence plates.
A computer, assisted by AI, reads the licence plate and matches it to a record of all licence plates registered into the system.
The system charges the user in real time.
Users are notified about the charge via an app that is linked to their payment method. Once set up, the system runs entirely in the background - no app open, no phone in the vehicle required.
Our three biggest questions to answer
ANPR cameras had been deployed elsewhere, but that didn’t tell us whether they’d work in Singapore. International benchmarks either didn’t account for local weather conditions, a key factor in camera accuracy, or relied on hybrid set-ups with wireless transponders.
The only way to find out was to test it ourselves. So we designed our experiment to answer three questions:
Accuracy
Can a camera-based system accurately read vehicles in Singapore’s conditions, and where would its limits show?
Cost
Can we get an accurate sense of how much this would cost to implement at the national level, and is it operationally feasible?
Citizen feedback
Would motorists actually want a solution like this?
From scrappy to serious
Answering these questions would take time, and we had far more unknowns than answers. Instead of trying to solve all of it at once, we tackled ERP X in phases, each one testing a little more than the last.
This let us learn at each stage and make our small, cheap mistakes early, before they could become big, costly ones.
Prototype
Jan 2024 - Sep 20241 web camera
We built ERP X’s first prototype using webcams bought from Sim Lim Square, fixed them on a tripod connected to a laptop, and drove our own vehicles along an empty road to test if the plates would be recognised.
Despite the barebones set-up, it worked well enough to show there was real potential.
Phase 1
Oct 2024 - Oct 20259 cameras on 1 road (Bras Basah Road)
Getting to our first, permanent ANPR set-up was a steep learning curve. We had to solve unfamiliar hardware problems: tapping power from lampposts, finding the right camera angles, weatherproofing the equipment.
We worked through them one by one, reaching 95-100% accuracy for cars and trucks, and around 85% for motorcycles.
Phase 2
Jun 2025 - Dec 202526 cameras in Bras Basah area
With solid baselines from Phase 1, we expanded from a single road to a neighbourhood. We tested a wider range of road conditions: single and dual lanes, then busier main roads with heavier traffic.
Average accuracy rose from 95.4% to 97.3%. Encouraging, but not enough to trust at national scale without testing on highways.
Phase 3
Oct 2025 - Mar 202663 cameras covering 22 active ERP gantry locations
Highway traffic conditions presented our toughest challenge: higher speeds, heavier traffic, and wider roads. Nighttime and rainy conditions started to affect camera accuracy for highway traffic when they didn’t before.
Our biggest issue was occlusion, which is when plates get blocked or obscured. It happened more frequently because of the steeper camera angle and the closeness of nearby vehicles in heavier traffic.
Phase 3 was our final phase of testing. From it, we gained valuable data on what conditions were necessary for the cameras to function well. We also had first-hand knowledge on the limits of the solution, and when things would start to break down and why.
03.
How ERP X can work
How to set-up the hardware
Here’s how a camera-based road pricing soluction can be implemented in Singapore.
Roadside camera set-up
What a basic hardware set-up for one camera looks like. This set-up won't change depending on road type.
Camera set-up
1. Automatic Number Plate Recognition (ANPR) camera
Captures images of vehicle licence plates and uses optical character recognition software to convert the plate characters into machine-readable text.
2. Illuminator
An infrared LED array that flashes in time with the camera to light up the licence plate, keeping it readable no matter the ambient light or time of day.
3. Extension arm
A bracket that mounts the camera and illuminator onto the lamp post, and positions them over the traffic lane.
Router and power
4. Equipment box
Weatherproof, tamper-resistant enclosure that houses the cabling, battery, and router (with SIM card) for connectivity.
There’s potential for this design to be improved upon if ERP X ever gets a proper nationwide roll-out (e.g. improving the equipment box, using extra SIM cards as a failsafe, using fibre broadband).
But for the purposes of the experiment, this version was already good enough for us to collect meaningful data.
How to deploy the cameras
For regular roads, a single camera pointing at 1-2 lanes of traffic works well (97.3% accurate, minimally impacted by nighttime or rain).
But for highways, which are where all 22 remaining active ERP sites are today, the conditions become more demanding. How the cameras are deployed, and how many, makes a real difference to accuracy.
Because we wanted to test how this solution could scale towards a national rollout, we held firm on two principles of camera deployment:
Roadside cameras only
Even though overhead cameras will be more accurate, they require gantry-like structures. This would be overkill for the experiment, and would undermine ERP X’s whole premise to move away from gantries.
As few cameras as possible
A brute force fix for accuracy is to mount a camera for each lane, but this is expensive and impractical. We used Phase 3 to find the minimum number of cameras each road type needed before the solution started to fail.
What the cameras need to work well
Working within these limits, we found optimum camera configurations for every type of road. Five key factors make the difference:
1. Unobstructed field of vision (i.e. can’t be too dark, can’t have trees blocking the road)
2. Cameras are only monitoring up to 3 lanes at a time
3. Cameras are only monitoring the lanes nearest to them
4. For highways, to deploy both Front-facing and Back-facing cameras
5. For highways, to use 4K Image Resolution
We tested up to 6 lanes each direction, the max in Singapore today. Anything wider might require mounting cameras overhead, which this approach was designed to avoid.
04.
Technical accuracy
ERP X is 97.16% accurate at recognising Singapore-registered vehicles.
Accuracy is a three-step check, and a failure at any step is a failure overall:
Did the camera detect the vehicle?
If detected, can it read the plate?
If the plate is read, can it pass a checksum confirming that it is a valid Singapore-registered plate?
97.16% is consistent with camera manufacturers’ accuracy claims, and exceeds the regulatory minimums set for similar pure-camera systems in the UK and New Zealand (at least 95%).
The data collected not only give us confidence on the solution’s technical viability, it also helps us understand when it actually starts to fail and why this happens. Most of the time, this was due to weather conditions. Some exceptionally rare (<1%) edge cases also apply.
How we calculated accuracy
97.16%
This is a weighted average. It represents what we think the overall performance of ERP X will be when deployed as a national system, operating year round.[1]
To get to this, we had to measure how camera accuracy fares across different times of day, and in different weather conditions.
☀️
Cameras are 99.23% accurate during the day, in dry weather.
Cameras miss less than 1% of the time, when licence plates are blocked by another object or vehicle.
Licence plates in these photos have been masked for privacy.
🌧️
When it’s raining, accuracy dips slightly to 98.55%.
Heavy rain and splatter can obscure some licence plates more than others.
🌙
When it’s nighttime, accuracy falls to 95.77%.
Darker shadows and brighter headlight glare make it harder for licence plates to be read.
Licence plates in these photos have been masked for privacy.
🌧️🌙
Rainy nights pose the biggest challenge at 90.98% accuracy.
Headlights create backscatter against rain, and wet surfaces reflect bright light.
Accuracy ranges from 90.98% to 99.23%, depending on conditions.
Cameras perform best in the day, and dip most on rainy nights.
☀️ Dry days
99.23%
🌧️ Rainy days
98.55%
🌙 Dry nights
95.77%
🌧️🌙 Rainy nights
90.98%
But Singapore experiences each of these weather conditions in different amounts.
E.g. Singapore has dry days 39.6% of the time, and dry nights 44.4% of the time.
This represents all weather conditions, based on rainfall data in 2025.
Dot counts are rounded to the nearest whole number, so they don't reflect each condition’s exact percentage.
Factoring this in gives us our final accuracy of 97.16%.
Footnotes
[1] All accuracy figures are for Singapore-registered vehicles only. Foreign plates, which lack a standard format and checksum, use the flat-fee model applied at existing ERP sites, and are excluded from calculations.
05.
Cost to implement
ERP X costs ~$2.2M per year, plus an additional ~$2.7M upfront, to deploy and operate at today’s 22 active ERP sites.
This works out to roughly ~$100K per site per year, and between $38K to $350K per site upfront.
How we estimated implementation cost
The cost of rolling out ERP X to the 22 ERP gantries active today can be broken down as follows:
These figures are grounded in actual pilot expenditure, with conservative estimates applied wherever we could not precisely determine them.
For context, we estimate the most expensive ERP X site to cost ~$250K to set up and ~$100K to run in its first year.
Just charging $1 per vehicle and at a poorer 5% leakage rate, that site would still offset its cost within its first year, on a modest 1,009 vehicles per day while ERP is active. For comparison, two lanes of the MCE already see more than 2000 vehicles in a 20-minute window.
Important note
These findings on accuracy and cost do not prescribe how future camera-based solutions should be implemented. They are indicative trade-offs that can help policymakers weigh their options.
For example, spending more to push accuracy higher, or accepting lower accuracy to bring cost down.
06.
Citizen feedback
Understanding how the technology would fare in real world conditions required us to test with real users too.
Over two years, 403 members of the public joined our Citizen Tester Programme. They downloaded the test app, enrolled their vehicle plates, and drove through our cameras to test accuracy. Whenever they faced an issue, they flagged it in a WhatsApp group, which let us investigate quickly and report back on what we found.
"Obviously, we were in testing, so sometimes it did not work properly - there was a period where my bike was not being picked up. Once reported, it got resolved quickly."
- Participant 1
Over time, they started offering suggestions unprompted, pointing out things we’d missed ourselves. One tester pushed for additional security around licence plate data, so we built a proper whitelisting system that pre-registered plates as an onboarding step.
Running the programme took more effort than a standard feedback form. But it gave us real insight into what users actually wanted and covered our blind spots. It surfaced the kinds of friction ERP X would eventually face if rolled out nationally, before it became too costly to fix.
After the experiment ended, we ran a final survey. 100 of our citizen testers responded, and this is what they told us:
Citizen testers enjoyed the experience of using ERP X, rating the solution 8.58 out of 10.
While the sample was a self-selected subset of registered ERP X citizen testers and therefore isn’t representative of Singapore’s driving population, the findings suggest that an ANPR-plus-app solution can work well for the people who use it.
Insights from our Citizen Tester Survey
Chart: Distribution of respondents' overall experience ratings with ERP X (N = 100), measured on a 1–10 scale. Ratings were classified as negative (1–4), neutral (5–7), or positive (8–10)
Top features respondents valued most
App usability
Ease of use, simplicity, and intuitiveness.
27
Notifications
Charge alerts arrived promptly and clearly
21
No hardware required
Just a phone, no in-vehicle device to install
19
Most frequently mentioned challenges
Notifications
Alerts were late, missing, unclear, too frequent, or duplicated
15
General responses
Other feedback that didn't fit a specific category
9
Detection accuracy
Missed crossings, or a charge with the wrong amount, location, or timing
8
The most common complaint about detection accuracy traces back to a known cause of not updating test app's logic to match the latest camera deployments, which gave the impression that the user was being charged twice. This bug would have been possible to fix, but as the experiment was concluding, we decided that engineering time was better spent on data analysis instead.
See Annex D for more on our survey methodology and findings.The final survey offers valuable insight into what users actually care about: a solution that works seamlessly and reliably, with minimal fuss.
07.
Our journey with citizen testers
Despite how valuable citizen feedback can be, exposing early prototypes to them can still be uncomfortable. Members of the public can be quick to judge, and unforgiving of rough edges.
ERP X was scrappy, and as an experiment, we knew that we would fail a lot. We were worried that citizens wouldn’t understand our approach, or would feel that it was a waste of time.
Transparency creates trust
What we found was that involving citizens early, and being transparent with them throughout, actually lowers the risk of unhappiness. Instead of shielding them from the mess of the process and only showing them the polished product, we exposed them to it all.
Citizen testers didn’t mind the scrappiness of the solution, and in fact, seemed to prefer it because it represented a government that was genuine about involving citizens. Many recognised it as a departure from how solutions are usually built, and wanted to see more of it.
"I want to thank this collaboration to involve citizens […] I used to work in the government sector a long time ago, and we have never done this."
- Participant 7
Reflecting on the overall experience, 97% said being a citizen tester for a government service was worth their time, even knowing that it might not go into production.
Why they’d do it again
Whatever brought people to join as a citizen tester in the first place—whether curiosity, frustration with the status quo, or a hope that camera-based solutions would launch—the process of experimenting together created a shift in perspective.
It had become less about road pricing, and more about what citizen-government collaboration could look like. By the end of the experiment, 96% said they’d want to be involved in future experiments.
"Proud of myself to have been able to participate in something for the future of Singapore."
- Participant 6
"If itchy hands can help for greater good, why not."
- Participant 5
To every citizen tester who drove past our cameras, and stuck around anyway, thank you for being a part of this with us.
08.
What’s next for ERP X?
After two years and 403 citizen testers, we concluded the ERP X experiment. At the time of writing, all cameras have been shut down. We return to the question: is there a different way to do ERP in Singapore?
We now know that the answer is yes. Camera-based road pricing does work, and we are able to address its three biggest unknowns:
Accuracy
We know that it can work accurately, across various environmental conditions.
Cost
We know how much it costs, and how to implement and scale it reasonably.
Citizen feedback
We know that users liked the solution.
But, ERP X will not be going ahead.
The government currently has no plans to roll out camera-based road pricing.
Nevertheless, testing the limits of the ANPR cameras in Singapore has been valuable. While they have already been deployed for other use-cases (Traffic Police’s enforcement of traffic violations, HDB’s barrier-free carpark entry system, and SPF’s detection of vehicles of interest), this is the first time that they have been validated as a viable alternative to road pricing.
With ERP X, policymakers can now weigh it seriously against the other options on the table.
This is especially so should the policy environment ever change. The transport landscape is complex and several bets are being made on what the future holds, many of which depend on predictions no one can make with certainty.
Take autonomous vehicle adoption: real-time data on every vehicle’s location could make camera-based congestion pricing obsolete. But no one knows if or when that will happen. Depending on which bets actually pay off, an option set aside today can suddenly look attractive tomorrow.
We've shared our findings with MOT and LTA
The ERP X experiment has produced something durable: a starting point that future camera-based solutions can build on, and a benchmark they can be measured against.
These findings are informing their explorations into what the future of Singapore’s transport policy can look like. Regardless of whether we ever implement camera-based road pricing, our work here is a step in that direction, and might even give Singapore a head start one day.
09.
Future of experimentation
OGP spent around $4.4 million running this two-year ERP X experiment. For less than 1% of the $556 million contract value of ERP 2.0, we ran a live, national-scale trial and got definitive answers on the technology and its limits before any commitment to build.
ERP X is evidence that testing whether a national infrastructure bet is worth taking, can cost very little relative to the bet itself.
The case for early prototyping
Committing to a build or calling for a tender without having tested anything in the real world carries significant risks. It requires near perfect foresight, and relies on the assumptions we make today still holding true by the time the product arrives.
But at the scale of national infrastructure, the things that can go wrong are exactly the things it cannot see coming. ERP X surfaced plenty of them: cameras that failed in ways no specification predicted, deployment problems that only appeared on real roads, citizen feedback that no one anticipated.
Prototyping is a hedge against imperfect plans. It is how we discover problems while they are still cheap to fix. Otherwise they surface later: as costly redeployments, delayed launches, or a public that rejects the thing on arrival.
Government is increasingly open to experimentation, but not for all projects. For national infrastructure, where the stakes are higher and where we need to get the solution right, we should be encouraging more prototyping, not less.
We should spend millions if it means avoiding billion-dollar mistakes.
ERP X and the future of experimentation
ERP X doesn’t just show that camera-based road pricing works.
It shows that government can safely prototype and stress-test national infrastructure, before committing to build it.
It shows that iterative prototyping works not only for digital products, but even for physical hardware.
It shows that ambition isn’t a barrier and that no domain is off-limits; that an experiment can begin with a webcam on a tripod and grow to span cameras across the island.
It shows how citizens can and should be brought in as collaborators at the earliest opportunity, not just as reviewers at the end.
And it shows that all of this can be done while documenting lessons openly, honestly, and in full view of the public. ERP X shows that there is a different way for government to approach problems.
This matters not only because of the promise of better outcomes, but for what it reflects: a government still willing to try, still capable of being surprised, and still not settled with the status quo.
Closing notes
This story was brought to you by the team behind ERP X: Amanda, Clement, Desmond, Jael, Je Min, Kee Hui, and Qilu.
Special thanks
To all the citizen testers of ERP X throughout the two-year experiment, whose contributions during testing helped validate the solution and whose insights helped shape this report. Thank you for your support, and for showing us that Singaporeans are willing to step up and take a leap of faith in experimenting with us. To our installation partners Deen, Max, William and countless others, for their expertise and hard work in tackling the challenges of unfamiliar hardware, and for all the late-night installations across various lamp posts and highways around the island. To the Ministry of Transport (MOT), Land Transport Authority (LTA), and National Parks Board (NParks) for their support in enabling live-site testing throughout the experimentation period. Thank you for supporting our efforts to experiment not only with technology, but also with new methodologies for building that could shape the future of transport policy.
OGP colleagues
To Hong, Nitya: thank you for the guidance, and for giving us the space to experiment with the format of this report. To Celine, Jessendra and Sabina: thank you for lending your expertise and encouragement, which helped to not only sharpen this report, but to also carry us through the harder stretches of getting here.
Past ERP X team members
Adan, Alicia, Amelia, Blake, Christabel, Darryl, Jenric, Justyn, Mike, Samuel and Stephanie: your hard work laid the foundations that we built upon. Thank you for blazing the trail.
If you’d like additional information
This report is accompanied by a set of Supporting Annexes, which contains additional information on the sources, definitions, and methodology behind this report. As part of OGP’s core mission, ethos and larger commitment to transparency around our work and the use of public funds, we publish report cards for all our products. Please see ERP X’s Report Card for more information on what the team at OGP worked on each quarter since 2024, and how much was spent (and on what).
If you’d like to carry on the conversation
For any media enquiries, please reach out to us at media@open.gov.sg or via this form. For all other general enquiries to the ERP X team, please reach out to us via this form. Please share with us any feedback you have about this report and how we presented it. Or tag OGP on our social media channels!
All figures in this report, including cost and accuracy estimates, are drawn from ERP X's own experimental conditions and are not guarantees of performance or pricing at national scale. Survey findings reflect a self-selected group of citizen testers and should be read as directional rather than representative. For this report, we collaborated with AI tools to assist with synthesis, prototyping and proofreading. All AI-assisted content underwent thorough review and evaluation. The final output accurately reflects our understanding, expertise, and intended meaning. We maintain full responsibility for the content, its accuracy, and its presentation. This disclosure is made in the spirit of transparency and to acknowledge the importance of AI diligence as an emerging best practice in professional work.