Skip to content
MargRakshak AI — Roadside Hazard Detection NetworkPre-pilot · Corridor New DelhiSpec v3.0 · Build 2026.11
MRAI logo
MRAI
by UniWebs
All clear
14ms
Document register

Operational Procedures

How incidents are triaged, escalated, and closed, and how nodes are maintained.

Document
MRAI-DOC-004
Revision
Rev. 1.1
Effective
2026-08-27
Classification
Operational

01 · Triage

An operator reviews open incidents at least once per shift, filtering by severity and acknowledgement state.

Acknowledging an incident claims it. The operator's identity and timestamp are recorded.

02 · Escalation

Escalate per the matrix on the governance section of this register. Critical incidents are verified against the node's recent readings before any external notification.

A confirmed collision is reported to emergency services (108 / 112). MRAI does not dispatch; it informs.

03 · Resolution

An incident is resolved with a closing note describing what was observed and what action was taken.

Auto-resolution applies only when the underlying sensor condition clears and the node keeps reporting.

04 · Node maintenance

A node offline beyond 24 hours generates a field task: check power, check enclosure, check antenna, re-seat sensors, then replay buffered packets.

Device keys are rotated after any enclosure is opened by someone outside the project.

Issued by UniWebs — Kavy (software) & Saksham (hardware)
Operator of record
UniWebs — Kavy (software) & Saksham (hardware)
Independent student-run studio · not a government body
Enquiries
operations@projectmrai.in
Revision
Spec v3.0 · Build 2026.11
Last reviewed 2026-11-02