Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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.
This section contains DIGIT product and module related documents
DIGIT offers several modules. Each module is designed to automate the manual workflows for various governance units.
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.
Click on the individual product links to explore the functional details.
Click on the respective link below to learn more about that product, its features, applications and configuration details.
Faecal Sludge Management
__All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Learn more about TL workflows and its configuration
Details coming soon..
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
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.
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.
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.
Trade Type can be further sub-classified into Trade Sub Type depending on the trade ontology existing in the ULBs or States. Hence, Hotels can be further classified into Dhabas in North India or Udupis in South India.
Once the are defined, the next task is to -
Define Trade Sub Types
Map Trade Types to corresponding Trade Sub Types
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.
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 )
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.
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
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.
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.
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
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.
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.
Sr. No. | Checklist Parameter | Example |
---|
Sr. No. | Checklist Parameter | Example |
---|
All content on this page by is licensed under a .
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 )
to view module capabilities and product functional specifications.
Stage 0 - Program Setup/ On-Boarding |
---|
*Details of TL cell is mentioned in of this handbook
Stage 1 - Program kick-off |
---|
#Details of TL cell is mentioned in of this handbook
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 is licensed under a .
Sr. No. | Checklist Parameter | Example |
---|
All content on this page by is licensed under a .
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]
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 | 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] |
Duration | 4-6 weeks |
Entry Criteria | Acceptance Letter/MoU by State |
Exit Criteria |
|
Duration | 4-6 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Duration | 4-6 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Duration | 6-8 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Duration | 2-3 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Duration | 5-6 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria | State-wide Rollout in batches:
|
Duration | Ongoing process |
Entry Criteria |
|
Key Ongoing Activities |
|
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:
| Execute | Consult |
Plans of ongoing Sustenance in Place with respect to:
| Consult | Execute | Consult |
Infrastructure |
|
Project Scope |
|
State Team |
|
Documentation |
|
Training |
|
Implementation |
|
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_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 |
1 | Make sure that each and every point in this reference list has been taken care of |
1 | Make sure that each and every point in this reference list has been taken care of |
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
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
Online automated management of property tax revenues and collections
DIGIT-Property Tax (PT) is a self-serve web and mobile-based, easy-to-use and configurable product that addresses the objectives of municipal corporations and local government to automate all property tax operations, thus providing property tax assessment and payment services to citizens in real-time.
Manage property database
Property registration feature and title transfer
GIS embedded and integrated with eGov financials municipal accounting system
Various payment options available to citizens to make payments from their convenient places
Auto-generated defaulters’ list and real-time online tracking
This section contains all docs and information required to understand the PT module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the PT module.
PT Roadmap
PT Workflows
PT Service Configuration
Demo Script
Navigation Tips
Click on the embedded links within the content to browse topic details
Use the Contents links available on the right side of the screen to move to a specific heading
Find the list of Related Docs links at the bottom of each page to browse through additional product details
Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on PT module deployment.
#147/J, 1st floor, 10th Cross, 12th Main, 3rd Block, Koramangala, Bangalore 560034
+91 80 4125 5708
contact@digit.org
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
Refer to the TL User Manual for step-by-step instructions for each of these demo scenarios.
Functional overview for stakeholders
The Property Tax System(PT) provides a digital interface to make property assessments, pay property tax, generate payment receipts and monitor tax collection. It can be used by the citizens, Urban Local Body (ULB) counter and field employees and ULB Administrators to accomplish their specific tasks. It is available as a mobile and web-based application.
The PT product features can be broadly classified as the following modules:
Registration, Login and Creation of User Profile
Filling an Assessment for a Property
Searching for a Property
Modifications to a Property
Generate Demand Notice
Payments collection and Receipts
Dashboards and Reports
General Features
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 hierarchy of employees
Role-based access for performing different actions relating to property tax modules
With this feature, a citizen and employee can perform a self-assessment of a new property for a financial year. This feature helps in registering the property in the system. The details of the property can be entered online and can be assessed for the calculation of the taxes.
The PT Product is designed in a user friendly manner and reduces chances of error. System calculates the tax automatically and creates the demand. If a user wants to reassess his property due to any reason (for eg, incorrect data, change in property etc), it can be done by editing details of the last assessment.
An employee can edit the details of the last assessment, on behalf of the citizen-based on the owner’s input. Citizen can track down the status of his incomplete assessment. Any incomplete assessment can be searched and completed.
Citizen/CSC can Assess New Property (By Different Financial Years).
Citizen/CSC can Capture Address, Assessment Info, Owner Info.for all types of properties like residential houses, flats and commercial buildings.
o Sample Details captured:
Door Number,
Mutation number,
Number of floors,
Area covered,
Owner and co-owner,
Mailing & permanent address,
Built year
Individual room measurements
The system computes the property taxes automatically as per process and rules of the state.
The system has a facility to make entry in system by inspector after site visit and assessment of the same by the superintendent.
The system supports dynamic calculation for late fees, interest, rebates, etc. as on the day of demand generation.
The system fetches the data of previous year property data while e-filing for current year so that all the dues are calculated.
The system assigns a unique property ID based on the process defined in the ULBs.
Citizen/CSC : View/Print Summary of Filled Form
Assessment Form
Assessment Form is also sent by email to citizen
Upload Documents
Ownership/Title related
ID Proof
Any other statutory documents
Citizen or Employee can track down the status of his incomplete assessment. Any incomplete assessment can be searched and completed.
Citizen/CSC can search for Property by
Mobile No,
City,
Property Tax Unique ID
Citizen/ CSC can view Incomplete Assessments
Citizen/CSC can reassess Searched Property
View Property details and pending dues
The PT system provides the ability to capture mutation and transfer of ownership. It reduces interfaces between the user and the State and thus promote greater transparency. It also helps in reducing the time taken for mutation after registration. The system provides the ability for alteration of assessment after verification and inspection. Any structural changes like addition/extension/reduction of existing built up area or construction type OR utility changes like usage or occupancy have an impact on the increase/decrease in property tax demand. These changes can be handled by the ‘Additional/Alteration of Assessment’ feature.
The System provides the ability for bifurcation/ amalgamation of property. The property bifurcation/ amalgamation undergoes an approval process. The parent property needs to be modified accordingly, which can be done in the system.
Mutation of property and change of ownership details
Capture Extension/ Addition and Alteration and reassessment based on changed property details
Bifurcation of property
Amalgamation of property