SANKALP / PHED HARYANA / LIVE DEMO
OPERATIONAL OVERVIEW
Review urgent cases first. Explore the evidence before taking action.
Illustrative composite of data completeness, freshness, model agreement and validation coverage. This is a demo score, not a calibrated reliability measure.
Why it mattersA quick indication of the available evidence, not permission to automate a decision.
Officer actionReview evidence and governance before approving an intervention.
Safety first, then incident priority. Each action opens its case for officer review.
Possible contamination near school
Collect an approved sample and verify the reported exposure before determining the response. 8 linked demo reports support review.
Uncertainty: Water-quality results and exposure are unverified.
Approval: Water-quality officer approval; emergency protocols remain authoritative.
Low pressure across Wards 11–12
Compare endpoint pressure with feeder readings and inspect the linked valve. 23 linked demo reports support review.
Uncertainty: A common root cause is inferred, not established.
Approval: Engineer approval before changing valve or pump settings.
Leakage along distribution main
Confirm the reported leak and check the asset record before proposing isolation. 14 linked demo reports support review.
Uncertainty: Leak rate, location and pipe condition are unverified.
Approval: Engineer approval before isolation or repair.
Count of synthetic incidents in the current demo worklist.
Why it mattersGrouped incidents in this worklist
Officer actionReview the case list below; open an incident to inspect its evidence.
Synthetic service-area reach, deduplicated across local split groups from the same original incident. Cross-area overlap is unknown.
Why it mattersEstimated reach across listed cases
Officer actionReview the case list below; open an incident to inspect its evidence.
Count of synthetic incidents in the current demo worklist.
Why it mattersRequires officer validation
Officer actionReview the case list below; open an incident to inspect its evidence.
Illustrative trends · District figures calculated from the demo worklist
DEMAND OUTLOOK
Synthetic hourly complaint series and illustrative forecast values. Not a trained model or a live operational feed.
Why it mattersCompare observed activity with a possible future trajectory.
Officer actionReview forecast assumptions before planning resources.
DISTRICT COMPARISON
District totals aggregated from listed synthetic incidents. People estimates may overlap; complaints are linked reports, not unique citizens.
Why it mattersCompare the scale of the current worklist across districts.
Officer actionReview high-impact cases before allocating field teams.
All 4 listed incidents · Not affected by queue search
REVIEW PRIORITY
Priority values supplied with the synthetic incident records; scores are not probabilities or validated risk estimates.
Why it mattersCompare case urgency without hiding the underlying score.
Officer actionSafety flags override numeric ranking. Open the queue below to review evidence.
Safety alerts first, then highest priority.
Synthetic grievance clusters, sorted by safety flag then priority score.
Why it mattersFocuses review on cases with the greatest potential consequence.
Officer actionOpen a case, check the evidence, and choose the appropriate response.
Mixed-scale analysis of demo records. Historical examples and model illustrations are labelled separately.
Six dated synthetic history records, distinct from the four-case worklist.
Why it matters / next actionInspect the outlook
Service-area reach deduplicated across split groups from the same source incident. Cross-area overlap is unknown.
Why it matters / next actionLocate affected districts
Reach of demo incidents marked Safety. Does not establish actual contamination or exposure.
Why it matters / next actionValidate safety evidence
Confidence labels in static demo records; not calibrated probabilities.
Why it matters / next actionInspect confidence limits
Complaint counts grouped by issue from the four incident records.
Why it matters / next actionReview issue evidence
Deterministic model for HR-W-042: 6-hour delay, 40% assumed effectiveness. Not observed operational outcomes.
Why it matters / next actionBuild a response scenario
Records whose recurrence field identifies an occurrence within a prior period.
Why it matters / next actionInvestigate repeat incidents
Counts derived from matching complaint records across the five BRD intake channels. SNK is the convergence system, not a sixth citizen channel.
Why it matters / next actionReview source coverage
Three deterministic recommendation templates are generated for each of four incidents.
Why it matters / next actionChoose a reviewed action
Browser-local action tracker, read when the overview opens. Not server-synchronised.
Why it matters / next actionManage assigned plans
Local calendar date compared with deadlines in browser-local actions; not an SLA measure.
Why it matters / next actionReview overdue plans
Completed local action records. Outcomes are officer-entered, not independently verified.
Why it matters / next actionInspect completion evidence
Priority values in synthetic incident records. Safety override takes precedence over the score.
Why it matters / next actionInspect priority decisions
The app has six illustrative overlays but no verified operational geographic dataset.
Why it matters / next actionInspect map assumptions
Briefing combines sorted demo incidents and locally stored action status. No live change detection.
Why it matters / next actionOpen the officer briefing