Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

Grievance sub-type defines the second the second level of classification of grievances which are related to ULB’s functions and add adds detail to a grievance type.

Data Table

Data table below represent the structure of template and given here to explain the template in detail.

Sr. No.

Grievance Subtype Code*

Grievance Subtype * (In English)

Grievance Subtype* (In Local Language)

Grievance Type Code*

Department Code*

SLA* (In Hours)

1

SLS01

No Street Light

कोई स्ट्रीट लाइट नहीं है

SLS

TP

48

2

SLS02

Street Light Not Working

स्ट्रीट लाइट काम नहीं कर रही है

SLS

TP

48

3

WNS01

Illegal Discharge of Sewage

सीवेज का अवैध निपटान

WNS

PHS

48

(Note: The Rows in the above table consists of Sample Data)

Procedure

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

1

Grievance Subtype Code

Alphameric

Max: 60 CHARAlphanumeric

64

Yes

Unique code given to the grievance subtype and is used to uniquely identify the complaint subtype. E.g. SLS01 given above in data table to identify Street Lights complaint subtype.

2

Grievance Subtype (In English)

Text

No Limit256

Yes

This is the text or string stating grievance subtype in English.

3

Grievance Subtype (In Local Language)

Text

No Limit256

Yes

This the text or string stating the grievance subtype in local language like Hindi, Telugu etc. whatever is applicable.

4

Grievance Type Code

Reference

No Limit64

Yes

Unique Reference to parent grievance type code from the Grievance Type entity.

5

Department Code

Reference

No Limit64

Yes

Unique department code from the ULB's Departments entity.

6

SLA (In Hours)

DecimalNo Limit

(5,2)

Yes

This field defined the service level agreements in hours. This the time within which a complaint raised to be resolved.

Steps to fill data

  1. Download the data template attached to this page.

  2. Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.

  3. Make sure all the headers, its data type, field size and its definition/ description is understood properly. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.

  4. Identify all different subtypes of grievances on the basis of ULB’s functions and grievance types.

  5. Start filling the data starting from serial no. and complete a record at once. repeat this exercise till the entire data is filled into a template.

  6. Verify the data once again by going through the checklist and taking care of each and every checklist point/ activity mentioned in the checklist.

Checklist

The checklist is a set of activities to be performed one after the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

To see the common checklist refer to the page Checklist consisting of all the activities which are to be followed to ensure complete and quality data.

Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

Sr. No.

Activity

Example

1

Grievance Subtype code should not have any special characters other than ‘-', and '_’.

SLS01 - [Allowed]

SLSA - [Allowed]

SLS#1 - [Not Allowed]

2

Grievance Subtype should be plan text and should not contain the special characters other than ‘-', '_', SPACE.

No Street Light - [Allowed]

No Street Light# -[Not allowed]

Attachments

  1. Grievance Subtype - Configuration Data Template - Grievance Subtype

View file
nameGrievance Subtype_Template_V1.xlsx

2. Grievance Subtype - DIGIT standard sample configuration data - Grievance Subtype

View file
nameGrievance Type and Subtype_Configuraion Data.xlsx