PM-SETU · DGT / MSDE · Detailed Project Report

Learning Outcome Management System

One integrated, federated digital platform that connects the full learner, institution and programme journey across ITIs, SPVs, States and DGT.

Pradhan Mantri Skilling and Employability Transformation through Upgraded ITIs

9
Integrated modules
1,000
PM-SETU ITIs in first rollout
12
States in As-Is assessment
1,300+
ITIs assessed
8–10
Months to implement & roll out
₹425 Cr
Overall 5-year provision

Why LOMS

The infrastructure exists. The connected journey does not.

The As-Is assessment of 12 priority States and 1,300+ ITIs found substantial digital assets — but uneven use, fragmented processes, and information that stops flowing after admission.
44%
Average ITI system uptime
38.2%
National digital course completion
38.9%
Digital assessment adoption
0
States with a fully operational LMS
56%
ITIs with dedicated IT support
~50%
States with exam → alumni stages digitised

Fragmented processes

Learner, academic and ITI activities run across State systems, national platforms, spreadsheets and registers — repeated entry and late reconciliation.

Visibility fades after admission

Admission is digitised, but learning, practicals, exams, credentials and employment are not connected.

No common standards

Different identifiers, terms and data structures produce parallel or conflicting records.

Infrastructure ≠ usage

Connectivity exists, but uptime, maintenance and local support vary widely.

Reporting is re-compiled

MIS data is collected again instead of reused from validated source systems.

Scattered administration

Tasks, milestones and grievances sit in different channels with no single view of SLA and closure.

What LOMS is

A federated programme layer — not a replacement

LOMS connects existing national, State and partner systems and adds only what no system covers today. Each type of record has one owning module and one system of record; modules talk only through governed APIs and events.

Who uses it

  • DGT / MSDE / NPMU
  • States / SPMU
  • SPVs & Anchor Industry Partners
  • ITIs, Trainers & Trainees
  • Industry & Employers
  • Auditors / IMA / MDB

Single sign-on · role & entity scoped

LOMS — federated programme layer

one owner per record · APIs & events only

Learner & institution journey

Programme governance

Common platform services — built once, used by all

SSO / IAM & rolesPM-SETU IDs & master dataWorkflow & rulesIntegration & event busNotificationsAudit & consentDocuments & evidenceAI gateway

Stays authoritative

  • SIDH (identity, exams, certificates)
  • State admission portals
  • Aadhaar eKYC · DigiLocker · APAAR / ABC
  • CPGRAMS
  • NIMI · CBT agency
  • NAPS · NCS
  • Escrow & banks

Connected — not replaced

The nine modules

Every module can be explored on its own

Each module page covers scope, stakeholders, functional pillars, user journeys, process flows, integrations and non-functional requirements.

Learner & institution journey

Programme governance

Vision & objectives

What LOMS sets out to achieve

01

Connected digital workflows

Move core processes off fragmented manual systems onto consistent digital workflows.

02

Continuity across the journey

Link identity, admission, batch, attendance, learning, exam, credential and placement records.

03

Common basis for operations

Shared master data, identifiers, validation rules and role responsibilities.

04

Stronger digital teaching

Governed Digital TLM, multilingual and accessible content, formative assessment, AI where approved.

05

Learning → credentials → jobs

Structured exchange with SIDH, credential repositories and opportunity platforms.

06

Better monitoring & analytics

Reuse validated data for KPI / DLI monitoring, dashboards, alerts and grievances.

07

Secure & interoperable by design

SSO / IAM, RBAC, governed APIs, audit trails, privacy and accessibility.

08

Adoption at every readiness level

Phased onboarding, low-bandwidth and mobile access, training and helpdesk.

Design principles

Thirteen principles that keep nine modules acting as one

Federated, clear systems of record

Existing authoritative platforms keep their data; LOMS coordinates through common identifiers.

Service integration as the architecture

Reusable services and governed integrations, not point-to-point links.

API-first, NDEAR-aligned

Documented, versioned APIs and open standards.

One identity and programme context

SIDH learner ID plus a stable PM-SETU participation context — no parallel identities.

Data contracts before dashboards

Definitions, ownership and freshness agreed before data is shown.

Capture once, validate once, reuse

Users enter only genuine gaps or explanations.

Configurable, not hard-coded

Rules, thresholds and workflows changed by configuration.

Mobile, multilingual, low-bandwidth

Built into the baseline, not added later.

Security & least privilege

SSO, MFA, segregation of duties, encryption, audit logging.

Traceable lineage

Every record keeps source, timestamp, validation status and history.

Human accountability for AI

AI is advisory; high-impact decisions stay with humans.

Consent captured once

Guardian consent for under-18s captured at admission and reused (DPDP Act).

Vendor-neutral & portable

Data, interfaces and configuration portable across providers.

Next

See how a learner moves through all nine modules

Twelve stages — from curriculum to placement, funds and monitoring — with the module, data and hand-off at every step.

Open the complete flow