⬢ National incident map · 2D satellite
3D button to tilt · Ctrl+scroll to zoom · auto-resets to 2D satellite after 5 min idle◉ 36 API links↗
Till date
Severity · 30 d
Response SLA · 30 d
accept ≤2 · advice ≤10⬢ Geo-intelligence · extruded State risk, cargo hubs, freight corridors
Drag rotate · Shift/right-drag pan · Scroll zoom · Double-click a State to fly inMap filters
Selection intelligence
Click an incident beam, a State or a hub on the map to see intelligence here.
Hotspot clusters (≤ 40 km)
Boundaries: embedded, simplified district/State GeoJSON (udit-001/india-maps-data, Census-2011-based, updated). Not certified by Survey of India; verify against official outline maps ↗ before any formal use. Hubs and corridor alignments are approximate and indicative. Works offline.
Case management · chemical road emergencies
Receive → classify → advise → update ERSS| Incident | State / district | Received (IST) | Event | Cargo | Level | Status | Accept |
|---|
Road tanker identification schematic
Click a markerSelect a marker on the tanker to see what the caller should look for and the questions to ask.
Caller interview script
Ask in this orderDaily incoming calls by severity
Stacked, IST daysWhen do incidents happen? Weekday × hour (IST)
Chemical Pareto · top cargo
Bars = cases · line = cumulative shareCalls by State / UT
Classification L1–L5
Case status
Time to accept (minutes)
SLA 2 minEvent type
Master calls register
| C-DAC incident ID | Received (IST) | State / district | Level | Status | Chemical / issue | Accept |
|---|
L1–L5 operator action matrix
Suggested; adapt to approved SOPCrisis-group hierarchy · Chemical Accidents (EPPR) Rules, 1996
Regulatory framework · road transport of hazardous goods
Emergency numbers & escalation
🔗 How a Smartflo call is hooked to its ERSS ticket · design
Hooks A–E in priority order📦 Dual-channel intake → one case packet · Tata Smartflo calls + ERSS tickets
Live counts · click a blockCall routing & surge control · Nicer Globe national control room (cloud contact centre)
Live counts · last 24 h · click a block112 integrationNG control roomSurge / volume controlResponders
Isometric system tiers
📦 Intake packets across 36 State/UT integrations · three sections
☎ call only · 🎫 ticket only · ☎+🎫 call plus ticketAll 36 State / UT endpoints
| State / UT | Code | Region | Link | Last success (IST) | Latency |
|---|
Network topology · tilted ring
Packets animate on live linksAll 36 jurisdictions · language assistance & local risk
Languages indicative, not comprehensiveMessage sequence · C-DAC ERSS ⇄ LCS NG
Proposed contractInbound · C-DAC → NG
Incoming events should be accepted by a secured backend, validated, de-duplicated by source + incident ID, then pushed to the browser by WebSocket or server-sent events.
Status update · NG → C-DAC
Use the exact C-DAC status keys. The backend substitutes managed credentials and submits to the approved endpoint. This prototype only prepares JSON.
Suggested LCS backend contract
POST /api/cdac/inboundReceive validated webhook payload from an authorized sourceGET /api/incidentsCurrent cases and authorized State mappingPOST /api/incidents/:id/statusValidate and queue a status update to C-DACGET /api/integrations/healthReal monitoring signals for all 36 integrationsGET /api/eventsAuthenticated SSE/WebSocket stream for live incoming callsPOST /api/incidents/:id/ackRecord operator acceptance of the referralPOST /api/ingest/ticketImplemented. ERSS / State API tickets (EMERGENCY_CALL JSON) · header X-LCS-KeyPOST /api/ingest/smartfloImplemented. Tata Smartflo webhooks (JSON or form) · ringing/answered/ended/CDR · X-LCS-KeyPOST /api/packets/link · /unlinkImplemented. Operator confirms or separates a call ↔ ticket matchGET /api/eventsImplemented. Server-sent events: live push of new tickets, calls and mergesProposed internal interfaces, not claims about existing C-DAC endpoints. Treat authId/authCode as secrets: never send them to the browser; verify origin, rate-limit, and keep an immutable audit trail. Implemented today by server.py: GET/POST /api/cases, GET /api/analytics.
Receiving APIs
| State / UT | Receiving URLs (give these to C-DAC) | Client id | Client secret | authId / authCode | Allowed addresses | Last received | |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Register a State's Reverse API
Secret fields: leave blank to keep what is stored.
Registered States
| State / UT | API URL | User id | Credentials | Sending | Last test |
|---|
Register DID numbers
| Number | Label | Primary (caller ID) |
|---|
All State lines
| State / UT | DID numbers | C2C key |
|---|
| Group | Setting | Current | New value | |
|---|---|---|---|---|
| Loading… | ||||