DIGIT offers several modules. Each module is designed to automate the manual workflows for various governance units.

Key Benefits

DIGIT enables ULBs to be more effective and accountable—and to make better, data-driven decisions. The platform ensures both interoperability among ULBs and rapid development of new modules by a wide array of software partners.

About mCollect

The mCollect module is designed to facilitate the ULBs process miscellaneous types of payments. Miscellaneous payments may include parking fees, advertising fees, etc. The module objective is to process and record payment collections on account of miscellaneous heads within the ULBs. This makes it easy to track payment receipts and generate reports for administrative purpose.

Key Features

1. Capture details of payment collection

2. Generate and print the collection receipt

3. Access to dashboard analytics

4. Generate reports for administration

Section Overview

This section contains all docs and information required to understand the MCS module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the MCS module.

• Functional Specifications

• MCS Roadmap

• MCS User Manual

• Product Brochure

• MCS Workflows

• Master Data Configuration Template

• MCS Service Configuration

• Implementation Handbook

• Demo Script

Navigation Tips

• Click on the embedded links within the content to browse topic details

• Use the Contents links available on the right side of the screen to move to a specific heading

• Find the list of Related Docs links at the bottom of each page to browse through additional product details.

Contact Us

Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on MCS module deployment.

#147/J, 1st floor, 10th Cross, 12th Main, 3rd Block, Koramangala, Bangalore 560034

• ​Find us on map​

• +91 80 4125 5708

• contact@digit.org

Roadmap Overview

Commitment and transparency are deeply ingrained values defining our product development approach. We are constantly developing new capabilities to facilitate the digital transformation of our cities. Take a glimpse into our DIGIT Roadmap to learn more about our upcoming tools and features.

Quarter 1 - April to June 2021

Quarter 2 - July to September 2021

Quarter 3 - October to December 2021

Quarter 4 - January to March 2022

Overview

Emptying of septic tank / Pit (Desludging) request can be created by the citizen online which will be processed by the ULB. The processed request will then be assigned to a particular desludging operator post payment of desludging charges by the citizen.

The desludging operator then completes the emptying task on the ground and transports the faecal sludge to the designated septage treatment plant where a plan operator updates the vehicle log and septage dumped at the plant.

Release Highlights

1. Citizen

   1. Create Emptying of septic tank/pit application

   2. View status of the application

   3. Make payment for an application

   4. Rate the service

2. Employee

   1. Create Emptying of septic tank/pit application

   2. Update application

   3. Make payment for an application

   4. Assign/Re-assign DSO for an application

   5. Complete request on behalf of DSO

3. Desludging operator

   1. Assign vehicle to a request

   2. Decline a request

   3. Complete request

4. FSTP Operator

   1. Update vehicle log

Release Features

Known Issues

None

Upcoming Release Features

• Dashboard and Reports

Reference Doc Links

MDMS changes

Config Changes

Infra Change

Service Build Updates

Overview

Bill Amendment is a platform-level feature that can be used to create credit/ debit notes against a consumer for a configured service. Demand revision required due to out of system calculations i.e. tax exemptions, court case settlements, one-time settlement schemes can be performed using this feature.

Release Highlights

1. Workflow-based application approval system for better accountability of demand revision.

2. Artifact generation in the form of credit/debit note for record purposes

3. Auto application of note amount into latest or upcoming bills

Release Features

Known Issues

Upcoming Release Features

1. New UI for better accessibility

2. Application initiation from the citizen side

3. Extending this feature to deal with the current year and previous year items

Reference Doc Links

The citizen pays the fees for miscellaneous services through the CEs or FEs. Once the payment transaction is complete the citizen can access the payment receipts online.

Citizens can

• Search receipts

• Download receipts

• Print receipts

Search Download And Print Receipts

Citizens can search for payment receipts and download or print these online. To search for payment receipts navigate to the Collections option in the sidebar main menu.

Enter the relevant search parameter. The system enables you to search using payment Receipt No. or Service Category, or payee Mobile No. Click on the Search button.

The system will display the relevant search results in the panel below. Click on the relevant record to view the payment receipt.

The system will generate a pdf format of the payment receipt. Click on the download icon on the pdf page to download the receipt.

Click on the Print icon on the pdf page to print the receipt.

Click on the Reset button to renew your search with different parameters.

Introduction

Service Category is a comprehensive list of services existing for the specific State/ULB. Service Category basically defines the miscellaneous revenue collection heads. Example - Rental, Entry Fees, User Charges etc.

Service categories are defined at a global level for different types of revenues. Payment collection and processing for certain services like property tax and trade licenses are done through the individual modules. The mCollect module processes payments for other miscellaneous services.

The Service Category masters list allows States/ULBs to identify the miscellaneous services for which payments and collections can be processed.

Data Table

The data given in the table is 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 all different types of service categories on the basis of ULB’s 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. 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 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.

Attachments

Configuration Data Templateconfiguration-data-template-service-category.xlsx - 10KB

Sample Datasample-confugration-data-service-category.xlsx - 10KB

DIGIT is India’s largest open-source platform for Urban Governance. It is built on OpenAPI (OAS 2.0) and provides API based access to a variety of urban/municipal services enabling state governments and city administrators to provide citizen services with relevant new services and also integrating the existing system into the platform and run seamlessly on any commercial/on-prem cloud infrastructure with scale and speed.

Key Architecture Highlights

• DIGIT is a microservices-based platform that is built to scale. Microservices are small, autonomous and developer-friendly services that work together.

• A big software or system can be broken down into multiple small components or services. These components can be designed, developed & deployed independently without compromising the integrity of the application.

• Parallelism in development: Microservices architectures are mainly business-centric.

• MicroServices have smart endpoints that process info and apply logic. They receive requests, process them, and generate a response accordingly.

• Decentralized control between teams, so that its developers strive to produce useful tools that can then be used by others to solve the same problems.

• MicroServices architecture allows its neighbouring services to function while it bows out of service. This architecture also scales to cater to its clients’ sudden spike in demand.

• MicroService is ideal for evolutionary systems where it is difficult to anticipate the types of devices that may be accessing our application.

Multi-layer Architecture

DIGIT follows Multilayer or n-tiered distributed architecture pattern. As seen in the illustration above there are different horizontal layers with some set of components eg. Data Access Layer, Infra Services, Business Services, different modules layers, client Apps and some vertical adapters. Every layer consists of a set of microservices. Each layer of the layered architecture pattern has a specific role and responsibility within the application.

• Layered architecture increases flexibility, maintainability, and scalability

• Multiple applications can reuse the components

• Parallelism

• Different components of the application can be independently deployed, maintained, and updated, on different time schedules

• Layered architecture also makes it possible to configure different levels of security to different components

• Layered architecture also helps users test the components independent of each other

DIGIT Urban Stack is a set of Open APIs, services, and reference implementations, setup as a public good, to allow government entities, businesses, startups, and civil society to use a unique digital Infrastructure and build solutions for urban India at a large scale. It provides a set of open standards, specifications and documentation to create a level playing field and enable ecosystem players to innovate on the stack. As a public good, the platform is provided without profit or restriction to all members of society.

• Open Source - DIGIT is Open Source and has been built using the best in class Open Source technology stacks powering the most advanced companies in the world. DIGIT is able to provide the lowest total cost of ownership and helps ensure that governments retain strategic control of their systems and data.

• Mobile-Enabled - DIGIT has adopted a mobile-first approach, with robust mobile applications enabling citizens to easily access government services through their phones. Government officials and field workers are also empowered with mobile applications that enable them to deliver 24×7 governance with ease.

• Real-time Dashboards - DIGIT’s real-time dashboards provide governments with actionable insights on demand. Administrators and department heads are empowered with verified data that enables them to manage their work and budgets better. Field level employee reports enable effective performance management and ensure efficient usage of government resources.

Our Core Principles

DIGIT focuses on inclusion and is designed on the principle of enhancing both platform openness and choice for citizens. The platform uses open APIs and standards, creating a powerful framework to drive convergence across the multiple systems currently in use and to lower the barrier to entry for locally-developed solutions. Keeping in mind that most Indians use the internet through their phones, we follow and advocate a “mobile-first” approach, while supporting multi-channel access to accommodate diverse needs and preferences.

Join the virtual DIGIT Technical Training sessions to learn in-depth about the DIGIT platform architecture, key capabilities, and applications. These sessions will help understand DIGIT products, platform configurations, customizations and extension possibilities.

Event registration links and session details are provided below. Click on the Register button to enrol for the sessions.

Release Summary

DIGIT 2.3 release offers new modules, few functional changes, and non-functional changes.

• Functional: Faecal Sludge Management module, Bill Amendment module, and Enhancements in HRMS.

• Non-functional: Security fixes.

New ‌Feature Additions

Enhancements

‌Document Resources and Links

UI Technical Documents

Backend Service Documents

Details coming soon..

Details coming soon..

Introduction

The mCollect module is designed to facilitate the ULBs process miscellaneous types of payments. Miscellaneous payments may include parking fees, advertising fees, etc. The module objective is to process and record payment collections on account of miscellaneous heads within the ULBs. This makes it easy to track payment receipts and generate reports for administrative purpose.

Module Features

1. Capture details of payment collection

2. Generate and print the collection receipt

3. Access to dashboard analytics

4. Generate reports for administration

Module Ontology

State Level

1. Service Category

2. Service Sub category

3. Service Sub-Category GL Code Mapping

ULB Level

None

Module Reports

1. Receipt Register

2. Cancelled Receipt Register

Introduction

The Trade License product provides a digital interface, allowing citizens to apply for the Trade License and subsequently make the trade license fee payment online.

The Trade License product enables:

• Ease of doing business — Traders can apply for new licenses, renewals, amendments, and supplemental licenses

• Regulatory Tracking — Administrators can track and manage regulatory processes

• Shorter Timelines — It streamlines and automates business licensing processes and helps a business to be set up quickly

• Data-driven decision making — The application collates valuable information on the economic activity and employment opportunities in a ULB

Functional Scope

The list below summarizes the key features supported by the TL module -

1. Registration, Login and Creation of User Profile

2. Applying for a Trade License

3. Trade License Issue

4. Modifications to a Trade License

5. Renewal of Trade License

6. Payments and Fee

7. Dashboards and Reports

8. General Features

Registration, Login and Creation of User Profile

Applying for a Trade License

User can apply for a new TL from the system. User can select the type of license to apply. The user enters trade details, owner details and documents after which application can be reviewed and submitted. Similarly, a counter employee can also apply for TL on behalf of the citizen. The system has a workflow integration which enables stage-wise approval before Approval for issuing the Trade License.

Trade License Issue

The system has the facility to assign the application to the respective Inspector for survey and verification. After the application is submitted, it goes to the document verifier. The next step after document verification is field inspection. After the field inspector’s approval, the TL is approved by the approver.

Modifications to a Trade License

The system has the facility to edit/update the Application based on the Inspection report against the application.

Renewal of a Trade License

The system has the facility to provide a hassle-free renewal process for citizen and employee ease, leading to increased revenues, by reducing unlicensed trades. The system allows sending of SMS and Email notifications and reminders based on the renewal cycle.

Payment and Fee

Dashboards and Reports

General Features

System specification in compliance with the Ease of Doing Business (EODB) BRAP 2019

List of Features- Trade License

About TL

DIGIT-Trade License (TL) enables local government to regulate the trade and protect the interest of the public at large against the health hazard and inconvenience which a business may cause. With DIGIT-TL traders can obtain the trade certificate in a simplified manner and ensure compliance with rules and safety guidelines issued by the government. The module offers the citizens and governance bodies a convenient and transparent means of processing trade licenses.

The Trade License application 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.

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

Section Overview

This section contains all docs and information required to understand the TL module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the TL module.

• Functional Specifications

• TL Roadmap

• TL User Manual

• Product Brochure

• TL Workflows

• Master Data Configuration Template

• TL Service Configuration

• Implementation Handbook

• Demo Script

Contact Us

Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on TL module deployment.

Overview

This release offers capabilities to create multi-tenant employees from the UI and provides out-of-the-box employee reports for the admins.

Release Highlights

1. Enabling multi-tenancy on the UI

2. Out of the box HRMS report

Release Features

Known Issues

None

Upcoming Release Features

UX revamp of the HRMS product

Reference Doc Links

Executive Summary

Overview of the Product

The computerized and automatic Trade License system offered by eGov, facilitates citizens who seek to apply for a Trade License within any Urban Local Body with a transparent, speedy, hassle-free and user-friendly procedure. Trade License (TL) is one of the components of a smart city that ensures a check on all the trade practices and increases the ease of conducting business within the state. Keeping in mind the benefits associated with the product offered, the proposed system is about to be implemented in 500+ ULBs across the country in 15 states. (For details on product features refer to Section-2)

Implementation Methodology for TL

For the offered product, the implementation process can be divided into seven major distinctive stages. Each stage has a predefined entry and exit criteria, roles & responsibilities to assure objective monitoring and decision making for the overall success of the engagement. The whole implementation lifecycle is typical of 38-42 weeks for the State, keeping in mind the entry and exit criteria defined at the beginning and end of each stage are met on time recommended.

Exhibit 1: Phases of Implementation.

Stage Zero is that of program setup and onboarding which is a pre-requisite for the initiative to kick-off and requires setup of the governance model, implementation Team and decision regarding other significant elements of the initiative like funding and procurement process. Stage One requires scoping of the initiative and decisions on the priorities for implementation by the State Implementation Team. In stage two, the State Team will work upon identifying and finding solutions to the significant gaps in the product offered with respect to the need of the State. Configuration and customization of the product offered is the primary objective of stage four. This involves working on various aspects of State-specific needs and incorporating them into the product offered. In stage five, post doing UAT and including all the necessary feedback on the product, the roll-out of the product is done at the State level (Go Live) from a couple of ULBs to pan State coverage in batches. Finally, in stage 6 sustenance and ongoing improvements are worked upon while the product is already functioning in the State. (For details on implementation plan refer to Section-3)

Critical Success Factors for implementation

Implementation of Trade License (TL) requires meticulous planning and close coordination between various stakeholders at the center and State level. The success of the initiative is dependent upon many factors like strong Program governance, availability of the trained resource, financial planning, targeted Implementation Team onboarding, focus on last-mile capacity building and ensuring necessary support to Urban center. Achievement of all these factors will provide the most effective and efficient roll-out and adoption of the Trade License System in the State.

Product-Overview

The purpose of this document is to give an overview of the Trade License System (TLS). The Trade License product provides a digital interface, allowing citizens to apply for the Trade License and subsequently make the payment online.

The Trade License product enables:

• Ease of doing business — Traders can apply for new licenses, renewals, amendments, and supplemental licenses

• Regulatory Tracking — Administrators can track and manage regulatory processes

• Shorter Timelines — It streamlines and automates business licensing processes and helps a business to be set up quickly

• Data-driven decision making — The application collates valuable information on the economic activity and employment opportunities in a ULB

  The TL product features can be broadly classified as the following modules:

• Registration, Login and Creation of User Profile

• Applying for a Trade License

• Trade License Issue

• Modifications to a Trade License

• Renewal of Trade License

• Payments and Fee

• Dashboards and Reports

• General Features

Click here to view module capabilities and product functional specifications.

Trade License (TL) Implementation Methodology

This section provides an overview of the methodology for State-wide implementation of TL. The Implementation of TL is distributed across seven distinct stages. Each stage has a predefined entry & exit criteria and roles & responsibilities. This is to ensure objective monitoring and decision making for the overall success of the program. Details of each stage are defined in this section.

Note: This document is specific for States that have more than 30 ULBs

TL implementation program is expected to be completed approximately between 38- 42 weeks with the resource deployment by the State and System Integrator (SI) Team (as defined below). However, it is critical that activities and exit criteria set for each stage are achieved to adhere to this timeline.

Seven Stages of Implementation for Trade License

Stage 0 - Program Setup/Onboarding

This is a set of initial critical activities undertaken on receiving a letter of Enrolment or MOU from the State. Successful completion of these activities assures that the program is started with crucial personnel, System Integrator (SI) Teams, and funds.

*Details of TL cell is mentioned in section 4 of the handbook

System Integrator (SI) Sign-up:

• System Integrator and state will agree on program scope, program timelines, and budgeting & resourcing.

Stage 1 - Program Kick-Off

This stage envisages the in-person interaction of crucial State officials and implementation System Integrator (SI) Teams to kick-start the program. This stage may require multiple interactions/meetings with different interest groups. The principal objective of these interactions is to identify scope and planning strategies for phasing/ rollout, create an active collaboration & Governance approach and agree on a high-level timeline for the engagement.

*Exploration is required to understand the Inter and Intra Departmental Jurisdictions of Local Governments with respect to Trade License.

#Details of TL cell is mentioned in section 4 of the handbook

Stage 2 - Solution Design

During the Solution design stage, key State officials and members, who are subject matter experts, are expected to share State acts and policies and help interpret the same for the System Integrator (SI) Team. This stage baselines the State-specific product features in the Product Configuration report.

Stage 3 - Configuration & Customization

This stage consists of a series of developments in accordance with the detailed project plan to ensure smooth functioning of the customised product. Master Data Collection & Environment Setup will be achieved in this phase. Further monitoring and maintenance strategies are put in place.

Stage 4 - UAT & Go Live

During this stage, demonstration of the product followed by a hands-on session is conducted for the ULB officials. Necessary training of ULB officials and resources required for UAT is conducted and identified respectively. The establishment of the State support Team and required processes are initiated in this stage.

Stage 5 – Rollout

On successful Go-Live in the Pilot ULBs, and further fine tuning to stabilize the product, the solution will be rolled out to the rest of the ULBs in phases. Guidance and support from the State Team will be required to create the rollout plans and assure the necessary infrastructure for training and deployment is available at each ULB.

Stage 6 – Sustenance and Ongoing Improvement

The final stage consists of strategies to ensure the sustenance of the product in the State. Systems are put in place to ensure the continuous tracking of data and provisions are made to improve the product if new data suggests.

Roles and Responsibilities - TL Cell, eGov Team & System Integrator (SI)Team

This section outlines the activities involved in each stage of the implementation along with responsibility and accountability of critical stakeholders - State, eGov Team and System Integrator Team onboard.

TL Cell: TL Cell is the government-appointed body chaired by the Principal Secretary/Secretary, Urban Development Department with members from Urban Development Department etc.

Resource requirements for the TL cell required to be formed by the State

eGOv Team: eGov Team is the technical partner of the project which will provide all necessary support to the State concerning the implementation, Program Designing etc.

System Integrator (SI)Team: SI Team will be responsible for consulting, program management and the implementation of products in the ULBs in close collaboration with the TL cell, technical partner (eGov) and various other stakeholders.

Overall Program Assumptions

Glossary

Vision:

Defining the time frame to go live, the time frame to scale it pan state, the value proposition of the programme for the state and year-on-year financial targets and adoption targets

Project Plan:

A detailed plan of Program schedule/timelines, implementation phases, team structure and ongoing support and maintenance required.

System Integrator:

The Entity/Company which collates all the subsystem required for the project and integrates them to achieve the program objective

Program Charter:

Outline of implementation plan agreement with priority applications and broad timelines, program governance model, program success metrics and capacity building.

Acceptance Letter/MOU:

Formal Acceptance/Sign Off of the Client State with a clear mandate of the Program

Program Success Metrics:

Defining the parameters (which are measurable) prior to the program, on which the success of the program is to be measured on the completion of the program

Project steering committee:

The key body within the governance structure which is responsible for the business issues associated with the project that are essential in ensuring the delivery of the project outputs and the attainment of project outcomes.

Project governance:

Set of policies, regulations, functions, processes, procedures and responsibilities that define the establishment, management and control of projects, programmes and portfolios.

Scoping:

List of activities measured against time taken to complete them in accordance with the project goals

Baseline data:

Set of information that serves as a foundation to compare other data acquired afterwards

Project Kick off meeting:

Meeting with the project team and the client of the project. This meeting would follow definition of the base elements for the project and other project planning activities

Fitment Study:

GAP Study of the Existing/Required Field Process Vs Product

Data migration:

Existing Records of the functional activities need to be moved into the Database of the newly released Application

Data collection:

Required data for the roll-out of the applications, which needs to be collected from the existing functional process

Data validation approach:

This approach enables the sanctity of the Data with built-in validation by Design

Data synchronization:

The process of establishing consistency among data from a source to a target data storage and vice versa and the continuous harmonization of the data over time.

Pilot Implementation:

Any new process is tested out as pilot in one or two instances before pan implementation

Pilot ULB:

The ULB's Selected for the pilot implementation are called pilot ULB’s.

Roll out:

On successful clearance of the Pilot, the Process/Application/Services are implemented across all Offices/ULB's

Deployment:

Deployment defines the complete package of Software components set up in a particular environment

Customization:

Details of changes to be made in the Product to comply with the needed field process

Configuration:

Defining existing content such as Options and Variables based on the requirements on the ground

Product walkthrough:

Explaining the users step-by-step through a set of actions that they need to take to achieve a specific outcome

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Release Highlights

eDCR Service 1.1.0 is a baselined release that has got few enhancements to the existing features.

Release Features

Upgrade Instructions

• eDCR 1.1.0: The above feature is useful and required in other states.

  • The above features are configurable. Users can enable the features if required for the selected state.

• Impact: Functionally, the upgrade to eDCR 1.1.0 will not impact the existing environments.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

The Service Subcategory refers to the secondary level of services. For instance, the Sanitation Tax service describes the specific tax collection service existing at the ULB level.

Before creating the Service Subcategory make sure you have created the Service Category list. Map the Service Subcategory to the corresponding Service Category.

Data Table

The data given in the table is 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 all different types of service subcategory on the basis of ULB’s 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. 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 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.

Attachments

Configuration Data Templateconfiguration-data-template-service-subcategory.xlsx - 14KB

Sample Datasample-confugration-data-service-subcategory.xlsx - 14KB

Introduction

Service Subcategory is mapped to relevant GL code to help capture the accounting-related parameters for each service subcategory. The same is used to pass the accounting vouchers into the accounting and finance system.

Data Table

The data given in the table above is 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 all different types of service subcategory GL code on the basis of ULB’s 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. 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 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 is no entity-specific checklist activity applicable.

Attachments

Introduction

Once the Trade Ontology is defined, the next step is to allocate the license fee associated with the Trades.

Dependent on the Trade Classification Level (/ ), the fee allocated might be the same across the Sate or could vary from ULB to ULB. There could be a distinct fee(s) for two different types of applications (new and renewal).

Following are the key tasks to be executed :

• Allocate the License Fee according to Trade Classification Level (Types/Subtypes).

• Map the License fee with respective Trade Classification Level.

Data Table

The table above contains sample data.

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.

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

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

6. Fill in the New License Fee & New Renewal Fee accordingly. The New License Fee & Renewal Fee can be the same as well as distinct, depending on the by-laws/ mandate followed by the State/ULB.

7. Fill in the fields related to Units of Measurement (UOM Unit, From/To) for the available trades only.

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

The table above contains sample Trade Category data.

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

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

The table above contains sample data.

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

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

Attachments

For traders to do business in India, ease in redundant procedures and regulatory processes is of paramount importance. DIGIT-Trade License increases procedural efficiency and improves the accessibility and transparency of information thus enabling the business to flourish and function with ease.

All content on this page by is licensed under a .

The mCollect module is designed to facilitate the ULBs process miscellaneous types of payments. Miscellaneous payments may include parking fees, advertising fees, rent, challans, etc. The module objective is to process and record payment collections on account of miscellaneous heads within the ULBs. This makes it easy to track payment receipts and generate reports for administrative purposes.

Key Features

The MCS module enables ULB employees to -

• Capture payment details

• Generate and print payment collection receipts

• Access dashboard analytics

• Generate reports for administration

User roles

Refer to the table below to understand the different user roles and the scope of action linked to each role. The applicable user roles and action items can vary from one State to another. DIGIT customizes the workflows to suit the requirements defined at the State level.

Using MCS

This section guides you through the details of using the MCS module for the defined roles. Click on the relevant role below to learn more about how to use the MCS system.

CE And FE

The counter employees or field employees collect and process the miscellaneous payments on behalf of the citizens.

The CE or FE role can -

• Collect payment

• Search payment receipts

• Print receipts

• Download payment receipts