Admin Management and FMS: named 21 times by Admin Management, 0 times by FMSAdmin Management and ITI Management: named 0 times by Admin Management, 3 times by ITI ManagementAdmin Management and Monitoring: named 4 times by Admin Management, 0 times by MonitoringAnalytics and FMS: named 37 times by Analytics, 0 times by FMSAnalytics and LMS: named 35 times by Analytics, 9 times by LMSAnalytics and ITI Management: named 8 times by Analytics, 2 times by ITI ManagementAnalytics and Exam Management: named 8 times by Analytics, 1 times by Exam ManagementAnalytics and Monitoring: named 31 times by Analytics, 1 times by MonitoringAnalytics and Industry Management: named 6 times by Analytics, 10 times by Industry ManagementFMS and ITI Management: named 0 times by FMS, 7 times by ITI ManagementFMS and Monitoring: named 0 times by FMS, 11 times by MonitoringFMS and Industry Management: named 0 times by FMS, 16 times by Industry ManagementLMS and ITI Management: named 0 times by LMS, 19 times by ITI ManagementLMS and Digital TLM: named 0 times by LMS, 18 times by Digital TLMLMS and Exam Management: named 0 times by LMS, 18 times by Exam ManagementLMS and Monitoring: named 0 times by LMS, 13 times by MonitoringLMS and Industry Management: named 0 times by LMS, 24 times by Industry ManagementITI Management and Digital TLM: named 0 times by ITI Management, 2 times by Digital TLMITI Management and Exam Management: named 27 times by ITI Management, 0 times by Exam ManagementITI Management and Monitoring: named 11 times by ITI Management, 0 times by MonitoringITI Management and Industry Management: named 6 times by ITI Management, 0 times by Industry ManagementDigital TLM and Exam Management: named 13 times by Digital TLM, 0 times by Exam ManagementExam Management and Monitoring: named 1 times by Exam Management, 0 times by MonitoringAdminAnalyticsFMSLMSITIDigital TLMExamMonitoringIndustry

Line thickness = number of times the two DPRs name each other. Tap a module for details.

Who names whom

This DPR names →Admin ManagementAnalyticsFMSLMSITI ManagementDigital TLMExam ManagementMonitoringIndustry Management
Admin Management–·21····4·
Analytics·–37358·8316
FMS··–······
LMS·9·–·····
ITI Management32719–·27116
Digital TLM···182–13··
Exam Management·1·18··–1·
Monitoring·11113···–·
Industry Management·101624····–

Module by module

Admin Management System

Programme task tracking and grievance redressal across SIDH, CPGRAMS and the PM-SETU portal.

Diagrams of this module Full document

This DPR refers to

FMS named 21 times
The integration architecture will support secure, API-driven data exchange with the SIDH and CPGRAMS portals, the PM-SETU FMS and LOMS platforms, government identity platforms, document repositories, and enterprise support services.PDF p.21 · Pillar 7: Integration
SLA and ageing monitoring; escalation management Grievance Analytics & Reporting National, State, ITI, SPV, and cell-wise dashboards; ageing and disposal reporting Integration Layer SIDH, CPGRAMS, FMS/LOMS integrations;PDF p.13 · Sub-module 2: Grievance Management — user journeys
Monitoring named 4 times
The PM-SETU Monitoring Platform shall publish programme-delivery and physical-progress events to the Alert & SLA Engine so that implementation risks surface alongside fiduciary and grievance exceptions within a single consolidated view.PDF p.19 · Pillar 5: Alert & SLA engine

Named by

National systems and umbrella names it mentions

SIDH · 52CPGRAMS · 44LOMS · 12

Analytics Management System

One portal for fiduciary, performance, approvals, alerts and reports, for Centre, State, SPV, Auditor, ITI, Student and MDB.

Diagrams of this module Full document

This DPR refers to

FMS named 37 times
Fiduciary sources: SPVs and States enter fund utilization, audit and contract information directly into the Fund Flow Tracker, Budget and AOP Management, Audit and Contract Management modules of the Fiduciary Management System, through their own user interfaces and workflows.PDF p.34 · 4.1.1 Sources of Inflow
Inflow to the Portal, from the source systems named above into the Alert Engine, Fiduciary Management and Performance Analytics pillars, occurs on a refresh cycle to be agreed with each source system, with the short-lived cache described at 4.1.3 employed where near real-time freshness is required.PDF p.36 · 4.1.4 Refresh Cycle
LMS named 35 times
Operational and fiduciary KPI rows are drawn from the source systems already named in Sections 3.1 and 3.2, including the Learning Management System (LMS) metrics that also constitute the Student stakeholder's own academic position (Section 2.7).PDF p.29 · 3.6. Consolidated KPI and DLI Reference
The Performance Analytics pillar draws upon the Learning Management System, Exam Management System, ITI Management System, PM-SETU Monitoring System, Financial Management System and Industry and Alumni Management System that together constitute LOMS.PDF p.4 · 1. Overview
Monitoring named 31 times
Present the DLI and operational KPI position set out in the consolidated register at Section 3.6, drawing DLI progress from the PM-SETU Monitoring System's validated quarterly snapshot and operational KPIs from the six source systems constituting LOMS, scoped to the stakeholder's entity.PDF p.22 · 3.2. Pillar 2: Performance Analytics Pillar
The Performance Analytics pillar draws upon the Learning Management System, Exam Management System, ITI Management System, PM-SETU Monitoring System, Financial Management System and Industry and Alumni Management System that together constitute LOMS.PDF p.4 · 1. Overview
ITI Management named 8 times
The Performance Analytics pillar draws upon the Learning Management System, Exam Management System, ITI Management System, PM-SETU Monitoring System, Financial Management System and Industry and Alumni Management System that together constitute LOMS.PDF p.4 · 1. Overview
Exam Management named 8 times
The Performance Analytics pillar draws upon the Learning Management System, Exam Management System, ITI Management System, PM-SETU Monitoring System, Financial Management System and Industry and Alumni Management System that together constitute LOMS.PDF p.4 · 1. Overview
Industry Management named 6 times
The Performance Analytics pillar draws upon the Learning Management System, Exam Management System, ITI Management System, PM-SETU Monitoring System, Financial Management System and Industry and Alumni Management System that together constitute LOMS.PDF p.4 · 1. Overview

Named by

National systems and umbrella names it mentions

LOMS · 10SIDH · 7

Fiduciary Management System (FMS)

Fund flow, budget and AOP, audit and reporting, and contract and MDB compliance.

Diagrams of this module Full document

This DPR refers to

This DPR does not name any of the other 8 modules.

Named by

National systems and umbrella names it mentions

SIDH · 2LOMS · 2

Learning Management System (LMS)

Course delivery, assessment, progress, credentials and AI learning assistance for learners and trainers.

Diagrams of this module Full document

This DPR refers to

Analytics named 9 times
Publish validated learning events and reconciliation status to the Analytics Portal or program monitoringPDF p.36 · Functional Capabilities - Progress Tracking
The platform exposes validated operational events to the Analytics Portal, but national,PDF p.4 · 1.1 Scope

Named by

National systems and umbrella names it mentions

SIDH · 55NCS / NAPS · 34NCVET · 18NIMI · 14Bhashini · 11DigiLocker · 5

ITI Management System

ITI administration: admissions, student records, attendance, timetable, hostel, fees, instructors and infrastructure.

Diagrams of this module Full document

This DPR refers to

Exam Management named 27 times
SIS- 030 Feed to Exam Management for continuous evaluation System shall push consolidated internal assessment scores to the Exam Management module where continuous/internal assessment marks contribute to the final result computation. (Integration Point)PDF p.34 · 4.2.1. Functional Capability
Sync Academic Calendar with Exam Management - The system syncs the academic calendar with the Exam Management module to avoid scheduling conflicts with examination periods.PDF p.20 · 3.3.4. Scheduling (Timetable and resource)
LMS named 19 times
The module integrates with supporting systems such as the LMS, Examination System, Fiduciary Management, Analytics, and Industry & Alumni networks, ensuring information moves seamlessly between academic, financial, and administrative functions rather than sitting in silos.PDF p.9 · 3. Business Requirements
The Student Information System is the unified system of record for every enrolled student, consolidating data created at admission and consumed across LMS, Exam Management, Attendance and Analytics.PDF p.33 · 4.2.1. Functional Capability
Monitoring named 11 times
Institute-level infrastructure readiness status shall be pushed to the PM-SETU Monitoring module.PDF p.45 · 4.8.2. Acceptance criteria
Governance and analytics layer: Feeds the Analytics & Dashboard module and PM-SETU MonitoringPDF p.46 · 5.1. Solution Architecture (Conceptual Block Diagram)
FMS named 7 times
A student record shared with the Exam Management System or the Fiduciary Management System shall reconcile to the same student, trade, and batch without duplicate entry.PDF p.58 · 7.1. Testing strategy
The module integrates with supporting systems such as the LMS, Examination System, Fiduciary Management, Analytics, and Industry & Alumni networks, ensuring information moves seamlessly between academic, financial, and administrative functions rather than sitting in silos.PDF p.9 · 3. Business Requirements
Industry Management named 6 times
Integration with the other LOMS modules- Learning Management System, Exam Management System, Industry Management System, Fiduciary Management System, PM-SETU Monitoring System, Analytics & Dashboard, and AdministratorPDF p.57 · 7.1. Testing strategy
Connected LOMS-module and DPI interfaces including the Exam Management System, Industry Management System, Fiduciary Management System, PM-SETU Monitoring System, Aadhaar/eKYC,PDF p.58 · 7.2. Acceptance criteria
Admin Management named 3 times
SIS- 024 Instructor-wise, subject-wise access control for score entry System shall restrict internal assessment score entry to the instructor(s) assigned to the specific subject/batch/session, based on roles defined in the Administrator Management System.PDF p.34 · 4.2.1. Functional Capability
Role-based access control shall be enforced across all modules aligned to Administrator Management System roles.PDF p.45 · 4.9. Cross-Cutting areas
Analytics named 2 times
ADM- 030 Admission data feed to Analytics module System shall push consolidated admission-cycle data (applications, allotments, enrolments, category-wise fill rate) to the Analytics & Dashboard module.PDF p.31 · 4.1.1. Functional Capability
Attendance push API (real-time or batch) to Analytics modulePDF p.47 · 5.2. API requirements (indicative)

Named by

National systems and umbrella names it mentions

LOMS · 34SIDH · 9DigiLocker · 9NCS / NAPS · 3NCVET · 2

Digital TLM Development Tools

Tools to author, review and publish teaching-learning material, assessments and AR/VR content.

Diagrams of this module Full document

This DPR refers to

LMS named 18 times
Integration with LMS, EMS and source systems Use approved curriculum, identity and institution data from the relevant source systems and send approved content and assessment material to the LMS and EMS.PDF p.13 · AI support and content compliance assist user journey
Validate approved devices and simulator data before learning events are passed to the LMS or shared learning record store.PDF p.21 · Pillar 8: Integration
Exam Management named 13 times
Integration with LMS, EMS and source systems Use approved curriculum, identity and institution data from the relevant source systems and send approved content and assessment material to the LMS and EMS.PDF p.13 · AI support and content compliance assist user journey
Material releases to LMS or EMS only after recorded approval within this module.PDF p.22 · Pillar 8: Integration
ITI Management named 2 times
ITI Management System Read institution, trainer andPDF p.21 · Pillar 8: Integration

Named by

Not named by the other DPRs.

National systems and umbrella names it mentions

NIMI · 15SIDH · 2

Exam Management System

Exam cycles, question banks and CBT, practical marks, results and certification.

Diagrams of this module Full document

This DPR refers to

LMS named 18 times
Validated examination events for this PM- SETU cohort will then be published through the common PM-SETU integration / canonical data layer for consumption by LMS, Monitoring and Analytics according to their system boundaries.PDF p.5 · 1. Overview
Publication and data exchange: Publish the authoritative result / certificate status on SIDH and emit validated PM-SETU result events to the common integration/KPI layer for LMS, Monitoring and Analytics.PDF p.10 · 2.3. DGT examination control user journey
Analytics named 1 times
Paper generation: The agency engine applies the approved selection and randomisation rules for the relevant shift; the generated paper remains traceable to the bank and rule version without exposing restricted content to PM-SETU analytics consumers.PDF p.11 · 2.4. NIMI / examination agency user journey
Monitoring named 1 times

Named by

National systems and umbrella names it mentions

SIDH · 142NIMI · 19

PM-SETU Monitoring System

Quarterly SPV monitoring, State review and Centre overview, tracked against DLIs and KPIs.

Diagrams of this module Full document

This DPR refers to

LMS named 13 times
Use agreed common identifiers and reporting-period definitions across Monitoring, LMS, FMS/UC/Audit and Analytics so records can be reconciled consistently.PDF p.21 · 6.5. Integration and Interoperability
Tracer / placement / LMS Quarterly status; formal source yearlyPDF p.9 · 4.1. Monitoring Form Functional Areas
FMS named 11 times
Use agreed common identifiers and reporting-period definitions across Monitoring, LMS, FMS/UC/Audit and Analytics so records can be reconciled consistently.PDF p.21 · 6.5. Integration and Interoperability
Information already available in LMS/LOMS, FMS/UC/Audit, SIDH/NCVT MIS, tracer and survey records, and approved programme records will be pre-filled.PDF p.5 · 1. Overview
Analytics named 1 times
Reviewed information will feed the Analytics module and Centre-level monitoring.PDF p.18 · 5. Solution Architecture

Named by

National systems and umbrella names it mentions

SIDH · 8LOMS · 3

Industry Management System

Industry partner onboarding, MoUs, apprenticeships, OJT, internships, placements and alumni tracking across 13 functional pillars.

Diagrams of this module Full document

This DPR refers to

LMS named 24 times
On-the-Job Training tracking: The mandatory industry-linked practical exposure component of the Craftsmen Training Scheme is tracked as its own record, reconciled with the PM-SETU Learning Management System.PDF p.28 · Functional Capabilities
Publish an approved submission's reference to the PM-SETU LMS Course Management pillar without altering the authoritative course record directly.PDF p.30 · Functional Capabilities
FMS named 16 times
Contribution value publishes to the Fiduciary Management System for reconciliation through PillarPDF p.23 · Acceptance Criteria
Auditor / Independent Monitoring Agency Reviews industry funding-contribution compliance, Memorandum-of- Understanding commitment fulfilment, and apprenticeship and placement outcome evidence feeding the Fiduciary Management System and DGT oversight.PDF p.8 · 1.4 Stakeholders
Analytics named 10 times
Analytics Portal unavailable to receive a published event Retain the event for retry and mark the figure as pending publication.PDF p.44 · Exception Management
Placement, apprenticeship, and employment-outcome data published by this platform feeds the Analytics Portal's Performance Analytics pillar and, where the relevant integration is enabled, the National Apprenticeship Promotion Scheme portal and the National Career Service.PDF p.7 · 1.3 Key Assumptions

Named by

National systems and umbrella names it mentions

NCS / NAPS · 20SIDH · 7NCVET · 3DigiLocker · 1

Solution architecture, as drawn in each DPR

The architecture diagram of each module, exactly as it appears in its document. They show which source systems and users each module connects to.