PROGRAMME MANAGEMENT INFORMATION SYSTEM (PMIS)

Program Management Information System (PMIS) is a web-based, centralized tool for monitoring and evaluation of the physical, financial and outcome parameters of the Mission Mode Projects under e-Kranti framework of Digital India program and other such e-Governance projects.

Objectives

Provide Centralized monitoring and analytics for physical & financial progress

Assist the Central/State Departments to track and monitor the progress of the project Centrally and State-wise

Support decentralized data collection at source

Generate project specific, state/ district/ national level MIS and Dashboard reports

Enable stakeholders to communicate information and decisions on MMPs/NeGD projects quickly, effectively and periodically

Reduce turnaround time in generating periodic progress reports

Features

  • 01 Customized Reports, Dashboard views with project performance matrices

  • 02 Interface with Project Management Tools for individual projects

  • 03 Integration with Rapid Assessment System (RAS)

  • 04 Cloud & Web enabled to ensure anywhere-anytime access

  • 05 Using Statistical and Analytics tools to analyze projects critically

  • 06 Contact repository of Mission Leader / Nodal Officers of e-Gov projects

  • 07 Monitoring and Evaluation (M&E) Framework

  • 08 Interface with the Digital India portal

  • 09 Mobile accessible

  • 10 Mail Service Integration to send mails, SMS, reminders

Role of PMIS

Role of PMIS for various projects depending on phase of implementation

1 Pre-Implementation (Conceptualization, Core Scoping, Design & Development)

  • Capture Vision & Objectives
  • Define funding requirement & approval
  • Define envisaged Services & prioritization
  • Define & schedule activities
  • Define M & E framework, Key Result Areas (KRAs)
    • Business Processes & Pain areas
    • Best Practices in similar environment
    • Assess current ICT infrastructure and their ability to support future plans
    • Assess current service levels
    • Business Process Re-engineering and to-be process definition
    • Define future service levels
    • Capacity building plan
    • Awareness & Communication Plan
    • Transformation and not translation
    • Integrated services
    • Mandatory GPR
    • Infrastructure on demand
    • Cloud First
    • Mobile First
    • e-Gov standards compliance
    • Language localization

2 Implementation & Operations

    • Business/implementation model
    • Identification of key stakeholders and their roles and responsibilities
    • Project investments and costs
    • Procurement approach
    • Vendor evaluation & on-boarding
    • Service Levels
    • Monitoring and Evaluation (M & E) Plan
    • e-Governance Solution/Software
    • Technical Design, Development, Testing(UAT) and Go Live
    • IT Infrastructure
    • Reports
    • Scheduling Activity
    • Tracking expenditure
    • Transformation and not translation
    • Integrated services
    • Mandatory GPR
    • Infrastructure on demand
    • Cloud First
    • Mobile First
    • e-Gov standards compliance
    • Language localization

3 Post Implementation (Operate, Sustain) and Monitoring & Evaluation of outcomes

  • Operate and maintain
  • Rollout services and systems (functionality and geography)
  • Objectives & benefits evaluation and reinforcement
  • Sustained change, capacity building and communications
  • Periodic / Monthly inputs of critical KRA metrics (both qualitative & quantitative)
    • e-Transactions
    • Stakeholder Feedback
    • Benchmarking vis-a-vis outcomes envisaged
    • Impact Assessment
    • Inputs for reworking implementation strategy
  • Rework on implementation based on evaluation

Steps in Project Creation

1. Project definition

The project owners fill basic information about the project such as project title, owning department, nodal officer, approval date, financial details, key objectives and present status.

2. Services

The user has to to fill information about Services, their names, nature (G2C,G2B or G2G), number of services planned, Operational and number of service delivery locations.

3. Financial Allocation

The users also expected to key-in financial information about budget allocated, released and spent for activities, performed at centre and state level.

4. Activities

They have to fill in activities planned at centre/state expected to be executed at state level. These actvities are stored as master set of activities. These activities are automatically percolated and become visible to all state level nodal officers for reporting progress.