NVIDIA Public Sector United States

City of Raleigh

Real-time Analytics

Raleigh needed to improve congestion management, mobility, and street safety as the city grew, but manual traffic counts and disconnected sensor repositories made it hard to visualize conditions, respond to incidents quickly, or plan infrastructure changes proactively.

$9.7 million annually in time and fuel costs
4x faster analytics and insights
55,000 vehicles a day at peak
95% vehicle detection and trajectory accuracy

Reported impact

Business outcome

Raleigh achieved 95 percent vehicle-detection accuracy, boosted a 2.5-person traffic-engineering team's analytical capacity by 4x, identified a path to save commuters an estimated $9.7 million annually, and built a scalable city platform that will expand with 1,000 more cameras and broader public-safety use cases.

  • Cost Reduction
  • Productivity Improvement
  • Risk Reduction
  • Scalability

Solution

Raleigh combined NVIDIA smart-city AI with its geospatial digital twin to create a real-time traffic and urban-operations platform. NVIDIA DeepStream, part of the NVIDIA Metropolis suite, performs video analytics for vehicle counts, trajectory tracking, and other traffic observations at key intersections. Those live signals are integrated with Esri ArcGIS on Microsoft Azure, which powers the city's digital twin and lets engineers visualize traffic, pedestrian, and bicycle flows inside a 3D map for scenario simulation and event planning. The city is also testing NVIDIA Blueprint for video search and summarization to automate incident understanding through vision-language agents that detect hazards and generate text descriptions under live video feeds. Together, these layers connect sensor data, geospatial context, and AI alerting so Raleigh can move from reactive operations to predictive, citywide traffic and safety management.

Data flow

Traffic video and sensor feeds are analyzed by DeepStream and related AI agents, the resulting vehicle and incident signals are pushed into Raleigh's ArcGIS digital twin on Azure, and planners and operators use the live 3D map to visualize congestion, simulate scenarios, and trigger faster operational responses.

Solution architecture

5 components · 2 layers
  1. Compute
    • Microsoft Azure Hosts the ArcGIS-based digital twin and cloud analytics operations platform used to scale city services.
  2. Serving
    • NVIDIA Metropolis Provides the broader smart-city vision AI suite behind Raleigh's traffic and safety analytics.
    • NVIDIA DeepStream Runs real-time video analytics for vehicle counting, trajectory tracking, and intersection monitoring.
    • NVIDIA Blueprint for video search and summarization (VSS) Enables AI agents to interpret incidents and generate live textual summaries from video feeds.
    • Esri ArcGIS Powers the city's geospatial digital twin and interactive visualization environment.

Architecture clues

  • DeepStream-generated vehicle counts and trajectories are merged with geospatial context rather than analyzed in isolation.
  • Raleigh uses a digital twin on ArcGIS and Azure as the central visualization layer for traffic intelligence.
  • The city is extending the same platform to flood detection, parking utilization, asset conditions, and other civic domains.

Evidence from the source

DeepStream achieving 95% accuracy in vehicle detection for turning movement counts.
Following the NVIDIA Blueprint for smart city AI, alongside Esri's ArcGIS geospatial platform that powers the city's digital twin on Microsoft Azure, Raleigh is transforming real-time urban management.
It also boosts the analytical capabilities of Raleigh's team of just 2.5 dedicated staff by 4x.
Potential to save commuters an estimated $9.7 million annually in time and fuel costs.
Raleigh adopted NVIDIA DeepStream, part of the NVIDIA Metropolis suite of vision AI tools.
Transparency Evidence & methodology 100/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. NVIDIA

    City of Raleigh customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/raleigh-smart-city/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Jan 28, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Sep 1, 2026 · NVIDIA · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.