DPR Part I · Programme governance
PM-SETU Monitoring System
Quarterly non-financial monitoring of DLI / KPI progress — reuse data before asking for data again.
Overview
What this module does
Programme leadership needs one consistent view of progress across SPVs. The Monitoring System is the quarterly non-financial reporting and review layer for PM-SETU.
It brings DLI / KPI progress, implementation status, risks, audit actions, resource gaps and employment outcomes into one structured cycle.
Data already in LMS, FMS, SIDH / NCVT MIS, tracer surveys and programme records is pre-filled. SPVs complete only the gaps, explanations and evidence. States review; Centre and Analytics consume the same validated position.
Why a separate module
The review cycle follows the approved KPI and DLI framework and needs its own validated record. Monitoring is where SPVs enter and States validate — Analytics only presents.
System of record for
- Quarterly KPI / DLI evidence
- Validated, immutable quarterly snapshots
- Issue / action tracking
Boundaries
Scope & key assumptions
In scope
- Quarterly form: DLI / KPI progress, delivery, audit actions, resources, risks, employment
- Auto-population with source and last-refresh shown on each field
- SPV input limited to gaps, variance explanations and evidence
- Field-level State review and return
- Centre consolidation, exception monitoring and escalation
- Validated snapshots feeding Analytics and alerts
- Q4 submission gate before the next AOP
Key assumptions
- Financial transactions remain in FMS — Monitoring reads status only.
- Quarterly capture is a PM-SETU operating cadence; formal DLI verification keeps its own frequency.
- Auto-filled fields are read-only unless a controlled exception is approved.
- DLIs 4–6 are mainly State / Centre responsibilities.
5 roles
Stakeholders & roles
SPV / HSIC
Reviews pre-filled data, completes gaps, explains deviations, attaches evidence.
IMA
Verifies SPV KPI and milestone data before State review.
State reviewer
Reviews submissions; returns only affected fields with comments.
Centre / NPMU
National view of coverage, exceptions and trends; issues actions.
IVA
Formal independent verification of national and State DLIs.
6 pillars
Functional pillars
- Reporting period created automatically
- Notifications to SPV and State
Persona by persona
User journeys
- 1
Notification
Quarter-open alert; sign in through SSO.
- 2
Review pre-fill
Check values from LMS, FMS, SIDH, surveys.
- 3
Complete gaps
Only missing fields are open; add value, explanation, evidence.
- 4
Validate & submit
Completeness check, then to State review queue.
- 5
Resubmit returns
Update only returned fields; Q4 must be complete before next AOP.
How work moves
Process flow
Quarterly monitoring cycle
= control / decision point- 1SystemOpen quarter; one form per active SPV
- 2Source systemsPre-fill LMS, FMS, SIDH, tracer, official records
- 3SPVComplete gaps, explanations, evidence
- 4IMAVerify SPV KPI & milestone data
- 5StateAccept or return selected fields
- 6SystemImmutable validated snapshot
- 7Centre / AnalyticsMonitoring, alerts, KPI score → CAPEX release
APIs and events only
Integrations & data exchange
Receives from
LMS
Enrolment, attendance, completion, trainer training
FMS / UC / Audit
SIP / AOP refs, UC & audit status
SIDH / NCVT MIS
Learner, course, certification records
Industry Management
Tracer & placement outcomes
Admin / official records
Governance orders, milestones, NSTI records
Sends to
Analytics
Validated quarterly snapshots with data-quality flags
FMS
KPI score for CAPEX tranche
Alerts
Reminders and threshold alerts
Numbers that matter
Key rules & non-functional requirements
Business rules
- Cadence
- Quarterly; formal DLI verification yearly / semi-annual
- DLIs
- 6 disbursement-linked indicators
- Funding-linked KPIs
- 13 cluster-level KPIs with weightages
- CAPEX rule
- Score ≥ 75% → 100% tranche; else Eligible × (Score / 75)
- Q4 gate
- Q4 submission required before next AOP
Performance, capacity & security
- Load
- Low steady use; peaks at quarterly deadlines
- Audit
- Immutable validated quarterly snapshots
- Infra (app tier)
- 16 vCPU · 64 GB · 4 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
First release
- — Single quarterly form with SSO and source tags
- — Priority pre-fill
- — DLI 1–6 structure, evidence, alerts
- — Field-level return
- — Q4 → AOP gate
- — Analytics feed
Enhancements
- — More API / event integrations
- — Automated evidence checks
- — Refined exception & risk scoring