Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Learn more about TL workflows and its configuration
Details coming soon..
Functional overview for stakeholders
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
The list below summarizes the key features supported by the TL module -
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
Key capabilities offered by this functional component -
OTP Based Login for Citizen via Web/Mobile App
OTP Based Login for Employee via Web/Mobile App
Provision for language selection during first time registration for both Employee and citizens
Provision of creating a personalized Profile for Citizens and employees on Web App
Login Credentials for the various hierarchies of employees
Role-based access for performing different actions relating to Trade License modules
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.
Key capabilities offered by this functional component -
Citizen can Apply for a new Trade License through mobile app/ Web
Citizen/CSC can capture Trade details, Trade Units, Accessories, Owner Details, Address, purpose, Date of issuance, License number etc.
Citizen/CSC Upload Documents
Citizen/CSC can calculate Breakup Based on Selected Trade
Citizen/CSC can select Multiple Accessories for the Trade
Citizen/CSC can Apply for Multiple Trade Licenses
Citizen/CSC can Download/Print Application Summary
Citizen/CSC can Download/Print Trade Reference No
Citizen/CSC can View the applied licenses
The system has the facility to deliver the service online & through SEWA KENDRA.
The portal displays all the information including the processes and documents required for the convenience of the citizen.
The system has the facility to assign a unique identification number based on the license type, which will be used for all future transactions of the license.
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.
Key capabilities offered by this functional component -
Document Verifier, Verifies & Forwards or Rejects the application
Licensing Inspector, Verifies and Forward the Application
Licensing Inspector, Sends Back or Rejects the Application
Licensing Inspectors Approves the Application
Citizen, Pays for the license post verification process online or at the CSC
CSC, Collects Fee post verification.
The system allows the printing of license and sending the license through e-mail.
The system allows the SMS alerts to the applicant regarding the date of inspection/visit by the inspector, approval/rejection of the application.
The system allows the inspector to enter the field visit details and a field visit report is generated and automatically routed to the superintendent.
The system has the facility to edit/update the Application based on the Inspection report against the application.
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.
Key capabilities offered by this functional component -
The citizen can pay for the license post verification process
CSC, Collects Fee post verification.
The system allows intimating the applicant about the payment of the license fee through SMS/ e-Mail.
The system allows the Generation of receipt for the payment
The payment modes enabled are Card(offline), cash, cheque, DD
Following reports offered by the module -
Cancelled Receipt Register Report
TL Collection
TL Application Status- showing the number of licenses approved/rejected.
TL ULB Wise Status
State Dashboard: View Reports for Total Licenses, Licenses Issued, Payment Collected, Payment Distribution
Notifications - The system has the capability to send notifications to citizens. These notifications can be sent for various steps like - verification completion, payment reminder, payment confirmation. These notifications can be sent in the language chosen by the ULB through all channels - SMS, Whatsapp, Email.
Configurable Masters - The system provides the following masters that can be configured as per the State’s requirements:
Charges & Calculation : Calculation Engine, Rebate, Penalty,
Rate Master
State Masters: Trade Ontology, Documents List, Accessories, Ownership, Employee Data Mapping, Boundary Data Mapping, Fee Matrix (License Fees)
System specification in compliance with the Ease of Doing Business (EODB) BRAP 2019
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.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
List of Functionalities | Corresponding Features |
---|---|
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Reform No.
Reform Area
Weightage (score)
Recommendation
Remarks
80
Sector Specific
2
Implement an online application system with the following features:
i. Online submission of application without the need to submit physical copy of application
ii. Eliminate physical touchpoint for document submission
iii. Allow option of online payment of application fee
iv. Allow applicant to track status of application online
v. Applicant can download the final certificate online
Already available in the system
Registration, Login, Creation of User Profile
Provision for Language Selection during first-time registration via Mobile/ Web App.
OTP Based Login for Citizen/ Employee via Mobile/ Web App
Login Credentials for the various hierarchy of employees
Provision of Personalized Profile for Citizen/ Employee on Web App
Applying for a Trade License
Citizen/CSC: Enters Trade Details, Trade Units, Accessories, Owner Details.
Citizen/CSC: Upload Documents
Citizen/CSC: ULB Wise Trade Selection
Citizen/CSC: Calculation Breakup Based on Selected Trade
Citizen/CSC: Multiple Accessories Field Count
Citizen/CSC: Multiple Trade License.
Citizen/CSC: Download/Print Application Summary
Citizen/CSC: Download/PRINT Trade Reference No
Citizen/CSC: View the applied licenses.
Citizen: Pays for the license post verification process.
CSC: Collects Fee post verification.
Trade Licence Issue
Document Verifier : Verify & Forward/ Reject the application
Licensing Inspector: Verify and Forward/ Send back/ Reject the Application.
Licensing Officer: Approve/ Send back the Application
Licensing Officer: Reject/ Cancel the Application
Modification to a Trade License
Edit/ Update the Application based on the Inspection report against the application.
Renewal of a Trade Licence
Renew trade license.
Payment and Fee
Configurable Workflow Rights : Edit & Payment Collection
Payments & Collection : Various Payment Modes
Dashboards and reports
Cancelled Receipt Register Report
TL Collection
TL Application Status- showing the number of licenses approved/rejected.
TL ULB Wise Status
State Dashboard: View Reports for Total Licenses, Licenses Issued, Payment Collected, Payment Distribution
General features
Notifications : SMS Notifications
Charges & Calculation : Calculation Engine
Charges & Calculation : Rebate/ Penalty- Date Based
Charges & Calculation : Ad-Hoc Rebate/ Penalty
Charges & Calculation : Exemptions Trade Type & Owner Type
Configuration masters
Configurable Workflow Rights : Edit & Payment Collection
Configurable Verification & Approval
This page provides configuration details for TL master data templates
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.
DIGIT Trade License module enables citizens to -
Apply for a new trade license or renew an existing trade license.
Upload all the relevant documents required for the license.
Make payment for the Trade License (New/Renewal) fee using the online payment gateway.
Receive notifications and alerts by emails or SMS for new application status updates and pending renewals.
Download Trade License, Payment & Acknowledgement Receipts online.
DIGIT Trade License module enables employees to -
Create flexible role-based workflows.
Configure license fees calculation logic.
View custom dashboards for module statistics.
Filter search results using advanced configurable search parameters.
Receipt Register
Application Status
Cancelled Receipt Register
ULBwise Collection Report
ULBwise Application Status
Apply for trade license, ensure compliance with trade safety guidelines, and lots more
DIGIT-Trade Licence (TL) enables local government bodies to regulate trading establishments. It also serves to protect the interest of the public at large against possible health hazards and inconveniences 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 Licence application makes the process of obtaining a Trade Licence easy, smooth, and transparent. The module, hence, removes the need for manual processing and streamlines the key trade licence management functions to provide a better user experience.
DIGIT Trade Licence module enables citizens to -
Apply for a new trade licence or renew an existing trade licence.
Upload all the relevant documents required for the licence.
Make payment for the Trade Licence (New/Renewal) fee using the online payment gateway.
Receive notifications and alerts by emails or SMS for new application status updates and pending renewals.
Download Trade Licence, Payment & Acknowledgement Receipts online.
DIGIT Trade Licence module enables employees to -
Create flexible role-based workflows.
Configure license fees calculation logic.
View custom dashboards for module statistics.
Filter search results using advanced configurable search parameters.
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.
TL Roadmap
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
Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on TL module deployment.
#147/J, 1st floor, 10th Cross, 12th Main, 3rd Block, Koramangala, Bangalore 560034
A comprehensive guide to an effective module demo
Welcome to the DIGIT-Trade License product demo script. The key objective of the demo script is to walk users through the trade license module and highlight module capabilities and functions.
The Trade License module offers a comprehensive platform that automates the entire trade license approval process. The TL module streamlines the entire process right from the point of citizens applying for a trade license to the trade license certificate generation.
The module aims to address key trade license governance challenges that include -
Most trades are not registered with the city administration
Lack of transparency in the manual application process
Lack of clarity in the trade license fee computation
Key benefits of using the Trade licenses application -
Transparent process and fee computation
The city administration has the registry of trades operating in the city which helps in better planning of resources
Faster issuance of licenses
Consolidated TL application help ULBs -
Plan city infrastructure
data of all restaurants/party halls are available with the ULBs with the amount of waste generated every day - ULBs can plan efficient SWM truck routing logistics to collect the waste
data of markets and hawkers are present - better infrastructure for shopping complexes can be planned
data of manufacturing and textile units are available - ULB can plan for better power management
Vital to know dangerous and offensive trades like cracker sales / Chemical companies to keep fire stations informed of events
Generate revenue and facilitate prompt services to the citizen
Any citizen who runs a business in the city should get his business/trade registered with the ULB. On registering ULB provides a valid license which is valid for a time period.
Citizens in the TL application should provide info about the
Business/trade (name, location, nature of business)
Ownership details of the trade
Required documents prescribed in the application form
Trade units and accessories - accessories are equipment that is required for the trade which might be of dangerous nature or might make noise during operation like compressors, motors, and pumps.
On submit, the application auto-generates the fee that should be paid by the application and on making the payment it moves to the department side for processing.
The fee depends on the trade type and subtype
Employee processing - Clerk - Revenue inspector - Revenue officer
Application submitted by the citizen lands in the clerk's inbox
The clerk's responsibility is to scrutinize the application and documents submitted and check for correctness.
He/she can either request additional documents from the applicant
Or Upload documents on behalf of the applicant
Or Reject the application citing the reason for a rejection
Or if the application and documents are in order, a clerk can recommend the application for field inspection
On forwarding the application, it will reach the Revenue inspector who is responsible for the field inspection of the site on the ground.
He/she does the field inspection on the field and upload the field inspection report to the application.
On attaching the inspection report the user can either recommend and forward the application for license approval or reject the application.
On forwarding, the application is routed to the revenue officer who is in charge of issuing all licenses within the ULB.
The Approver can approve the application and provide a license certificate, which the applicant can download from his login.
Possible use case scenarios for the demo -
Citizen applies for Trade License
Citizen pays the Trade License fee
Citizen applies for renewal of Trade License
Counter employee submits an application for Trade License on behalf of citizen
Counter employee accepts Trade License fee payment
Employee reviews the application and forwards it for document verification
Employee reviews the documents and forwards them for field inspection
Employee approves the trade license application
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.
Sr.No. | Trade Category Code* | Trade Category Name* (In English) | Trade Category Name* (In Local Language) |
---|---|---|---|
The table above contains sample Trade Category data.
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
---|---|---|---|---|---|
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Enter a unique Trade Category Code for each trade head.
Enter the Trade Category Name. Some trade categories are already defined in the master. Add new categories as required.
Enter the Trade Category Name (Local Language).
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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
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.
Sr. No | Trade Sub Type Code* | Trade Sub Type Name (In English) | New License Fee* | Renewal License Fee* | UOM | UOM From | UOM To |
---|---|---|---|---|---|---|---|
The table above contains sample data.
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
---|---|---|---|---|---|
Download the data template attached to this page.
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.
Identify the “Trade Sub Types” that exists at a ULB/ State level.
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.
Add the “Trade Sub Type Code” respectively against the identified trade type(s).
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.
Fill in the fields related to Units of Measurement (UOM Unit, From/To) for the available trades only.
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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
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)
For the offered product, the implementation process can be divided into seven major distinctive stages. Each stage has 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.
Stage Two - the State Team works on identifying and finding solutions to the significant gaps in the product offered with respect to the need of the State. Stage Three - involves the Configuration and customization of the product offered. This involves working on various aspects of State-specific needs and incorporating them into the product offered.
Stage Four - is about doing a pilot launch in UAT and including all the necessary feedback on the product. Stage Five - 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 Six sustenance and ongoing improvements are worked upon while the product is already functioning in the State. (For details on the implementation plan refer to Section 3)
Implementation of the Trade License (TL) module requires meticulous planning and close coordination between various stakeholders at the centre and State levels. The success of the initiative is dependent upon many factors like strong Program governance, availability of trained resources, financial planning, targeted Implementation Team onboarding, focus on last-mile capacity building and ensuring necessary support to the Urban centre. Achievement of all these factors will provide the most effective and efficient roll-out and adoption of the Trade License System in the State.
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.
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 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.
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 this handbook
System Integrator and state will agree on program scope, program timelines, and budgeting & resourcing.
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 this handbook
State Baseline Data: A Baseline Template is provided to collect certain vital information like no. of transactions, revenue collected in the last FYs, collection mode, budget data, etc. This data must be collected pre-rollout
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.
Pilot ULBs Specific Product Data Configuration: Master data is required from the Product Perspective for go live. For e.g.: Boundary Data, List of Employees etc. A Master Data Template will be provided for the collection of this particular data type.
This stage consists of a series of developments in accordance with the detailed project plan to ensure the 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.
During this stage, a 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.
Note: The Nodal Officer is responsible to identify the ULB officials who are associated with the TL process on the ground and will be working with the technological Product in the respective ULBs
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.
Note: The rollout phase needs to be detailed for iterative activities of onboarding ULBs in batches.
Note: Only once all the stages are complete in one batch of the rollout of around 30 ULBs, the next batch begins. There are multiple phases of rollout. The second batch begins after the first batch has successfully fulfilled all the criteria of the Rollout Phase. A typical timeline for the closure of rollout in each batch is 5-6 weeks (in a batch of 30 ULBs)
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 suggest.
This section outlines the activities involved in each stage of the implementation along with the 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
Note:
Designations mentioned above are as per designations already driving TLs implementation at the State level.
The description of each designation is explained below.
These are the preferred figures. In the case of Domain Expert, 2 people are subject to the availability
Description of resource persons:
Project Head: Is the Head of the TL Cell who will drive the project from the State’s Side
Domain Expert: A person who is well aware of the on-ground scenario, well versed with the act, GOs passed, Prevalent Business processes, Deviations from the acts, TL Rates/ slabs applicable
Nodal officer (EO/Commissioner/ Senior Official): the project coordinator in each district to drive the project centrally. Monitor usage post Go Live- point of escalation for Implementation Team, Seasoned and worked in Multiple ULBs on various modules and has a good understanding of TL, Facilitates and Tracks data collection Post Go Live, Monitors and facilitates the adoption of the application. point of contact for eGov, SI and at the HQ level.
MIS Expert: Day-to-day tracking of the data specific to ULBs, data entry, reporting and review to senior officials
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.
Guidelines to read the tables below:
Execute - One who owns the accountability to complete the activity
Consult - One who may initiate, guide and in the process, handhold the execution of the activity
Note: Stage 0 is where the TL cell and SI team is formed, hence there are only two entities playing a role which are that of eGov and the state leadership. Once the TL cell and SI team are finalised, their role begins in the following stages.
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 is required.
System Integrator: The Entity/Company collates all the subsystems 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 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 the 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 the 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 the 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 a pilot in one or two instances before pan implementation
Pilot ULB: The ULBs selected for the pilot implementation are called pilot ULBs.
Roll out: On successful clearance of the Pilot, the Process/Application/Services are implemented across all Offices/ULBs
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 to the users step-by-step through a set of actions that they need to take to achieve a specific outcome
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
Sr. No. | Trade Sub Type Code* | Trade Sub Type Name* (In English) | Trade Sub Type Name* (In Local Language) | Trade Type Code* |
---|---|---|---|---|
The table above contains sample data.
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
---|---|---|---|---|---|
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
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.
Enter a unique value for Trade Sub Type Code.
Enter the English name for Trade Sub Type Name (English).
Enter the local name for the Trade Sub Type Name (Local Language).
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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
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.
Sr. No. | Trade Type Code* | Trade Type Name* (In English) | Trade Type Name* (In Local Language) | Trade Category Code* |
---|---|---|---|---|
The table above contains sample Trade Type data.
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
---|---|---|---|---|---|
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
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.
Enter a unique Trade Type Code to identify the type of trade.
Enter a Trade Type Name (In English).
Enter the Trade Type Name (In Local Language).
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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
An illustrative guide to using the TL module
The Trade License (TL) module offers the citizens and governance bodies a convenient and transparent means of processing trade licenses. Trade license is the permission issued by the local governing bodies to carry on specified business or trading activity within the authorized area. It is a mandatory document required to run a business or commercial activity of any type.
The TL module enables citizens to apply for trade licenses or renew existing licenses online. It facilitates the governing bodies to validate and approve the license applications.
User Role | Scope of Action | Role Description |
---|---|---|
This section guides you through the details of using the TL module for each role. Click on the relevant role below to learn more about how to use the TL system.
Learn how to apply for new trade license, renew and pay trade license fee
Citizens represent individuals, communities, or business entities who are the system end-users. The TL module allows business owners to apply for a trade license online or even apply for renewal of an existing license.
The citizen can also approach the Counter Employee (CE) to submit new TL applications or raise renewal requests for existing licenses.
The Citizen or CE role can -
Citizens or CE can apply for a new trade license through the DIGIT web portal or the DIGIT mobile app. To apply for a new TL click on the Trade License card available in the Citizen Services section of the DIGIT home page.
Enter your Mobile Number, Name, and City details. Click on the Continue button.
Enter the OTP received on the given mobile number. Click on Continue. The system validates the details and allows the user to log in to the system with the registered mobile number.
Enter your registered mobile number and the OTP received on the mobile to log in. Click on Continue with Whatsapp button to register your service request using the WhatsApp channel.
Click on the Continue button.
Click on Apply for Trade License.
The initial application screen displays the list of documents that have to be submitted for trade license registration. Scroll through the list and make sure the required documents are scanned and ready for submission online.
Enter the Trade Name. Click on the Next button.
Click on the Yes or No option to indicate the Structure Type of the trading premises. Yes to indicate the trade will run on an immovable structure. And, No to indicate the trade will run on a movable structure.
Select Pucca or Kutcha option to indicate the Building Type. The Building Type option appears if the selected Structure Type in the previous screen is Immovable. In the case of Movable structures, the system displays the Structure Sub Type as Vehicle Type. Select Hand Driven Vehicle or Motor-Driven Vehicle option depending on the trading plans.
Enter the Trade Commencement Date. This date indicates the inception or starting date of the trade.
Select the Trade Category as either Goods or Services in the Trade Units screen. Next, select the appropriate Trade Type and Trade Sub Type from the available drop-down list. Click on Add More Trade Units button to append multiple trading units.
Select Yes or No to indicate if you have any trade accessories.
If Yes, select the applicable Accessory from the drop-down list. Enter the Count for the selected Accessory to provide details on the number of accessories required. The system auto-populates the applicable UOM, if any, for the selected accessory. Enter the UOM value. Click on Add More Trade Accessories button to append multiple accessories.
Enable the Location Finder to allow GPS to track the current location. Or, move the pin to the location manually. Alternatively, you can also enter the location in the Search bar.
The Pincode field gets auto-populated if the location is selected on the map. Else, enter the Pincode of the location details manually. Click on Skip and Continue in case you are unable to provide the Pincode details.
City and Locality/Mohalla fields are auto-populated once the Pincode is entered. Else, select the City and applicable Locality/Mohalla from the drop-down list.
Enter the Street Name and Door No. details.
Provide a Landmark to locate the trading premise.
Select either the Single Owner or Multiple Owners option to indicate the type of ownership in the Ownership Details screen.
Enter the Owner Name. Select the applicable Gender and enter the owner’s Mobile Number.
Enter the Owner’s Address. Check the Same as Trade Address box if the owner’s address and trading address are the same. This will auto-populate the trading address provided earlier.
Upload the documents as required.
Validate the information entered in the application summary screen. Click on Change to modify the information if required. Click on Submit button once the filled-in details are found correct and complete.
The system generates a unique application reference number. Click on Download Acknowledgement Form to download and print the acknowledgement.
Citizens can renew their existing trade applications on the DIGIT portal. CE can also apply for TL renewal on behalf of the citizens. To renew TL navigate to the home page and then click on the Trade License option. Click on My Applications. Click on the Renew Trade License option to view the license details for renewal.
The system will display the license details. Click on the Renew button to apply for renewal.
If there are any changes in the trade details, click on the Change button adjacent to the fields before submitting for renewal.
Click on the Submit button once all changes are done and reviewed.
The Trade License is submitted for renewal.
My Applications option allows applicants to view their applications and track their status.
Click on My Applications.
The screen displays all the applications tagged to the registered mobile number. Click on the View Details button to view the application details. In case the application is pending payment click on View Details & Pay button to make the payment.
The Application Timeline displays the current status and completed actions on the selected application. If the application status shows Pending for Payment, click on the View Details and then the Pay button to initiate payment.
Click on Pay redirects the citizen to the internet banking page and make the payment.
Click on Print Receipt to download the receipt. The citizen can also click on the home page to go back to the home page.
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.
Sr. No. | Code* | Structure Type* (In English) | Structure Type* (In Local Language) |
---|
The table above contains sample data.
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
---|
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.
Contact the person who shared this template with you to discuss and clear your doubts.
Enter the relevant structure types.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
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.
This checklist covers all the activities which are common across the entities.
A separate entity-specific checklist is not needed for this entity data template.
Along with the , 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.
Sr. No. | *Trade Subtype Code | *Trade Subtype Name (In English) | *Application Type | *Document 1 | *Document 2 |
---|
The table above contains sample data.
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
---|
Download the data template attached to this page.
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.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
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.
Add the “Trade Sub Type Code” respectively against the identified trade type(s).
Fill in the *Document 1 & *Document 2 columns respectively.
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.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
This section illustrates the steps for different employee user roles at the ULB level
Employees can
Log in to the employee portal using your credential.
Click on the New Application option in the top left corner of the landing page.
An employee can create the application on behalf of citizens over the counter.
Select the applicable Financial Year for which the trade license is to be issued.
Fill in the application details (same as given in the citizen application process).
Click on the Submit button once all details are found complete and accurate.
A unique application reference number is generated. This number is used to access the application and for further processing. The citizen receives a notification along with this application number in the registered mobile number.
Click on Inbox to view the list of applications submitted.
Click on the relevant Application Number hyperlink to open and view the application details.
Scroll down the application and click on the Take Action button. Click on Pay.
Enter the Payment and Payer Details. Click on Collect Payment to process the payment.
The system generates a unique payment Receipt Number. Click on the Print Receipt button to print the receipt. Click on the Go Back to Home Page button to navigate back to the home page.
Click on Renew Trade License option on the home page.
Click on the relevant Trade License Number to renew. Edit the trade license details in the application form as required.
Click on the Take Action button. Click on Renew Trade License option.
The user can renew it without modifying the trade details or it can be modified. If it is modified, it goes into application processing similar to a new TL application. If it is not edited then renewal happens in real-time after making payment.
Trade license applications pass through various stages where details are scanned, verified, and inspected before the final approval. The workflows are defined at the State or ULB level and adjusted to meet individual department requirements.
The prescribed stages through which trade license applications are routed include -
Document Verification
Field Inspection
Approval
Log in with Document Verifier credentials.
The employee landing page displays the list of applications waiting for processing. Use the search filters on the page to find specific applications from the list.
Click on the Application Number hyperlink to open the application.
Scroll through the application details and review the uploaded documents.
Click on the Take Action button and click on Verify and Forward option if all documents are found complete and satisfactory.
Select the Assignee Name. The application will be forwarded to the selected assignee for field inspection.
In case, the documents are found incomplete or missing, click on Send Back to Citizen option. This will send back the application to the citizen for necessary action.
Click on the Reject option if the application details are found inaccurate. This will reject the application.
Log in with Field Inspector credentials.
The employee landing page displays the list of applications waiting for processing. Use the search filters on the page to find specific applications from the list.
Click on the Application Number hyperlink to open the application.
Scroll through the application details and review the details.
Click on the Take Action button and click on Verify and Forward option if all details are found complete and satisfactory.
Select the Assignee Name. The application will be forwarded to the selected assignee for approval.
In case, the documents and details are found incomplete or missing, click on Send Back to Citizen option. This will send back the application to the citizen for necessary action.
Click on the Reject option if the application details are found inaccurate. This will reject the application.
Click on Send Back option to send the application back to the previous employee (document verifier in this case) for further action.
Log in with Approver credentials.
The employee landing page displays the list of applications waiting for processing. Use the search filters on the page to find specific applications from the list.
Click on the Application Number hyperlink to open the application.
Scroll through the application details and review the details.
Click on the Take Action button and click on Approve option if all documents and details are found complete and satisfactory. The trade license is approved and a Trade License certificate is issued to the applicant.
Click on the Reject option if the application details are found inaccurate. This will reject the application.
Click on Send Back option to send the application back to the previous employee (field inspector in this case) for further action.
The TL application is approved and the TL Certificate is issued to the applicant. Click on the Download or Print button to download or print the TL Certificate.
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.
Sr. No. | Code* | Structure Sub Type* (In English) | Structure Sub Type* (In Local Language) | Structure Type Code* |
---|
The table above contains sample data.
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
---|
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.
Contact the person who shared this template with you to discuss and clear your doubts.
Enter the relevant structure sub types with its proper mapping with structure type.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
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.
This checklist covers all the activities which are common across the entities.
A separate entity-specific checklist is not needed for this entity data template.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Refer to the for step-by-step instructions for each of these demo scenarios.
All content on this page by is licensed under a .
Sr. No. | Checklist Parameter | Example |
---|---|---|
Sr. No. | Checklist Parameter | Example |
---|---|---|
__All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Sr. No. | Checklist Parameter | Example |
---|---|---|
Sr. No. | Checklist Parameter | Example |
---|---|---|
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Stage 0 - Program Setup/ On-Boarding | |
---|---|
Stage 1 - Program kick-off | |
---|---|
Stage 2 - Solution Design | |
---|---|
Stage 3 – Configuration & Customization | |
---|---|
Stage 4 – UAT & Go Live | |
---|---|
Stage 5 – Rollout | |
---|---|
Stage 6- Sustenance and Ongoing Improvement | |
---|---|
Resource Name | No. Of Resources |
---|---|
Stage 0 - Program Setup/ On-Boarding | ||
---|---|---|
Stage 1 - Program kick-off | |||
---|---|---|---|
Stage 2 - Solution Design | |||
---|---|---|---|
Stage 3 – Configuration & Customization | |||
---|---|---|---|
Stage 4 – UAT & Go Live | |||
---|---|---|---|
Stage 5: Rollout | |||
---|---|---|---|
Stage 6- Sustenance and Ongoing Improvement | |||
---|---|---|---|
Areas | Assumptions |
---|---|
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Sr. No. | Checklist Parameter | Example |
---|---|---|
Sr. No. | Checklist Parameter | Example |
---|---|---|
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Sr. No. | Checklist Parameter | Example |
---|---|---|
Sr. No. | Checklist Parameter | Example |
---|---|---|
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by is licensed under a .
Sr. No. | Checklist Parameter | Example |
---|
All content on this page by is licensed under a .
Identify the “” that exists at a ULB/ State level.
Sr. No. | Checklist Parameter | Example |
---|
Sr. No. | Checklist Parameter | Example |
---|
All content on this page by is licensed under a .
Sr. No. | Checklist Parameter | Example |
---|
All content on this page by is licensed under a .
1
TC1
Goods
सामग्री
2
TC2
Services
सर्विस
1
Trade Category Code
Alphameric
64
Yes
The Code assigned to the Trade Category. Eg: TC1 For Goods, TC2 for Services
2
Trade Category Name (In English)
Text
256
Yes
Name of the Trade Category in English. Eg: Goods, Services etc.
3
Trade Category Name (In Local Language)
Text
256
Yes
Name of the Trade Category in Local Language (as decided). Eg: Service is described as “सर्विस” in Hindi
1
Make sure that each and every point in this reference list has been taken care of
1
The format of the Trade Category Code defined should be alphanumeric and unique
TC1: Goods
TC2: Services
2
Trade Category Name (In either Language) should not contain any special characters
Goods: [Allowed]
#Goods! : [Not allowed]
1
TRADE_SMALL_BAKERY
Small Bakery
2500
2000
Workers
1
20
2
TRADE_SMALL_BAKERY
Small Bakery
3000
2500
Workers
21
30
2
TRADE_MED_BAKERY
Medium Bakery
5000
4500
Workers
1
30
1
Trade Sub Type Code
Reference
64
Yes
The Code assigned to the Trade Sub Type. Eg: TRADE_SMALL_BAKERY is assigned to Bakery
2
Trade Sub Type Name (In English)
Text
256
Yes
Name of the Trade Sub Type in English. Eg: Small Bakery
3
New License Fee
Decimal
(6,2)
Yes
The fee charged when the license applied for the respective trade for the first time.
4
Renewal License Fee
Decimal
(6,2)
Yes
The fee charged when the license applied for the respective trade for the renewal.
5
UOM
Text
64
No
The Units of Measurement” associated with the Trade. Eg: Workers is the UOM associated with the trade “Bakery”
6
UOM From
Integer
6
No
Initial Range from which the “Units of Measurement” is applicable for a Trade
7
UOM To
Integer
6
No
Final Range to which the “Units of Measurement” is applicable to a Trade
1
Make sure that each and every point in this reference list has been taken care of
1
Trade Type Name (In either Language) should not contain any special characters
Small Bakery: [Allowed]
#Small_Bakery! : [Not allowed]
Duration
4-6 weeks
Entry Criteria
Acceptance Letter/MoU by State
Exit Criteria
Finalise Trade License Program Vision
Finalise funding for the program
Define State-specific procurement process
Trade License Cell appointment (*). Consisting of:
Domain expert
Nodal officer (EO/ Commissioner/ Senior Official)
Program Head
System Integrator (SI) Team sign-up/onboarding
Duration
4-6 weeks
Entry Criteria
Program setup (Stage 0) is complete
SI Team signed-up
Key Activities
Project kick-off meeting and consultation from stakeholders
Identify & agree on high-level scope and exclusions
Identify pilot ULBs (using criteria such as business penetration, revenue generated from previous TL systems etc.)
Product Walkthroughs
Define Project Steering Committee structure and Project Governance process
Define phases of Rollout/ Deployment
Agreement on Deployment Priorities and high-level delivery timelines
Identify and study all TL process
Definition of TL as per the municipal governance of the State
State wise conceptualization of trade categories
Citizen services/channels around it
Integration with other Departmental processes (*)
Finalise Program Success Metrics for Rollout, Adoption and Governance adhering to the vision of the program
Internal Capacity Building, program logistics at State and ULBs, as per the current scenario
Collection of baseline data to measure end line target for the product (revenue generated, total properties in ULBs etc.)
Circulation of baseline data collection templates to the state/SI Team
Exit Criteria
Publish the program charter
Implementation plan agreement with priority features and broad timelines
Program Governance Model
Program Success Metrics
Capacity Building
TL Cell formation and appointment (#)
Data preparation/collection kick-off from Pilot ULBs
Cloud Infrastructure procured
Project Office Space allocated
Program Branding (name, logo, tagline etc.)
Duration
4-6 weeks
Entry Criteria
Program Charter
TL cell appointment
Key Activities
Standardisation of all TL processes
Initiate policy change if needed, based on the Processes defined
Define criteria for success
Conduct Product familiarisation workshop
Initiate collection of master data from pilot ULBs
Finalise data migration/collection/sync-up approach as per requirement
Finalise data validation approach
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc.
Dashboard design finalisation for Program Tracking
Exit Criteria
State Sign Off and Publishing of the TL processes, data template/workflows
Finalisation of Roll-out plan (in different phases)
Product Configuration Report Sign Off
Solution agreement for required State- specific product customisations
Program tracking mechanism finalization and sign off by the state
Initial reporting structure
Dashboard KPIs
Sign-off on data approach (Data collection/migration/correction/ sync-up/validation)
Detailed project plan
Duration
6-8 weeks
Entry Criteria
Product Configuration Report has been Signed Off by the state
Sign-off on data approach (Data collection/migration/correction/ sync-up/validation)
State Sign Off and Publishing of the TL processes, data template/workflows
Detailed Project Plan
Key Activities
Setting up development environments
Development/customisation of reports and dashboards
Development/Integration of portal
Third-Party Integrations (Payment gateway, Handheld/pos device)
Updation of user manuals and other key documents
Preparation & execution of Test Cases
Setup monitoring, support & maintenance processes, tools and dashboards
TL Legacy data collection from Pilot ULBs as per the data agreement signoff by the state
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc.
Identify ULB level nodal officers for day to day support
Migration and verification of Pilot ULB data as per the data agreement signoff by the state
Exit Criteria
Configured/Customized product that is ready for UAT
Set up of Monitoring, support & maintenance of Dashboards
finalization of Initial Reporting and Dashboard KPIs
Identification of participants for UAT session
Duration
2-3 weeks
Entry Criteria
Configured/Customized product ready for UAT
Pilot ULB Officials associated with TL are available for UAT & Training
Key Activities
UAT Environment Setup
Issues/bug identification and resolution
Regression UAT and Sign off from Pilot ULBs/ State
Setting up the Production environment
Setting up Support Centre & processes (Help Desk)
Training (Users, trainer)
master trainers identified from ground for simultaneous training
Training the Support Resources
Marketing & promotion activities
Go Live & launch event
Setup of review and monitoring cadence/team
Usage/review/Dashboard/Field Visits
Exit Criteria
UAT Sign-off & Go Live for Pilot ULBs
Setup of review and monitoring cadence
Duration
5-6 weeks
Entry Criteria
A pilot has been successful in the State
there are less than 3 open critical incidents (issues) with respect to product, implementation and data
Key Activities
ULB configurations phase wise as per the Project Plan
Verification and migration of ULB data phase wise as per the Data Agreement Sign Off provided by the State
Establishment of bug ticketing tool for resolving ground level issues by the state team
Training the Users at the district level
Pan State Roll Out - Phase wise
Stabilise product
Exit Criteria
State-wide Rollout in batches:
Adoption tracking & Review Cadence operational
Help Desk Effectiveness assured
Critical Bugs fixed
Program Success Metrics Tracking Kick-started
Duration
Ongoing process
Entry Criteria
Rollout Phase 1(First set of ULBs where rollout will happen after Pilot)
Key Ongoing Activities
Adoption Review Meetings as per the vision defined for the program.
Meetings are chaired by the Program Head
Need to be conducted weekly
TL Cell Focuses on Using data for:
tracking field issues and performance data to identify improvements
identify additional Integrations around TL to make processes more robust towards enhancing TL revenues (e.g. Upstream and downstream Processes)
Plans of ongoing Sustenance in Place with respect to:
Funding
IT support
Process Effectiveness and Improvements
Project Head
1
Domain Expert
2
District Nodal Officer
1 per district
MIS Expert
4
Task/Activity
eGov
State Leadership
Appoint of TL Cell
Consult
Execute
Finalise funding for the program
Consult
Execute
Define state -specific procurement process
Consult
Execute
System Integrator(SI) Team sign-up/onboarding
Consult
Execute
Finalise Trade License Program Vision
Consult
Execute
Task/Activity
eGov
TL Cell
SI Team
Identify & agree on scope and exclusions
Consult
Consult
Execute
Identify pilot ULBs
Execute
Consult
Project Kickoff - Implementation Methodology Presentation
Consult
Consult
Execute
Product Walkthroughs
Consult
Execute
Define Project Steering Committee structure and Project Governance process
Consult
Consult
Execute
Define phases of deployment/ rollout
Consult
Execute
Agreement on Deployment Priorities and high-level delivery timelines
Consult
Execute
Identify and study all TL process
Consult
Execute
Finalize Program Success Metrics for Adoption and Governance adhering to the vision of the program
Consult
Consult
Execute
Stage 1 - Program kick-off
Task/Activity
eGov
TL Cell
SI Team
Internal Capacity Building, program logistics at State and ULBs, as per the current scenario
Execute
Consult
Collection of baseline data to measure end line target for the product (Revenue generated, total properties in ULBs etc.)
Consult
Execute
Consult
Circulation of baseline data collection templates to the state/SI Team
Execute
Consult
Task/Activity
eGov
TL Cell
SI Team
Standardisation of all TL processes
Consult
Execute
Define criteria for success
Execute
Consult
Initiate policy change, if needed based on Processes defined
Consult
Execute
Consult
Conduct Product familiarisation workshop
Consult
Execute
Initiate collection of master data from pilot ULBs
Consult
Execute
Finalise data migration/collection/sync-up approach
Consult
Execute
Finalise data validation approach
Execute
Consult
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc.
Execute
Consult
Dashboard design finalisation for Program Tracking
Execute
Consult
Task/Activity
eGov
TL Cell
SI Team
Setting up development environments
Consult
Execute
Development/customisation of reports and dashboards
Consult
Execute
Development/Integration of portal
Consult
Execute
Third-Party Integrations (Payment gateway, Handheld/pos device)
Consult
Execute
Updation of user manuals and other key documents
Consult
Execute
Preparation & execution of Test Cases
Consult
Execute
Setup monitoring, support & maintenance processes, tools and dashboards
Consult
Execute
TL legacy data collection from Pilot ULBs (at least)
Consult
Execute
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc.
Execute
Consult
Verification and Migration of Pilot ULB data
Consult
Execute
Identification of participants for UAT session
Execute
Consult
Task/Activity
eGov
TL Cell
SI Team
UAT Environment Setup
Consult
Consult
Execute
Issues/bug identification and resolution
Consult
Execute
Regression UAT and sign off from Pilot ULBs/ State
Execute
Consult
Setting up the Production environment
Consult
Execute
Setting up Support Centre & processes (Help Desk)
Execute
Consult
Training user
Execute
Consult
Training Trainer
Consult
Execute
Stage 4 – UAT & Go Live
Task/Activity
eGov
TL Cell
SI Team
Training the Support Resources
Consult
Execute
Marketing & promotion activities
Execute
Consult
Go Live & launch event
Consult
Execute
Execute
Setup of review and monitoring cadence/team
Execute
Consult
Task/Activity
eGov
TL Cell
SI Team
ULB configurations phase wise as per the Project Plan
Consult
Execute
Verification and Migration of ULB data phase wise as per the Data Agreement Sign Off provided by the State
Execute
Consult
Establishment of bug ticketing tool for resolving ground level issues by the state team
Consult
Execute
Training the Users at the district level
Execute
Consult
Pan State Roll Out – Phase wise
Consult
Execute
Execute
Stabilise product
Consult
Execute
Task/Activity
eGov
TL Cell
SI Team
Adoption Review Meetings as per the vision defined for the program
Consult
Execute
Consult
TL Cell Focuses on Using data for:
tracking field issues and performance data to identify improvements
identify additional Integrations around TL to make processes more robust towards enhancing TL revenues (e.g Upstream and downstream Processes)
Execute
Consult
Plans of ongoing Sustenance in Place with respect to:
Funding
IT support (infra, helpdesk, ongoing enhancements)
Process Effectiveness and Improvements
Consult
Execute
Consult
Infrastructure
The actual Infra will be provided based on the questionnaire inputs received from the state
The state will take care of providing necessary project infrastructure and office facilities during the program for all on-site project Team members, which will be confirmed during the initiation phase. This includes workspace, office equipment (e.g., telephone with STD, fax machine, photocopy machine, etc.), stationery, PC/workstation, project LAN and internet access, etc.
The state will provide the necessary administrative support staff to carry out day-to-day project administration tasks, e.g., meeting rooms, Videoconferencing, etc.
The state should provide a Project Office and at least one conference room with speakerphone throughout the Project Duration.
Project Scope
Any new requirements received from State during the implementation phase will be handled through a change management process
State Team
The state will nominate a reasonably sized multifunctional Team from various departments of the State to be responsible for the implementation. The state Team would be required for information, validation, and execution through the implementation cycle and the Team members should be reasonably empowered to take decisions. Any delay in the decision-making process and the non-availability of the State Team may have an impact on the schedule.
The participants from State are expected to have a thorough understanding of the State’s internal processes.
The state will engage internal and external stakeholders required for this engagement and ensure their availability whenever needed.
Documentation
The Tech Implementation Partner will ensure provision of the following:
User education and training documentation delivery as per the default product documentation of the identified product versions.
Product manuals are expected to be shared with the State as part of the user manual.
All documentation in English and the language requirement of the state.
Training
Training to the end-users will be driven by the state Team.
The state will be responsible for providing the necessary infrastructure required for the Training, which includes the following readiness.
Training Rooms (Parallel Training Sessions) with Projector, White Board, Markers, Internet Connection, sufficient seating capacity, Desktop/Laptop for each participant and availability of Network for Trainees to connect to the server.
Implementation
The scope of the implementation will be limited to the services mentioned in Section 2.
eGoc Team will have an identified SPOC for handling the first level of communication with the client unless discussed and agreed.
eGov Team will not be involved in defining the test cases or executing the test cases.
Necessary signoff would be provided by the state upon completion of the defined milestones.
1
TRADE_SUBTYPE_CLINIC
Clinic
क्लिनिक
TRADE_TYPE_MEDICAL
2
TRADE_SUBTYPE_DHABA
Dhaba
ढाबा
TRADE_TYPE_HOTEL
1
Trade Sub Type Code
Alphanumeric
64
Yes
The Code assigned to the Trade Sub Type. Eg: TRADE_TYPE_Dhaba is assigned to Hotels
2
Trade Sub Type Name (In English)
Text
256
Yes
Name of the Trade Sub Type in English. Eg: Clinic
3
Trade Sub Type Name (In Local Language)
Text
256
Yes
Name of the Trade Sub Type in Local Language (as decided). Eg: Dhaba is described as “ढाबा” in Hindi
4
Trade Type Code
Reference
64
Yes
The Code assigned to the Trade Type. Eg: TRADE_TYPE_MEDICAL is assigned to Hospitals
1
Make sure that each and every point in this reference list has been taken care of
1
The format of the Trade Sub Type Code defined should be text and unique
TRADE_SUBTYPE_CLINIC
2
Trade Type Name (in either language) should not contain any special characters
Clinic: [Allowed]
#Clinic! : [Not allowed]
1
TRADE_TYPE_MEDICAL
Hospital
अस्पताल
TC1
2
TRADE_TYPE_HOTEL
Hotels
होटल
TC2
1
Trade Type Code
Alphanumeric
64
Yes
The Code assigned to the Trade Type. Eg: TRADE_TYPE_MEDICAL is assigned to Hospitals
3
Trade Type Name (In English)
Text
256
Yes
Name of the Trade Type in English. Eg: Goods, Services etc.
3
Trade Type Name (In Local Language)
Text
256
Yes
Name of the Trade Type in Local Language (as decided). Eg: Service is described as “सर्विस” in Hindi
4
Trade Category Code
Reference
64
Yes
The Code assigned to the Trade Category. Eg: TC1 For Goods, TC2 for Services
1
Make sure that each and every point in this reference list has been taken care of
1
The format of the Trade Type Code defined should be alphanumeric and unique
TRADE_TYPE_MEDICAL
TRADE_TYPE_HOTELS
2
Trade Type Name (in either language) should not contain any special characters
Hospital: [Allowed]
#Hospital! : [Not allowed]
Citizen
Apply for Trade License
Pay for license
Track status of the license application
Download payment receipts
Individuals and business entities
Counter Employee (CE)
Apply for a Trade License
Complete the Payment for Trade License
Keep a track of the status of the Trade License
Download/Print payment receipts, applications, TL certificate
Counter employees who assist citizens and file new trade license applications or renewal applications on their behalf
Document Verifier (DV)
Verify and forward
Send Back
Edit
Employees responsible for verifying the supporting documents submitted by citizens for new trade license or renewal of existing licenses
Field Inspector (FI)
Verify and forward
Send Back
Reject
Edit
Employees who go on to the field (i.e. location of trade) and physically verifies the information provided by the applicant is correct, checks safety precaution followed by the trade owner
Approver
Approve
Send Back
Reject
Cancel TL
The employee who has the final authority to approve or reject the application
1 | IMMOVABLE | Immovable | अचल |
2 | MOVABLE | Movable | चल |
1 | Code | Alphanumeric | 64 | Yes | Unique code to identify the records uniquely |
2 | Structure Type* (In English) | Text | 256 | Yes | Structure type in English |
3 | Structure Type* (In Local Language) | Text | 256 | Yes | Structure type in local language e.g. Hindi, Telugu etc. |
1 | Trade Sub Type Name (In either Language) should not contain any special characters | Small Bakery: [Allowed] #Small_Bakery! : [Not allowed] |
1 | Make sure that each and every point in this reference list has been taken care of |
1 | TRADE_SMALL_BAKERY | Small Bakery | New | PAN/VOTER ID | LAND LEASE |
2 | TRADE_SMALL_BAKERY | Small Bakery | Renewal | PAN/VOTER ID | ELEC BILL |
1 | Trade Sub Type Code | Reference | 64 | Yes |
2 | Trade Sub Type Name (English) | Text | 256 | Yes | Name of the Trade Sub Type in English Eg: Clinic |
3 | Application Type | Text | 256 | Yes | Type of application for which the documents related to trade are configured. It can either be new or renewal |
4 | Document 1 | Reference | 256 | Yes |
5 | Document 2 | Reference | 256 | Yes |
1 | Make sure that each and every point in this reference list has been taken care of |
1 | PUCCA | Pucca | पक्का | IMMOVABLE |
2 | KUTCHA | Kutcha | कच्चा | IMMOVABLE |
3 | HDV | Hand Driven Vehicle | हाथ चालित वाहन | MOVABLE |
4 | MDV | Motor-Driven Vehicle | मोटर चालित वाहन | MOVABLE |
1 | Code | Alphanumeric | 64 | Yes | Unique code to identify each and every record uniquely |
2 | Structure Sub Type* (In English) | Text | 256 | Yes | Structure sub type in English |
3 | Structure Sub Type* (In Local Language) | Text | 256 | Yes | Structure sub type in local language e.g. in Hindi, Telugu etc. |
4 | Structure Type Code* | Reference | 64 | Yes |
1 | Make sure that each and every point in this reference list has been taken care of. |
The Code assigned to the. Eg: TRADE_SMALL_BAKERY is assigned to Bakery
The primary document required as a verification parameter. Refer to the
The Secondary Document required as a verification parameter. Refer to the
Unique code of structure type to establish the mapping with