A Geographic Information System (GIS) for smart city operations turns scattered municipal data into a single live map of the city, so departments act on current conditions instead of last month’s reports. In India, that capability sits inside Integrated Command and Control Centres (ICCCs), where spatial layers, sensor feeds, and field reports converge into dashboards that let officials see and manage services ward by ward.
Real-Time Governance in India’s 100 Smart Cities
All 100 cities selected under the Smart Cities Mission set up an ICCC before the Mission closed on 31 March 2025. The Government of India launched it on 25 June 2015 and picked those cities through successive rounds between 2016 and 2018. The control rooms remain in daily use.
The Ministry of Housing and Urban Affairs (MoHUA) describes each ICCC as the brain and nerve center of day-to-day city management. These centers support crime tracking, citizen safety, traffic, solid waste, and water supply from one room, pulling in departments that historically never shared a screen. The question for administrators has moved from whether to build a control room to what it should show.
What Is Real-Time GIS for Smart City Operations?
Real-time GIS streams live data onto a spatial framework so location, status, and time stay visible together. A static map tells an official where the bins are. A real-time map tells them which bins are full right now, which collection vehicle sits closest, and which ward the crew missed twice this week.
Static layers establish the baseline: ward boundaries, road networks, water and sewer lines, health and education facilities. Live feeds attach current state to those features through sensors, vehicle trackers, and citizen reports. Analysis closes the loop, turning that picture into a decision such as rerouting a vehicle or dispatching an inspection.
India’s ICCC Backbone: MoHUA’s Mandate for 100 Smart Cities
An ICCC is the physical and digital hub where a city’s data streams meet. Interdepartmental coordination defines it. Traffic police, health, water, solid waste, and irrigation departments feed the same operational picture, which separates an ICCC from parallel departmental systems.
ICCC designs commonly include a link to the criminal database under the Crime and Criminal Tracking Networks and Systems (CCTNS). That linkage supports surveillance, citizen safety, and crime resolution across police stations while feeding a centralized citizen portal.
The spatial layer makes an ICCC legible. Video walls and data tables show volume, but a map shows distribution. When a city needs to know whether a service failure is isolated or systemic, the answer is geographic before it is statistical.
The ArcGIS Workflow Behind Real-Time City Dashboards
A control room is a chain of decisions, not a screen. Following one overflowing bin through that chain makes each component concrete. This describes capability rather than a record of installations.
The authoritative layer has to sit somewhere defensible
Surveillance footage, utility alignments, and citizen complaint records rarely clear the bar for a public cloud. Cities keep the system of record on their own infrastructure with ArcGIS Enterprise instead. The harder question is what fills it on day one. Building ward boundaries, road networks, and facility layers from scratch usually consumes the first year of a project, which is why ready-made Indian content from Indo ArcGIS Living Atlas matters: the city already has ward boundaries and road networks to work with, so teams can start making updates right away instead of building that data from zero.
A reading only counts once something acts on it
Bin sensors, vehicle trackers, and air quality monitors push thousands of readings an hour, and almost all of them are unremarkable. ArcGIS Velocity holds that stream against rules the city sets, running in ArcGIS Online so the operator sees the twelve bins above threshold rather than the four thousand that reported normally. Cities guarding sensitive layers process the stream in the cloud and land only the results on premises.
Routing decides whether the alert is worth anything
Knowing which bin is full solves nothing if the nearest vehicle sits on the wrong side of a one-way stretch. ArcGIS Network Analyst calculates routes and service areas using real street data, including turn restrictions and travel times. This shows the difference between a route that looks short on a map and one a driver can actually complete.
The same engine answers the question a commissioner asks: which wards fall outside an acceptable response radius, and where a new depot would close the gap.
Ground truth comes from people, not only sensors
Inspectors and residents see what no meter captures, including a blocked drain, a sensor knocked off its mount, or a bin moved to the next street. ArcGIS Survey123 turns those reports into structured records with location attached, so a complaint becomes a point on the map rather than a line in a register. Publishing outward closes the loop, with ArcGIS Hub exposing the same datasets to residents and developers and ArcGIS StoryMaps explaining what the numbers mean to the many more people who will never open a dashboard.
The screen is the last mile, and it is role-specific
A zonal officer needs today’s failures in their wards, a commissioner needs the pattern across the city, and a standing committee needs one defensible number. ArcGIS Dashboards builds all three from the same layers, filtered by role, which heads off the familiar failure where every department arrives at the meeting with its own spreadsheet.
See how Esri India supports urban operations and planning for smart cities.
Inside Varanasi’s Kashi GeoHub Operations Dashboard
Varanasi Smart City Limited (VSCL) built Kashi GeoHub as an open geospatial platform, and it remains one of the most documented Indian examples of the approach.
Dr. D. Vasudevan, Chief General Manager at VSCL, presented the work internationally alongside Dr. Ruma Chakrabarty, Urban Expert at Esri India.
Baseline layers came before the sensors
VSCL created and published spatial layers covering ward boundaries, public services, education and health facilities, transportation, water bodies, sewage drainage, and surveillance camera locations. Every department now works from a common base map instead of competing versions of the city.
Sensors made those layers live
VSCL connected the GIS layers to sensor feeds through application programming interfaces (APIs) covering solid waste management, pollution, safety, and traffic control. Smart bins report fill status ward by ward, which supports collection routing built around the bins that need emptying rather than a fixed daily circuit. The platform also tracks the working status of traffic lights.
The platform extends past the control room
Kashi GeoHub runs on ArcGIS Hub and publishes open data, thematic maps, and APIs for developers, alongside crowdsourcing applications that let residents contribute to civic initiatives. The portal serves multiple languages and hosts a story map on disabled-friendly cities.
Breaking Data Silos: IUDX, NUDM, and Interoperability
A dashboard is only as good as the data it can reach, and municipal data has historically sat trapped inside individual departments and vendor systems. MoHUA and the Ministry of Electronics and Information Technology (MeitY) launched the National Urban Digital Mission (NUDM) in February 2021 to address this, building shared digital infrastructure across three pillars: people, process, and platform.
The India Urban Data Exchange (IUDX) matters most for real-time operations. The Indian Institute of Science (IISc), Bengaluru, developed it with the Smart Cities Mission, creating a common interface where data providers and users, including urban local bodies, share and request city datasets. IUDX targets silos both within and across cities, and leaves data owners in control of what they share.
The IUDX city directory now lists more than 50 partner cities, including Varanasi and Surat. That reach matters for a city running an ICCC, because an exchange lets the city pull mobility or environmental data it does not own, and publish its own without building a bespoke integration each time.
Beyond the Pilot 100: Scaling Real-Time Operations to Smaller Towns
The original mandate covered 100 cities. NUDM targets every city and town in India rather than a selected list, and two mechanisms make that plausible for smaller urban local bodies with thin budgets and thinner GIS teams.
SmartCode lowers the build cost
The repository offers open-source code for urban governance applications at no charge, so a Tier-2 municipality adapts a working solution instead of commissioning one from scratch. Procurement shrinks to a configuration exercise.
Shared platforms remove the hosting burden
A town that cannot staff a control room can still run a hosted dashboard and a citizen-facing data portal, monitoring waste collection and water supply without the capital cost of a full ICCC. Hosting costs shift from capital to subscription.
MoHUA launched the Geospatial Management Information System (GMIS) alongside NUDM to monitor mission projects, and it points the same way. Spatial monitoring is becoming the default reporting format for urban programs, which pushes smaller cities toward it regardless of local capacity.
Challenges and the Road Ahead
Interoperability is a governance problem before a technical one
IUDX solves the exchange mechanism, but departments still need to agree which asset register carries authority and who updates it. Water supply and property tax departments routinely hold different versions of the same layer, each correct for its own purpose and incompatible with the other. Until a city names a single custodian per dataset, the dashboard inherits those disagreements and ends up precise and wrong.
Base layers go stale faster than cities refresh them
Ward boundaries change, new colonies come up, and agencies realign roads, while the base map beneath them follows no fixed update schedule. A live sensor feed on an outdated network snaps to the wrong segment, so the dashboard reports a real problem in the wrong place. A defined update cycle with a named owner fixes that, and field apps turn every inspection into a chance to correct the base data.
Sensor networks decay quietly
On a dashboard, a bin sensor that has stopped reporting looks identical to a bin that is empty, and the same holds for vehicle trackers that drift or flow meters that stick. Real-time operations therefore depend on monitoring the instrumentation as closely as the service, treating last-reported timestamps as a metric. A panel showing which sensors have gone silent often beats the one showing what the rest report.
Real-time data does not produce real-time response
A dashboard refreshing every minute delivers nothing if the work order behind it takes three days to close. Cities have to redesign detection and response together, which means revisiting who can dispatch and what triggers an escalation. Shortening only the detection side builds a backlog, and staff learn to ignore alerts they cannot act on.
Citizen data now comes with statutory obligations
ICCC feeds aggregate surveillance footage, service complaints, and location traces that qualify as personal data. India’s Digital Personal Data Protection Rules, 2025 took effect in November 2025, with core duties on data fiduciaries applying from May 2027. Cities running an open data portal alongside an operational dashboard need defensible lines between published, internal, and consent-bound data.
Capacity and funding decide what survives handover
An ICCC that changes hands at the end of a contract needs municipal staff who can edit layers, adjust thresholds, and publish dashboards without raising a change request. Recurring costs for licenses, connectivity, and sensor replacement have to sit in the municipal budget, not a time-bound project line. Where neither the skills nor the money move across, systems degrade into video walls displaying data nobody acts on.
Expectation now drives this shift as much as policy does. Residents who can track a food delivery in real time will not accept opacity about when their street last saw a sweeper or why their water supply failed. A city that can answer those questions on a map, ward by ward, governs differently from one that answers them a month later in a report.
FAQs
1.What is real-time GIS in a smart city context?
Real-time GIS streams live data such as sensor readings, vehicle locations, and citizen reports onto a spatial framework so status and location stay visible together. City staff act on current conditions rather than reviewing what happened after the fact.
2.What is an Integrated Command and Control Centre (ICCC)?
An ICCC is the central hub where a city’s data streams and departments converge for coordinated operations. All 100 cities under the Smart Cities Mission set one up, and MoHUA describes the ICCC as the brain and nerve center of day-to-day city management.
3.Which ArcGIS products power smart city operations dashboards?
A typical stack uses ArcGIS Enterprise to host authoritative data, ArcGIS Velocity for live sensor feeds, ArcGIS Network Analyst for routing, and ArcGIS Dashboards for the operational view. ArcGIS Survey123, ArcGIS Hub, and ArcGIS StoryMaps handle field collection and citizen-facing publishing.
4.How does the India Urban Data Exchange (IUDX) support ICCCs?
IISc Bengaluru developed IUDX as an open-source exchange that lets cities and urban local bodies share and request datasets through a common interface. It breaks data silos within and across cities, so an ICCC can consume data it does not own while controlling what it shares.
5.What are the main challenges to real-time GIS adoption in Indian cities?
The recurring obstacles are governance rather than software: agreeing which datasets carry authority, maintaining sensor networks that fail silently, and building municipal staff capacity that survives contract handover. Funding continuity after mission timelines end remains a persistent risk.
Written by
Esri India Marketing
