DPR §A.9 – A.12 · Programme

Budget, delivery, rollout and risk

A Service Integrator-led model using COTS and open-source products for commodity capabilities, with custom development only for PM-SETU-specific requirements. Rolled out first to the 1,000 PM-SETU ITIs over 8–10 months.

Indicative cost

₹404 Cr base + ₹21 Cr contingency = ₹425 Cr

A. Integrator-led implementation

₹148 Cr

  • Mobilisation, enterprise / solution architecture, detailed design

    12
  • Build / configuration of eight LOMS modules & PM-SETU workflows

    68
  • Common platform services, API / integration, identity, master data, observability

    32
  • Data platform, analytics and governed AI capabilities

    16
  • Data discovery, cleansing, migration, reconciliation, cutover

    10
  • Functional, integration, security, performance, accessibility & UAT testing

    10

B. Cloud, products & cyber security

₹126 Cr

  • COTS / open-source implementation, licences, OEM support

    38
  • Cloud hosting, environments, backup, DR, network, monitoring (5 years)

    70
  • Cyber-security tooling, SOC / SIEM, VAPT, audits, certification

    18

C. Content, rollout & operations

₹99 Cr

  • Digital TLM digitisation, conversion, multilingual, accessibility, QA

    45
  • Training, change management, communications, adoption monitoring

    14
  • Pilot, phased national rollout, field readiness, hypercare

    12
  • Application operations, L1–L3 support, helpdesk, enhancements (5 years)

    28

D. Programme governance & assurance

₹31 Cr

  • PMU / Lead Integrator governance, monitoring, coordination

    25
  • Independent quality, cyber-security and milestone assurance

    6

₹ Crore, indicative. FMS development is excluded; FMS integration is included. Contingency (5%) only for approved changes, not an automatic allocation.

Expenditure phasing

₹240
Y1
₹70
Y2
₹40
Y3
₹40
Y4
₹35
Y5

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 / serviceRecommended approachReasoning
Digital TLMCOTS / open-source authoring, extended by SIAuthoring and packaging are commodity; governance workflows built around them.
ITI ManagementEducation ERP COTS configured by SIMature in packaged products; value is in State variants and integration.
LMSCOTS / open-source LMS core + SI extensionsAvoids rebuilding standard delivery; learner record & AI integrated via platform.
Exam ManagementService Integrator buildIntegration over SIDH — nothing to buy.
MonitoringSI build on common platform servicesKPI / DLI cycle and CAPEX rules are PM-SETU-specific.
AnalyticsCOTS / open-source BI + SI data engineeringVisualisation is commodity; reconciled models are specific.
Admin ManagementCOTS workflow / grievance tooling + native SPV channelTask & grievance tools exist; SIDH / CPGRAMS routing is specific.
Industry ManagementCOTS CRM + MoU engine extensionsRegistry is CRM; MoU / SLA / renewal engine is specific.
Common platformSI build & operation on open standardsIdentity, master data, integration and audit need single accountability.
Architecture governanceIn-house within DGT / MSDEPolicy, record ownership and priorities cannot be delegated.

Rollout

Phased by readiness, gated on evidence

  1. Step 01

    Confirm programme governance and decision rights

  2. Step 02

    Freeze the system-of-record and data-ownership map

  3. Step 03

    Finalise the integration and master-data framework

  4. Step 04

    Prioritise the release plan — foundation first, then core workflows, then analytics & AI

  5. Step 05

    Complete State and ITI readiness segmentation

  6. Step 06

    Finalise budget, procurement and commercial packaging

  7. Step 07

    Build, integrate and test the initial release

  8. Step 08

    Prepare adoption and operating support before go-live

  9. Step 09

    Pilot, measure and scale on evidence

  10. 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

StakeholderRole in PM-SETUKey needs from LOMS
DGT / MSDE / NPMUPolicy, standards, governance, national oversightComparable national data, exception views, clear system ownership
State Directorates / SPMUState rollout, review, escalationState / cluster dashboards, review workflows, readiness visibility
SPVs / Anchor Industry PartnersCluster implementation, industry linkage, monitoring evidenceTask ownership, cluster data, structured submission, grievance channel
ITI administrators & staffAdmissions, operations, attendance, fees, recordsSimple daily workflows, no duplicate entry, mobile / low-bandwidth
Trainers / assessorsDeliver learning, record evidence, interveneFast workshop workflows, approved content, progress views
Learners / traineesLearn, assess, OJT, transition to jobsAccessible, multilingual access; transparent progress and credentials
NIMI / SIDH / exam ecosystemQuestion bank, exams, certificationStable scheme identification and agreed data contracts
Industry, content & opportunity partnersContent, OJT, apprenticeship, placementGoverned interfaces, consent rules, keep own systems
Auditors / IMA / IVA / MDBIndependent review and assuranceTraceable data, read-only access, audit history
Technology & support partnersBuild, integrate, operateStable requirements, documented interfaces, SLAs