Nine modules · one platform

LOMS modules

Each module has one clear job and owns its own records. Open any module to see it explained on its own — or compare all nine side by side below.

At a glance

Compare all modules

ModulePartSystem of record forPillarsRolesWhy separate
Digital TLMCTeaching-learning content; Assessment items and blueprints810Content is created and approved once, and reused across States and ITIs. Newly developed content is the property of DGT and may be used in any ITI.
ITI ManagementEStudent master record (PRN); Attendance — the single source for all LOMS modules87ITI operations are the largest manual gap in the As-Is baseline, and they provide the validated base for every other module.
LMSBLearning activity and module-level progress; Formative and practical assessment records119It holds the learning record of each learner, which no other system holds. SIDH is a discovery and identity layer, NIMI/Bharat Skills are content repositories — neither keeps the batch-level teaching record.
Exam ManagementGPM-SETU participation mapping; Validated examination events published to LOMS98SIDH stays authoritative, so LOMS adds only scheme context and integration and creates no parallel examination system.
Industry ManagementJIndustry Master Profile & relationships; MoUs, commitments and SLAs1310Industry partners, agreements and outcomes need their own record — it is what links training to employment.
FMSDFunds, budgets, utilisation; SIP and AOP plans with revisions77Financial records need separate controls and audit trail, apart from programme monitoring. FMS is a LOMS module, not an external system — its development is costed separately.
MonitoringIQuarterly KPI / DLI evidence; Validated, immutable quarterly snapshots65The 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.
Analytics PortalHDashboards, alerts and reports (presentation only); Reconciled analytics warehouse57It presents reconciled data and does not become a new point of first entry. Approvals are tracked here but decided in the source module.
Admin ManagementFProgramme tasks, workplans and milestones; SPV / AIP grievances78Task and grievance handling cuts across all other modules and reuses existing grievance channels.