DPR Part F · Programme governance
Admin Management System
PM-SETU project and task management, plus scheme-tagged grievance redressal across SIDH, CPGRAMS and the PM-SETU portal.
Overview
What this module does
Two sub-modules on one platform: (i) PM-SETU Project Management — planning, assignment, tracking and monitoring of all programme work by SPMU, PMU, State and partner teams; (ii) Grievance Management — unified, scheme-tagged redressal.
Existing grievance portals are reused: trainees and trainers continue on SIDH, ministry-level grievances on CPGRAMS. PM-SETU adds a scheme-selection dropdown and routing tags at those portals.
SPVs and AIPs — central actors with no grievance channel today — get native filing on the PM-SETU portal for fiduciary and IT / platform matters.
Why a separate module
Task and grievance handling cuts across all other modules and reuses existing grievance channels.
System of record for
- Programme tasks, workplans and milestones
- SPV / AIP grievances
- Consolidated PM-SETU grievance disposal records
Boundaries
Scope & key assumptions
In scope
- Task creation, assignment, prioritisation and tracking across workstreams
- Milestone and workplan monitoring with RAG dashboards
- PM-SETU scheme dropdown on SIDH and CPGRAMS
- Native SPV / AIP grievance channel (fiduciary, IT / platform)
- SLA timers, escalation and closure workflows
- Grievance analytics — volumes, ageing, disposal, SLA compliance
Key assumptions
- SIDH and CPGRAMS remain designated intake channels; tagging depends on agreement with portal owners.
- Escalation hierarchy (ITI → Nodal Officer → RDST → State → Centre) remains stable.
- Pre-2014 examination grievances remain manual; a register is provided once digitised.
- Project Management does not replace MSDE or State project systems.
| As-Is gap | How this module responds |
|---|---|
| 12 divisions / cells run separate grievance mechanisms | Consolidated, scheme-tagged view across channels. |
| No scheme tagging on SIDH / CPGRAMS | PM-SETU dropdown and routing tags at every channel. |
| No channel for SPVs / AIPs | Native filing on the PM-SETU portal. |
| Sequential, untimed escalation | SLA timers with automatic escalation. |
| No unified grievance analytics | National → State → ITI / SPV drill-down dashboards. |
8 roles
Stakeholders & roles
DGT / MSDE / SPMU / PMU
Task assignment and monitoring, grievance oversight, escalations.
State / RDST
State-level task execution; grievance review within the chain.
SPVs & AIPs
Task updates; file fiduciary and IT grievances on PM-SETU portal.
ITIs
Approve trainee grievances; submit institutional grievances.
Trainees
File marks, profile and exam grievances on SIDH.
Trainers
File marks / certification and profile grievances on SIDH.
Nodal Officers
First-level review (one per 4–5 ITIs); CPGRAMS transfers.
DGT divisions / cells
Resolve routed grievances; prepare Action Taken Reports.
7 pillars
Functional pillars
- Title, workstream, priority, due date, assignee, milestone
- States: Open → In-Progress → Under Review → Rework → Closed
- Progress, effort and blocker logging
- No closure without reviewer approval
Persona by persona
User journeys
- 1
Workplan setup
Workstreams, workplans and sprint / milestone calendars.
- 2
Create & assign
Title, priority, due date and assignee; assignee notified.
- 3
Execute
Progress, effort and blockers logged; due dates monitored.
- 4
Review & close
Deliverable attached; reviewer approves or returns for rework.
- 5
Report
Completion % recomputed; delayed tasks surfaced to SPMU, State, Centre.
How work moves
Process flow
Grievance redressal across channels
= control / decision point- 1Trainee / Trainer / Citizen / SPVFile on SIDH, CPGRAMS or PM-SETU portal with PM-SETU tag
- 2ITI / DGT nodalVerify, categorise, approve
- 3Routing engineRoute by channel & category; start SLA timer
- 4Resolver (cell / State / IT)Resolve; record action / ATR
- 5SLA engineAuto-escalate on breach
- 6AnalyticsDisposal synced; ageing & SLA dashboards
APIs and events only
Integrations & data exchange
Receives from
SIDH
Trainee & trainer grievance status
CPGRAMS
Ministry-level grievances and ATRs
All modules
Task context and milestones
Sends to
FMS
Fiduciary grievances for resolution
LOMS modules
IT / platform issues to owners
Monitoring / Analytics
Task progress and grievance KPIs
Numbers that matter
Key rules & non-functional requirements
Business rules
- Nodal Officer ratio
- 1 per 4–5 ITIs
- Trainee chain
- ITI → Nodal → RDST → State → Centre
- Exam grievances
- Only within the examination window
- Alert dispatch
- Within 5 minutes
- Pre-2014 exam grievances
- Manual; tracked in a register
Performance, capacity & security
- Concurrent users
- 1,000 normal · 3,000 in exam windows
- Throughput
- 100 TPS rising to 300 TPS
- Infra (app tier)
- 24 vCPU · 96 GB · 5 TB objects
Platform-wide: page load ≤ 3 s (p90), API ≤ 500 ms (p95), ≥ 99.5% availability, RTO 4 h / RPO 30 min. See architecture.
Implementation
Phased rollout
Initial
- — Task board & dashboards
- — Native SPV / AIP channel
- — SLA engine
With portal owners
- — SIDH and CPGRAMS scheme tagging
- — Status synchronisation