1 of 22

DIKSHA

Support Document

2 of 22

Introduction

The purpose of this document is to describe the support offerings available for DIKSHA App, related to Learn, Survey, and Projects and how the services defined within those offerings are delivered to our partners.

Note: This document will be revised periodically to reflect changes in the products and solutions being supported and the processes, procedures, and technologies being used to deliver support services.

1

DIKSHA Support

3 of 22

Who can avail of the service.

  • State.
  • Partner Organisations working with the State.

2

DIKSHA Support

4 of 22

Who Can Contact US

Support requests will be accepted only from specific users in partner organizations.

To get access, the state/partner organization needs to provide a list of user's email addresses. The respective Programs PoC will raise the request to include these email IDs in the support desk.

The email address will be registered on the support desk, then the user will be able to raise requests directly.

2

DIKSHA Support

Note: User’s with Creator role can raise service requests for uploading the resources related to Programs, Observations, Surveys & Projects

5 of 22

How To Contact US

You can contact DIKSHA’s Support Team via Email for,

Note: For deep-linked learning content to assessments/ projects please raise the request via the email ID mentioned above

We recommend that all support requests be submitted via email, to enhance the process of reporting, tracking and resolving issues. Please include the brief description of issue on the subject line.

Note: DIKSHA support services are not available on Saturdays, Sundays, Public Holidays and outside of working hours which are Monday to Friday 9:30AM to 5:30PM. Ticket resolution times will depend on the nature of the issue/request raised.

2

DIKSHA Support

6 of 22

Support Category

The first step in the support process is to determine the nature of the support requirement. There are five categories of support available to customers via email:

  • General Enquiry
  • Technical Support
  • Service Request
  • Feature Request
  • Feedback & Suggestions

To view the list of requests, please refer to:

• Appendix A – Technical Support

• Appendix B – Service Request

3

DIKSHA Support

7 of 22

Support Severity

The responsiveness of Support is driven by the severity of a request. Requests are assigned a severity level by support team, but this may be changed after consultation with the Programs Team if it is reasonable to do so in accordance with the severity levels as defined below.

  • S1 - DIKSHA’s functionality is completely unavailable or inaccessible.
  • S2 - DIKSHA’s functionality is impaired, a single function is impacted but key programs are not interrupted.
  • S3 - The problem causes minimal operational or program impact, a general technical question or enhancement request.�

4

DIKSHA Support

8 of 22

Service Level Agreement

  • Service Milestones

5

DIKSHA Support

Milestone

Description

Response

Initialization of the support process, through engagement with the partner to progress information gathering, analysis or issue replication.

Resolution

Provision of a solution to an request or problem, either by employing a temporary fix, an answer or a technique that provides a solution to the reported problem.

9 of 22

Service Level Agreement

  • Service Timelines per Milestone

6

DIKSHA Support

Severity

Response

Resolution

S1

4 Service Hours

48 Service Hours or *ETA

S2

8 Service Hours

5 Business Days or *ETA

S3

24 Service Hours

10 Business Days or *ETA

  • * ETA – Estimated Time of Resolution

Note: For Data Anomaly - Investigation takes up to 7 working days, post-investigation ETA will be shared.

10 of 22

SLA’s for Service Requests – Survey & Projects

13

DIKSHA Support

Service Type

Timelines

Sub Role Upload

2 Business Days

Observation Sol/Survey - Upload+Mapping+Link Generation

4 Business Days

Observation Sol/Survey – Modification

4 Business Days

Improvement Projects - Upload/Mapping/Modification

4 Business Days

Program Manager & Program Designer Role Mapping

2 Business Days

11 of 22

SLA’s for Service Requests – Platform & Courses

13

DIKSHA Support

Service Type

Timelines

Content Provider Org Upload

3 Business Days

State School Data Upload

7 Business Days

User Upload

2 Business Days

Reverse Verification

5 Business Days

State Tenant Page Creation

5 Business Days

12 of 22

SLA’s for Service Requests – Platform & Courses

13

DIKSHA Support

Service Type

Timelines

Framework Upload (Only BMGS)

5 Business Days

Geo or Location Upload

8 Business Days

Content Bulk Upload

7 Business Days

Taxonomy Upload

7 Business Days

13 of 22

Service Level Agreement

  • Timelines

All timelines are measured from the original time and date of the request unless otherwise specified. DIKSHA’s support team shall monitor performance against response and resolution timelines and shall report on the percentage of requests where these timelines are achieved within the respective target. DIKSHA’s support aims to achieve 99% compliance against these stated timelines.

Note: Should Support reasonably request additional information, the time periods where Support is awaiting a response from the Partners/Programs Team will be deducted from the measurement of Service Level Targets (SLAs).

7

DIKSHA Support

14 of 22

Support at Level 1

DIKSHA provides first line (L1) support for issues that can’t be handled by the partners or for which partners require additional information/clarification to ensure continued program availability.

Key responsibilities include:

  • Response to incidents raised by Partners.
  • Knowledge base searching to verify if reported problems are already known issues with a defined resolution plan.
  • Impact analysis with accurate classification of reported issues to ensure appropriate prioritization.
  • Qualification/replication of the reported issue in an appropriate partners/users environment.
  • Provision of technical resolution or problem workaround.
  • Information gathering to ensure complete availability of details required for root cause analysis.
  • Problem routing/escalation to second/third level support where required.

9

DIKSHA Support

15 of 22

Support at Level 2

DIKSHA provides second line (L2) support, with expert Senior Technical Support professionals providing analysis and resolution of reported issues.

Key responsibilities include:

  • Problem replication and diagnostic troubleshooting.
  • Provision of technical resolution or problem workaround.
  • Issue verification with full documentation of replication environment and workflow.
  • Workaround analysis for identified issues.
  • Delivery of workarounds/fixes provided by L3 Support.
  • Problem routing/escalation to third level support where required.

10

DIKSHA Support

16 of 22

Support at Level 3

DIKSHA’s engineering team provides third line support services for back-to-back consultation with second line support , including the delivery of code changes, planned releases, and hotfixes.

Key responsibilities include:

  • Escalation support for unresolved second line technical support issues.
  • Workaround analysis for escalated issues.
  • Issue resolution through the deployment of hotfixes and planned releases.
  • Issue roll-up/back-port between code branches.
  • Quality Assurance and acceptance testing.

11

DIKSHA Support

17 of 22

Support Workflow

Support services are delivered through a leveled support model. The following diagram details the process flow followed during the lifecycle of an request and the key responsibilities defined within each support level.�

8

DIKSHA Support

18 of 22

Service Request - Workflow (with Programs Team)

The following is the prescribed process flow for service requests.

1. SL program manager/team identifies the need for ID/Access Creation/Modification/Clarification/Deletion.

2. SL program team routes this request to the State SPOC

3. State SPOC routes the request to Diksha Support Team (the regular process being followed for all tenants)

4. Request is serviced and confirmation sent to the State SPOC along with the people marked in the initial email from the State SPOC.

8

DIKSHA Support

19 of 22

Knowledge Base (KB) Articles

DIKSHA provides a wealth of vital information via the DIKSHA’s Help Centre including the app and portal documentation, and FAQs driven knowledge base. For general technical queries, troubleshooting specific issues or seeking to prevent known problems from occurring, the knowledge base is an effective resource. The DIKSHA Support knowledge base consists of articles created to enable sharing of information about known problems and their resolution, software update releases, ‘how to’ information, implementation tips/ tricks, etc. Partners can search and view the KB articles at DIKSHA’s Help Centre. �

12

DIKSHA Support

20 of 22

Thank You

21 of 22

Appendix A – Technical Support

13

DIKSHA Support

Login

Observations

Projects

Feedbacks & Survey

Programs

Tasks

Library

Polls

My Institutions

Reports

Dashboard

Sync

22 of 22

Appendix B – Service Requests

13

DIKSHA Support

Roles

Improvement Projects

Observation Solution 

Feedbacks & Survey