What is DIGIT?
Digital Infrastructure for Governance, Impact & Transformation (DIGIT) is an open-source platform that helps governments deliver public services reliably. The platform enables effortless collaboration within or across government bodies, ensuring administrators and policymakers have access to the data needed for decision-making. Further, it provides frontline employees and government contractors with the information and tools needed on the ground to deliver services. The platform is continuously evolving with the needs and requirements of the governments to serve the changing needs and aspirations of their citizens. Being open source, the platform empowers market players to design and implement innovative solutions that resolve societal problems. The open digital ecosystem empowers our partners to build system capabilities and run programs that promote ease of living, enable the development of local solutions and accelerate the impact on the ground. The DIGIT platform is globally recognised for resolving e-governance challenges and is certified as a Digital Public Good (DPG) by the [Digital Public Goods Alliance (DPGA)](https://digitalpublicgoods.net/). Find the DIGIT platform in the [DPG registry](https://digitalpublicgoods.net/registry/) along with a host of other globally recognised DPGs.What is the background and story of DIGIT?
DIGIT - Builds state capacity for public sector delivery through DPIs (Digital Public Infrastructure). It improves the translation of policy intent into on-ground execution. We started our journey with a vision of good governance being supported and enhanced by a digital backbone. We had seen that local governments had poor capacity due to: 1. human resource deficits (both adequate numbers and skill levels of staff) 2. financial deficits (ability to mobilise own revenues as well as the ability to spend in a strategic manner 3. policy blockers (either lack of policies or often multiple contradictory policies in the same domain) We developed DIGIT to address these challenges: 1. shifting drudgework away from staff to digital systems (routine, repeatable, codified tasks are easier to automate/disintermediate) to drive improved efficiency in public service delivery 2. improving resource mobilisation by easing demand generation and collections of taxes, user charges, fees, licences etc 3. Surfacing relevant data to government administrators and functionaries to enable timely decision-making and action.Who are the primary users of DIGIT?
1. Citizens - to avail, apply, track, pay service fees, and raise complaints for services. 2. Governments - to interact with the citizens, provide services and collect feedback. 3. Field employees/officers - primary users responsible for the daily operations and service delivery. 4. Administrators/decision makers - use dashboards to view progress on how services are being adopted by citizens and take course corrective actions and policy changes accordingly.What are the benefits for governments or agencies using DIGIT?
Essentially, the benefits of this open-source platform can be viewed from short to long-term perspectives. The pointers below provide the phase-wise adoption impacts of the DIGIT platform as evidenced during DIGIT implementations. First phase: Coordination costs decrease as the execution focuses on improving existing processes. Second phase: Data-driven reforms and performance management enabled by more consistent, granular and timely data generated by the DPIs. Third phase: Interoperability of DPIs across departments and ministries improves targeting of policy interventions and speed of execution and improved financial and operational efficiency. Governments use DIGIT to enable DPIs for public service delivery and governance. The platform serves multiple domains including urban governance (collecting taxes and fees, providing certificates, services, and resolving grievances), improving sanitation management, strengthening public health systems, enabling better public finance management, and managing rural water supply operations to name a few. The implementations have improved state capacity through: 1. Consistent improvement in revenue collections across all geographies (this is often a leading indicator of state capacity). 2. Reduction in employee burden – across various geographical locations DIGIT delivers average time savings of 6 hours per week to frontline workers (findings from lean data survey). 3. Streamlined/re-engineered policies that reduce the paperwork and process burden on frontline workers and citizens. Find more about the DIGIT value proposition [here](https://docs.digit.org/platform/platform/digit-value-proposition).What is the DIGIT value proposition?
The DIGIT value proposition highlights the key capabilities and aspirations that form the foundational base of the technology platform. Accelerated reforms, trustworthiness, productivity, adoption, sustainability, ease of access, quick deployment, a strong network of system integrators, support and global recognition - These buzzwords reflect the robust design of the DPIs built on this platform, geared to resolve complex societal problems. DIGIT has carved its own niche space with its open-source platform that leverages the capabilities of microservice design to promote responsive and agile governance solutions. Find more about the DIGIT value proposition [here](https://docs.digit.org/platform/platform/digit-value-proposition).What are the DIGIT platform capabilities?
DIGIT is a technology platform that offers multiple building blocks or microservices that can be reused by products or applications. The platform focuses on inclusion and is designed on the principle of enhancing both platform openness and choice for citizens. The platform uses open APIs and standards, creating a powerful framework to drive convergence across multiple systems currently in use and to lower the barrier to entry for locally-developed solutions. Explore the DIGIT platform features in detail [here](/welcome-aboard/digit-platform).What are the current applications/modules hosted on DIGIT?
DIGIT offers multiple modules that facilitate citizen services ranging from submitting public grievances to applying for trade licences, water or sewerage connections, paying property taxes or submitting applications for building permits. The platform also offers public finance management and faecal sludge management applications designed to ease the governance of funds and improve sanitation. More about DIGIT modules [here](/welcome-aboard/products-and-solutions).What are the upcoming features in DIGIT?
Planned release features and future enhancements for the next 4 quarters are available in our roadmap [here](https://core.digit.org/roadmap).I want to see a demo of DIGIT. Where can I see it?
Access details for the demo of DIGIT applications and features are available below: * To browse as a citizen, [click here](https://staging.digit.org/digit-ui/citizen). * To browse as an employee, [click here](https://staging.digit.org/employee/language-selection). Additional details on DIGIT platform resources and product areas are available [here](/). You can also access the multiple videos on our [DIGIT Youtube](https://www.youtube.com/@digit_dpg) channel as well that provide a detailed walkthrough of the DIGIT modules and platform capabilities.What are the open source tools used to build, deploy and operate the DIGIT platform?
The list of open-source tools used is listed [here](https://docs.digit.org/platform/platform/architecture/technology-architecture).What are the common DIGIT platform services that I can reuse?
List and details of common platform services such as notifications, file store, telemetry, payment gateway are listed [here](https://docs.digit.org/platform/platform/core-services).Where can I find details about DIGIT architecture?
DIGIT is a microservices-based platform that is built to scale. All details about the architecture can be found [here](https://docs.digit.org/platform/platform/architecture).What are the setup requirements? What technical skills do I need to set up or use DIGIT?
Setup requirements and technical skills required on the team can be found [here](/welcome-aboard/digit-platform).Where can I find the API specs for DIGIT core services?
The API specs for all core services are listed [here](https://specs.digit.org/common-service-specs). You can also explore the various application specs [here](https://specs.digit.org/).Does DIGIT offer analytics dashboards for visualisation of data?
Yes, the DIGIT National Dashboard Ingest service provides a one-stop framework for ingesting data from defined sources based on configuration. More about dashboards [here](https://docs.digit.org/local-governance/local-governance-product-suite/local-governance-stack/dashboards-and-analytics).Is it interoperable with other DPGs? Can it interoperate with other systems?
1. DIGIT uses micro-service architecture and is interoperable with other DPGs exposing integration APIs 2. Relevant integration adaptors/connectors would need to be developed for this integration 3. For example -What does “Building Blocks Approach” mean?
Digital building blocks are conceptually similar to physical building blocks with a few key differences * Easier and (almost) free to replicate * Exchange info to complete a task * Can be simultaneously used * Evolved differently in multiple solutions Building blocks are the key design choice to enable solutions to evolve. The following diagram conceptually illustrates how building blocks make evolution possible.# The concept of Tenant in DIGIT #### What is a tenant? In the context of software architecture, a "tenant" typically refers to an individual or organization that uses a shared software application or service. Each tenant operates within its isolated portion of the application's resources, such as data, configuration, and user interface. #### What is a multitenant system? Multitenancy refers to a software architecture where a single instance of the software serves multiple tenants or clients. Each tenant typically has its own isolated and customizable environment, but they all share the same underlying infrastructure and codebase. In a multitenant system, tenants are often distinguished by factors such as data, configuration, user interface, and access rights. This architecture is commonly used in cloud-based applications, where it allows software providers to efficiently serve multiple customers while minimizing infrastructure costs and maintenance efforts. For example, in a multitenant web application, each tenant might have its own database or database schema or data partition, ensuring data isolation and security. However, all tenants share the same application codebase and runtime environment, reducing overhead and simplifying updates and maintenance. #### Goals and Objectives * Implement multi-tenancy to support multiple tenants within a single instance of the platform and product. * Enable creation, updating, and searching of tenants/accounts * Ensure data isolation and security by enforcing tenant-level authorization. * Provide configuration options for administrators to customize system behaviour. #### Key Stakeholders * Development Team * Project Stakeholders * End Users # Introducing Local Governance The digital local governance solution ## About Local Governance The DIGIT-powered local governance solution catalyses digital transformation across towns and cities - changing how citizens interact with government bodies. As a digital public good, the DIGIT Local Governance stack fosters an open digital ecosystem, enabling co-creation and deployment of locally relevant solutions that enhance business operations and improve overall quality of life. By transforming local governance, this initiative not only elevates citizen well-being but also accelerates the nation's economic growth. ## Useful Links
| Local governance | Overview of challenges and approach used to resolve with DIGIT Local Governance module | /spaces/OorNqx5By246mkjipsn7/pages/z01m5po8mjFNGrJzS8wI | |
| Product Specifications | Explore the local governance product suite functional specifications & user module details | /spaces/OorNqx5By246mkjipsn7/pages/01KmDPmaqxM8w7IRnGmv | |
| Technology | Find the tech building blocks details for local governance | /spaces/OorNqx5By246mkjipsn7/pages/MIzdVxXMTkdHhMuHpTVz | |
| Setup | Plan, gather requirements, install and configure modules | /spaces/OorNqx5By246mkjipsn7/pages/eaxC3Q8cYyniHJPeraPd |
| Feature | Description |
|---|---|
| Citizen Consent Form | This feature is to get a consent from the citizen during the citizen login |
| Citizen Feedback Rating | This feature is focused to get a citizen rating when a service is completed. |
| NDSS KPIs | This includes
|
| Central Instance | This feature includes changes related to central instance for modules - Property Tax, Trade License, PGR, OBPS, Water and Sewerage, Firenoc, Birth and Death, mCollect, Reports, Inbox |
| Updated Feature | Description | Category | Change Link |
|---|---|---|---|
| PT bugs | While creating a new property the Institution name allowing special characters,institution-type options updated,in PDF, showing the proper name of the usage type. | Frontend | |
| TL | Create New Application from CE end and TL Renewal billing slab issues. | Frontend | |
| Finance | Total bill amount not showing proper | Frontend | |
| Common | Fetch bill api issue, Localisations issue in release kit. | Frontend | |
| mCollect | UI alignment issue, Payer's Name is not visible while scanning the QR code, The footer is overlapping the drop down. | Backend | Config change |
| UI Technical Documents | Backend Service Documents |
|---|---|
New Docs Citizen consent form | New Docs KPIs: Pendancy, Citizen Feedback and Pt-SLA changes Citizen feedback Service |
reportName:
AssetImmovableRegister
state1\_AssetImmovableRegister
state2\_AssetImmovableRegister
# Init Containers Configs
initContainers:
dbMigration:
enabled: true
schemaTable: "property_services_schema"
image:
repository: "property-services-db"
env: |
{{- if index .Values "property-ismultischema-enabled" }}
- name: SCHEMA_NAME
value: {{ index .Values "property-schemas" | quote }}
{{- end }}
- name: "DB_URL"
valueFrom:
configMapKeyRef:
name: egov-config
key: db-url
- name: "SCHEMA_TABLE"
value: {{ .Values.initContainers.dbMigration.schemaTable | quote }}
- name: "FLYWAY_USER"
valueFrom:
secretKeyRef:
name: db
key: flyway-username
- name: "FLYWAY_PASSWORD"
valueFrom:
secretKeyRef:
name: db
key: flyway-password
- name: "FLYWAY_LOCATIONS"
valueFrom:
configMapKeyRef:
name: egov-config
key: flyway-location
persister config
| | mCollect Pdf - QR Code Bug Fix | | [2646](https://github.com/egovernments/configs/pull/2646) | | | Internal Gateway Config | | [
| Feature | Service Name | Changes | Description |
|---|---|---|---|
| DIGIT 2.9 release changes. | |||
| DSS | 1332, 1333, 1334, 1335, 1336, 1432, 1458, 1466, 1487, 1487 |
| S.No. | Checklist | Yes/No/Partially | Reference Link | Owner | Reviewer | Remarks |
|---|---|---|---|---|---|---|
| 1 | Development is completed for all the features that are part of the release. | Yes | @Kaviyarasan P | @Kaviyarasan P | Code is frozen by APR-2023 | |
| 2 | Test cases are documented by the QA team, and reviewed by the product owners and test results are updated in the test cases sheet. | Yes | @Gurjeet Singh
| @Priyanka Samantaroy | No new test cases for central instance are there. All existing test cases should work as is. | |
| 3 | The incremental demo of the features showcased during the sprint showcase and feedback incorporated. If possible list out the JIRA tickets for feedback. | Yes |  Demo (Citizen Feedback, Consent and DSS KPIs).mp4Demo (Citizen Feedback, Consent and DSS KPIs)_1.mp4Jira tickets for feedback | @Kaviyarasan P | Demo given on 18-APR-2023 for Citizen Feedback Citizen Consent Form DSS New KPIs. Central Instance - No demo required. | |
| 4 | UI/UX Audit review by UX Architect is completed along with feedback incorporation for any changes in UI/UX. | Yes | 2.9-DesignReview.mp4 | @Andrew Jones @Vamshikrishna Kole | UI/UX audit is done and review comments are incorporated. | |
| 5 | Incremental demos to the product owners are completed as part of the sprint and feedbacks are incorporated. | Yes | Demo (Citizen Feedback, Consent and DSS KPIs).mp4Demo (Citizen Feedback, Consent and DSS KPIs)_1.mp4 | @Megha S @P. Sankar | @P. Sankar | Demo given on 18-APR-2023 for Citizen Feedback Citizen Consent Form DSS New KPIs. Central Instance - No demo required. |
| 6 | QA signoff is completed by the QA team and communicated to the product owners. All the tickets QA signoff status is updated in the JIRA. | Yes | Test Cases for Release Digit 2.9 | @Gurjeet Singh
| QA signoff was completed. Sign-off dates 14th April 2023 Citizen Feedback Citizen Consent Form DSS New KPIs Central Instance - 15th September 2023 | |
| 7 | UI, API Technical documents are updated for the release along with the configuration documents. | Yes | UI documentation for central instance | @Kaviyarasan P @Vamshikrishna Kole | ||
| 8 | UAT promotion and regression testing from the QA team is completed. QA team has shared the UAT regression test cases with the product owners. | Yes | @Gurjeet Singh
|
| No new test cases for central instance are there. All existing test cases should work as is. | |
| 9 | API Automation scripts are updated for new APIs or changes to any existing APIs for the release. API automation regression is completed on UAT, the automation test results are analyzed and necessary actions are taken to fix the failure cases. Publish the list of failure use cases with a reason for failure and the resolution taken to fix these failures for the release. | No | @Gurjeet Singh |
Not picked up in this release due to lack of resources. We do not have QA resource who can write automation scripts. | ||
| 10 | The API backward compatibility testing is completed. | Yes | Backward Compatibilty Report | @Gurjeet Singh | @Kaviyarasan P | Tested on 25-AUG-2023 |
| 11 | The communication is shared with the product owners for the completion of UAT promotion and regression by the QA team. The product owners have to give a Product signoff within one week of this communication. | Yes | @Gurjeet Singh @KeerthiBhaskara-eGov
| @Megha S | UAT signoff was completed.
Central Instance- No communication required
| |
| 12 | UAT Product Signoff communication is received from the Product owners along with the release notes and User guides (if applicable). | Yes | @Megha S | @P. Sankar | UAT product signoff for Citizen Feedback given on 19th April 2023 Central Instance - UAT product signoff not needed. Central Instance is a separate environment | |
| 13 | The GIT tags and releases are created for the code changes for the release. | Yes | Service Build Updates | @Priyanka Samantaroy | @Kaviyarasan P | |
| 14 | Verify whether the Release notes are updated | Yes | @Priyanka Samantaroy | @Kaviyarasan P | ||
| 15 | Verify whether all UAT Builds are updated along with the GIT tag details. | Yes | Service Build Updates | @Priyanka Samantaroy | @Kaviyarasan P | |
| 16 | Verify whether all MDMS, Configs, InfraOps configs updated. | Yes | MDMS, Configurations | @Priyanka Samantaroy | @Kaviyarasan P | |
| 17 | Verify whether all docs will be Published to http://urban.digit.org by the Technical Writer as part of the release. | Yes | @Kaviyarasan P, @Pradeep Kumar, @Ajay Rawat, @Megha S | @Anjoo Narayan | ||
| 18 | Verify whether all test cases are up to date and updated along with necessary permissions to view the test cases sheet. The test cases sheet is verified by the Test Lead. | Yes | @Gurjeet Singh
| No new test cases for central instance are there. All existing test cases should work as is. | ||
| 19 | Verify whether the UAT credentials sheet is updated with the details of new Users and Roles if any | Yes | @Gurjeet Singh | No new credentials required for - New credential for Central Instance Attached
| ||
| 20 | Verify whether all the localization data was added in UAT including Hindi and updated in Release Kits. | Yes | @Priyanka Samantaroy | @Kaviyarasan P | No new localization added for the central instance | |
| 21 | Verify whether the product release notes and user guides are updated and published | Yes | Product Owners | |||
| 22 | The Demo of released features is done by the product team as part of the Sprint/Release showcase. | Yes | Demo (Citizen Feedback, Consent and DSS KPIs).mp4Demo (Citizen Feedback, Consent and DSS KPIs)_1.mp4 | Demo given on 18-APR-2023 for Citizen Feedback Citizen Consent Form DSS New KPIs. Central Instance - No demo required. | ||
| 23 | Technical and Product workshops/demos are conducted by the Engineering and Product team to the implementation team (Implementation handover) | Yes | DIGIT SAAS Guideline - Central Instance | @Kaviyarasan P | @Kaviyarasan P | Technical and Product workshops/demo conducted on 23-July-2023 |
| 24 | Architect SignOff and Technical Quality Report | Yes | @Kaviyarasan P | @Ghanshyam Rawat | Signed off by @Kaviyarasan P on 31-July-2023 | |
| 25 | Success Metrics and Product Roadmap | Yes | Program Roll Out Plan | @Ajay Rawat | ||
| 26 | Adoption Metrics | Yes | Program Roll Out Plan | @Ajay Rawat
| ||
| 27 | Program Roll-out Plan | Yes | Program Roll Out Plan | @Ajay Rawat | @Pradeep Kumar | |
| 28 | Implementation checklist | Yes | Implementation Checklist | @Pradeep Kumar/@Vinoth | Prepared. | |
| 29 | Implementation Roll-out plan | Yes | Roll-out Plan | @Pradeep Kumar/@Vinoth | ||
| 30 | Gate 2 | Yes | DIGIT Urban Gate 2 | @Ajay Rawat | ||
| 31 | The Internal release communication along with all the release artefacts are shared by the Engineering/Product team. | Yes | Release Notes DIGIT 2.9 | @Priyanka Samantaroy | @Kaviyarasan P | |
| 32 | Plan for upgrading the staging/demo instance with the release product - within 2-4 weeks based on the period where no demos are planned from staging for the previous version of the released product. | Yes | Staging Upgrade | @Pradeep Kumar/@Vinoth | ||
| 33 | The Release communication to partners is shared by the GTM team and the Webinar is arranged by the GTM team after the release communication - within 2-4 weeks of the release. | No |
|
# Implementation Checklist
| @Sl No | Checklist | Yes/No/Partially | Reference link | Owner | Date(mm/dd/yyyy) | Remarks |
| 1 | Product Release Notes | Yes | Release Notes | Kavi | ||
| 2 | List of services that needs to be upgraded | Yes | Service Build Updates | Kavi/Priyanka | Verified. | |
| 3 | Verify Configs, MDMS, devOps Changes | Yes | Mdms & Config updates 2.9 | Pradeep/Vinoth | Verified | |
| 4 | Verify test cases for all enhancements/updates | Yes | Test cases for 2.9 | Gurjeet | ||
| 5 | Verify performance testing report | Gurjeet | No report found | |||
| 6 | Verify backward compatibility testing report | Yes | Backward Compatibility Testing report | Gurjeet | ||
| 7 | Verify the documents for released features | Yes | Clarifications | Pradeep/Vinoth | ||
| 8 | Backward compatibility testing by disabling central instance flag on existing environment | Yes | Backward compatibility testing by disabling central instance flag | Vinoth/Gurjeet | Verified the backward compatibility in UAT environment by disabling the flag and deploying latest builds. | |
| 9 | Setup fresh central instance from scratch for two states and verify | Yes | Setup fresh central instance and verify | Vinoth | Verified documents and updated missing gaps in the document. | |
| 10 | Impel-Singoff | Yes | Signoff | Vinoth/Gurjeet | 15/09/2023 | Verified |
| 11 | Technical discussion on central instance with Partners | Yes | discussion and demo | Vinoth/Pradeep | 31/07/2023 | Technical Discussion with NIUA and PWC team done on 31st July '23. |
| 12 | Demo on Release features to partners | Yes | Vinoth/Pradeep | 18/05/2023 | Demo Provided 18th May 2023 to Impel partners. | |
| 13 | Staging upgradation plan | Yes | Staging Upgrade | Vinoth | ||
| 14 | Deployment strategy for DIGIT 2.9 | Yes | Deployment strategy for DIGIT 2.9 | NIUA Team /Ajay | ||
| 15 | Address queries raised by partner on central instance | No | Queries raised by NIUA to be addressed post Gate 2 as additional effort is required. | NIUA Team /Ajay |
# Program Roll Out Plan DIGIT Urban 2.9 release has a new following features: * DIGIT Urban 2.9 Beta Features * DIGIT as a Service * Bug Fixes | Task | Status | Owner | | ------------------------------------------------------------------------ | ----------- | ------------- | | Upgrade of UPYOG with Beta features | 15/05/2023 | Pradeep Kumar | | Session with NUDM team on Central Instance | 31/07/2023 | Ajay Rawat | | Getting approval from partners for UPYOG upgrade with DIGIT as a Service | In Progress | Ajay Rawat | | Effort Estimate for Upgrade created | Done | Vinoth | | Gate 2 | In Progress | Ajay Rawat | | Release Communication Shared with Partners | To Do | Ajay Rawat | ### NUDM Roll Out The NUDM Team has shared the following requirements for upgrading UPYOG with the Central Instance: **\*Conditions for Upgrading UPYOG with Central Instance** * Role & Access Management at Cluster Level so that each State SI can do its scope of work * Role & Access Management at Logs Level so that each State SI can do its scope of work * Role & Access Management at Elastic Search & Kibana Level so that each State SI can do its scope of work * Enhancement & verification of Product default Kafka with more nodes, partitions, etc so that it sustains and performs for National Level traffic * Enhancement & verification of Product default ElasticSearch with more nodes, shards, etc so that it sustains and performs for National Level traffic * Availability of all States data in its DB schemas and the same should apply with ElasticSearch * Other enhancements so that the State Infra & DevOps team can manage their resources independently. ## **Adoption Metrics** | Feature | Metric | Estimate | | ------------------ | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | Citizen Feedback | No. of states adopting feature and sharing data with National Dashboard | At least 2 states to implement the feature under NUDM in next 6 months | | Consent form | Compliance to NUIS Assessment | Compliance report already shared post release of feature | | Dashboard KPIs | No. of states sharing data on new KPIs | Citizen Feedback feature to be implemented in states, for KPIs to start reflecting data. 2+ states to implement the feature and share data on the KPIs | | DIGIT as a Service | No. of accounts/projects using feature in all missions | At least 2 accounts use DIGIT as a Service in next 6 months | ## Success Metrics | Feature | Objective | Estimate | | ------------------ | ---------------------------------------------- | ------------------------------------------------------------------------- | | Citizen Feedback | Improvement in Citizen Satisfaction | Improvement in Metrics by 20% in first 3 years in state using the feature | | Consent form | Compliance to NUIS Assessment | Compliance report already shared post release of feature | | Dashboard KPIs | Improvement in Citizen Satisfaction | Improvement in Metrics by 20% in first 3 years in state using the KPIs | | DIGIT as a Service | Optimizing resources for saving in infra costs | Saving to be estimated | # Product Release Notes # Property Tax System Release Notes ## Overview This release provides PRDs of 3 property tax features and a few bug fixes. ## Release Highlights PRDs of 3 property tax features and bug fixes. 1. [Properties amalgamation](/local-governance/access/local-governance-stack/property-tax/property-tax-system-product-requirements-document/property-amalgamation) 2. [Property bifurcation](/local-governance/access/local-governance-stack/property-tax/property-tax-system-product-requirements-document/property-bifurcation) 3. [Capital value system](/local-governance/access/local-governance-stack/property-tax/property-tax-system-product-requirements-document/capital-value-system) 4. Property mutation bug fixes ## Release Features None ## Known Issues Bug [UM-5322: PT: Mutation flow: In Acknowledgement Form only one Transferor Details are present.SIGNED OFF](https://digit-discuss.atlassian.net/browse/UM-5322) ## Upcoming Release Features None ## Reference Doc Links | | | | - | - | | | | | | |
# Residential Construction Permit System UI/UX Revamp Release Notes OBPS Release notes for Urban DIGIT 2.8 release. ## Overview This release offers the UI/UX revamp of the Residential Construction Permit System, workflow timeline changes and reports. ## Release Highlights The functionality in OBPS remains the same - only the UI/UX has changed. Two reports were added for administrative purposes. Changes made to the workflow timeline for clear representation of application status to the users. Notification based on channels. ## Release Features * Stakeholder registration and employee approval flow * Architect flow (permit application creation) and employee approval flow * Architect occupancy certificate creation and employee approval flow * Fire NOC employee approval flow * Open link for stakeholder registration flow * Daily collection report
OBPS daily collection report
OBPS application status report
Workflow timeline changes
TL Daily Collection report
TL Application status report
Trade license registry
Trade license renewal pending report
| Key Features | Description |
|---|---|
| CITIZEN | |
| Apply for new connection | UI/UX revamp and change in application form to remove the information which is to be filled by employee. |
| Search and Pay | UI/UX revamps and added by Door no. and Owner’s Name. |
| My Payments | UI/UX revamp of payment history to My Payments. |
| My Bills | Added My Bills to list all the bills due for payment. |
| My Connections | UI/UX revamp of Search Connection and Card view of Connection Details. |
| View Connection Details | UI/UX revamps of complete view connection details. |
| View Consumption Details | UI/UX revamps of complete view of consumption details. |
| My Applications | UI/UX revamps of Search Application to My Applications and Card view of application details. |
| View Application Details | UI/UX revamps of complete view application details. |
| Pay Application Fee | UI/UX revamps of complete flow of payment of application fee. |
| Apply for disconnection | A new feature added to allow the consumer of the service to apply for is disconnection. |
| Data Privacy Audit Report | This report is added to see the details who all have unmasked to see the logged in user’s PII data. |
| EMPLOYEE | |
| Employee Inbox | UI/ UX revamp of inbox and separating out the water and sewerage inboxes. |
| Apply for new connection | UI/ UX revamp of and change in application form to remove the information which is to be filled by Field Inspector. |
| Search Applications | UI/ UX revamp of Search Application. |
| View Application Details | UI/ UX revamp of Search Application details. |
| Application Workflow | UI/ UX revamp of all the states of application flow and the option to edit the application by the FI only to add the additional details |
| Collect Application Fee | UI/ UX revamp of Collect Application Fee. |
| Search Connection | UI/ UX revamp of Search Connection. |
| Collect Water/ Sewerage Bills | UI/ UX revamp of Collect the Water/ Sewerage Bills. |
| View Connection Details | UI/ UX revamp of view connection details |
| View Consumption Details | UI/ UX revamp of view consumption details |
| Add Meter Reading | UI/ UX revamp of add meter reading. |
| Modify Connection | UI/ UX revamp of modify connection. |
| Bill Amendment | UI/ UX revamp of bill amendment. |
| Apply for disconnection | New feature to apply for disconnection has been added. |
| Data Privacy | Data privacy aspect is added to mask the PII data of a consumer and capturing the information up on unmasking of PII to generate the report.
|
| Reports |
|
| Key Features | Description |
|---|---|
| Inbox | UI/UX revamp of employee inbox and service wise separate inboxes. |
| View Application | UI/ UX revamp of the application details view. |
# Bill Genie UI/UX Revamp Release Notes ## Overview UI/ UX revamp of Bill Genie. ## Release Highlights UI/UX revamp of Bill Genie features. ## Release Features | Features | Description | | ----------------- | -------------------------------------------------------------------------------------------------------- | | Search Bill | UI/UX revamps of searching a bill and then downloading the bill PDF. Bill amounts can also be collected. | | Cancel Bill | UI/UX revamp of cancelling an active bill. | | Group Bill | UI/ UX revamp of the grouping and merging of the multiple bills into single PDF. | | Group W\&S Bills | UI/ UX revamp of grouping and merging of related water and sewerage bill into single PDF. | | Download Bill PDF | UI/ UX revamp of download PDF. | ## Known Issues None ## Upcoming Release Features None ## Reference Doc Links | **Doc Links** | | ------------- | | | | | # Birth & Death Reports Release Notes Birth and death release note for Urban DIGIT 2.8. ## Overview Reports have been added to birth and death for administrative purposes. ## Release Highlights Birth count report Death count report Birth and death certificate payment records ## Release Features Birth count report
Birth count report
Death count report
Birth and death certificate payment records
About page
FAQ
| 01 - Accelerated Reforms |
The Local Governance transforms the way governments deliver public services. By establishing a digital public infrastructure (DPI), multiple states have built capacity, removed administrative burdens, and improved governance, enabling faster, better, and cheaper delivery of public services. Governments face multiple challenges in transformation initiatives, including capacity issues, emergent needs and behaviours, and variance in context and requirements at different scales. DIGIT was designed from the ground up to address such challenges and has evolved over multiple years of implementation to solve for accelerated reforms. | |
| 02 - Trustworthy Data For Effective Decision Making | Timely and trustworthy data for effective decision-making at different administrative levels and to fix accountability. DIGIT Local Governance comes ready with data dashboards to enable decision-making at all levels of government, right from administrators to frontline workers. DIGIT makes possible:
This ensures that products built on DIGIT enhance visibility, increase trust and reduce the cost of coordination across multiple departments and programs. | |
| 03 - Improved Productivity & Faster Adoption | Reduce overheads for technology teams and learning curve for the final product users. Single login for multiple applications and a standardised user interface make adoption quicker and easier. Role-based access takes away the overheads of multiple environments for different systems and multiple user accounts for each system. For employees, it removes having to do tedious, repetitive tasks by automating processes, improving productivity, and allowing them to focus on more meaningful aspects of their jobs. | |
| 04 - Sustainable Impact At Scale & Speed | Scalability is at the core of the DIGIT platform. It has been deployed as a digital public infrastructure serving large-scale sub-national and national populations. What makes it possible? A technologically robust platform with open and freely available specifications and standardised APIs that have proven its performance at massive deployments at the population scale. DIGIT's source code is open source, data is stored in shared registries and data stores are owned by the government, mitigating the risks associated with vendor lock-ins, and allowing digital transformation initiatives to move ahead with speed at scale. | |
| 05 - Enhanced Citizen Access To Public Services | Local Governance solutions built on DIGIT can be accessed by multiple channels. So that, services can be delivered to citizens via mobile, web, WhatsApp, chatbots, through intermediaries or over the counter in physical offices. All are seamlessly connected. It comes ready with a well-defined design system with a standardised user interface that has been created considering the realities of population-scale digital products. The user interface is straightforward and minimal. It follows a guided approach for citizens using these digital products. | |
| 06 - Quick Development, Easy Deployment | All products on DIGIT are designed to be configured, customised, and extended to suit the needs of the local context. These changes can be made at different levels of government. A federated architecture supports the different realities of each unit of governance. A set of reusable building blocks can be leveraged by market players to build products and services rapidly. Well-defined specifications, documentation, guides, and training materials make deployment quick and easy for teams. Thus, making it possible to build products for different programs and services, urgent needs and take them to the ground as fast as possible. | |
| 07 - Strong Network Of Trusted System Integrators | The DIGIT team works actively with partners and has created a robust ecosystem of application developers and system integrators who are trained and certified in DIGIT. Open training sessions on design, development, deployment and implementation are held regularly. In addition to that, DIGIT provides certifications to trained personnel. | |
| 08 - Continued Platform Support | For governments using DIGIT as their technology platform, the DIGIT team offers:
DIGIT promises long-term support of the platform for all its core components and also underwrites the performance of the core platform. | |
| 9 - Designed For Global Challenges, Recognised Globally | DIGIT has the capabilities needed to rapidly develop digital applications to address global development challenges. From its origin in solving for urban governance, the platform has rapidly evolved to address challenges in areas of sanitation, public health welfare, public finance, rural governance and legal case management among others. DIGIT is certified as a Digital Public Good (DPG) by the Digital Public Goods Alliance (DPGA). The DIGIT team sits on the technical advisory committee of the Govstack that works to identify and support the advancement of digital public goods with relevance to the whole of the government transformation approach. |
| Citizen Users | 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 email or SMS for new application status updates and pending renewals Download Trade Licence, Payment & Acknowledgement Receipts online | ||
| Employee Users | Create flexible role-based workflows Configure license fee calculation logic View custom dashboards for module statistics Filter search results using advanced configurable search parameters |
| Reform Number | 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 |
| List of Functionalities | Corresponding Features |
|---|---|
| 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 Licence | 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 Licence | |
| Citizen/CSC: Download/Print Application Summary | |
| Citizen/CSC: Download/PRINT Trade Reference No | |
| Citizen/CSC: View the applied licences | |
| Citizen: Pays for the licence post-verification | |
| CSC: Collects fee post verification | |
| Issue of trade licence | Document Verifier : Verify & Forward/ Reject the application |
| Licencing Inspector: Verify and Forward/ Send back/ Reject the Application. | |
| Licencing Officer: Approve/ Send back the Application | |
| Licencing Officer: Reject/ Cancel the Application | |
| Modification to a Trade Licence | Edit/ Update the Application based on the Inspection report against the application. |
| Renewal of a Trade Licence | Renew trade licence |
| Payment and Fee | Configurable Workflow Rights : Edit & Payment Collection |
| Payments & Collection : Various Payment Modes | |
| Dashboards and reports | Cancelled Receipt Register Report |
| Trade licence collection | |
| Trade licence application status- showing the number of licences approved/rejected | |
| Trade licence ULB-wise status | |
| State Dashboard: View Reports for Total Licences, Licences 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 |
TRADE\_TYPE\_MEDICAL
TRADE\_TYPE\_HOTELS
| | 2 | Trade Type Name (in either language) should not contain any special characters |Hospital: \[Allowed]
#Hospital! : \[Not allowed]
| ## Attachments {% file src="/files/CaTpf0a9dhBsnSpJpTH3" %} {% file src="/files/aw1J71fiHVmqAPZUGlYK" %} # Trade Sub Type ## Introduction Trade Type can be further sub-classified into Trade Sub Type depending on the trade ontology existing in the ULBs or States. Hence, Hotels can be further classified into Dhabas in North India or Udupis in South India. Once the[ Trade Type(s)](/local-governance/access/local-governance-stack/trade-license-tl/tl-master-data-templates/trade-type) are defined, the next task is to - * Define Trade Sub Types * Map Trade Types to corresponding Trade Sub Types ## Data Table | Sr. No. | Trade Sub Type Code\* | Trade Sub Type Name\* (In English) | Trade Sub Type Name\* (In Local Language) | Trade Type Code\* | | ------- | ---------------------- | ---------------------------------- | ----------------------------------------- | -------------------- | | 1 | TRADE\_SUBTYPE\_CLINIC | Clinic | क्लिनिक | TRADE\_TYPE\_MEDICAL | | 2 | TRADE\_SUBTYPE\_DHABA | Dhaba | ढाबा | TRADE\_TYPE\_HOTEL | The table above contains sample data. ## Procedure ### Data Definition | Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description | | ------- | --------------------------------------- | ------------ | --------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 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.](/local-governance/access/local-governance-stack/trade-license-tl/tl-master-data-templates/trade-type) Eg: TRADE\_TYPE\_MEDICAL is assigned to Hospitals | ### Steps to fill data 1. Download the data template attached to this page. 2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions. 3. Select the relevant Trade Type Code from the Trade Type master data. This will map the listed Trade Sub Type to the selected Trade Type. 4. Enter a unique value for Trade Sub Type Code. 5. Enter the English name for Trade Sub Type Name (English). 6. Enter the local name for the Trade Sub Type Name (Local Language). ## Checklist The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below. ### Common Checklist This checklist covers all the activities which are common across the entities. | Sr. No. | Checklist Parameter | Example | | ------- | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | 1 | Make sure that each and every point in this reference list has been taken care of | [Checklist](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist) | ### Entity Specific Checklist This checklist covers the activities which are specific to the entity. | Sr. No. | Checklist Parameter | Example | | ------- | ------------------------------------------------------------------------------ | --------------------------------------------------------- | | 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]
| ## Attachments {% file src="/files/CaTpf0a9dhBsnSpJpTH3" %} {% file src="/files/oalJ5l2SD9qnqRyYX2zx" %} # Trade Category ## Introduction The Trade Category List can be defined as the primary or the 1st level classification “head” for trade(s) defined at a ULB/State Level. ## Data Table | Sr.No. | Trade Category Code\* | Trade Category Name\* (In English) | Trade Category Name\* (In Local Language) | | ------ | --------------------- | ---------------------------------- | ----------------------------------------- | | 1 | TC1 | Goods | सामग्री | | 2 | TC2 | Services | सर्विस | The table above contains sample Trade Category data. ## Procedure ### Data Definition | Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description | | ------- | --------------------------------------- | ---------- | --------- | ------------- | -------------------------------------------------------------------------------------------------------- | | 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 | ### Steps to fill data 1. Download the data template attached to this page. 2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions. 3. Enter a unique Trade Category Code for each trade head. 4. Enter the Trade Category Name. Some trade categories are already defined in the master. Add new categories as required. 5. Enter the Trade Category Name (Local Language). ## Checklist The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below. ### Common Checklist This checklist covers all the activities which are common across the entities. | Sr. No. | Checklist Parameter | Example | | ------- | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | 1 | Make sure that each and every point in this reference list has been taken care of | [Checklist](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist) | ### Entity Specific Checklist This checklist covers the activities which are specific to the entity. | Sr. No. | Checklist Parameter | Example | | ------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------- | | 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]
| ## Attachments {% file src="/files/CaTpf0a9dhBsnSpJpTH3" %} {% file src="/files/aw1J71fiHVmqAPZUGlYK" %} # Trade License Fee ## Introduction Once the Trade Ontology is defined, the next step is to allocate the license fee associated with the Trades. Dependent on the Trade Classification Level ([Types](/local-governance/access/local-governance-stack/trade-license-tl/tl-master-data-templates/trade-type)/ [Subtypes](/local-governance/access/local-governance-stack/trade-license-tl/tl-master-data-templates/trade-sub-type)), the fee allocated might be the same across the Sate or could vary from ULB to ULB. There could be a distinct fee(s) for two different types of applications (new and renewal). Following are the key tasks to be executed : * Allocate the License Fee according to Trade Classification Level (Types/Subtypes). * Map the License fee with the respective Trade Classification Level. ## Data Table | Sr. No | Trade Sub Type Code\* | Trade Sub Type Name (In English) | New License Fee\* | Renewal License Fee\* | UOM | UOM From | UOM To | | ------ | --------------------- | -------------------------------- | ----------------- | --------------------- | ------- | -------- | ------ | | 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 | The table above contains sample data. ## Procedure | Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description | | ------- | -------------------------------- | --------- | --------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | Trade Sub Type Code | Reference | 64 | Yes | The Code assigned to the [Trade Sub Type](/local-governance/access/local-governance-stack/trade-license-tl/tl-master-data-templates/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 | ### How to fill data 1. Download the data template attached to this page. 2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document. 3. Identify the “[Trade Sub Types](/local-governance/access/local-governance-stack/trade-license-tl/tl-master-data-templates/trade-sub-type)” that exists at a ULB/ State level. 4. Collect the above information and feed it below the “Trade Sub Type Name” column accordingly. The Description of Trade Sub Type Name must be provided as per the language specified in the respective column. 5. Add the “Trade Sub Type Code” respectively against the identified trade type(s). 6. Fill in the New License Fee & New Renewal Fee accordingly. The New License Fee & Renewal Fee can be the same as well as distinct, depending on the by-laws/ mandate followed by the State/ULB. 7. Fill in the fields related to Units of Measurement (UOM Unit, From/To) for the available trades only. ## Checklist The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below. ### Common Checklist This checklist covers all the activities which are common across the entities. | Sr. No. | Checklist Parameter | Example | | ------- | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | 1 | Make sure that each and every point in this reference list has been taken care of | [Checklist](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist) | ### Entity Specific Checklist This checklist covers the activities which are specific to the entity. | Sr. No. | Checklist Parameter | Example | | ------- | ------------------------------------------------------------------------------ | ---------------------------------------------------------------------- | | 1 | Trade Type Name (In either Language) should not contain any special characters |Small Bakery: \[Allowed]
#Small\_Bakery! : \[Not allowed]
| ## Attachments {% file src="/files/CaTpf0a9dhBsnSpJpTH3" %} {% file src="/files/oalJ5l2SD9qnqRyYX2zx" %} # Structure Type ## Introduction The structure type is the first level of classification of the premises where the trade has to be established and conducted. This is mostly used as management information in the trade detail. ## Data Table | Sr. No. | Code\* | Structure Type\* (In English) | Structure Type\* (In Local Language) | | ------- | --------- | ----------------------------- | ------------------------------------ | | 1 | IMMOVABLE | Immovable | अचल | | 2 | MOVABLE | Movable | चल | The table above contains sample data. ## Procedure ### Data Definition | Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description | | ------- | ------------------------------------ | ------------ | --------- | ------------- | -------------------------------------------------------- | | 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. | ### Steps to fill data 1. Download the data template attached to this page. 2. Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions. 3. Contact the person who shared this template with you to discuss and clear your doubts. 4. Enter the relevant structure types. 5. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered. ## Checklist The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. These activities have been divided into 2 groups as given below. ### Common Checklist This checklist covers all the activities which are common across the entities. | Sr. No. | Checklist Parameter | Example | | ------- | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | 1 | Make sure that each and every point in this reference list has been taken care of | [Checklist](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist) | ### Entity Specific Checklist A separate entity-specific checklist is not needed for this entity data template. ## Attachments {% file src="/files/FN4USmLehe3Fa3eMM906" %} {% file src="/files/P0Idf6xla227ULFJzJja" %} # Structure Sub Type ## Introduction Structure sub type is the second level of classification of the premises where the trade has to be established and conducted. This is mostly used as management information in the trade detail. ## Data Table | Sr. No. | Code\* | Structure Sub Type\* (In English) | Structure Sub Type\* (In Local Language) | Structure Type Code\* | | ------- | ------ | --------------------------------- | ---------------------------------------- | --------------------- | | 1 | PUCCA | Pucca | पक्का | IMMOVABLE | | 2 | KUTCHA | Kutcha | कच्चा | IMMOVABLE | | 3 | HDV | Hand Driven Vehicle | हाथ चालित वाहन | MOVABLE | | 4 | MDV | Motor-Driven Vehicle | मोटर चालित वाहन | MOVABLE | The table above contains sample data. ## Procedure ### Data Definition | Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description | | ------- | ---------------------------------------- | ------------ | --------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 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 | Unique code of structure type to establish the mapping with [Structure Type](/local-governance/access/local-governance-stack/trade-license-tl/tl-master-data-templates/structure-type) | ### Steps to fill data 1. Download the data template attached to this page. 2. Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions. 3. Contact the person who shared this template with you to discuss and clear your doubts. 4. Enter the relevant structure sub types with its proper mapping with structure type. 5. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered. ## Checklist The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. These activities have been divided into 2 groups as given below. ### Common Checklist This checklist covers all the activities which are common across the entities. | Sr. No. | Checklist Parameter | Example | | ------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | 1 | Make sure that each and every point in this reference list has been taken care of. | [Checklist](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist) | ### Entity Specific Checklist A separate entity-specific checklist is not needed for this entity data template. ## Attachments {% file src="/files/vaI6C2Fteu8lc03vQSvz" %} {% file src="/files/P0Idf6xla227ULFJzJja" %} # Trade License Document Attachment ## Introduction Along with the [rates](/local-governance/access/local-governance-stack/trade-license-tl/tl-master-data-templates/trade-license-fee), the Trade License application process does require certain documents as an attachment of proof. The proof can be defined by a set of documents ranging from * Identification Proof (Drivers License/ Voter Card/ Adhaar/ Pan etc.) * Trade Premises Proof (Lease Agreement, Electricity Bills, etc). * Misc Documents (Affidavit, Self- Declaration, etc). The Number and the Documents required could vary across the State, ULB(s), and might be dependent on Trade Subtypes, all of which are totally configurable on DIGIT. ## Data Table | Sr. No. | \*Trade Subtype Code | \*Trade Subtype Name (In English) | \*Application Type | \*Document 1 | \*Document 2 | | ------- | -------------------- | --------------------------------- | ------------------ | ------------ | ------------ | | 1 | TRADE\_SMALL\_BAKERY | Small Bakery | New | PAN/VOTER ID | LAND LEASE | | 2 | TRADE\_SMALL\_BAKERY | Small Bakery | Renewal | PAN/VOTER ID | ELEC BILL | The table above contains sample data. ## Procedure | Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description | | ------- | ----------------------------- | --------- | --------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | Trade Sub Type Code | Reference | 64 | Yes | The Code assigned to the[ Trade Sub Type](/local-governance/access/local-governance-stack/trade-license-tl/tl-master-data-templates/trade-sub-type). Eg: TRADE\_SMALL\_BAKERY is assigned to Bakery | | 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 | The primary document required as a verification parameter. Refer to the [Standard Document List](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/standard-document-list) | | 5 | Document 2 | Reference | 256 | Yes | The Secondary Document required as a verification parameter. Refer to the [Standard Document List](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/standard-document-list) | ### How to fill data 1. Download the data template attached to this page. 2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document. 3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts. 4. Identify the “[Trade Sub Types](/local-governance/access/local-governance-stack/trade-license-tl/tl-master-data-templates/trade-sub-type)” that exists at a ULB/ State level. 5. Collect the above information and feed it below the “Trade Sub Type Name” column accordingly. The Description of Trade Sub Type Name must be provided as per the language specified in the respective column. 6. Add the “Trade Sub Type Code” respectively against the identified trade type(s). 7. Fill in the \*Document 1 & \*Document 2 columns respectively. ## Checklist The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below. ### Common Checklist This checklist covers all the activities which are common across the entities. | Sr. No. | Checklist Parameter | Example | | ------- | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | 1 | Make sure that each and every point in this reference list has been taken care of | [Checklist](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist) | ### Entity Specific Checklist This checklist covers the activities which are specific to the entity. | Sr. No. | Checklist Parameter | Example | | ------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | | 1 | Trade Sub Type Name (In either Language) should not contain any special characters |Small Bakery: \[Allowed]
#Small\_Bakery! : \[Not allowed]
| ## Attachments {% file src="/files/CaTpf0a9dhBsnSpJpTH3" %} {% file src="/files/oalJ5l2SD9qnqRyYX2zx" %} # Local Business License Service Configuration ## Overview This service is used to issue a license to the user after verification. The service is designed in such a way that it can be used to serve different type of licenses. Currently used to issue trade licenses, perform stakeholder registration and issue lockdown pass. The service is integrated with workflow where we can define the steps for approval of the application. Once the application is approved the license is generated. ## Pre-requisites Before you proceed with the documentation, make sure the following pre-requisites are met - * Java 8 * Kafka server is up and running * egov-persister service is running and has tl-services persister config path added in it * PSQL server is running and database is created ## Key Functionalities * Used for license generations in trade licenses, stakeholder registration and issue lockdown pass * Define roles to applicants on successful application to access Building Plan Approval services at the time of stakeholder registration * Generate application number and license number * Support workflows * Provide notification on various status changes for an application ## Interaction Diagram  ## Deployment Details 1. Add MDMS configs required for Trade License and BPA stakeholder registration and restart MDMS service 2. Deploy the latest version of tl-services service 3. Add tl-service persister yaml path in persister configuration and restart persister service 4. Add Role-Action mapping for API’s 5. Create businessService (workflow configuration) according to trade license and stakeholder registration 6. Add tl-service indexer yaml path in indexer service configuration and restart indexer service ## Configuration Details Following application properties in the Trade License service are configurable. | Property | Value | Remarks | | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | | egov.idgen.tl.applicationNum.format | PB-TL-\[cy:yyyy-MM-dd]-\[SEQ\_EG\_TL\_APL] | The format of the TL application number | | egov.idgen.tl.licensenumber.format | PB-TL-\[cy:yyyy-MM-dd]-\[SEQ\_EG\_PT\_LN] | The format of the TL license number | | egov.idgen.bpa.applicationNum.format | PB-SK-\[cy:yyyy-MM-dd]-\[SEQ\_EG\_TL\_APL] | The format of the Stake holder application number | | egov.idgen.bpa.licensenumber.format | PB-SK-\[cy:yyyy-MM-dd]-\[SEQ\_EG\_PT\_LN] | The format of the Stake holder license number | | egov.tl.max.limit | 100 | Max number of records to be returned | | citizen.allowed.search.params | tenantId, applicationNumber, limit, offset, licenseNumbers | The search parameters on which citizen can search | | employee.allowed.search.params | tenantId, applicationNumber, applicationType, status, mobileNumber, fromDate, toDate, licenseNumbers, oldLicenseNumber, limit, offset | The search parameters on which employee can search | | persister.save.tradelicense.topic | save-tl-tradelicense | The name of kafka topic on which create request is published | | persister.update.tradelicense.topic | update-tl-tradelicense | The name of kafka topic on which update request is published | | persister.update.tradelicense.workflow\.topic | update-tl-workflow | The name of kafka topic on which update request is published | ## Integration ### Integration Scope The trade-license service is currently used to issue trade licenses, perform stakeholder registration and issue lockdown pass. ### Integration Benefits * Provide backend support for the different license registration process. * Mseva and SMS notifications on application status changes. * The elastic search index for creating visualizations and Dashboards. * Bpa Stakeholder registration provides new roles to the user to access the Building Plan Approval system. * Supports workflow which is configurable ### Steps to Integration 1. To integrate, host of tl-services service should be overwritten in the helm chart. 2. {servicename}/\_create/ \_create should be added as the create endpoint for creating any license in the system 3. {servicename}/\_search/ \_search should be added as the search endpoint. This method handles all requests to search existing records depending on different search criteria 4. {servicename}/\_update/ \_update should be added as the update endpoint. This method is used to update fields in existing records or to update the status of the application based on workflow. ## Reference Docs ### Doc Links {% file src="/files/-MWUKL0lgMPk45Rm6g-e" %} {% file src="/files/-MWUKL0oRoXDLnlAkaCi" %} {% content-ref url="/pages/rN4SIdKA5N4lFD6D8yXN" %} [BPA Stakeholder Registration](/local-governance/access/local-governance-stack/online-building-plan-approval-system-obpas/obpas-service-configuration/bpa-stakeholder-registration) {% endcontent-ref %} | Title | Link | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | Local Setup | [LOCALSETUP.md](https://github.com/egovernments/core-services/blob/4a74fd3be04ab0a2fe0641f10b57b7e9b9f82aff/egov-user/LOCALSETUP.md) | | API Swagger Documentation (Trade License) | [Swagger Documentation TL](https://raw.githubusercontent.com/egovernments/egov-services/master/docs/common/contracts/v1-0-0.yml) | ### API List In all below endpoints if the service name is BPAREG it is treated as a stakeholder registration application and if it is TL or if it is absent then the application is treated as trade license application. Stakeholder registration APIs:-The \_update API is used to update the application information or to forward the application from one state to another.
In the case of the stakeholder registration if the application reaches the last stage the role depending on the license type is given to the user.
| | {servicename}/{jobname}/\_batch, /\_batch | Searches trade licenses that are expiring and send a reminder SMS to owner's of the licenses | # Local Business License Issuing Service - Steps To Upload Data ## 1. Add Tenant/Urban Local Body Data To onboard a new Urban Local Body (ULB) or tenant for the **Local Business License Issuing Service** modules, follow the steps given below: {% stepper %} {% step %} ### Add data in MDMS Refer to the table below to find the location for specific data types and its description.| Reference from Sample Data Load | Data | Location | Description |
|---|---|---|---|
| Tenants | Tenant Details | tenant/tenants.json | To show the tenant at login screen |
| tenant/citymodule.json | To enable ulb to create application,add tenant in TL module | ||
| TL Trade Type | Trade Type (Business Units) information | TradeLicense/TradeType.json | To add Business Units |
| Property Type | Create Property | ULBNAME/PropertyTax/PropertyType.json | To create new property.From citizen end,in create property screen,provide property Type |
| Owership Type | Property Ownership Details | ULBNAME/common-masters/OwnerShipCategory.json | To provide type of ownership in create property screen |
| Owner Type | Property Owner Type | ULBNAME/PropertyTax/OwnerType.json | To provide owner type in create property screen |
| Role | URL |
|---|---|
| Employee | https://ips-demo.digit.org/digit-ui/employee/user/login |
| Citizen | https://ips-demo.digit.org/digit-ui/citizen/select-language |
| Role | Username | Password | ULB | ULB |
|---|---|---|---|---|
Common Role for Employees Property Tax Counter Employee
TL Counter Employee
| CSR | Demo@123 | Alameda | 6000000001 |
Common Role for Employees Property Tax Counter Employee
Business License field inspector
BPA Field Inspector BPA NOC Verifier FireNoc Approver Airport Authority Approver | FieldEmployee | Demo@123 | Alameda | 6000000002 |
Common Role for Employees Property Tax Counter Employee TL Approver Counter Employee BPA Services Approver BPAREG doc verifier BPAREG Approver | OfficeEmployee | Demo@123 | Alameda | 6000000003 |
Common Role for Employees State Administrator | Administrator | Demo@123 | Alameda | 6000000004 |
| displayName | Roles |
|---|---|
| /tl-services/v1/_create | EMPLOYEE,CITIZEN,TL_APPROVER,TL_CEMP |
| /tl-services/v1/_update | EMPLOYEE,CITIZEN,TL_DOC_VERIFIER,TL_FIELD_INSPECTOR,TL_APPROVER,TL_CEMP |
| /tl-services/v1/_search | EMPLOYEE,CITIZEN,TL_APPROVER,TL_CEMP,TL_DOC_VERIFIER,TL_FIELD_INSPECTOR |
| /collection-services/payments/_create | TL_CEMP,SUPERUSER,EMPLOYEE |
| /inbox/v1/_search | TL_CEMP,TL_DOC_VERIFIER,TL_FIELD_INSPECTOR,TL_APPROVER,AIRPORT_AUTHORITY_APPROVER |
| displayName | Roles |
|---|---|
| /tl-calculator/billingslab/_search | SUPERUSER,EMPLOYEE,TL_APPROVER,TL_CEMP,CITIZEN,TL_DOC_VERIFIER,TL_FIELD_INSPECTOR |
| /tl-calculator/billingslab/_create | SUPERUSER |
| /tl-calculator/billingslab/_update | SUPERUSER |
| tl-calculator/v1/_getbill | EMPLOYEE,TL_APPROVER,TL_CEMP,CITIZEN |
| /tl-calculator/v1/_calculate | SUPERUSER |
| displayName | Roles |
|---|---|
| /property-services/property/_search | CITIZEN,PT_CEMP,PT_DOC_VERIFIER,PT_FIELD_INSPECTOR,PT_APPROVER,TL_CEMP |
| /property-services/property/_create | CITIZEN,PT_CEMP,TL_CEMP |
| /property-services/property/_update | CITIZEN,PT_CEMP,PT_DOC_VERIFIER,PT_FIELD_INSPECTOR,PT_APPROVER,TL_CEMP |
| /pt-calculator-v2/propertytax/v2/_estimate | PT_CEMP,CITIZEN,TL_CEMP |
| /property-services/assessment/_create | SUPERUSER,PT_CEMP,CITIZEN,TL_CEMP,CITIZEN |
| /property-services/assessment/_search | TL_CEMP,SUPERUSER,PT_CEMP,CITIZEN |
| Ticket reference | Issue | RCA |
|---|---|---|
| ISNE-378 | TL: Create new application issue when user selects TL owner details from PT | In the code level, it is hardcoded that if ownershipcategory code includes (“SINGLEOWNER”or ”MULTIPLEOWNERS” or “INSTITUTIONAL”) then only it will form the owner object. https://github.com/egovernments/egov-mdms-data/commit/51a50852dd4a312aaea8c1b824864fd7bc7f0c47 https://github.com/egovernments/egov-mdms-data/commit/dc8930811e28f0042b7694bf466870929cd5b483 |
| ISNE-366 | TL: Accessory category options not displayed in UI | Accessory category needs to be added to TL billing slab Property type and Ownership category are required to be having a dot separated value in mdms |
| ISNE-392 | TL: Pop up message to be displayed when user clicks on payment button | Localization updated |
| ISNE-393 | TL: Financial Year hard coded for TL renewal Need to make it dynamic based on current TL validity period | Financial year was hard coded in the code,so fetched current financial year and from mdms data - validfrom and validto and Removed the hardcoded part of financial year. https://github.com/egovernments/DIGIT-Dev/commit/0971443040d2c192816165a93629f8df93489335 |
| ISNE-389 | TL employee randomly gets navigated to citizen login screen | Removed working of isCreateEnabledEmployee variable because it was redirecting to another url without any reason. https://github.com/egovernments/DIGIT-Dev/commit/85bf283f163d0b19e8b981662fe5a8af09ab22b7 |
digit-ui-internals/index.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pages/citizen/EditTrade/index.js)
User can delete and add as many accessory or units as it needs but there should be at least one unit to complete the application, to add a new unit or accessory “Add” button is used which is located at the end of the page. A new array is formed with all the updated details or with the old unit/accessory, when the flow is completed, this new array is then compared with the old array of accessories and units, and a new resulting array object is formed for the request body, you can find the respective code in the following method : `gettradeupdateaccessories` & `gettradeupdateunits`. this can be found in the below link[ digit-ui-internals/index.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/utils/index.js)
Similarly, for owners the method which is used to form the new request param array is `gettradeownerarray`
It is similar to Accessories and Units - the only difference is in UI. Users can’t select multiple owners and only add one owner, it needs to either add more than one owner or select a single owner in the ownership category and proceed. After the successful update, the application's next action will be “Pending for document verification” as there is an update in the data.
On completing the flow, the same object structure which was being used earlier in the flow gets changed into the request body structure for the update API: `/tl-services/v1/_update`, for this, the method which gets used is declared inside the Utils folder. Method name: `convertToResubmitTrade` and it can be found in the below link:
{% embed url=" **Address Details Flow -** In the next flow, users have to enter the trade address details. This flow is straightforward, without any conditional routing. 
digit-ui-internals/packages/modules/tl/src/pages/citizen/Applications at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/tree/main/packages/modules/tl/src/pages/citizen/Applications)
The template for My Application List is present under digit-ui-internals/TLCard.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/components/TLCard.js) and[ digit-ui-internals/DesktopInbox.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/components/inbox/DesktopInbox.js)
Clicking on New Application navigates to the New Trade License Application screen.
Route:[ mSeva](https://qa.digit.org/digit-ui/employee/tl/new-application)
File Path:[ digit-ui-internals/index.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pages/employee/NewApplication/index.js)
## **Technical Implementation Details**
Initial MDMS call is being made on page load like old UI.
## **MDMS Data**
Structure Type and Sub Structure Type field data is fetched from[ egov-mdms-data/StructureType.json at master · egovernments/egov-mdms-data](https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/common-masters/StructureType.json)
Trade Category, Trade Type, Trade Sub Type field data is fetched from[ egov-mdms-data/TradeType.json at master · egovernments/egov-mdms-data](https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/TradeLicense/TradeType.json)
Mohalla Data -[ egov-mdms-data/boundary-data.json at master · egovernments/egov-mdms-data](https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/amritsar/egov-location/boundary-data.json) (For Amritsar)
Accessories -[ egov-mdms-data/AccessoriesCategory.json at master · egovernments/egov-mdms-data](https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/TradeLicense/AccessoriesCategory.json)
Type of Ownership and Type of Sub ownership -[ egov-mdms-data/OwnerShipCategory.json at master · egovernments/egov-mdms-data](https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/common-masters/OwnerShipCategory.json)[ egov-mdms-data/OwnerType.json at master · egovernments/egov-mdms-data](https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/common-masters/OwnerType.json)
documents:[ egov-mdms-data/documentObj.json at master · egovernments/egov-mdms-data](https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/TradeLicense/documentObj.json)
**Data fetch, load and render**
* Clicking on Submit button, `tl-services/v1/_create` api is called and create the application, after getting success response, we are calling update API `tl-services/v1/_update`.
* On loading the page, `/tl-calculator/billingslab/_search` api is called for showing the licence type (File Path:[ digit-ui-internals/TLTradeDetailsEmployee.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pageComponents/TLTradeDetailsEmployee.js) ) and accessories options (File Path:[ digit-ui-internals/TLAccessoriesEmployee.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pageComponents/TLAccessoriesEmployee.js) ).
**Acknowledgement Screen**
After the success of creating and updating calls will route to the acknowledgement screen.
File Path:[ digit-ui-internals/getTLAcknowledgementData.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/utils/getTLAcknowledgementData.js)
## **Role Action Mapping**
| S.No. | API | Roles | Action ID |
|---|---|---|---|
| 1 | /egov-mdms-service/v1/_search | TL_CEMP | 954 |
| 2 | /tl-services/v1/_create | TL_CEMP | 1685 |
| 3 | /tl-services/v1/_update | TL_CEMP | 1686 |
| 4 | /tl-calculator/billingslab/_search | TL_CEMP | 1684 |
digit-ui-internals/ApplicationDetails.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pages/employee/ApplicationDetails.js)
## **Trade Details**
### Timeline View
digit-ui-internals/ApplicationDetailsContent.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/templates/ApplicationDetails/components/ApplicationDetailsContent.js)
The workflow is the same as Old UI only, please refer to the documentation link below.
{% content-ref url="/pages/-MgiGQwa-aT3Ug\_BqSBj" %}
[TL Apply Flow UI Details](/local-governance/access/local-governance-stack/trade-license-tl/tl-service-configuration/business-license-ui-configuration/tl-apply-flow-ui-details)
{% endcontent-ref %}
## **Role Action Mapping**
| S.No. | API | Roles | Action ID |
| ----- | ------------------------------------------- | --------------------------------------------------------------------- | --------- |
| 1 | `egov-mdms-service/v1/_search` | `CR_PT` | `954` |
| 2 | `/tl-services/v1/_update` | `TL_APPROVER, TL_CEMP, EMPLOYEE, TL_DOC_VERIFIER, TL_FIELD_INSPECTOR` | `2029` |
| 3 | `/egov-workflow-v2/egov-wf/process/_search` | `EMPLOYEE` | `1730` |
| 4 | `/tl-services/v1/_search` | `EMPLOYEE`, `TL_APPROVER`, `TL_CEMP` | `1687` |
| 5 | `/egov-hrms/employees/_search` | `TL_APPROVER, TL_CEMP, EMPLOYEE, TL_DOC_VERIFIER, TL_FIELD_INSPECTOR` | `1752` |
# Renew Edit Application
All the fields in this flow are the same as the New TL Application. The difference here is that max fields are having pre-populated data (On Loading the page, search is made for that particular application).
Will get the Renew Trade License option, when the application is in an approved state and the same financial year application is not present in the workflow.
File path:[ digit-ui-internals/ApplicationDetails.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pages/employee/ApplicationDetails.js)
When we click on the Renew Trade License application, it will route to Renew screen
File Path:[ digit-ui-internals/ApplicationDetails.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pages/employee/ApplicationDetails.js)
File Path:[ digit-ui-internals/index.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pages/employee/ReNewApplication/index.js)
**Direct Renewal:** There is no change in any fields and directly clicks on submitting an application, an update API call is made for the respective application with respective to Direct Renewal (`applicationType`: `RENEWAL`, `workflowCode`: `DIRECTRENEWAL,` )and it will go into direct renewal flow.
**Edit Renewal:** If there is any change in any fields and clicks on submitting an application, an update API call is made with respect to edit renewal (`applicationType`: `RENEWAL`,`workflowCode`: `EDITRENEWAL` )and update the application and it will go into the edit renewal flow.
**Units, Accessories, Owners and documents details in case of Edit/Renewal flow**
1. Employee can edit units in both cases, employee can add and delete multiple units, please find the file below reg all use cases:[ digit-ui-internals/TLTradeUnitsEmployee.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pageComponents/TLTradeUnitsEmployee.js)
2. Employee cannot edit accessories in both cases, the employee can not add and delete multiple units and all fields are in disable state, please find the file below reg all use cases:[ digit-ui-internals/TLAccessoriesEmployee.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pageComponents/TLAccessoriesEmployee.js)
3. Employee can edit in both cases, expect ownership details, ownership details field is in disable state in both cases. please find the file below reg all use cases:[ digit-ui-internals/TLTradeUnitsEmployee.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pageComponents/TLTradeUnitsEmployee.js)
4. Employee can edit the documents in both cases, please find the file below reg all use cases:[ digit-ui-internals/TLDocumentsEmployee.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pageComponents/TLDocumentsEmployee.js)
**Acknowledgement Screen**
After a successful update call, the user is routed to the acknowledgement screen.
File Path:[ digit-ui-internals/getTLAcknowledgementData.js at main · egovernments/digit-ui-internals](https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/utils/getTLAcknowledgementData.js)
**EDIT Flow:** It is also the same as renewal flow only, but we are passing the action `action`: `RESUBMIT` on the update call with all the changes.
**Application/ Trade Details:** [Application Details/Trade Details](/local-governance/access/local-governance-stack/trade-license-tl/tl-service-configuration/business-license-ui-configuration/application-details-trade-details-ui-flows)
**TL Create New Application:**[ New Trade License Application](/local-governance/access/local-governance-stack/trade-license-tl/tl-service-configuration/business-license-ui-configuration/new-trade-license-ui-flow)
## **Role Action Mapping**
| S.No. | API | Roles | Action ID |
|---|---|---|---|
| 1 | /egov-mdms-service/v1/_search | TL_CEMP | 954 |
| 2 | /tl-services/v1/_create | TL_CEMP | 1685 |
| 3 | /tl-services/v1/_update | TL_CEMP | 1686 |
| 4 | /tl-calculator/billingslab/_search | TL_CEMP | 1684 |
| Stage 0 - Program Setup/ On-Boarding | |
|---|---|
| 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 |
|
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 (infra, helpdesk, ongoing enhancements)
- Process Effectiveness and Improvements
| Areas | Assumptions |
|---|---|
| Infrastructure |
|
| Project Scope |
|
| State Team |
|
| Documentation |
|
| Training |
|
| Implementation |
|
- Dynamic tax calculation based on configurable billing slabs
- Support for multiple property types and usage categories
- Penalty, rebate, and interest calculations
- Advance payment and partial payment handling
- Integration with finance systems for voucher creation
- Demand generation and update mechanisms
- SMS integration for notifications
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(128) | PRIMARY KEY, NOT NULL | Unique identifier for the property |
| propertyid | VARCHAR(256) | UNIQUE (with tenantid, status) | Human-readable property ID |
| tenantid | VARCHAR(256) | NOT NULL | Tenant/ULB identifier for multi-tenancy |
| surveyid | VARCHAR(256) | Survey number of the property | |
| accountid | VARCHAR(128) | NOT NULL | Account identifier for the property |
| oldpropertyid | VARCHAR(128) | Previous/legacy property ID for migration | |
| status | VARCHAR(128) | NOT NULL | Property status (ACTIVE, INACTIVE, etc.) |
| acknowldgementnumber | VARCHAR(128) | Acknowledgement number for property registration | |
| propertytype | VARCHAR(256) | NOT NULL | Type of property (BUILT_UP, VACANT, etc.) |
| ownershipcategory | VARCHAR(256) | NOT NULL | Ownership category (INDIVIDUAL, INSTITUTIONAL, etc.) |
| usagecategory | VARCHAR(256) | Usage category (RESIDENTIAL, COMMERCIAL, etc.) | |
| creationreason | VARCHAR(256) | Reason for property creation (NEW, SUBDIVISION, etc.) | |
| nooffloors | BIGINT | Number of floors in the property | |
| landarea | NUMERIC(10,2) | Total land area in square units | |
| superbuiltuparea | NUMERIC(10,2) | Total super built-up area | |
| linkedproperties | VARCHAR(2048) | Comma-separated list of linked property IDs | |
| source | VARCHAR(128) | NOT NULL | Source system (MUNICIPAL_RECORDS, etc.) |
| channel | VARCHAR(128) | NOT NULL | Channel of creation (WEB, MOBILE, COUNTER, etc.) |
| createdby | VARCHAR(128) | User who created the record | |
| lastModifiedBy | VARCHAR(128) | User who last modified the record | |
| createdTime | BIGINT | NOT NULL | Creation timestamp (epoch milliseconds) |
| lastModifiedTime | BIGINT | Last modification timestamp | |
| additionaldetails | JSONB | Additional flexible attributes in JSON format |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| ownerinfouuid | VARCHAR(256) | PRIMARY KEY, NOT NULL | Unique identifier for owner record |
| tenantid | VARCHAR(256) | NOT NULL | Tenant/ULB identifier |
| propertyid | VARCHAR(256) | FOREIGN KEY, NOT NULL | Reference to eg_pt_property.id |
| userid | VARCHAR(128) | UNIQUE (with propertyid), NOT NULL | User ID from user service |
| status | VARCHAR(128) | NOT NULL | Owner status (ACTIVE, INACTIVE) |
| isprimaryowner | BOOLEAN | Flag indicating primary owner | |
| ownertype | VARCHAR(256) | Type of owner (INDIVIDUAL, COMPANY, etc.) | |
| ownershippercentage | VARCHAR(128) | Percentage of ownership | |
| institutionid | VARCHAR(128) | Reference to institution if applicable | |
| relationship | VARCHAR(128) | Relationship with primary owner | |
| createdby | VARCHAR(128) | User who created the record | |
| createdtime | BIGINT | NOT NULL | Creation timestamp |
| lastmodifiedby | VARCHAR(128) | User who last modified the record | |
| lastmodifiedtime | BIGINT | Last modification timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(128) | PRIMARY KEY, NOT NULL | Unique identifier for institution |
| propertyid | VARCHAR(256) | FOREIGN KEY, NOT NULL | Reference to eg_pt_property.id |
| tenantId | VARCHAR(256) | NOT NULL | Tenant/ULB identifier |
| name | VARCHAR(1024) | NOT NULL | Name of the institution |
| nameofauthorizedperson | VARCHAR(1024) | Name of authorized person | |
| type | VARCHAR(128) | NOT NULL | Type of institution (GOVERNMENT, PRIVATE, NGO, etc.) |
| designation | VARCHAR(128) | Designation of authorized person | |
| createdby | VARCHAR(128) | NOT NULL | User who created the record |
| createdtime | BIGINT | NOT NULL | Creation timestamp |
| lastmodifiedby | VARCHAR(128) | User who last modified the record | |
| lastmodifiedtime | BIGINT | Last modification timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(256) | PRIMARY KEY, NOT NULL | Unique identifier for address |
| tenantId | VARCHAR(256) | NOT NULL | Tenant/ULB identifier |
| propertyid | VARCHAR(256) | FOREIGN KEY, NOT NULL | Reference to eg_pt_property.id |
| doorno | VARCHAR(128) | Door/house number | |
| plotno | VARCHAR(256) | Plot number | |
| buildingName | VARCHAR(1024) | Building name | |
| street | VARCHAR(1024) | Street name | |
| landmark | VARCHAR(1024) | Nearby landmark | |
| city | VARCHAR(512) | City name | |
| pincode | VARCHAR(16) | Postal code | |
| locality | VARCHAR(128) | NOT NULL | Locality/area code |
| district | VARCHAR(256) | District name | |
| region | VARCHAR(256) | Region name | |
| state | VARCHAR(256) | State name | |
| country | VARCHAR(512) | Country name | |
| latitude | NUMERIC(9,6) | Geographical latitude | |
| longitude | NUMERIC(10,7) | Geographical longitude | |
| createdby | VARCHAR(128) | User who created the record | |
| createdtime | BIGINT | NOT NULL | Creation timestamp |
| lastmodifiedby | VARCHAR(128) | User who last modified the record | |
| lastmodifiedtime | BIGINT | Last modification timestamp | |
| additionaldetails | JSONB | Additional flexible attributes |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(128) | PRIMARY KEY, NOT NULL | Unique identifier for unit |
| tenantId | VARCHAR(256) | NOT NULL | Tenant/ULB identifier |
| propertyid | VARCHAR(128) | FOREIGN KEY, NOT NULL | Reference to eg_pt_property.id |
| floorNo | BIGINT | Floor number | |
| unitType | VARCHAR(256) | Type of unit (ROOM, FLOOR, etc.) | |
| usageCategory | VARCHAR(2048) | NOT NULL | Usage category (RESIDENTIAL, COMMERCIAL, etc.) |
| occupancyType | VARCHAR(256) | NOT NULL | Occupancy type (OWNER, TENANT, UNOCCUPIED) |
| occupancyDate | BIGINT | Date of occupancy | |
| carpetArea | NUMERIC(10,2) | Carpet area in square units | |
| builtUpArea | NUMERIC(10,2) | Built-up area | |
| plinthArea | NUMERIC(10,2) | Plinth area | |
| superBuiltUpArea | NUMERIC(10,2) | Super built-up area | |
| arv | NUMERIC(10,2) | Annual Rental Value | |
| constructionType | VARCHAR(1024) | Type of construction (RCC, BRICK, etc.) | |
| constructionDate | BIGINT | Construction completion date | |
| dimensions | JSON | Unit dimensions in JSON format | |
| active | BOOLEAN | Flag indicating if unit is active | |
| createdby | VARCHAR(128) | User who created the record | |
| createdtime | BIGINT | NOT NULL | Creation timestamp |
| lastmodifiedby | VARCHAR(128) | User who last modified the record | |
| lastmodifiedtime | BIGINT | Last modification timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(128) | PRIMARY KEY, NOT NULL | Unique identifier for document |
| tenantId | VARCHAR(256) | NOT NULL | Tenant/ULB identifier |
| entityid | VARCHAR(256) | NOT NULL | Entity ID (property/owner/unit) this document belongs to |
| documentType | VARCHAR(128) | Type of document (OWNERSHIP_PROOF, ID_PROOF, etc.) | |
| fileStoreid | VARCHAR(128) | NOT NULL | File store service reference ID |
| documentuid | VARCHAR(128) | Document unique identifier | |
| status | VARCHAR(128) | Document status (ACTIVE, INACTIVE) | |
| createdBy | VARCHAR(128) | NOT NULL | User who created the record |
| lastModifiedBy | VARCHAR(128) | User who last modified the record | |
| createdTime | BIGINT | NOT NULL | Creation timestamp |
| lastModifiedTime | BIGINT | Last modification timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(256) | PRIMARY KEY, NOT NULL | Unique identifier for assessment |
| tenantId | VARCHAR(256) | NOT NULL | Tenant/ULB identifier |
| assessmentNumber | VARCHAR(64) | UNIQUE (with tenantId), NOT NULL | Human-readable assessment number |
| financialyear | VARCHAR(256) | NOT NULL | Financial year (e.g., 2023-24) |
| propertyId | VARCHAR(256) | NOT NULL | Reference to property |
| status | VARCHAR(64) | NOT NULL | Assessment status (ACTIVE, CANCELLED, etc.) |
| source | VARCHAR(64) | Source system | |
| channel | VARCHAR(256) | Channel of creation | |
| assessmentDate | BIGINT | NOT NULL | Date of assessment |
| additionalDetails | JSONB | Additional flexible attributes | |
| createdby | VARCHAR(64) | User who created the record | |
| createdtime | BIGINT | NOT NULL | Creation timestamp |
| lastmodifiedby | VARCHAR(64) | User who last modified the record | |
| lastmodifiedtime | BIGINT | NOT NULL | Last modification timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(256) | PRIMARY KEY, NOT NULL | Unique identifier for unit usage |
| tenantId | VARCHAR(256) | NOT NULL | Tenant/ULB identifier |
| assessmentId | VARCHAR(256) | FOREIGN KEY, NOT NULL | Reference to eg_pt_asmt_assessment.id |
| unitId | VARCHAR(64) | NOT NULL | Reference to unit |
| usageCategory | VARCHAR(256) | NOT NULL | Usage category for assessment |
| occupancyType | VARCHAR(64) | NOT NULL | Occupancy type |
| occupancyDate | BIGINT | Date of occupancy | |
| active | BOOLEAN | Flag indicating if record is active | |
| createdby | VARCHAR(64) | User who created the record | |
| createdtime | BIGINT | NOT NULL | Creation timestamp |
| lastmodifiedby | VARCHAR(64) | User who last modified the record | |
| lastmodifiedtime | BIGINT | NOT NULL | Last modification timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(128) | PRIMARY KEY, NOT NULL | Unique identifier for document |
| tenantId | VARCHAR(256) | NOT NULL | Tenant/ULB identifier |
| entityid | VARCHAR(128) | FOREIGN KEY, NOT NULL | Reference to eg_pt_asmt_unitusage.id |
| documentType | VARCHAR(128) | Type of document | |
| fileStoreId | VARCHAR(128) | NOT NULL | File store service reference ID |
| documentuid | VARCHAR(128) | Document unique identifier | |
| status | VARCHAR(128) | Document status | |
| createdBy | VARCHAR(128) | NOT NULL | User who created the record |
| lastModifiedBy | VARCHAR(128) | User who last modified the record | |
| createdTime | BIGINT | NOT NULL | Creation timestamp |
| lastModifiedTime | BIGINT | NOT NULL | Last modification timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| audituuid | VARCHAR(128) | NOT NULL | Unique identifier for audit record |
| propertyid | VARCHAR(128) | NOT NULL | Reference to property |
| property | JSONB | NOT NULL | Complete property object snapshot in JSON |
| auditcreatedtime | BIGINT | NOT NULL | Audit record creation timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(256) | NOT NULL | Assessment ID |
| tenantId | VARCHAR(256) | NOT NULL | Tenant/ULB identifier |
| assessmentNumber | VARCHAR(64) | NOT NULL | Assessment number |
| financialyear | VARCHAR(256) | NOT NULL | Financial year |
| propertyId | VARCHAR(256) | NOT NULL | Property reference |
| status | VARCHAR(64) | NOT NULL | Status |
| source | VARCHAR(64) | Source system | |
| channel | VARCHAR(256) | Channel | |
| assessmentDate | BIGINT | NOT NULL | Assessment date |
| additionalDetails | JSONB | Additional details | |
| createdby | VARCHAR(64) | NOT NULL | Creator |
| createdtime | BIGINT | NOT NULL | Creation time |
| lastmodifiedby | VARCHAR(64) | NOT NULL | Last modifier |
| lastmodifiedtime | BIGINT | NOT NULL | Last modification time |
| auditcreatedtime | BIGINT | NOT NULL | Audit record creation timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(256) | NOT NULL | Unit usage ID |
| tenantId | VARCHAR(256) | NOT NULL | Tenant/ULB identifier |
| assessmentId | VARCHAR(256) | NOT NULL | Assessment reference |
| unitId | VARCHAR(64) | NOT NULL | Unit reference |
| usageCategory | VARCHAR(256) | NOT NULL | Usage category |
| occupancyType | VARCHAR(64) | NOT NULL | Occupancy type |
| occupancyDate | BIGINT | Occupancy date | |
| active | BOOLEAN | Active flag | |
| createdby | VARCHAR(64) | NOT NULL | Creator |
| createdtime | BIGINT | NOT NULL | Creation time |
| lastmodifiedby | VARCHAR(64) | NOT NULL | Last modifier |
| lastmodifiedtime | BIGINT | NOT NULL | Last modification time |
| auditcreatedtime | BIGINT | NOT NULL | Audit record creation timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(128) | PRIMARY KEY, NOT NULL | Unique identifier for migration batch |
| batch | BIGINT | NOT NULL | Batch number |
| batchsize | BIGINT | NOT NULL | Size of the batch |
| tenantid | VARCHAR(256) | NOT NULL | Tenant identifier |
| recordCount | BIGINT | NOT NULL | Number of records migrated |
| createdtime | BIGINT | NOT NULL | Creation timestamp |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(128) | PRIMARY KEY, NOT NULL | Unique identifier |
| batchoffset | BIGINT | NOT NULL | Batch offset for encryption |
| createdtime | BIGINT | NOT NULL | Creation timestamp |
| recordCount | BIGINT | NOT NULL | Number of records encrypted |
| tenantid | VARCHAR(256) | NOT NULL | Tenant identifier |
| message | VARCHAR(2048) | NOT NULL | Encryption message/log |
| encryptiontime | BIGINT | NOT NULL | Time taken for encryption |
| Column Name | Data Type | Constraints | Description |
|---|---|---|---|
| id | VARCHAR(128) | PRIMARY KEY, NOT NULL | Unique identifier |
| tenantid | VARCHAR(256) | UNIQUE (with propertyid, acknowldgementnumber), NOT NULL | Tenant identifier |
| propertyid | VARCHAR(256) | Property ID reference | |
| acknowldgementnumber | VARCHAR(128) | Acknowledgement number | |
| createdTime | BIGINT | NOT NULL | Creation timestamp |
```json {"openapi":"3.0.0","info":{"title":"eGov Property Registry System.","version":"1.0.0"},"tags":[{"name":"Property","description":""}],"servers":[{"url":"https://virtserver.swaggerhub.com/egovernmets-faundation/PT-2.0/1.0.0","description":"SwaggerHub API Auto Mocking","variables":{}},{"url":"https://egov-micro-dev.egovernments.org","variables":{}}],"paths":{"/property/_search":{"post":{"tags":["Property"],"summary":"Get the list of properties defined in the system.","description":"Get the properties list based on the input parameters.\n","operationId":"Getthelistofpropertiesdefinedinthesystem.","parameters":[{"name":"tenantId","in":"query","description":"Unique id for a tenant.","required":true,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"name","in":"query","description":"Name of owner whose property is to be searched.","style":"form","explode":true,"schema":{"type":"string","nullable":true}},{"name":"ids","in":"query","description":"List of system generated ids of properties.","style":"form","explode":true,"schema":{"type":"string"}},{"name":"constructionDetailNumbers","in":"query","description":"List of constructionDetailNumbers to search.","style":"form","explode":true,"schema":{"maxLength":128,"minLength":4,"type":"string"}},{"name":"oldpropertyids","in":"query","description":"List of oldPropertyIds to search..","style":"form","explode":true,"schema":{"maxLength":128,"minLength":4,"type":"string"}},{"name":"mobileNumber","in":"query","description":"MobileNumber of owner whose property is to be searched.","style":"form","explode":true,"schema":{"type":"integer","format":"int64"}},{"name":"fromDate","in":"query","description":"Fetches properties with created time after fromDate.","style":"form","explode":true,"schema":{"type":"number","format":"double"}},{"name":"toDate","in":"query","description":"Fetches properties with created time till toDate.","style":"form","explode":true,"schema":{"type":"number","format":"double"}}],"requestBody":{"description":"RequestHeader meta data.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/RequestHeader"}}},"required":true},"responses":{"200":{"description":"Successful response","headers":{},"content":{"text/plain":{"schema":{"type":"object","description":"Successful response"}}}},"400":{"description":"Invalid input."}},"deprecated":false}}},"components":{"schemas":{"RequestHeader":{"title":"RequestHeader","required":["ts","action","msgId"],"type":"object","properties":{"apiInfo":{"$ref":"#/components/schemas/ApiInfo"},"deviceDetail":{"$ref":"#/components/schemas/DeviceDetail"},"ts":{"type":"integer","description":"time in epoch","format":"int64"},"action":{"maxLength":32,"type":"string","description":"API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc"},"key":{"maxLength":256,"type":"string","description":"API key (API key provided to the caller in case of server to server communication)"},"msgId":{"maxLength":256,"type":"string","description":"Unique request message id from the caller"},"requesterId":{"maxLength":256,"type":"string","description":"UserId of the user calling"},"authToken":{"type":"string","description":"//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token"},"userInfo":{"$ref":"#/components/schemas/UserInfo"},"correlationId":{"type":"string"},"signature":{"type":"string","description":"Hash describing the current RequestHeader"}},"description":"RequestHeader should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestHeader as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseHeader in the response body to ensure correlation."},"ApiInfo":{"title":"ApiInfo","type":"object","properties":{"id":{"maxLength":64,"minLength":2,"type":"string","description":"The id of the API being called"},"version":{"maxLength":64,"minLength":2,"type":"string","description":"The version of the API"},"path":{"type":"string","description":"The URI of the API"}},"description":"Info of the API being called"},"DeviceDetail":{"title":"DeviceDetail","type":"object","properties":{"id":{"type":"string","description":"The id of the device which is trying to accessed"},"signature":{"type":"string","description":"The electronic signature of the device"}},"description":"Contains information about the device used to access the api"},"UserInfo":{"title":"UserInfo","required":["tenantId","userName","primaryrole"],"type":"object","properties":{"tenantId":{"type":"string","description":"Unique Identifier of the tenant to which user primarily belongs"},"uuid":{"type":"string","description":"System Generated User id of the authenticated user."},"userName":{"type":"string","description":"Unique user name of the authenticated user"},"password":{"type":"string","description":"password of the user."},"idToken":{"type":"string","description":"This will be the OTP."},"mobile":{"type":"string","description":"mobile number of the autheticated user"},"email":{"type":"string","description":"email address of the authenticated user"},"primaryrole":{"type":"array","items":{"$ref":"#/components/schemas/Primaryrole"},"description":"List of all the roles for the primary tenant"},"additionalroles":{"type":"array","items":{"$ref":"#/components/schemas/Additionalrole"},"description":"array of additional tenantids authorized for the authenticated user"}},"description":"This is acting ID token of the authenticated user on the server. Any value provided by the clients will be ignored and actual user based on authtoken will be used on the server."},"Primaryrole":{"title":"Primaryrole","required":["code","tenantId"],"type":"object","properties":{"name":{"maxLength":64,"type":"string","description":"Unique name of the role"},"code":{"maxLength":64,"type":"string","description":"Unique code of the role"},"tenantId":{"maxLength":64,"type":"string","description":"The tenantId for which the role is available"},"description":{"type":"string","description":"brief description of the role"}},"description":"minimal representation of the Roles in the system to be carried along in UserInfo with RequestHeader meta data. Actual authorization service to extend this to have more role related attributes"},"Additionalrole":{"title":"Additionalrole","required":["tenantId","roles"],"type":"object","properties":{"tenantId":{"type":"string","description":"tenantid for the tenant"},"roles":{"type":"array","items":{"$ref":"#/components/schemas/Primaryrole"},"description":"Roles assigned for a particular tenant - array of role codes/names"}},"description":"User role carries the tenant related role information for the user. A user can have multiple roles per tenant based on the need of the tenant. A user may also have multiple roles for multiple tenants."}}}} ``` ## Delete Existing Property ## Delete existing property. > The API will delete the property associated with the given propertyId from the system The API works in idempotent manner. ```json {"openapi":"3.0.0","info":{"title":"eGov Property Registry System.","version":"1.0.0"},"tags":[{"name":"Property","description":""}],"servers":[{"url":"https://virtserver.swaggerhub.com/egovernmets-faundation/PT-2.0/1.0.0","description":"SwaggerHub API Auto Mocking","variables":{}},{"url":"https://egov-micro-dev.egovernments.org","variables":{}}],"paths":{"/property/_delete":{"post":{"tags":["Property"],"summary":"Delete existing property.","description":"The API will delete the property associated with the given propertyId from the system The API works in idempotent manner.","operationId":"Deleteexistingproperty.","parameters":[{"name":"tenantId","in":"query","description":"Unique id for a tenant.","required":true,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"propertyId","in":"query","description":"The properrtyId to be deactivated","required":true,"style":"form","explode":true,"schema":{"maxLength":128,"minLength":4,"type":"string"}}],"requestBody":{"description":"Request header for the property delete Request.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/RequestHeader"}}},"required":true},"responses":{"200":{"description":"Deleted Property successful","headers":{},"content":{"text/plain":{"schema":{"type":"object","description":"Deleted Property successful"}}}},"404":{"description":"Delete Property failed"}},"deprecated":false}}},"components":{"schemas":{"RequestHeader":{"title":"RequestHeader","required":["ts","action","msgId"],"type":"object","properties":{"apiInfo":{"$ref":"#/components/schemas/ApiInfo"},"deviceDetail":{"$ref":"#/components/schemas/DeviceDetail"},"ts":{"type":"integer","description":"time in epoch","format":"int64"},"action":{"maxLength":32,"type":"string","description":"API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc"},"key":{"maxLength":256,"type":"string","description":"API key (API key provided to the caller in case of server to server communication)"},"msgId":{"maxLength":256,"type":"string","description":"Unique request message id from the caller"},"requesterId":{"maxLength":256,"type":"string","description":"UserId of the user calling"},"authToken":{"type":"string","description":"//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token"},"userInfo":{"$ref":"#/components/schemas/UserInfo"},"correlationId":{"type":"string"},"signature":{"type":"string","description":"Hash describing the current RequestHeader"}},"description":"RequestHeader should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestHeader as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseHeader in the response body to ensure correlation."},"ApiInfo":{"title":"ApiInfo","type":"object","properties":{"id":{"maxLength":64,"minLength":2,"type":"string","description":"The id of the API being called"},"version":{"maxLength":64,"minLength":2,"type":"string","description":"The version of the API"},"path":{"type":"string","description":"The URI of the API"}},"description":"Info of the API being called"},"DeviceDetail":{"title":"DeviceDetail","type":"object","properties":{"id":{"type":"string","description":"The id of the device which is trying to accessed"},"signature":{"type":"string","description":"The electronic signature of the device"}},"description":"Contains information about the device used to access the api"},"UserInfo":{"title":"UserInfo","required":["tenantId","userName","primaryrole"],"type":"object","properties":{"tenantId":{"type":"string","description":"Unique Identifier of the tenant to which user primarily belongs"},"uuid":{"type":"string","description":"System Generated User id of the authenticated user."},"userName":{"type":"string","description":"Unique user name of the authenticated user"},"password":{"type":"string","description":"password of the user."},"idToken":{"type":"string","description":"This will be the OTP."},"mobile":{"type":"string","description":"mobile number of the autheticated user"},"email":{"type":"string","description":"email address of the authenticated user"},"primaryrole":{"type":"array","items":{"$ref":"#/components/schemas/Primaryrole"},"description":"List of all the roles for the primary tenant"},"additionalroles":{"type":"array","items":{"$ref":"#/components/schemas/Additionalrole"},"description":"array of additional tenantids authorized for the authenticated user"}},"description":"This is acting ID token of the authenticated user on the server. Any value provided by the clients will be ignored and actual user based on authtoken will be used on the server."},"Primaryrole":{"title":"Primaryrole","required":["code","tenantId"],"type":"object","properties":{"name":{"maxLength":64,"type":"string","description":"Unique name of the role"},"code":{"maxLength":64,"type":"string","description":"Unique code of the role"},"tenantId":{"maxLength":64,"type":"string","description":"The tenantId for which the role is available"},"description":{"type":"string","description":"brief description of the role"}},"description":"minimal representation of the Roles in the system to be carried along in UserInfo with RequestHeader meta data. Actual authorization service to extend this to have more role related attributes"},"Additionalrole":{"title":"Additionalrole","required":["tenantId","roles"],"type":"object","properties":{"tenantId":{"type":"string","description":"tenantid for the tenant"},"roles":{"type":"array","items":{"$ref":"#/components/schemas/Primaryrole"},"description":"Roles assigned for a particular tenant - array of role codes/names"}},"description":"User role carries the tenant related role information for the user. A user can have multiple roles per tenant based on the need of the tenant. A user may also have multiple roles for multiple tenants."}}}} ``` ## Cancel Existing Property ## Cancel existing property. > The API will delete the property associated with the given propertyId from the system The API works in idempotent manner. ```json {"openapi":"3.0.0","info":{"title":"eGov Property Registry System.","version":"1.0.0"},"tags":[{"name":"Property","description":""}],"servers":[{"url":"https://virtserver.swaggerhub.com/egovernmets-faundation/PT-2.0/1.0.0","description":"SwaggerHub API Auto Mocking","variables":{}},{"url":"https://egov-micro-dev.egovernments.org","variables":{}}],"paths":{"/property/_cancel":{"post":{"tags":["Property"],"summary":"Cancel existing property.","description":"The API will delete the property associated with the given propertyId from the system The API works in idempotent manner.","operationId":"Cancelexistingproperty.","parameters":[{"name":"tenantId","in":"query","description":"Unique id for a tenant.","required":true,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"propertyId","in":"query","description":"The properrtyId to be deactivated","required":true,"style":"form","explode":true,"schema":{"maxLength":128,"minLength":4,"type":"string"}}],"requestBody":{"description":"Request header for the property delete Request.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/RequestHeader"}}},"required":true},"responses":{"200":{"description":"Deleted Property successful","headers":{},"content":{"text/plain":{"schema":{"type":"object","description":"Deleted Property successful"}}}},"404":{"description":"Delete Property failed"}},"deprecated":false}}},"components":{"schemas":{"RequestHeader":{"title":"RequestHeader","required":["ts","action","msgId"],"type":"object","properties":{"apiInfo":{"$ref":"#/components/schemas/ApiInfo"},"deviceDetail":{"$ref":"#/components/schemas/DeviceDetail"},"ts":{"type":"integer","description":"time in epoch","format":"int64"},"action":{"maxLength":32,"type":"string","description":"API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc"},"key":{"maxLength":256,"type":"string","description":"API key (API key provided to the caller in case of server to server communication)"},"msgId":{"maxLength":256,"type":"string","description":"Unique request message id from the caller"},"requesterId":{"maxLength":256,"type":"string","description":"UserId of the user calling"},"authToken":{"type":"string","description":"//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token"},"userInfo":{"$ref":"#/components/schemas/UserInfo"},"correlationId":{"type":"string"},"signature":{"type":"string","description":"Hash describing the current RequestHeader"}},"description":"RequestHeader should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestHeader as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseHeader in the response body to ensure correlation."},"ApiInfo":{"title":"ApiInfo","type":"object","properties":{"id":{"maxLength":64,"minLength":2,"type":"string","description":"The id of the API being called"},"version":{"maxLength":64,"minLength":2,"type":"string","description":"The version of the API"},"path":{"type":"string","description":"The URI of the API"}},"description":"Info of the API being called"},"DeviceDetail":{"title":"DeviceDetail","type":"object","properties":{"id":{"type":"string","description":"The id of the device which is trying to accessed"},"signature":{"type":"string","description":"The electronic signature of the device"}},"description":"Contains information about the device used to access the api"},"UserInfo":{"title":"UserInfo","required":["tenantId","userName","primaryrole"],"type":"object","properties":{"tenantId":{"type":"string","description":"Unique Identifier of the tenant to which user primarily belongs"},"uuid":{"type":"string","description":"System Generated User id of the authenticated user."},"userName":{"type":"string","description":"Unique user name of the authenticated user"},"password":{"type":"string","description":"password of the user."},"idToken":{"type":"string","description":"This will be the OTP."},"mobile":{"type":"string","description":"mobile number of the autheticated user"},"email":{"type":"string","description":"email address of the authenticated user"},"primaryrole":{"type":"array","items":{"$ref":"#/components/schemas/Primaryrole"},"description":"List of all the roles for the primary tenant"},"additionalroles":{"type":"array","items":{"$ref":"#/components/schemas/Additionalrole"},"description":"array of additional tenantids authorized for the authenticated user"}},"description":"This is acting ID token of the authenticated user on the server. Any value provided by the clients will be ignored and actual user based on authtoken will be used on the server."},"Primaryrole":{"title":"Primaryrole","required":["code","tenantId"],"type":"object","properties":{"name":{"maxLength":64,"type":"string","description":"Unique name of the role"},"code":{"maxLength":64,"type":"string","description":"Unique code of the role"},"tenantId":{"maxLength":64,"type":"string","description":"The tenantId for which the role is available"},"description":{"type":"string","description":"brief description of the role"}},"description":"minimal representation of the Roles in the system to be carried along in UserInfo with RequestHeader meta data. Actual authorization service to extend this to have more role related attributes"},"Additionalrole":{"title":"Additionalrole","required":["tenantId","roles"],"type":"object","properties":{"tenantId":{"type":"string","description":"tenantid for the tenant"},"roles":{"type":"array","items":{"$ref":"#/components/schemas/Primaryrole"},"description":"Roles assigned for a particular tenant - array of role codes/names"}},"description":"User role carries the tenant related role information for the user. A user can have multiple roles per tenant based on the need of the tenant. A user may also have multiple roles for multiple tenants."}}}} ``` # Property Tax Calucator API # Property Tax System - Functional Specifications Functional overview for stakeholders ## Introduction The Property Tax System provides a digital interface to make property assessments, pay property tax, generate payment receipts and monitor tax collection. The citizens can use it, Urban Local Body (ULB) counter field employees and ULB Administrators to accomplish their specific tasks. It is available as a mobile and web-based application. ## Functional Scope The property tax application features can be broadly classified as the following modules: 1. Registration, Login and Creation of User Profile 2. Filling an Assessment for a Property 3. Searching for a Property 4. Modifications to a Property 5. Generate Demand Notice 6. Payments collection and Receipts 7. Dashboards and Reports 8. General Features ### Registration, Login and Creation of User Profile {% hint style="warning" %} * OTP Based Login for Citizens via Web/Mobile App * OTP Based Login for Employees via Web/Mobile App * Provision for language selection during first-time registration for both employees and citizens * Provision of creating a personalized Profile for Citizens and employees on the Web App * Login Credentials for the various hierarchy of employees * Role-based access for performing different actions relating to property tax modules {% endhint %} ### Filing For Property Assessment This feature enables citizens and employees to self-assess a new property for a financial year. It 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 property tax system design is user-friendly and reduces the chances of error. The system calculates the tax automatically and creates the demand. If a user wants to reassess his property for any reason (for example - incorrect data, change in property etc), it can be done by editing the 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. Citizens can track down the status of their incomplete assessment. Any incomplete assessment can be searched and completed. {% hint style="warning" %} * Citizen/CSC can assess new property (by different financial years). * Citizen/CSC can capture Address, Assessment Info, and Owner information for all property types like residential houses, flats and commercial buildings. o Sample Details captured include - * 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 state-specific processes and rules. * The system has a facility to make entries in the system by the inspector after a site visit and assessment of the same by the superintendent. * The system dynamically calculates the late fees, interest, rebates, etc for demand generation. * The system fetches the previous year's property data while e-filing the current year to calculate the dues. * 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 {% endhint %} ### Searching for a Property Citizens or employees can track down the status of their incomplete assessment. Any incomplete assessment can be searched and completed. {% hint style="warning" %} * Citizens/CSC can search for property using * Mobile No * City * Property Tax Unique ID * Citizens/ CSC can view incomplete assessments * Citizens/CSC can reassess searched property * View property details and pending dues {% endhint %} ### Modifications to a Property The property tax system provides the ability to capture mutation and transfer of ownership. It reduces interfaces between the user and the State and thus promotes 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 impact 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. {% hint style="warning" %} * 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 {% endhint %} ### Generate Demand Notice The system can automatically generate demand notices for a financial year based on set triggers like time-based rollover on the completion of a financial year. The system notifies the citizens about the demand through SMS/Email. The generated bills can also be grouped and printed for physical distribution by the ULB employees. The system enables employees to merge and download bills based on defined parameters to plan distribution drives. {% hint style="warning" %} * Generate demand notice based periodically * Group demand notices * Print demand notices * Cancel demand notices * Send notifications to citizens on demand generation- SMS, WhatsApp, Email, physical bill {% endhint %} ### Payments collection and Receipts The citizen/ employee can view the payment status of previous assessments from the Assessment History section. It allows users to pay assessment fees fully or partially. Assessment receipts can be downloaded from the assessment history section within the property details. {% hint style="warning" %} * Payment of property tax - online, cheque, cash, DD, during assessment * Partial payment of property tax - online, cheque, cash, DD, during assessment * The system allows a citizen to pay for anyone's property without changing the demand * The system can also be integrated with PoS machines to enable doorstep collection of property tax and issue of receipt {% endhint %} ### Reports and Dashboards Property tax reports provide the facility to access the receipt register, cancelled receipt register, account receipt register, ULB-wise PT collection report, and DCB Register. All reports can be downloaded in PDF/XLS format. State-level administrators can monitor property tax collections, assessments and other information at a state level through dashboards. {% hint style="warning" %} * State Dashboard: View Reports for Total Collections, Properties Assessed, ULBs on Prod, Usage Type, Payment Distribution * State Dashboard: PT Collection Timeline (Monthly, Weekly) * State Dashboard: ULB Wise (Collection, Assessments) * Cancelled Receipt Register Report * PT Collection Report (ULB/Date Wise) {% endhint %} ### General Features {% hint style="warning" %} **Notifications -** The system can send notifications to citizens. These notifications can be sent for various steps like - assessment completion, payment reminder, and payment confirmation. These notifications can be sent in the language chosen by the ULB through all channels - SMS, WhatsApp, and Email. **Legacy Data Migration -** The system can migrate Demand and Collection. In most states, the preliminary step would be to migrate Legacy data of existing properties/connections along with the Demand and Collection details. This would ensure that subsequent demand generation happens through the system. **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: Property Ontology, Documents List, Employee Data Mapping, Boundary Data Mapping {% endhint %} System specification in compliance with the Ease of Doing Business (EODB) BRAP 2019.
| Reform No. | Reform Area | Weightage (score) | Recommendation | Remarks |
|---|---|---|---|---|
| 7 | Land administration and Transfer of Land and Property | 3 | Digitize land transaction deeds of last 10 years at all sub-registrar offices and make the same available on an online system to check for ownership details and history. The metadata should be searchable for each record and a soft copy of the registered deed should be available. The searchable metadata available should be: i. Name of buyer ii. Name of seller iii. Survey no. iv. Registration number v. Registration date | The feature of ‘Property Registry’ in the product will enable this recommendation |
| 8 | Land administration and Transfer of Land and Property | 3 | Digitize and publish the updated Record of Rights (ROR) at all Revenue department offices online in public domain for all areas of the State/UT. The searchable metadata available should be: i. Name of buyer ii. Name of seller iii. Date of mutation iv. Survey no. | The Property tax system enables this capability |
| 9 | Land administration and Transfer of Land and Property | 2 | Digitize and publish data of Property Tax payment dues online in public domain for all the Urban Local Bodies (ULBs) in the State/UT. The searchable metadata available should be: i. Name of the Property Tax payer ii. Property Tax dues iii. Survey no. of land / Unique Identification no. of property | This feature is enabled by the citizens itself |
| 10 | Land administration and Transfer of Land and Property | 2 | Digitize cadastral maps of all rural areas in the State/UT and make them available in public domain | This can be enabled and worked on by the state team |
| 11 | Land administration and Transfer of Land and Property | 5 | Integrate the below-mentioned records on one website: i. Data of land transaction deeds for last 10 years at all sub-registrar offices (Name of buyer, Name of seller, Registration number, Registration date, Survey no.), ii. Updated Record of Rights at all Revenue department offices (Date of mutation), and iii. Data of Property Tax payment dues at all urban areas of the State/UT (Name of the Property Tax payer, Property Tax dues) iv. Revenue Court case data (Court case number, Name of parties involved, Date of filing of court case, Status of case [Ongoing/Resolved]) v. Civil Court case data (Court case number, Name of parties involved, Date of filing of court case, Status of case [Ongoing/Resolved]) The website should be publicly accessible. It will help in establishing property ownership and identify tax encumbrances. The integration should be done for all areas of the State/UT. | The integration with external portals and systems of other departments can be enabled by state teams who can enhance the offered product to cater to this recommendation |
| 12 | Land administration and Transfer of Land and Property | 2 | Implement an online application system having the following features i. Mandatory Online application submission including submission of draft deed and other documents ii. Provision of online payment of Stamp duty and Registration fee iii. Auto generation of appointment date and time on making the payment of Stamp duty and Registration fee | The system will provide these capabilities which can be customised as per the state specific rules and regulations |
| 13 | Land administration and Transfer of Land and Property | 1 | Provide model deed templates for sale, gift, lease, mortgage and rent in downloadable and editable format along with instructions to use them | This provision is made available through the ULB portal to make these features accessible to the citizens |
| 14 | Land administration and Transfer of Land and Property | 2 | Integrate the mutation process with the registration process and mandate initiation of mutation process (Revenue department and/ or ULB) as soon as the deed is registered. Ensure that: i. Information to mutation authority to be automatically shared on completion of transaction (registration). This should be considered as initiation of mutation process. ii. No separate application from transferee to be required. iii. SMS/email should be sent to transferee/ transferor to inform about the initiation of mutation | The integration with external portals and systems of other departments can be enabled by state teams who can enhance the offered product to cater to this recommendation |
| List of Functionalities | Corresponding Features |
|---|---|
| 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 various hierarchy of employees. | |
| Provision of Personalized Profile for Citizen/ Employee on Web App | |
| Filing an assessment for a property | Citizen/CSC : Assess New Property (By Different Financial Years). |
| Citizen/CSC : Capture Address, Assessment Info, Owner Info. | |
| Citizen/CSC : View/Print Summary of Filled Form | |
| Searching for a property | Citizen/CSC : Search Property (By Mobile No,City, Property Tax Unique ID, Existing ID). |
| Citizen/CSC : View the Searched Property | |
| Citizen : View My Properties | |
| Citizen : View Incomplete Assessments | |
| Citizen/CSC : Edit the Searched Property | |
| Citizen/CSC : Reassess Searched Property | |
| Generate demand notice | Generate Demand Notice based on periodic basis |
| Group/ Print/ Cancel Demand Notices | |
| Send notifications to citizens on demand generation- SMS, Whatsapp, Email, Physical bill | |
| Modifications to a property | Mutation of property and change of ownership details |
| Capture Extension/ Addition and Alteration and reassessment based on changed property details | |
| Bifurcation/ Amalgamation of property | |
| Payment collection and receipts | Payment of TAX (Online,Cheque,Cash,DD) : During Assessment |
| Payment of TAX (Online,Cheque,Cash,DD) : Partial Payment | |
| Citizen/CSC : Download Receipts for payments | |
| Dashboards and reports | State Dashboard : View Reports for Total Collections, Properties Assessed, ULBs on Prod, Usage Type, Payment Distribution |
| State Dashboard : PT Collection Timeline (Monthly,Weekly) | |
| State Dashboard : ULB Wise (Collection, Assessments) | |
| Cancelled Receipt Register Report | |
| PT Collection Report (ULB/Date Wise) | |
| General features | Notification |
| Legacy data migration | |
| System assigns a unique property ID based on the Process defined in the ULBs. | |
| System has the facility to classify the property based on its type. | |
| System allows changing the type of property. | |
| Configuration masters | Configurable Rate Master (ULB Specific) : Fire Cess/ Building Height |
| Charges & Calculation : Calculation Engine, Rebate, Penalty | |
| State Masters : Property Ontology, Documents List, Employee Data Mapping, Boundary Data Mapping |
| State | Basis | # Applications |
|---|---|---|
| Andhra Pradesh | [On basis of data available in the property tax system] | 453 |
| Punjab | [On the basis of application received manually] | 3000 |
| Uttarakhand | [On the basis of application received manually] | 1500 |
| Cantonment Boards | [On the basis of application received manually] | 1000 |
| Odisha | [On the basis of application received manually] | NA |
| Acronym | Value |
|---|---|
| ARVM | Annual Rental Value Method |
| UAVM | Unit Area Value Method |
| CVM | Capital Value Method |
| IGRS | Inspector General of Registration and Stamps |
| CV | Capital Value |
| ARVM/UAVM | CVM | Comments |
|---|---|---|
| Property Type | Property Type | It is to define the structure of property as a property would be a vacant land, or a building. |
| Property Usage | Property Usage | It is upto 3 levels of categorization of usage of a property. |
| Floors | Floors | It is to define the floors e.g. Ground Floor, First Floor etc. |
| Occupancy | Not Applicable | Occupancy defines whether a property is occupied by the owner itself or rented out to a tenant. |
| Ownership Type | Ownership Type | It is upto 2 levels of categorization of ownership of a property. |
| Owner’s Category | Owner’s Category | It is a category of owner based on which owner would be eligible for certain exemption on property tax. E.g. Freedom Fighter, Army Personal etc. |
| Construction Type | Construction Type | It is to define the consumption category of a building. A building would be a Pakka, Kachha or Semi Pakka etc. |
| Not Applicable | Distance From Road | Distance of the building from the main road plays the role to calculate the capital value. It is applicable to vacant land properties only. |
| ARVM/UAVM | CVM | Comments |
|---|---|---|
| ULB | ULB | It is to define the ULB with all its attributes like District, Address, Grade etc. |
| Ward | Not Applicable | All the ULBs in the state have only one boundary hierarchy i.e. Admin Boundary which is used for both Revenue and Administration purposes. Ward is the smallest boundary in this hierarchy and placed at second level just below the ULB boundary itself. |
| Locality | Not Applicable | Locality or Mohalla is the smallest boudry unit within the ULB which defines the state of the bounded area. So a locality would be specified as posh, modest, slum etc. and the rares are defined accordingly. Rental and Unit Area rates are defined based on the locality. |
| Not Applicable | SRO | Name of sub registrar office within the given district. For smaller cities there is only one SRO. |
| Not Applicable | Segment/ Block | Localities are further segmented into multiple blocks to define the circle rates. |
| ARVM/UAVM | CVM | Comments |
|---|---|---|
| Rental Rates | Not Applicable | Rental rates are generally defined based on the locality, usage, and the construction type of the property. |
| Unit Rates | Not Applicable | Rental rates are generally defined based on the locality, usage, and the construction type of the property. |
| Not Applicable | Circle Rates | Circle rates are generally defined based on the Segment or Block, Usage, Property Type, Construction Type, and Distance of property from the road. |
| Tax Rates | Tax Rates | |
| Penal Interest | Penal Interest | |
| Penalties | Penalties | |
| Rebates | Rebates |
| Field Name | Field Type | Is Mandatory | Comments |
|---|---|---|---|
| Pincode | Textbox | No | Pincode of the locality property belongs to. Though it is non-mandatory. |
| Locality | Dropdown | Yes | Locality to which property belongs to. It is internally mapped to ward and ULB boundary. |
| Street Name | Textbox | No | Street name on which property is situated. |
| Door No. | Textbox | Yes | It is mandatory for Buildings and Flats |
| SRO | Dropdown | Yes | SRO will be populated based on the district of ULB. |
| Block/ Segment | Dropdown | Yes | It is a non-editable field. It is populated on SRO selected and cross hierarchy mapping if it exists. |
| Type | Usage 1 | Construction | Usage 2 | Rate |
|---|---|---|---|---|
| Individual | Residential | Pakka | 12000 | |
| Individual | Residential | Kachcha | 10000 | |
| Individual | Non-residential | Shop/ Restaurant/ Office | 64000 | |
| Individual | Non-residential | Others | 58000 | |
| Flat | 30000 | |||
| Plot | 16000 |
| Property Type | Property Type (Hindi) | Usage | Nature Of Business | Construction Type | Distance From Road |
|---|---|---|---|---|---|
| Forming Land | कृषि भूमि | ||||
Vacant Land (Land area In Sq. Mt.) | अकृषि भूमि | NA | NA | 0 से 50 मीटर तक | |
| 51 से 350 मीटर तक | |||||
| 350 मीटर से अधिक | |||||
| 0-50 मीटर | |||||
| 51 से 200 मीटर तक | |||||
| 200 मीटर से अधिक | |||||
| 0 से 200 मीटर तक | |||||
Flat in apartment (Super builtup area In Sq. Mt.) | बहुमंजलीय आवासीय भवन में स्थित आवासीय फ्लैट | Residential | NA | NA | NA |
Individual building (Builtup area in Sq. Mt.) | वाण्ज्यििक भवन/ गैर वाण्ज्यििक भवन | Residential | NA | प्रथम श्रेणी (लिन्टरपोष)/ (पक्का ) | NA |
| द्वितीय श्रेणी (टीनपोश)/ (सेमी पक्का/ कच्चा) | NA | ||||
| Non-residential | दुकान/रेस्टेरेन्ट/कार्यालय | NA | NA | ||
| अन्य वाण्ज्यििक प्रतिष्ठान | NA | NA |
| dcode | srocode | circle_rate_id | Block Code | Block Name |
|---|---|---|---|---|
| Segment Master | ||||
| 4 | 1 | 5 | 3070 | रायपुर मार्ग पर काली मन्दिर से नालापानी चौक होते हुये सहस्त्रधारा मार्ग तक |
| 4 | 1 | 5 | 3071 | डोईवाला - बुल्लावाला मार्ग |
| 4 | 1 | 5 | 3072 | डोईवाला - खत्ता मार्ग |
| 4 | 1 | 5 | 3073 | डोईवाला - धर्मूचक मार्ग |
| 4 | 1 | 5 | 3074 | मियॉवाला नहर वाली सड़क से रायपुर राझांवाला तक |
| 4 | 1 | 5 | 3075 | नकरौन्दा-घिसर पडी रोड |
| 4 | 1 | 5 | 3076 | गूलरघाटी रायपुर रोड |
| 4 | 1 | 5 | 3077 | मुख्य हिरद्वार मार्ग मियॉवाला चौक से चकतुनाला होते हये हाथीखाना चौक तक |
| 4 | 1 | 5 | 3078 | मुख्य हरिद्वार मार्ग से माजरी माफी (रेलवे फाटक), हरिपुर/नवादा होते हुए इन्दरपुर तक |
| 4 | 1 | 5 | 3079 | जोगीवाला चौक से बद्रीपुर होते हुए इन्दरपुर तक, बद्रीपुर चौक से माजरी माफी तक |
| 4 | 1 | 5 | 3080 | विधान सभा के बाद स्थित रेलवे फाटक के बाद से एम0डी0डी0ए0 कालोनी केदारपुरम तक |
| 4 | 1 | 5 | 3081 | हरिद्वार रोड पर कुऑवाला से गूलरघाटी चौक तक |
| 4 | 1 | 5 | 3082 | फयरिंग रेंज के बाद से दौडवाला होते हुये दुधली डोईवाला मार्ग तक, केदारपुर सचिवालय कालोनी के बाद से दुधली डोईवाला मार्ग तक |
| 4 | 1 | 5 | 3083 | दून यूनिवर्सिटी से मोथरोवाला लिंक रोड |
| 4 | 1 | 5 | 3084 | सहारनपुर हरिद्वार बाईपास मार्द से दक्षिण दिशा की ओर जाने वाली मोथरोवाला मार्ग से दून यूनिवर्सिटी के सामने से केदारपुर / सचिवालय कालोनी होकर जाने वाला मार्ग जो अन्त में फाईरिंग रैज के पुल पर मिल जाता है । |
| 4 | 1 | 5 | 3085 | सहारनपुर हरिद्वार बाईपास मार्ग पर पुलिस चैक पोस्ट के सामने, महिन्द्रा शोरूम के बाराबर से मोथरोवाला रोड बंगाली कोठी के बाद ,केदारपुर, प्राथमिक पाठशाला होते हुए दुधली-डोईवाला मार्ग के पुल तक, |
| 4 | 1 | 5 | 3086 | सहारनपुर हरिद्वार बाईपास मार्द से दक्षिण दिशा की ओर जाने वाली कारगी / कारगी चौक से बंजारावाला तक, |
| 4 | 1 | 5 | 3087 | मौथरोवाला दूधली डोईवाला मार्ग |
| 4 | 1 | 5 | 3088 | चकराता रोड आई0एम0ए0 के सामने से प्रेमनगर-गोरखपुर रोड ग्राम आरकेडियाग्रान्ट की सीमा तक तथा तेलपुरा चौक तक |
| 4 | 1 | 5 | 3089 | डाईवर्जन रोड से सिनौला-जोहडी-अनारवाला वाला मार्ग |
| 4 | 1 | 5 | 3090 | जाखन-जोहडी मार्ग |
| 4 | 1 | 5 | 3091 | रिखोली-मसूरी बाईपास रोड |
| 4 | 1 | 5 | 3092 | कुठाल गेट से मसूरी तक मुख्य मार्ग |
| 4 | 1 | 5 | 3093 | पुराना पोस्ट आफिस (जोगीवाला) से किद्दूवाला चौक तक |
| 4 | 1 | 5 | 3094 | पुलिया नं0 6 से किद्दूवाला चौक होते हुये महाराणा प्रताप चौक तक |
| 4 | 1 | 5 | 3095 | मसूरी बाईपास रोड-रिंग रोड (पुलिया नं0 6 के बाद से रायपुर रोड तक ) |
| 4 | 1 | 5 | 3096 | मालसी पुलिया से दोनाली चौक तक |
| 4 | 1 | 5 | 3097 | रायपुर चौक (शिव मन्दिर) से मालदेवता मार्ग वाया वाण्डा वाली |
| 4 | 1 | 5 | 3098 | किरसाली चौक से काला गॉव तक |
| 4 | 1 | 5 | 3099 | सहस्त्रधारा रोड ( कुल्हान करनपुर के बाद से मालदेवता तक) |
| 4 | 1 | 5 | 3100 | मालदेवता सिल्ला क्यारा रोड |
| 4 | 1 | 5 | 3101 | रायपुर रोड पर चक्की नम्बर चार से दोनाली चौक तक |
| 4 | 1 | 5 | 6285 | रायपुर - थानो मार्ग (रायपुर चौक से थानो चौक तक) |
| 4 | 1 | 5 | 3102 | सहस्त्रधारा मार्ग पर स्थित किरसाली चौक से मसूरी बाई पास मार्ग पड़नेवाले समस्त राजस्व ग्राम एवं उक्त मार्ग के अन्त में स्थित साई मन्दिर के बराबर पर पहॅुचने वाले मार्ग तक |
| 4 | 1 | 5 | 3103 | गुनियाल गांव-भगवतपुर मार्ग पुरूकुल गॉव तक |
| 4 | 1 | 5 | 3104 | हरिद्वार रोड पर लच्छीवाला फलाईओवर के बाद से डोईवाला टाउन एरिया क्षेत्र के प्रारम्भ होने तक |
| 4 | 1 | 5 | 3105 | शिमला बाईपास राड पर मेहुवाला ग्राम के बाद से ग्राम बडोवाल की सीमा समाप्ति तक |
| 4 | 1 | 5 | 3106 | सहारनपुर रोड पर चन्द्रबनी चौक से वाईल्ड लाईफ संस्थान तक |
| 4 | 1 | 5 | 3107 | सहारनपुर रोड से ब्राहमणवाला रोड माजरा क्षेत्र |
| 4 | 1 | 5 | 3108 | सहारनपुर रोड से इन्द्रा गाधी मार्ग माजरा क्षेत्र |
| 4 | 1 | 5 | 3109 | सहस्त्रधारा रोड पर छतरी के बाद से सहस्त्रधारा तक |
| 4 | 1 | 5 | 3110 | रायपुर रोड से काली मन्दिर से रायपुर तक |
| 4 | 1 | 5 | 3111 | रायपुर रोड पर सहस्त्रधारा चौक से काली मंदिर तक |
| 4 | 1 | 5 | 3112 | सहस्त्रधारा मार्ग पर स्थित आई0टी0 पार्क वाले मार्ग पर पड़नेवाले समस्त राजस्व ग्राम एवं उक्त मार्ग के अन्त में स्थित उप्पल टावर से होते हुये कैनाल रोड से पूर्व तक |
| 4 | 1 | 5 | 3113 | सहस्त्रधारा रोड पर आई0 टी0 पार्क के आगे से छतरी तक |
| 4 | 1 | 5 | 3114 | मसूरी बाईपास रोड-रिंग रोड (जोगीवाला चौक से पोस्ट आफिस होते हुये पुलिया नं0 6 तक) |
| 4 | 1 | 5 | 3115 | लक्ष्मी रोड के चौराहे से बद्रीश कालोनी होते हुए पुलिया नं0 6 तक) |
| 4 | 1 | 5 | 3116 | मोथरोवाला रोड (धर्मपुर चौक के निकट से बाईपास रोड तक) |
| 4 | 1 | 5 | 3117 | माता मन्दिर रोड (धर्मपुर चौक से बाईपास रोड पर स्थित पुलिस चौक पोस्ट तक) |
| 4 | 1 | 5 | 3118 | हरिद्वार रोड पर कुऑवाला से लच्छीवाला फ्लाई ओवर तक |
| 4 | 1 | 5 | 3119 | कौलागढ रोड पर सैन्ट्रल स्कूल से आगे कौलागढ की सीमा तक |
| 4 | 1 | 5 | 3120 | चकराता रोड पर प्रेननगर बस स्टैन्ड से नदी तक |
| 4 | 1 | 5 | 3121 | बाईपास रोड (सहारनपुररोड से हरिद्वार रोड तक) |
| 4 | 1 | 5 | 3122 | शिमला बाईपास रोड पर सहारनपुर रोड के 350 मीटर बाद से मेहुवाला ग्राम की सीमा समाप्ति तक |
| 4 | 1 | 5 | 3123 | सहारनपुर रोड पर सुभाष नगर चौक से आगे वन क्षेत्र तक |
| 4 | 1 | 5 | 3124 | सहारनपुर रोड लाल पुल से महन्त इन्द्रेश अस्पताल- देहराखास होते हुये कारगी चौक तक |
| 4 | 1 | 5 | 3125 | सर्वे चौक से रायपुर रोड पर रिस्पना पुल, सहस्त्रधारा चौक होते हुये आई0टी0पार्क तक |
| 4 | 1 | 5 | 3126 | हरिद्वार रोड पर जोगीवाला से कुँवावाला तक |
| 4 | 1 | 5 | 3127 | सहारनपुर रोड पर टर्नर रोड से सुभाष नगर चौक तक |
| 4 | 1 | 5 | 3128 | एफ आर आई के सामने से बसन्त विहार चौक तक |
| 4 | 1 | 5 | 3129 | अनुराग नर्सरी रोड पर बल्लीवाला चौक से बसन्त विहार चौक- लवली मार्किट- पंडितवाडी चकराता रोड तक |
| 4 | 1 | 5 | 3130 | अनुराग नर्सरी से इन्द्रानगर- सीमाद्वार- जी0एम0एस0 रोड तक |
| 4 | 1 | 5 | 3131 | कांवली रोड/शिवाजी मार्ग पर सहारनपुर चौक से बल्लीवाला चौक तक |
| 4 | 1 | 5 | 3132 | मौरवियन इन्स्टीटयूट वाली ओल्ड मसूरी रोड पर राजपुर तिराहे से कुठालगेट तक |
| 4 | 1 | 5 | 3133 | शहंशाही आश्रम वाली ओल्ड मसूरी रोड पर राजपुर तिराहे से कुठालगेट तक |
| 4 | 1 | 5 | 3134 | जी0एम0एस0 रोड (बल्लीवाला चौक से सेवला कलां ट्रान्सपोर्ट नगर होते हुए मौहब्बेवाला, सहारनपुर रोड तक) तथा सकलानी गैस गोदाम क्रासिंग से सहारनपुर रोड पर सब्जी मण्डी तिराहे तक |
| 4 | 1 | 5 | 3135 | सहारनपुर रोड पर बिन्दाल पुल से टर्नर रोड तक |
| 4 | 1 | 5 | 3136 | गढी चौक से बल्लुपुर चौक वाली- कैनाल रोड |
| 4 | 1 | 5 | 3137 | चकराता रोड पर बल्लुपुर चौक से प्रेमनगर बस स्टैण्ड तक |
| 4 | 1 | 5 | 3138 | हरिद्वार रोड रिस्पना पुल से जोगीवाला तक |
| 4 | 1 | 5 | 3139 | जी0एम0एस0 रोड (बल्लुपुर चौक से बल्लीवाला चौक तक) |
| 4 | 1 | 5 | 3140 | कौलागढ़ रोड पर किशन नगर चौक से सैन्ट्रल स्कूल तक |
| 4 | 1 | 5 | 3141 | सहारनपुर रोड पर सहारनपुर चौक से बिन्दाल पुल तक |
| 4 | 1 | 5 | 3142 | डायवर्जन रोड पर मालसी डीयर पार्क से कुठाल गेट तक |
| 4 | 1 | 5 | 3143 | डायवर्जन रोड पर मसूरी बाईपास से मालसी डीयर पार्क तक |
| 4 | 1 | 5 | 3144 | राजपुर रोड के समानान्तर कैनाल रोड काठबंगला तक |
| 4 | 1 | 5 | 3145 | राजपुर रोड पर मसूरी बाईपास से राजपुर तक (साई मन्दिर होते हुए) |
| 4 | 1 | 5 | 3146 | सुभाष रोड |
| 4 | 1 | 5 | 3147 | ईस्ट कैनाल राड |
| 4 | 1 | 5 | 3148 | न्यू कैन्ट रोड (कैंट सीमा तक) |
| 4 | 1 | 5 | 3149 | हरिद्वार रोड प्रिन्स चौक से रिस्पना पुल तक |
| 4 | 1 | 5 | 3150 | चकराता रोड पर घंटाघर से बिन्दाल पुल-किशन नगर चौक होते हुये बल्लुपुर चौराहे तक |
| 4 | 1 | 5 | 3151 | गांधी रोड पर रेलवे स्टेशन से आढत बाजार होते हुये सहारनपुर चौक तक |
| 4 | 1 | 5 | 3152 | सहारनपुर रोड पर रेलवे स्टेशन से सहारनपुर चौक तक |
| 4 | 1 | 5 | 3153 | घंटाघर से लक्खीबाग चौकी तक के मध्य स्थित पल्टन बाजार/धामावाला/पीपल मण्डी/दर्शनी गेट |
| 4 | 1 | 5 | 3154 | गांधी रोड पर घंटाघर से दर्शन लाल चौक/ प्रिन्स चौक होते हुये रेलवे सटशन तक |
| 4 | 1 | 5 | 3155 | राजपुर रोड पर आर0टी0ओ0 कार्यालय से मसूरी बाईपास तक |
| 4 | 1 | 5 | 3157 | राजपुर रोड पर घण्टाघर से आर0टी0ओ0 कार्यालय तक |
| 4 | 1 | 5 | 3218 | अजबपुर कलां |
| 4 | 1 | 5 | 3420 | बिन्दाल रोड |
| 4 | 1 | 5 | 3421 | खदरी मौहल्ला |
| 4 | 1 | 5 | 3422 | छबील बाग |
| 4 | 1 | 5 | 3423 | जटिया मौहल्ला |
| 4 | 1 | 5 | 3424 | इन्द्रश नगर |
| 4 | 1 | 5 | 3425 | प्रेमनगर |
| 4 | 1 | 5 | 3426 | कांवली शेष क्षेत्र (कांवली क्षेत्र की उल्लिखित कालोनी / मौहल्लों को छोड़कर) |
| 4 | 1 | 5 | 3427 | चक सेवलाखर्द |
| 4 | 1 | 5 | 3428 | कारगी ग्राण्ट |
| 4 | 1 | 5 | 3429 | निरंजनपुर |
| 4 | 1 | 5 | 3430 | ब्राहमणवाला |
| 4 | 1 | 5 | 3431 | सत्यान मौहल्ला |
| 4 | 1 | 5 | 3432 | पुराना राजपुर |
| 4 | 1 | 5 | 3433 | राजपुर माफी |
| 4 | 1 | 5 | 3434 | प्रेमपुर माफी |
| 4 | 1 | 5 | 3435 | लोहारवाला |
| 4 | 1 | 5 | 3436 | गोपीवाला |
| 4 | 1 | 5 | 3437 | धरतावाला |
| 4 | 1 | 5 | 3438 | डुगालगांव |
| 4 | 1 | 5 | 3439 | थानीगांव |
| 4 | 1 | 5 | 3440 | गढी कैन्ट |
| 4 | 1 | 5 | 3441 | कौलागढ मय चक भूड |
| 4 | 1 | 5 | 3442 | चक शाहनगर |
| 4 | 1 | 5 | 3443 | शाहनगर |
| 4 | 1 | 5 | 3444 | शाहपुर सन्तौर |
| 4 | 1 | 5 | 3445 | इन्दरपुर |
| 4 | 1 | 5 | 3446 | केदारपुर |
| 4 | 1 | 5 | 3447 | चक डालनवाला |
| 4 | 1 | 5 | 3448 | धर्मपुर डांडा |
| 4 | 1 | 5 | 3449 | डिफेन्स कालोनी, शाहनगर |
| 4 | 1 | 5 | 3450 | एम0डी0डी0ए0 कालोनी अजबपुर |
| 4 | 1 | 5 | 3451 | एम0डी0डी0ए0 कालोनी केदारपुर |
| 4 | 1 | 5 | 3452 | अजबपुर चक-2 (चक अजबपुरकला) |
| 4 | 1 | 5 | 3453 | अजबपुर चक- 1 (चक अजबपुरकला) |
| 4 | 1 | 5 | 3454 | अजबपुर खुर्द |
| 4 | 1 | 5 | 3455 | ब्रहमावाला |
| 4 | 1 | 5 | 3456 | चिडोवाली |
| 4 | 1 | 5 | 3457 | धोरण खास |
| 4 | 1 | 5 | 3458 | कण्डोली (केन्द्रीयदून) |
| 4 | 1 | 5 | 3459 | हथड़ीगांव |
| 4 | 1 | 5 | 3460 | रांघडवाला |
| 4 | 1 | 5 | 3461 | बाजावाला |
| 4 | 1 | 5 | 3462 | माजरा |
| 4 | 1 | 5 | 3464 | धर्मपुर |
| 4 | 1 | 5 | 3465 | पंडितवाडी |
| 4 | 1 | 5 | 3466 | अजीत प्रसाद मार्ग |
| 4 | 1 | 5 | 3467 | आनन्द चौक |
| 4 | 1 | 5 | 3468 | रामेश्वर मौहल्ला |
| 4 | 1 | 5 | 3469 | अखाडा मौहल्ला |
| 4 | 1 | 5 | 3470 | मुस्लिम कालोनी |
| 4 | 1 | 5 | 3471 | खुडबुडा समस्त ब्लांक |
| 4 | 1 | 5 | 3472 | गुजराती मौहल्ला |
| 4 | 1 | 5 | 3473 | डांडीपुर मौहल्ला |
| 4 | 1 | 5 | 3474 | मन्नूगंज |
| 4 | 1 | 5 | 3475 | हकीकतराय नगर |
| 4 | 1 | 5 | 3476 | नेताजी मौहल्ला |
| 4 | 1 | 5 | 3477 | मालियाना मौहल्ला |
| 4 | 1 | 5 | 3478 | लक्खीबाग |
| 4 | 1 | 5 | 3479 | रामनगर |
| 4 | 1 | 5 | 3480 | सिंगल मण्डी |
| 4 | 1 | 5 | 3481 | रीठा मण्डी |
| 4 | 1 | 5 | 3482 | पथरीबाग |
| 4 | 1 | 5 | 3483 | भण्डारी बाग समस्त ब्लांक |
| 4 | 1 | 5 | 3484 | ट्रान्सपोर्ट नगर |
| 4 | 1 | 5 | 3485 | बाडीगार्ड |
| 4 | 1 | 5 | 3486 | टीचर्स कालोनी |
| 4 | 1 | 5 | 3487 | कुम्हारमण्डी |
| 4 | 1 | 5 | 3488 | गोविन्दगढ |
| 4 | 1 | 5 | 3489 | कौलागढ मय चक |
| 4 | 1 | 5 | 3491 | सैय्यद मौहल्ला |
| 4 | 1 | 5 | 3492 | हाथीबडकला |
| 4 | 1 | 5 | 3493 | विजय कालोनी |
| 4 | 1 | 5 | 3494 | चक सालावाला |
| 4 | 1 | 5 | 3495 | सालावाला |
| 4 | 1 | 5 | 3496 | पथरियापीर |
| 4 | 1 | 5 | 3497 | अहीर मण्डी |
| 4 | 1 | 5 | 3498 | परसोलीवाला मय चक नरसिह वाला |
| 4 | 1 | 5 | 3499 | डोभालवाला |
| 4 | 1 | 5 | 3500 | बकराल वाला |
| 4 | 1 | 5 | 3501 | डंगवाल मार्ग |
| 4 | 1 | 5 | 3502 | ओंकार रोड |
| 4 | 1 | 5 | 3503 | मित्रलोक कालोनी |
| 4 | 1 | 5 | 3504 | चुक्खुवाला |
| 4 | 1 | 5 | 3505 | चुक्खुवाला नई बस्ती |
| 4 | 1 | 5 | 3506 | इन्द्रा कालोनी चुक्खुवाला |
| 4 | 1 | 5 | 3507 | गढ़ी उद्दीवाला |
| 4 | 1 | 5 | 3508 | गढ़ी |
| 4 | 1 | 5 | 3509 | आराघर |
| 4 | 1 | 5 | 3510 | शास्त्रीनगर (समस्त लेन) |
| 4 | 1 | 5 | 3511 | नेहरू कालोनी (क्रमांक 4-D-15 में वर्णित क्षेत्र को छोड़कर) |
| 4 | 1 | 5 | 3512 | वीरगिरवाली |
| 4 | 1 | 5 | 3513 | घास मण्डी |
| 4 | 1 | 5 | 3514 | द्वारिका पुरी |
| 4 | 1 | 5 | 3515 | शक्ति एन्कलेव |
| 4 | 1 | 5 | 3516 | व्योमप्रस्थ एन्कलेव |
| 4 | 1 | 5 | 3517 | अलकनन्दा एन्कलेव |
| 4 | 1 | 5 | 3518 | मिलन विहार/ एन्कलेव |
| 4 | 1 | 5 | 3519 | काली मंदिर एन्कलेव |
| 4 | 1 | 5 | 3520 | पुष्पांजली एन्कलेव |
| 4 | 1 | 5 | 3521 | मेघा एन्कलेव |
| 4 | 1 | 5 | 3522 | नर्मदा एन्कलेव |
| 4 | 1 | 5 | 3523 | अंकित पुरम एन्कलेव |
| 4 | 1 | 5 | 3524 | संगम विहार |
| 4 | 1 | 5 | 3525 | नेहरूपुरम एन्कलेव |
| 4 | 1 | 5 | 3526 | विवेक विहार |
| 4 | 1 | 5 | 3527 | दुर्गा विहार |
| 4 | 1 | 5 | 3528 | कालिन्दी एन्कलेव |
| 4 | 1 | 5 | 3529 | उत्सव विहार |
| 4 | 1 | 5 | 3530 | वन विहार |
| 4 | 1 | 5 | 3531 | महारानी बाग |
| 4 | 1 | 5 | 3532 | हिल व्यू कालोनी |
| 4 | 1 | 5 | 3533 | दत्ता इन्कलेव |
| 4 | 1 | 5 | 3534 | इंजीनियर्स इन्कलेव (समस्त फेज कॅावली क्षेत्र) |
| 4 | 1 | 5 | 3535 | आशीर्वाद इन्कलेव |
| 4 | 1 | 5 | 3536 | मोहित नगर |
| 4 | 1 | 5 | 3537 | बसंत विहार |
| 4 | 1 | 5 | 3538 | इन्दिरा नगर कालोनी |
| 4 | 1 | 5 | 3539 | कलालोवाली गली |
| 4 | 1 | 5 | 3659 | लूनिया मौहल्ला |
| 4 | 1 | 5 | 3661 | नेहरू नगर |
| 4 | 1 | 5 | 3662 | गांधी ग्राम |
| 4 | 1 | 5 | 3667 | देहराखास |
| 4 | 1 | 5 | 3668 | लक्ष्मण चौक |
| 4 | 1 | 5 | 3670 | वेस्ट पटेल नगर |
| 4 | 1 | 5 | 3671 | ईस्ट पटेल नगर |
| 4 | 1 | 5 | 3672 | गुरू रोड |
| 4 | 1 | 5 | 3673 | सरस्वती सोनी मार्ग |
| 4 | 1 | 5 | 3674 | केशव रोड |
| 4 | 1 | 5 | 3675 | पार्क रोड |
| 4 | 1 | 5 | 3676 | विचारनन्द मार्ग |
| 4 | 1 | 5 | 3677 | पी0डी0 टंडन रोड |
| 4 | 1 | 5 | 3678 | नैशनल रोड |
| 4 | 1 | 5 | 3679 | मालवीय रोड |
| 4 | 1 | 5 | 3680 | महन्त रोड |
| 4 | 1 | 5 | 3681 | केशव विहार |
| 4 | 1 | 5 | 3682 | काली मंदिर एन्कलेव |
| 4 | 1 | 5 | 3683 | शाम्भबी लोक |
| 4 | 1 | 5 | 3684 | वसंत विहार एन्कलेव |
| 4 | 1 | 5 | 3685 | साई लोक |
| 4 | 1 | 5 | 3686 | अशोक विहार |
| 4 | 1 | 5 | 3688 | जनकपुरी एन्कलेव |
| 4 | 1 | 5 | 3689 | गढवाल कालोनी |
| 4 | 1 | 5 | 3691 | शिवालिकपुरम |
| 4 | 1 | 5 | 3692 | प्रियदर्शनी एन्कलेव |
| 4 | 1 | 5 | 3694 | ओल्ड सहस्त्रधारा रोड (अरविन्द मार्ग) |
| 4 | 1 | 5 | 3695 | मानसिंहवाला |
| 4 | 1 | 5 | 3696 | ओल्ड डालनवाला |
| 4 | 1 | 5 | 3697 | करनपुर बाजार |
| 4 | 1 | 5 | 3698 | आर्य नगर |
| 4 | 1 | 5 | 3699 | किशनपुर |
| 4 | 1 | 5 | 3700 | ढाकपट्टी |
| 4 | 1 | 5 | 3701 | जाखन |
| 4 | 1 | 5 | 3702 | राजपुर |
| 4 | 1 | 5 | 3703 | प्रतीतपुर संतौर |
| 4 | 1 | 5 | 3704 | आकाशदीप कालोनी |
| 4 | 1 | 5 | 3705 | विजयपार्क एक्सटेशन |
| 4 | 1 | 5 | 3706 | विजयपार्क |
| 4 | 1 | 5 | 3707 | यमुना कालोनी |
| 4 | 1 | 5 | 3708 | ईदगाह |
| 4 | 1 | 5 | 3709 | प्रकाश नगर |
| 4 | 1 | 5 | 3710 | राम विहार |
| 4 | 1 | 5 | 3711 | महेंद्र विहार |
| 4 | 1 | 5 | 3712 | आनन्द विहार |
| 4 | 1 | 5 | 3713 | नरेन्द्र विहार |
| 4 | 1 | 5 | 3714 | दीप लोक कालोनी |
| 4 | 1 | 5 | 3715 | चायबाग कौलागढ |
| 4 | 1 | 5 | 3717 | कौलागढ |
| 4 | 1 | 5 | 3718 | बल्लुपुर |
| 4 | 1 | 5 | 3721 | किशन नगर |
| 4 | 1 | 5 | 3722 | राजेन्द्र नगर |
| 4 | 1 | 5 | 3723 | एम0डी0डी0ए0 कालोनी चन्दर रोड |
| 4 | 1 | 5 | 3725 | डिफेन्स कालोनी चक शाहनगर |
| 4 | 1 | 5 | 3729 | उषा कालोनी |
| 4 | 1 | 5 | 3731 | अमन विहार |
| 4 | 1 | 5 | 3732 | गंगोत्री विहार |
| 4 | 1 | 5 | 3733 | सुमन विहार |
| 4 | 1 | 5 | 3735 | मन्दाकिनी विहार |
| 4 | 1 | 5 | 3736 | गोविन्द नगर |
| 4 | 1 | 5 | 3737 | मयूर विहार |
| 4 | 1 | 5 | 3741 | करनपुर खास (सहस्त्रधारा मार्ग पर स्थित ) |
| 4 | 1 | 5 | 3743 | केवल विहार |
| 4 | 1 | 5 | 3744 | नालापानी रोड |
| 4 | 1 | 5 | 3745 | नदी रिस्पना |
| 4 | 1 | 5 | 3747 | अधोईवाला |
| 4 | 1 | 5 | 3748 | बिष्णु रोड |
| 4 | 1 | 5 | 3749 | सेवक आश्रम रोड |
| 4 | 1 | 5 | 3750 | डी0एल0 रोड |
| 4 | 1 | 5 | 3751 | बंगाली लाईब्रेरी रोड |
| 4 | 1 | 5 | 3753 | करनपुर मौहल्ला |
| 4 | 1 | 5 | 3754 | प्रिन्सिपल रोड |
| 4 | 1 | 5 | 3755 | नेगी रोड |
| 4 | 1 | 5 | 3756 | सीमेंट रोड |
| 4 | 1 | 5 | 3757 | डी0ए0वी0 कालेज रोड |
| 4 | 1 | 5 | 3758 | बंगाली मौहल्ला |
| 4 | 1 | 5 | 3760 | एम0डी0डी0ए0 कालोनी, सहस्त्रधारा रोड |
| 4 | 1 | 5 | 3761 | उप्पल टावर |
| 4 | 1 | 5 | 3764 | राजेश्वर नगर |
| 4 | 1 | 5 | 3766 | नैशविला रोड पर काम्बोज स्वीट शॅाप से छोटी बिन्दाल नदी तक |
| 4 | 1 | 5 | 3767 | राजपुर रोड, करनपुरखास, एंव खेडा मानसिहवाला का वह क्षेत्र जो कि राजपुर रोड से 350 माटर दूरी के बाद स्थित है (अर्थात क्रमांक 1-A-में वणिर्त क्षेत्र को छोड़कर) |
| 4 | 1 | 5 | 3768 | एम0डी0डी0ए0 कालोनी लोहियापुरम |
| 4 | 1 | 5 | 3769 | सन्त विनोबा भावे मार्ग (अम्बर पैलेस से बाद) |
| 4 | 1 | 5 | 3770 | सन्त विनोबा भावे मार्ग (अम्बर पैलेस से पूर्व) |
| 4 | 1 | 5 | 3771 | त्यागी रोड |
| 4 | 1 | 5 | 3772 | चन्दर नगर |
| 4 | 1 | 5 | 3773 | सिक्का ग्रीन |
| 4 | 1 | 5 | 3774 | रिवर वैली |
| 4 | 1 | 5 | 3775 | ओर्किड / ओर्चिड पार्क |
| 4 | 1 | 5 | 3776 | विहस्प्रिंग विलोज |
| 4 | 1 | 5 | 3777 | पैसिफिक गोल्फ इस्टेट |
| 4 | 1 | 5 | 3778 | पनाष वैली |
| 4 | 1 | 5 | 4253 | रैस्ट कैम्प |
| 4 | 1 | 5 | 6286 | शिव लोक कॉलोनी |
| 4 | 1 | 5 | 6287 | बद्रीश कॉलोनी |
| 4 | 1 | 5 | 3780 | धर्मपुर सब्जी मण्डी चौराहे से लक्ष्मी रोड के चौराहे तक सड़क से 100 माटर दूरी तक (नेहरू कालोनी क्षेत्र की ओर पड़ने वाला क्षेत्र) |
| 4 | 1 | 5 | 3781 | हरिद्वार रोड पर रिस्पना पुल तिराहे से विधान सभा होते हुये रेलवे फाटक तक |
| 4 | 1 | 5 | 3782 | पो0ओ0 रोड (सुभाष नगर क्षेत्र) |
| 4 | 1 | 5 | 3783 | टर्नर रोड (क्लेमेनटाउन क्षेत्र) |
| 4 | 1 | 5 | 3784 | कृष्णा विहार |
| 4 | 1 | 5 | 3785 | आनन्द विहार |
| 4 | 1 | 5 | 3786 | इंजीनियर्स इन्कलेव जाखन क्षेत्र |
| 4 | 1 | 5 | 3787 | दून विहार |
| 4 | 1 | 5 | 3788 | अंसल ग्रीन वैली |
| 4 | 1 | 5 | 3789 | भागीरथीपुरम - जाखन क्षेत्र |
| 4 | 1 | 5 | 3790 | दिलाराम बाजार |
| 4 | 1 | 5 | 3791 | ओल्ड सर्वे रोड |
| 4 | 1 | 5 | 3792 | विदेश संचार कालोनी |
| 4 | 1 | 5 | 3793 | आयकर कालोनी |
| 4 | 1 | 5 | 3794 | नेहरू कालोनी (सी0 ब्लांक) |
| 4 | 1 | 5 | 3795 | इन्द्रा मार्केट |
| 4 | 1 | 5 | 3796 | कचहरी रोड |
| 4 | 1 | 5 | 3797 | नरदेव शास्त्री मार्ग |
| 4 | 1 | 5 | 3798 | पंत रोड |
| 4 | 1 | 5 | 3799 | कॅान्वेन्ट रोड |
| 4 | 1 | 5 | 3800 | न्यू रोड |
| 4 | 1 | 5 | 3801 | पटेल रोड |
| 4 | 1 | 5 | 3802 | अंसारी रोड |
| 4 | 1 | 5 | 3803 | तिलक रोड |
| 4 | 1 | 5 | 3805 | इनद्रापुरम |
| 4 | 1 | 5 | 3806 | चन्द्रलोक कालोनी |
| 4 | 1 | 5 | 3807 | साकेत कालोनी |
| 4 | 1 | 5 | 3808 | इन्द्रबाबा मार्ग |
| 4 | 1 | 5 | 3809 | कश्मीरी कालोनी |
| 4 | 1 | 5 | 3810 | कोचर कालोनी |
| 4 | 1 | 5 | 3811 | जज कालोनी |
| 4 | 1 | 5 | 3812 | डिक रोड |
| 4 | 1 | 5 | 3813 | उग्र रोड |
| 4 | 1 | 5 | 3814 | नेमी रोड |
| 4 | 1 | 5 | 3815 | चन्दर रोड |
| 4 | 1 | 5 | 3816 | लक्ष्मी रोड |
| 4 | 1 | 5 | 3817 | कर्जन रोड |
| 4 | 1 | 5 | 3818 | नेहरू रोड |
| 4 | 1 | 5 | 3819 | सकुर्लर रोड |
| 4 | 1 | 5 | 3820 | तेग बहादुर रोड |
| 4 | 1 | 5 | 3821 | बलवीर रोड |
| 4 | 1 | 5 | 3822 | मोहिनी रोड |
| 4 | 1 | 5 | 3823 | प्रीतम रोड |
| 4 | 1 | 5 | 3824 | इन्दर रोड |
| 4 | 1 | 5 | 3825 | म्यूनिस्पिल रोड |
| 4 | 1 | 5 | 3826 | रेसकोर्स |
| 4 | 1 | 5 | 3827 | डालनवाला क्षेत्र में पड़नें वाले समस्त सड़के तथा मौजा धर्मपुर के अग्रवाल बेकर्स- सब्जी मण्डी से पुलियां नं0- 6 तक की सड़क के उत्तर पूर्व का डालनवाला में पड़ने वाला समस्त क्षेत्र |
| 4 | 1 | 5 | 3828 | कालीदास रोड |
| 4 | 1 | 5 | 3829 | न्यू कैन्ट रोड पर कैन्ट सीमा से आगे गढी डाकरा बाजार तक |
| 4 | 1 | 5 | 3830 | नैशविला रोड पर राजपुर रोड से काम्बोज स्वीट शॉप तक |
| 4 | 1 | 5 | 3831 | चकराता रोड पर चुक्खुवाला मार्ग, नारी शिल्प मन्दिर मार्ग, रामपुर मण्डी रोड (क्रमांक-8-एच-1 में वर्णित क्षेत्र को छोड़कर) |
| 4 | 1 | 5 | 3832 | लक्ष्मी पार्क जैन कासोनी |
| 4 | 1 | 5 | 3833 | व्हिस्पिरिंग विलोज |
| 4 | 1 | 5 | 3834 | शिवम विहार |
| 4 | 1 | 5 | 3835 | शिप्रा कॉलोनी |
| 4 | 1 | 5 | 3836 | फ्रेंड्स कॉलोनी |
| 4 | 1 | 5 | 3837 | प्लेजंट वैली |
| 4 | 1 | 5 | 3838 | एकता कॉलोनी (अकेटा एवेन्यू) |
| 4 | 1 | 5 | 3839 | एकता कॉलोनी (अकेटा एवेन्यू) |
| 4 | 1 | 5 | 3840 | रामलीला बाजार |
| 4 | 1 | 5 | 3841 | घोसी गली |
| 4 | 1 | 5 | 3842 | बाबूगंज |
| 4 | 1 | 5 | 3843 | झण्डा मौहल्ला/बाजार |
| 4 | 1 | 5 | 3844 | हनुमान चौक |
| 4 | 1 | 5 | 3845 | मोती बाजार |
| 4 | 1 | 5 | 3846 | सरनीमल बाजार |
| 4 | 1 | 5 | 3847 | डिस्पेन्सरी रोड |
| 4 | 1 | 5 | 3848 | अजमल खॉ रोड |
| 4 | 1 | 5 | 3849 | राजा रोड |
| 4 | 1 | 5 | 3850 | दर्शनी गेट/आढ़त बाजार (क्रमांक-8-एच -4/5 में वर्णित क्षेत्र को छोड़कर) |
| 4 | 1 | 5 | 3851 | पीपल मण्डी (क्रमांक-8-एच -4 में वर्णित क्षेत्र को छोड़कर) |
| 4 | 1 | 5 | 3852 | धामावाला (क्रमांक-8-एच -4 में वर्णित क्षेत्र को छोड़कर) |
| 4 | 1 | 5 | 3853 | क्रास रोड |
| 4 | 1 | 5 | 3854 | न्यू सर्वे रोड |
| 4 | 1 | 5 | 3855 | जबर क्षेत्र से आगे नगर पालिका परिषद मसूरी सीमा में दोनों ओर की सम्पत्तियों हेतु । |
| 4 | 1 | 5 | 3856 | सिस्टर बाजार से आगे जबर खेत का क्षेत्र मंलिगार गेट से आगे मसूरी-टिहरी रोड पर जवर खेत का क्षेत्र (कम्युनिटी हास्पिटल, बुड स्टाक स्कूल, बुड स्टाक धोबीघाट, के साथ ही इस मार्ग से सम्पत्तियों के पहुच तक के लिए तथा मसूरी-चम्बा टिहरी बाई पास मार्ग की दोनों ओर की सम्पत्तियों हेतु) |
| 4 | 1 | 5 | 3857 | 350 मीटर (मसूरी चकराता रोड) कैम्पटी रोड के पश्चात भिलाडू के सम्पूर्ण क्षेत्र नगर पालिका परिषद, मसूरी सीमा तक |
| 4 | 1 | 5 | 3858 | लण्ढोर अनुपम होटल से नीचे भण्डारी निवास, रावत हाऊस के पश्चात खच्चरखाना लक्ष्मणपुरी क्षेत्र |
| 4 | 1 | 5 | 3859 | गांधी द्वारा के किंकेग मोटर मार्ग से 350 मीटर दूरी के पश्चात तथा देहरादून की ओर तथा आई.टी.बी.पी. का क्षेत्र तथा कार्टमेकेन्जी रोड नगर देवता मन्दिर का क्षेत्र गांधी द्वारा तथा उक्त मोटर मार्ग के दोनों ओर की भूमि (थापर टेरस, जय निवास, हुसैन गंज , विल्ला फॉल आदि का सम्पूर्ण क्षेत्र) |
| 4 | 1 | 5 | 3860 | अनुपम होटल से मंलिगार क्षेत्र चौक तक का पूरा (कैन्ट क्षेत्र) |
| 4 | 1 | 5 | 3861 | चार्लीविली गेट के नीचे हैप्पी वैली, के साथ ही पोलोग्राउण्ड का सम्पूर्ण क्षेत्र तथा देवदार रोड होते हुए तिब्बतन होम फाउण्डेसन के साथ ही इस क्षेत्र में नगर पालिका परिषद, मसूरी सीमा तक |
| 4 | 1 | 5 | 3862 | हाथीपांव व आसपास के क्षेत्र जहां पर खनन कार्य किया जाता था, पार्क एस्टेट, क्लाउड एण्ड जार्ज एवरेस्ट का सम्पूर्ण क्षेत्र ग्राम दुधली तक नगर पालिका परिषद मसूरी सीमान्तर्गत) |
| 4 | 1 | 5 | 3863 | पिक्चर पैलेस से लण्ढौर बाजार का पूरा क्षेत्र अनुपम होटल तक (बूचडखाना, अनुपम चौक गुरूद्वारा रोड से भण्डारी निवास, रावत हाऊस तक) |
| 4 | 1 | 5 | 3864 | मसूरी इंटरनेशनल स्कूल सीमा समाप्ति पर उससे आगे कैम्पटी फाल रोड (मसूरी से चकराता) पर नगर पालिका सीमा मसूरी तक के दोनों ओर के भाग के लिए (श्रीनगर इस्टेट) |
| 4 | 1 | 5 | 3865 | मंलिगार होटल से ऊपर का क्षेत्र 4 दुकान होकर सिस्टर बाजार से दूरदर्शन केन्द्र तक का क्षेत्र चार दुकान से र्सीक वाली कोठी तक का क्षेत्र, र्सीक वाली कोठी से लाल टिब्बा के पिछे की ओर की सड़क का पूरा क्षेत्र |
| 4 | 1 | 5 | 3866 | कचहरी के उपर एवोलोन गनहिल रोड को जोड़ने वाला तिराहा के पाश्चात का पूरा क्षेत्र सेन्ट मेरी अस्पताल व साहू जैन इस्टेट व पोंदार हाउस के पश्चात का सम्पूर्ण ऊपरी भाग |
| 4 | 1 | 5 | 3867 | घंघटार लण्ढौर से साउथ रोड होकर सिविल अस्पताल, वाईन वर्ग ऐलन स्कूल एवं बाला हिसार क्षेत्र (घन्टाघर से बालाहिसार तक जिसे पुराना राजपुर रोड से भी जाना जाता है) |
| 4 | 1 | 5 | 3869 | जीरो पॉइंट से आगे हरनाम सिंह रोड पर वेवरली कान्वेन्ट स्कूल (काला स्कूल गेट) से पूर्व का सम्पूर्ण क्षेत्र |
| 4 | 1 | 5 | 3870 | चार्लीविला गेट से डिक रोड होकर कम्पनी बाग, लौगी गार्डन, होलो ओक का सम्पूर्ण क्षेत्र |
| 4 | 1 | 5 | 3871 | नगर पालिका परिषद, मसूरी में सम्मिलित ग्राम मिसरासपट्टी का क्षेत्र |
| 4 | 1 | 5 | 3872 | भट्टा गॉव नगर पालिका सीमा के अन्दर का भाग के लिए मार्ग के दोनों ओर के भाग (देहरादून- मसूरी मार्ग हेतु निर्धारित 350 मीटर दूरी को छोड़ कर) |
| 4 | 1 | 5 | 3873 | होटल सेवेन ओक्स से आगे कैमल्स बैक रोड पर बहुगुणा पार्क से पूर्व तक (मार्ग के दोनों ओर पहुच सम्पत्तियों तक के लिए |
| 4 | 1 | 5 | 3874 | कम्पनी बाग लौगी गार्डेन के पश्चात हाथी पांव चौक तक |
| 4 | 1 | 5 | 3875 | घोबीघाट मसूरी झील के पश्चात ग्राम भट्टा तक नगर पालिका परिषद मसूरी सीमा में (देहरादून- मसूरी मार्ग हेतु निर्धारित 350 मीटर दूरी को छोड़ कर) |
| 4 | 1 | 5 | 3876 | बड़े मोड के अंतिम छोर के पाश्चात से किंकेग मोटर मार्ग पर दोनों ओर 350 मीटर की परिधि में किंकेग से नीचे घनानन्द रा.इ.का. के पश्चात देहरादून की ओर धोबीघाट का क्षेत्र नगर पालिका परिषद, मसूरी सीमा अन्तर्गत कीलिफ़ हाल इस्टेट का सम्पूर्ण क्षेत्र) |
| 4 | 1 | 5 | 3877 | राधा भवन इस्टेट, मुख्य भाग से आगे की ओर गुरूनानक स्कूल से सड़क से ऊपरी भाग न्यू सर्कुलर रोड से मानव भारती संगीला एस्टेट क्षेत्र कम्पनी बाग उपरी क्षेत्र वेवरली कान्वेंट स्कूल (काला स्कूल) गेट तक |
| 4 | 1 | 5 | 3878 | लाइब्रेरी चौक से होटल क्लासिक तथा लाइब्रेरी बस स्टैन्ड से नीचे की ओर 350 मीटर दूरी के पश्चात मुख्य मेनर हाउस भवन तथा सर्कुलर रोड एवं सप्रिंग रोड मोतीलाल नहरू रोड से लेकर सम्पूर्ण चमर खण्ड का क्षेत्र, मैकनेन पम्प क्षेत्र, ऐस्टल इस्टेट का सम्पूर्ण क्षेत्र, आई0टी0बी0पी0 गेट से पहले तक |
| 4 | 1 | 5 | 3879 | चकराता रोड पर सा0नि0वि0 निरीक्षण भवन मसूरी के क्षेत्र से आगे चकराता टोल में मसूरी इंटरनेशल स्कूल तक पोलो ग्राउन्ड क्षेत्र तक 100 मीटर रोड क्षेत्र की ओर(श्रीनगर इस्टेट) |
| 4 | 1 | 5 | 3880 | झडीपानी क्षेत्र (ओकग्रोव स्कूल का क्षेत्र, झडीपानी टोल के साथ ही राजपुर पुराना टोल नगर पालिका परिषद, मसूरी सीमान्तर्गत) |
| 4 | 1 | 5 | 3881 | बार्लोगंज क्षेत्र (जेपी बैड से बार्लोगंज मार्ग की सम्पूर्ण सम्पत्तियों हेतु, बालाहिसार मार्ग पर बालाहिसार के पश्चात सम्पूर्ण मैरीविल एस्टेट, भट्टा गॉव नगर पालिका सीमा तक, देहरादून-मसूरी मार्ग हेतु निर्धारित 350 मीटर दूरी को छोड़कर सम्पूर्ण बार्लोगंज-झडीपानी मार्ग पर स्थित भूमि भवन जो नगर पालिका परिषद मसूरी की सीमा के अन्तर्गत हो) |
| 4 | 1 | 5 | 3882 | लाइब्रेरी चौक से आगे मोतीलाल नहरू मार्ग पर दोनो ओर पहुच मार्ग (काला स्कूल) वेवरली कान्वेंट स्कूल तक का क्षेत्र । |
| 4 | 1 | 5 | 3883 | मसूरी मार्डन स्कूल तिराहे से राधा भवन मसूरी मुख्य भवन से होते हुए मान काटेज, बडौदा हाऊस चण्डालगढी क्षेत्र एवं विन्सेट हिल का सम्पूर्ण ऊपरी क्षेत्र |
| 4 | 1 | 5 | 6288 | पिक्चरपैलेस के ऊपर नगर पालिका परिषद कार्यालय मसूरी, हिमालय क्लब नान पारा हो कर आर एन भार्गव इंटर कॉलेज मार्ग होते हुये वाइन वर्ग एलेन स्कूल प्राइमरी सेक्शन तक तथा घंटा घर से ओकबुश रोड होते हुये |
| 4 | 1 | 5 | 3884 | इन्द्राभवन से आगे चार्लीविली गेट तक (साथ ही इस मार्ग से सम्पत्तियों तक की पहुच हेतु) |
| 4 | 1 | 5 | 3885 | लाईब्रेरी चौक के बाद आगे इन्द्रा भवन तक (होटल ओएसेज मार्ग, गाडीखाना, सेवाय होटल स्टाफ क्वाटर्स का भाग, इन्दिरा भवन आदि के साथ ही इस मार्ग से सम्पत्तियों तक की पहुच हेतु) |
| 4 | 1 | 5 | 3886 | माल रोड पर रोजलीन होटल से होते हुए कैमल बैक रोड पर बहुगुणा पार्क तक का भाग (प्राईमरी पाठशाला लाईब्रेरी भिलाडू मार्ग पर मित्तल हाउस व धर निवास आदि तक का अन्तिम भाग ) |
| 4 | 1 | 5 | 3887 | लाइब्रेरी चौक से संपूर्ण माल रोड कुलड़ी बाज़ार, जफर हाल , स्टुडियो लौज़, तिलक मार्ग , बारह कैंची पर डॉक्टर ठुकराल के आगे वाले किंक्रग की ओर वाले बंद तक सड़क के दोनों ओर 50 मीटर तक कैमल बैंक रोड पर होटल नन्द विला एवं होटल सोलिटेयर प्लाज़ा तक (दुग्गल विला का गुनसोला निवास दुग्गल विला कॉटेज, रोज़लीन होटल से कालाकाकर हाउस एवम चर्च रोड पर पोदार हाउस आदि तक का भाग, कचहरी रोड पर एवलॉन-गनहिल मार्ग को जोड़ने वाला तिराहा, हैकमन्स होटल मे शगुन पैलेस, घोडा लाइन, हम्पटन कोर्ट, क्रेग कालिज आदि के साथ ही एस्टेला कालिज, लॉलर बैक, तिब्बतन मार्केट मार्ग पर इन्दर निवास पदमनी आदि के साथ ही वासू सिनेमा बिल्डिंग आदि) |
| 4 | 1 | 5 | 3991 | डोईवाला टाउन एरिया का शेष क्षेत्र0 |
| 4 | 1 | 5 | 3992 | डोईवाला चौक से शुगर मिल प्रेम नगर बाज़ार चादमारी चौक तक |
| 4 | 1 | 5 | 3993 | डोईवाला चौक से रेल्वे स्टेशन रोड पर रेल्वे स्टेशन तक |
| 4 | 1 | 5 | 3994 | डोईवाला चौक से देहारादून रोड पर टाउन एरिया सीमा समाप्ती तक |
| 4 | 1 | 5 | 3995 | डोईवाला चौक से ऋषिकेश रोड पर सौंग नदी तक |
| 4 | 1 | 5 | 3996 | मारखम ग्रन्ट- । |
| 4 | 1 | 5 | 3997 | मिस्सरवाला खुर्द |
| 4 | 1 | 5 | 3999 | हंसूवाला |
| 4 | 1 | 5 | 4000 | डोईवाला |
| 4 | 1 | 5 | 4001 | घिसरपड़ी |
| 4 | 1 | 5 | 4002 | मिस्सरवाला कलां |
| 4 | 1 | 5 | 4003 | लच्छीवाला |
| 4 | 1 | 5 | 4004 | डैशवाला |
| 4 | 1 | 5 | 4005 | गुजरमी |
| 4 | 1 | 5 | 4006 | जगातखाना, जगातखाना करनपुर |
| 4 | 1 | 5 | 4007 | डोमगांव |
| 4 | 1 | 5 | 4008 | भंडारीवाला मयचक |
| 4 | 1 | 5 | 4009 | मंगलूवाला |
| 4 | 1 | 5 | 6289 | भण्डारी वाला |
| 4 | 1 | 5 | 4010 | विजयपुर गोपीवाला |
| 4 | 1 | 5 | 4011 | लाडपुर |
| 4 | 1 | 5 | 4012 | गुजराडा मानसिंह |
| 4 | 1 | 5 | 4013 | आरकेडिया ग्रांट |
| 4 | 1 | 5 | 4014 | नवादा |
| 4 | 1 | 5 | 4015 | नथुवावाला |
| 4 | 1 | 5 | 4016 | चंद्रबनी ग्रांट |
| 4 | 1 | 5 | 4017 | चकतुनवाला |
| 4 | 1 | 5 | 4018 | चकरायपुर |
| 4 | 1 | 5 | 4019 | दानियों का डांडा |
| 4 | 1 | 5 | 4020 | सेवलाखुर्द |
| 4 | 1 | 5 | 4021 | सुन्दरवाला |
| 4 | 1 | 5 | 4022 | सौन्धोवाली ,सौन्धोवाली धौरन |
| 4 | 1 | 5 | 4023 | रायपुर |
| 4 | 1 | 5 | 4024 | हर्रावाला |
| 4 | 1 | 5 | 4025 | हरभजवाला |
| 4 | 1 | 5 | 4026 | हरबंश वाला |
| 4 | 1 | 5 | 4027 | हरिपुर |
| 4 | 1 | 5 | 4028 | सिनौला |
| 4 | 1 | 5 | 4029 | पित्थूवाला |
| 4 | 1 | 5 | 4030 | मियांवाला |
| 4 | 1 | 5 | 4031 | किरसाली पछवादून |
| 4 | 1 | 5 | 4032 | मेहुवाला माफी |
| 4 | 1 | 5 | 4033 | माजरी माफी |
| 4 | 1 | 5 | 4034 | मोहकमपुर कलां |
| 4 | 1 | 5 | 4035 | मोहकमपुर खुर्द |
| 4 | 1 | 5 | 4036 | मोहब्बेवाला |
| 4 | 1 | 5 | 4037 | मक्कावाला |
| 4 | 1 | 5 | 4038 | कुवांवाला |
| 4 | 1 | 5 | 4039 | कुठाल गांव |
| 4 | 1 | 5 | 4040 | आसारोडी |
| 4 | 1 | 5 | 4041 | चन्द्रबनी |
| 4 | 1 | 5 | 4042 | चन्द्रबनी खालसा |
| 4 | 1 | 5 | 4043 | विजयपुर हाथीबड़कला |
| 4 | 1 | 5 | 4044 | मिटठी भेडी |
| 4 | 1 | 5 | 4045 | मरेठा |
| 4 | 1 | 5 | 4046 | कुल्हान करनपुर |
| 4 | 1 | 5 | 4047 | कुल्हान मानसिंह |
| 4 | 1 | 5 | 4048 | सोन्धोवाली मानसिंह |
| 4 | 1 | 5 | 4049 | नागल हटनाला |
| 4 | 1 | 5 | 4050 | हटनाल गांव |
| 4 | 1 | 5 | 4051 | आमवाला करनपुर |
| 4 | 1 | 5 | 4052 | कालागांव |
| 4 | 1 | 5 | 4053 | चांलग |
| 4 | 1 | 5 | 4054 | आमवाला उपरला |
| 4 | 1 | 5 | 4055 | आमवाला मझला |
| 4 | 1 | 5 | 4056 | किरसाली परवादून |
| 4 | 1 | 5 | 4057 | तरलानांगल |
| 4 | 1 | 5 | 4058 | ननूरखेडा |
| 4 | 1 | 5 | 4059 | बालावाला |
| 4 | 1 | 5 | 4060 | बगराल गांव |
| 4 | 1 | 5 | 6290 | नकरौंदा |
| 4 | 1 | 5 | 6291 | जोहड़ी |
| 4 | 1 | 5 | 6292 | मोथरोंवाला |
| 4 | 1 | 5 | 4061 | भंडारगाँव |
| 4 | 1 | 5 | 4062 | खुरावा |
| 4 | 1 | 5 | 4063 | खाला गांव |
| 4 | 1 | 5 | 4064 | आमवाला तरला |
| 4 | 1 | 5 | 4065 | नत्थनपुर |
| 4 | 1 | 5 | 4066 | डांडा नूरीवाला |
| 4 | 1 | 5 | 4067 | डांडा लखौण्ड |
| 4 | 1 | 5 | 4068 | डांडा खुदानेवाला |
| 4 | 1 | 5 | 4069 | डांडा धोरण |
| 4 | 1 | 5 | 4070 | सेवलाकलां |
| 4 | 1 | 5 | 4071 | भारुवालाग्रान्ट |
| 4 | 1 | 5 | 4072 | मासली |
| S.No. | As a | <Role> | I want | <What> | so that | <Why> |
|---|---|---|---|---|---|---|
| 1. | As a | Employee orCitizen | I want | Search a property by unique property ID | so that | I can create an application for bifurcation of property. |
| 2. | As a | Employee orCitizen | I want | Search a property by owner’s mobile no. | So that | I can create an application for bifurcation of property. |
| 3. | As a | Employee or Citizen | I want | Search a property by owner’s name or by door no. | So that | I can create an application for bifurcation of property. |
| 3. | As a | Employee orCitizen | I want | Initiate new application for property bifurcation | So that | I can create an application to bifurcate a property. |
| 4. | As a | Citizen | I want | Notification for my property bifurcation application | So that | I can keep track of my application (notification sent will be according to workflow) |
| 5. | As a | Employee (Workflow) | I want | Bifurcation application in my inbox | So that | I can take appropriate action on the application. |
| 6. | As a | Employee | I want | Search application | So that | I can search and see the application details. |
| 7. | As a | Citizen | I want | My Applications | So that | I can see the application details and keep track of the application. |
| Field Name | Data Type | Is Mandatory? | Description |
|---|---|---|---|
| Property Address | |||
| Pincode | Display | Yes | Pincode of area property is located. |
| City | Display | Yes | City name of the property. |
| Locality/ Mohalla | Display | Yes | Locality or mohalla name property is located. |
| Street Name | Display | Yes | Street name property is located. |
| Door No./ House No. | Display | Yes | House or door no. of the property. |
| Ownership Details | |||
| Ownership Type | Display | Yes | Display of ownership type. |
| Institution Name | Display | Yes | It is applicable for the ownership type institution. |
| Institution Type | Display | Yes | It is applicable for the ownership type institution. |
| Name | Display | Yes | Name of the owner of property or the authorized person in case of institutional property. |
| Guardian Name | Display | Yes | Name of guardian and applicable for single and multiple ownership type only. |
| Gender | Display | Yes | Gender of owner/authorized person of the property. |
| Landline No. | Display | Yes | Office landline no. in case of institutional ownership. |
| Mobile No. | Display | Yes | Mobile no. of the owner/ authorized person. |
| Designation | Display | Yes | Designation of the authorized person |
| Display | Yes | Email address of owner/ authorized person. | |
| Corresponding Address | Display | Yes | Corresponding address of the owner/ authorized person. |
| Assessment Details | |||
| Property Type | Drop-down | Yes | Type of property |
| Property Usage | Drop-down | Yes | Usage of property, residential, non-residential, or mixed. |
| Plot Size (In Sq. Ft.) | Textbox | Yes | Total area of land in square feet on which the property is constructed. |
| Unit 1 | |||
| Floor No. | Drop-down | Yes | Floor no. unit is located. |
| Usage | Drop-down | Yes | Usage of unit, residential/ non-residential. |
| Sub-usage | Drop-down | Yes | Sub-usage of unit, mandatory in case of non-residential usage. |
| Occupancy | Drop-down | Yes | The type of occupancy of property. |
| Annual Rent | Textbox | Yes | Annual rent in INR, in case property is rented out. |
| Built-up Area | Textbox | Yes | Built-up area of the unit in square feet. |
| Child Propertie(s) | |||
| Add Child Property | Icon | Yes | To add child property. |
| Property 1 | |||
| Property ID | Display | Yes | Unique Property ID. |
| Door/ House No. | Display | Yes | House no./ Door no. of newly created child property. |
| Property Type | Display | Yes | Type of property of child property. |
| Property Usage | Display | Yes | Usage of child property, residential, non-residential, or mixed. |
| Plot Size (In Sq. Ft.) | Display | Yes | Total area of land in square feet on which the child property is constructed. |
| No. of floors | Display | Yes | No. of floors child property is having. |
| Total Builtup Area (Sq. Ft.) | Display | Total built-up area of the child property across all the floors. | |
| Property 2 | |||
| Property ID | Display | Yes | Unique Property ID. |
| Door/ House No. | Display | Yes | House no./ Door no. of newly created child property. |
| Property Type | Display | Yes | Type of property of child property. |
| Property Usage | Display | Yes | Usage of child property, residential, non-residential, or mixed. |
| Plot Size (In Sq. Ft.) | Display | Yes | Total area of land in square feet on which the child property is constructed. |
| No. of floors | Display | Yes | No. of floors child property is having. |
| Total Builtup Area (Sq. Ft.) | Display | Total built-up area of the child property across all the floors. | |
| View Property Details/ Remove Property | Hyperlink | Yes | To view the completed property details/ remove the added property. |
| Documents | File Picker | Yes | The documents required to process the request. |
| Timelines | Workflow | Yes | Display of workflow steps completed. |
| Field Name | Data Type | Is Mandatory? | Description |
|---|---|---|---|
| Property ID | Display | Yes | Unique Property ID. |
| Door/ House No. | Display | Yes | Full address of property. |
| Assessment Details | |||
| Property Type | Drop-down | Yes | Type of property |
| Property Usage | Drop-down | Yes | Usage of property, residential, non-residential, or mixed. |
| Plot Size (In Sq. Ft.) | Textbox | Yes | Total area of land in square feet on which the property is constructed. |
| Unit 1 | |||
| Floor No. | Drop-down | Yes | Floor no. unit is located. |
| Usage | Drop-down | Yes | Usage of unit, residential/ non-residential. |
| Sub-usage | Drop-down | Yes | Sub-usage of unit, mandatory in case of non-residential usage. |
| Occupancy | Drop-down | Yes | The type of occupancy of property. |
| Annual Rent | Textbox | Yes | Annual rent in INR, in case property is rented out. |
| Built-up Area | Textbox | Yes | Built-up area of the unit in square feet. |
| S.No. | Action | Role | From State | To State |
|---|---|---|---|---|
| 1 | Initiate Application | Citizen/ Counter Employee | Initiated | |
| 2 | Submit Application | Citizen/ Counter Employee | Initiated | Pending for document verification |
| 3 | Verify and Forward | Document Verifier | Pending for document verification | Pending for field inspection |
| 4 | Verify and Forward | Field Inspector | Pending for field inspection | Pending approval for bifurcation |
| 5 | Send Back | Document Verifier | Pending for document verification | Pending for citizen action |
| 6 | Send Back | Field Inspector | Pending for Field inspection | Pending for document verification |
| 7 | Send Back | Approver | Pending approval for bifurcation | Pending for field inspection |
| 8 | Send Back To Citizen | <roles having access> | <Current Status> | Pending for citizen action |
| 9 | Re-submit | Citizen/ Counter Employee | Pending for citizen action | Pending for document verification |
| 10 | Re-submit | Document Verifier | Pending for document verification | Pending for field inspection |
| 11 | Re-submit | Field Inspector | Pending for field inspection | Pending approval for bifurcation |
| 12 | Approve | Approver | Pending approval for bifurcation | Approved |
| 13 | Reject | <roles having access> | <Current Status> | Rejected |
| My properties and selecting a property for bifurcation. The property should not be inactive or in the workflow. | ||
| Parent property address and ownership details are displayed. | ||
Parent property assessment details are edited and the flow of screens is according to the property type of the parent property.
| ||
| Property Type: Flat/ Part of building | ||
| Property Type: Vacant Land | ||
Child property (ies) is/are added to the application. To add the child property, the flow of property registration is used with the below-given limitations.
| ||
| Documents and application summary page are displayed. |
Log in to the system.
Click on the Register Property option on the home page.
| The screen displays the **Required Documents** list. Note the list of documents valid for address, identity, registration, usage, special category, and occupancy proofs. | |Enter the Ground Floor Details like Unit Usage Type, Occupancy, and Total Super Built-Up Area (sq ft).
Click on the Add One More Unit option to add G+1 or G+2 and additional floor details.
| |