DPR §A.9 – A.12 · Programme
Budget, delivery, rollout and risk
Indicative cost
₹404 Cr base + ₹21 Cr contingency = ₹425 Cr
A. Integrator-led implementation
₹148 Cr
- 12
Mobilisation, enterprise / solution architecture, detailed design
- 68
Build / configuration of eight LOMS modules & PM-SETU workflows
- 32
Common platform services, API / integration, identity, master data, observability
- 16
Data platform, analytics and governed AI capabilities
- 10
Data discovery, cleansing, migration, reconciliation, cutover
- 10
Functional, integration, security, performance, accessibility & UAT testing
B. Cloud, products & cyber security
₹126 Cr
- 38
COTS / open-source implementation, licences, OEM support
- 70
Cloud hosting, environments, backup, DR, network, monitoring (5 years)
- 18
Cyber-security tooling, SOC / SIEM, VAPT, audits, certification
C. Content, rollout & operations
₹99 Cr
- 45
Digital TLM digitisation, conversion, multilingual, accessibility, QA
- 14
Training, change management, communications, adoption monitoring
- 12
Pilot, phased national rollout, field readiness, hypercare
- 28
Application operations, L1–L3 support, helpdesk, enhancements (5 years)
D. Programme governance & assurance
₹31 Cr
- 25
PMU / Lead Integrator governance, monitoring, coordination
- 6
Independent quality, cyber-security and milestone assurance
₹ Crore, indicative. FMS development is excluded; FMS integration is included. Contingency (5%) only for approved changes, not an automatic allocation.
Expenditure phasing
Front-loaded in Year 1 for the 8–10-month build and national rollout.
Financial controls
- — Fixed-price milestones for the baseline; unit-rate for cloud, licences, content, changes
- — Payments tied to accepted deliverables
- — FinOps: tagging, usage alerts, reserved capacity only after the pilot
- — Hosting provision of ~₹8–19 Cr per year at steady state
- — Code, configuration and data in DGT-controlled repositories
Technology development approach
Service Integrator-led, module by module
| Module / service | Recommended approach | Reasoning |
|---|---|---|
| Digital TLM | COTS / open-source authoring, extended by SI | Authoring and packaging are commodity; governance workflows built around them. |
| ITI Management | Education ERP COTS configured by SI | Mature in packaged products; value is in State variants and integration. |
| LMS | COTS / open-source LMS core + SI extensions | Avoids rebuilding standard delivery; learner record & AI integrated via platform. |
| Exam Management | Service Integrator build | Integration over SIDH — nothing to buy. |
| Monitoring | SI build on common platform services | KPI / DLI cycle and CAPEX rules are PM-SETU-specific. |
| Analytics | COTS / open-source BI + SI data engineering | Visualisation is commodity; reconciled models are specific. |
| Admin Management | COTS workflow / grievance tooling + native SPV channel | Task & grievance tools exist; SIDH / CPGRAMS routing is specific. |
| Industry Management | COTS CRM + MoU engine extensions | Registry is CRM; MoU / SLA / renewal engine is specific. |
| Common platform | SI build & operation on open standards | Identity, master data, integration and audit need single accountability. |
| Architecture governance | In-house within DGT / MSDE | Policy, record ownership and priorities cannot be delegated. |
Rollout
Phased by readiness, gated on evidence
- Step 01
Confirm programme governance and decision rights
- Step 02
Freeze the system-of-record and data-ownership map
- Step 03
Finalise the integration and master-data framework
- Step 04
Prioritise the release plan — foundation first, then core workflows, then analytics & AI
- Step 05
Complete State and ITI readiness segmentation
- Step 06
Finalise budget, procurement and commercial packaging
- Step 07
Build, integrate and test the initial release
- Step 08
Prepare adoption and operating support before go-live
- Step 09
Pilot, measure and scale on evidence
- Step 10
Establish continuous improvement
Risks & mitigation
What could go wrong — and the plan
Adoption & change
Users stay on manual processes; partial usage.
→ Readiness-based onboarding, role training, multilingual help, adoption monitoring.
Data quality & identity
Duplicate or inconsistent records reduce trust.
→ Common IDs and master data, validation at entry, lineage, reconciliation.
External integration
SIDH, FMS, CPGRAMS, DigiLocker or State outages interrupt workflows.
→ Versioned contracts, retries, stale-data handling, fallbacks.
Infrastructure reliability
Connectivity, power or support gaps at ITIs.
→ Mobile & low-bandwidth design, readiness checks, local support.
Security & privacy
Unauthorised access or weak role mapping.
→ SSO / IAM, RBAC, encryption, audit logs, security testing.
Policy change
Rule changes require rework if hard-coded.
→ Configurable rules, versioned workflows, change control.
Vendor dependency
Lock-in to one provider or proprietary interface.
→ Open standards, exit obligations, portability.
Sustainability
Support weakens after rollout.
→ Service ownership, SLAs, budgeted operations.
AI governance
AI outputs treated as authoritative too early.
→ Advisory AI, human confirmation, bias testing, phased introduction.
Success measures
How success is measured
Adoption & active use
ITIs / trainers / admins completing core workflows; routine transactions beyond login.
Digital learning & assessment
Course completion and assessment usage vs 38.2% / 38.9% baseline.
Reliability & security
Availability vs ~44% baseline uptime; no unresolved critical finding at release.
Data quality & integration
Records passing validation; priority interfaces live and reconciling.
Monitoring & grievances
Share of fields auto-populated; on-time SPV submissions; SLA compliance.
Learner & institution visibility
Lifecycle stages covered; successful exam / credential hand-offs.
Stakeholders
Who needs what from the platform
| Stakeholder | Role in PM-SETU | Key needs from LOMS |
|---|---|---|
| DGT / MSDE / NPMU | Policy, standards, governance, national oversight | Comparable national data, exception views, clear system ownership |
| State Directorates / SPMU | State rollout, review, escalation | State / cluster dashboards, review workflows, readiness visibility |
| SPVs / Anchor Industry Partners | Cluster implementation, industry linkage, monitoring evidence | Task ownership, cluster data, structured submission, grievance channel |
| ITI administrators & staff | Admissions, operations, attendance, fees, records | Simple daily workflows, no duplicate entry, mobile / low-bandwidth |
| Trainers / assessors | Deliver learning, record evidence, intervene | Fast workshop workflows, approved content, progress views |
| Learners / trainees | Learn, assess, OJT, transition to jobs | Accessible, multilingual access; transparent progress and credentials |
| NIMI / SIDH / exam ecosystem | Question bank, exams, certification | Stable scheme identification and agreed data contracts |
| Industry, content & opportunity partners | Content, OJT, apprenticeship, placement | Governed interfaces, consent rules, keep own systems |
| Auditors / IMA / IVA / MDB | Independent review and assurance | Traceable data, read-only access, audit history |
| Technology & support partners | Build, integrate, operate | Stable requirements, documented interfaces, SLAs |