1 of 100

v2.5

DIGIT

The Digital Governance Platform

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

Open Source - DIGIT is Open Source and has been built using the best in class Open Source technology stacks powering the most advanced companies in the world. DIGIT is able to provide the lowest total cost of ownership and helps ensure that governments retain strategic control of their systems and data.
Mobile-Enabled - DIGIT has adopted a mobile-first approach, with robust mobile applications enabling citizens to easily access government services through their phones. Government officials and field workers are also empowered with mobile applications that enable them to deliver 24×7 governance with ease.
Real-time Dashboards - DIGIT’s real-time dashboards provide governments with actionable insights on demand. Administrators and department heads are empowered with verified data that enables them to manage their work and budgets better. Field level employee reports enable effective performance management and ensure efficient usage of government resources.

Our Core Principles

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

Access DIGIT

Explore DIGIT platform

Server Maintenance scheduled from 7th Feb 2022 10 AM to 14th Feb 2022 10 AM. The Demo Instance is temporarily unavailable due to system upgrades & maintenance.

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

Steps To Access DIGIT

You can access DIGIT as a Citizen or an Employee.

****Click here to access DIGIT as a Citizen. Follow the steps below to register as a Citizen user.

Enter your registered mobile number and OTP to log in to the DIGIT platform.
Select City as City B from the drop-down list.

You are now registered as a Citizen user.

Click here to access DIGIT as an Employee.

First time users - click here to generate your role-based credentials.
Use the credentials generated and sent to your registered email ID to log in as an employee.
Select City as City B.

Use the role-based credentials to explore the features and functions specific to the given role.

Demo Scripts

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

Feedback

We would love to get your feedback and suggestions on the Access DIGIT experience to help us build on this!

****Click here to enter your feedback.

For any further queries or feedback please write to us at partner@egov.org.in

Click here to fill in and submit your request for a personalised walkthrough demo of the platform.

Architecture

DIGIT Infra and architecture details

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

Key Architecture Highlights

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

A big software or system can be broken down into multiple small components or services. These components can be designed, developed & deployed independently without compromising the integrity of the application.
Parallelism in development: Microservices architectures are mainly business-centric.
MicroServices have smart endpoints that process info and apply logic. They receive requests, process them, and generate a response accordingly.
Decentralized control between teams, so that its developers strive to produce useful tools that can then be used by others to solve the same problems.

MicroServices architecture allows its neighbouring services to function while it bows out of service. This architecture also scales to cater to its clients’ sudden spike in demand.
MicroService is ideal for evolutionary systems where it is difficult to anticipate the types of devices that may be accessing our application.

Multi-layer Architecture

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

Layered architecture increases flexibility, maintainability, and scalability
Multiple applications can reuse the components
Parallelism
Different components of the application can be independently deployed, maintained, and updated, on different time schedules
Layered architecture also makes it possible to configure different levels of security to different components
Layered architecture also helps users test the components independent of each other

Roadmap

Key themes and deliverables

Roadmap Overview

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

Theme

Description

Widen Urban Mission Impact

Product feature enhancements and concentrated focus on increasing adoption

Champion Societal Missions

New products to address the sanitation issues facing urban areas and public finance management solutions

Promote Usability and Accessibility

Create integrated user experience with a key focus on flexibility, accessibility, quality of service; Optimized user experience

Enhance Platform Capabilities

Adopt improvements on the platforms that will address some key issues like privacy, security as well as adding new capabilities like GIS

Drive Product Research and Innovation

Identify high-impact research and product innovation areas through validation, understanding the domain, and processes involved

Quarter 2 - July to September 2021

Property Tax -

Simplified Push Payments BBPS, demand base system - Internalize BBPS integration in the product and enable out of box implementation to increase citizen-led payment
Implementing registry principles in PT - Identify and plug the gaps in the current PT registry
Data uploader using excel files - User interface to allow the upload of legacy data excel files to upload legacy data in the product

Public Grievances & Redressal (PGR) -

Multi-selection of complaints & bulk action - Employees can select multiple complaints and perform actions (like allocation) in a couple of steps

mCollect -

Collection extension for other services like PT, TL - Enable collection of the core taxes through the mCollect interface

FSM -

Whatsapp POC - WhatsApp as a channel for citizens to request desludging
OCR POC - Use Optical character recognition to get test result info by taking a photograph instead of manually entering the figures
Scheduling - Manage schedule for the desludging vehicles on a daily basis

Standardization and Simplification -

Standardization of Master Data, Configurations, Taxonomies for ease of deployment

Knowledge assets, Tools, Documentation -

Self-help demo setup - product videos to assist users with key module workflows
Product Training material - help links and how-to articles

Quarter 3 - October to December 2021

Property Tax -

Capital rules-based assessments supporting the product
Amalgamation of property / Bifurcation of property - feature enhancement to manage amalgamation or division of a property use cases

PGR -

Third-party integration with national or local initiatives - Expand capabilities to allow complaints lodged via National Initiatives (Like Swachta) to be routed to DIGIT's PGR for action

mCollect -

POS integration - Out of box app to integrate with POS machines on the field

Finance -

TP collection reconciliation - Third-party collection reconciliation framework

FSM -

Vehicle tracking - Track the desludging vehicles that are servicing the requests from citizens
Integration with IoT devices - Integrating IoT devices to track performance and assess standards at FSTP plant
FSTP performance tracking - Building capability for the treatment operators to track the performance of various treatment plants

Adoption -

Rollout dashboards
Automating infra uptime and tracking incidences via a dashboard
Bots - CSV to system data transfer
Bots - email id
National dashboard - POC
Mobile app
Findability/access to multiple channels -
- Product packaging

Quarter 4 - January to March 2022

Release Date: 01/03/2022

Beta date:

GA date:

Property Tax -

Explore PT integration with other departments like stamps and registration - the key objective is to increase the coverage of the property tax base of the ULB and also identify the revenue leakage points in the ULB

FSM -

Abstraction to business models - Abstracting the core components of various business models across containment/transport/treatment/reuse so that any state can use the platform
Marketplace - Having a marketplace model that connects desludging operators with citizens and manages the entire logistics chain
Open dashboards/data (for researchers) - Creating a one-stop solution for accessing key data points in the FSM space

Adoption and Enhancements -

BBPS integration - BBPs has multiple modes of payment - cash, transfer cheques, and electronic modes
Offline to online driven adoption (QR codes, redesign of receipts, etc) - critical in providing awareness of onboarding on the digital medium and a key catalyst for boosting online adoption
Pair with Whatsapp portal - Provide an alternative channel for the citizen to avail services, eliminating the dependency on other traditional channels
IVRS integration - Interactive Voice Response, a phone call based channel for availing services like Grievance Redressal
CSC integration - Inclusion of CSC/ Sewa Kendras as a channel for providing DIGIT services to Citizens

Release Notes

New release features, enhancements, and fixes

Release Summary

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

Functional: Property Tax Citizen Open search flow UI/UX revamp, Property Tax Employee flow UI/UX revamp, Property Tax Mutation flow UI/UX revamp, HRMS UI/UX revamp, mCollect v2 (eChallan) UI/UX revamp, Trade License Citizen & Employee UI/UX revamp, Receipt Cancellation UI/UX Revamp, WhatsApp v2 (Pay and Enhanced PGR), Workflow Auto Escalation with reference implementations in PGR, W&S Enhancements, FSM DSS, and Standardized Reports for FSM/PT/mCollect.
Non-functional: QA Automaton of APIs for FSM & eChallan, Product Standard Ontologies, Technical improvements, Internal Data Mart, etc.

New ‌Feature Additions

Feature

Description

Property Tax UI/UX Revamp

Citizen flow

Open Search and Payment

Employee flow

Employee Inbox
Create Property
Search Property
Transfer of Ownership
Update Property
Property Assessment

HRMS UI/UX Revamp

Create employee
Search employee
Edit Employee
Deactivate/re-activate employee

Trade License UX revamp

Allow citizen to create Trade License application
Allow citizen to check application status and make payment, download artefacts
Allow Employee to create Trade License application on behalf of citizen
Application processing by employees
Allow citizen to renew the existing trade licenses which are due for renewal
Allow employee to renew the existing trade license which are due for renewal

mCollect v2 (eChallan) UI/UX Revamp

Challan Generation
Challan Search Employee
Total Challan Count
My Challan - Citizen
Search and Pay - Citizen

Receipt Cancellation UI/UX Revamp

FSM DSS

SLA Compliance
Average Collections
Performance by ULB and Districts
Performance by Desludging Operator
Plant Operating Efficiency
Drill downs for Desluding and Vehicle log report

Workflow Auto Escalation

Configure SLA at a workflow state level
Escalate the application to a role if there is a breach in SLA
Make the application status as deemed approved or reject on breach of an SLA
Escalate the application to the next logical step in the workflow ladder if there is a breach in SLA

Product Standardized Reports

FSM

Daily Collection Report
Desludging Request Report
Vehicle Log Report

Defaulter Report
Collection Register Report
Receipt Register Report

mCollect

Challan Register Report
Daily Collection Report
Receipt Register Report

Enhancements

Updated Feature

Description

Water & Sewerage Enhancements

Bill Cancellation of latest bill
Show Due Date in Arrears breakup
Water & Sewerage Combined PDF Changes
Water & Sewerage Due Validation on PT Title Transfer

WhatsApp v2 (Pay and PGR) Enhancements

Improvements in Public Grievance Redressal Module
- Enhancements in messaging language.
- NLP Inclusion (For City & Boundary Selection).
Improvements in Bill Payments
- Enhancements in messaging language.
  - Inclusion of call to action buttons (for certain messages).
- For Linked Mobile Numbers
  - Single-click access to bills (for PT and W&S)
- For Non-Linked Mobile Numbers
  - Provision of Search & Pay (If Property/Connection Details are known).
  - Inclusion of Open Search Links (If Property/ Connection Details are unknown).
Improvements in Payment History
- Enhancements in messaging language and flow.
  - Inclusion of call to action buttons (for certain messages).
- For Linked Mobile Numbers
  - Access to view the last three payments made (for PT & W&S)
  - Provision to download the last three payment receipts
- For Non-Linked Mobile Numbers
  - Access control to view payments history only.

Bill Amendment Enhancement

Additional changes in Bill Amendment screen to display current Demand

PT Enhancements

PT Enhancements - Fuzzy search for Name, Door number, and old PT ID (old UI)

QA Automaton of APIs

APIs automation for

eChallan APIs including end to end APIs automation
Bill Amendment APIs
FSM Inbox API

Other Improvements and Tech Enhancements

Changes in Gender to introduce Transgender and Others.
Standardization of Product ontologies for Property Tax, Water & Sewerage, Fire NOC, mCollect (eChallan), PGR, and Online Building Plan Approval.
Inbox API to support module wise inbox for UI/UX revamp.

Internal Data mart

Internal Data mart for PT, TL, PGR, W&S, FSM, eChallan, OBPS, and Fire NOC modules.

eDCR Enhancements

River Distance: Colour code used to identify different river types.
In the basement footprint layer, captured additional dimension to define the level of the basement under the ground.
In the stilt parking layer, captured height from floor to the bottom of a beam of the stilt floor.

‌Document Resources and Links

UI Technical Documents

Trade License UI/UX Revamp

Citizen

Employee

HRMS UI/UX Revamp

Receipt cancellation UI/UX Revamp

Bill Cancellation

mCollect v2 (eChallan) UI/UX Revamp

Workflow Auto Escalation

Property Tax UI/UX Revamp

Citizen

Employee

Mutation

DSS

Backend Service Documents

MDMS Configuration & Service Build Updates

Configuration changes and service build details

MDMS Changes

Feature

Service Name

Changes

Description

Common

Digit 2.5 common changes

Digit Employee Inbox

Employee navigation to Digit UI

Role Action

FSM inbox correction
Updated role action mapping

Property Tax

Updated documents for PT create and mutation flow

Auto Escalation

Auto Escalation specific changes

FSM-DSS

Added districtTenantCode for each city
Added fsm & ulb-fsm in uiCommonConstants

Product Ontology

Product Ontology Changes

NLP chatbot

NLP chatbot specific changes

Config Changes

Module

Action

Description

Common

Digit 2.5 common changes
Indentation correction for Indexer

FSM-DSS and FSM Reports

Updated Mater Dashboard config for FSM DSS
Added FSM DSS configurations
Updated Chart Api changes for fsm dss

Inbox API

Added Inbox searcher config for TL
Updated searcher config for sorting application
Added config for count TL search,
Provided custom sorting for PT inbox

PT Reports

Removed duplicate records for PT reports
Corrected duplicate owner issue

PDF

Changes for localization for Receipt Cancellation
Changes for mcollect challan for Hindi localization

Infra Changes

Feature

Description

Common

Digit 2.5 common changes
Corrected the indentation for Inbox
State level tenant ID for workflow v2

Open Payment (PT & WS)

Added mixed end point for PT and WS

TL Searcher

Added searcher for Inbox TL

nlp-engine

Added NLP specific changes

turn-io-adapter

Changes for turn-IO adapter

Service Build Updates

Test Cases

WhatsApp Channel Release Notes

WhatsApp channel v2 release details

Overview

This release leverages the capabilities of WhatsApp as an additional channel for citizens to access/ pay bills for revenue modules like property tax and water/sewerage. With the improved user experience in terms of messaging and overall application flow, WhatsApp (V2) aims to strengthen the ease of service access for citizens at the last mile.

Release Highlights

Improvements in Public Grievance Redressal Module

Enhancements in messaging language.
NLP Inclusion (For City & Boundary Selection).

Improvements in Bill Payments

Enhancements in messaging language.
- Inclusion of call to action buttons (for certain messages).
For Linked Mobile Numbers
- Single-click access to bills (for PT and W&S)
For Non-Linked Mobile Numbers
- Provision of Search & Pay (If Property/Connection Details are known).
- Inclusion of Open Search Links (If Property/ Connection Details are unknown).

Improvements in Payment History

Enhancements in messaging language and flow.
- Inclusion of call to action buttons (for certain messages).
For Linked Mobile Numbers
- Access to view the last three payments made (for PT & W&S)
- Provision to download the last three payment receipts
For Non-Linked Mobile Numbers
- Access control to view payments history only.

Release Features

Key Feature

Description

Call to action (CTA) Buttons

Call to action buttons (CTA) is an interactive message template that aims to provide an improved conversational experience. For WhatsApp V2, certain endpoints have called to action buttons included.

Instead of citizens typing for a reply, CTA buttons allow citizens to select the option and perform action instantly. The CTAs are applicable to the following scenarios :

Pay Bills.
Return to Main Menu.
View Payment Receipts.

Provision For Search & Pay Bills.

(Non-Linked Mobile Numbers)

As part of the WhatsApp V2, citizens :

whose mobile numbers are not linked with DIGIT.
are aware of the account details (PT ID/ Connection No).

can now search and pay the outstanding bills.

This feature encourages citizens to have access to outstanding bills on DIGIT even if the mobile number is not registered on the platform.

Inclusion of Open Search Links

As part of the WhatsApp V2, citizens :

whose mobile numbers are not linked with DIGIT
not aware of the account details (PT ID/ Connection No)

can now use the open search and pay the outstanding bills.

The open search allows citizens to fetch outstanding bills using other parameters (like door no/ name etc). In this case, the citizens will be redirected to the open search webpage and all the further interactions are exclusive of WhatsApp Chatbot.

This feature encourages citizens to have an access gateway to pay outstanding bills even when the required details are unknown.

View Payment History

View Payment History feature allows citizens to view the last three payments made for revenue service.

Further, in order to comply with data privacy :

Only linked mobile numbers are allowed to download the past payment receipts.
Non-Linked Mobile numbers cannot access the receipts and only have provision to view payments history.

NLP Inclusion

As part of the WhatsApp V2, citizens can now type and submit the :

City Name
Locality Details

while filing a complaint on PGR.

This feature is a major enhancement to the older version as now citizens don't have to be redirected outside the chatbot to select details.

Instead, citizens can now type and submit the information. Even when the information entered is incorrect, the NLP engine provides a suggestion for citizens to make corrections and proceed.

Limitations

As an external independent environment, WhatsApp has the following limitations (applicable for current and future initiatives) :

Limitation

Description

Access Control On Template Messages

Only messages that are approved by WhatsApp can be part of the chatbot.
Post-approval only, internal development/ configuration can take place.

No Alteration/External Development Allowed.

WhatsApp does not allow the alteration such as chat inbox or message pad.

Access control over the User Experience

We cannot control UX Aspects such as :
- Messaging Alignment (Auto-adjusted by WhatsApp as per Device).
- Resolution Adjustment (Image & Multimedia Files).
- Font Size & Style.
- Message Character Length.
- Message Delivery Speed (Not Fully)
- Message Ordering

Upcoming Release Features

Water & Sewerage Open Search Infographic (For New UI).
Integrate common pay new UI.
DIGIT Platform Enhancements
- Update a non linked mobile number as an alternate number (post payments).
- Access control on payment recipients (owner vs others).

Trade License Release Notes

Overview

This release is for the trade license UX revamp. There is no change in the existing functionality but the entire module moved to the new DIGIT UX

Release Highlights

This release has the following features

Allow citizens to create trade license application
Allow citizens to check application status and make payment, download artefacts
Allow Employee to create trade license application on behalf of citizen
Application processing by employees
Allow citizens to renew the existing trade licenses which are due for renewal
Allow employees to renew the existing trade license which is due for renewal

Release Features

Key Feature

Description

Allow citizens to create trade license application

This feature allows the citizen to register a trade license application online.

Allow citizens to check application status and make payment, download artefacts

This feature allows citizens to check the status of the application that was created online, respond to comments or clarifications raised by the employees, make the payment if there is an amount due and download trade license certificate and payment receipt online.

Allow Employee to create trade license application on behalf of citizen

This feature allows employees to create a trade license application on behalf of the citizen over the ULB counter and provide application acknowledgement for the applicant.

Application processing by employees

The application either created by the citizen online or by the employee over the counter can be processed for document verification, field inspection and approval.

In the process, the application can be sent back to the citizen for clarification, send back to the officer in the workflow approval for queries. The application can also be rejected with reasons.

Allow citizens to renew the existing trade licenses which are due for renewal

Citizens can apply for license renewal online, in the process if there are some changes made to the trade that can be updated in the application. If the trade details are modified during renewal then the application is considered as a new application and goes for processing at the employee side for doc verification and field inspection.

If it is not modified then it can be renewed right away after making payment.

Allow employees to renew the existing trade license which is due for renewal

Similar to the TLcreate , renewal also can be done by the employee on behalf of the citizen.

Known Issues

Upcoming Release Features

Reference Doc Links

Doc Links

Description

FSM Release Notes

Overview

This release is for the FSM decision support system used by the ULB administrators and the day to day reports used by the officials.

Release Highlights

FSM DSS
Daily collection register
Vehicle log report
Desludging request report

Release Features

Key Feature

Description

FSM DSS

This decision support system will provide a comprehensive view for a state administrator to know the SLA compliance, average collections, performance by district and ULB, performance by the desludging operator, plan operational efficiency etc…

Daily Collection register

This report will help the head cashier and collection operator to know the daily collection instrument type wise and reconcile the physical collection at the end of the day.

Vehicle log report

This report details the volume of septage that is transported by a vehicle or operator for a date range.

Desludging request report

This is a detailed report which provides the life cycle of a desludging transaction, starting from application creation to septage being dumped at the plant

Known Issues

Upcoming Release Features

Reference Doc Links

Doc Links

Description

eDCR Release Notes

Release Highlights

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

Release Features

Upgrade Instructions

eDCR 2.0.0: The above feature is useful and required in other states.
Impact: Functionally, the upgrade to eDCR 2.0.0 will not impact the existing environments.

Workflow Auto Escalation Release Notes

Overview

This is an enhancement in the workflow service where applications can get auto escalated to a designated role on breach of an SLA

Release Highlights

Configure SLA at a workflow state level
Escalate the application to a role if there is a breach in SLA
Make the application status as deemed approved or reject on breach of an SLA
Escalate the application to the next logical step in the workflow ladder if there is a breach in SLA

Release Features

Known Issues

One UX issue which will go out in the next patch release

Upcoming Release Features

Reference Doc Links

QA Automation Release Notes

Below is the list of services for which APIs are automated in this release.

Doc Links

HRMS UI/UX Revamp Release Notes

Overview

This release aims at the UI/UX Revamp of the existing HRMS module primarily, with certain minor enhancements incorporated functionally.

Release Highlights

Employee summary card (post-login).
UI Enhancements for
- Create new Employee
- Search employee screen.
Usability enhancements
- Inclusion of various filters
- View of roles assigned in terms of count (post search)

Release Features

Key Feature

Description

Employee Summary Card

(Post Login)

Once, State/ ULB Administrator has logged in to the master portal, they will land on the homepage consisting of the HRMS card.

This card provides an overall summary on:

The Total Employees Created (Total Employees in the Database).
The Total Employees that are active (at this time).

Along with the above, the admin has the following options :

Search Employee.
Create Employee

Employee Search

The UI of employee search has been upgraded with search now possible by using the following filters :

By ULB (Useful when an employee is operating jurisdictions)
By Designation
By Role (This filter is Multi-Select)
By Employment Status (Active/ Inactive).

The following search displays the following fields :

Employee ID
Name
No of Roles (Describes the no of roles assigned).
Designation
Department
Employment Status

Known Issues

The case sensitive search

Upcoming Features

Reports UI Revamp.
Onground implication for multiple assignment dates and propose the product changes.
Enhance the text for Exception Handling.
Inclusion of Privacy Bit.

Bill Amendment Release Notes

Overview

Changes in Bill Amendment application to ensure ease of process for the user.

Release Highlights

Changes in Bill Amendment screen to display current Demand

Release Features

Key Feature

Description

Changes in Bill Amendment screen to display current Demand

The changes in the application screen are as below

Add a new column in the amount adjustment screen - "Current Demand" along with Reduced Amount and Additional Amount.
The New column would display the current demand (Latest) against each of the Tax Heads.
The Summary Screen which is shown after the Submission would also display this column info.

Known Issues

Upcoming Release Features

Reference Doc Links

Doc Links

Description

W&S Release Notes

Overview

This release for the Water and Sewerage module consists of a major feature and few enhancements for the urban local body employee to handle the ground operations seamlessly.

Release Highlights

Dues validation on Property Transfer
Combined PDFs for Water and Sewerage Services
Arrears breakup and due date on the bill
Bill Cancelation

Feature Details

Upcoming Release Features

Handling combined PDFs batch-wise, for more than 50 connections
Property details on the bill
Current bill cancellation completeness for non-metered and sewerage connections
Role-based control for dues collection on property transfer

Product Docs

Products & Modules

This section contains DIGIT product and module related documents

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

🧐 Key Benefits

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

🔗 Product Links

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

TL Brochure

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

PT Workflows

Learn more about PT workflows and its configuration

MDMS Configuration & Service Build Updates

Configuration changes and service build details

MDMS Changes

Feature

Service Name

Changes

Description

Common

Digit 2.5 common changes

Digit Employee Inbox

Employee navigation to Digit UI

Role Action

, , , , ,

FSM inbox correction
Updated role action mapping

Property Tax

Updated documents for PT create and mutation flow

Auto Escalation

Auto Escalation specific changes

FSM-DSS

, ,

Added districtTenantCode for each city
Added fsm & ulb-fsm in uiCommonConstants

Product Ontology

, ,

Product Ontology Changes

NLP chatbot

NLP chatbot specific changes

Config Changes

Module

Action

Description

Common

, ,

Digit 2.5 common changes
Indentation correction for Indexer

FSM-DSS and FSM Reports

, , , ,

Updated Mater Dashboard config for FSM DSS
Added FSM DSS configurations
Updated Chart Api changes for fsm dss

Inbox API

, , , , , , , ,

Added Inbox searcher config for TL
Updated searcher config for sorting application
Added config for count TL search,
Provided custom sorting for PT inbox

PT Reports

Removed duplicate records for PT reports
Corrected duplicate owner issue

PDF

, ,

Changes for localization for Receipt Cancellation
Changes for mcollect challan for Hindi localization

Infra Changes

Feature

Description

Common

, ,

Digit 2.5 common changes
Corrected the indentation for Inbox
State level tenant ID for workflow v2

Open Payment (PT & WS)

Added mixed end point for PT and WS

TL Searcher

Added searcher for Inbox TL

nlp-engine

Added NLP specific changes

turn-io-adapter

Changes for turn-IO adapter

Service Build Updates

TL Module Functional Specifications

Functional overview for stakeholders

Introduction

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

The Trade License product enables:

Ease of doing business — Traders can apply for new licenses, renewals, amendments, and supplemental licenses
Regulatory Tracking — Administrators can track and manage regulatory processes
Shorter Timelines — It streamlines and automates business licensing processes and helps a business to be set up quickly
Data-driven decision making — The application collates valuable information on the economic activity and employment opportunities in a ULB

Functional Scope

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

Registration, Login and Creation of User Profile
Applying for a Trade License
Trade License Issue
Modifications to a Trade License
Renewal of Trade License
Payments and Fee
Dashboards and Reports
General Features

Key capabilities offered by this functional component -

OTP Based Login for Citizen via Web/Mobile App
OTP Based Login for Employee via Web/Mobile App
Provision for language selection during first time registration for both Employee and citizens
Provision of creating a personalized Profile for Citizens and employees on Web App
Login Credentials for the various hierarchies of employees
Role-based access for performing different actions relating to Trade License modules

Applying for a Trade License

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

Key capabilities offered by this functional component -

Citizen can Apply for a new Trade License through mobile app/ Web
Citizen/CSC can capture Trade details, Trade Units, Accessories, Owner Details, Address, purpose, Date of issuance, License number etc.
Citizen/CSC Upload Documents
Citizen/CSC can calculate Breakup Based on Selected Trade
Citizen/CSC can select Multiple Accessories for the Trade
Citizen/CSC can Apply for Multiple Trade Licenses
Citizen/CSC can Download/Print Application Summary
Citizen/CSC can Download/Print Trade Reference No
Citizen/CSC can View the applied licenses
The system has the facility to deliver the service online & through SEWA KENDRA.
The portal displays all the information including the processes and documents required for the convenience of the citizen.
The system has the facility to assign a unique identification number based on the license type, which will be used for all future transactions of the license.

Trade License Issue

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

Key capabilities offered by this functional component -

Document Verifier, Verifies & Forwards or Rejects the application
Licensing Inspector, Verifies and Forward the Application
Licensing Inspector, Sends Back or Rejects the Application
Licensing Inspectors Approves the Application
Citizen, Pays for the license post verification process online or at the CSC
CSC, Collects Fee post verification.
The system allows the printing of license and sending the license through e-mail.
The system allows the SMS alerts to the applicant regarding the date of inspection/visit by the inspector, approval/rejection of the application.
The system allows the inspector to enter the field visit details and a field visit report is generated and automatically routed to the superintendent.

Modifications to a Trade License

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

Renewal of a Trade License

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

Payment and Fee

Key capabilities offered by this functional component -

The citizen can pay for the license post verification process
CSC, Collects Fee post verification.
The system allows intimating the applicant about the payment of the license fee through SMS/ e-Mail.
The system allows the Generation of receipt for the payment
The payment modes enabled are Card(offline), cash, cheque, DD

Dashboards and Reports

Following reports offered by the module -

Cancelled Receipt Register Report
TL Collection
TL Application Status- showing the number of licenses approved/rejected.
TL ULB Wise Status
State Dashboard: View Reports for Total Licenses, Licenses Issued, Payment Collected, Payment Distribution

General Features

Notifications - The system has the capability to send notifications to citizens. These notifications can be sent for various steps like - verification completion, payment reminder, payment confirmation. These notifications can be sent in the language chosen by the ULB through all channels - SMS, Whatsapp, Email.

Configurable Masters - The system provides the following masters that can be configured as per the State’s requirements:

Charges & Calculation : Calculation Engine, Rebate, Penalty,
Rate Master
State Masters: Trade Ontology, Documents List, Accessories, Ownership, Employee Data Mapping, Boundary Data Mapping, Fee Matrix (License Fees)

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

Reform No.

Reform Area

Weightage (score)

Recommendation

Remarks

Sector Specific

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 Features- Trade License

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

Provision of Personalized Profile for Citizen/ Employee on Web App

Applying for a Trade License

Citizen/CSC: Enters Trade Details, Trade Units, Accessories, Owner Details.

Citizen/CSC: Upload Documents

Citizen/CSC: ULB Wise Trade Selection

Citizen/CSC: Calculation Breakup Based on Selected Trade

Citizen/CSC: Multiple Accessories Field Count

Citizen/CSC: Multiple Trade License.

Citizen/CSC: Download/Print Application Summary

Citizen/CSC: Download/PRINT Trade Reference No

Citizen/CSC: View the applied licenses.

Citizen: Pays for the license post verification process.

CSC: Collects Fee post verification.

Trade Licence Issue

Document Verifier : Verify & Forward/ Reject the application

Licensing Inspector: Verify and Forward/ Send back/ Reject the Application.

Licensing Officer: Approve/ Send back the Application

Licensing Officer: Reject/ Cancel the Application

Modification to a Trade License

Edit/ Update the Application based on the Inspection report against the application.

Renewal of a Trade Licence

Renew trade license.

Payment and Fee

Configurable Workflow Rights : Edit & Payment Collection

Payments & Collection : Various Payment Modes

Dashboards and reports

Cancelled Receipt Register Report

TL Collection

TL Application Status- showing the number of licenses approved/rejected.

TL ULB Wise Status

State Dashboard: View Reports for Total Licenses, Licenses Issued, Payment Collected, Payment Distribution

General features

Notifications : SMS Notifications

Charges & Calculation : Calculation Engine

Charges & Calculation : Rebate/ Penalty- Date Based

Charges & Calculation : Ad-Hoc Rebate/ Penalty

Charges & Calculation : Exemptions Trade Type & Owner Type

Configuration masters

Configurable Workflow Rights : Edit & Payment Collection

Configurable Verification & Approval

TL Implementation Guide

Executive Summary

Overview of the Product

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

Implementation Methodology for TL

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

Exhibit 1: Phases of Implementation.

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

Critical Success Factors for implementation

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

Product-Overview

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

The Trade License product enables:

Ease of doing business — Traders can apply for new licenses, renewals, amendments, and supplemental licenses
Regulatory Tracking — Administrators can track and manage regulatory processes
Shorter Timelines — It streamlines and automates business licensing processes and helps a business to be set up quickly
Data-driven decision making — The application collates valuable information on the economic activity and employment opportunities in a ULB

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

Registration, Login and Creation of User Profile
Applying for a Trade License
Trade License Issue
Modifications to a Trade License
Renewal of Trade License
Payments and Fee
Dashboards and Reports
General Features

Trade License (TL) Implementation Methodology

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

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

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

Seven Stages of Implementation for Trade License

Stage 0 - Program Setup/Onboarding

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

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

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

Stage 1 - Program Kick-Off

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

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

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

State Baseline Data: A Baseline Template is provided to collect certain vital information like no. of transactions, revenue collected in the last FYs, collection mode, budget data, etc. This data must be collected pre-rollout

Stage 2 - Solution Design

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

Pilot ULBs Specific Product Data Configuration: Master data is required from the Product Perspective for go live. For e.g.: Boundary Data, List of Employees etc. A Master Data Template will be provided for the collection of this particular data type.

Stage 3 - Configuration & Customization

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

Stage 4 - UAT & Go Live

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

Note: The Nodal Officer is responsible to identify the ULB officials who are associated with the TL process on ground and will be working with the technological Product in the respective ULBs

Stage 5 – Rollout

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

Note: The rollout phase needs to be detailed out for iterative activities of onboarding ULBs in batches.

Note: Only once all the stages are complete in one batch of rollout of around 30 ULBs, the next batch begins. There are multiple phases of rollout. The second batch begins after the first batch has successfully fulfilled all the criteria of the Rollout Phase. Typical timeline for closure of rollout in each batch is 5-6 weeks (in a batch of 30 ULBs)

Stage 6 – Sustenance and Ongoing Improvement

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

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

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

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

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

Note:

Designation mentioned above are as per designations already driving TLs implementation at the State level.
The description of each designation is explained below.
These are the preferred figures. In the case of Domain Expert, 2 people is subject to availability

Description of resource persons:

Project Head: Is the Head of the TL Cell who will drive the project from the State’s Side
Domain Expert: Person who is well aware of the on-ground scenario, well versed with the act, GOs passed, Prevalent Business processes, Deviations from the acts, TL Rates/ slabs applicable
Nodal officer (EO/Commissioner/ Senior Official): the project coordinator in each district to drive the project centrally. Monitor usage post Go Live- point of escalation for Implementation Team, Seasoned and worked in Multiple ULBs on various modules and has a good understanding of TL, Facilitate and Track data collection Post Go Live, Monitors and facilitates adoption of application. point of contact for eGov, SI and at the HQ level.
MIS Expert: Day to day tracking of the data specific to ULBs, data entry, reporting and review to senior officials

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

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

Guidelines to read the tables below:

Execute - One who owns the accountability to complete the activity

Consult - One who may initiate, guide and in the process, handhold the execution of the activity

Note: Stage 0 is where the TL cell and SI team is formed, hence there are only two entities playing a role which is that of eGov and the state leadership. Once the TL cell and SI team is finalised, their role begins in the following stages.

Overall Program Assumptions

Glossary

Vision:

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

Project Plan:

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

System Integrator:

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

Program Charter:

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

Acceptance Letter/MOU:

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

Program Success Metrics:

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

Project steering committee:

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

Project governance:

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

Scoping:

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

Baseline data:

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

Project Kick off meeting:

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

Fitment Study:

GAP Study of the Existing/Required Field Process Vs Product

Data migration:

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

Data collection:

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

Data validation approach:

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

Data synchronization:

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

Pilot Implementation:

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

Pilot ULB:

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

Roll out:

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

Deployment:

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

Customization:

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

Configuration:

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

Product walkthrough:

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

PT Module Functional Specifications

Functional overview for stakeholders

Introduction

The Property Tax System(PT) provides a digital interface to make property assessments, pay property tax, generate payment receipts and monitor tax collection. It can be used by the citizens, Urban Local Body (ULB) counter and field employees and ULB Administrators to accomplish their specific tasks. It is available as a mobile and web-based application.

Functional Scope

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

Registration, Login and Creation of User Profile
Filling an Assessment for a Property
Searching for a Property
Modifications to a Property
Generate Demand Notice
Payments collection and Receipts
Dashboards and Reports
General Features

OTP Based Login for Citizen via Web/Mobile App
OTP Based Login for Employee via Web/Mobile App
Provision for language selection during first time registration for both Employee and citizens
Provision of creating a personalized Profile for Citizens and employees on Web App
Login Credentials for the various hierarchy of employees
Role-based access for performing different actions relating to property tax modules

Filing For Property Assessment

With this feature, a citizen and employee can perform a self-assessment of a new property for a financial year. This feature helps in registering the property in the system. The details of the property can be entered online and can be assessed for the calculation of the taxes.

The PT Product is designed in a user friendly manner and reduces chances of error. System calculates the tax automatically and creates the demand. If a user wants to reassess his property due to any reason (for eg, incorrect data, change in property etc), it can be done by editing details of the last assessment.

An employee can edit the details of the last assessment, on behalf of the citizen-based on the owner’s input. Citizen can track down the status of his incomplete assessment. Any incomplete assessment can be searched and completed.

Citizen/CSC can Assess New Property (By Different Financial Years).
Citizen/CSC can Capture Address, Assessment Info, Owner Info.for all types of properties like residential houses, flats and commercial buildings.

o Sample Details captured:

Door Number,
Mutation number,
Number of floors,
Area covered,
Owner and co-owner,
Mailing & permanent address,
Built year
Individual room measurements
The system computes the property taxes automatically as per process and rules of the state.
The system has a facility to make entry in system by inspector after site visit and assessment of the same by the superintendent.
The system supports dynamic calculation for late fees, interest, rebates, etc. as on the day of demand generation.
The system fetches the data of previous year property data while e-filing for current year so that all the dues are calculated.
The system assigns a unique property ID based on the process defined in the ULBs.
Citizen/CSC : View/Print Summary of Filled Form
Assessment Form
Assessment Form is also sent by email to citizen
Upload Documents
Ownership/Title related
ID Proof
Any other statutory documents

Searching for a Property

Citizen or Employee can track down the status of his incomplete assessment. Any incomplete assessment can be searched and completed.

Citizen/CSC can search for Property by
- Mobile No,
- City,
- Property Tax Unique ID
Citizen/ CSC can view Incomplete Assessments
Citizen/CSC can reassess Searched Property
View Property details and pending dues

Modifications to a Property

The PT system provides the ability to capture mutation and transfer of ownership. It reduces interfaces between the user and the State and thus promote greater transparency. It also helps in reducing the time taken for mutation after registration. The system provides the ability for alteration of assessment after verification and inspection. Any structural changes like addition/extension/reduction of existing built up area or construction type OR utility changes like usage or occupancy have an impact on the increase/decrease in property tax demand. These changes can be handled by the ‘Additional/Alteration of Assessment’ feature.

The System provides the ability for bifurcation/ amalgamation of property. The property bifurcation/ amalgamation undergoes an approval process. The parent property needs to be modified accordingly, which can be done in the system.

Mutation of property and change of ownership details
Capture Extension/ Addition and Alteration and reassessment based on changed property details
Bifurcation of property
Amalgamation of property

Generate Demand Notice

System has the capability to automatically generate demand notice for a financial year based on set triggers like time-based roll over on 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 provides the capability to Employees to merge and download bills based on given parameters to plan their distribution drives.

Generate Demand Notice based on periodic basis
Group Demand Notices
Print Demand Notices
Cancel Demand Notices
Send notifications to citizens on demand generation- SMS, Whatsapp, Email, Physical bil

Payments collection and Receipts

The citizen/ employee can view payment status of previous assessments from Assessment History section. Payment for any assessment with full or partially paid amount can be completed. Receipts for assessment can be downloaded in Assessment history section after searching for the property details.

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 issual of receipt

Reports and Dashboards

PT reports provides facility to access receipt register, cancelled receipt register, account receipt register, ULB wise PT collection report, DCB Register. All reports can be downloaded in PDF/XLS format.State level administrator can monitor property tax collections, assessments and other information at a state level through dashboards.

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

Notifications - The system has the capability to send notifications to citizens. These notifications can be sent for various steps like - assessment completion, payment reminder, payment confirmation. These notifications can be sent in the language chosen by the ULB through all channels - SMS, Whatsapp, Email.

Legacy Data Migration - The system has the capability to 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

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

Reform No.

Reform Area

Weightage (score)

Recommendation

Remarks

Land administration and Transfer of Land and Property

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

Land administration and Transfer of Land and Property

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

Land administration and Transfer of Land and Property

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

Land administration and Transfer of Land and Property

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

Land administration and Transfer of Land and Property

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

Land administration and Transfer of Land and Property

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

Land administration and Transfer of Land and Property

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

Land administration and Transfer of Land and Property

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 Features- Property Tax

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

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

PT Implementation Guide

Executive Summary

Overview of the Product

The computerized and automatic Property Tax system offered by eGov, facilitates citizens who seek to pay their Property Tax within any Urban Local Body with a transparent, speedy, hassle-free and user-friendly procedure. Property Tax (PT) is one of the components of a smart city that has the capability of providing the highest revenue of a state. Keeping in mind the benefits associated with the product offered, the proposed system is about to be implemented in 500+ ULBs across the country in 15 states. (For details on product features refer to Section-2)

Implementation Methodology for PT

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

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

Critical Success Factors for implementation

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

Property Tax (PT) Product - Overview

The Property Tax System(PT) provides a digital interface to make property assessments, pay property tax, generate payment receipts and monitor tax collection. It can be used by the citizens, Urban Local Body (ULB) counter and field employees, and ULB Administrators to accomplish their specific tasks. It is available as a mobile and web-based application. The PT product features can be broadly classified as the following modules:

Registration, Login and Creation of User Profile
Filling an Assessment for a Property
Searching for a Property
Modifications to a Property
Generate Demand Notice
Payments collection and Receipts
Dashboards and Reports
General Features

This module provides enables the following capabilities

OTP Based Login for Citizen via Web/Mobile App
OTP Based Login for Employee via Web/Mobile App
Provision for language selection during first time registration for both Employee and citizens
Provision of creating a personalized Profile for Citizens and employees on Web App
Login Credentials for various hierarchy of employees
Role based access for performing different actions relating to property tax modules

Module 2: Filing an Assessment for a Property

With this feature, a citizen and employee can perform self assessment of a new property for a financial year. This feature helps in registering the property in the system. The details of the property can be entered online and can be assessed for calculation of the taxes. The PT Product is designed in a user friendly manner and reduces chances of error. System calculates the tax automatically and creates the demand. If a user wants to reassess his property due to any reason (for eg, incorrect data, change in property etc), it can be done by editing details of last assessment. Employee can edit the details of the last assessment, on behalf of the citizen based on owner’s input. Citizen can track down the status of his incomplete assessment. Any incomplete assessment can be searched and completed.

This module provides enables the following capabilities:

Citizen/CSC can Assess New Property (By Different Financial Years).
Citizen/CSC can Capture Address, Assessment Info, Owner Info.for all types of properties like residential houses, flats and commercial buildings.
- Sample Details captured:
Door Number,
Mutation number,
Number of floors,
Area covered,
Owner and co-owner,
Mailing & permanent address,
Built year
Individual room measurements
The system computes the property taxes automatically as per process and rules of the state.
The system has a facility to make entry in system by inspector after site visit and assessment of the same by the superintendent.
The system supports dynamic calculation for late fees, interest, rebates, etc. as on the day of demand generation.
The system fetches the data of previous year property data while e-filing for current year so that all the dues are calculated.
The system assigns a unique property ID based on the process defined in the ULBs.
Citizen/CSC : View/Print Summary of Filled Form
- Assessment Form
- Assessment Form is also sent by email to citizen
Upload Documents
- Ownership/Title related
- ID Proof
- Any other statutory documents

Module 3: Searching for a Property

Citizen or Employee can track down the status of his incomplete assessment. Any incomplete assessment can be searched and completed.

This module provides the following capabilities:

Citizen/CSC can search for Property by
- Mobile No,
- City,
- Property Tax Unique ID
Citizen/ CSC can view Incomplete Assessments
Citizen/CSC can reassess Searched Property
View Property details and pending dues

Module 4: Modifications to a Property

This module provides the following capabilities:

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

Module 5: Generate Demand Notice

This module provides the following capabilities:

Generate Demand Notice based on periodic basis
Group Demand Notices
Print Demand Notices
Cancel Demand Notices
Send notifications to citizens on demand generation- SMS, Whatsapp, Email, Physical bill

Module 6: Payments collection and Receipts

This module provides the following capabilities:

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.

Module 7: Reports and Dashboards

PT reports provides facility to access receipt register, cancelled receipt register, account receipt register, ULB wise PT collection report, DCB Register. All reports can be downloaded in PDF/XLS format. State level administrator can monitor property tax collections, assessments and other information at a state level through dashboards.

This module provides the following capabilities:

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)

Module 8: General Features

Notifications

The system has the capability to send notifications to citizens. These notifications can be sent for various steps like - assessment completion, payment reminder, payment confirmation. These notifications can be sent in the language chosen by the ULB through all channels - SMS, Whatsapp, Email.

Legacy Data Migration

The system has the capability to 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

Property Tax (PT) Implementation Methodology

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

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

PT implementation program is expected to be completed approximately between 38- 42 weeks depending on the variety in Processes, Integration and the Disparate legacy data systems involved. This is done with the resource deployment by the State and System Integrator (SI) Team. However, it is critical that activities and exit criteria set for each stage are achieved to adhere to this timeline.

Seven Stages of Implementation

Stage 0 - Program Setup/Onboarding

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

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

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

Stage 1 - Program Kick-Off

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

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

Stage 2 - Solution Design

During the Solution design stage, key State officials and members, who are subject matter experts, are expected to share their inputs, discuss the process and help understand how to bring in compliance around the system design for the System Integrator(SI) Team. This stage baselines the State-specific product features in the Product Configuration report.

Stage 3 - Configuration & Customization

Stage 4 - UAT & Go Live

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

Stage 5 – Rollout

Note: The rollout phase needs to be detailed out for iterative activities of onboarding ULBs in batches.

Stage 6 – Sustenance and Ongoing Improvement

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

Roles and Responsibilities

PT Cell, eGov Team & System Integrator(SI)Team

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

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

Note:

Designations mentioned above are in accordance with those already driving PT implementation at the State level.
The description of each designation is explained below.
Project Head: Is the Head of the PT Cell who will drive the project from the State’s Side
Domain Expert: Person who is well aware of the on ground scenario, well versed with the act, GOs passed, Prevalent Business processes, Deviations from the acts, PT Rates/ slabs applicable. In addition, provisions may be made to include External Domain Consultants/Advisors.
Nodal officer (EO/Commissioner/ Senior Official): the product coordinator to drive the project centrally. Monitor usage post Go Live- point of escalation for Implementation Team, Seasoned and worked in Multiple ULBs on various modules and has a good understanding of PT, Facilitate and Track data collection Post Go Live, Monitors and facilitates adoption of application. Point of contact for Management team, SI and at the HQ level.
MIS Expert: Data Preparation for ULBs,Day to day tracking of the data specific to ULBs, data collection/validation for correctness and comprehesiness, reporting and review to senior officials

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

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

Guidelines to read the tables below:

Execute - One who owns the accountability to complete the activity

Consult - One who may initiate, guide and in the process, handhold the execution of the activity

Note: Stage 0 is where the PT cell and SI team is formed, hence there are only two entities playing a role which is that of eGov and the state leadership. Once the PT cell and SI team is finalised, their role begins in the following stages.

Overall Program Assumptions

Glossary

Vision:

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

Project Plan:

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

System Integrator:

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

Program Charter:

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

Acceptance Letter/MOU:

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

Program Success Metrics:

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

Project steering committee:

Project governance:

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

Scoping:

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

Baseline data:

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

Project Kick off meeting:

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

Fitment Study:

GAP Study of the Existing/Required Field Process Vs Product

Data migration:

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

Data collection:

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

Data validation approach:

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

Data synchronization:

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

Pilot Implementation:

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

Pilot ULB:

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

Roll out:

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

Deployment:

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

Customisation:

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

Configuration:

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

Product walkthrough:

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

Fuzzy Search Reindexing

Step 1

Get the current mapping of the pt index using the _mapping API

GET /property-services/_mapping

Step 2

Add the following json mappings in the existing mappings (parallel to properties key):

"_source": {
        "excludes": [
          "Data.street",
          "Data.doorNo",
          "Data.ownerNames"
        ]
      }

Sample QA final mapping for reference is attached at the end.

Step 3

Recreate property-services-enriched with the new mapping.

Step 4

Update the indexer configuration, add the following 3 fields ownerNames, doorNo, street in custom mapping as added below in sample configuration:

https://github.com/egovernments/configs/blob/qa/egov-indexer/property-services.yml

** If search has to be enabled only on names of only ACTIVE user, configure indexer jsonPath accordingly. Use $.owners[*][?(@.status=='ACTIVE')].name instead in the config

Step 5

Restart indexer

Step 6

Trigger reindexing

Steps followed for Reindexing on QA env

Recreated property-services-enriched index with the new mapping
Created kafka connector
Hit the legacy index api
Once data is indexed in property-services-enriched, verify that all the data is indexed
After validating the data, drop the property-services index and use alias to point property-services to property-services-enriched

POST /_aliases
{
  "actions": [
    {
      "add": {
        "index": "property-services-enriched",
        "alias": "property-services"
      }
    }
  ]
}

Sample mappings from QA env:

{
  "mappings": {
    "general": {
      "_source": {
        "excludes": [
          "Data.street",
          "Data.doorNo",
          "Data.ownerNames"
        ]
      },
      "properties" : {
          "Data" : {
            "properties" : {
              "@timestamp" : {
                "type" : "date"
              },
              "accountId" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "acknowldgementNumber" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "auditDetails" : {
                "properties" : {
                  "createdBy" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "createdTime" : {
                    "type" : "long"
                  },
                  "lastModifiedBy" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "lastModifiedTime" : {
                    "type" : "long"
                  }
                }
              },
              "channel" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "creationReason" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "history" : {
                "properties" : {
                  "action" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "assigner" : {
                    "properties" : {
                      "emailId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "id" : {
                        "type" : "long"
                      },
                      "mobileNumber" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "name" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "roles" : {
                        "properties" : {
                          "code" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "name" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "tenantId" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          }
                        }
                      },
                      "tenantId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "type" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "userName" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "uuid" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      }
                    }
                  },
                  "assignes" : {
                    "properties" : {
                      "emailId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "id" : {
                        "type" : "long"
                      },
                      "mobileNumber" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "name" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "roles" : {
                        "properties" : {
                          "code" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "name" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "tenantId" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          }
                        }
                      },
                      "tenantId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "type" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "userName" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "uuid" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      }
                    }
                  },
                  "auditDetails" : {
                    "properties" : {
                      "createdBy" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "createdTime" : {
                        "type" : "long"
                      },
                      "lastModifiedBy" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "lastModifiedTime" : {
                        "type" : "long"
                      }
                    }
                  },
                  "businessId" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "businessService" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "businesssServiceSla" : {
                    "type" : "long"
                  },
                  "comment" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "documents" : {
                    "properties" : {
                      "auditDetails" : {
                        "properties" : {
                          "createdBy" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "createdTime" : {
                            "type" : "long"
                          },
                          "lastModifiedBy" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "lastModifiedTime" : {
                            "type" : "long"
                          }
                        }
                      },
                      "documentType" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "fileStoreId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "id" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "tenantId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      }
                    }
                  },
                  "id" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "moduleName" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "nextActions" : {
                    "properties" : {
                      "action" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "currentState" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "nextState" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "roles" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "tenantId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "uuid" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      }
                    }
                  },
                  "previousStatus" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "rating" : {
                    "type" : "long"
                  },
                  "state" : {
                    "properties" : {
                      "actions" : {
                        "properties" : {
                          "action" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "currentState" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "nextState" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "roles" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "tenantId" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "uuid" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          }
                        }
                      },
                      "applicationStatus" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "businessServiceId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "docUploadRequired" : {
                        "type" : "boolean"
                      },
                      "isStartState" : {
                        "type" : "boolean"
                      },
                      "isTerminateState" : {
                        "type" : "boolean"
                      },
                      "sla" : {
                        "type" : "long"
                      },
                      "state" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "tenantId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "uuid" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      }
                    }
                  },
                  "stateSla" : {
                    "type" : "long"
                  },
                  "tenantId" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  }
                }
              },
              "id" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "landArea" : {
                "type" : "long"
              },
              "noOfFloors" : {
                "type" : "long"
              },
              "oldPropertyId" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "owners" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "ownershipCategory" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "propertyId" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "propertyType" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "source" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "status" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "superBuiltUpArea" : {
                "type" : "long"
              },
              "tenantData" : {
                "properties" : {
                  "OfficeTimings" : {
                    "properties" : {
                      "Mon - Fri" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "Sat" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      }
                    }
                  },
                  "address" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "city" : {
                    "properties" : {
                      "code" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "ddrName" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "districtCode" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "districtName" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "districtTenantCode" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "latitude" : {
                        "type" : "float"
                      },
                      "localName" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "longitude" : {
                        "type" : "float"
                      },
                      "municipalityName" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "name" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "regionCode" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "regionName" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "ulbGrade" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      }
                    }
                  },
                  "code" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "contactNumber" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "description" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "domainUrl" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "emailId" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "facebookUrl" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "helpLineNumber" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "imageId" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "logoId" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "name" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "pdfContactDetails" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "pdfHeader" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "pincode" : {
                    "type" : "long"
                  },
                  "twitterUrl" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "type" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  }
                }
              },
              "tenantId" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "units" : {
                "properties" : {
                  "active" : {
                    "type" : "boolean"
                  },
                  "arv" : {
                    "type" : "long"
                  },
                  "constructionDetail" : {
                    "properties" : {
                      "builtUpArea" : {
                        "type" : "float"
                      },
                      "carpetArea" : {
                        "type" : "long"
                      },
                      "constructionDate" : {
                        "type" : "long"
                      },
                      "constructionType" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "plinthArea" : {
                        "type" : "long"
                      },
                      "superBuiltUpArea" : {
                        "type" : "long"
                      }
                    }
                  },
                  "floorNo" : {
                    "type" : "long"
                  },
                  "id" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "occupancyDate" : {
                    "type" : "long"
                  },
                  "occupancyType" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "tenantId" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "unitType" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "usageCategory" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  }
                }
              },
              "usageCategory" : {
                "type" : "text",
                "fields" : {
                  "keyword" : {
                    "type" : "keyword",
                    "ignore_above" : 256
                  }
                }
              },
              "ward" : {
                "properties" : {
                  "boundaryNum" : {
                    "type" : "long"
                  },
                  "children" : {
                    "properties" : {
                      "area" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "boundaryNum" : {
                        "type" : "long"
                      },
                      "code" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "label" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "name" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "pincode" : {
                        "type" : "long"
                      }
                    }
                  },
                  "code" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "label" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "name" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  }
                }
              },
              "workflow" : {
                "properties" : {
                  "action" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "assignes" : {
                    "type" : "text",
                    "fields" : {
                      "keyword" : {
                        "type" : "keyword",
                        "ignore_above" : 256
                      }
                    }
                  },
                  "state" : {
                    "properties" : {
                      "actions" : {
                        "properties" : {
                          "action" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "auditDetails" : {
                            "properties" : {
                              "createdBy" : {
                                "type" : "text",
                                "fields" : {
                                  "keyword" : {
                                    "type" : "keyword",
                                    "ignore_above" : 256
                                  }
                                }
                              },
                              "createdTime" : {
                                "type" : "long"
                              },
                              "lastModifiedBy" : {
                                "type" : "text",
                                "fields" : {
                                  "keyword" : {
                                    "type" : "keyword",
                                    "ignore_above" : 256
                                  }
                                }
                              },
                              "lastModifiedTime" : {
                                "type" : "long"
                              }
                            }
                          },
                          "currentState" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "nextState" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "roles" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "tenantId" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "uuid" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          }
                        }
                      },
                      "applicationStatus" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "auditDetails" : {
                        "properties" : {
                          "createdBy" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "createdTime" : {
                            "type" : "long"
                          },
                          "lastModifiedBy" : {
                            "type" : "text",
                            "fields" : {
                              "keyword" : {
                                "type" : "keyword",
                                "ignore_above" : 256
                              }
                            }
                          },
                          "lastModifiedTime" : {
                            "type" : "long"
                          }
                        }
                      },
                      "businessServiceId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "docUploadRequired" : {
                        "type" : "boolean"
                      },
                      "isStartState" : {
                        "type" : "boolean"
                      },
                      "isStateUpdatable" : {
                        "type" : "boolean"
                      },
                      "isTerminateState" : {
                        "type" : "boolean"
                      },
                      "sla" : {
                        "type" : "long"
                      },
                      "state" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "tenantId" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      },
                      "uuid" : {
                        "type" : "text",
                        "fields" : {
                          "keyword" : {
                            "type" : "keyword",
                            "ignore_above" : 256
                          }
                        }
                      }
                    }
                  }
                }
              }
            }
          }
        }
    }
  }
}

Assessment of Property

For overview Please refer to the parent file - Property Services

Key Functionality

The assessment set of services inside the property module is used for assessing the value of a property in a given time frame and collect taxes for the same. Assessment is a snapshot of Property for a given transaction on that Property. These APIs provide functionalities to create/update/search the assessments. An assessment cannot exist without property.

Configuration Details

Configs

Assessment shares most of the configs with Property as mentioned above, only exclusive properties are mentioned in this section.

name

value

description

assessment id format

PB-AS-[cy:yyyy-MM-dd]-[SEQ_EG_PT_ASSM]

kafka create assessment topic

save-pt-assessment

kafka update assesmsent topic

update-pt-assessment

assessment.workflow.enabled

true/false

Workflow integration can be controlled by the following two properties

assessment.workflow.trigger.param

usageCategory,occupancyType,occupancyDate

PERSISTER CONFIG: https://raw.githubusercontent.com/egovernments/configs/master/egov-persister/assessment-persister.yml?token=AE4Z2KFWEQBDCUY6AZLGGIK6AM3QQ``

serviceMaps:
  serviceName: property-services
  mappings:
  - version: 1.0
    description: Persists assessment details to eg_pt_asmt_assessment table
    fromTopic: save-pt-assessment
    isTransaction: true
    queryMaps:

    - query: INSERT INTO eg_pt_asmt_assessment(id, tenantid, assessmentnumber, financialyear, propertyid, status, source, channel, assessmentdate, additionaldetails, createdby, createdtime, lastmodifiedby, lastmodifiedtime) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?);
      basePath: Assessment
      jsonMaps:

      - jsonPath: $.Assessment.id

      - jsonPath: $.Assessment.tenantId

      - jsonPath: $.Assessment.assessmentNumber

      - jsonPath: $.Assessment.financialYear

      - jsonPath: $.Assessment.propertyId

      - jsonPath: $.Assessment.status

      - jsonPath: $.Assessment.source

      - jsonPath: $.Assessment.channel

      - jsonPath: $.Assessment.assessmentDate

      - jsonPath: $.Assessment.additionalDetails
        type: JSON
        dbType: JSONB

      - jsonPath: $.Assessment.auditDetails.createdBy

      - jsonPath: $.Assessment.auditDetails.createdTime

      - jsonPath: $.Assessment.auditDetails.lastModifiedBy

      - jsonPath: $.Assessment.auditDetails.lastModifiedTime



    - query: INSERT INTO eg_pt_asmt_unitusage (tenantid, id, assessmentid, unitid, usagecategory, occupancytype, occupancydate, active, createdby, createdtime, lastmodifiedby, lastmodifiedtime) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?);
      basePath: Assessment.unitUsageList.*
      jsonMaps:

      - jsonPath: $.Assessment.unitUsageList.*.tenantId

      - jsonPath: $.Assessment.unitUsageList.*.id

      - jsonPath: $.Assessment[?({id} in @.unitUsageList[*].id)].id

      - jsonPath: $.Assessment.unitUsageList.*.unitId

      - jsonPath: $.Assessment.unitUsageList.*.usageCategory

      - jsonPath: $.Assessment.unitUsageList.*.occupancyType

      - jsonPath: $.Assessment.unitUsageList.*.occupancyDate

      - jsonPath: $.Assessment.unitUsageList.*.active

      - jsonPath: $.Assessment.unitUsageList.*.auditDetails.createdBy

      - jsonPath: $.Assessment.unitUsageList.*.auditDetails.createdTime

      - jsonPath: $.Assessment.unitUsageList.*.auditDetails.lastModifiedBy

      - jsonPath: $.Assessment.unitUsageList.*.auditDetails.lastModifiedTime



    - query: INSERT INTO eg_pt_asmt_document (id, tenantid, entityid, documenttype, filestoreid, documentuid, status, createdby, lastmodifiedby, createdtime, lastmodifiedtime) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?);
      basePath: $.Assessment.documents.*
      jsonMaps:

      - jsonPath: $.Assessment.documents.*.id

      - jsonPath: $.Assessment.tenantId

      - jsonPath: $.Assessment.id

      - jsonPath: $.Assessment.documents.*.documentType

      - jsonPath: $.Assessment.documents.*.fileStoreId

      - jsonPath: $.Assessment.documents.*.documentUid

      - jsonPath: $.Assessment.documents.*.status

      - jsonPath: $.Assessment.documents.*.auditDetails.createdBy

      - jsonPath: $.Assessment.documents.*.auditDetails.lastModifiedBy

      - jsonPath: $.Assessment.documents.*.auditDetails.createdTime

      - jsonPath: $.Assessment.documents.*.auditDetails.lastModifiedTime



  - version: 1.0
    description: Updates assessment details to eg_pt_asmt_assessment table
    fromTopic: update-pt-assessment
    isTransaction: true
    queryMaps:

    - query: INSERT INTO eg_pt_asmt_assessment_audit SELECT *, (SELECT extract(epoch from now())) FROM eg_pt_asmt_assessment WHERE id = ?;
      basePath: Assessment
      jsonMaps:

      - jsonPath: $.Assessment.id


    - query: INSERT INTO eg_pt_asmt_unitusage_audit SELECT *, (SELECT extract(epoch from now())) FROM eg_pt_asmt_unitusage WHERE id = ?;
      basePath: Assessment.unitUsageList.*
      jsonMaps:

      - jsonPath: $.Assessment.unitUsageList.*.id


    - query: UPDATE eg_pt_asmt_assessment SET financialyear = ?, status = ?, source = ?, assessmentDate = ?, additionaldetails = ?, lastmodifiedby = ?, lastmodifiedtime = ? WHERE id = ?;
      basePath: Assessment
      jsonMaps:

      - jsonPath: $.Assessment.financialYear

      - jsonPath: $.Assessment.status

      - jsonPath: $.Assessment.source

      - jsonPath: $.Assessment.assessmentDate

      - jsonPath: $.Assessment.additionalDetails
        type: JSON
        dbType: JSONB

      - jsonPath: $.Assessment.auditDetails.lastModifiedBy

      - jsonPath: $.Assessment.auditDetails.lastModifiedTime

      - jsonPath: $.Assessment.id




    - query: INSERT INTO eg_pt_asmt_unitusage (tenantid, id, assessmentId, unitid, usageCategory, occupancyType, occupancyDate, active, createdby, createdtime, lastmodifiedby, lastmodifiedtime) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) ON CONFLICT (id) DO UPDATE SET usageCategory = ?, occupancyType = ?, occupancyDate = ?, active = ?, lastmodifiedby = ?, lastmodifiedtime = ?;
      basePath: Assessment.unitUsageList.*
      jsonMaps:

      - jsonPath: $.Assessment.unitUsageList.*.tenantId

      - jsonPath: $.Assessment.unitUsageList.*.id

      - jsonPath: $.Assessment[?({id} in @.unitUsageList[*].id)].id

      - jsonPath: $.Assessment.unitUsageList.*.unitId

      - jsonPath: $.Assessment.unitUsageList.*.usageCategory

      - jsonPath: $.Assessment.unitUsageList.*.occupancyType

      - jsonPath: $.Assessment.unitUsageList.*.occupancyDate

      - jsonPath: $.Assessment.unitUsageList.*.active

      - jsonPath: $.Assessment.unitUsageList.*.auditDetails.createdBy

      - jsonPath: $.Assessment.unitUsageList.*.auditDetails.createdTime

      - jsonPath: $.Assessment.unitUsageList.*.auditDetails.lastModifiedBy

      - jsonPath: $.Assessment.unitUsageList.*.auditDetails.lastModifiedTime

      - jsonPath: $.Assessment.unitUsageList.*.usageCategory

      - jsonPath: $.Assessment.unitUsageList.*.occupancyType

      - jsonPath: $.Assessment.unitUsageList.*.occupancyDate

      - jsonPath: $.Assessment.unitUsageList.*.active

      - jsonPath: $.Assessment.unitUsageList.*.auditDetails.lastModifiedBy

      - jsonPath: $.Assessment.unitUsageList.*.auditDetails.lastModifiedTime




    - query: INSERT INTO eg_pt_asmt_document (id, tenantid, entityid, documenttype, filestoreid, documentuid, status, createdby, lastmodifiedby, createdtime, lastmodifiedtime) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) ON CONFLICT (id) DO UPDATE documenttype = ?, documentuid = ?, status = ?, lastmodifiedby = ?, lastmodifiedtime = ?;
      basePath: $.Assessment.documents.*
      jsonMaps:

      - jsonPath: $.Assessment.documents.*.id

      - jsonPath: $.Assessment.tenantId

      - jsonPath: $.Assessment.id

      - jsonPath: $.Assessment.documents.*.documentType

      - jsonPath: $.Assessment.documents.*.fileStoreId

      - jsonPath: $.Assessment.documents.*.documentUid

      - jsonPath: $.Assessment.documents.*.status

      - jsonPath: $.Assessment.documents.*.auditDetails.createdBy

      - jsonPath: $.Assessment.documents.*.auditDetails.lastModifiedBy

      - jsonPath: $.Assessment.documents.*.auditDetails.createdTime

      - jsonPath: $.Assessment.documents.*.auditDetails.lastModifiedTime

      - jsonPath: $.Assessment.documents.*.documentType

      - jsonPath: $.Assessment.documents.*.documentUid

      - jsonPath: $.Assessment.documents.*.status

      - jsonPath: $.Assessment.documents.*.auditDetails.lastModifiedBy

      - jsonPath: $.Assessment.documents.*.auditDetails.lastModifiedTime

Workflow Config

The first property switches workflow on or off, while the second property provides a way to control which field change can trigger the workflow. A businessService needs to be created using the workflow /egov-workflow-v2/egov-wf/businessservice/_create API.

Sample businessService create API body for Assessment workflow:

{
  "RequestInfo": {
    "apiId": "Rainmaker",
    "action": "",
    "did": 1,
    "key": "",
    "msgId": "20170310130900|en_IN",
    "requesterId": "",
    "ts": 1513579888683,
    "ver": ".01",
    "authToken": "b39181b1-5c6b-484a-b825-6be2f62012b8"
  },
 "BusinessServices": [
    {
      "tenantId": "pb",
      "businessService": "ASMT",
      "business": "pt-services",
      "businessServiceSla": 172800000,
      "states": [
        {
          "sla": null,
          "state": null,
          "applicationStatus": null,
          "docUploadRequired": false,
          "isStartState": true,
          "isTerminateState": false,
          "isStateUpdatable": true,
          "actions": [
            {
              "action": "INITIATE",
              "nextState": "INITIATED",
              "roles": [
                "CITIZEN",
                "PT_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "INITIATED",
          "applicationStatus": "INITIATED",
          "docUploadRequired": false,
          "isStartState": true,
          "isTerminateState": false,
          "actions": [
            {
              "action": "APPLY",
              "nextState": "APPLIED",
              "roles": [
                "CITIZEN",
                "PT_CEMP"
              ]
            },
            {
              "action": "INITIATE",
              "nextState": "INITIATED",
              "roles": [
                "CITIZEN",
                "PT_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "APPLIED",
          "applicationStatus": "APPLIED",
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": false,
          "isStateUpdatable": true,
          "actions": [
            {
              "action": "FORWARD",
              "nextState": "FIELDINSPECTION",
              "roles": [
                "PT_DOC_VERIFIER"
              ]
            },
            {
              "action": "REJECT",
              "nextState": "REJECTED",
              "roles": [
                "PT_DOC_VERIFIER"
              ]
            },
            {
              "action" : "SENDBACKTOCITIZEN",
              "nextState" : "INITIATED",
              "roles":["PT_DOC_VERIFIER"]
            }
          ]
        },
        {
          "sla": null,
          "state": "REJECTED",
          "applicationStatus": "REJECTED",
          "isStateUpdatable": false,
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": true
        },
        {
          "sla": 86400000,
          "state": "FIELDINSPECTION",
          "applicationStatus": "FIELDINSPECTION",
          "docUploadRequired": false,
          "isStartState": false,
          "isStateUpdatable": true,
          "isTerminateState": false,
          "actions": [
            {
              "action": "FORWARD",
              "nextState": "PENDINGAPPROVAL",
              "roles": [
                "PT_FIELD_INSPECTOR"
              ]
            },
            {
              "action": "REJECT",
              "nextState": "REJECTED",
              "roles": [
                "PT_FIELD_INSPECTOR"
              ]
            },
            {
              "action": "SENDBACK",
              "nextState": "APPLIED",
              "roles": [
                "PT_FIELD_INSPECTOR"
              ]
            }
          ]
        },
        {
          "sla": 43200000,
          "state": "PENDINGAPPROVAL",
          "applicationStatus": "PENDINGAPPROVAL",
          "docUploadRequired": false,
          "isStartState": false,
          "isStateUpdatable": false,
          "isTerminateState": false,
          "actions": [
            {
              "action": "APPROVE",
              "nextState": "PENDINGPAYMENT",
              "roles": [
                "PT_APPROVER"
              ]
            },
            {
              "action": "REJECT",
              "nextState": "REJECTED",
              "roles": [
                "PT_APPROVER"
              ]
            },
            {
              "action": "SENDBACK",
              "nextState": "FIELDINSPECTION",
              "roles": [
                "PT_APPROVER"
              ]
            }
          ]
        },
        {
          "sla": 43200000,
          "state": "PENDINGPAYMENT",
          "applicationStatus": "PENDINGPAYMENT",
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": false,
          "isStateUpdatable": false,
          "actions": [
            {
              "action": "PAY",
              "nextState": "APPROVED",
              "roles": [
                "CITIZEN",
                "PT_CEMP",
                "SYSTEM_PAYMENT"
              ]
            },
            {
              "action": "ADHOC",
              "nextState": "PENDINGPAYMENT",
              "roles": [
                "PT_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "APPROVED",
          "applicationStatus": "APPROVED",
          "isStateUpdatable": false,
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": true
        }
      ]
    }
  ]
}

Other system-level configs are the same as PT-Registry as mentioned above.

Notification Configs

Payment Notification

    {
      "code": "PT_NOTIFICATION_PAYMENT_FAIL",
      "message": "Dear Citizen, Your payment of Rs. <insert amount to pay> for Property Tax Unique ID <insert ID> has failed. Your assessment is pending. Please try again. Ignore this message if you have completed your payment. You can pay your Property Tax online here - <payLink>",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    },
    {
      "code": "PT_NOTIFICATION_PAYMENT_OFFILE",
      "message": "Dear Citizen,  Your Property Tax payment of Rs. <amount>  has been accepted. Mode of Payment: <insert mode of payment> Pending Amount: <Enter pending amount>.",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    },
    {
      "code": "PT_NOTIFICATION_PAYMENT_ONLINE",
      "message": "Dear Citizen, Your payment of Rs.< insert amount paid> with payment transaction id < insert payment transaction id from PG> has been made successfully. Assessment for Property Tax Unique ID <insert Property Tax Assessment ID>  was succesful. Property Tax due is Rs.<pt due>.",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    },
    {
      "code": "PT_NOTIFICATION_PAYMENT_PARTIAL_OFFLINE",
      "message": "Dear Citizen,  Your Property Tax payment of Rs. <amount>  has been accepted. Mode of Payment: <insert mode of payment> Pending Amount: <Enter pending amount>. You can pay your Property Tax online here - <payLink>",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    },
    {
      "code": "PT_NOTIFICATION_PAYMENT_PARTIAL_ONLINE",
      "message": "Dear Citizen, Your payment of Rs.< insert amount paid> with payment transaction id < insert payment transaction id from PG> has been made successfully. Assessment for Property Tax Unique ID <insert ID>  was succesful. Property Tax due is Rs.<pt due>. You can pay your Property Tax here - <payLink>",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    }

Assessment Notification

    {
      "code": "ASMT_APPLIED",
      "message": "Applied",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    },
    {
      "code": "ASMT_APPROVED",
      "message": "Approved",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    },
    {
      "code": "ASMT_CREATE",
      "message": "Dear {OWNER_NAME}, Your assessment with {ASSESSMENTNUMBER} for financial year {FINANCIALYEAR} and property id {PROPERTYID} is created.",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    },
    {
      "code": "ASMT_UPDATE",
      "message": "Dear {OWNER_NAME}, Your assessment with {ASSESSMENTNUMBER} for financial year {FINANCIALYEAR} and property id {PROPERTYID} is reassessed.",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    },
    {
      "code": "ASMT_MSG_APPLIED",
      "message": "Dear {OWNER_NAME}, Your assessment with {ASSESSMENTNUMBER} for financial year {FINANCIALYEAR} and property id {PROPERTYID} is updated to {STATUS}.",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    },
    {
      "code": "ASMT_MSG_APPROVED",
      "message": "Dear {OWNER_NAME}, Your assessment with {ASSESSMENTNUMBER} for financial year {FINANCIALYEAR} and property id {PROPERTYID} is {STATUS}.",
      "module": "rainmaker-pt",
      "locale": "en_IN"
    }

For adding localization for any status append ASMT_ prefix to the status and for adding a message for any status add ASMT_MSG_ before the status.

Assessment ****(Property Calculator) -

The calculator service Prepares and property tax and files the demand in the billing service for payment. It has the ‘estimate’ API to give the estimated property tax without persisting data and a calculated API to create demand for payments.

The calculator service PT Calculator

Integration

Integration Scope

Assessment integration helps citizens to assess their property with ease and helps them verify their tax values by themselves which gives more control to the citizens and hep the municipality collect taxes with ease.

Integration Benefits

Easy to create and simple process of self-assessment to avoid the hassle.
Integrated payment for multiple years enables by digit platform.

Steps to Integration

Customer can create an assessment on a given property using the /assessment/_create
Search the assessment and its workflow status by using /assessment/_searchendpoint
/assessment/_update endpoint to update the assessment and its workflow states as per need.

Reference Docs

please refer to the property document Property Services | Doc-Links

API LIST

Title

Link

/assessment/_create

/assessment/_update

/assessment/_search

Citizen User Manual

Learn how to add new property, assess or transfer property and pay property tax

Citizens and CE

Citizens represent individuals, communities, or business entities who are the system end-users. The PT module allows property owners to register their property details online. These details are then used for various property-related transactions.

The Citizen or CE role can -

Add New Property

Citizens or CE can add new property details through the DIGIT web portal or the DIGIT mobile app.

The system will display the Required Documents - Property Tax list. Note the list of documents valid for address, identity, registration, usage, special category, and occupancy proofs.

Click on the Print button to get a hard copy of the documents list for reference. Click on the Apply button to proceed with adding your property. The form sections are available on the top of the page.

Add Property Form Sections

The add property form page contains various sections that include

Property Address
Property Details
Owner Details
Document Info
Summary

Enter the following information in the Property Address section.

The City field displays the registered city by default. Click on the drop-down list to select a different city. Enter the House/Shop No., Building/Colony Name, Street Name, Locality/Mohalla, and the Pincode. Enter the Existing Property ID in case there is a legacy property ID available for the listed property.

Click on the Next button to move to the next section.

Enter the following details in the Property Details section

Select the applicable Property Usage Type and the Property Type from the drop-down list available.

Check Yes or No to indicate Whether rainwater harvesting structure provided on the property? Enter Vasika No. and Vasika Date if applicable. Enter Allotment Letter No. and Allotment Date if applicable.

Enter Firm/Business Name if the property is listed as commercial or institutional. Enter any information in the Remarks field. Check the box Do you have any inflammable material stored on your property? if it is true. Check the box adjacent to Height of property more than 36 feet? if it is true. Fill in the Unit details if the selected property usage type is Commercial, Institutional, Other Non-Residential, or Residential.

The Unit Usage Type by default accepts the Property Usage Type value. Select the applicable Sub Usage Type for the listed property in case of Commercial or Institutional properties. Select the most applicable option for the type of Occupancy. Enter the Built-up-area (sq ft) value of the property. Select Floor to identify the relevant floor of the property. Click on +Add One More Unit button to add more units.

Click on the Next button to proceed to enter the Owner Details.

Enter the following information in the Owner Details section. Select the relevant Type of Ownership. Enter the Owner’s Name.

Check the applicable Gender of the owner. Enter the owner’s Mobile No. and Guardian’s Name. Select Relationship of the owner with the guardian. Enter the applicable Special Category. Enter the owner’s Email Id and the Correspondence Address. Check the Same as property address box if the correspondence address is the same as the address of the listed property. The Correspondence Address field is auto-populated in that case.

Click on the Next button to move to the Documents section.

Upload the required documents in the Documents section of the application form. In the Select Document field, select the type of document you are uploading for Address Proof, Identity Proof, Registration Proof, Usage Proof, and Construction Proof.

Click on the Upload File button to upload the documents.

Click on the Next button to proceed to the next section.

Click on the Add Property button once the details are reviewed and corrected. The system displays the New Property Successfully Added acknowledgement message.

The Property ID is available along with this message.

Click on the Download button on top of the message box to download the application. Click on the Print button to print the application.

Search Property

To search for a submitted application or track the status of submitted applications navigate to the Property Tax home page. There are two search options available. Users can search by property or application.

To Search by Property click on the Search Property tab. Enter the ULB. The system displays the registered City or ULB details by default. Enter any of the following search parameters or combinations to refine the search for property. Enter the Owner Mobile No. or the Unique Property ID allotted by the system. Enter the Existing Property ID if there is any legacy ID linked to the property.

Click on the Search button to view the results. Click on the Reset button to renew search with different parameters.

To Search by Application click on the Search Application tab.

Enter any of the following search parameters or combinations to refine the search for property. Enter the Application No. or the Owner Mobile No. or the Unique Property ID.

Click on the Search button to view the search results. Click on the Reset button to renew search with different parameters.

The search results show the filtered list of property entries along with the application Status.

An Active Status means the listed property is pending for further action. Inworkflow status means there is some action going on for the listed property and hence it is not accessible for any other action. Once the action is complete the status will change to Active.

Click on the Unique Property ID or Application No. hyperlink to access the property details.

Assess Property

Listed properties are assessed every financial year to calculate the property tax amount.

To assess property navigate to the Property Tax >> Assess & Search menu option on the sidebar. Alternatively, click on the Property Tax card on the Home page. Enter the required search parameter to refine your search for properties.

Click on the Search button to view the results. Click on the relevant Unique Property ID.

Scroll down the Property Information page to view the property details. Expand the Assessment History panel to view the previous assessment details.

Click on the Re-Assess button if you want to reassess the property. Expand the Payment History panel to view earlier payments made for the listed property.

Click on the Download Receipt button to get a soft copy of the listed payment. Expand the Application History panel to view the property application details.

Click on the View Details button to fetch application details. Click on the Assess Property button.

Select the relevant Financial Year.

The panel will display the Property Tax Amount details.

Click on the Add Rebate button to apply any rebates or discounts on the tax amount. This feature is not available for the citizens.

Enter any Additional Charges amount, if applicable. Select the appropriate Reason for Charges. Enter any Additional Rebate amount, if applicable. Select the appropriate Reason for Rebate.

Click on the Submit button to apply the rebate or charges to the tax amount. Click on the Calculation Details button to view the calculation logic applied for calculating the tax amount.

Click on the OK button to move back to the Assessment page.

Click on Assess Property once you complete reviewing all details. The system will display the assessment success acknowledgement message.

Click on the Proceed to Payment button to pay the property tax. Else click on the Home button to navigate back to the home page.

Pay Property Tax

Applicants have to pay the property tax once the property is assessed for the specified financial year.

To make payment for property tax click on the Proceed to Payment button after the property assessment is complete. The Payment Collection Details panel displays the tax Fee Details.

Enter the payment details. The system allows you to pay by cash, cheque, or credit/debit card. Click on the Cash, Cheque, Credit/Debit Card tab depending on the preferred payment method.

Enter payment details as requested on the screen. Click on the Generate Receipt button to confirm the payment. The screen displays the success acknowledgement message along with the Payment Receipt No.

Once the payment is complete the Property Tax Receipt is issued. Click on the Download or Print button to download or print the tax Payment Receipt.

Transfer Property Ownership

The PT module allows users to transfer the ownership of property.

To transfer the ownership of property search for the property by entering the Unique Property ID or any other search parameter. Click on the Unique Property ID to open the application. Scroll down the Property Information page. Click on the Transfer Ownership button available in the Owner Details panel.

The system will display the list of Required Documents - Transfer to Ownership.

Click on the Print button to print the list of documents. Click on the Transfer Ownership button to proceed with the mutation process. The Transfer of Ownership form page is displayed.

The application timeline shows three sections -

Transfer Details
Document Upload
Summary

The Transfer Details page includes three panels -

Transferor Details - This panel displays the current owner details.

Transferee Details - This panel requires the user to input the details of the individual to whom the property is to be transferred.

Enter the following details in the form -

Select applicable Ownership Type. Enter the Name, Gender, and Mobile No. of the transferee. Enter Guardian’s Name of the transferee and the Relationship with Guardian. Enter the Email address of the transferee. Select the relevant Special Applicant Category. Enter the Correspondence Address of the transferee.

Registration Details - This panel requires the user to input the registration details in context to the transfer of the property ownership.

Enter the following details in the form.

Select Reason for Property Transfer. Enter Property Market Value, the Registration Document No. and the Registration Document Issue Date. Enter the Registration Document Value. Enter any Remarks.

Click on the Next Step button to move to the Document Upload section.

Select Document you want to upload for Address Proof, Identity Proof, and Registration Proof. Click on the Upload File button to upload the copy of scanned documents.

Click on the Next Step button to move to the Summary section.

The Summary page will display the filled-in application details. Scroll down the page to review the information entered. Click on the Previous Step button to go back and make any changes in the form.

Click on the Submit button once all details are reviewed. The screen will display the application success message. Click on the Download button on top of the message box to download the application. Click on the Print button to print the application.

Edit Property

To make any changes in the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on the Application No. to open the application. Scroll down the form to review the filled in details.

Click on the Edit Property button available at the bottom of the page. Change any details in the form as required. Click on the Update Property button once all changes are complete.

Water Services

Overview

Water service is the egov application, which helps and gives flexibility to municipal and citizen to handle the water service like apply for water connection, search water connection. The application will go on different stages that the state can verify by given roles, If that role can take the action then the application will go to the next state. Based on the state, a citizen will get a notification (SMS and in-app ). Citizens also can pay for application fees or employees can collect the fee for the application.

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 water service persister config path added in it
PSQL server is running and database is created to store water connection / application data
knowledge of eGov-mdms service, eGov-persister, eGov-idgen, eGov-sms, eGov-email,eGov-user, eGov-localization, eGov-workflow-service will be helpful.

Key Functionalities

Apply for a water connection.
Searching for water connections.
Apply for Property creation.
Can take different action based on state (Workflow)
Notification based on the application state.

Environment Variables

Description

egov.waterservice.createwaterconnection

This variable contains the kafka topic name which is used to create new water connection application in the system.

egov.waterservice.updatewaterconnection

This variable contains the kafka topic name which is used to update the existing water connection application in the system.

egov.waterservice.updatewaterconnection.workflow.topic

This variable contains the kafka topic name which is used to update the process instance of the water connection application.

egov.idgen.wcapid.name

This variable contain the idgen format name for water application

egov.idgen.wcapid.format

This variable contain the idgen format for water application ex:- WS/[CITY.CODE]/[fy:yyyy-yy]/[SEQ_EGOV_COMMON]

egov.idgen.wcid.name

This variable contain the idgen format name for water connection

egov.idgen.wcid.format

This variable contain the idgen format for water connection ex:- WS_AP/[CITY.CODE]/[fy:yyyy-yy]/[SEQ_EGOV_COMMON]

Interaction Diagram

To Do

Table UML diagram

****

Configuration Details

MDMS configuration

ws-services-calculation
ws-services-masters
PropertyTax

master-config.json for water service

"ws-services-masters": {
    "connectionCategory": {
      "masterName": "connectionCategory",
      "isStateLevel": true,
      "uniqueKeys": [
        "$.code"
      ]
    },
    "connectionType": {
      "masterName": "connectionType",
      "isStateLevel": true,
      "uniqueKeys": [
        "$.code"
      ]
    },
    "waterSource": {
      "masterName": "waterSource",
      "isStateLevel": true,
      "uniqueKeys": [
        "$.code"
      ]
    },
    "billingPeriod": {
      "masterName": "billingPeriod",
      "isStateLevel": true,
      "uniqueKeys": [
        "$.billingCycle"
      ]
    },
    "waterSourceWithSubSource": {
      "masterName": "waterSourceWithSubSource",
      "isStateLevel": true,
      "uniqueKeys": []
    }
  },
  "ws-services-calculation": {
    "WaterCess": {
      "masterName": "WaterCess",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "Interest": {
      "masterName": "Interest",
      "isStateLevel": true,
      "uniqueKeys": [
        "$.fromFY"
      ]
    },
    "Rebate": {
      "masterName": "Rebate",
      "isStateLevel": true,
      "uniqueKeys": [
        "$.fromFY"
      ]
    },
    "Penalty": {
      "masterName": "Penalty",
      "isStateLevel": true,
      "uniqueKeys": [
        "$.fromFY"
      ]
    },
    "WCBillingSlab": {
      "masterName": "WCBillingSlab",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "WS_CHARGE": {
      "masterName": "WS_CHARGE",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "WS_TIME_PENALTY": {
      "masterName": "WS_TIME_PENALTY",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "WS_WATER_CESS": {
      "masterName": "WS_WATER_CESS",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "MeterStatus": {
      "masterName": "MeterStatus",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "WS_Round_Off": {
      "masterName": "WS_Round_Off",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "PlotSizeSlab": {
      "masterName": "PlotSizeSlab",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "PropertyUsageType": {
      "masterName": "PropertyUsageType",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "FeeSlab": {
      "masterName": "FeeSlab",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "RoadType": {
      "masterName": "RoadType",
      "isStateLevel": true,
      "uniqueKeys": []
    },
    "CalculationAttribute": {
      "masterName": "CalculationAttribute",
      "isStateLevel": true,
      "uniqueKeys": []
    }
  }

Property creation through WNS module https://github.com/egovernments/egov-mdms-data/blob/DEV/data/pb/PropertyTax/PTWorkflow.json

Persister configuration

https://github.com/egovernments/configs/blob/DEV/egov-persister/water-persist.yml https://github.com/egovernments/configs/blob/master/egov-persister/water-meter.yml

Actions & Role Action Mapping

Actions

[
  {
      "id": {{PLACEHOLDER1}},
      "name": "Create Water Connection",
      "url": "/ws-services/wc/_create",
      "displayName": "Create Water COnnection",
      "orderNumber": 0,
      "enabled": false,
      "serviceCode": "ws-services",
      "code": "null",
      "path": ""
    },
    {
      "id": {{PLACEHOLDER2}},
      "name": "Search Water Connection",
      "url": "/ws-services/wc/_search",
      "displayName": "Search Water COnnection",
      "orderNumber": 0,
      "enabled": false,
      "serviceCode": "ws-services",
      "code": "null",
      "path": ""
    },
    {
      "id": {{PLACEHOLDER3}},
      "name": "Update Water Connection",
      "url": "/ws-services/wc/_update",
      "displayName": "Update Water COnnection",
      "orderNumber": 0,
      "enabled": false,
      "serviceCode": "ws-services",
      "code": "null",
      "path": ""
    }
]

Role Action Mapping

[
  {
      "rolecode": "CITIZEN",
      "actionid": {{PLACEHOLDER1}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "CITIZEN",
      "actionid": {{PLACEHOLDER2}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "CITIZEN",
      "actionid": {{PLACEHOLDER3}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_CEMP",
      "actionid": {{PLACEHOLDER1}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_CEMP",
      "actionid": {{PLACEHOLDER2}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_CEMP",
      "actionid": {{PLACEHOLDER3}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_DOC_VERIFIER",
      "actionid": {{PLACEHOLDER2}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_DOC_VERIFIER",
      "actionid": {{PLACEHOLDER3}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_FIELD_INSPECTOR",
      "actionid": {{PLACEHOLDER2}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_FIELD_INSPECTOR",
      "actionid": {{PLACEHOLDER3}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_APPROVER",
      "actionid": {{PLACEHOLDER2}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_APPROVER",
      "actionid": {{PLACEHOLDER3}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_CLERK",
      "actionid": {{PLACEHOLDER2}},
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "WS_CLERK",
      "actionid": {{PLACEHOLDER3}},
      "actioncode": "",
      "tenantId": "pb"
    }
]

Workflow business service config

Create businessService (workflow configuration) using the __/businessservice/_create. Following is the product configuration for water service

{
  "RequestInfo": {
    "apiId": "Rainmaker",
    "action": "",
    "did": 1,
    "key": "",
    "msgId": "20170310130900|en_IN",
    "requesterId": "",
    "ts": 1513579888683,
    "ver": ".01",
    "authToken": "{{Auth_Token}}"
  },
  "BusinessServices": [
    {
      "tenantId": "pb",
      "businessService": "NewWS1",
      "business": "ws-services",
      "businessServiceSla": 259200000,
      "states": [
        {
          "sla": null,
          "state": null,
          "applicationStatus": null,
          "docUploadRequired": false,
          "isStartState": true,
          "isTerminateState": false,
          "isStateUpdatable": false,
          "actions": [
            {
              "action": "INITIATE",
              "nextState": "INITIATED",
              "roles": [
                "CITIZEN",
                "WS_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "INITIATED",
          "applicationStatus": "INITIATED",
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": false,
          "isStateUpdatable": true,
          "actions": [
            {
              "action": "SUBMIT_APPLICATION",
              "nextState": "PENDING_FOR_DOCUMENT_VERIFICATION",
              "roles": [
                "CITIZEN",
                "WS_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "PENDING_FOR_CITIZEN_ACTION",
          "applicationStatus": "PENDING_FOR_CITIZEN_ACTION",
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": false,
          "isStateUpdatable": true,
          "actions": [
            {
              "action": "RESUBMIT_APPLICATION",
              "nextState": "PENDING_FOR_DOCUMENT_VERIFICATION",
              "roles": [
                "CITIZEN",
                "WS_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "PENDING_FOR_DOCUMENT_VERIFICATION",
          "applicationStatus": "PENDING_FOR_DOCUMENT_VERIFICATION",
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": false,
          "isStateUpdatable": true,
          "actions": [
            {
              "action": "VERIFY_AND_FORWARD",
              "nextState": "PENDING_FOR_FIELD_INSPECTION",
              "roles": [
                "WS_DOC_VERIFIER"
              ]
            },
            {
              "action": "REJECT",
              "nextState": "REJECTED",
              "roles": [
                "WS_DOC_VERIFIER"
              ]
            },
            {
              "action": "SEND_BACK_TO_CITIZEN",
              "nextState": "PENDING_FOR_CITIZEN_ACTION",
              "roles": [
                "WS_DOC_VERIFIER"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "REJECTED",
          "applicationStatus": "REJECTED",
          "isStateUpdatable": false,
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": true
        },
        {
          "sla": 86400000,
          "state": "PENDING_FOR_FIELD_INSPECTION",
          "applicationStatus": "PENDING_FOR_FIELD_INSPECTION",
          "docUploadRequired": false,
          "isStartState": false,
          "isStateUpdatable": true,
          "isTerminateState": false,
          "actions": [
            {
              "action": "VERIFY_AND_FORWARD",
              "nextState": "PENDING_APPROVAL_FOR_CONNECTION",
              "roles": [
                "WS_FIELD_INSPECTOR"
              ]
            },
            {
              "action": "REJECT",
              "nextState": "REJECTED",
              "roles": [
                "WS_FIELD_INSPECTOR"
              ]
            },
            {
              "action": "SEND_BACK_FOR_DOCUMENT_VERIFICATION",
              "nextState": "PENDING_FOR_DOCUMENT_VERIFICATION",
              "roles": [
                "WS_FIELD_INSPECTOR"
              ]
            }
          ]
        },
        {
          "sla": 43200000,
          "state": "PENDING_APPROVAL_FOR_CONNECTION",
          "applicationStatus": "PENDING_APPROVAL_FOR_CONNECTION",
          "docUploadRequired": false,
          "isStartState": false,
          "isStateUpdatable": true,
          "isTerminateState": false,
          "actions": [
            {
              "action": "APPROVE_FOR_CONNECTION",
              "nextState": "PENDING_FOR_PAYMENT",
              "roles": [
                "WS_APPROVER"
              ]
            },
            {
              "action": "REJECT",
              "nextState": "REJECTED",
              "roles": [
                "WS_APPROVER"
              ]
            },
            {
              "action": "SEND_BACK_FOR_FIELD_INSPECTION",
              "nextState": "PENDING_FOR_FIELD_INSPECTION",
              "roles": [
                "WS_APPROVER"
              ]
            }
          ]
        },
        {
          "sla": 43200000,
          "state": "PENDING_FOR_PAYMENT",
          "applicationStatus": "PENDING_FOR_PAYMENT",
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": false,
          "isStateUpdatable": false,
          "actions": [
            {
              "action": "PAY",
              "nextState": "PENDING_FOR_CONNECTION_ACTIVATION",
              "roles": [
                "CITIZEN",
                "WS_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "PENDING_FOR_CONNECTION_ACTIVATION",
          "applicationStatus": "PENDING_FOR_CONNECTION_ACTIVATION",
          "isStateUpdatable": true,
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": false,
          "actions": [
            {
              "action": "ACTIVATE_CONNECTION",
              "nextState": "CONNECTION_ACTIVATED",
              "roles": [
                "WS_CLERK"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "CONNECTION_ACTIVATED",
          "applicationStatus": "CONNECTION_ACTIVATED",
          "isStateUpdatable": false,
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": true
        }
      ]
    }
  ]
}

Workflow for property creation through Water and Sewerage Module

{
    "BusinessServices": [
    {
      "tenantId": "pb",
      "businessService": "PT.CREATEWITHWNS",
      "business": "PT",
      "businessServiceSla": null,
      "states": [
        {
          "sla": null,
          "state": null,
          "applicationStatus": "INWORKFLOW",
          "docUploadRequired": false,
          "isStartState": true,
          "isTerminateState": false,
          "isStateUpdatable": false,
          "actions": [
            {
              "action": "OPEN",
              "nextState": "INITIATED",
              "roles": [
                "CITIZEN",
                "WS_CEMP",
                "SW_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "INITIATED",
          "applicationStatus": "INWORKFLOW",
          "docUploadRequired": false,
          "isStartState": true,
          "isTerminateState": false,
          "isStateUpdatable": true,
          "actions": [
            {
              "action": "SUBMIT",
              "nextState": "APPROVED",
              "roles": [
                "EMPLOYEE",
                "CITIZEN",
                "SW_CEMP",
                "WS_CEMP"
              ]
            },
            {
              "action": "BACK",
              "nextState": "INWORKFLOW",
              "roles": [
                "EMPLOYEE",
                "CITIZEN",
                "SW_CEMP",
                "WS_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "INWORKFLOW",
          "applicationStatus": "INWORKFLOW",
          "docUploadRequired": false,
          "isStartState": true,
          "isTerminateState": false,
          "isStateUpdatable": true,
          "actions": [
            {
              "action": "SUBMIT",
              "nextState": "APPROVED",
              "roles": [
                "EMPLOYEE",
                "CITIZEN",
                "SW_CEMP",
                "WS_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "APPROVED",
          "applicationStatus": "ACTIVE",
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": true,
          "isStateUpdatable": false,
          "actions": null
        }
      ]
    }
  ]
}

Indexer config for water-service

The indexer provides the facility for indexing the data to elastic search. https://github.com/egovernments/configs/blob/DEV/egov-indexer/water-service.yml https://github.com/egovernments/configs/blob/DEV/egov-indexer/water-services-meter.yml

Setup

Write the configuration for water service. https://github.com/egovernments/configs/blob/DEV/egov-indexer/water-service.yml https://github.com/egovernments/configs/blob/DEV/egov-indexer/water-services-meter.yml
Provide the absolute path of the checked-in file to DevOps, to add it to the file-read path of egov-indexer. The file will be added to the egov-indexer's environment manifest file for it to be read at the start-up of the application.
Run the egov-indexer app, Since it is a consumer, it starts listening to the configured topics and indexes the data.

Modify connection

After connection activation or legacy connection, we can edit the connection. This process based on a defined workflow. Any action is based on defined roles on the action level. For edit connection, we need to upload some supporting documents and mandatory info.

Workflow config for edit connection

Create businessService (workflow configuration) using the __/businessservice/_create. Following is the product configuration for editing the water connection.

{
  "RequestInfo": {
    "apiId": "Rainmaker",
    "action": "",
    "did": 1,
    "key": "",
    "msgId": "20170310130900|en_IN",
    "requesterId": "",
    "ts": 1513579888683,
    "ver": ".01",
    "authToken": "{{Auth_Token}}"
  },
  "BusinessServices": [
    {
      "tenantId": "pb",
      "businessService": "ModifyWSConnection",
      "business": "ws-services",
      "businessServiceSla": 259200000,
      "states": [
        {
          "sla": null,
          "state": null,
          "applicationStatus": null,
          "docUploadRequired": false,
          "isStartState": true,
          "isTerminateState": false,
          "isStateUpdatable": false,
          "actions": [
            {
              "action": "INITIATE",
              "nextState": "INITIATED",
              "roles": [
                "WS_CEMP"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "INITIATED",
          "applicationStatus": "INITIATED",
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": false,
          "isStateUpdatable": true,
          "actions": [
            {
              "action": "SUBMIT_APPLICATION",
              "nextState": "PENDING_FOR_APPROVAL",
              "roles": [
                "WS_CEMP"
              ]
            }
          ]
        },
        {
          "sla": 86400000,
          "state": "PENDING_FOR_APPROVAL",
          "applicationStatus": "PENDING_FOR_APPROVAL",
          "docUploadRequired": false,
          "isStartState": false,
          "isStateUpdatable": true,
          "isTerminateState": false,
          "actions": [
            {
              "action": "APPROVE_CONNECTION",
              "nextState": "APPROVED",
              "roles": [
                "WS_APPROVER"
              ]
            },
            {
              "action": "REJECT",
              "nextState": "REJECTED",
              "roles": [
                "WS_APPROVER"
              ]
            },
            {
              "action": "SEND_BACK",
              "nextState": "INITIATED",
              "roles": [
                "WS_APPROVER"
              ]
            }
          ]
        },
        {
          "sla": null,
          "state": "REJECTED",
          "applicationStatus": "REJECTED",
          "isStateUpdatable": false,
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": true
        },
        {
          "sla": null,
          "state": "APPROVED",
          "applicationStatus": "APPROVED",
          "isStateUpdatable": false,
          "docUploadRequired": false,
          "isStartState": false,
          "isTerminateState": true
        }
      ]
    }
  ]
}

Notification

Notification will be sent to the property owners and connection holders based on different application states.

Capturing connection holders

We can add connection holders to the water connection which will be the owner of the connection. We can fill in the connection holders' details or we can just make the property owner to the connection holder.

The connection holder will get a notification based on a different state of the application. We are pushing the data of the connection holders in the user service too.

Multiple Road Type Support We can add road cutting details of multiple roads to the water connection. For each road that goes undercutting process, we have to fill their road type details and road cutting area. Based on this information, the application one-time fee estimate is calculated.

Deployment Details

Add MDMS configs required for water connection registration and restart MDMS service.
Deploy the latest version of ws-services service.
Add water-service and water-services-meter persister yaml path in persister configuration and restart persister service.
Add Role-Action mapping for API’s.
Create businessService (workflow configuration) according for trade water connection, modify water connection
Add ws-service indexer yaml path in indexer service configuration and restart indexer service.

Integration Details

Integration Scope

This ws-service module is used to manage water service connections against a property in the system.

Integration Benefits

Provide backend support for the different water connection registration process.
Mseva and SMS notifications on application status changes.
Elastic search index for creating visualizations and Dashboards.
Supports workflow which is configurable

Steps to Integration

To integrate, host of ws-service module should be overwritten in helm chart.
/ws-services/wc/_create should be added as the create endpoint for creating water application/connection in the system
/ws-services/wc/_search should be added as the search endpoint. This method handles all requests to search existing records depending on different search criteria
/ws-services/wc/_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

Title

Link

API Swagger Documentation

Water Calculator Service

API List

Title

Link

/ws-services/wc/_create

/ws-services/wc/_update

/ws-services/wc/_search

(Note: All the API’s are in the same postman collection therefore same link is added in each row)

W&S Implementation Guide

Section 1: Executive Summary

Overview of the Product

Access to clean and safe water is one of the basic needs of citizens. Each Urban local body has been mandated with catering to the water and sanitation needs of its citizens. The computerized and automatic Water and Sewerage system offered by eGov enables citizens who seek to apply and pay for water and sewerage connections within any Urban Local Body with a transparent, speedy, hassle-free and user-friendly procedure. The ULB officials can now sanction connections, generate bills and collect payments for water and sewerage connections more efficiently. (For details on product features refer to Section-2)

Implementation Methodology for W&S

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

Stage Zero-program setup and onboarding is a pre-requisite for the initiative to kick-off and requires setup of the governance model, implementation team and decision regarding other significant elements of the initiative like funding and procurement process. Stage One of the initiative requires scoping of the initiative and decide on the priorities for implementation by the State/UT implementation Team. In Stage Two, the W&S team is appointed and its processes are standardized. In Stage Three, the State/UT Team will work upon identifying and finding solutions to the significant gaps in the product offered w.r.t. to the need of the State/UT. Configuration and customization of the product offered in the primary objective of stage four. This involves working on various aspects of UT-specific needs and incorporating them into the product suite offered. In Stage Four and Five, post doing UAT and including all the necessary feedback on the product, the roll-out of the product is done at the State/UT level(Go Live) from a couple of ULBs to pan State/UT coverage. In Stage Six of sustenance and ongoing improvement, key activities are adoption and governance tracking with the planning of ongoing sustenance. (For details on implementation plan refer to Section-3).

Critical Success Factors for implementation

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

Section 2: Water and Sewerage (W&S) Product - Overview

The Water and Sewerage (W&S) module provides a digital interface to apply for water and sewerage connections and pay the water and sewerage charges for connection/s. It can be used by the citizens, Urban Local Body (ULB) counter employees and field employees, and ULB Administrators to accomplish their specific tasks. It is available as a mobile and web-based application. The W&S product features can be broadly classified as the following modules:

Registration, Login and Creation of User Profile
Application for new Water/Sewerage connection
Searching for a Connection
Modifications to a Connection
Entering meter reading of metered connections
Generate Demand
Payments collection and Receipts
Dashboards and Reports

This module provides enables the following capabilities:

OTP Based Login for Citizen via Web/Mobile App
OTP Based Login for Employee via Web/Mobile App
Provision for language selection during first time registration for both Employee and
citizens
Provision of creating a personalized Profile for Citizens and employees on Web App
Login Credentials for the various hierarchy of employees
Role-based access for performing different actions relating to the W&S module

Module 2: Application for new Water & Sewerage connection

The system allows the Citizen / ULB user (with an appropriate role in the system) to apply for a New Water/Sewerage connection. The application goes through an approval workflow before it is available for various transactions in the system. The workflow to be followed for a new water/sewerage connection is configurable. In the workflow, the ULB official will generate the estimation notice. Once the payment is made, a work order will be generated.

Every time there is a change in the status of an application, the citizen will be intimated through in-app notifications, SMS and email. The citizen and employee can view the history of the various states that an application has been in and the comments added by the employee in each state of the application.

Module 3: Searching for a Connection

Only employees from the W&S department will be able to access the feature, to search for water and sewerage connections. They can search for any connection based on parameters such as:

Consumer number
Application number
Owner mobile number
Application status
From date
To date

The search result contains the Application number, Consumer number, Owner name, Status, Due amount and the Pay now option. The Employee can make payment for a connection on the citizen’s behalf using the ‘Pay Now’ option.

Citizens can also search for their connection in the portal. They can search using the Owners mobile number, Property ID, Consumer number etc. The search result yields, Owner’s Name, Address, Due amount and Pay option.

Module 4: Modifications to a Connection

The system facilitates the title transfer of water tap connection from one person to the other person. Title transfer of water tap connection directly depends upon Property tax. If title transfer is done in the property tax module then at the time of final approval, the changes will reflect in the W&S module automatically. After the title transfer has been completed successfully, subsequent bills will be generated with the details of the new owner/s.

Water tap change in usage happens when property type is changed from residential to Non-residential or from Non-residential to residential. Change in usage directly depends on the property tax module. If the property type is changed in the Property tax system then it will automatically reflect in the W&S system. When there is a change in the usage type, the subsequent bills will reflect the rates as per the updated usage category. When there is a change in the usage category in the middle of the billing cycle, pro-rata charges will be applied in the next billing period.

The change in connection category from non-metered to metered and vice-versa is also possible in the W&S system with the appropriate workflow configured to intimate all stakeholders of the change and collect any charges (if applicable) from the citizen.

Module 5: Entering meter reading of metered connections

On the W&S billing screen, there is a card called ‘Meter reading’. An employee can click on Meter reading which redirects the employee to the meter reading landing screen. The employee can search based on the following criteria:

ULB
Boundary Type
Boundary Value
Billing Year
Billing Period
Billing Period Value
Consumer No.

This feature facilitates the employee to search for all results based on desired criteria. The search result yields the following values: consumer number, owner name, meter status, last reading, current reading, date and consumption.

The employee can edit meter status, current reading, date and consumption under certain conditions. Based on this information the employee can generate the bills for connections.

Module 6: Generate Demand

In the system, there is a feature to generate demand under the billing section. Generate demand has a search feature in which the connections can be searched for which demand has been already generated. An employee can view, also edit those demands based on certain conditions.

The system has the capability to configure the demand generation as an automatic or a manual process. In the automatic process, the demand generation for non-metered connections is automatically done periodically. For metered connection as soon as the employee enters the meter reading and clicks on ‘SAVE’, the demand is generated.

Any success/ failure to generate demand triggers an automatic notification to the concerned ULB officials via email. Also, the demand generation cycle, demand generation date and officials who should receive the notifications can be configured.

Module 7: Payments collection and Receipts

The citizen can pay for dues by searching his/her connection. In search results, the citizen can click on pay, which redirects to the summary page of the dues. After this, the citizen can pay for dues online. An employee can also collect the payment on the citizen’s behalf. After searching for the desired connection, clicking on pay will redirect the employee to the common payment page. The employee can print the receipt after the payment is successfully collected. The citizen is also notified and gets a download receipt link in the notification.

Module 8: Closure of Water Connection

If the Water tap owner has got his own water source then the water tap owner can initiate for Water tap connection closure permanently. So, that tap will be closed permanently and demand would not be generated for the connection. Application for the closing of water tap connection is accepted only with the latest water charges receipt and clearing of old dues.

Module 9: Dashboards and Reports

The state-level administrator can keep track of relevant metrics by using dashboards. Dashboards for W&S can be accessed by a state-level user under login.

The dashboard has these components:

Financial Indicators
- W&S Total collections YTD
- Water Collection
- Sewerage Collection
- Water - Demand vs Collection (Monthly trend)
- Sewerage - Demand vs Collection (Monthly trend)
Municipal Adoption
- W & S: No. Of ULBs Live
- W & S: Total Number of ULBs
- Water Consumers by Connection Type
- W & S Consumers by Usage Type
- Total Collections by Source
- Total Collections by Mode
- W & S Adoption : ULB Wise
Today’s Collections
- W&S Total collections: Today
- Water Charges - Total collections: Today
- Sewerage Charges - Total collections: Today
- W&S - Total No. of Receipts: Today
- Water - Total No. of Receipts: Today
- Sewerage - Total No. of Receipts: Today
- Mode wise W&S collections: Today
- W&S ULB wise collections: Today

Water & Sewerage (W&S) Implementation Methodology for the State of xxx

Section 3 Water and Sewerage (W&S) Implementation Methodology

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

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

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

Seven Stages of Implementation

Stage 0 - Program Setup/Onboarding

There is a set of initial critical activities that are undertaken on receiving a letter of Enrollment from the State/Union Territory. Successful completion of these activities assures that the program is started with crucial personnel, System Integrator(SI) Teams and funds.

Stage 0 - Program Setup/ On-Boarding

Duration

4-6 weeks

Entry Criteria

Acceptance Letter/MoU by State

Exit Criteria

Finalize Water and Sewerage Program Vision
Finalize funding for the program
Define State/Union Territory -specific procurement process
Water and Sewerage Cell appointment. Consisting of :
- Domain expert
- Nodal officer (EO/ Commissioner/ Senior Official)
- Program Head
System Integrator(SI) Team sign-up/onboarding

Vision:

Define the value proposition of the programme for the state
Define the time frame within which the state needs to:
- Go live
- Scale pan-state
Define Year-on-Year(YoY) Financial Targets

System Integrator(SI) Sign-up:

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

Stage 1 - Program Kick-Off

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

Stage 1 - Program kick-off

Duration

4-6 weeks

Entry Criteria

Program setup (Stage 0) is complete
SI Team signed-up

Key Activities

Project kick-off meeting and stakeholders consultation
Identify & agree on scope and exclusions
Finalize the approach on obtaining the W&S Connection Legacy Data (At least from the Pilot ULBs)
Identify pilot ULBs
Product Walkthroughs
Define Project Steering Committee Structure and Project Governance process
Define phases of rollout/ deployment
State Baseline Data (As per the Module)
Pilot ULBs Specific Product Data Configuration
Agreement on Product Feature Priorities and high-level delivery timelines
Assessment of all on ground W&S process along (1) citizen services/channels around it (2) Integration with other Department process
Finalize Program Success Metrics for Rollout and Adoption and Governance adhering to the vision of the program
Internal Capacity Building, program logistics at State and ULBs, as per the current scenario

Exit Criteria

Publish the program charter
- Implementation plan agreement with priority applications and broad timelines
- Program Governance Model
- Program Success Metrics
- Capacity Building
W&S Cell formation and appointment
Finalizing the strategy for W&S Connections Legacy Data
Master Data preparation/collection kickoff from Pilot ULBs
Cloud Infrastructure procured
Project Office Space allocated
Program Branding( Name, Logo, Tagline etc.)

Note

1) State Baseline Data (As per the Module): A Baseline Template is provided to collect certain vital information like no. of transactions, revenue collected in the last FYs, collection mode, budget data, etc. This data is vital for various analysis at the state level. This data must be collected pre-rollout. The baseline data collection templates will be provided to the state/SI Team.

2) ULBs Specific Product Data Configuration: This Master data is required from the Product Perspective to go live. For eg: Connection Legacy Data, Boundary Data, List of Employees, Rates etc. Master Data Template will be provided for the collection of this particular data type.

Stage 2 - Solution Design

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

Stage 2 - Solution Design

Duration

4-6 weeks

Entry Criteria

Program Charter
W&S Cell appointment

Key Activities

Standardization of all W&S processes, if needed
Initiate policy change and Process Re-engineering, if needed based on identified improvements
Conduct Product familiarization workshop
Initiate collection of Master Data (Legacy & Product Based) from pilot ULBs
Finalize data migration/collection/sync-up approach (State needs to provide a signoff)
Finalize data validation approach (State needs to provide a signoff)
Building capacity for basic understanding of resources and tools required to be used

Exit Criteria

Publish the W&S processes, data template/workflows (State needs to provide a signoff)
Finalization of Roll-out plan(in different phases)
Solution agreement for required state/UT-specific customisations
Finalization of Initial Reporting and Design (State needs to provide a signoff)
Finalization of Dashboard KPIs (State needs to provide a signoff)
Sign-off on data approach( Data collection/migration/correction/sync-up/validation) from the state
Detailed project plan

Stage 3 - Configuration & Customization

This stage consists of a series of developments in accordance with the detailed project plan to ensure the smooth functioning of the customised product. Preparation for the testing and data collection of the product UAT is complete. Further monitoring and maintenance strategies are put in place.

Stage 3 – Configuration & Customization

Duration

6-8 weeks

Entry Criteria

Product Configuration Report has been Signed Off by the State/UT
Detailed Project Plan set up in accordance with master data collection and environment setup

Key Activities

Setting up development environments
Development/customization of reports and dashboards
Development/Integration of portal
Third-Party Integrations (Payment gateway, Handheld/pos device)
Updation of user manuals and other key documents
Preparation & execution of Test Cases
Setup monitoring, support & maintenance processes and tools
W&S and Legacy data collection from Pilot ULBs (at least)
Training for basic understanding of resources and tools required to be used (system-related)
- identify ULB level nodal officers for day to day support
Legacy Data Validation signoff from the state on Data Validation
- Post this migration exercise will be taken up for water/sewerage connections
- Migration and verification of Pilot ULB data as per data provided by the State

Exit Criteria

Data Validation Signoff by the state, post which the Legacy Data will be uploaded to UAT
Configured/Customized product that is ready for UAT
Monitoring, support & maintenance of Dashboards
- finalization of Initial Reporting and Dashboard KPIs

Stage 4 - UAT & Go Live

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

Stage 4 – UAT & Go Live

Duration

2-3 weeks

Entry Criteria

Configured/Customized product ready for UAT
Pilot ULB Officials (Associated with W&S) are available for UAT & Training

Key Activities

UAT Environment Setup
Sign off from Pilot ULBs on the Migrated Connection Legacy Data during UAT
Issues/bug identification and resolution
Regression UAT and Sign off from Pilot ULBs/ State
Setting up the Production environment
Setting up Support Center & processes (Help Desk)
Training (Users, trainer)
- master trainers identified from the ground for simultaneous training
Training the Support Resources
Marketing & promotion activities
Go Live & launch event
Setup of review and monitoring cadence/team
- Usage/review/Dashboard/Field Visits

Exit Criteria

UAT Sign-off & Go Live for Pilot ULBs
Setup of review and monitoring cadence

Stage 5 – Rollout

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

Note: The rollout phase needs to be detailed out for iterative activities of onboarding ULBs in batches.

Stage 5 – Rollout

Duration

5-6 weeks

Entry Criteria

The pilot has been successful in the State/UT
- there are less than 3 open critical incidents (issues) with respect to product, implementation and data

Key Activities

ULB configurations phase-wise as per the Project Plan
Phase wise migration and verification of ULB data (as per the Data Agreement signoff, provided by the State)
Logistics planning for training
Establishment of bug ticketing tool for resolving ground-level issues by the state team
Training the Users at the district level
Pan State Roll-Out - Phase wise
Stabilise product

Exit Criteria

State/UT wide Rollout in batches:

Adoption tracking & Review Cadence operational
Help Desk Effectiveness assured
Critical Bugs fixed
Program Success Metrics Tracking Kick-started

Note: Only once all the stages are complete in one batch of the rollout of around 30 ULBs, the next batch begins. There are multiple phases of rollout. The second batch begins after the first batch has successfully fulfilled all the criteria of the Rollout Phase. Typical timelines for closure of rollout in each batch is 5-6 weeks (in a batch of 30 ULBs).

Stage 6 – Sustenance and Ongoing Improvement

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

Stage 6- Sustenance and Ongoing Improvement

Duration

Ongoing process

Entry Criteria

Rollout Phase 1( First set of 30 ULBs where rollout will happen after Pilot)

Key Ongoing Activities

Adoption Review Meetings as per the vision defined for the program
W&S Cell Focuses on Using data for:
tracking field issues and performance data to identify improvements
identify additional Integrations around W&S to make processes more robust towards enhancing W&S revenues (e.g Upstream and downstream Processes)
Conduct Weekly Review Meeting between ULBs, State Team for feedback on the system, which must be chaired by the Program Head
- Plans of ongoing Sustenance in Place with respect to :
  - Funding
  - IT support (infra, helpdesk, ongoing enhancements)
  - Process Effectiveness and Improvements

Section 4: Roles and Responsibilities – W&S Cell, NUS Team & System Integrator (SI)Team

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

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

Resource requirements for the W&S cell required to be formed by the UT

Resource Name

No. Of Resources

Project Head

Domain Expert

Nodal Officer

MIS Expert

Note: Designation mentioned above are as per designations known driving W&S implementation at the State/UT level as explained below. (These are the preferred figures in the case of Domain Expert, 2 people are subject to availability)

Project Head: Is the Head of the W&S Cell who will drive the project from the State/UT Side
Domain Expert: Person who is well aware of the on-ground scenario, well versed with the act, GOs passed, Prevalent Business processes, Deviations from the acts, Rates/ slabs applicable
Nodal officer (EO/Commissioner/ Senior Official): the product coordinator to drive the project centrally. Monitor usage post Go Live- point of escalation for Implementation Team, Seasoned and worked in Multiple ULBs on various modules and has a good understanding of W&S, Facilitate and Track data collection Post Go Live, Monitors and facilitates the adoption of the application. point of contact for eGov, SI and at the HQ level.
MIS Expert: Day to day tracking of the program, data entry, reporting and review to senior officials

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

System Integrator (SI) Team: SI Team will be responsible for the rollout of the initiative in the UT, providing end to end support to the State/UT w.r.t. The implementation of the products in the ULBs.

Guidelines to read the table are mentioned on the next page:

Execute - One who owns the accountability to complete the activity
Consult - One who may initiate, guide and in the process, handhold the execution of the activity

Stage 0 - Program Setup/ On-Boarding

Task/Activity

eGov

State Leadership

Appoint W&S Cell

Consult

Execute

Finalize funding for the program

Consult

Execute

Define state/UT-specific procurement process

Consult

Execute

System Integrator(SI) Team sign-up/onboarding

Consult

Execute

Finalize Water and Sewerage Program Vision

Consult

Execute

Note: Stage 0 is where the W&S cell and SI team are formed, hence there are only two entities playing a role which is that of eGov and the state leadership. Once the W&S cell and SI team are finalized, their role begins in the following stages.

Stage 1 - Program kick-off

Task/Activity

eGov

W&S Cell

SI Team

Identify & agree on scope and exclusions

Consult

Identify pilot ULBs

Execute

Consult

Project kick-off meeting and stakeholders consultation

Execute

Consult

Product Walkthroughs

Consult

Execute

Define Project Steering Committee structure and Project Governance process

Consult

Execute

Define phases of deployment/ rollout

Consult

Execute

Agreement on Product Feature Priorities and high-level delivery timelines

Consult

Execute

Assessment of all W&S process along

(1) citizen services/channels around it

(2) Integration with other department processes

Consult

Execute

Finalize Program Success Metrics for Adoption and Governance adhering to the vision of the program

Consult

Execute

Internal Capacity Building, program logistics at State and ULBs, as per the current scenario

Execute

Consult

Stage 2 - Solution Design

Task/Activity

eGov

W&S Cell

SI Team

Standardisation of all W&S processes, if needed

Consult

Execute

Initiate policy change and Process Re-engineering, if needed based on identified improvements

Consult

Execute

Consult

Conduct Product familiarization workshop

Consult

Execute

Initiate collection of master data from pilot ULBs

Consult

Execute

Finalize data migration/collection/sync-up approach

Consult

Execute

Finalize data validation approach

Execute

Consult

Building capacity for basic understanding of resources and tools required to be used

Execute

Consult

Stage 3 – Configuration & Customization

Task/Activity

eGov

W&S Cell

SI Team

Setting up development environments

Consult

Execute

Development/customization of reports and dashboards

Consult

Execute

Development/Integration of portal

Consult

Execute

Third-Party Integrations (Payment gateway, Handheld/pos device)

Consult

Execute

Updation of user manuals and other key documents

Consult

Execute

Preparation & execution of Test Cases

Consult

Execute

Setup monitoring, support & maintenance processes, tools and dashboards

Consult

Execute

Data Migration for Pilot ULBs(at least)

Consult

Execute

Training for basic understanding of resources and tools required to be used (system-related)

Execute

Consult

Legacy Data Validation signoff from the state on Data Validation

Execute

Consult

Stage 4 – UAT & Go Live

Task/Activity

eGov

W&S Cell

SI Team

UAT Environment Setup

Consult

Execute

UAT Testing

Consult

Execute

Issues/bug resolution

Consult

Execute

UAT Sign off from Pilot ULBs

Execute

Consult

Setting up the Production environment

Consult

Execute

Setting up Support Center & processes (Help Desk)

Execute

Consult

Training (Users, trainer)

Execute

Consult

Training the Support Resources

Consult

Execute

Marketing & promotion activities

Execute

Consult

Go Live & launch event

Execute

Consult

Setup of review and monitoring cadence/team Usage/ review/Dashboard/Field Visits

Execute

Consult

Stage 5: Rollout

Task/Activity

eGov

W&S Cell

SI Team

ULB configurations

Consult

Execute

Phase wise Migration and verification of ULB data

Execute

Consult

Logistics planning for training

Execute

Consult

Training the Users at the district level

Execute

Consult

Roll Out - All Locations

Consult

Execute

Stabilize product

Consult

Execute

Stage 6- Sustenance and Ongoing Improvement

Task/Activity

eGov

W&S Cell

SI Team

Adoption Review Meetings as per the vision defined for the program

Consult

Execute

Consult

W&S Cell Focuses on Using data for:

tracking field issues and performance data to identify improvements
identify additional Integrations around W&S to make processes more robust towards enhancing W&S revenues (e.g Upstream and downstream Processes)

Execute

Consult

Conduct Weekly Review Meeting between ULBs, State Team for feedback on the system, which must be chaired by the Program Head

Execute

Consult

Plans of ongoing Sustenance in Place with respect to :

Funding
IT support
Process Effectiveness and Improvements

Consult

Execute

Consult

Section 5: Overall Program Assumptions

Areas

Assumptions

Infrastructure

The actual Infra will be provided based on the questionnaire inputs received from the state
The state will take care of providing necessary project infrastructure and office facilities during the program for all on-site project Team members, which will be confirmed during the initiation phase. This includes workspace, office equipment (e.g., telephone with STD, fax machine, photocopy machine, etc.), stationery, PC/workstation, project LAN and internet access, etc.
The state will provide the necessary administrative support staff to carry out day-to-day project administration tasks, e.g., meeting rooms, Videoconferencing, etc.
The state should provide a Project Office and at least one conference room with a speaker phone throughout the Project Duration.

Project Scope

Any new requirements received from the State during the implementation phase will be handled through a change management process

State Team

The state will nominate a reasonably sized multifunctional Team from various departments of the State to be responsible for the implementation. The state Team would be required for information, validation, and execution through the implementation cycle and the Team members should be reasonably empowered to take decisions. Any delay in the decision-making process and the non-availability of the State Team may have an impact on the schedule.
The participants from State are expected to have a thorough understanding of the State’s internal processes.
The state will engage internal and external stakeholders required for this engagement and ensure their availability whenever needed.

Documentation

User education and training documentation will be delivered as per the default product documentation of the identified product versions.
The product manuals are expected to be shared with the State as part of the user manual.
All documentation would be in English only.

Training

Training to the end-users will be driven by the state Team.
The state will be responsible for providing the necessary infrastructure required for the Training, which includes the following readiness.
Training Rooms (Parallel Training Sessions) with Projector, White Board, Markers, Internet Connection, sufficient seating capacity, Desktop/Laptop for each participant and availability of Network for Trainees to connect to the server.

Implementation

The scope of the implementation will be limited to the services mentioned in Section 2.
eGov Team will have an identified SPOC for handling the first level of communication with the client unless discussed and agreed upon.
eGov Team will not be involved in defining the test cases or executing the test cases.
Necessary signoff would be provided by the state upon completion of the defined milestones.

Glossary

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

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

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

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

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

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

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

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

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

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

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

Fitment Study: GAP Study of the Existing/Required Field Process Vs Product

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

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

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

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

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

Pilot ULB: The ULBs selected for the pilot implementation are called pilot ULB.

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

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

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

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

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