CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/Urban & City Planning

πŸŒ† Urban & City Planning Β· Data Flow

Adaptive Traffic Management Data Flow

How an adaptive traffic system uses cameras and sensors to time signals, spot congestion and catch violations.

More Urban & City Planning templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Vehicle counts adjust signal timings junction by junction
  • Congestion and incidents appear in the control room
  • Violations become e-challans automatically

Prompt used

Data flow for adaptive traffic management: junction cameras and loop detectors send vehicle counts to an edge analytics unit at each junction, which adjusts signal timing through the signal controller and sends aggregated data to the central traffic management server. The server detects congestion and incidents for the traffic control room, publishes travel times to navigation apps and variable message signs, and sends red-light and speed violations with number plate images to the e-challan system.

Mermaid code
flowchart LR
subgraph EXT ["External entities"]
cams["Junction Cameras"]
loops["Loop Detectors"]
sig["Signal Controllers"]
room["Traffic Control Room"]
signs["Variable Message Signs and Navigation Apps"]
echallan["E-challan System"]
end
subgraph PROC ["Processes"]
p1("1.0 Count vehicles at the junction")
p2("2.0 Adapt signal timing")
p3("3.0 Detect congestion and incidents")
p4("4.0 Publish travel times")
p5("5.0 Detect violations")
p6("6.0 Send violations for e-challan")
end
subgraph STORE ["Data stores"]
d1[("D1 Traffic Data")]
d2[("D2 Signal Timing Plans")]
d3[("D3 Violation Evidence")]
end
cams -->|"Video"| p1
loops -->|"Vehicle counts"| p1
p1 -->|"Counts and queue lengths"| p2
d2 -->|"Timing plans"| p2
p2 -->|"Signal timing"| sig
p1 -->|"Aggregated traffic data"| d1
d1 -->|"Traffic data"| p3
p3 -->|"Congestion and incident alerts"| room
d1 -->|"Speeds per segment"| p4
p4 -->|"Travel times"| signs
cams -->|"Red-light and speed events"| p5
p5 -->|"Plate images and evidence"| d3
d3 -->|"Violation records"| p6
p6 -->|"Violations with plate images"| echallan

Inside this diagram

A data flow diagram with 12 processes and outside parties, 3 data stores and 14 data flows.

Processes and outside parties

  • Junction Cameras
  • Loop Detectors
  • Signal Controllers
  • Traffic Control Room
  • Variable Message Signs and Navigation Apps
  • E-challan System
  • 1.0 Count vehicles at the junction
  • 2.0 Adapt signal timing
  • 3.0 Detect congestion and incidents
  • 4.0 Publish travel times
  • 5.0 Detect violations
  • 6.0 Send violations for e-challan

Data stores

  • D1 Traffic Data
  • D2 Signal Timing Plans
  • D3 Violation Evidence

Data flows

  • Junction Cameras β†’ 1.0 Count vehicles at the junction: Video
  • Loop Detectors β†’ 1.0 Count vehicles at the junction: Vehicle counts
  • 1.0 Count vehicles at the junction β†’ 2.0 Adapt signal timing: Counts and queue lengths
  • D2 Signal Timing Plans β†’ 2.0 Adapt signal timing: Timing plans
  • 2.0 Adapt signal timing β†’ Signal Controllers: Signal timing
  • 1.0 Count vehicles at the junction β†’ D1 Traffic Data: Aggregated traffic data
  • D1 Traffic Data β†’ 3.0 Detect congestion and incidents: Traffic data
  • 3.0 Detect congestion and incidents β†’ Traffic Control Room: Congestion and incident alerts
  • D1 Traffic Data β†’ 4.0 Publish travel times: Speeds per segment
  • 4.0 Publish travel times β†’ Variable Message Signs and Navigation Apps: Travel times
  • Junction Cameras β†’ 5.0 Detect violations: Red-light and speed events
  • 5.0 Detect violations β†’ D3 Violation Evidence: Plate images and evidence
  • D3 Violation Evidence β†’ 6.0 Send violations for e-challan: Violation records
  • 6.0 Send violations for e-challan β†’ E-challan System: Violations with plate images

Boundaries

  • External entities: Junction Cameras, Loop Detectors, Signal Controllers, Traffic Control Room, Variable Message Signs and Navigation Apps and E-challan System
  • Processes: 1.0 Count vehicles at the junction, 2.0 Adapt signal timing, 3.0 Detect congestion and incidents, 4.0 Publish travel times, 5.0 Detect violations and 6.0 Send violations for e-challan
  • Data stores: D1 Traffic Data, D2 Signal Timing Plans and D3 Violation Evidence

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

C4 ArchitectureProUrban & City Planning

Smart City Platform Architecture

An integrated smart city platform: sensors and city systems feeding a central data platform that runs the command centre and citizen services.

FlowchartUrban & City Planning

Online Building Plan Approval

How a city approves building plans online with automated checks: submission, auto-scrutiny against bye-laws, department NOCs and sanction.

MindmapUrban & City Planning

Urban Planning Services Map

A map of the main areas city planners work on and the data and systems behind each one.

SequenceUrban & City Planning

Smart Parking Sequence

How a smart parking system guides a driver to a free space: sensors, a parking app, reservation, entry by number plate and automatic payment.

Data FlowUrban & City Planning

Smart Waste Collection Data Flow

How a city optimises garbage collection: bin fill-level sensors, truck GPS, route planning and citizen complaints.

SequenceUrban & City Planning

Online Property Tax Payment Sequence

How a citizen pays property tax to the city online: property lookup, assessment, payment and receipt.