Automations

Scheduled and event-driven operating loops

Automations prove this is more than a chat interface. Each run creates a record, links to cases, recommends next action, and appears in the audit trail.

Scheduled Jobs

Cron-based officer and department loops

Event Triggers

Complaint spikes, utility thresholds, and sensitivity events

Runs Today

Every run is linked to case state and audit logs

Attention Runs

Runs that surfaced officer action requirements

Run status

Automation runs on March 6, 2026

Chart loads after page mount.

What each automation does

Mandatory behaviors

Create or update a case.

Draft a summary and notify the relevant view.

Propose the next action, but do not imply completion without a log.

Write the run into automation history and audit events.

Scheduled jobs

Officer brief and monitoring cadence

7:00 AM IAS Brief

Summarize top decision items across service backlog, project slippage, deadline risk, and public-risk signals.

0 7 * * *

Timezone Asia/Kolkata. Last run 2026-03-06T07:00:00+05:30.

8:00 AM IPS Brief

Summarize police, traffic, cyber, and public-order hotspots with sectors needing watch.

0 8 * * *

Timezone Asia/Kolkata. Last run 2026-03-06T08:00:00+05:30.

Every 30 min SLA Monitor

Detect nearing deadlines for grievances, RTI, and unresolved cases.

*/30 * * * *

Timezone Asia/Kolkata. Last run 2026-03-06T09:00:00+05:30.

Every 60 min Project Risk Scan

Find project delays, milestone slippage, and risk of public blowback.

0 * * * *

Timezone Asia/Kolkata. Last run 2026-03-06T09:00:00+05:30.

48-hour Closure Verification

Re-open or flag cases where closure lacks verification evidence.

Timezone Asia/Kolkata. Last run 2026-03-05T18:00:00+05:30.

Event-driven triggers

Signals that open or update cases

Complaint spike in one sector

enabled

Complaint volume threshold crossed inside one geography

Create or merge a case, notify the officer view, and recommend next action.

Utility anomaly over threshold

enabled

SCADA anomaly above threshold

Open or update a utility-linked case and request verification.

VIP / protest / traffic sensitivity event

enabled

VIP, protest, or traffic risk signal arrives

Move the geography into active control-room watch and publish a coordination note.

Project milestone slipped plus complaint rise

enabled

Project delay combined with citizen complaint growth

Open a project exception case and queue a review brief.

Recent runs

Inputs, outputs, and linked cases

Every 30 min SLA Monitor

requires decision

Input: {"sourceRecordIds":["SRC-JS-SLA-01","SRC-SAM-SLA-02"]}

Output: {"result":"Two filings remain inside the officer attention window."}

Linked cases: CASE-SLA-014

Project milestone slipped plus complaint rise

completed

Input: {"sourceRecordIds":["SRC-SMART-PROC-01","SRC-SMART-PROC-02"]}

Output: {"result":"Project exception case queued for Monday review."}

Linked cases: CASE-PROC-009

Utility anomaly over threshold

completed

Input: {"sourceRecordIds":["SRC-UTIL-056-03"]}

Output: {"result":"Utility anomaly attached to CASE-OPS-056 and feeder follow-up created."}

Linked cases: CASE-OPS-056

VIP / protest / traffic sensitivity event

completed

Input: {"sourceRecordIds":["SRC-POL-IPS-02"]}

Output: {"result":"CASE-IPS-021 pushed into active control-room watch."}

Linked cases: CASE-IPS-021

8:00 AM IPS Brief

completed

Input: {"casesConsidered":["CASE-IPS-021"]}

Output: {"brief":"Sector 17/22 moved to active watch for the 8:00 AM IPS brief."}

Linked cases: CASE-IPS-021

Complaint spike in one sector

completed

Input: {"sourceRecordIds":["SRC-SAM-056-01","SRC-JS-056-02"]}

Output: {"result":"Merged service and grievance spike into CASE-OPS-056."}

Linked cases: CASE-OPS-056

7:00 AM IAS Brief

completed

Input: {"casesConsidered":["CASE-OPS-056","CASE-SLA-014","CASE-PROC-009"]}

Output: {"brief":"Five matters requiring decision were published to the Officer Brief."}

Linked cases: CASE-OPS-056, CASE-SLA-014, CASE-IPS-021, CASE-PROC-009, CASE-ENV-004