DIGIT Urban Stack is a set of Open APIs, services, and reference implementations, set up 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.

Know more about our Ecosystem or Contact Us for more details.

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

Access DIGIT tool is an Open Demo Instance to provide you with a first-hand experience of the DIGIT platform. Use this facility to navigate all the features & workflows of DIGIT Platform Applications.

Steps To Access DIGIT

Access DIGIT in Citizen Role

• Click here to access DIGIT as Citizen.

• Provide a mobile number for OTP verification. Make sure you provide a mobile number other than the one shared in the request form to generate demo credentials.

• Select City as City B for all transactions.

Access DIGIT in Employee Role

• Click here to access DIGIT in an employee role.

• Use the credentials to log in as an employee. (If you do not have the credentials, click here to generate your role-based credentials).

• Select City as City B.

Demo Scripts

We have added user assistance docs below to help you learn more about DIGIT modules and the use-case scenarios supported by each.

Feedback

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 3 - October to December 2021

Quarter 4 - January to March 2022

Overview

This release provides new UI/UX features for the OBPS product.

Release Highlights

New UI / UX for OBPS

Release Features

There is no change in the functionality, it is only the UI / UX upgrade. For the list of features, please refer to the release notes of 2.0 and 2.1 for BPA.

Known Issues

Upcoming Release Features

Patch release for the above fixes

Reference Doc Links

Details coming soon..

Details coming soon..

Overview

This feature allows citizens to view documents that are uploaded by employees in the specified ULB account.

Release Features

Citizen

1. Under Citizen Services, the Documents section has been added

2. All new & old documents available to citizens are seen here.

3. Documents are also divided into categories for easy UX

4. Citizens can view/download any document from here

5. Citizen is also notified when a new document is added

Employee

1. Under citizen engagement, documents section is added

2. Employees can select more than 1 ULB to create a document

3. Documents have Title, Description, Attachments and links

4. Documents can be modified and deleted from the same space

MDMS

1. Document categories can be configured from MDMS

Notifications

1. In-app notifications are sent to citizens when a new document is uploaded

Known Issues

None

Upcoming Release Features

1. Ability to expire document after a certain time period and make it auto-disappear from the citizen view.

2. Attach more details for certain types of documents like Tenders.

Reference Doc Links

Overview

This release provides a mobile number and alternate mobile number update feature as a data correction measure to allow citizens and ULBs to update correct mobile numbers in owner records.

Release Highlights

The update mobile number feature brings changes in the usage of certain features mentioned below.

Citizen

1. My Properties → View Property Details: OTP based update in the mobile number and alternate mobile number

2. Open Search and Pay: OTP based update in alternate mobile number after the payment of property tax

3. Inclusion of alternate mobile no. for below screens

   1. Property registration

   2. Property modification

   3. Property mutation (Title Transfer)

Employee

1. Search Property → View Property: Update mobile number and alternate mobile number with an attachment of documents.

2. Inclusion of alternate mobile no. for below screens.

   1. Property registration

   2. Property modification

   3. Property mutation (Title Transfer)

Notifications

1. SMS notification on the update of the mobile or alternate mobile number

2. SMS notification on payment of tax to owner’s mobile/ alternate mobile and taxpayer’s (other than the owner) mobile number

3. Property assessment notification to owner’s mobile/alternate mobile and taxpayer’s (other than the owner) mobile number

Release Features

Known Issues

1. Employee - Edit alternate mobile number option not provided if the alternate mobile number is not available in the record.

2. Citizen - Edit alternate mobile no. option not provided for the logged-in user’s alternate mobile no.

Upcoming Release Features

Property tax new UI audit

Reference Doc Links

About TL

DIGIT-Trade License (TL) enables local government bodies to regulate trading establishments. It also serves to protect the interest of the public at large against possible health hazard and inconvenience that can be caused by any business operations. 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 a 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.

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

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

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

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

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

Attachments

Configuration Data Templateconfiguration-data-template-structure-subtype_v1-1-.xlsx - 10KB

Sample Datasample-configuraion-data-structure-type-and-subtype-2-.xlsx - 9KB

MDMS Changes

Config Changes

Infra Changes

Service Build Updates

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

The table above contains sample Trade Type 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. 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

Configuration Data Templateconfiguration-data-template-trade-master-3-.xlsx - 17KB

Sample Data Templatesample-configuration-data-template-trade-master-filled-3- (1).xlsx - 19KB

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 (Types/ Subtypes), 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 the 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.

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

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 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-trade-master-4-.xlsx - 23KB

Sample Data Templatesample-configuration-data-template-trade-master-filled-4- (1).xlsx - 24KB

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 Trade Type(s) are defined, the next task is to -

• Define Trade Sub Types

• Map Trade Types to corresponding Trade Sub Types

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

Configuration Data Templateconfiguration-data-template-trade-master-3- (1).xlsx - 17KB

Sample Data Templatesample-configuration-data-template-trade-master-filled-3-.xlsx - 19KB

Introduction

The DIGIT-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.

Module Features

DIGIT Trade License module enables citizens to -

1. Apply for a 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

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

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.

🔗 Product Links

Click on the respective link below to learn more about that product, its features, applications and configuration details.

Release Summary

DIGIT 2.6 is a release that has got new modules, a few functional changes, and non-functional changes.

• Functional: OBPS UI/UX Revamp, Common UI/UX Revamp, Citizen Engagement: Documents, Property Tax Enhancements, WhatsApp Enhancements, Provision to have different content for notifications based on a channel, FSM Enhancements, TL Enhancements, and a few UI/UX gaps, PGR Enhancements, and W&S Enhancements.

• Non-functional: QA Automaton of APIs for new APIs, Technical improvements, Log4J security patch, etc.

New ‌Feature Additions

Enhancements

‌Document Resources and Links

UI Technical Documents

OBPS UI/UX Revamp

Events & Notifications

Backend Service Documents

New Docs

Updated/Refactored Docs

Overview

This service is used to issue a license to the user after verification. The service is designed in such a way that it can be used to serve different type of licenses. Currently used to issue trade licenses, perform stakeholder registration and issue lockdown pass. The service is integrated with workflow where we can define the steps for approval of the application. Once the application is approved the license is generated.

Pre-requisites

Before you proceed with the documentation, make sure the following pre-requisites are met -

• Java 8

• Kafka server is up and running

• egov-persister service is running and has tl-services persister config path added in it

• PSQL server is running and database is created

Key Functionalities

• Used for license generations in trade licenses, stakeholder registration and issue lockdown pass

• Define roles to applicants on successful application to access Building Plan Approval services at the time of stakeholder registration

• Generate application number and license number

• Support workflows

• Provide notification on various status changes for an application

Interaction Diagram

Deployment Details

1. Add MDMS configs required for Trade License and BPA stakeholder registration and restart MDMS service

2. Deploy the latest version of tl-services service

3. Add tl-service persister yaml path in persister configuration and restart persister service

4. Add Role-Action mapping for API’s

5. Create businessService (workflow configuration) according to trade license and stakeholder registration

6. Add tl-service indexer yaml path in indexer service configuration and restart indexer service

Configuration Details

Following application properties in the Trade License service are configurable.

Integration

Integration Scope

The trade-license service is currently used to issue trade licenses, perform stakeholder registration and issue lockdown pass.

Integration Benefits

• Provide backend support for the different license registration process.

• Mseva and SMS notifications on application status changes.

• The elastic search index for creating visualizations and Dashboards.

• Bpa Stakeholder registration provides new roles to the user to access the Building Plan Approval system.

• Supports workflow which is configurable

Steps to Integration

1. To integrate, host of tl-services service should be overwritten in the helm chart.

2. {servicename}/_create/ _create should be added as the create endpoint for creating any license in the system

3. {servicename}/_search/ _search should be added as the search endpoint. This method handles all requests to search existing records depending on different search criteria

4. {servicename}/_update/ _update should be added as the update endpoint. This method is used to update fields in existing records or to update the status of the application based on workflow.

Reference Docs

Doc Links

API List

In all below endpoints if the service name is BPAREG it is treated as a stakeholder registration application and if it is TL or if it is absent then the application is treated as trade license application.

Stakeholder registration APIs:- https://www.getpostman.com/collections/d18b79ccfb69ee8bb526

Trade-License APIs:- https://www.getpostman.com/collections/99f98723c45f97024831

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:

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

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.