From the NVIDIA edition of November 3, 2026
ITMAX: SamurAI V2 on NVIDIA VSS and Cosmos runs on 1,000+ of 16,000+ Kuala Lumpur cameras; claims 70%+ better alert verification and 26% shorter peak corridor times
ITMAX System Berhad · Smart-city managed services / traffic management · Malaysia (Kuala Lumpur)
- Publisher
- ITMAX Newsroom
- Original publication
- 2026-11-03
- Source retrieved
- 2026-11-04
- Event date
- 2026-11-03
What happened
ITMAX, a Smart City-as-a-Service provider, described its NVIDIA stack: RTX PRO 6000 Blackwell for inference, H100 for fine-tuning, Jetson Orin at the edge. SamurAI V2 is built on the Metropolis VSS blueprint with Cosmos 3 fine-tuned on Malaysian roads; it runs on 1,000+ of 16,000+ managed cameras, with 10,000 planned in 2027. ITMAX claims alert verification accuracy improved by more than 70% and incident search time fell more than 90% in the first KL deployment. On 10 corridors with adaptive signals, peak travel time is 26% shorter on average; TeraSim simulation of a three-junction cluster cut delay 29.8 s per vehicle at about 700 vehicles/hour. City Maestro (Nemotron) agent runs on-demand simulations.
Why it matters
Gives transportation departments and traffic-management centres a concrete, partner-reported architecture for vision agents and simulation-tested signal timing. Transferability to U.S. DOTs and cities is limited: Malaysian legal context, a single managed-service vendor, and unaudited figures.
Evidence and measured results
Partner press release; no baseline period, methodology or independent evaluation for the 70%, 90% or 26% figures. The 1,300-hours citywide figure is an extrapolation from simulation.
Limitations and uncertainty
Self-reported metrics; '26% shorter' lacks a stated baseline; simulation results are not field results; non-U.S.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-04; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Traffic operations teams face many camera alerts and slow manual incident search and signal retiming.
- Stakeholders
- Traffic management centre manager
- DOT or city transportation director
- Procurement officer
- Discovery questions
- What is the current false-alarm rate and incident search time?
- Are signal timing changes simulated before deployment?
- Would a managed-service contract be acceptable?
- Value hypothesis
- Simulation-tested signal timing and alert verification may reduce delay and operator workload, to be measured locally.
- Potential engagement
- A baseline measurement and corridor pilot design.
- Unsupported claims
- 26% travel-time reduction in U.S. corridors
- 70% accuracy gain as a general benchmark
- Citywide 1,300-hour savings
Pre-sales engineering
Role takeaway
- Fit
- Fits agencies with dense camera networks and adaptive signal programs.
- Architecture and integration
- Edge Jetson to central GPU inference; VSS over camera streams; agent-triggered TeraSim simulations.
- Prerequisites
- Local labelled footage for fine-tuning
- ATMS/signal controller integration
- GPU capacity
- Constraints
- Single-vendor managed service
- Malaysian deployment context
- No published methodology
- Security
- Restrict video search access; separate traffic and law-enforcement uses.
- Proof of value
- Compare false-alarm rates before and after on the same cameras
- Field-validate simulated signal timing on one corridor
Delivery
Role takeaway
- Work
- Corridor pilot of AI alert verification and simulation-tested signal timing.
- Dependencies
- Camera and controller access
- Baseline data
- Vendor contract terms
- Ownership
- Traffic management centre.
- Skills and adoption
- Operators learn natural-language search and simulation requests.
- Governance checkpoints
- Use limited to traffic operations
- Data ownership and audit rights in contract
- Review before enforcement uses
- Acceptance criteria
- Proposal: measured false-alarm reduction vs 30-day baseline
- Proposal: corridor travel time measured before and after for 8 weeks
- Risks
- Unverified vendor metrics
- Scope creep into enforcement
- Lock-in
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Edge (Jetson Orin) plus central inference (RTX PRO 6000) and fine-tuning (H100) over operator-owned fibre; VSS blueprint for video reasoning; LLM agent orchestrating simulation.
Governance
Who approves, reviews and stays accountable for outcomes?
Long-term managed-service contracts concentrate operational control in one vendor; the city needs contractual audit and data-ownership rights.
Security and privacy
What data, permissions and controls need testing?
Press release is silent on facial recognition, retention and police access, which independent reporting says apply to the same camera network.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Natural-language video search may lower skill barriers for operators.
Procurement
What should contracts, pricing and exit terms secure?
Illustrates Smart City-as-a-Service: bundled compute, networking and applications under multi-year contracts (10-year DBKL contract per The Edge).
Operating model
Which teams own the service once it runs?
City buys outcomes as a service; vendor runs infrastructure.
Publication history
- 2026-11-03NVIDIA · Issue 594 resources
Stable resource ID: itmax-samurai-v2-kuala-lumpur-nvidia-vss-cosmos-traffic-20261103