DIGIT environment setup is conducted at two levels.

• State Level Setup

• ULB Level Setup

Introduction

An email account of the client/state team has to be set up in order to receive/send the email notifications.

In order to achieve the functionality, an email account has to be set up at there server since most of the states would defer from creating an account with the Gmail/public server. Further, this email account has to be integrated with the various DIGIT modules.

Data Table

In order to achieve the above functionality, we require the below-mentioned details

Procedure

Data Definition

Steps to fill Data

Below steps could be followed in order to fill the template:

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Ask the state to gather all the data related to the technical configuration from the email server settings.

5. Get the attached template filled from the state and a sample data is provided in the data table section for reference.

6. The data would be available in the POP and IMAP account settings at the server level.

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

Checklist

The checklist is a set of activities to be performed one 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.

Entity Specific Checklist

Not Applicable

Attachments

Introduction

Point of Sales (POS) machine is a machine that helps in handling transaction processing. This machine accepts and verifies the payments which are made by citizens for prevailing the services of DIGIT.

POS facilitates a middleware app developed in order to verify the payment process between the DIGIT module and the payment.

In this case, no data is required from the state team.

Data Table

Not applicable.

Procedure

Not applicable.

Checklist

Not applicable.

Attachments

Not applicable.

Objective

Content of pages within this document is designed to help implementation parties and end-users in providing the required data in minimal interaction and iterations and ensure the quality, consistency and shape of data needed to configure into the system.

Audience

This page is intended to help stakeholders as given below on data gathering activities.

1. State Team

2. eGov Onsite Team/ Implementation Team

3. ULB Team (Nodal and DEO)

4. Implementation Partners

Output Artefacts

The artefacts of this document are the data template of a configurable entity, a page with content defining the entity template and helping on how to fill the template with required data.

Introduction

SSL is Secure Sockets Layer is an encryption-based network security protocol developed for the assurance of privacy, authenticity and data integrity in internet communications.

Ideally, the domain name configuration and the SSL certification are obtained consecutively without fail from the state’s IT team.

No data is needed from the state team for this.

Data Table

Not Applicable

Procedure

Not Applicable

Data Definition

Not Applicable

Steps to fill data

Not Applicable

Checklist

Not Applicable

Attachments

Not Applicable

Introduction

Whenever an android mobile App is developed it has to be published on the Google play store in order to let the users avail its service. This page provides information about configuring the google play store account to make DIGIT mobile apps available for easy download.

Data Table

In order to start the configuration for the google play store following would be required:

Procedure

Data Definition

Steps to fill Data

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Ask the state team/client to create an email account on Gmail.

5. Ask the client to log in to the google play console here and make the required payment so that further tasks could be processed.

6. Ask the client to share the email id and password in the template.

7. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed one 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.

Entity Specific Checklist

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

Attachments

Introduction

DIGIT has modules which require the user to pay for the service that he/ she is availing for example property tax, trade license etc. . In order to achieve the functionality, we have a common payment gateway developed which acts a liaison between DIGIT apps and external payment gateways (which depends on the client requirements).

This module facilitates payments and lookup of transaction status.

Data Table

Following are the details required from the payment gateway vendor in order to configure the payment gateway:

Procedure

Data Definition

Steps to fill data

The payment gateway is a vendor oriented service that is integrated with different modules in order to facilitate the transactions. Below mentioned are the steps which are followed:

1. The client has to finalize a payment gateway vendor (for example PAYU, Paytm, HDFC, AXIS atc.) depending upon the requirements.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. After which the details/ documents mentioned in the template would be provided by the vendor.

5. These details are to be received separately for both prods as well as UAT.

6. Get the IP address for UAT and Production environments whitelisted from the vendor.

7. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed one 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.

Entity Specific Checklist

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

Attachments

Key configurations at the state level include -

Introduction

The SMS service is a way of communicating necessary information/updates to the users on their various transactions on DIGIT applications.

In order to update the users, there are certain notification parameters that are system configured for various steps in the application process. These configurations can be changed/reconfigured based upon the ULB requirements.

Data Table

We have the below-mentioned parameters which we use for configuration:

Procedure

For the SMS service to be integrated there are various things for which the vendor more or less guides us for the steps to be followed but below mentioned are a few basic steps and the generic data definitions which could be followed.

Data Definition

Below mentioned are the descriptions of the parameters which are needed for configuration:

Steps to fill Data

Since the SMS service is a vendor delivered service for which the below steps would have to be followed:

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. The SMS vendor has to provide the data in the data template attached.

5. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed one 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.

Entity Specific Checklist

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

Attachments

Introduction

An Urban Local Body (ULB) is defined as a tenant. The information which describes the various attributes of a ULB is known as tenant information. This detail is required to add the ULB into the system.

Data Table

Procedure

Data Definition

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 as given in this document under section 'Data Definition'.

3. Make sure all the headers, its data type, field size and its definition/ description are understood properly.

4. In case of any doubt, please reach out to the person who has shared this document with you and discuss the same to clear out the doubts.

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

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

Checklist

The checklist is a set of activities to be performed once 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.

Entity Specific Checklist

This checklist covers the activities which are specific to the entity. There are no checklist activities exists which are specific to the entity.

Attachments

Introduction

The domain name is the address through which the internet users can access the website rather than entering the whole IP address in the search bar of the browser.

This domain name is ideally chosen by the state/client since its a product which has to be used for/by them.

Data Table

Following is the table through which the information can be shared.

Procedure

Since all state governments/clients prefer to host the websites on their servers, this activity is ideally done by them.

Data Definition

Steps to fill data

Following are the steps which are to be followed:

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. If the state agrees to host the website on their server, provide them with the 2 columns mentioned in the attached template.

5. If the state disagrees to host on their server, then a domain name has to be purchased by any of the external vendors and the EXTERNAL-IP address has to be mapped with them.

6. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

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

Entity Specific Checklist

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

Attachments

Introduction

The departments are defined as different sections within the ULB based on which the functions performed by ULBs and employees in ULB are grouped. The budgets details of the ULBs are also defined by the department. It is suggested that the ULB across the state adopt the same department naming terminology. This document will help you in filling the department detail in the template provided.

Data Table

Procedure

Data Definition

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 given in this document under section 'Data Definition'.

3. Make sure all the headers, its data type, field size and its definition/ description are understood properly.

4. 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.

5. Identify all the departments in ULB well before start filling then into the template.

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

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

Checklist

The checklist is a set of activities to be performed 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.

Entity Specific Checklist

This checklist covers the activities which are specific to the entity. There is no entity-specific checklist is applicable for this entity.

Attachments

ULB level setup involves the configuration of ULB specific data parameters such as ULB boundaries, ULB bank accounts, and hierarchy details.

Introduction

A ULB is divided into certain categories of boundaries by ULB administrative authorities in order to carry out ULB’s functions better. A ULB/City could be divided by a different set of delimitation of boundaries based on functions as given below.

1. Revenue - Delimitation of ULB into boundaries to perform the target setting and collection of revenue.

2. Administration - Delimitation of ULB into boundaries for the better administration of ULB.

3. Locality/ Location - Delimitation of ULB into boundaries based on the places known to citizen with names and easily identifiable by the common person.

All these authorities have designated certain levels of boundary classification for a certain ULB.

Data Table

The below mention table is used to collect data for the types of hierarchy being followed:

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Identify all the types of boundaries which are being used in the state in order to carry out various administrative/revenue functions.

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

6. Then fill up the hierarchy types and the codes in the respective columns in the template.

7. Code should be created for the type of boundary being classified.

8. A brief description of the boundary hierarchy type would be helpful.

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

Checklist

The checklist is a set of activities to be performed one 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.

Entity Specific Checklist

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

Attachments

Introduction

The Trade License application, developed on the eGov-DIGIT platform, makes the process of obtaining a Trade License easy, smooth, and transparent. The module, hence, removes the need for manual processing and streamlines the key trade license management functions to provide a better user experience.

Module Features

DIGIT Trade License module enables citizens to -

1. Apply for new trade license or renew an existing trade license.

2. Upload all the relevant documents required for the license.

3. Make payment for the Trade License (New/Renewal) fee using the online payment gateway.

4. Receive notifications and alerts by emails or SMS for new application status updates and pending renewals.

5. Download Trade License, Payment & Acknowledgement Receipts online.

DIGIT Trade License module enables employees to -

1. Create flexible role-based workflows.

2. Configure license fees calculation logic.

3. View custom dashboards for module statistics.

4. Filter search results using advanced configurable search parameters.

Module Ontology

State Level

1. Trade Category

2. Trade Type

3. Trade Sub Type

4. Trade License Documents Attachment

5. Structure Type

6. Structure Subtype

ULB Level

1. Trade License Fee

Module Reports

1. Receipt Register

2. Application Status

3. Cancelled Receipt Register

4. ULBwise Collection Report

5. ULBwise Application Status

Introduction

Localization is a practice to localize various UI visible data into the local wordings according to the client's requirements. This practice of localization is enforced to various clients so that it becomes easier for the people using the service to understand the common terminology and make the best use of the available system.

The following texts (but not limited to) on the web page can be localized:

1. Labels

2. Messages: Alert messages, success messages, validation messages and other notifications etc.

3. Help Texts

Data Table

Procedure

Data Definition

Steps to fill Data

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Present the client the full sheet of codes as well as the English language for which the localized texts are required.

5. Ask the client to fill the localized text in the last column which is the message(local language) column.

6. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

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

Entity Specific Checklist

Not Applicable

Attachments

Introduction

This is the 3rd step that comes after the boundary data collection. Cross hierarchy mapping happens in case a child has a relationship with more than 2 parents. This double relationship between the child and parents could happen between different hierarchies as well.

For example: In Admin level boundary hierarchy a mohalla M1(child) could be a part of 2 Wards(parent) W1 and W2. In such a case a single Mohalla(child) has to be mapped to 2 Wards(parent).

Data Table

Below is the data table for the Boundary:

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Firstly Identify all the child levels which have a relation with more than 2 parent boundary types and their hierarchy types as well.

5. Fill up the boundary hierarchy (names/ codes) types in place of boundary type 1/2.

6. Then along with the codes start filling in one by one with the proper mapping between every child and parent.

7. The Sr. No should be in an incremental order for every new child level.

8. Prepare a new table for every different parent-child relation.

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

Checklist

The checklist is a set of activities to be performed one 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.

Entity Specific Checklist

This checklist covers the activities which are specific to the entity. There is no entity-specific checklist activity applicable here.

Attachments

Introduction

The Trade Category List can be defined as the primary or the 1st level classification “head” for trade(s) defined at a ULB/State Level.

Data Table

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.

3. Enter a unique Trade Category Code for each trade head.

4. Enter the Trade Category Name. Some trade categories are already defined in the master. Add new categories as required.

5. Enter the Trade Category Name (Local Language).

Checklist

The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. 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.

Entity Specific Checklist

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

Attachments

Introduction

This is the next step after collating all the boundary hierarchies which are being used in the state. In a hierarchy, there are certain types of boundary classification and in all the levels there will be a mapping which we could define as a parent-child mapping in order to link certain levels of the classification.

For example, a hierarchy could be:

Administration Hierarchy: City/ULB → Zone → Ward → Locality

In the above-mentioned hierarchy, a City/ULB is being divided into different into zones followed by zones into wards and at the end wards into the locality.

Data Table

Data has to be collected for every boundary hierarchy type and boundary type with a mapping between the boundary code and its parent boundary code. Following is the table which is to be used across all the hierarchy types.

Procedure

Data Definition

Following is the definition of the data columns which are being used in the template:

Steps to fill data

Following are the steps which should be used to fill the template:

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. After Identifying all the boundary hierarchy, get the sub-classification of all the hierarchies.

5. Figure out the codes for all the sub-classification for a particular city/ULB.

6. Start filling the template from the top of the hierarchy in a drill-down approach.

7. A parent-child mapping code has to be created for every boundary level except for the top level.

8. Follow the steps until you reach the last sub-classification.

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

Checklist

The checklist is a set of activities to be performed one 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.

Entity Specific Checklist

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

Attachments

Introduction

It is a ULB bank account which is operative at least to receive or deposit the day to day revenue collection done by the ULB. It is used by online payment integrator to disburse the amount in ULBs accounts which have been collected through a payment gateway into a pool account managed by the payment gateway.

Data Table

Below given data table represents the excel template attached. Data given in the table is a sample data.

Procedure

Data Definition

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 the bank account which is to be used to transfer the amount which is collected online for various services.

5. Start filling the data starting from serial no. and complete a record at once. repeat this exercise until 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 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.

Attachments

Introduction

A designation is an act of pointing someone out with a name, a title or an assignment. For example, someone being named president of an organization. This document is to help to gather various designations data which are generally used in ULBs.

Data Table

Procedure

Data Definition

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 given in this document under section 'Data Definition'.

3. Make sure all the headers, its data type, field size and its definition/ description are understood properly.

4. 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.

5. Identify all the designations exists in the ULB, refer to governments gazette to define the designations in ULBs.

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

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

Checklist

The checklist is a set of activities to be performed 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 Checklist page 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. There is no entity-specific checklist is applicable for this entity.

Attachments

Introduction

At times in the different modules, there is a need to capture the address of the user’s place of residence or where the person is doing a trade, for which the user has to enter his/her full address which creates a task. In order to simplify the process, we can have google map geolocation service in place which would help us get the exact coordinates of the place on the map and help us identify the place.

This service is paid and the client has to purchase the below items:

Data Table

Note:

Procedure

Data Definition

Steps to fill the data

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Ask the clients to purchase the above-mentioned APIs in the Introduction section.

5. Get the details for the API URL and key from the client.

6. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed one 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.

Entity Specific Checklist

Not Applicable

Attachments

Introduction

The structure type is the first level of classification of the premises where the trade has to be established and conducted. This is mostly used as management information in the trade detail.

Data Table

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.

3. Contact the person who shared this template with you to discuss and clear your doubts.

4. Enter the relevant structure types.

5. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. 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.

Entity Specific Checklist

The separate entity-specific checklist is not needed for this entity data template.

Attachments

Introduction

Once the Trade Categories are defined, the next task is to -

• Define Trade Types

• Map Trade Category to listed Trade Types

The Trade Type can be defined as the next (2nd) level classification of Trade. There can be multiple trade types and the list may vary from one State/ULB to another.

Data Table

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.

3. Select the relevant Trade Category Code from the available drop-down list of Trade Category. This will map the listed Trade Type to the corresponding Trade Category.

4. Enter a unique Trade Type Code to identify the type of trade.

5. Enter a Trade Type Name (In English).

6. Enter the Trade Type Name (In Local Language).

Checklist

The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. 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.

Entity Specific Checklist

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

Attachments

Introduction

Along with the rates, the Trade License application process does require certain documents as an attachment of proof. The proof can be defined by a set of documents ranging from

• Identification Proof (Drivers License/ Voter Card/ Adhaar/ Pan etc.)

• Trade Premises Proof (Lease Agreement, Electricity Bills, etc).

• Misc Documents (Affidavit, Self- Declaration, etc).

The Number and the Documents required could vary across the State, ULB(s), and might be dependent on Trade Subtypes, all of which are totally configurable on DIGIT.

Data Table

Procedure

How to fill data

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Identify the “Trade Sub Types” that exists at a ULB/ State level.

5. Collect the above information and feed it below the “Trade Sub Type Name” column accordingly. The Description of Trade Sub Type Name must be provided as per the language specified in the respective column.

6. Add the “Trade Sub Type Code” respectively against the identified trade type(s).

7. Fill in the *Document 1 & *Document 2 columns respectively.

Checklist

The checklist is a set of activities to be performed one 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.

Entity Specific Checklist

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

Attachments

Introduction

Structure sub type is the second level of classification of the premises where the trade has to be established and conducted. This is mostly used as management information in the trade detail.

Data Table

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.

3. Contact the person who shared this template with you to discuss and clear your doubts.

4. Enter the relevant structure sub types with its proper mapping with structure type.

5. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. 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.

Entity Specific Checklist

The separate entity-specific checklist is not needed for this entity data template.

Attachments

Introduction

DIGIT Property Tax facilitate ULBs and citizens to automate the assessment/ re-assessment of property tax for a property and its demand billing and collection. It also enables the ULBs as well as citizens to process the transfer of title of a property in case of a sale, gift or will and captures the history of ownership.

Module Features

The main features of the product are as given below.

1. Completely automated assessment and re-assessment of property tax against a property.

   1. Online self-assessment process

   2. Integrated workflow for ULB staff to perform the check and approve.

2. Transfer of title (Mutation)

   1. Online application

   2. Integrated workflow for ULB staff to perform the check and approve.

3. Generating the demand

4. Collection of property tax through various modes (Cash, Cheque, POS (Credit/ Debit Card), NEFT/RTGS, Online - Through Payment Gateway)

5. Auto calculation of rebate, interest and penalty.

Module Ontology

State Level

ULB Level

Module Reports

1. Receipt Register

2. Cancelled Receipt Register

3. Demand Register

Master data templates allow users to configure the key parameters and details required for the effective functioning of the modules. This section offers comprehensive information on how to configure the master data templates for each module.

Introduction

Trade Type can be further sub-classified into Trade Sub Type depending on the trade ontology existing in the ULBs or States. Hence, Hotels can be further classified into Dhabas in North India or Udupis in South India.

Once the are defined, the next task is to -

• Define Trade Sub Types

• Map Trade Types to corresponding Trade Sub Types

Data Table

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.

3. Select the relevant Trade Type Code from the Trade Type master data. This will map the listed Trade Sub Type to the selected Trade Type.

4. Enter a unique value for Trade Sub Type Code.

5. Enter the English name for Trade Sub Type Name (English).

6. Enter the local name for the Trade Sub Type Name (Local Language).

Checklist

The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. 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.

Entity Specific Checklist

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

Attachments

Introduction

The first level of classification of a property based on its construction is defined as Property Type. Generally, the property is divided into two types :

• Built-up

• Vacant Land

Data Table

Procedure

Steps to fill data

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

4. Identify the “Property Types” that exists at a ULB/ State level.

5. Collect the above information and feed it below the “Property Type Description” column accordingly. The Description of Property Type must be provided as per the language specified in the respective column.

6. Add the “Property Type Code” respectively against the identified Property Type(s).

Checklist

The checklist is a set of activities to be performed once 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.

Entity Specific Checklist

There is no separate checklist applicable to this entity.

Attachments

Introduction

The Construction Type refers to the list of Building construction types in the ULB limits considered for tax calculation.

DIGIT Property Tax system has certain pre-defined categories namely :

• Pucca

• Semi Pucca

• Kuccha