Skip to content
Solutions · Digital Twin

Open the geography first.

Every campaign, grievance, survey, event, community signal, media narrative and field report attaches to a geographic unit and becomes part of that place's timeline. That is what makes the picture add up rather than fragment across departments.

Hierarchy

Eight levels, configurable per deployment

Administrative structures differ by country and by state, so the hierarchy is configuration rather than code. What stays constant is that aggregation follows the tree: a ward's numbers roll into its district, and a district's into its state, without anyone maintaining a spreadsheet of mappings.

  • Drill from territory to booth without changing tools
  • Roll-up is automatic and consistent across modules
  • Optional intermediate levels where a state needs them
  • Geometry stored alongside the identifier
New DelhiMumbaiKolkataChennaiBengaluruGuwahatiAhmedabadHyderabad
Digital Twin

Live civic data across regions

Real-Time

Feedback & signals

AI Insights

Detect trends & understand communities

Actionable Insights

Drive better outcomes

Canonical levels

The default hierarchy

Canonical geographic unit types
LevelCanonical typeTypical use
1CountryNational view and territory-wide indicators
2State / ProvinceState headquarters control room
3DistrictAdministrative or programme district
4Parliamentary constituencyNational representative area
5Assembly constituencyLegislative seat area
6Block / Mandal / City zoneOptional intermediate unit
7Ward / Local unitWard, panchayat, village cluster, municipal unit
8Booth / PrecinctLowest operational field unit

Capabilities

What the twin service maintains

GeoUnit as a first-class entity

Every relevant record references a geographic unit and, where useful, a precise geometry. Aggregation follows the parent-child tree automatically.

  • Configurable hierarchy per deployment
  • PostGIS-compatible geometry
  • Records roll up without manual mapping

State plus snapshots

Each unit holds a current state vector and periodic snapshots, so any two moments can be compared directly rather than reconstructed.

  • Current state always available
  • Periodic historical snapshots
  • Before/after comparison built in

Confidence and provenance

Every score carries a confidence value and the sources behind it, so sparse or biased data is visible rather than smoothed away.

  • Freshness and coverage weighting
  • Source diversity accounted for
  • Model version recorded

Event-driven updates

Domain services publish normalized events; the twin service consumes them and maintains state. Dashboards read from query-optimized stores.

  • Real-time updates over WebSocket/SSE
  • Append-only event history
  • Last-known state on source failure

In practice

How a analyst actually uses it

  1. 01

    Open the geography

    Start from the territory view and select any unit. The map, indicators, alerts and lists all rescope together.

  2. 02

    Read the state vector

    Mood, issue state, service state, feedback state, organisation activity and data quality for that unit.

  3. 03

    Follow the change

    Every indicator is drillable to the timeline of events and the individual records that moved it.

  4. 04

    Compare two moments

    Pull a snapshot from before an intervention and compare it against the current state.

  5. 05

    Check the confidence

    See how much data sits behind the reading, and where coverage is thin enough to hold the conclusion loosely.

  6. 06

    Act in place

    Assign work, open a corrective action or brief a team without leaving the geographic context.

Ready to transform civic outcomes?

See how Civiq.plus can help your teams make better decisions, faster.