Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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.
DIGIT is a microservices-based platform which 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.
Illustrative help docs
DIGIT modules follow structured workflows to allow easy tracking of applications and processes. This section walks you through the various workflows and features supported by each module.
An overview of the product and it's various modules
DIGIT offers several modules. Each module is designed to automate the manual workflows for various governance units.
DIGIT enables ULBs to be more effective and accountable—and to make better, data-driven decisions. The platform ensures both interoperability among ULBs and rapid development of new modules by a wide array of software partners.
Functional training events for DIGIT Municipal Finance and Online Building Permission System
DIGIT-Municipal Finance automates the entire financial management process. The module design complies with the National Municipal Accounting Manual to help municipalities maintain financial records of urban local bodies in tune with established policies and procedures.
Register for the DIGIT-Municipal Finance functional training event now.
Training Session Plan - Municipal Finance (March 9 - 10, 2021)
Session 1 - Municipal Finance Overview (30 mins) + Product Demo (1.5 hr)
Session 2 - Hands-on session (1 hr) + Self Practice (2 hr)
Session 3 - Clarification session (1.5 hr)
DIGIT-Online Building Permission System (OBPS) streamlines the building plan approval system right from the point of plan scrutiny to obtaining the Permit Order and Occupancy Certificate.
Register for the DIGIT-Online Building Permission System functional training event now.
Training Session Plan - OBPAS (March 16 - 17, 2021)
Session 1 - OBPAS Overview (30 mins) + Product Demo (1.5 hr)
Session 2 - Hands-on session (1 hr) + Self Practice (2 hr)
Session 3 - Clarification session (1.5 hr)
Individual event registration links are provided below. Click on the Register button to enrol for the sessions now.
Disclaimer
Registration for Session 1 is an essential pre-requisite for attending session 2 and session 3.
Session
Date
Time
Link
Finance Session 1
9 March 2021
2 - 4 pm
Finance Session 2
10 March 2021
11 - 12 pm
Finance Session 3
10 March 2021
4 - 5.30 pm
OBPS Session 1
16 March 2021
3 - 5 pm
OBPS Session 2
17 March 2021
11 - 12 pm
OBPS Session 3
17 March 2021
4 - 5 pm
The new features additions and enhancements in DIGIT 2.2 simplify the overall user experience. The updates serve to fulfil the overall goal of integrating various services in an effort to simplify citizen interaction with government agencies while improving the service delivery capabilities of individual departments.
DIGIT 2.2 release offers a revamped user interface, workflow integrations for streamlined module performance, custom-search capabilities, and rich analytics view.
For Citizens - The upgraded DIGIT platform provides citizens with additional capabilities in terms of integrated module workflows, and convenient bill payment options.
For States & ULBs - DIGIT 2.2 offers enhanced features in Property Tax, Water & Sewerage, HRMS, and Collections modules. User interface and backend enhancements allow streamlined performance across modules.
Notable enhancements include -
pay water & sewerage bills without registration or login
advanced search options for payment receipts across modules
file complaints easily through PGR module
cancel payment receipts in the Collections module
activate or deactivate employees in HRMS module
extended options for property mutation in PT module
user interface enhancements
Check out the DIGIT 2.2 Release Notes for more details.
Visit our Support pages for details on our partner support strategy.
The Building Plan Approval or BPA module allows stakeholders to submit building plans for approval by the concerned ULB departments. Construction or renovation of buildings is regulated by the Municipal Body in India. One must get permission from ULB prior to construction. This process involves submitting the building plan to ULB along with other documents. The ULB verifies the plan with other documents and approves the construction. The document which authorizes the construction is called Permit Order. One must have this permit order with him till the completion of construction. ULB officials will inspect various stages of construction and make sure it is compliant to the plan. Once the construction is complete, the Inspection Secretary inspects the building and releases a Completion certificate and finally an Occupancy Certificate. This completes the Building Plan Approval process.
The module supports the following key functions -
eDCR scrutiny
Online submission of application for building permits and occupancy certificates
Document Scrutiny
Field inspection report capture
Pay fee, generate permit order and occupancy certificate online
Inspection of applications and online status
Configurable workflows
Auto fee calculation
Send applications back to citizens or reject applications
Integration with NOC department
Refer to the table below to understand the different user roles and the scope of action linked to each role. The applicable user roles and action items can vary from one State to another. DIGIT customizes the workflows to suit the requirements defined at the State level.
This section of the user manual guides you through the user login process. Citizens can sign up to use the module through the online web portal or the mobile application login interface.
Refer to Logging Into DIGIT page to learn more about DIGIT user registration, logging in, editing user profile, and logging out.
This section guides you through the details of using the BPA module for each role. Click on the relevant role below to learn more about how to use the module.
Guide to user registration and user profile management
DIGIT users can sign up to use various modules through the online web portal or the mobile application login interface.
The first step to logging in to use the DIGIT modules is to register as a user.
Enter the ULB url in your browser. For instance, people of Punjab will use the link https://mseva.lgpunjab.gov.in/citizen/user/register to register for Punjab mSeva services.
Enter your Mobile Number, Name, City to register as a user. Click on the Continue button.
The system sends an OTP to the given mobile number. Enter the OTP.
Click on the Resend button on the screen in case you have not received your OTP. Click on the Get Started button after entering the OTP. You are now registered as a user in the DIGIT app.
Enter the URL https://egov-micro-qa.egovernments.org/citizen/ to log in to the system. Click on the Login button.
Enter your Mobile Number. Mobile app users can scan the QR code on the screen to file/track complaints. Click on the Continue button.
Enter the OTP sent to the registered mobile number. Click on the Continue button. You are logged in to the app.
Click on the drop-down icon next to your profile logo on the top right corner of the window to change your account details. Click on Edit Profile.
Enter your new user Name if you want to change the existing profile name. Select the applicable City from the drop-down list if you want to change your city settings. Enter your Email Id if you want to reset your email address.
Click on the Save button. The profile changes are saved and applied.
Users can change the language of the app from English to Hindi or the local language for ease and convenience. To change language click on the button labelled English adjacent to the profile icon.
Select the preferred language from the list of available languages. The system menu and prompts will now be displayed in the selected language.
To log out from the app click on the drop-down icon next to your profile logo on the top right corner of the window. Click on Logout.
You are logged out of the system.
This section illustrates the steps for different employee user roles at the ULB level
DV is responsible for verifying the supporting documents uploaded by the applicants or the counter employee on behalf of the applicant.
The DV can
Trade license applications are rejected if the supporting documents uploaded by the applicant fails to comply with the license requirements or the details provided in the form are incorrect.
To reject applications 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 Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The DV verifies and forwards the TL application to the Field Inspector if the DV finds all information and documents provided by the applicant correct.
To verify and forward 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 Take Action button available at the bottom of the page. Click on the Verify and Forward button. Select the relevant Assignee Name from the list of available employees for subsequent processing.
Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Verify and Forward button.
The TL application is assigned to the selected Assignee for subsequent processing.
To edit applications 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 Take Action button available at the bottom of the page. Click on the Edit button. Change any details in the form as required.
FI is responsible for verifying the field details provided by the applicants.
The FI can
FI sends back the applications to the citizens if some vital information is missing in the application or there is a mistake in the information provided.
To send applications back to the citizen 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 Take Action button available at the bottom of the page. Click on the Send Back to Citizen button. Enter any Comments stating why the application is sent back.
Click on the Upload Files button to upload any files or images in context to the application. Click on the Send Back to Citizen button.
The system displays a success acknowledgement message stating that the application is sent back to the initiator.
The FI can send back the TL application to the DV if there is any mistake or lapses in the document verification process.
To send back applications to the DV 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 Take Action button available at the bottom of the page. Click on the Send Back button.
Select the Assignee Name who will be responsible for verifying the application. Enter any Comments as additional information to the assignee stating why the application is sent back. Click on the Upload Files button to upload any files or images in context. Click on the Send Back button.
The application is assigned back to the selected assignee for verification of documents.
Trade license applications are rejected if the supporting documents uploaded by the applicant fails to comply with the license requirements or the details provided in the form are incorrect.
To reject applications 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 Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The FI verifies and forwards the TL application to the Approver if the information and documents provided by the applicant are correct.
To verify and forward 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 Take Action button available at the bottom of the page. Click on the Verify and Forward button. Select the relevant Assignee Name from the list of available employees for subsequent processing.
Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Verify and Forward button.
The TL application is assigned to the selected Assignee for subsequent processing.
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 Take Action button available at the bottom of the page. Click on the Edit button. Change any details in the form as required.
The Approver is responsible for the final approval of the TL application.
The Approver can
The Approver can send back the TL application to the FI or DV if there is any mistake or lapses in the document verification process.
To send back applications to the DV or FI 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 Take Action button available at the bottom of the page. Click on the Send Back button.
Select the Assignee Name who will be responsible for verifying the application. Enter any Comments stating why the application is sent back. Click on the Upload Files button to upload any files or images in context. Click on the Send Back button.
The application is assigned back to the selected assignee for verification of application.
Trade license applications are rejected if the supporting documents uploaded by the applicant fails to comply with the license requirements or the details provided in the form are incorrect.
To reject applications 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 Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The Approver signs off the TL application once the information and documents provided by the applicant are found correct. The TL Certificate is issued once the application is approved.
To approve 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 Take Action button available at the bottom of the page. Click on the Approve button.
Select the relevant Assignee Name from the list of available employees for subsequent processing. Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Approve button.
The TL application is approved and the TL Certificate is issued to the applicant. Click on the Download or Print button to download or print the TL Certificate.
The Digital Governance Platform
DIGIT Urban Stack is a set of Open APIs, services, and reference implementations, setup 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.
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.
Citizens represent individuals, groups, and communities who are the building owners or occupants. The BPA module provides the citizens with the scope to view building permit applications submitted by the stakeholders or architects. They can request the stakeholders to make any changes in the application if required. Citizens approve the applications and make the payment.
The citizen can -
The citizen user portal allows stakeholders to register themselves on the OBPAS system. Stakeholders constitute architects, builders, engineers, supervisors, or town planners. A unique license number is generated for each stakeholder on the system.
Citizens can have multi-stakeholder access. Hence, a citizen can be registered as an architect, a builder, and a normal citizen.
The registered stakeholder will have state-level access permission to apply for new building permits or occupancy certificates.
To register stakeholders
Navigate to Building Plan Approval option in the sidebar. Click on the Register Technical Person/Builder card on the screen.
Select the applicable Technical Person License Type in the License Details tab.
Click on the Next Step button to move to the next section of the registration form.
Enter the Applicant Name. Select the applicable Gender of the applicant. Enter the applicant’s Date of Birth, Mobile No., Email, and PAN No. Enter the Permanent Address of the applicant. Scroll down to enter the Correspondence Address. Check the Same as Permanent Address box if both addresses are the same. This will auto-populate the permanent address as the correspondence address.
Click on the Next Step button.
Click on the Upload File button to upload the Required Documents for verification. The list of required documents depends on the selected licensee type. Click on the Next Step button to move to the Summary page of the application.
Check the box in the Declaration section to testify the submitted details in the application. Click on the Submit button. The application is submitted for further processing. A unique Application Number is generated by the system for easy reference. Make a note of this number to track your application status and details.
Now click on the Proceed to Payment button to pay the registration fee.
Click on the Make Payment button.
Select the preferred payment option. Enter the required details to process the payment.
The system displays the payment success acknowledgement message along with the Payment Receipt No. Click on the Download or the Print button above to download or print the payment receipt.
The registration application is now in queue for document verification and approval by the Document Verifier and Approver.
Once the stakeholder is approved the applicant receives a notification. In addition, the Building Permit New Construction, Occupancy Certificate New Building Construction, and the DIGIT DCR Scrutiny options are added to the system menu.
The view application option allows citizens to review the application submitted by the stakeholder. In case there are any mistakes or changes required in the application the citizen can request the stakeholder to make these edits.
To view application status
Navigate to the Building Plan Approval option in the sidebar. Click on My Applications.
The My Applications screen will list all the applications submitted by the stakeholders on behalf of the citizen. The application details will display the status of each application.
Click on the View Details button below the relevant application details. Scroll down the application to view the submitted details. Click on the View History button on the top of the application to check the task and activity updates on the application.
Building permit applications submitted by the architects or any other stakeholders are routed to the citizens or the owner to verify details. The owner reviews the application details and sends back the application to the stakeholders if there is any mistake or any changes required in the application.
To request edits or approve application
Navigate to Building Plan Approval menu option in the sidebar. Click on My Applications.
Click on View Details button available for the relevant application.
Scroll down the application page to review the details submitted in the application.
Click on the Take Action button. Click on the Send to Architect button if some details require editing. This will open the Forward Application panel.
Enter the information you want to pass on to the architect in context to the application in the Comments section. Click on the Upload Files button to upload any supporting documents for the application.
Click on the Send To Architect button. The application is now in the stakeholder’s queue for further processing. Click on the Approve button if there are no changes required in the application. This will open the Forward Application panel.
Enter any Comments in context to the application in the panel. Click on the Upload Files button to upload any supporting documents for the application. Click on the Approve button. The system displays the approved success acknowledgement message.
The Make Payment button is enabled once the stakeholder submits the building permit or occupancy certificate application on behalf of the owner.
Click on the Application No. for which payment has to be made. The Payment Information details are available on the top of the application.
Click on the Make Payment button at the bottom of the screen.
The Payment Collection Details panel displays the Total Amount payable towards Application Fee along with the break-ups.
Select the relevant payment method. Enter the payment details.
The payment success acknowledgement message is displayed along with the Payment Receipt No. Click on the Download button to view or download the receipt in pdf format or click on the Print button to print the receipt.
Stakeholders represent the registered builders, architects, town planners, engineers or supervisors. The stakeholder role within the system encompasses submitting details for eDCR scrutiny, obtaining building permit orders, completion certificates, and occupancy certificates.
Stakeholders can
The DIGIT-DCR Scrutiny option in the BPA module allows stakeholders to upload and submit building plan diagrams. The scrutiny process checks if the drawing meets the required standards and applicable compliance guidelines. Once the scrutiny is complete, the plan is either approved or rejected depending on the scrutiny findings.
To submit plans and diagrams for DIGIT-DCR Scrutiny
Navigate to the eDCR Scrutiny menu option in the sidebar. Click on the New Building Plan Scrutiny card.
Select the applicable City for the proposed construction. Enter the Applicant Name. Click on the Upload File button to upload the plans and diagrams. The system accepts only .dxf files and maximum file size should not exceed 30MB.
Click on the Submit button to submit the plans for scrutiny. Click on the Clear Form button to start a fresh application.
The system displays a success acknowledgement message along with a unique Building Plan Scrutiny Number. Note this number for future reference. This number is required at the time of applying for a new building permit.
Click on the Download or Print button to download or print the Scrutiny Report.
The system might reject the submitted building plan if there are any errors or omissions in the plan. Make the corrections and upload the plan for scrutiny once again. Click on the Download or Print button to download or print the Scrutiny Report.
Click on the Create Building Permit Application button to apply for a permit.
Follow the same steps to apply for Occupancy Certificate eDCR Scrutiny for New Building.
Stakeholders can apply for low-risk building permit applications following the same steps outlined above. Permits for building plans marked as low risk are processed immediately and the stakeholders can download the permit order after submitting the required documents and details.
The key parameters defining low-risk application categories include -
Height of the building is less than 10 meters
The building construction site does not fall in any airport zone
The building occupancy type is purely residential
The permit order issued for low-risk applications can be revoked by the State or ULB authorities if any inconsistencies or instances of non-compliance found during the verification and inspection process.
Stakeholders can apply for building permits for new construction once the eDCR Scrutiny is approved.
To apply for building permits for new construction
Navigate to the Building Plan Approval menu option in the sidebar.
Click on Building Permit New Construction card. Select the City for the proposed construction in the popup window.
Alternatively, click on the Create Building Permit Application button once the DIGIT-DCR scrutiny is accepted.
The Apply for Building Permit form contains 5 sections - Basic Details, Scrutiny Details, Owner Info, Document and NOC Details, and Summary.
Occupancy, Application Type, Risk Type, and Service Type information in the Basic Details panel is auto-populated from the listed DIGIT-DCR scrutiny report. The Risk Type is Low in the case of low-risk permit applications.
Enter any additional comments in the Remarks field.
The system populates the current date as Application Date by default. In the Location Details panel enter Building/Colony Name, Street Name, Mohalla, Pincode, and GIS coordinates. The City field is auto-populated.
In the Details of Plot panel the Plot Area, and Khata No. are auto-populated from the listed eDCR reference document. Enter the Holding No., Plot No. (MSP), and Land Registration Details.
Click on the Next Step button to move to the Scrutiny Details section of the application form. The Scrutiny Details page displays the DIGIT DCR Number, a clickable link to download the Uploaded Diagram, and the Scrutiny Report.
The Occupancy, Sub-Occupancy, and Usage details are auto-populated from the eDCR report. Click on the Next Step button to move to the Owner Info section.
In the Owner Details panel select the applicable Owner Type and Type of Owner Subtype.
Enter the owner’s Mobile No., Applicant Name, Gender, Date of Birth, Email, Guardian’s Name, Relationship with guardian, PAN No., and Correspondence Address in the Owner Information panel.
Check the Is Primary Owner box if the person filling the application details is the primary owner. All system notifications will be sent to the primary owner.
Click on the Next Step button to move to the Document and NOC Details section.
Select the appropriate document type for each of the Required Documents categories. Click on the Upload File button to upload the documents. The permissible document file formats include .pdf and. jpeg extensions.
Scroll down the page to upload the Building Plan Diagram, Fire and Airport Authority NOC Details. If the users have the NOC documents click on the Upload button to attach the documents to the application.
Click on the Next Step button to review the application details. The Summary page displays the payable Application Fee details.
Once the owner approves the application it is put back in the stakeholder’s queue for submission. The stakeholder will find this application in the My Applications page with the status Stakeholder’s submission pending.
Click on the Application Number hyperlink to open the application. Check the Declaration checkbox at the bottom of the application. Scroll down the page and click on the Submit button.
The submit successful acknowledgement message is displayed on the screen. Click on the Make Payment button at the bottom of the screen to pay the application fees.
Stakeholders can apply for occupancy certificates for new building construction once the occupancy eDCR Scrutiny is approved.
To submit for OC eDCR scrutiny
Navigate to eDCR Scrutiny menu option in the sidebar.
Click on Occupancy Certificate eDCR Scrutiny for New Building card. Select City.
Enter the applicable Building Permit Date and the Building Permit Number. Click on the search icon to populate the building permit details. Upload the Building Plan diagram.
Click on the Submit button to process the scrutiny.
Click on the Download or Print button to download or print the Scrutiny Report.
Click on the Create Occupancy Certificate Application button to proceed with the application or you can choose to proceed with the application later. Make a note of the OC Scrutiny Number that is required to create the application.
To apply for building permits for new construction
Navigate to the Building Plan Approval menu option in the sidebar. Click on Occupancy Certificate New Building Construction card.
Enter the applicable City for the new building construction.
Click on the Select button.
Enter the Occupancy Certificate Security Number. (The above steps are not required if the user has selected to create the OC application immediately after the OC scrutiny is completed).
The Application Type, Risk Type, Service Type, Applicant Name, Stakeholder Name, and Building Permit Number details will be auto-populated from the listed OC Scrutiny document.
The Application Date accepts the current date by default. Enter any comments in the Remarks field.
The Occupancy Certificate Scrutiny Details panel displays the eDCR Number, and a clickable link to download the Uploaded Image and Scrutiny Report.
The Actual Building Details are auto-populated from the scrutiny report. A Comparison Report is also generated at this stage. The comparison report provides a comparative assessment between the proposed construction and the actual construction diagram. This report can be downloaded once the OC application is submitted for further processing by the stakeholder.
Enter the Total Buildup Area (Sq Mtrs), Number of Floors, High From Ground Level from Mumty (In mtrs) details in the Actual Building Abstract panel.
Click on the Next Step button to move to the Documents and NOC Details section.
Select the appropriate document type for each of the Required Documents categories. Click on the Upload File button to upload the documents.
Click on the Next Step button to review the application details. The Summary page displays the payable Application Fee details.
Scroll down the page to review the application details. Click on the Send to Citizen button for final review and approval of the owner
To download the Comparison Report
Click on My Applications on the BPA home page.
Click on the relevant Application Number hyperlink to view the application.
Click on the Download or Print button to download the Comparison Report. This report is available for citizen download too.
Click on the camera icon to upload or change your Profile photo. Click on the Gallery button to select an image from your photo gallery or files on the computer. Select the file and click on the Open button. This will load the selected image as the profile picture. Click on the Remove button to delete the existing profile picture.
or for more details.
The Summary page displays the payable Registration Fee. Scroll down the page to view the application details. Click on the Edit icon available on the right side of each panel to make any changes.
Follow the steps outlined for in the Citizens section.
Enter the Building Plan Scrutiny Number. Click on the Search icon adjacent to the Building Plan Scrutiny Number. This will fetch the building and application details from the scrutiny report. The Building Plan Scrutiny Number is auto-populated in case the user initiates the application from the DCR scrutiny accepted acknowledgement screen.
Scroll down the page to review the application details. Click on the edit icon to make any changes in the application. Click on the Send to Citizen button for final review and approval of the owner.
User Role
Scope of Action
Role Description
Citizen
View BPA Application Status
Download Payment Receipts
Provide concurrence to the Architect to submit the application
Make payment for an application
Download Building Permit Order
Individuals and society groups/communities who engage stakeholder/architects to construct buildings for them
Stakeholder/Architect
Create BPA Application
Send application to the citizen for approval
Make payment for the application
Download permits
Download receipts
Check application status
Architects, builders, or engineers who register as a stakeholder in the BPA system - submit applications on behalf of the citizens
Document Verifier (DV)
Send application back to citizen
Reject applications
Upload document on behalf of citizen
Verify and forward applications to FI
DV is the ULB employee responsible for verifying all documents uploaded by the stakeholder / citizen along with the building permit or occupancy certificate application.
Field Inspector (FI)
Prepare Inspection Report
Send application back to the citizen
Reject applications
Verify and forward applications to NOC Verifier
FI is the ULB employee responsible for inspecting construction onsite details submitted by the stakeholder or owner.
NOC Verifier
Send back to citizen
Reject applications
Update NOC details on behalf of NOC department users
Verify and forward applications to BPA Approver
NOC Verifier is the ULB employee responsible for verifying NOC details obtained from concerned authorities.
BPA Approver
Reject application
Update permit conditions
Approve application
The BPA Approver is the ULB employee responsible for rejecting or approving building permit or occupancy certificate applications.
DIGIT is API based Platform here each API is denoting to a DIGIT resource. Access Control Service (ACS) primary job is to authorise end-user based on their roles and provide access to the DIGIT platform resources. Access control functionality basically works based on below points:
Actions: Actions are events which are performed by a user. This can be an API end-point or Frontend event. This is MDMS master
Roles: Role are assigned to the user, a user can hold multiple roles. Roles are defined in MDMS masters.
Role-Action: Role actions are mapping b/w Actions and Roles. Based on role, action mapping access control service identifies applicable action for the role.
Before you proceed with the configuration, make sure the following pre-requisites are met -
Java 8
MDMS service is up and running
Serve the applicable actions for a user based on user role (To print menu three).
On each action which is performed by a user, access control looks at the roles for the user and validate actions mapping with the role.
Support tenant-level role-action. For instance, an employee from Amritsar can have a role of APPROVER for other ULB like Jalandhar and hence will be authorised to act as APPROVER in Jalandhar.
Deploy the latest version of Access Control Service
Deploy MDMS service to fetch the Role Action Mappings
Define the roles
Add the Actions (URL)
Add the role action mapping
(The details about the fields in the configuration can be found in the swagger contract)
Any microservice which requires authorisation can leverage the functionalities provided by access control service.
Any new microservice that is to be added in the platform won’t have to worry about authorisation. It can just add it’s role action mapping in the master data and Access Control Service will perform authorisation whenever API for the microservice is called.
To integrate with Access Control Service the role action mapping has to be configured(added) in the MDMS service.
The service needs to call /actions/_authorize API of Access Control Service to check for authorisation of any request
Workflows are a series of steps that moves a process from one state to another state by actions performed by different kind of Actors - Humans, Machines, Time based events etc. to achieve a goal like onboarding an employee, or approve an application or grant a resource etc. The egov-workflow-v2 is a workflow engine which helps in performing these operations seamlessly using a predefined configuration.
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 workflow persister config path added in it
PSQL server is running and database is created to store workflow configuration and data
Always allow anyone with a role in the workflow state machine to view the workflow instances and comment on it
On the creation of workflow, it will appear in the inbox of all employees that have roles that can perform any state transitioning actions in this state.
Once an instance is marked to an individual employee it will appear only in that employee's inbox although point 1 will still hold true and all others participating in the workflow can still search it and act if they have necessary action available to them
If the instance is marked to a person who cannot perform any state transitioning action, they can still comment/upload and mark to anyone else.
Overall SLA: SLA for the complete processing of the application/Entity
State-level SLA: SLA for a particular state in the workflow
Deploy the latest version of egov-workflow-v2 service
Add businessService persister yaml path in persister configuration
Add Role-Action mapping for BusinessService API’s
Overwrite the egov.wf.statelevel flag ( true for state level and false for tenant level)
Create businessService (workflow configuration) according to product requirements
Add Role-Action mapping for /processInstance/_search API
Add workflow persister yaml path in persister configuration
For Configuration details please refer to the links in Reference Docs
The workflow configuration can be used by any module which performs a sequence of operations on an application/Entity. It can be used to simulate and track processes in organisations to make it more efficient too and increase accountability.
Role-based workflow
An easy way of writing rule
File movement within workflow roles
To integrate, host of egov-workflow-v2 should be overwritten in helm chart
/process/_search should be added as the search endpoint for searching workflow process Instance object.
/process/_transition should be added to perform an action on an application. (It’s for internal use in modules and should not be added in Role-Action mapping)
The workflow configuration can be fetched by calling _search API to check if data can be updated or not in the current state
(Note: All the API’s are in the same postman collection, therefore, the same link is added in each row)
Download DIGIT Product Brochures
DIGIT-Property Tax (PT) is a self-serve web and mobile-based, easy-to-use and configurable product that addresses the objectives of municipal corporations and local government to automate all property tax operations, thus providing property tax assessment and payment services to citizens in real-time.
Illustrative guide to using the trade license module
The Trade License (TL) module offers the citizens and governance bodies a convenient and transparent means of processing trade licenses. Trade license is the permission issued by the local governing bodies to carry on specified business or trading activity within the authorized area. It is a mandatory document required to run a business or commercial activity of any type.
The TL module enables citizens to apply for trade licenses or renew existing licenses online. It facilitates the governing bodies to validate and approve the license applications.
This section guides you through the details of using the TL module for each role. Click on the relevant role below to learn more about how to use the TL system.
A complete guide to using the PGR module
The Public Grievance Redressal or the PGR is a standardized solution offering on DIGIT platform to register and redress citizen grievances. It provides a transparent and trackable mechanism to solve public grievances by inducing responsive administration. PGR enables the citizens to file the complaints using various channels and helps the municipal employees to resolve them timely.
Citizens can lodge complaints, track, reopen and rate complaints through the web portal or the mobile application.
ULB employees too can use the web or mobile interface to comment, forward, assign, verify, share, and resolve citizen complaints.
Refer to the table below to understand the different user roles and the scope of action linked to each role. The manual provides a detailed description of how to use the system for each role.
This section guides you through the details of using the PGR module for each role. Click on the relevant role below to learn more about how to use the PGR system.
Learn how to file complaints and track your complaints
Citizens represent individuals or communities who are the system end-users. The PGR module provides the citizens with the scope to file their complaints or grievances to initiate necessary action.
The Citizen role can -
The File Complaints option allows citizens to register their complaints.
To file complaints navigate to Complaints Home page. Click on the File Complaints tab on the screen. This will open the complaint form page. Select the relevant Complaint Type and the subtype from the drop-down list of options. Refer to the list of complaint types available in PGR.
The system will display the Complaint Registered Successfully message along with the Complaint No. Click on the Continue button. Your complaint details are available on the dashboard.
My Complaints tab enables citizens to track the status of their complaints.
To view or track complaints click on My Complaints tab. The system will display all complaints filed by you or from your account and the corresponding status. Click on the Open button corresponding to any complaint to view the complaint details.
The complaint summary view contains the Complaint Details, Complaint Timeline, and Comments text box. The complaint timeline indicates the action taken on the complaint and the current or pending action status of the complaint.
Enter any additional information about the complaint in the Comments section.
The PGR module enables the citizens to give their feedback on resolved complaints.
To rate resolved complaints navigate to the Complaints menu option in the sidebar. Click on the My Complaints tab. Scroll down to the complaint you want to rate. You can rate only complaints marked as Closed. Scroll down to the Complaint Timeline section.
Click on the Rate button on the timeline.
Click on the number of stars on the screen to rate the work on the complaint on five. Click on the most appropriate feedback statement to rate the work. Add any additional information in the Comments section. Click on the Submit button.
The system displays an acknowledgement for your ratings. Click on the Go To Home button to navigate back to the home page.
To reopen the complaint navigate to Complaints > My Complaints menu option in the sidebar. Click on the closed complaint that you want to reopen. Scroll down to the Complaint Timeline section. Click on the Re-Open button on the timeline.
The Re-Open button will be available only for 5 days after the complaint is resolved and closed by the department employee. The number of days can vary depending on the State or ULBs. The citizen or CSR will not be able to reopen complaints once this period is over.
Select the appropriate reason for reopening the complaint. Click on the camera icon to upload any photos related to the complaint. Enter any additional information in the Comments section. Click on the Continue button once done. The system displays an acknowledgement message stating the complaint is reopened. Click on the Go To Home button to navigate back to the home page.
This section illustrates the steps for different employee user roles at the ULB level
The Document Verifier (DV) is responsible for verifying the required and supporting documents uploaded by the citizen or the stakeholder with the building permit or occupancy certificate application. The application is forwarded to the Field Inspector for further review once the DV finds the documents uploaded meet the requirements. Else, the application is either sent back to the citizen for refurbishing the documents or rejected.
DV can
DV can send the application back to the citizen for any corrections or if any vital document has not been uploaded. The DV can also upload the documents on behalf of the citizens.
To send the application back to the citizen
Click on the Application No. hyperlink available in the list of applications Assigned to Me section of the employee dashboard.
Or, enter the Application No. or any other search parameter to search for the application.
Click on the Application No. link to open the application.
Scroll down the application page to review the filled in details. Click on the View File button to open the documents uploaded in the application.
Click on the Upload button to upload relevant documents and NOC documents on behalf of the citizen.
Click on the Take Action button at the bottom of the application page once the review is complete.
Click on the Send Back to Citizen button if the documents do not meet the application requirements or any document is missing.
Select the applicable Assignee Name. State the reasons for sending the application back to the citizen in the Comments section.
Click on the Upload Files button to upload any supporting documents. Click on the Send Back to Citizen button.
The application is placed back in the Citizen queue for required edits.
The DV can reject the application if the documents and information furnished by the citizen do not meet the permit or occupancy guidelines.
To reject or revoke applications
Enter the Application No. or any other search parameter to search for the application. Click on the Application No. link to open the application.
Scroll down the application page to review the filled in details. Click on the View File button to open the documents uploaded in the application.
Click on the Take Action button at the bottom of the application page once the review is complete.
Click on the Reject button if the documents do not meet the application requirements or the information provided in the application is inaccurate.
State the reasons for rejecting the application in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Reject button.
The application is rejected and a notification is sent to the owner informing the same.
Permit orders are sanctioned instantly for low-risk applications. However, the application goes through the normal workflows for document verification, field inspection, and NOC verification. The ULB authorities can revoke the permit order in case any anomalies are detected during the verification process.
Applications can be revoked at any stage by the Document Verifier, Field Inspector, or the NOC Verifier.
To revoke application
Click on the Application No. in the Assigned to Me section of the employee dashboard or enter the Application No. or any other search parameter to search for the application.
Click on the Application No. link to open the application. Scroll down the application page to review the filled in details. Click on the View File button to open the documents uploaded in the application.
Click on the Take Action button at the bottom of the application page once the review is completed.
Click on the Revocate button if the application details do not meet the permit requirements.
Enter the reason for revoking the permit in the Comments field.
Click on Upload Files to attach supporting documents. Click on the Revocate button. The permit order is revocated.
The DV verifies and forwards the application if the documents and information provided in the application are found satisfactory and complete.
To verify and forward the application
Enter the Application No. or any other search parameter to search for the application. Click on the Application No. link to open the application.
Scroll down the application page to review the filled in details. Click on the View File button to open the documents uploaded in the application. Click on the Take Action button at the bottom of the application page once the review is complete.
Click on the Forward button once all documents are verified.
Select the applicable Assignee Name who will carry out the next phase of verification. Provide any additional information for the assignee in the Comments section.
Click on the Upload Files button to upload any supporting documents. Click on the Verify and Forward button.
The application is forwarded to the field inspector for further processing.
The field inspector or FI is responsible for conducting the field inspection of the construction site and premises. The FI prepares the inspection report based on the observations on the defined inspection parameters.
The FI can
FI prepares the field inspection report and attaches the report to the application.
To prepare the inspection report
Click on the Application No. hyperlink available in the list of applications Assigned to Me section of the employee dashboard.
Or, enter the Application No. or any other search parameter to search for the application. Click on the Application No. link to open the application.
Scroll down the application page to review the filled in details. Enter the Inspection Date and Inspection Time in the Inspection Report -1 panel. FI can add multiple field inspection reports as required.
Mark Yes or No as applicable for each item in the Inspection Checklist. Enter any additional information in the Remarks section available for each item in the checklist.
Select the applicable Document Type for each of the listed Documents. Click on the Upload File button to upload the relevant documents.
Click on +Add Another Field Inspection Report button to append additional inspection details.
Click on the Take Action button at the bottom of the application page once the review is complete.
To send the application back to the citizen
Click on Send Back to Citizen if any information or document is missing in the application.
Select the applicable Assignee Name. State the reasons for sending the application back to the citizen in the Comments section.
Click on the Upload Files button to upload any supporting documents. Click on the Send Back to Citizen button.
The application is placed back in the Citizen queue for required edits.
The FI can reject the application if the documents and information furnished by the citizen do not meet the permit or occupancy guidelines.
To reject the application
Click on the Reject button if the documents do not meet the application requirements or the information provided in the application is inaccurate.
State the reasons for rejecting the application in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Reject button.
The application is rejected and a notification is sent to the owner informing the same.
The FI verifies and forwards the application if the documents and information provided in the application are found satisfactory and complete.
To forward the applications
Click on the Verify and Forward button.
Select the applicable Assignee Name who will carry out the next phase of verification. Provide any additional information for the assignee in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Verify and Forward button.
The application is forwarded to the NOC Verifier for further processing.
The NOC Verifier is responsible for checking the no-objection permissions obtained for various civic authorities in context to the building construction. Commonly, a NOC is required from the Airports Authority and the Fire department to certify all guidelines are met by the builder and owner. If all requirements are met the NOC verifier forwards the application to the BPA Approver.
NOC Verifier can
The NOC Verifier can send the application back to the citizen in case there are some details missing in the form.
To send the application back to the citizen
Click on the Application No. hyperlink available in the list of applications Assigned to Me section of the employee dashboard. Or, enter the Application No. or any other search parameter to search for the application.
Click on the Application No. link to open the application.
Scroll down the application page to review the filled in details.
Click on the View File button to review the NOC documents uploaded with the application. Click on the Upload File button to upload NOC documents on behalf of the NOC issuing authority like Fire or Airport.
Click on the Take Action button at the bottom of the application page once the review is complete.
Click on the Send Back to Citizen button if the documents do not meet the application requirements or any document is missing.
Select the applicable Assignee Name. State the reasons for sending the application back to the citizen in the Comments section.
Click on the Upload Files button to upload any supporting documents. Click on the Send Back to Citizen button.
The application is placed back in the Citizen queue for required edits.
The NOC Verifier can reject the application if the documents and information furnished by the citizen do not meet the prescribed guidelines.
To reject the application
Click on the Reject button if the documents do not meet the application requirements or the information provided in the application is inaccurate.
State the reasons for rejecting the application in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Reject button.
The application is rejected and a notification is sent to the owner informing the same.
The NOC Verifier verifies and forwards the application to the BPA Approver if the documents and information provided in the application are found satisfactory and complete.
The NOC Verifier cannot forward the application to the BPA Approver until and unless the NOC from the respective authorities is received.
To forward the applications
Click on the Verify and Forward button once all details are verified and found satisfactory.
Select the applicable Assignee Name who will carry out the next phase of verification. Provide any additional information for the assignee in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Verify and Forward button.
The application is forwarded to the BPA Approval for final approval.
The BPA Approver is responsible for approving or rejecting the application for building permits or occupancy certificates. Once approved the owner can download the permit or the occupancy certificate from the portal.
The BPA Approver can
BPA Approver can reject the application if the documents and information furnished by the citizen do not meet the prescribed guidelines.
To reject applications
Click on the Application No. hyperlink available in the list of applications Assigned to Me section of the employee dashboard.
Or, enter the search parameter to find the application pending for approval.
Click on the Application No. link to open the application. Scroll down the application to review the filled in details. Check the applicable conditions in the Permit Conditions list.
Enter any additional Permit Condition in the space given below the list. These conditions will be appended in the permit order. Click on the +Add More button to add more conditions.
Click on the Take Action button. Click on the Reject button if the documents do not meet the application requirements or the information provided in the application is inaccurate.
State the reasons for rejecting the application in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Reject button.
The application is rejected and a notification is sent to the owner informing the same.
The BPA Approver approves the application for building permit or occupancy certificate once the verification is complete and prescribed guidelines are met.
To approve applications
Click on the Approve button once all requirements and verifications are complete.
Provide any additional information for the assignee in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Approve button.
The application is approved.
The citizen or the stakeholder can now download and print the building permit or occupancy certificate from their account only after paying the permit fee. There is no fee applicable for an occupancy certificate.
Learn how to apply for new trade license, renew and pay trade license fee
Citizens represent individuals, communities, or business entities who are the system end-users. The TL module allows business owners to apply for a trade license online or even apply for renewal of an existing license.
The citizen can also approach the Counter Employee (CE) to submit new TL applications or raise renewal requests for existing licenses.
The Citizen or CE role can -
Download payment receipts, license certificates, or applications
Citizens or CE can apply for a new trade license through the DIGIT web portal or the DIGIT mobile app. To apply for new TL click on the Trade License card available in the Citizen Services section of the DIGIT home page.
Click on the New Application button on the screen. This will open the TL application form page.
The system displays the Required Documents - Trade License list. Click on the Print button to get a hard copy of the documents list for reference.
Click on the Apply button to proceed with the trade license application. The form sections are available on the top of the page.
The New Application form page contains various sub-sections -
Trade Details
Owner Details
Documents
Summary
The system displays the Trade Details page. The page contains 4 panels - Trade Details, Trade Unit, Accessories, and Trade Location Details.
In the Trade Details panel, enter the following details.
Select the applicable Financial Year. Select the relevant License Type from the drop-down list. Enter the Name of Trade. Select the appropriate Structure Type and Structure Sub Type. Enter the Trade Commencement Date. Enter the Trade GST No. if applicable. Enter the Operational Area (Sq Ft). and the Number of Employees for the listed trade.
In the Trade Unit panel, provide the following details -
In the Accessories panel, enter the following details -
Enter the following details in the Trade Location Details panel -
Select the City. The system displays the registered city by default. Enter the Property ID/UID, Door/House No., Building/Colony Name, Street Name, Mohalla, and Pincode for the listed premises. Click on the map icon to provide the GIS coordinates for the location. Enter the Electricity Connection No. for the listed premise.
Click on the Next Step button to move to the Owner Details section.
Select the Type of Ownership and the Type of Sub-Ownership. Provide the following information in the Owner Information section.
Enter the owner Mobile No., Name, Father/Husband’s Name. Check Father or Husband to indicate the Relationship of the given name with the owner. Check the applicable Gender of the owner. Enter the Date of Birth of the owner. Enter the owner’s Email ID, PAN No., Correspondence Address. Select the applicable Special Owner Category from the drop-down list.
Click on the Next Step button to move to the Documents section.
Click on the Upload File button to browse and upload the required documents for processing the TL. Click on the Next Step button once all the documents are uploaded.
The Application Summary page provides all the information filled in by the applicant. The Application Summary panel on top of the page provides the Trade License Tax and Total Amount details. This amount has to be paid by the applicant.
Click on the View Breakup button to fetch the fee details.
The Trade License Application No. is displayed along with this message. Click on the Download button to download a copy of the application. Click on the Print button to print the application.
Citizens can renew their existing trade applications on the DIGIT portal. CE can also apply for TL renewal on behalf of the citizens. To renew TL navigate to the home page and then click on the Trade License option. Click on My Applications. Click on the Renew Now button on the specific license.
The system will display the license details. Click on the Take Action button. Click on the Edit button to make any changes to the existing license details. Click on the Submit for Renewal button to apply for renewal.
The Trade License is submitted for renewal.
To search for a submitted application or track the status of submitted applications navigate to the Trade License home page.
Enter at least one of the listed search parameters in the Search panel. The listed search parameters include
Application No.
Trade License No.
Owner Mobile No.
Application Type
From Date
To Date
Application Status
Click on the Search button. The system displays the records matching the listed parameter.
Click on the Application No. link. The screen displays the application details. Scroll down the page to view the details.
Click on the Take Action button and click on Edit option to edit the form details. The Task Status panel on the top of the Application displays the current status of the application.
Click on the View History button on the top right corner of the Task Status panel to view the actions taken on the application to date.
Applicants have to pay the license fee once the TL application is approved. The application status changes to Pending for Payment. To make payment for the trade license fee click on your Application No. to open the application. Click on the Take Action button.
Click on Pay. 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 Trade License Certificate is issued. Click on the Download or Print button to download or print the Payment Receipt and Trade License Certificate.
The Counter Employee (CE) represents the ULB employee responsible for assisting the citizens with water and sewerage connection related activities. The W&S module provides the CE with the scope to submit applications for new connections on behalf of the citizens or collect payment for the citizen bills at the counter.
The CE can -
The CEs can apply for new water or sewerage connection applications and submit it on behalf of the citizens.
To apply for new connections
Click on the Water & Sewerage menu option in the sidebar or the Water & Sewerage card on the DIGIT home page.
Click on the New Application button available on the top right corner of the page. Follow the steps iterated in the Citizens Apply for new connections section to apply for new connections.
The W&S portal enables CEs and other ULB employees to search for specific applications or connections using different search parameters.
To search for W&S connections
Click on the Water & Sewerage menu option in the sidebar or the Water & Sewerage card on the DIGIT home page. The Search Connections tab on the page displays the various search parameters that filter the search for specific connections. Enter the applicable City. This is a mandatory search filter.
Enter the Property ID, or Owner Mobile No., or Consumer Number, or the Old Consumer Number to filter the view of connections based on the specified parameter. Click on the Search button to view the search results. Click on the Reset button to renew the search using different parameters.
To search for W&S applications
Click on the Water & Sewerage menu option in the sidebar or the Water & Sewerage card on the DIGIT home page. Click on the Search Applications tab.
Enter the Consumer No. or Application Number, or Owner Mobile No., or Application Type to filter the search for applications. The application search can also be filtered by Application Status or defining a specific period in the From Date and To Date fields. The system fetches the applications created between the specified period or after the specified date.
Click on the Search button to view the search results. Click on the Reset button to renew the search using different parameters.
CEs add the meter readings for each connection to generate monthly bills based on the recorded usage.
To add meter readings
Search for the specific connection using relevant search parameters. Click on the Consumer Number link available for listed connections. Click on View Consumption Details available in the Service Details panel.
Click on the Add Meter Reading button on the top right corner of the Consumption Details page.
The Billing Period by default is set to the last reading date and current reading date.
Select the applicable Meter Status. The meter status can be changed to reflect the current working condition of the meter. Meters can be set to Working, Locked, Breakdown, Non-meter, Reset, or Replacement, as applicable.
Enter the Current Reading in the meter reading page. The system displays the Last Reading and the Last Reading Date. Enter the Current Reading Date. The date field auto-populates the current date by default.
The actual Consumption is automatically calculated by the system. The customer is billed on the basis of the actual consumption.
Click on the Save button to save the reading. This will generate the bill or demand for payment that has to be made by the customer.
Once the application for new water or sewerage connection is approved and the citizen has paid the applicable connection charges, the CE is responsible for activating the new connection.
To activate new connections
Search for the applications that are Pending for Connection Activation. Click on the Application No. to open the application.
Click on the Take Action button and click on Edit option to enter connection activation details.
Review the Connection Details and the list of Documents furnished with the application.
Enter the connection details in the Additional Details section of the application.
Enter the Connection Execution Date. The connection will be activated on the specified date. For metered connections, enter the Meter ID, Meter Installation Date, and Initial Meter Reading (KL).
Click on Next Step to the Summary section of the application. Review the application details. Click on the Take Action button and then click on the Activate Connection option.
Enter any Comments for activating the connection. Click on the Activate Connection button.
The connection activation success message is displayed on the screen. A system generates a unique Consumer No. to identify the connection.
CEs can pay W&S bills for the citizens. The CEs can add penalty or rebates to the bill amount depending on the applicable penalty or rebates available for the customers.
To pay bills
Enter the relevant search parameter to filter the view of W&S connections. Click on the Collect button for the specific connection.
The Bill Details panel displays the pending dues details and its breakup.
Click on the Add Rebate/Penalty button to adjust any penalties or rebates applicable for the customer.
Add the Adhoc Penalty Amount or the Adhoc Rebate Amount. Select the Reason For Adhoc Penalty or Reason for Adhoc Rebate from the given drop-down list. Enter any additional information in the Enter Comments section.
Click on the Add button to add the penalty or rebate amount to the total bill amount. Click on the Download Bill button to download the bill. Click on the Pay button.
Select Full Amount or Custom Amount to specify the full or partial payment of the bill. Enter the Amount to Pay if Custom Amount is selected. Click on the applicable payment tab in the Capture Payment panel.
Enter the required payment details and make the payment. Click on the Generate Receipt button to process the payment.
The payment success acknowledgement message is displayed on the screen. Click on the Download or Print button to download or print the payment receipt.
The W&S module enables CEs to make any changes to the existing water or sewerage connection details in a few simple steps. Such changes may reflect any updates in property details or the connection details.
To modify connection details
Search for the specific connection using applicable search parameters. Click on the Consumer Number link to open the connection details page.
Scroll down the page and click on the Take Action button. Click on Modify Connection.
The system does not allow employees to modify connection details in 2 cases
If there are any pending dues for the connection - the owner has to settle the pending dues before making any modifications to the connection details.
If there is already any other modification application pending for approval - the owner can raise another modification request only once the previous application is approved.
The Modify Connection application form contains 4 sections. The Property Details panel displays the existing property details linked to the connection. Click on the Search Property button to replace the existing property details with another property. Select the applicable Property ID. The change request for property details will be forwarded to the Approver for final approval.
Click on the Modify Property button to make any changes to the existing property. This action is integrated with the Property Tax module. So, whatever changes or edits are requested for the listed property will go through the Edit Property workflow for verification and final approval from the Property Tax department.
Click on the Next Step button to move to the Additional Details section.
Change the Connection Details as required on this page. Users can modify the existing Connection Type, Number of Taps, Water Source, Water Sub Source, and applicable Pipe Size details. Change the Activation Details if required. Enter new meter details in the Meter ID and Meter Installation Date fields.
Enter the Modification Effective From date. The requested changes will be reflected from the selected date. Click on the Next Step button to upload supporting documents for the requested changes.
Select the applicable Documents and then click on Upload Files to attach the selected documents with the application.
Click on the Next Step button to move to the Summary page of the application. Scroll down the page to review the modification requests. The existing connection details are available below the requested changes for easy reference.
Click on the Submit button for processing the modification requests. The application is sent to the Approver for final approval.
The Document Verifier (DV) is responsible for verifying the required and supporting documents uploaded by the citizen with the W&S application. The application is forwarded to the Field Inspector for further review once the DV finds the documents uploaded meet the requirements. Else, the application is either sent back to the citizen for refurbishing the documents or rejected.
DV can
DV can edit application details on behalf of the applicants.
To edit applications
The applications Pending for Document Verification is available on the DIGIT home page. Else, search for the application using the search parameters.
Open the application. Click on the View History button available in the Task Status panel on top to view the list of actions taken on the application so far. Click on the View Breakup button to find the fee breakup details in the Fee Estimate panel.
Click on the Add Rebate/Penalty button to add any ad hoc penalty or rebate amount to the total fee payable. Scroll down the application to review the filled in details. Click on the View button for each uploaded document to review details.
Click on the Take Action button and then click on Edit to make required corrections. Review the Connection Details and the list of Documents furnished with the application.
Enter the connection details in the Additional Details section of the application. Select the applicable Connection Type. Enter the Number of Taps, Water Source, Water Sub Source, and Pipe Size details.
Select ULB if the plumber is provided by the ULB. Else, check the Self option. In case the plumber is provided by the ULB enter the Plumber License No., Plumber Name, and Plumber Mobile No. details.
Select the relevant Road Type. Enter the Area (in sq ft) to indicate the length of road cutting required to lay the pipes. Enter the Connection Execution Date. The connection will be activated on the specified date.
Click on Next Step to the Summary section of the application. Review the application details. Complete the changes and click on the Submit button to save the changes.
DV can send the application back to the citizen for any corrections or if any vital document has not been uploaded.
To send the application back to the citizen
Enter the Application No. or any other search parameter to search for the application. Click on the Application No. link to open the application. Scroll down the application page to review the filled in details.
Click on the View File button to open the documents uploaded in the application. Click on the Take Action button at the bottom of the application page once the review is complete. Click on the Send Back to citizen button if the documents do not meet the application requirements or any document is missing.
State the reasons for sending the application back to the citizen in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Send Back button.
The application is placed back in the Citizen queue for required edits.
The DV can reject the application if the documents and information furnished by the citizen do not meet the prescribed guidelines.
To reject the application
Click on the Take Action button at the bottom of the application page once the review is complete. Click on the Reject button if the documents do not meet the application requirements or the information provided in the application is inaccurate.
State the reasons for rejecting the application in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Reject button.
The application is rejected and a notification is sent to the applicant informing the same.
The DV verifies and forwards the application if the documents and information provided in the application are found satisfactory and complete.
To verify and forward the application
Click on the Take Action button at the bottom of the application page once the review is complete. Click on the Verify and Forward button once all documents are verified.
Select the applicable Assignee Name who will carry out the next phase of verification. Provide any additional information for the assignee in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Verify and Forward button.
The application is forwarded to the field inspector for further processing.
The field inspector or FI is responsible for conducting the field inspection of the connection site and premises. The FI prepares the inspection report based on the observations on the defined inspection parameters.
The FI can
To edit applications
The application Pending for Field Inspection is available on the DIGIT home page. Else, search for the application using the search parameters.
Open the application. Click on the View History button available in the Task Status panel on top to view the list of actions taken on the application so far. Click on the View Breakup button to find the fee breakup details in the Fee Estimate panel.
Click on the Add Rebate/Penalty button to add any ad hoc penalty or rebate amount to the total fee payable.
Scroll down the application to review the filled in details. Click on the View button for each uploaded document to review details. Click on the Take Action button and then click on Edit to make required corrections.
Review the Connection Details and the list of Documents furnished with the application.
Enter the connection details in the Additional Details section of the application. Select the applicable Connection Type. Enter the Number of Taps, Water Source, Water Sub Source, and Pipe Size details.
Select ULB if the plumber is provided by the ULB. Else, check the Self option. In case the plumber is provided by the ULB enter the Plumber License No., Plumber Name, and Plumber Mobile No. details.
Select the relevant Road Type. Enter the Area (in sq ft) to indicate the length of road cutting required to lay the pipes. Enter the Connection Execution Date. The connection will be activated on the specified date. For metered connections, enter the Meter ID, Meter Installation Date, and Initial Meter Reading (KL).
Click on Next Step to the Summary section of the application. Review the application details. Complete the changes and click on the Take Action button to proceed with the required action on the application.
FIs can send the application back to the DV for any corrections or if any vital document has not been uploaded.
To send the application back
Enter the Application No. or any other search parameter to search for the application. Click on the Application No. link to open the application. Scroll down the application page to review the filled in details.
Click on the View File button to open the documents uploaded in the application. Click on the Take Action button at the bottom of the application page once the review is complete. Click on the Send Back button if the documents do not meet the application requirements or any document is missing.
State the reasons for sending the application back to the citizen in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Send Back button.
The application is placed back in the DV queue for required edits.
The FI can reject the application if the documents and information furnished by the citizen do not meet the prescribed guidelines.
To reject the application
Click on the Take Action button at the bottom of the application page once the review is complete. Click on the Reject button if the documents do not meet the application requirements or the information provided in the application is inaccurate.
State the reasons for rejecting the application in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Reject button.
The application is rejected and a notification is sent to the applicant informing the same.
The FI verifies and forwards the application if the documents and information provided in the application are found satisfactory and complete.
To verify and forward the application
Click on the Take Action button at the bottom of the application page once the review is complete. Click on the Verify and Forward button once the field inspection is complete and found to be satisfactory.
Select the applicable Assignee Name who will carry out the next phase of verification. Provide any additional information for the assignee in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Verify and Forward button.
The application is forwarded to the W&S Approver for final approval.
The W&S Approver is responsible for approving or rejecting the application for new water or sewerage connections. Once approved the applicant must pay the connection charges to initiate the activation of connection. The counter employee fills in the activation details and activates the connection. Post connection activation the system generates a unique consumer number.
The Approver can
To edit applications
The application Pending for Approval is available on the DIGIT home page. Else, search for the application using the search parameters. Open the application.
Click on the View History button available in the Task Status panel on top to view the list of actions taken on the application so far. Click on the View Breakup button to find the fee breakup details in the Fee Estimate panel. Click on the Add Rebate/Penalty button to add any ad hoc penalty or rebate amount to the total fee payable.
Scroll down the application to review the filled in details. Click on the View button for each uploaded document to review details.
Click on the Take Action button and then click on Edit to make required corrections. Complete the changes and click on the Submit button to save the changes.
The Approver can send the application back to the FI for any corrections or if any vital document has not been uploaded.
To send the application back to the citizen
Enter the Application No. or any other search parameter to search for the application. Click on the Application No. link to open the application. Scroll down the application page to review the filled in details.
Click on the View File button to open the documents uploaded in the application. Click on the Take Action button at the bottom of the application page once the review is complete. Click on the Send Back button if the application does not meet specific requirements or any document is missing.
State the reasons for sending the application back to the FI in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Send Back button.
The application is placed back in the FI queue for the required processing.
The Approver can reject the application if the documents and information furnished by the citizen do not meet the prescribed guidelines.
To reject the application
Click on the Take Action button at the bottom of the application page once the review is complete. Click on the Reject button if the documents do not meet the application requirements or the information provided in the application is inaccurate.
State the reasons for rejecting the application in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Reject button.
The application is rejected and a notification is sent to the applicant informing the same.
The Approver verifies the application and if the documents and information provided in the application are found satisfactory and complete, the connection request is approved.
To approve connections
Click on the Take Action button at the bottom of the application page once the review is complete. Click on the Approve Connection button once the application is reviewed and verified.
Provide any additional information for the applicant in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Approve Connection button.
The application for new water or sewerage connection is approved. The applicant is allotted a unique Consumer Number. The application is now routed back to the citizen to make the payment towards connection charges. Once the payment is done the connection is activated.
Learn how to add new property, assess or transfer property and pay property tax
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 can also approach the Counter Employee (CE) to register new property, assess property or pay property tax.
The Citizen or CE role can -
Citizens or CE can add new property details through the DIGIT web portal or the DIGIT mobile app.
To add a new property click on the Property Tax card available in the Citizen Services section of the Home page.
Click on the Add New Property button on the screen. This will open a new form page.
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 system will display the New Property form page.
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.
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.
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.
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.
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.
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.
A complete guide to using Water & Sewerage module
The W&S module allows citizens to apply for new connections and pay bills online. For employees, this module enables automated processing of new connection requests, editing existing connection details, generating water bills, and facilitating online collection of bill payments.
The module supports the following key functions -
Apply for new connections
Pay one-time connection charges for new water or sewerage connections
Pay recurring bills using online payment gateway
Download artefacts such as application details, connection details, bills, receipts, sanction letter and estimation notice
Process applications using configurable workflows
Refer to the table below to understand the different user roles and the scope of action linked to each role. The applicable user roles and action items can vary from one State to another. DIGIT customizes the workflows to suit the requirements defined at the State level.
This section guides you through the details of using the [module name] module for each role. Click on the relevant role below to learn more about how to use the module.
An illustrative guide to using the property tax module
The Property Tax (PT) module offers the citizens and governance bodies a convenient and transparent means of processing property taxes. Local governing bodies identify the applicable tax slabs for different types of properties. The PT module assesses properties, calculates tax amount, processes tax payment and generates tax collection reports.
The PT module enables citizens to pay property taxes online. It facilitates the governing bodies process property tax payments.
Refer to the table below to understand the different user roles and the scope of action linked to each role. The applicable user roles and action items can vary from one State to another. DIGIT customizes the workflows to suit the requirements defined at the State level.
This section guides you through the details of using the PT module for each role. Click on the relevant role below to learn more about how to use the PT system.
This section illustrates the steps for different employee user roles at the ULB level
DV is responsible for verifying the supporting documents uploaded by the property applicants or the counter employee on behalf of the applicants.
The DV can
Property applications are rejected if the supporting documents uploaded by the applicant fails to comply with the property regulatory requirements or the details provided in the form are incorrect.
To reject applications 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 Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The DV verifies and forwards the property applications to the Field Inspector if the DV finds all information and documents provided by the applicant correct.
To verify and forward 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 Take Action button available at the bottom of the page. Click on the Verify and Forward button. Select the relevant Assignee Name from the list of available employees for subsequent processing.
Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Verify and Forward button.
The property application is assigned to the selected assignee for subsequent processing.
To edit applications 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 Take Action button available at the bottom of the page. Click on the Edit button. Change any details in the form as required.
FI is responsible for inspecting and verifying the field details of the property in the application.
The FI can
FI sends back the applications to the citizens if some vital information is missing in the application or there is a mistake in the information provided.
To send applications back to the citizen 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 Take Action button available at the bottom of the page. Click on the Send Back to Citizen button. Enter any Comments stating why the application is sent back.
Click on the Upload Files button to upload any files or images in context to the application. Click on the Send Back to Citizen button.
The system displays a success acknowledgement message stating that the application is sent back to the initiator.
The FI can send back the PT application to the DV if there is any mistake or lapses in the document verification process.
To send back applications to the DV 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 Take Action button available at the bottom of the page. Click on the Send Back button.
Select the Assignee Name who will be responsible for verifying the application. Enter any Comments stating why the application is sent back. Click on the Upload Files button to upload any files or images in context. Click on the Send Back button.
The application is assigned back to the selected assignee for verification of documents.
Property tax applications are rejected if the supporting documents uploaded by the applicant fails to comply with the license requirements or the details provided in the form are incorrect.
To reject applications 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 Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The FI verifies and forwards the property applications to the Approver if the information and documents provided by the applicant are correct.
To verify and forward 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 Take Action button available at the bottom of the page. Click on the Verify and Forward button. Select the relevant Assignee Name from the list of available employees for subsequent processing.
Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Verify and Forward button.
The property application is assigned to the selected assignee for subsequent processing.
The Approver is responsible for the final approval of the PT application.
The Approver can
The Approver can send back the property applications to the FI or DV if there is any mistake or lapses in the document verification process.
To send back applications to the DV or FI 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 Take Action button available at the bottom of the page. Click on the Send Back button.
Select the Assignee Name who will be responsible for verifying the application. Enter any Comments stating why the application is sent back. Click on the Upload Files button to upload any files or images in context. Click on the Send Back button.
The application is assigned back to the selected assignee for verification of application.
Property applications are rejected if the supporting documents uploaded by the applicant fails to comply with the regulatory requirements or the details provided in the form are incorrect.
To reject applications 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 Take Action button available at the bottom of the page. Click on Reject.
Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.
The applicant will receive a rejection notification on his mobile number or email address.
The Approver signs off the PT application once the information and documents provided by the applicant are found correct.
To approve 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 Take Action button available at the bottom of the page. Click on the Approve button.
Select the relevant Assignee Name from the list of available employees for subsequent processing. Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Approve button.
The property application is approved.
Core Services is one of the key DIGIT components. Browse through this section to learn more about key configuration and integration details of these core services.
This section contains all technical documents related to DIGIT stack.
The key services include -
This section illustrates the steps for different employee user roles at the ULB level
The counter employees or field employees collect and process the miscellaneous payments on behalf of the citizens.
The CE or FE role can -
Collect payment
Search payment receipts
Print receipts
Download payment receipts
CE can process and collect payments for miscellaneous services through the DIGIT web portal or the DIGIT mobile app. To process a new payment navigate to the Universal Collections option in the sidebar main menu.
Click on the New Collection button on the screen. This will open a new collection form page.
Enter the Mobile No. and Consumer Name of the payee.
Select the applicable Service Category.
The system will prompt the input of Tax amount, CGST, SGST, Field Fee, or any other details depending on the selected Service Category.
Enter the From Date and To Date to identify the applicable payment period. **Enter any additional information in the Comments** field.
Click on the Next button to move to the payment section. The Payment Collection Details page displays the fee details and capture payment form. The Fee Details panel displays the fee breakup and Total Amount details.
The Capture Payment panel displays the available payment methods. Click on the preferred payment tab. The available payment tabs are Cash, Cheque, Credit/Debit Card.
Enter the Paid By and the Payee Name details.
Enter the Payer Mobile No.
Enter the Cheque No., Cheque Date, IFSC, Bank Name, and Bank Branch details in case of payment by cheque. Enter your credit card or debit card Last 4 digits, Transaction No., and Re-enter Transaction No. details if you have selected the Credit/Debit Card payment option.
Enter the Gen/G8 Receipt No. issued at the payment counter in case payments are made offline. Enter Gen/G8 Receipt Issue Date mentioned on the receipt.
Click on the Generate Receipt button once the payment is collected or processed. The system will display the payment success acknowledgement message.
Click on the Download button to download/view the receipt. Click on the Print button to print the receipt.
To search for payment receipts navigate to the Universal Collections page in the sidebar main menu.
Enter the relevant search parameter. The system enables you to search using payment Receipt No. or Service Category, or payee Mobile No. Click on the Search button.
The system will display the relevant search results in the panel below. Click on the relevant record to view the payment receipt. The system will generate a pdf format of the payment receipt.
Click on the download icon on the pdf page to download the receipt. Click on the print icon on the pdf page to print the receipt.
Click on the Reset button to renew your search with different parameters.
Learn how to apply for new water or sewerage connections, pay bills
Citizens represent individuals, groups or communities that are using the W&S module online to manage their water and sewerage connections. The W&S module offers an efficient means of tracking and managing water and sewerage connections.
The citizens can -
Download bills, receipts and approval letters
The Apply for New Connection option allows citizens to submit their application for new water or sewerage connection. Application forms are submitted through the portal for further processing and approval for new connections by the ULB employees.
To apply for new connections
Navigate to the Water & Sewerage menu option in the sidebar. Alternatively, click on the Water & Sewerage card available on the Citizen Services panel on the home page.
Click on the Apply for New Connection option.
The system displays the list of required documents for processing new water or sewerage connections. Click on the Print button below to print the list for reference.
Click on the Apply button to begin filling the application form. The application form contains three sections - Connection Details, Documents, and Summary.
In the Property Details panel enter the Property ID for the new connection. Click on the Find/Create Property ID click here link if you do not remember the property ID or the property is not yet registered in the system. Search for the relevant property details or click on the Register New Property button to register the property.
Click on the Select button available for the relevant property in the search list. This will auto-populate the property details in the application.
The Same as Owner Details box is checked by default in the Connection Holder Details panel. Uncheck this box if the connection holder details are not the same as the property owner. Now enter the connection holder’s Mobile No., Name, Gender, Guardian Name, Relationship with the mentioned guardian, Correspondence Address and Special Applicant Category details.
Check the Water or Sewerage box in the Connection Details panel to indicate the type of connection you are applying for. Check both boxes if the application is for both water and sewerage.
Enter the No. of Taps proposed if you are applying for water connection. Select the applicable value for Pipe Size Proposed (in inches). Enter the required No. of Water Closets and No. of Toilets details for sewerage connection. Click on the Next Step button to proceed to the Documents section of the application.
The system allocates a unique Application No. available on the top of the application form page. Click on the Select Documents drop-down menu to identify the relevant document that will be uploaded as Identity Proof, Address Proof, Building Plan etc.
Click on the Upload File button to attach the documents to the application. Click on the Next Step button to move to the Summary section of the application.
The system displays the success acknowledgement message. Click on the Download or Print button to download or print the application.
The application is processed by the ULB employees who verify the attached documents and carry out field inspections before the final approval. The citizen is allotted a unique consumer number once the application is processed and approved.
Citizens can view their applications to find status details, pending fees to be paid, or any other notifications linked to the application.
To view applications
Click on the My Applications option in the W&S home page.
The system displays all the applications submitted by the citizen and the current status of each application. Click on the View Details button below the application for detailed information on the application status and actions taken on the application.
Click on the View History button available in the Application Summary panel on top. This displays all the tasks completed and in progress along with the date.
The Fee Estimate panel displays the payable application fee details. Click on the View Breakup button to find the fee calculation details.
Click on the Take Action button at the bottom of the application and then click on Pay to make the fee payment. The Pay option is enabled once the application is in Pending for Payment status.
Click on the Download or Print button on the top right corner of the page to download or print the application or the payment receipt.
The W&S module allows citizens to check the meter readings in case they have metered connections.
To check meter readings
Click on My Connections card on the W&S home page. The existing connections for the listed user are available on the screen. Click on the Consumer Number link available for listed connection.
Click on the View Consumption Details button available in the Service Details panel on the Connection Details page.
The meter reading and current consumption readings are available in the Consumption Details page.
Scroll down the page to view past readings.
Citizens can view their water or sewerage connection details through the portal.
To view connection details
Click on My Connections card on the W&S home page. The existing connections for the listed user are available on the screen. Click on the Consumer Number link available for the listed connection.
The Connection Details page displays the Service Details, Property Details, Owner Details and the Connection Holder Details. Scroll down the page to view these details.
The citizen portal allows users to view their existing connection details and pay water or sewerage bills online.
To view and pay bills
Click on My Connections card on the W&S home page. The existing connections for the listed user are available on the screen.
Click on the Pay Now button available for connections that have pending dues.
Alternatively, click on the Pay Water & Sewerage Bill card on the W&S home page. Enter the required search parameters to search for a specific bill.
Click on the Pay Now button available for connections that have pending dues.
The Bill Details shows the Total Amount, Due Date, and amount breakup details. Scroll down to view the associated Service Details and Property Details. Click on the Download Bill button to download the bill. Click on the Pay button to make the payment.
Select Full Amount or Custom Amount depending on whether you are paying the entire bill amount or making a partial payment or advance payment. Enter the Amount to pay (Rs) in case of Custom Amount. Enter the Payer Details.
Select the relevant option for Payment Paid By. Select Owner if the payment is done by the owner else select Other if someone else is making the bill payment. Enter the Payer Name and Payer Mobile No. In the case of Owner, these details are auto-populated.
Click on the Make Payment button to proceed with the payment. Select the preferred payment method and provide the required payment details. The system displays the payment success acknowledgement message.
Click on the Download or Print button to download or print the payment receipt.
Citizens can view past bill payment details from their portal.
To view past payment details -
Click on the Past Payments option on the W&S home page.
The system displays historic payment details.
Click on the Download Receipt button to download the payment receipt. The Partially Paid status will be displayed if only part of the bill amount is paid.
Enter any additional information in the Complaint Additional Details field. Click on the map icon to pinpoint the Complaint Location. The City field will display the city specified in your profile by default. You can change the city if required. Choose the applicable Locality/Mohalla from the drop-down list. Enter the House No. and Street Name. Enter any Landmark to identify the exact location for the listed complaint.
Click on the camera icon to upload any photos for the complaint. Click on the Submit Complaint button once you have finished filling in all the details.
The bell icon on the top right corner of the complaint tab will display any notifications received for the complaint. Click on the bell icon to view the complaint details.
Select the applicable Trade Category, Trade Type, Trade Sub Type, UOM (Unit of Measurement), and UOM value. Click on the icon to add more trade units.
Select the applicable Accessories for the listed trade. Select the corresponding UOM for the selected accessories. Enter the UOM value. Enter the Accessory Count. Click on the icon to add more accessories.
Scroll down the page to view the filled-in details. Click on the Edit icon to make any changes to the application. Click on the Submit Application button. The system displays the Application Submitted Successfully acknowledgement message.
The Application Summary page provides all the information filled in by the applicant. Click on the Edit icon to make any changes to the application.
The Summary page displays the filled in application details. Scroll down the page to check the details. Click on the Edit icon to make any changes to the application. Click on the Submit button once the review is complete.
User Role
Scope of Action
Role Description
Citizen
Apply for Trade License
Pay for license
Track status of the license application
Download payment receipts
Individuals and business entities
Counter Employee (CE)
Apply for a Trade License
Complete the Payment for Trade License
Keep a track of the status of the Trade License
Download/Print payment receipts, applications, TL certificate
Counter employees who assist citizens and file new trade license applications or renewal applications on their behalf
Document Verifier (DV)
Verify and forward
Send Back
Edit
Employees responsible for verifying the supporting documents submitted by citizens for new trade license or renewal of existing licenses
Field Inspector (FI)
Verify and forward
Send Back
Reject
Edit
Employees who go on to the field (i.e. location of trade) and physically verifies the information provided by the applicant is correct, checks safety precaution followed by the trade owner
Approver
Approve
Send Back
Reject
Cancel TL
The employee who has the final authority to approve or reject the application
User Role
Scope of Action
Role Description
Citizens
File Complaints
Track Complaints
Rate Complaints
Reopen Complaints
Individuals and society groups/communities
Customer Service Representatives (CSR)
File Complaints
Track Complaints
Reopen Complaints
Counter employees who assist citizens and register complaints on their behalf
Grievance Routing Officer (GRO)
Assign Complaints to FME
Rejects Complaints
ULB officers who assign complaints to concerned employees
First Mile Employee (FME)
Resolve Complaints
Share Complaints - Whatsapp/SMS
Request Re-assign
Employees who work on assigned complaints
Complaint Types
Complaints Sub-Types
Streetlights
Streetlight not working
Installation of new street light
Garbage
Garbage needs to be cleared
Burning of garbage
Damaged garbage bin
Non-sweeping of road
Congress grass-cutting
Drains
Overflowing/Blocked drain
Cleaning of drains
Water entered house rainy season
Water & Sewerage
Illegal discharge of sewage
Block/overflowing sewage
Shortage of water
Dirty water supply
Broken water pipe/leakage
Water pressure is very less
No water supply
Sewage main hole cover missing or broken
Sewerage main hole cover raising
Cleaning of sewerage moves slurry gear
Property Tax/ House Tax
How to pay property tax
Wrong calculation
Receipt not generated
Others
Roads & Footpaths
Damaged road
Waterlogged road
Manhole cover missing or broken
Damaged/Blocked footpath
Construction material lying on road
Illegal rehries on road
Road jalli broken
Mosquitoes
Request spraying or fogging operation
Animals
Stray animals
Dead animals
Public Toilets
Dirty or smelly public toilets
Public toilet damaged
No water or electricity in public toilet
Land Violations
Illegal shops on footpath
Illegal construction
Illegal parking
Trees
Illegal cutting of trees
Cutting or trimming of tree required
Open Defecation
Open defecation
Parks
Parks require maintenance
Others
User Role
Scope of Action
Role Description
Citizen
Apply for new connection
Pay one-time connection charges
Pay bills
Download artefacts
Individuals and society groups/communities who want to apply for new water or sewerage connections, or pay bills
Counter Employee
Create new applications
Process applications
Edit existing connection details
Add meter reading
Collect connection charges
Collect bill payment
Download bills, receipts, and approval letter for new connections
ULB employees responsible for submitting applications for new connections on behalf of the citizens or pay their bills at the counter
Document Verifier (DV)
Send applications back to citizen
Reject applications
Verify and forward applications
ULB employees responsible for verifying the documents uploaded along with the application
Field Inspector (FI)
Send applications back to citizen
Generate estimation notice
Add additional details
Reject applications
Verify and forward applications
ULB employees responsible for conducting the onsite inspection
Approver
Reject applications
Approve applications
ULB employee responsible for rejecting or approving new connection requests
All employee roles
Search connections/applications
Process new connections/modify applications
View connection details
Download artefacts
User Role
Scope of Action
Role Description
Citizen
Add Property
Search Property
Edit Property
Assess Property
Re-Assess Property
Pay Property Tax
Transfer Property Ownership
Download Receipts/Applications
Individuals and Community groups
Counter Employee (CE)
Add Property
Search Property
Edit Property
Assess Property
Re-Assess Property
Pay Property Tax
Transfer Property Ownership
Download Receipts/Applications
Counter employees who assist citizens register new property details, transfer ownership of property, pay property tax on their behalf
Document Verifier (DV)
Verify and forward
Send Back
Edit Application
Employees responsible for verifying the supporting documents submitted by citizens for a new property or transfer of ownership of property
Field Inspector (FI)
Verify and forward
Send Back
Reject
Edit
Employees who go on to the field (i.e. location of property) and physically verifies the information provided by the applicant is correct
Approver
Approve
Send Back
Reject
Cancel
An employee who has the final authority to approve or reject the property registration
Title | Link |
Environment Variables | Description |
egov.wf.default.offset | The default value of offset in search |
egov.wf.default.limit | The default value of limit in search |
egov.wf.max.limit | The maximum number of records that are returned in search response |
egov.wf.inbox.assignedonly | Boolean flag if set to true default search will return records assigned to the user only, if false it will return all the records based on the user’s role. (default search is the search call when no query params are sent and based on the RequestInfo of the call, records are returned, it’s used to show applications in employee inbox) |
egov.wf.statelevel | Boolean flag set to true if a state-level workflow is required |
DIGIT offers key municipal services such as Public Grievance & Redressal, Trade License, Water & Sewerage, Property Tax, Fire NOC, and Building Plan Approval.
Learn all about setting up DIGIT and its various components.
Details for these pages coming up soon...
Details coming soon...
Details coming soon...
Details coming soon...
Details coming soon...
Content of pages within this document is designed to help implementation parties and end-users in providing the required data in minimal interaction and iterations and ensure the quality, consistency and shape of data needed to configure into the system.
This page is intended to help stakeholders as given below on data gathering activities.
State Team
eGov Onsite Team/ Implementation Team
ULB Team (Nodal and DEO)
Implementation Partners
The artefacts of this document are the data template of a configurable entity, a page with content defining the entity template and helping on how to fill the template with required data.
Title | Link |
API Contract |
Title | Link |
Configuring Workflows For New Product/Entity |
Setting Up Workflows |
API Swagger Documentation |
Migration to Workflow 2.0 |
Title | Link |
/businessservice/_create |
/businessservice/_update |
/businessservice/_search |
/process/_transition |
/process/_search |
Public Grievances & Redressal (PGR) is a system that enables citizens to raise a complaint with the ULBs. A citizen can track the complaint, upload image related to the complaint, re-open the complaint if he/she is not satisfied and rate the service. This document contains the details about how to setup PGR service and describes the functionalities it provides
Before you proceed with the configuration, make sure the following pre-requisites are met -
Java 8
Kafka server is up and running
egov-persister service is running and has pgr-services persister config path added in it
PSQL server is running and database is created to store complaint data
(Optional) Indexer config for pgr-services is added in egov-indexer yaml paths to index the generated data. Index is required for data visualisation in Kibana or in DSS.
(Optional) Report config for pgr-services is added in Report service config paths. Required if reports are to be provided to the user.
Following services should be up and running:
egov-user
egov-workflow-v2
egov-perister
egov-localization
egov-notification-sms
egov-mdms
egov-idgen
egov-url-shortening
egov-hrms
A citizen can file, track and rate the complaint
A citizen can add image and comments related to the complaint
A citizen can re-open the complaint in a certain given period of time after resolution
ULB can setup the complaint workflow according to their requirements and staff capacity
ULB can track the SLA for resolving each complaint and can use it as a metric to streamline the process for resolving complaints
Department wise assignment of the complaint to the LME
Deploy the latest version of pgr-services
Add pgr-service-persister.yml file in config folder in git and add that path in persister. (The file path is to be added in environment yaml file in param called persist-yml-path )
If any Report Config is created, the config should be added to the config folder in git and that path should be added in Report service. (The file path is to be added in a file called “reportFileLocationsv1.txt” in Config folder)
If index is to be created add the indexer config path in indexer service. (The file path is to be added in environment yaml file in param called egov-indexer-yaml-repo-path)
Add master data in MDMS service with the module name as RAINMAKER-PGR. Following is some sample master data for the service:
Create businessService (workflow configuration) using the __/businessservice/_create. Following is the product configuration for PGR:
Using /localization/messages/v1/_upsert , add localisation (templates) for notification messages to be sent. Following are the product notification templates:
Add Role-Action mapping for the APIs in MDMS. Following are the required entries. They should be mapped to both CITIZEN and appropriate employee roles.
PGR service can be integrated with any organisation or system which wants to track customer queries or complaint. The organisations can customise the workflow depending on their product requirements.
Easy tracking and resolution of complaints
Configurable workflow according to client requirement
Customer can raise a complaint using the /requests/_create
.
Organisation or System can search the complaint using /requests/_searchendpoint
.
Once the complaint is raised the organisation or system can call /requests/_update
endpoint to move the application further in workflow until it gets resolved.
eGov Payment Gateway acts as a liaison between eGov apps and external payment gateways facilitating payments, reconciliation of payments and lookup of transactions' status'.
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 pg service persister config path added in it
PSQL server is running and the database is created to store transaction data.
Create or initiate a transaction, to make a payment against a bill.
Make payment for multiple bill details [multi module] for a single consumer code at once.
Transaction to be initiated with a call to the transaction/_create API, various validations are carried out to ensure the sanctity of the request.
The response includes a generated transaction id and a redirect URL to the payment gateway itself.
Various validations are carried out to verify the authenticity of the request and the status is updated accordingly. If the transaction is successful, a receipt is generated for the same.
Reconciliation is carried out by two jobs scheduled via a Quartz clustered scheduler.
Early Reconciliation job is set to run every 15 minutes [configurable via app properties], and is aimed at reconciling transactions which were created 15 - 30 minutes ago and are in PENDING state.
Daily Reconciliation job is set to run once per day and is aimed at reconciling all transactions that are in PENDING state, except for ones which were created 30 minutes ago.
Axis, Phonepe and Paytm payment gateways are implemented.
Additional gateways can be added by implementing the Gateway interface. No changes required to the core packages.
Following properties in the application.properties file in egov-pg-service has to be added and set to default value after integrating with the new payment gateway. In the below table properties for AXIS bank, payment gateway is shown the same relevant property needs to be added for other payment gateways.
Deploy the latest version of egov-pg-service
Add pg service persister yaml path in persister configuration
The egov-pg-service acts as communication/contact between eGov apps and external payment gateways.
Record of every transaction against a bill.
Record of payment for multiple bill details for a single consumer code at once.
To integrate, host of egov-pg-service should be overwritten in helm chart
/pg-service/transaction/v1/_create should be added in the module to initiates a new payment transaction, on successful validation
/pg-service/transaction/v1/_update should be added as the update endpoint to updates an existing payment transaction. This endpoint is issued only by payment gateways to update the status of payments. It verifies the authenticity of the request with the payment gateway and forward all query params received from a payment gateway
/pg-service/transaction/v1/_search should be added as the search endpoint for retrieving the current status of a payment in our system.
(Note: All the API’s are in the same postman collection, therefore, the same link is added in each row)
BPA application and BPA Occupancy Certificate application has Fee involved. Based on the Application Type, RiskType and ServiceType Fee to be calculated and generates a demand for the calculated amount for Payment. This service used to generate Application Fee, Sanction Fee, Low Application Permit Fee, Deviation Charges for BPA application and Occupancy Certificate Application.
Knowledge of Java/J2EE(preferably Java 8 version)
Knowledge of Spring Boot and spring-boot microservices.
Knowledge of Git or any version control system.
Knowledge of RESTful Web services.
Knowledge of the Lombok library will helpful.
knowledge of eGov-mdms service, eGov-persister, eGov-idgen, eGov-sms, eGov-email, eGov-user, eGov-localization, bpa-services will be helpful.
bpa calculator services present in municipal services provide multiple functionalities like calculating Application Fee, Sanction Fee, Low Permit Fee, OC Deviation Charges, generating demands for a particular BPA, BPA OC applications, updating demands, The different functionalities provided by sewerage calculator services are:
The Application is present among the municipal services group of applications available in the eGov-services git repository with the folder name bpa-calculator. The spring boot application needs the Lombok* extension added in your IDE to load it. Once the application is up and running API requests can be posted to the URL and ids can be generated.
in case of IntelliJ, the plugin can be installed directly, for eclipse the Lombok jar location has to be added in eclipse.ini file in this format javaagent:lombok.jar
Business service codes for
BPA High/Medium Risk Application Fee
egov.demand.appl.businessservice=BPA.NC_APP_FEE
BPA High/Medium Risk Sanction Fee
egov.demand.sanc.businessservice=BPA.NC_SAN_FEE
BPA Low Risk Permit Fee
egov.demand.lowriskpermit.businessservice=BPA.LOW_RISK_PERMIT_FEE
BPA OC Application Fee
egov.demand.oc.appl.businessservice=BPA.NC_OC_APP_FEE
BPA OC Sanction Fee
egov.demand.oc.sanc.businessservice=BPA.NC_OC_SAN_FEE
Tax Head Code for
BPA High/Medium Risk Application Fee
egov.appl.fee=BPA_APPL_FEES
BPA High/Medium Risk Sanction Fee
egov.sanc.fee= BPA_SANC_FEES
BPA Low Risk Sanction Fee
egov.low.sanc.fee= BPA_LOW_SANC_FEES
BPA Low Risk Application Fee
egov.low.appl.fee=BPA_LOW_APPL_FEES
BPA OC Application Fee
egov.oc.appl.fee=BPA_OC_APPL_FEES
BPA OC Sanction Fee
egov.oc.sanc.fee= BPA_OC_SANC_FEES
External Application references
dcr-services (Use Edcr data )
egov-mdms ( Configurations/master by MDMS )
billing-service ( Generate and update demands )
bpa-services (Get the bpa application data for fee calculation )
bpa-calculator/v1/_calculate End point to calculate the Fee and create Demand with the applicable businessService and TaxHeads
Access MDMS Config
bpa-calculator cannot be accessed publicly, Only called by the bpa-calculator
Billing Service MDMS Config
BusinessService Config for Fee’s to be collected
Application Fee, Sanction Fee BPA High/Medium Risk
Application Fee, Sanction Fee for BPA Low Risk
Application Fee, Sanction Fee for BPA OC
TaxHead MDMS
Tax Head for BPA High/Medium Risk
TaxHead config for BPA Low Risk
TaxHead config for BPA OC
TaxPeriod MDMS Config
TaxPeriod MDMS for BPA High/Medium Risk
TaxPeriod MDMS for BPA Low Risk
TaxPeriod Config for BPA OC
NA
NA
NA
NA
NA
Construction or renovation of buildings is regulated by Municipal Body in India. One must get permission from the ULB prior to construction. This process involves submitting the building plan to ULB along with other documents, ULB verifies the plan with other documents and approves the construction. The document which authorizes the construction is called “Permit Order” One must have this permit order with him till the completion of construction. ULB officials will inspect various stages of construction and make sure it is compliance with the plan. When construction completed, after inspection Secretary provides “Completion certificate” and finally will provide “Occupancy Certificate”. This entire process is known as “Building Plan Approval”.
This section covers the high-level details of the functionalities available in the Building Plan Application system.
Centralized login page for citizen, official and stakeholders
Citizen functionalities
Online application submission - New construction
Occupancy certificate request
FieldInspection Report Capture
Pay fee online and generate permit order online
Inspection of applications and online status
Configurable workflow
Auto fee calculation
Online and offline payment collection
Rejection process
Revocation process
Configurable functionalities
Knowledge of Java/J2EE(preferably Java 8 version)
Knowledge of Spring Boot and spring-boot microservices
Knowledge of Git or any version control system
Knowledge of RESTful Web services
Knowledge of the Lombok library will helpful
knowledge of eGov-mdms service, eGov-persister, eGov-idgen, eGov-sms, eGov-email,eGov-user, eGov-localization, eGov-workflow-service,dcr, land-services, bpa-calculator will be helpful
The Application is present among the municipal services group of applications available in the eGov-services git repository with the folder name bpa-services. The spring boot application needs the Lombok* extension added in your IDE to load it. Once the application is up and running API requests can be posted to the URL and ids can be generated.
in case of IntelliJ, the plugin can be installed directly, for eclipse the Lombok jar location has to be added in eclipse.ini file in this format javaagent:lombok.jar
Please refer to Swagger API for YAML file details. Link - API Specs.
Here we are listing the configs apart from dependent service host, URLs, DB and Flyway configs.
kafka topics persister configs for eGov persister to save and update BPA Data
persister.save.buildingplan.topic=save-bpa-buildingplan
persister.update.buildingplan.topic=update-bpa-buildingplan
persister.update.buildingplan.workflow.topic=update-bpa-workflow
persister.update.buildingplan.adhoc.topic=update-bpa-adhoc-buildingplan
Receipt kafka topics where BPA application listens to move the application Status after payment completion
kafka.topics.receipt.create=egov.collection.payment-create
Config for Demand Business service codes for different fees to be paid for BPA
egov.receipt.businessservice=
BPA.NC_APP_FEE := Building Plan Approval Application Fee
BPA.NC_SAN_FEE := Building Plan Approval Sanction Fee
BPA.LOW_RISK_PERMIT_FEE := Building Plan Approval Low Risk Permit Fee
BPA.NC_OC_APP_FEE := Building Plan Approval Occupancy Certificate Application Fee
BPA.NC_OC_SAN_FEE := Building Plan Approval Occupancy Certificate Sanction Fee
Application and Permit Number Formats
egov.idgen.bpa.applicationNum.format=PB-BP-[cy:yyyy-MM-dd]-[SEQ_EG_BP_APN]
egov.idgen.bpa.permitNum.format=PB-BP-[cy:yyyy-MM-dd]-[SEQ_EG_BP_PN]
SMS Notification Topic to push the SMS and Notification’s to be sent by BPA module
kafka.topics.notification.sms=egov.core.notification.sms
Payment Notification Config
egov.ui.app.host=https://egov-micro-dev.egovernments.org
egov.usr.events.create.topic=persist-user-events-async
egov.usr.events.pay.link=citizen/otpLogin?mobileNo=$mobile&redirectTo=egov-common/pay?consumerCode=$applicationNo&tenantId=$tenantId&businessService=$businessService
egov.usr.events.pay.code=PAY
List of Application Statuses on which payment notification to be sent
egov.usr.events.pay.triggers=PENDING_SANC_FEE_PAYMENT,PENDING_APPL_FEE,PENDING_FEE
Validity of the permit order generated in no of months
egov.bpa.validity.date.in.months=36
Workflow code for the combination of applicationType , ServiceType
appSrvTypeBussSrvCode={"BUILDING_PLAN_SCRUTINY":{"NEW_CONSTRUCTION":"BPA,BPA_LOW"},"BUILDING_OC_PLAN_SCRUTINY":{"NEW_CONSTRUCTION":"BPA_OC"}}
Application Status on which SKIP_PAYMENT action to be considered
egov.bpa.skippayment.status=PENDING_APPL_FEE,PENDING_SANC_FEE_PAYMENT,PENDING_FEE
Business Service Code for WorkflowCode and Application Status
workflowStatusFeeBusinessSrvMap={"BPA":{"PENDING_APPL_FEE":"BPA.NC_APP_FEE","PENDING_SANC_FEE_PAYMENT":"BPA.NC_SAN_FEE"},"BPA_LOW":{"PENDING_FEE":"BPA.LOW_RISK_PERMIT_FEE"},"BPA_OC":{"PENDING_APPL_FEE":"BPA.NC_OC_APP_FEE","PENDING_SANC_FEE_PAYMENT":"BPA.NC_OC_SAN_FEE"}}
NOC application Integration configs
Config to validate the status of applicable noc’s status to allow application to move forward from NOC_VERIFICATION_PENDING Workflow State
validate.required.nocs.statuses=APPROVED,AUTO_APPROVED,REJECTED,VOIDED
NOC workflow initiate action code to initiate the workflow of the NOC when appliation reachers the respective nocTrigerState
egov.noc.initiate.action=INITIATE
NOC workflow void action code to void the applicable NOC’s, when the application moved to REJECTED State
egov.noc.void.action=VOID
NOC workflow action goes for AutoAprove to auto-approve offline NOC , while moving from NOC_VERIFICATION_PENDING to next state
egov.noc.autoapprove.action=AUTO_APPROVE
egov-user - (Manage user)
tl-services - Stakeholder Registration (Registration process of Stakeholder is handled by this service)
egov-user-event (What’s New and Events)
egov-filestore (To store the documents uploaded by the user)
egov-idgen (To generate the application No, Permit No)
egov-indexer (To index the BPA data)
egov-localization (To use the localized messages)
egov-location (To store the address locality)
egov-mdms (Configurations/master data used in the application is served by MDMS)
egov-notification-sms (Service to send SMS to the users involved in the application)
egov-persister (Helps to persist the data)
egov-searcher (Search query used to simplify the search)
egov-workflow-v2 (Workflow configuration for different BPA application is configured)
pdf-service (Receipt’s, permit order etc.. and prepared)
billing-service (Create demands and bills for the fees to be collected)
collection-services (Create a receipt for the payment received for the bills)
bpa-calculator (Calculates the fees to be collected at different stages)
land-services (land information related to BPA application is stored)
dcr-services (get and validate EDCR data)
noc-services (NOC application)
Under the data/<state code> folder you can find the BPA which has all the MDMS JSON’s
master-config.json for BPA
Action Test : URL Actions adding
Access to the Roles for the above Actions
BusinessService Config for Fee’s to be collected
Application Fee, Sanction Fee BPA High/Medium Risk
Application Fee, Sanction Fee for BPA Low Risk
Application Fee, Sanction Fee for BPA OC
Tax Head for BPA High/Medium Risk
TaxHead config for BPA Low Risk
TaxHead config for BPA OC
TaxPeriod MDMS for BPA High/Medium Risk
TaxPeriod MDMS for BPA Low Risk
TaxPeriod Config for BPA OC
BPA Application Number format Config
BPA Permit Number format Config
BPA Receipt Number format config
BPA OC Receipt Number format config
Setup the locality Search query in the localitySearcher.yml as a new entry. Add RoleAction Test and Role Action for the URL “
/egov-searcher/locality/bpa-services/_get
“
BPA - Building Plan Approval Apply High/Medium Risk
BPA Low – Building Plan Approval Apply Low Risk
BPA OC - Building Plan Approval Occupancy Certificate Apply
BPA and BPA OC Workflow Stages
BPA workflow configuration is for Building Plan Approval Apply High and Medium Risk Types.
BPA OC workflow configuration is for Building Plan Approval Occupancy Certificate irrespective of RiskTypes
Both the workflow flows as depicted below
In the above Flow Chart
Rectangle Indicates the Workflow State
Line connecting two states indicates the action
Action name is in black colour text
User Role who can take action is in Blue colour Text
Specific Configurations and How To’s
System allows configuring the Documents that can be visible, allowed to upload and Mandatory to move from the current state in DocumentTypeMapping MDMS as described in MDMS Details Table DocumentTypeMapping Row
Application Creation Sage
Process
DCR system is integrated to get the applicationType, serviceType and riskType based on the EDCR Number populated by the architect.
DCR system is integrated to validate the status of the EDCRNumber populated
New BPA or BPAOC application cannot be created if there is existing un ended( application status other than approved or rejected is considered as unended) application with the same EDCR
How To add new Document
Should add new documentType group in DocumentTypeMapping MDMS with the applicable applicationType, serviceType, riskType, wfState (refer existing sample for understanding)
Can configure allow, required as well as the order for each documentType
Make sure the new documentType added exists in documentType of common-masters
Initiated Stage
Process
NOC’s from the NocTypeMapping MDMS matching to the application data will get created
How To add new NocType
Should add new NOCType in NocTypeMapping MDMS
New NocType should add in noc-services application as well
Citizen Approval Pending Stage
Process
According to the example in the NocTypeMapping Data in the MDMS Details Table, Once BPA or BPA OC reaches this Staus all the Applicable Noc’s workflow would be initiated.
How to change NOC workflow initiation step
Should change the nocTriggerState in NocTypeMapping to the desired application status.
InProgress Stage
Process
Application fee Demand gets generated by the bpa-calculator
Notification to the Stakeholder and owner will be sent regarding the fee payment
How To change the Fee Amount
Will be discussed in bpa-calculator service
Document Verification Pending Stage
Process
Nothing Specific
How To
NA
FieldInspection Pending Stage
Process
At this stage, FieldInspector should answer the checklist questions and attached the documents which will be configured in checklist MDMS, as described in MDMS Details Table CheckList Row
Field Inspector can create multiple FieldInspection Reports
How to add new questions and documents
Should add/modify the questions for the desired combination of applicationType, serviceType, risktype
with the localization code for question text
specify the fieldType ( ass of now only YES/NO/NA only supported )
Should add/modify documents for the desired combination of applicationType, serviceType, risktype
Noc Verification Pending State
Process
NOC verifier can upload the Documents to the NOC application’s if available.
Offline Noc’s would get auto-approved while NOC verifier is forwarding the BPA or BPAOC application from the current state
BPA or BPAOC application cannot be forwarded if any NOC is not in matching the status configured for validate.required.nocs.statuses in application.properties
How to change the NOC application status to be verified to move forward
should update the validate.required.nocs.statuses property in value in application.properties with the list of status to be considered to move forward
Approval Pending Stage
Process
Approver can select the predefined conditions for approval updated in CheckList MDMS, as described in MDMS Details Table checkList Row
Approver can add new conditions as well for approval
Sanction fee Demand gets generated by the bpa-calculator
Notification to the Stakeholder and owner will be sent regarding the fee payment
How to add/remove/modify conditions
Should add/modify the conditions array for the desired combination of applicationType, serviceType, riskType
Approved Stage
Process
System generates PermitOrder for the application
System Stamps the validate date for the permit Order by adding the no of months configured for the property egov.bpa.validity.date.in.months in application.properties
How to change the validity period of the permit order which will generate from now
Change the value of the property egov.bpa.validity.date.in.months in application.properties file to the desired no of months
How to change Permit Order
Can be changed by changing the data and format configs of the permit order, please refer PDF’s section of Permit Order
Rejected Stage
Process
NA
BPA LOW Workflow
BPA with riskType low has a separate workflow, which is almost same as the BPA workflow as depicted below
In the above Flow Chart
Rectangle Indicates the Workflow State
Line connecting two states indicates the action
Action name is in black colour text
User Role who can take action is in Blue colour Text
Specific Configurations and How To’s which are not common to BPA Workflow
InProgress Stage
Process
Application and Sanction Fee together gets calculated and Demand gets generated by the bpa-calculator
Notification to the Stakeholder and owner will be sent regarding the fee payment
How To change the Fee Amount
Will be discussed in bpa-calculator service
Document Verification Pending Stage
Process
System generates PermitOrder for the application
System Stamps the validate date for the permit Order by adding the no of months configured for the property egov.bpa.validity.date.in.months in application.properties
How to change the validity period of the permit order which will generate from now
Change the value of the property egov.bpa.validity.date.in.months in application.properties file to the desired no of months
Approved Stage
Process
NA
Revocated Stage
Process
System generates Revocation letter
How to change Revocation Letter format
Can be changed by changing the data and format configs of the revocation letter, please refer PDF’s section of Revocation letter
On Workflow action of Every Stage, System verifies the Documents Configured for the given stage of the workflow from the DocumentTypeMapping MDMS and validates the required Documents attached to move forward
DropDown values to be validated against the MDMS values, Value in those fields should be one of the MDMS value.
Notifications Message codes for SMS and User Events are prepared as follows
ApplicationType_ServiceType_WorkflowAction_ApplicationStatus.
Example BPA Apply Application (i.e applicationType is BUILDING_PLAN_SCRUTINY) with ServiceType NEW_CONSTRUCTION and the current application status is DOCUMENT_VERIFICATION_PENDING and workflow Action of the request is FORWARD then the localized message for this notification will be looked for the code: BUILDING_PLAN_SCRUTINY_NEW_CONSTRUCTION_FORWARD_DOCUMENT_VERIFICATION_PENDING
The message text for the above code is sent through SMS and Notification filling the owner, serviceType, application Number and other values.
BPA supports below PDF’s
For every building plan application, there is a need to get the No objection certificate from concerned departments. Based on the configuration we have for the NOCs, for every application, there will be a set of NOCs required. There should be a provision to allow the NOC department user to login to our system and upload the required NOC. We are providing a user to one NOC department. Based on the workflow mode(online/offline) of each NOC type, the NOC department user can perform the action.
Online mode – NOC department user can log in to the system and approve/reject the application.
Offline mode – NOC application will be auto-approved.
Knowledge of Java/J2EE(preferably Java 8 version)
Knowledge of Spring Boot and spring-boot microservices.
Knowledge of Git or any version control system.
Knowledge of RESTful Web services.
Knowledge of the Lombok library will helpful.
knowledge of eGov-mdms service, eGov-persister, eGov-idgen, eGov-user, eGov-localization will be helpful.
egov-user (Manage user)
egov-idgen (To generate the application No)
egov-localization (To use the localized messages)
egov-location (To store the address locality)
egov-mdms (Configurations/master data used in the application is served by MDMS)
egov-notification-sms (Service to send SMS to the users involved in the application)
egov-persister (Helps to persist the data)
egov-workflow-v2 (Workflow configuration for different BPA application is configured)
Please refer to Swagger API for YAML file details. Link - API Specs.
Fire Noc: online configuration
Airport Authority: online configuration
NA
NA
This service is used to issue a license to the user after verification. The service is designed in such a way that it can be used to serve different type of licenses. Currently used to issue trade licenses, perform stakeholder registration and issue lockdown pass. The service is integrated with workflow where we can define the steps for approval of the application. Once the application is approved the license is generated.
Before you proceed with the documentation, make sure the following pre-requisites are met -
Java 8
Kafka server is up and running
egov-persister service is running and has tl-services persister config path added in it
PSQL server is running and database is created
Used for license generations in trade licenses, stakeholder registration and issue lockdown pass
Define roles to applicants on successful application to access Building Plan Approval services at the time of stakeholder registration
Generate application number and license number
Support workflows
Provide notification on various status changes for an application
Add MDMS configs required for Trade License and BPA stakeholder registration and restart MDMS service
Deploy the latest version of tl-services service
Add tl-service persister yaml path in persister configuration and restart persister service
Add Role-Action mapping for API’s
Create businessService (workflow configuration) according to trade license and stakeholder registration
Add tl-service indexer yaml path in indexer service configuration and restart indexer service
Following application properties in the Trade License service are configurable.
The trade-license service is currently used to issue trade licenses, perform stakeholder registration and issue lockdown pass.
Provide backend support for the different license registration process.
Mseva and SMS notifications on application status changes.
The elastic search index for creating visualizations and Dashboards.
Bpa Stakeholder registration provides new roles to the user to access the Building Plan Approval system.
Supports workflow which is configurable
To integrate, host of tl-services service should be overwritten in the helm chart.
{servicename}/_create/ _create should be added as the create endpoint for creating any license in the system
{servicename}/_search/ _search should be added as the search endpoint. This method handles all requests to search existing records depending on different search criteria
{servicename}/_update/ _update should be added as the update endpoint. This method is used to update fields in existing records or to update the status of the application based on workflow.
In all below endpoints if the service name is BPAREG it is treated as a stakeholder registration application and if it is TL or if it is absent then the application is treated as trade license application.
Stakeholder registration APIs:- https://www.getpostman.com/collections/d18b79ccfb69ee8bb526
Trade-License APIs:- https://www.getpostman.com/collections/99f98723c45f97024831
This service is the major service supporting bpa-services which handles the data of the land like land details, owner information, unit, address and documents which has the complete information of the land.
Which can be used as input for the bpa-services to create and process the Building Plan Application.
This section covers the high-level details of the functionalities available Land Service
UI integrated as part of BPA screens
Ability to create/update Land Details
Knowledge of Java/J2EE(preferably Java 8 version)
Knowledge of Spring Boot and spring-boot microservices.
Knowledge of Git or any version control system.
Knowledge of RESTful Web services.
Knowledge of the Lombok library will helpful.
knowledge of eGov-mdms service, eGov-persister, eGov-idgen, eGov-user, eGov-localization will be helpful.
The Application is present among the municipal services group of applications available in the eGov-services git repository with the folder name land-services. The spring boot application needs the Lombok* extension added in your IDE to load it. Once the application is up and running API requests can be posted to the URL and ids can be generated.
in case of IntelliJ, the plugin can be installed directly, for eclipse the Lombok jar location has to be added in eclipse.ini file in this format javaagent:lombok.jar
Please refer to Swagger API for YAML file details. Link - API Specs.
Here we are listing the configs apart from dependent service host, url’s, DB and Flyway configs.
kafka topics persister configs for eGov persister to save and update land Data
persister.save.landinfo.topic=save-landinfo
persister.update.landinfo.topic=update-landinfo
egov-user - ( Manage user )
egov-filestore ( To store the documents uploaded by the user )
egov-idgen ( To generate the application No, Permit No )
egov-indexer ( To index the bpa data )
egov-localization ( To use the localized messages )
egov-location ( To store the address locality )
egov-mdms ( Configurations/master data used in the application is served by MDMS )
egov-persister ( Helps to persist the data )
There is not MDMS config for Land Service exists as of now.
Access MDMS Config
Action Test : URL Actions adding
Access to the Roles for the above Actions
NA
NA
NA
MDMS stands for Master Data Management Service. MDMS is One of the applications in the eGov DIGIT core group of services. This service aims to reduce the time spent by developers on writing codes to store and fetch master data ( primary data needed for module functionality ) which doesn’t have any business logic associated with them.
Before you proceed with the configuration, make sure the following pre-requisites are met -
Prior Knowledge of Java/J2EE.
Prior Knowledge of Spring Boot.
Prior Knowledge of REST APIs and related concepts like path parameters, headers, JSON, etc.
Prior knowledge of Git.
Advanced knowledge on how to operate JSON data would be an added advantage to understand the service.
The MDMS service reads the data from a set of JSON files from a pre-specified location.
It can either be an online location (readable JSON files from online) or offline (JSON files stored in local memory).
The JSON files will be in a prescribed format and store the data on a map. The tenantID of the file serves as a key and a map of master data details as values.
Once the data is stored in the map the same can be retrieved by making an API request to the MDMS service. Filters can be applied in the request to retrieve data based on the existing fields of JSON.
For deploying the changes in MDMS data, the service needs to be restarted.
The changes in MDMS data could be adding new data, updating existing data, or deletion.
The config JSON files to be written should follow the listed rules
The config files should have JSON extension
The file should mention the tenantId, module name, and the master name first before defining the data
Example Config JSON for “Billing Service”
MDMS supports the configuration of data at different levels. While we enable a state there can be data that is common to all the ULB’s of the state and data specific to each ULB’s. The data further can be configured at each module level as state-specific or ULB’s specific.
Before you proceed with the configuration, make sure the following pre-requisites are met -
Prior Knowledge of Java/J2EE.
Prior Knowledge of Spring Boot.
Prior Knowledge of REST APIs and related concepts like path parameters, headers, JSON, etc.
Prior knowledge of Git.
Advanced knowledge on how to operate JSON data would be an added advantage to understand the service.
State Level Masters are maintained in a common folder.
ULB Level Masters are maintained in separate folders named after the ULB.
Module Specific State Level Masters are maintained by a folder named after the specific module that is placed outside the common folder.
For deploying the changes(adding new data, updating existing data or deletion) in MDMS, the MDMS service needs to be restarted.
State Level Master Configuration
The common master data across all ULB’s and modules like department, designation, etc are placed under the common-masters folder which is under the tenant folder of the MDMS repository.
The common master data across all ULB’s and are module-specific are placed in a folder named after each module. These folders are placed directly under the tenant folder.
ULB Level Master Configuration
Modules data that are specific to each ULB like boundary data, interest, penalty, etc are configured each ULBwise. There will be a folder per ULB under the tenant folder and all the ULB’s module-specific data are placed under this folder.
Tenant represents a body in a system. In the municipal system, a state and its ULBs (Urban local bodies) are tenants. ULB represents a city or a town in a state. Tenant configuration is done in MDMS.
Before proceeding with the configuration, the following pre-requisites are met -
Knowledge of json and how to write a json is required.
Knowledge of MDMS is required.
User with permissions to edit the git repository where MDMS data is configured.
For login page city name selection is required. Tenant added in MDMS shows in city drop-down of the login page.
In reports or in the employee inbox page the details related to ULB is displayed from the fetched ULB data which is added in MDMS.
Modules i.e., TL, PT, MCS can be enabled based on the requirement for the tenant.
After adding the new tenant, the MDMS service needs to be restarted to read the newly added data.
Tenant is added in tenant.json. In MDMS, file tenant.json, under tenant folder holds the details of state and ULBs to be added in that state.
Naming Convention for Tenants Code
“Code”:“uk.citya” is StateTenantId.ULBTenantName"
Localization should be pushed for ULB grade and ULB name. The format is given below.
Localization for ULB Grade
Localization for ULB Name
Format of localization code for tenant name <MDMS_State_Tenant_Folder_Name>_<Tenants_Fille_Name>_<Tenant_Code> (replace dot with underscore)
Boundary data should be added for the new tenant.
Configuring Master Data for a new module requires creating a new module in the master config file and adding masters data. For better organizing, create all the master data files belongs to the module in the same folder. Organizing in the same folder is not mandatory it is based on the moduleName in the Master data file.
Before you proceed with the configuration, make sure the following pre-requisites are met -
User with permissions to edit the git repository where MDMS data is configured.
These data can be used to validate the incoming data.
After adding the new module data, the MDMS service needs to be restarted to read the newly added data.
Adding new module
The Master config file is structured as below. Each key in the Master config is a module and each key in the module is a master.
The new module can be added below the existing modules in the master config file.
Creating Masters data
The URL shortening service is used to shorten long URLs. There may be requirement when we want to avoid sending very long urls to the user via SMS, Whatsapp etc, this service compresses the URL.
Before you proceed with the configuration, make sure the following pre-requisites are met -
Prior Knowledge of Java/J2EE
Prior Knowledge of SpringBoot
Prior Knowledge of REST APIs and related concepts like path parameters, headers, JSON etc.
Compress long URLs.
Converted short URLs contains id, which is used by this service to identify and get longer URLs.
Deploy latest version of URL Shortening service
Receive long urls and converts them to shorter urls. Shortened urls contains urls to endpoint mentioned next. When user clicks on shortened URL, user is redirected to long URL.
This shortened urls contains path to this endpoint. The service uses id used in last endpoint to get long URL. As response the user is redirected to long URL.
DIGIT 2.2 changes in HRMS module
This release offers capabilities to re-activate and deactivate employees from the UI to the ULB administrators. Also, we’ve standardized the input field validation as in other products on the DIGIT platform.
Deactivate employee
Re-activate employee
Usability enhancements like input validations, searchable dropdowns, etc.
None
Multi-tenancy support in the product
Reports
DIGIT 2.2 Changes in the Property Tax Module
The latest release version of the Property Tax module focuses on enhancing application usability, handling instances of payment failure, and the capability to capture data for better reporting & dashboards. Also, employees can now cancel the receipts from the UI to promote efficient service delivery.
Search API enhancements
UI for cancel receipt
Capturing transactional data for reporting
Transfer of ownership 'Transferee details' validations
None
None
New release features, enhancements, and fixes
DIGIT 2.2 is a release that has got a few functional changes and few non-functional standardization changes.
Functional: PGR v2 (Revamped UI/UX, Revamped APIs, and Workflow integration), Water & Sewerage Enhancements (Public Domain Search, Open Payments, and PT Workflow Config Changes), Property Enhancements, Search/Cancel Receipts Screen, and Enhancements in HRMS.
Non-functional: Config Repo baselining (Indexer and Persister configs sem version and baselining).
DIGIT 2.2 changes in the PGR Module
This release provides a revamped UX to all the stakeholders using the PGR product. Updated UX will drive the adoption and increase employee efficiency. Also, we’ve configured a workflow service in the product which will speed up the GTM speed as it can be configured easily.
Revamped UI and UX for all stakeholders
API redesign and workflow integration
PGR migration from v1 to v2 including the workflow data and reindexing
DSS config changes to support PGR v2
None
None
Product themes and deliverable
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.
Water & Sewerage (W&S) -
Provide the capability to apply for new Water and Sewerage Connection. This simplifies the application process for Citizens and for Employees.
All the steps from application submission to connection provision are digitized.
All the processes and steps can be mapped to SLAs to enable tracking and monitoring for improving quality of service to citizens
Through standard workflows and notifications, citizens are updated on the status of the application and action needed.
Provide a configurable ‘Connection fee’ computation mechanism
The Water and Sewerage Connection is integrated with the DIGIT Property Registry. This enables ULBs to maintain a single source of truth for Properties in a decentralized manner, and ensure data is updated in a transparent and verifiable manner.
Property Tax (PT) -
Provide Citizens with the capability to search properties registered in DIGIT in the public domain without Login.
EoDB mandates the following details about a Property should be verifiable information, available in the public domain -
Ownership of the property for prospective buyers
Pending dues
Historical or past data about the property
Online Building Plan Approval System(OBPAS) -
Provide the capability to scrutinize the plan diagram for occupancy certificate post-construction online
Facilitate stakeholder to apply for an occupancy certificate application online
Provision to view the comparison report online, which shows the delta between permit diagram before construction and OC diagram post-construction.
Enable document scrutiny and real-time field inspection by the ULB officials
Generate occupancy certificate online with QR code
The entire application process is digitized without manual intervention.
Enable Citizen to make payments for a permit online
Keep Citizen informed of the application current status and probable SLAs by which the task would be complete
Integrated user Experience -
Enable ease of payments for Citizens
Citizens can pay their property tax dues without having to login into the system. Citizens can access this feature from open search, SMS/email notification, or any physical artefact having a payment link
At the time of bill generation, SMS and an email notification will be triggered to the citizen’s registered IDs. The notification will have a payment link that will direct the citizen to the common payment page. Users can make the payment without having to log in.
Bills will have a payment QR code printed. Each bill will have a unique QR code which will be a link to the common pay page.
Water & Sewerage (W&S) -
Provide the capability to modify existing Water and Sewerage Connection. This simplifies the process for modification of Connection for Citizens and for Employees in a transparent manner through
Notifications
Workflow steps for verification of details
Decision Support System (DSS) -
Enhancements to Real-Time Dashboards with focus on the following
Improved drill-downs and drill throughs
Enhancements to search capability
Redesign for greater usability through mobile
Rigorous testing on multiple browsers and device sizes to improve responsiveness
Online Building Plan Approval System(OBPAS) -
EODB mandates CAF ( Common application form) for building permits
Allows citizen to create permit application as well as the application for NOCs in a single interface
Facilitate NOC department users to log in to the system online
View and process the application
Provide NOC online
Facilitate ULB users to validate the NOCs provided by the NOC department user online and process the building permit and occupancy certificate application.
Enable citizen to check the status of both permit application and NOC application online
Enhancement to Platform Capability -
Capability to handle Advance payments. This will be a platform level capability available for all Services. The first reference implementation of this will be with the Water & Sewerage module
Pay/ Adjust excess amount against the demand generated
Generate Receipt showing the excess payment
Generate Bill with advance amount adjustment
PGR Integration with WorkFlow service
The integration will help PGR to get features of workflow directly such as common Inbox for the employee, configurable actions for a role, view history, edit, comment, view summary
Workflow configuration will be possible while implementing it in new states (if required) as per their requirement.
Integrated user Experience -
Provide the capability to make payments through Whatsapp
Creating an additional channel for payment
Improve demand collection efficiency
Improve the ease of search and view bills
Improve speed and convenience for bill payment
Revamp the ‘User Experience’ to improve ease of use and ease of access for Citizens and Employees with focus on ‘Inclusiveness’
Evaluate alternative UX designs which improve- accessibility, usability and content
New Product Innovation -
Work with a knowledge partner to study and identify areas to be addressed in the domain of ‘Non-networked Sewerage Management’. This study will help identify:
Need assessment
Potential areas, where Digitization can be used
Solution Map
Standardization and Simplification -
Standardization of Master Data, Configurations, Taxonomies for ease of deployment
Knowledge assets, Tools, Documentation -
Upgrades to Product and Technical Documentation, Templates, Release Documentation
Knowledge repository setup for internal users and Partners
Self-help demo setup
Product Training material
Functional Enhancements -
Functional enhancements to meet State or Partner requirements.
Possible Products - mCollect, Finance
Enhancement to Platform Capability -
Provide the capability to configure notifications based on the channel - Email, SMS, Whatsapp
Enhancements to the Workflow services to address advanced use cases - auto-routing, escalation
Decision Support System -
Enhancements to Real-Time Dashboards to enable
Employee Performance Measurement
Configurable Notifications
Data Privacy -
Update and enhance the data privacy parameters on DIGIT in all aspects- reports, dashboards, specific modules
Standardization and Simplification -
Improve automation test cases coverage
Automating onboarding procedures
Add a provision to simplify most often asked state-level UI changes
Integrated User Experience -
Redesigned Citizen Portal with enhanced accessibility, findability
Redesigned Citizen and Employee User Experience
New Product Innovation -
Impactful product Innovation areas through validation and understanding the domain and processes involved by working with customers and partners
Proof of Concept for one Product. Possible: “ Fecal Sludge Management”
Knowledge assets, Tools, Documentation -
Upgrades to Product and Technical Documentation, Templates, Release Documentation
Knowledge repository setup
Self-help demo setup
Product Training material
For creating a new master in MDMS, create the JSON file with the master data and configure the newly created master in the master config file.
Before proceeding with the configuration, make sure the following pre-requisites are met -
User with permissions to edit the git repository where MDMS data is configured.
After adding the new master, the MDMS service needs to be restarted to read the newly added data.
Creating Master JSON The new JSON file needs to contain 3 keys as shown in the below code snippet. The new master can be created for Statewide or ULB wise. Tenant id and config in the master config file determines this.
Configuring the master config file The Master config file is structured as below. Each key in the Master config is a module and each key in the module is a master.
Each master contain the following data and keys are self-explanatory
DIGIT environment setup is conducted at two levels.
Learn how to setup DIGIT master data.
ex: ///common-masters/ Here “pb” is the tenant folder name.
ex: ///TradeLicense/ Here “pb” is the tenant folder name and “TradeLicense“ is the module name.
ex: ////TradeLicense/ Here “amritsar“ is the ULB name and “TradeLicense“ is the module name. All the data specific to this module for the ULB are configured inside this folder.
To enable tenant the above data should be pushed in tenant.json file. Here "ULB Grade" and City "Code" are important fields. ULB Grade can have a set of allowed values that determines the ULB type, (, Municipality (municipal council, municipal board, municipal committee) (Nagar Parishad), etc). City "Code" has to be unique to each tenant. This city-specific code is used in all transactions. Not permissible to change the code. If changed we will lose the data of the previous transactions done.
"logoId": "", Here the last section of the path should be "/<tenantId>/logo.png". If we use anything else, logo will not be displayed on the UI. <tenantId> is the tenant code ie “uk.citya”.
Please check the link to create new master
Environment Variable
Description
host.name
Host name to append in short URL
db.persistance.enabled
The boolean flag to store the short URL in database when flag is set as TRUE.
Title
Link
Swagger API Contract
Local Setup
Title
Link
Workflow Technical Document
User Technical Document
Link
/requests/_create
/requests/_update
/requests/_search
/requests/_count
Property
Remarks
axis.active
Bollean lag to set the payment gateway active/inactive
axis.currency
Currency representation for merchant, default(INR)
axis.merchant.id
Payment merchant Id
axis.merchant.secret.key
Secret key for payment merchant
axis.merchant.user
User name to access the payment merchant for transaction
axis.merchant.pwd
Password of the user tp access payment merchant
axis.merchant.access.code
Access code
axis.merchant.vpc.command.pay
Pay command
axis.merchant.vpc.command.status
commans status
axis.url.debit
Url for making payment
axis.url.status
URL to get the status of the transaction
Title
Link
Swagger API Contract
Title
Link
/pg-service/transaction/v1/_create
/pg-service/transaction/v1/_update
/pg-service/transaction/v1/_search
/pg-service/gateway/v1/_search
MDMS Name
Path
Description
Example Json
CalculationType
Used by bpa-calculator Service which Defines the Fee to be collected for Given ApplicationType, ServiceType, RiskType and feeType
2. Second Example defines the calculation logic to figure out the fee for the Service, considering the different parameters from EDCR information of the BPA.
ParameterPath indicates the EDCR Response Data path to get the data point.
from
Indicates the from value of the data point to be considered
to
Indicates the to value of the data point to be considered
MF
multiplication factor to be considered to multiple the datapoint value to calculate the value when data point value falls between from and to
UOM
UOM to be considered to multiple the datapoint value and MF to calculate the Fee when data point value falls between from and to
{ "applicationType": "BUILDING_PLAN_SCRUTINY", "serviceType": "ALL", "riskType": "LOW", "feeType": "SanctionFee", "amount": 500 }, { "applicationType": "BUILDING_PLAN_SCRUTINY", "serviceType": "NEW_CONSTRUCTION", "riskType": "ALL", "feeType": "ApplicationFee", "amount": 120 }, { "applicationType": "BUILDING_PLAN_SCRUTINY", "serviceType": "NEW_CONSTRUCTION", "riskType": "LOW", "feeType": "Low_ApplicationFee", "amount": 100 }, { "applicationType": "BUILDING_OC_PLAN_SCRUTINY", "serviceType": "ALL", "riskType": "ALL", "feeType": "SanctionFee", "amount": 500, "calsiLogic": [ { "parameter": "builtuparea", "tolerancelimit": 10, "calculationType": "number", "deviation": [ { "from": 11, "to": 50, "MF": 1, "uom": 100 }, { "from": 51, "to": 100, "MF": 2, "uom": 150 }, { "from": 101, "to": 499, "MF": 3, "uom": 200 } ], "paramPath": "edcrDetail[0].planDetail.virtualBuilding.totalBuitUpArea" } ] }
From the above example
indicates SanctionFee is Rs 500 for applicationType=BuildingPlanScrutiny, RiskType=LOW and any ServiceType
indicates applicationFee is Rs 120 for applicationType=BuildingPlanScrutiny, ServiceType=NEW_CONSTRUCTION and any RiskType
indicates applicationFee is Rs 100 for applicationType=BuildingPlanScrutiny, ServiceType=NEW_CONSTRUCTION and RiskType=LOW
MDMS Name
MDMS Path
Description
Example
ServiceType
Values for ServiceType Dropdown
NA
Application Type
Values for Application Type Dropdown
NA
Occupancy Type
Values for Occupancy Type Dropdown
NA
SubOccupancy Type
Values for SubOccupancy Type Dropdown
NA
DocumentTypeMapping
List’s out the documents required at the given stage of the application for Given ApplicationType, ServiceType, RiskType and WorklowState.
In the docTypes we have
Order - Indicates the sequence of the document
Code - Refers to the DocumentType parentGroup from DocumentTypes from common masters MDMS
allow - Indicates allow to edit
required - Mandatory at given stage
{ "applicationType": "BUILDING_PLAN_SCRUTINY", "ServiceType": "NEW_CONSTRUCTION", "RiskType": "LOW", "WFState": "INPROGRESS", "docTypes": [ { "code": "APPL.IDENTITYPROOF", "required": false, "allow": "false", "order": 1 }, { "code": "APPL.ADDRESSPROOF", "required": true, "allow": "true", "order": 2 } ]}
Above example indicates Documents from the common-master documentTypes starting with code(s) in the above example should be displayed in BPA Application UI when the Application of ApplicationType -BUILDINGPLAN_SCRUTINY ServiceType- NEW_CONSTRUCTION RiskType- LOW Workflow State - INPROGRESS Out of this, IDENTITY documentType is not allowed to upload in this stage and not mandatory. ADDRESSPROOF documentType is allowed to upload in this stage and mandatory to move forward from this stage.
CalculationType
Used by bpa-calculator Service which Defines the Fee to be collected for Given ApplicationType, ServiceType, RiskType and feeType
{ "applicationType": "BUILDING_PLAN_SCRUTINY", "serviceType": "ALL", "riskType": "LOW", "feeType": "SanctionFee", "amount": 500 }, { "applicationType": "BUILDING_PLAN_SCRUTINY", "serviceType": "NEW_CONSTRUCTION", "riskType": "ALL", "feeType": "ApplicationFee", "amount": 120 }, { "applicationType": "BUILDING_PLAN_SCRUTINY", "serviceType": "NEW_CONSTRUCTION", "riskType": "LOW", "feeType": "Low_ApplicationFee", "amount": 100 },
From the above example
indicates SanctionFee is Rs 500 for applicationType=BuildingPlanScrutiny, RiskType=LOW and any ServiceType
indicates applicationFee is Rs 120 for applicationType=BuildingPlanScrutiny, ServiceType=NEW_CONSTRUCTION and any RiskType
indicates applicationFee is Rs 100 for applicationType=BuildingPlanScrutiny, ServiceType=NEW_CONSTRUCTION and RiskType=LOW
RiskTypeComputation
Helps to Defines the RiskType of the Application based on the building Height and plotArea received from the EDCR System
{"fromPlotArea": 500, "toPlotArea": 9999999999, "fromBuildingHeight": 15, "toBuildingHeight":9999999999, "riskType": "HIGH", "note": "(Heigh 15 Mt or More) or ( Plot area >=800 sq.Mt)" }
CheckList
Used to Define the List of Questions and Documents to be attached on Field Inspection Pending Stage by Field Inspector.
The Example indicates
Four Questions with fieldType “YES/NO/NA“ ( Which indicates that field of type dropdown with Yes, NO and NA options) should be asked.
Readable question will be available in
2. Used to configure the conditions for Approval Stage
Condition checkboxes to be shown before approve which can be considered as Conditions for Approval
Field Inspection Questions & Documents { "applicationType": "BUILDING_PLAN_SCRUTINY", "ServiceType": "NEW_CONSTRUCTION", "RiskType": "LOW", "WFState": "FIELDINSPECTION_PENDING", "questions": [ { "question": "RIVER_EXISTS_ON_SITE", "fieldType": "YES/NO/NA", "active": true }, { "question": "TREE_EXISTS_ON_SITE", "fieldType": "YES/NO/NA", "active": true }, { "question": "PLAN_AS_PER_THE_SITE", "fieldType": "YES/NO/NA", "active": true }, { "question": "ROADWIDTH_AS_PER_THE_PLAN", "fieldType": "YES/NO/NA", "active": true } ], "docTypes": [ { "code": "FI.FIR", "required": true }, { "code": "FI.SINS", "required": true }, { "code": "FI.SISS", "required": true }, { "code": "FI.SIES", "required": true }, { "code": "FI.SIWS", "required": true } ] }
2. Conditions for Approval Stage { "applicationType": "BUILDING_PLAN_SCRUTINY", "ServiceType": "NEW_CONSTRUCTION", "RiskType": "HIGH", "WFState": "PENDINGAPPROVAL", "conditions": [ "The development shall be undertaken strictly according to plans enclosed with necessary permission endorsement.", "The land in question must be in lawful ownership and peaceful possession of the applicant.", "The permission is valid for period of X(this is the validity period in years) years with effect from the date of issue.", "Permission accorded under the provision cannot be construed as evidence in respect of right title interest of the plot over which the plan is approved.", "Any dispute arising out of land record or in respect of right/ title/ interest after this approval the plan shall be treated automatically cancelled during the period of dispute.", "Adequate safety precaution shall be provided at all stages of construction for safe guarding the life of workers and any public hazard.", "The land/ Building shall be used exclusively for the above occupancy for which you applied and the uses shall not be changed to any other use without prior approval of this Authority.", "Adequate space mentioned in the approved plan shall be kept open for parking and no part of it will be built upon.", "The land over which construction is proposed is accessible by an approved means of access with sufficient road width." ] }
NocTypeMapping
Mapping of the NOC Types applicable for BPA ApplicationType, ServiceType and riskType
From the Example
AIRPORT_AUTHORITY, NOC_FIRE NOC’s are applicable for applicationType → BULDING_PLAN_SCRUTINY
serviceType-> NEW_CONSTRUCTION
riskType-> ALL ( Any )
NocTypes-> list out the NOC Type object
and NOC Applications get created when BPA is created by the NOC’s Workflow would be initiated when the BPA application Status is equl to the nocTriggerState configured. ( According to this example, when the application status changes to Citizen Approval Pending, all the NOc’s workflow would be initiated)
{ "applicationType": "BUILDING_PLAN_SCRUTINY", "serviceType": "NEW_CONSTRUCTION", "riskType": "ALL", "nocTriggerState": "CITIZEN_APPROVAL_INPROCESS", "nocTypes": [ { "type": "AIRPORT_AUTHORITY", "required": true }, { "type": "FIRE_NOC", "required": false } ] }
PDF Name
Description
Config’s
BPA Permit Order
PDF Generated for the Permit Order on approval of the BPA HIGH and MEDIUM RISK Applications
BPA LOW Permit Order
PDF Generated for the Permit Order on approval of the BPA LOW RISK Applications
Revocation Letter
PDF of the Revocation Letter Generated when the LOW RISK BPA Application is Rejected
Occupancy Certificate
PDF Germinated for the Occupancy Certificate on Approval of the Occupancy Certificate Application
Property
Value
Remarks
egov.idgen.tl.applicationNum.format
PB-TL-[cy:yyyy-MM-dd]-[SEQ_EG_TL_APL]
The format of the TL application number
egov.idgen.tl.licensenumber.format
PB-TL-[cy:yyyy-MM-dd]-[SEQ_EG_PT_LN]
The format of the TL license number
egov.idgen.bpa.applicationNum.format
PB-SK-[cy:yyyy-MM-dd]-[SEQ_EG_TL_APL]
The format of the Stake holder application number
egov.idgen.bpa.licensenumber.format
PB-SK-[cy:yyyy-MM-dd]-[SEQ_EG_PT_LN]
The format of the Stake holder license number
egov.tl.max.limit
100
Max number of records to be returned
citizen.allowed.search.params
tenantId, applicationNumber, limit, offset, licenseNumbers
The search parameters on which citizen can search
employee.allowed.search.params
tenantId, applicationNumber, applicationType, status, mobileNumber, fromDate, toDate, licenseNumbers, oldLicenseNumber, limit, offset
The search parameters on which employee can search
persister.save.tradelicense.topic
save-tl-tradelicense
The name of kafka topic on which create request is published
persister.update.tradelicense.topic
update-tl-tradelicense
The name of kafka topic on which update request is published
persister.update.tradelicense.workflow.topic
update-tl-workflow
The name of kafka topic on which update request is published
Title
Link
Local Setup
API Swagger Documentation (Trade License)
Link
{servicename}/_create, _create
This API is used to create an application for the license in the system. Whenever an application is created an application number is generated and assigned to the application for future reference.
{servicename}/_search, /_search
This API is used to search the applications in the system based on various search parameters like mobile number, the application number, status etc.
{servicename}/_update, _update
The _update API is used to update the application information or to forward the application from one state to another.
In the case of the stakeholder registration if the application reaches the last stage the role depending on the license type is given to the user.
{servicename}/{jobname}/_batch, /_batch
Searches trade licenses which are expiring and send a reminder SMS to owner's of the licenses
Doc Links
Description
Doc Links
Description
Feature
Description
PGR v2 (UI/UX/API revamp and Workflow integration)
Citizen
Create a Complaint
My Complaints and View Complaints
Rating and Reopening of the Complaint
CSR
Create a Complaint
View Complaints
Reopen Complaints
Inbox
Grievance Routing Officer
View Complaints
Assign Complaints
Reject Complaints
Inbox
Last Mile Employee
View Complaints
Assign Complaints
ReAssign Complaints
Inbox
Water and Sewerage
Public domain search for Water and Sewerage
Open payment for Water and Sewerage
Collection
Search Receipt
Receipt cancellation and its impact
HRMS
Deactivate and activate employee
Updated Feature
Description
Property Tax
Payment Notification
Payment Failure Scenario for Open payment
Capturing data for better reporting and analysis
Show the status of the receipt if the receipt is cancelled
Mutation - Allow Guardian name to change
Mutation - Multiple owners to single owner change and vice versa
Tenant and date range wise re-indexing Utility
Water and Sewerage Enhancements
Property Workflow Config Changes for Water and Sewerage
Collection Enhancements
Tenant and date range wise re-indexing Utility
Zero payment changes
HRMS Enhancements
Employee Create and Search Enhancements
Other minor enhancements and validations
UI and backend Enhancements
Pagination on process instance search API
Pagination in Employee Inbox
Addition of spinners in all the UI screens
DSS improvements to enable/disable module configs in MDMS and table headings Localization
PGR migration from v1 to v2 including the workflow data and reindexing
DSS config changes to support PGR v2
SENDBACKTOCITIZEN send’s application back to the user’s with a registered Mobile Number
Non-functional enhancements
Config Repo baselining (Indexer and Persister configs sem version and baselining)
Improvement in Loading localization data in UI - module wise localization caching
eDCR Enhancements
Road Reserve area captured
Height of Room - The colour codes are used to identify the type of room
Vehicle Ramp captured and slope auto calculated
Floor Unit - Colour codes used to differentiate the different type of dwelling unit
Key Feature
Description
Revamped UI and UX for all stakeholders
Key features of the new UI -
Well defined call to actions
Mobile-first approach
In-app help and messaging
Searchable dropdowns, pincode mapping with ULB and locality.
Complaint search filters on the employee side for efficient ops
API redesign and workflow integration
API redesign to cater to new UX (details will be added by tech team). Workflow service has been integrated with PGR and the simple flow has been configured. Now, administrators can easily customize PGR complaint resolution flow in the system.
PGR migration from v1 to v2 including the workflow data and reindexing
All the data has been migrated and indexed in V2 so that it can easily be viewed and analysed in the DSS.
DSS config changes to support PGR v2
It will be added by the tech team in tech documentation.
Doc Links
Description
Themes | Objectives |
Theme 1: Standardize and simplify for ease of use | Standardize software support processes, knowledge repositories; Improve tools to support automation |
Theme 2: Deliver value to States | Deliver product backlog, completion of DIGIT products and decision support systems |
Theme 3: Increase ease of use and ease of access to citizens | Create integrated user experience with a key focus on flexibility, accessibility, quality of service; Optimized user experience |
Theme 4: Enhance data privacy and security | Update and enhance data privacy parameters on DIGIT across reports, modules, and dashboards |
Theme 5: New product innovation | Identify high-impact product innovation areas through validation, understanding the domain, and processes involved |
Release Date: 01/06/2020 | Beta date: | GA date: |
Release Date: 01/06/2020 | Beta date: | GA date: |
Title | Description |
tenantId | Serves as a Key |
moduleName | Name of the module to which the master data belongs |
MasterName | The Master Name will be substituted by the actual name of the master data. The array succeeding it will contain the actual data. |
Title | Link |
Reference Doc Link 1 | MDMS-Service |
Reference Doc Link 2 | MDMS-Rewritten |
SSL is Secure Sockets Layer is an encryption-based network security protocol developed for the assurance of privacy, authenticity and data integrity in internet communications.
Ideally, the domain name configuration and the SSL certification are obtained consecutively without fail from the state’s IT team.
No data is needed from the state team for this.
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Not Applicable
ULB level setup involves the configuration of ULB specific data parameters such as ULB boundaries, ULB bank accounts, and hierarchy details.
The Trade License application, developed on the eGov-DIGIT platform, makes the process of obtaining a Trade License easy, smooth, and transparent. The module, hence, removes the need for manual processing and streamlines the key trade license management functions to provide a better user experience.
DIGIT Trade License module enables citizens to -
Apply for new trade license or renew an existing trade license.
Upload all the relevant documents required for the license.
Make payment for the Trade License (New/Renewal) fee using the online payment gateway.
Receive notifications and alerts by emails or SMS for new application status updates and pending renewals.
Download Trade License, Payment & Acknowledgement Receipts online.
DIGIT Trade License module enables employees to -
Create flexible role-based workflows.
Configure license fees calculation logic.
View custom dashboards for module statistics.
Filter search results using advanced configurable search parameters.
Receipt Register
Application Status
Cancelled Receipt Register
ULBwise Collection Report
ULBwise Application Status
Key Feature
Description
Re-activate employee
Once an employee is de-activated the ULB admin can re-activate the employee in the system. It will automatically map the roles and responsibilities assigned earlier to the employee. UI provides the input field to capture the reason for re-activation and the supporting information for the same.
Employee search
Standardized input validations for all the employee information fields. The dropdowns are turned to 'searchable dropdown' for better UX. Employee search parameters and the results are standardized as per DIGIT standards.
Key Feature
Description
Payment Notification
The enhancement defines the notification content and triggers the notification to different stakeholders.
Payment Failure Scenario - Open payment
For open payments, the property owners will not receive any notification in the event of a payment failure. Only the payer will receive the notification. The feature details out the scenario and content of the notification.
Capturing data for better reporting and analysis
This is backend enhancement concerning the transactional data. The system offers the scope to generate reports on various transactional data such as type, device, task creator information, legacy entry, etc. This enables users to track product usage and understand the adoption patterns of the product.
PT:: Show the status of the receipt if the receipt is cancelled
In case the receipt is cancelled, the system displays the receipt status in red to avoid any confusion to the users.
Search receipt
Enhance user access control for the search API. Search data access is now restricted to the user-specific role. Earlier, a user had search access to search application, receipt, etc. for all products.
Cancel receipt
Employees can cancel the receipts at the counter in case of any discrepancy in the receipt. This feature aims to improve the service delivery of the ULBs. Employees will be able to capture the reason for cancelling the receipt and add penalties to the bills, if applicable.
Transfer of ownership - All use cases
This enhancement covers all the combinations and possible values in the transferee details. Now, the user can change a single owner to multiple owners or private owner to institutional and so on. The user story covers all the corner cases in the mutation process.
Zero payment changes
This enhancement in the billing service will solve the reporting problem in case of consolidated bill generation by excluding the demands that are already consumed.
Link |
API Contract Reference |
Title | Link |
Sample Master file |
Sample Master configuration |
Title | Link |
State Level Common-Master Data |
State Level Module Specific Common-Master Data |
ULB Specific Data |
Link |
API Contract Reference |
Title | Link |
tenant json file |
content |
Title | Link |
Sample Master config file |
Sample Module folder |
Whenever an android mobile App is developed it has to be published on the Google play store in order to let the users avail its service. This page provides information about configuring the google play store account to make DIGIT mobile apps available for easy download.
In order to start the configuration for the google play store following would be required:
Data given in the table is sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Ask the state team/client to create an email account on Gmail.
Ask the client to log in to the google play console here and make the required payment so that further tasks could be processed.
Ask the client to share the email id and password in the template.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
An Urban Local Body (ULB) is defined as a tenant. The information which describes the various attributes of a ULB is known as tenant information. This detail is required to add the ULB into the system.
Data given in the table is a sample data.
Download the data template attached to this page.
Have it open and go through all the headers and understand the meaning as given in this document under section 'Data Definition'.
Make sure all the headers, its data type, field size and its definition/ description are understood properly.
In case of any doubt, please reach out to the person who has shared this document with you and discuss the same to clear out the doubts.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until the entire data is filled into a template.
Verify the data once again by going through the checklist by taking care of each and every point mentioned in the checklist.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
To see common checklist refer to the page Checklist consisting of all the activities which are to be followed to ensure completeness and quality of data.
This checklist covers the activities which are specific to the entity. There are no checklist activities exists which are specific to the entity.
The departments are defined as different sections within the ULB based on which the functions performed by ULBs and employees in ULB are grouped. The budgets details of the ULBs are also defined by the department. It is suggested that the ULB across the state adopt the same department naming terminology. This document will help you in filling the department detail in the template provided.
Data given in the table is a sample data.
Download the data template attached to this page.
Have it open and go through all the headers and understand the meaning given in this document under section 'Data Definition'.
Make sure all the headers, its data type, field size and its definition/ description are understood properly.
In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
Identify all the departments in ULB well before start filling then into the template.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until the entire data is filled into a template.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.
The checklist is a set of activities to be performed after the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
To see the common checklist refer to the Checklist page consisting of all the activities which are to be followed to ensure complete and quality data.
This checklist covers the activities which are specific to the entity. There is no entity-specific checklist is applicable for this entity.
An email account of the client/state team has to be set up in order to receive/send the email notifications.
In order to achieve the functionality, an email account has to be set up at there server since most of the states would defer from creating an account with the Gmail/public server. Further, this email account has to be integrated with the various DIGIT modules.
In order to achieve the above functionality, we require the below-mentioned details
The values mentioned here are sample data.
Below steps could be followed in order to fill the template:
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Ask the state to gather all the data related to the technical configuration from the email server settings.
Get the attached template filled from the state and a sample data is provided in the data table section for reference.
The data would be available in the POP and IMAP account settings at the server level.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
Not Applicable
Localization is a practice to localize various UI visible data into the local wordings according to the client's requirements. This practice of localization is enforced to various clients so that it becomes easier for the people using the service to understand the common terminology and make the best use of the available system.
The following texts (but not limited to) on the web page can be localized:
Labels
Messages: Alert messages, success messages, validation messages and other notifications etc.
Help Texts
The module-specific master data would already have been made available in the localized form while collecting the data for the respective module-specific configuration.
Data mentioned in the data table is a sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Present the client the full sheet of codes as well as the English language for which the localized texts are required.
Ask the client to fill the localized text in the last column which is the message(local language) column.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
This checklist covers all the activities which are common across the entities.
Not Applicable
A ULB is divided into certain categories of boundaries by ULB administrative authorities in order to carry out ULB’s functions better. A ULB/City could be divided by a different set of delimitation of boundaries based on functions as given below.
Revenue - Delimitation of ULB into boundaries to perform the target setting and collection of revenue.
Administration - Delimitation of ULB into boundaries for the better administration of ULB.
Locality/ Location - Delimitation of ULB into boundaries based on the places known to citizen with names and easily identifiable by the common person.
All these authorities have designated certain levels of boundary classification for a certain ULB.
The below mention table is used to collect data for the types of hierarchy being followed:
The above-mentioned data for the boundary hierarchy is sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify all the types of boundaries which are being used in the state in order to carry out various administrative/revenue functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until the entire data is filled into a template.
Then fill up the hierarchy types and the codes in the respective columns in the template.
Code should be created for the type of boundary being classified.
A brief description of the boundary hierarchy type would be helpful.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
A designation is an act of pointing someone out with a name, a title or an assignment. For example, someone being named president of an organization. This document is to help to gather various designations data which are generally used in ULBs.
Data given in the table is a sample data.
Download the data template attached to this page.
Have it open and go through all the headers and understand the meaning given in this document under section 'Data Definition'.
Make sure all the headers, its data type, field size and its definition/ description are understood properly.
In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
Identify all the designations exists in the ULB, refer to governments gazette to define the designations in ULBs.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until the entire data is filled into a template.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.
The checklist is a set of activities to be performed after the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
To see the common checklist refer to the Checklist page consisting of all the activities which are to be followed to ensure complete and quality data.
This checklist covers the activities which are specific to the entity. There is no entity-specific checklist is applicable for this entity.
The SMS service is a way of communicating necessary information/updates to the users on their various transactions on DIGIT applications.
In order to update the users, there are certain notification parameters that are system configured for various steps in the application process. These configurations can be changed/reconfigured based upon the ULB requirements.
We have the below-mentioned parameters which we use for configuration:
The data given in the above table is sample data. The parameters and its values are SMS service provided specific and may vary accordingly.
For the SMS service to be integrated there are various things for which the vendor more or less guides us for the steps to be followed but below mentioned are a few basic steps and the generic data definitions which could be followed.
Below mentioned are the descriptions of the parameters which are needed for configuration:
Parameter names could differ from vendor to vendor.
Since the SMS service is a vendor delivered service for which the below steps would have to be followed:
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
The SMS vendor has to provide the data in the data template attached.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
At times in the different modules, there is a need to capture the address of the user’s place of residence or where the person is doing a trade, for which the user has to enter his/her full address which creates a task. In order to simplify the process, we can have google map geolocation service in place which would help us get the exact coordinates of the place on the map and help us identify the place.
This service is paid and the client has to purchase the below items:
Google Map API's
https://developers.google.com/maps/documentation/javascript/get-api-key "Maps Javascript API", "Places API" and "Geolocation API" are needed and first 200$ usages are free, once it exceeds, the price per 1000 requests as given below.
Maps JavaScript API (web-client) Return the location and accuracy radius of a device, based on Wi-Fi or cell towers. $5
Geolocation API Return the location and accuracy radius of a device, based on Wi-Fi or cell towers. $5
Places API for Web (web-server) Turn a phone number, address, or name into a place, and provide its name and address. $17
Note:
The data provided is sample data
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Ask the clients to purchase the above-mentioned APIs in the Introduction section.
Get the details for the API URL and key from the client.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
Not Applicable
The domain name is the address through which the internet users can access the website rather than entering the whole IP address in the search bar of the browser.
This domain name is ideally chosen by the state/client since its a product which has to be used for/by them.
Following is the table through which the information can be shared.
Data given in the table is a sample data.
Since all state governments/clients prefer to host the websites on their servers, this activity is ideally done by them.
Following are the steps which are to be followed:
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
If the state agrees to host the website on their server, provide them with the 2 columns mentioned in the attached template.
If the state disagrees to host on their server, then a domain name has to be purchased by any of the external vendors and the EXTERNAL-IP address has to be mapped with them.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity:
Master data templates allow users to configure the key parameters and details required for the effective functioning of the modules. This section offers comprehensive information on how to configure the master data templates for each module.
The Trade Category List can be defined as the primary or the 1st level classification “head” for trade(s) defined at a ULB/State Level.
The table above contains sample Trade Category data.
Download the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.
Enter a unique Trade Category Code for each trade head.
Enter the Trade Category Name. Some trade categories are already defined in the master. Add new categories as required.
Enter the Trade Category Name (Local Language).
The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
This is the 3rd step that comes after the boundary data collection. Cross hierarchy mapping happens in case a child has a relationship with more than 2 parents. This double relationship between the child and parents could happen between different hierarchies as well.
For example: In Admin level boundary hierarchy a mohalla M1(child) could be a part of 2 Wards(parent) W1 and W2. In such a case a single Mohalla(child) has to be mapped to 2 Wards(parent).
Below is the data table for the Boundary:
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Firstly Identify all the child levels which have a relation with more than 2 parent boundary types and their hierarchy types as well.
Fill up the boundary hierarchy (names/ codes) types in place of boundary type 1/2.
Then along with the codes start filling in one by one with the proper mapping between every child and parent.
The Sr. No should be in an incremental order for every new child level.
Prepare a new table for every different parent-child relation.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity. There is no entity-specific checklist activity applicable here.
User Story - RAIN-1904: Employee search EnhancementsQA SIGNOFF
User story - RAIN-1137: Payment NotificationQA SIGNOFF
User story -RAIN-1756: Search ReceiptQA SIGNOFF
User story - RAIN-1757: Cancel ReceiptQA SIGNOFF
User Story - RAIN-1820: PT Mutation - Allow the following changes in the mutation application QA SIGNOFF
User story - RAIN-1893: Backend: Zero payment changesQA SIGNOFF
Sr. No
Email Id
Password
1.
*******
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Email Id
Alphanumeric
NA
Yes
Gmail account id through which the app would be published on the google play store
2
Password
Alphanumeric
NA
Yes
Password for the Gmail account
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
Make sure that the email account is created on Gmail since the play store works on Google accounts only
-
2
Email Id and Password is required in order to login to the google play store for configuration
-
S. No.
ULB Name*
ULB Code*
ULB Grade*
City Name*
City Local Name
District Name*
District Code*
Region Name
Region Code
1
Sonepur Nagar Panchayat
47
Corp
Sonepur
Sonepur
Banka
BN47
Bihar
BBD47
Contact Number*
Address*
ULB Website*
Latitude
Longitude
Email Address
GIS Location Link
Call Center No.
Facebook Link
Twitter Link
Logo file Path*
98362532657
Main Hall, Sonepur
24.8874° N
86.9198° E
snp@bihar.gov.in
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
ULB Name
Text
256
Yes
Name of ULB. E.g. Kannur Municipal Corporation/ Saptarishi Municipal Council
2
ULB Code
Alphanumeric
64
Yes
It is a unique identifier which is assigned to each ULB. LGD (Local Government Directory) has already assigned a code urban local bodies and the same is used here
3
ULB Grade
Alphanumeric
64
Yes
Grade of ULB. e.g. Corporation, Municipality, Nagar Panchayat etc
4
City Name
Text
256
Yes
Name of city/ town which is covered by the ULB. E.g. Kannur/ Saptarishi
5
City Local Name
Text
256
No
Name of the city in the local language. e.g Telugu, Hindi etc
6
District Name
Text
256
Yes
Name of the District where the city is situated
7
District Code
Alphanumeric
64
Yes
It is a unique identifier which is assigned to each district. LGD (Local Government Directory) has already assigned code districts and the same is used here
8
Region Name
Text
256
No
Name of the region the listed district belongs to
9
Region Code
Alphanumeric
64
No
Unique code of the region to uniquely identify it
10
Contact Number
Alphanumeric
10
Yes
Contact person phone no. of ULB
11
Address
Text
256
Yes
Postal address of the ULB for the correspondence
12
ULB Website
Alphanumeric
256
Yes
URL address of the website for the ULB
13
Email Address
Alphanumeric
64
No
Email of the address of ULB where the email from the citizen can be received
14
Latitude
Alphanumeric
64
No
Latitude part of coordinates of the centroid of the city
15
Longitude
Alphanumeric
64
No
Longitude part of coordinates of the centroid of the city
16
GIS Location Link
Text
NA
No
GIS Location link of the ULB
17
Call Center No
Alphanumeric
10
No
Call centre contact number of ULB
18
Facebook Link
Text
NA
No
Face book page link of ULB
19
Twitter Link
Text
NA
No
Twitter page link of the ULB
20
Logo file Path
Document
NA
Yes
URL of logo file path to download the logo of ULB
Sr. No.
Department Code*
Department name (In English)*
Department Name (In Local Language)*
1
ACC
Accounts
लेखा
2
PHS
Public Health And Sanitation
सार्वजनिक स्वास्थ्य और स्वच्छता
3
REV
Revenue
राजस्व
4
TP
Town Planning
नगर नियोजन
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Department Code*
Alphanumeric
64
Yes
Unique code for the department to identify a department
2
Department Name ( In English)*
Text
256
Yes
The name of the department in the ULB in English
3
Department Name (In Local Language)*
Text
256
Yes
The name of the department working in the ULB in local language e.g. Telugu, Hindi etc. whichever is applicable
Sr. No.
Email ID
Your Name
Account Type
Incoming Mail Server
Outgoing Mail Server (SMTP)
Password
Incoming Server POP3 Port
Outgoing server SMTP Port
Encrypted Connection Type
Days after which the email should be removed from the server
1
Bihar
POP3
SMTP
SMTP
****
192.172.82.12
192.172.82.12
Auto
14
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Email ID
Alphanumeric
N/A
Yes
Email id which is being configured
2
Your Name
Text
256
Yes
The name on behalf of which the email would be sent in order to receive the updates
3
Account Type
Alphanumeric
64
Yes
The type of email account type protocol which will be used to download messages
4
Incoming Mail Server
Numeric
(12,2)
Yes
The IP address of the email server through which messages would be received
5
Outgoing Mail Server(SMTP)
Numeric
(12,2)
Yes
The IP address of the email server through which messages would be sent
6
Password
Alphanumeric
64
Yes
The password of the email server
7
Incoming Server POP3 Port
Numeric
(12,2)
Yes
The port number through which the emails are received
8
Outgoing server SMTP Port
Numeric
(12,2)
Yes
The port number through which the emails are to be sent
9
Encrypted Connection Type
Alphanumeric
64
Yes
The encryption type which is used for the connection
10
Days after which the email should be removed from the server
Numeric
(12,2)
Yes
The number of days after which the email should be deleted from the server (not from the local device)
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Code*
Module*
Message (In English)*
Message (In Local Language)*
1
ACTION_TEXT_APPLICATION
Trade License
Search Trade Licenses
व्यापार लाइसेंस खोजें
2
ACTION_TEST_TL_REPORTS
Trade License
Trade License Reports
ट्रेड लाइसेंस रिपोर्ट
3
CORE_COMMON_CITY
Property Tax
City
शहर
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Code
Alphanumeric
64
Yes
The code for which the localized language is to be provided
2
Module
Alphanumeric
64
Yes
The module in which the code belongs to
3
Message(In English)
Text
256
Yes
The English language that is being displayed on the UI
4
Message(In Local Language)
Text
256
Yes
The text in the local language that the client wants to be displayed
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Code*
Boundary Hierarchy Type*
Description
1
ADM
Administration
Administration level boundary classified on the basis of administrative functions such as scrutinize certain rules and regulations
2
REV
Revenue
Revenue-based classification of a ULB is done on the basis of revenue collection
3
LOC
Locality
Location-based classification could be done in order to identify a certain place. For example, Locality of a house of a citizen could follow the below hierarchy:
House no.
Mohalla
Area
Ward
City
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Code
Alphabet
64
Yes
Code is used to identify a certain classification of the type of boundary hierarchy
2
Boundary Hierarchy Type
Alphanumeric
256
Yes
The meaningful name to define one group of boundaries defined to perform one function
3
Description
Alphanumeric
256
Yes
A brief description of the boundary hierarchy
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
Make sure that the hierarchies types should be uniform across all the ULB’s /cities in the state
-
2
Only 3 types of boundary hierarchies are allowed
-
Sr. No.
Designation Code*
Designation Name* (In English )
Designation Name* (In Local Language)
1
ACT
Accountant
अकाउंटेंट
2
AO
Accounts Officer
लेखा अधिकारी
3
AC
Additional Commissioner
अपर आयुक्त
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Designation Code
Alphanumeric
64
Yes
Unique Identifier for designation which is used as a reference for child configuration mapping
2
Designation Name (In English)
Text
256
Yes
Designation name in English
3
Designation Name (In Local Language)
Text
256
Yes
Designation Name in the local language. e.g. Hindi, Telugu etc. whichever is applicable
Sr. No.
Parameter
Value
1
sms.provider.url
www.xyz.com
2
sms.username.parameter
mnsbihar@001
3
sms.username.value
***
Sr. No.
Column Name
Data Type
Data Size
Mandatory
Description
1
Parameter
Alphanumeric
64
Yes
The parameter required to be configured
2
Value
Alphanumeric
64
Yes
The corresponding value of the parameter
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of.
Sr. No.
Checklist Parameter
Example
1
Make sure that the vendor should support multiple language functionality and especially the local language of the state.
-
Sr. No
Google API URL*
API Key*
1458-ASD785-987722
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
Google API URL
Alphanumeric
64
Yes
The URL of the API that is being purchased
2.
API Key
Alphanumeric
64
Yes
The key which the google would provide after the purchase for the API has been done
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Domain Name
EXTERNAL-IP
192.78.98.12
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
Domain Name
Alphanumeric
253
Yes
The name/address of the website being used to access the website/ module
EXTERNAL-IP
Alphanumeric
32
Yes
It is the IP address that has to be mapped to the domain name
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of.
Sr. No.
Checklist Parameter
Example
No mistake should be done in providing the EXTERNAL-IP address
-
2.
Only one domain name and its corresponding IP address have to be provided
-
Sr.No.
Trade Category Code*
Trade Category Name* (In English)
Trade Category Name* (In Local Language)
1
TC1
Goods
सामग्री
2
TC2
Services
सर्विस
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Trade Category Code
Alphameric
64
Yes
The Code assigned to the Trade Category. Eg: TC1 For Goods, TC2 for Services
2
Trade Category Name (In English)
Text
256
Yes
Name of the Trade Category in English. Eg: Goods, Services etc.
3
Trade Category Name (In Local Language)
Text
256
Yes
Name of the Trade Category in Local Language (as decided). Eg: Service is described as “सर्विस” in Hindi
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
The format of the Trade Category Code defined should be alphanumeric and unique
TC1: Goods
TC2: Services
2
Trade Category Name (In either Language) should not contain any special characters
Goods: [Allowed]
#Goods! : [Not allowed]
Hierarchy Type
Hierarchy Type 1*
Hierarchy Type 2*
Sr.No
Boundary Type*
Boundary Code*
Boundary Type*
Boundary Code*
1
Ward
W1
Mohalla
M1
Ward
W2
Mohalla
M1
2
Ward
W3
Mohalla
M2
Ward
W4
Mohalla
M2
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Hierarchy Type 1
Text
256
Yes
The type of hierarchy 1 the boundary belongs to which is to be mapped with other boundaries in hierarchy 2. Refer Boundary Hierarchies
2
Hierarchy Type 2
Text
256
Yes
The type of hierarchy 2 the boundary belongs to which is to be mapped with other boundaries in hierarchy 1. Refer Boundary Hierarchies
3
Boundary Type
Text
64
Yes
This is the type of boundary from hierarchy 1. Refer Boundary Data
4
Boundary Code
Alphanumeric
64
Yes
This is the code of the boundary for the boundary from hierarchy 1. Refer Boundary Data
5
Boundary Type
Text
64
Yes
This is the type of boundary from hierarchy 2. Refer Boundary Data
6
Boundary Code
Alphanumeric
64
Yes
This is the code of the boundary for the boundary from hierarchy 2. Refer Boundary Data
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
This section illustrates the steps for different employee user roles at the ULB level
Complaints can also be registered by ULB counter employees on behalf of the citizen.
The CSR or counter employees can perform the following actions on PGR -
To file complaints on behalf of the citizen navigate to the Home page and click on the Complaints card. Else, click on the Complaints menu option in the sidebar. Click on the File Complaint tab on the screen. This will open the complaint form page.
Enter the Citizen Name. and the Citizen Mobile No. Select the relevant Complaint Type and the subtype from the drop-down list of options. Refer to the list of complaint types available in PGR. Enter any additional information in the Complaint Additional Details field. The City field will display the city specified in your profile by default. You can change the city if required. Choose the applicable Locality/Mohalla from the drop-down list. Enter the House No. and Street Name. Enter any Landmark to identify the exact location for the listed complaint.
Click on File Complaint button once you have finished filling in all the details. The system will display the Complaint Registered Successfully message along with the Complaint No.
Click on the Continue button. Your complaint details are available on the dashboard. Click on the complaint to view the complaint details.
Employees can search for specific complaints using the registered mobile number of citizens or by entering the last few digits of the complaint number.
To search complaints navigate to Complaints Home page. Enter Citizen Mobile No. Or, enter the last 6 digits of the Complaint No.
Click on the Search button. The system will retrieve and display the matching records. Click on the Clear Search button to initiate a fresh search.
To reopen the complaints navigate to Complaints > My Complaints menu option in the sidebar. Click on the closed complaint that you want to reopen. Scroll down to the Complaint Timeline section. Click on the Re-Open button on the timeline.
The Re-Open button will be available only for 5 days after the complaint is resolved and closed by the department employee. The number of days can vary depending on the State or ULBs. The citizen or CSR will not be able to reopen complaints once this period is over.
Select the appropriate reason for reopening the complaint. Click on the camera icon to upload any photos related to the complaint. Enter any additional information in the Comments section. Click on the Continue button once done.
The system displays an acknowledgement message stating the complaint is reopened. Click on the Go To Home button to navigate back to the home page.
The Grievance Routing Officer or GRO manages the complaints queue. The role ensures the complaints are routed to the appropriate employees for prompt action.
GROs can
Call citizens
Comment on complaints
Grievances filed by citizens are assigned to specific employees who are responsible for acting on and resolving the complaints.
To assign complaints, navigate to the Home page and click on the Complaints card. Or, navigate to Complaints > Open Complaints. The GRO Complaint page contains two tabs - Unassigned and Assigned complaints.
Click on the Unassigned tab. The list of unassigned complaints is available on the screen. Click on the Complaint you want to assign. This will open the Complaint Summary page.
Click on the Assign button available in the bottom right corner of the screen. This will display the list of employees. Select an employee.
Click on the Assign button.
The complaint is assigned to the selected employee.
Assigned complaints can be re-assigned by the GRO depending on the situation and requirements.
To re-assign complaints navigate to the Home page and click on the Complaints card. Click on the Assigned tab. Click on the complaint you want to re-assign. Click on the Re-Assign button available on the bottom right corner of the screen. Select the employee to whom the complaint should be assigned. Click on the Assign button.
The Complaint is re-assigned to the selected employee.
GROs can share complaints with other department users based on the requirements.
To share complaints click on the complaint you want to share.
Click on the share icon in blue on the top right corner of the screen.
Select the appropriate channel. The system will redirect you to the selected channel interface. Select the person or list of people for sharing. Click on the Send button.
The complaint is shared with the selected recipients.
In certain cases, the GRO might reject registered complaints. This usually happens when the complaint is beyond the operational scope of the department or the complaint is invalid.
To reject complaints navigate to the Home page and click on the Complaints card. Click on the relevant Complaint. This will open the Complaint Summary page. Click on the Reject button available in the bottom right corner of the screen. Select the appropriate Reason to Reject.
Add any additional information in the Comments space. Click on the Submit button. The complaint is rejected.
First Mile Employees or FMEs are responsible for acting on citizen complaints.
FMEs can -
Call citizens
Comment on complaints
FMEs work on the assigned complaints. In some cases, the FMEs may request complaints to be reassigned to some other employee.
To request reassign navigate to the Complaints menu option in the sidebar. Click on Open Complaints. Search for a specific complaint using the Citizen Mobile No. or inputting the last 6 digits of the Complaint No.
Else, click on the relevant complaint from the list of open complaints. Click on the Request Re-Assign button available in the bottom right corner of the screen.
Select a specific reason for requesting a re-assign.
Enter any additional information in the Comments section. Click on the Request Re-Assign button.
Once the complaints are actioned on the FME marks the issue resolved. The complaint is closed subsequently.
To mark the complaint resolved, navigate to the Complaints menu option in the sidebar. Click on Open Complaints. Search for a specific complaint using the Citizen Mobile No. or inputting the last 6 digits of the Complaint No.
Else, click on the relevant complaint from the list of open complaints. **Click on the Mark Resolved** button available in the bottom right corner of the screen.
Click on the camera icon to upload photos as evidence that the issue has been resolved.
Enter any additional information related to the issue resolution in the Comments section. Click on the Mark Resolved button.
The system will display an acknowledgement message. Click on the Go To Home button to navigate back to the home page.
The objective of PDF generation service is to bulk generate pdf as per requirement.
Before you proceed with the documentation, make sure the following pre-requisites are met -
Install npm.
Kafka server is up and running.
egov-persister service is running and has pdf generation persister config path added in it.
PSQL server is running and the database is created to store filestore id and job id of generated pdf.
Provide a common framework to generate PDF.
Provide flexibility to customise the PDF as per the requirement.
Provide functionality to add an image, Qr Code in PDF.
Provide functionality to generate pdf in bulk.
Provide functionality to specify a maximum number of records to be written in one PDF.
Mustache.js: (https://github.com/janl/mustache.js/ ):- as templating engine to populate format as defined in format config, from request json based on mappings defined in data config
Create data config and format config for a PDF according to product requirement.
Add data config and format config files in PDF configuration
Add the file path of data and format config in the environment yml file
Deploy the latest version of pdf-service in a particular environment.
For Configuration details please refer to Customizing PDF Receipts & Certificates.
The PDF configuration can be used by any module which needs to show particular information in PDF format that can be print/downloaded by the user.
Functionality to generate PDFs in bulk.
Avoid regeneration.
Support QR codes and Images.
Functionality to specify the maximum number of records to be written in one PDF.
Uploading generated PDF to filestore and return filestore id for easy access.
To download and print the required PDF _create API has to be called with the required key (For Integration with UI, please refer to the links in Reference Docs)
(Note: All the API’s are in the same postman collection, therefore, the same link is added in each row)
User service is responsible for user data management and providing functionality to login and logout into Digit system
Before you proceed with the configuration, make sure the following pre-requisites are met -
Java 8
Kafka server is up and running
Encryption and MDMS services are running
PSQL server is running and database
Redis is running
Store, update and search user data
Provide authentication
Provide login, logout functionality into DIGIT platform
Store user data PIIs in encrypted form
Setup latest version of egov-enc-service and egov-mdms- service
Deploy the latest version of egov-user service
Add Role-Action mapping for API’s
Following application properties file in user service are configurable.
User data management and functionality to login and logout into Digit system using OTP and password.
Providing following functionality to citizen and employee type users
Employee:
User registration
Search user
Update user details
Forgot password
Change password
User role mapping(Single ULB to multiple roles)
Enable employee to login into DIGIT system based on a password.
Citizen:
Create user
Update user
Search user
User registration using OTP
OTP based login
To integrate, host of egov-user should be overwritten in the helm chart.
Use /citizen/_create and /users/_createnovalidate endpoints for creating users into the system
Use /v1/_search and /_search endpoints to search users in the system depending on various search parameters
Use /profile/_update for partial update and /users/_updatenovalidate for update
Use /password/nologin/_update for otp based password reset and /password/_update for logged in user password reset
Use /user/oauth/token for generating token, /_logoutfor logout and /_details for getting user information from his token
A complete guide to using mCollect module
The mCollect module is designed to facilitate the ULBs process miscellaneous types of payments. Miscellaneous payments may include parking fees, advertising fees, rent, challans, etc. The module objective is to process and record payment collections on account of miscellaneous heads within the ULBs. This makes it easy to track payment receipts and generate reports for administrative purposes.
The MCS module enables ULB employees to -
Capture payment details
Generate and print payment collection receipts
Access dashboard analytics
Generate reports for administration
Refer to the table below to understand the different user roles and the scope of action linked to each role. The applicable user roles and action items can vary from one State to another. DIGIT customizes the workflows to suit the requirements defined at the State level.
This section guides you through the details of using the MCS module for the defined roles. Click on the relevant role below to learn more about how to use the MCS system.
A core application which provides location details of the tenant for which the services are being provided.
Before you proceed with the documentation, make sure the following pre-requisites are met -
Java 8
PSQL server is running and database is created
Knowledge of egov-mdms service
egov-mdms service is running and all the required mdms master are loaded in it
The location information is also known as boundary data of ULB
Boundary data can be of different hierarchies ADMIN, ELECTION hierarchy which is defined by the Administrators, Revenue hierarchy defined by the Revenue department.
The election hierarchy has the locations divided into several types like zone, election ward, block, street and locality. The Revenue hierarchy has the locations divided into a zone, ward, block and locality.
The model which defines the localities like zone, ward and etc is boundary object which contains information like name, lat, long, parent or children boundary if any. The boundaries come under each other in a hierarchy like a zone contains wards, ward contains blocks, a block contains locality. The order in which the boundaries are contained in each other will differ based on the tenants.
Add/Update the mdms master file which contain boundary data of ULB’s.
Add Role-Action mapping for egov-location API’s.
Deploy/Redeploy the latest version of egov-mdms service.
Fill the above environment variables in egov-location with proper values.
Deploy the latest version of egov-location service.
The boundary data has been moved to mdms from the master tables in DB. The location service fetches the JSON from mdms and parses it to the structure of boundary object as mentioned above. A sample master would look like below.
The egov-location API’s can be used by any module which needs to store the location details of the tenant.
Get the boundary details based on boundary type and hierarchy type within the tenant boundary structure.
Get the geographical boundaries by providing appropriate GeoJson.
Get the tenant list in the given latitude and longitude.
To integrate, host of egov-location should be overwritten in helm chart.
/boundarys/_search should be added as the search endpoint for searching boundary details based on tenant Id, Boundary Type, Hierarchy Type etc.
/geography/_search should be added as the search endpoint .This method handles all requests related to geographical boundaries by providing appropriate GeoJson and other associated data based on tenantId or lat/long etc.
/tenant/_search should be added as the search endpoint. This method tries to resolve a given lat, long to a corresponding tenant, provided there exists a mapping between the reverse geocoded city to tenant.
The MDMS Tenant boundary master file should be loaded in MDMS service.
Please refer to the Swagger API contract for egov-location service to understand the structure of APIs and to have a visualisation of all internal APIs.
PDFMake: (https://github.com/bpampuch/pdfmake - Connect to preview ):- for generating PDFs
User Role
Scope of Action
Role Description
Citizen
Search Receipts
Download Receipts
Print Receipts
The citizen pays the applicable fees for miscellaneous services through the CEs or FEs
Counter Employee (CE)
Process New Collection
Search Receipts
Download Receipts
Print Receipts
Counter employees collect miscellaneous payments from the citizens online
Field Employee (FE)
Process New Collection
Search Receipts
Download Receipts
Print Receipts
Field employees also collect miscellaneous payments from the citizens on the field
Environment Variables
Description
MAX_NUMBER_PAGES
Maximum number of records to be written in one PDF
DATE_TIMEZONE
Date timezone which will be used to convert epoch timestamp into date (DD/MM/YYYY)
DEFAULT_LOCALISATION_LOCALE
Default value of localisation locale
DEFAULT_LOCALISATION_TENANT
Default value of localisation tenant
DATA_CONFIG_URLS
File path/URL'S of data config
FORMAT_CONFIG_URLS
File path/URL'S of format config
Title
Link
Customizing PDF Receipts & Certificates
Steps for Integration of PDF in UI for download and print PDF
API Swagger Documentation
Link
pdf-service/v1/_create
pdf-service/v1/_createnosave
pdf-service/v1/_search
Environment Variables
Description
egov.services.egov_mdms.hostname
Host name for MDMS service.
egov.services.egov_mdms.searchpath
MDMS Search URL.
egov.service.egov.mdms.moduleName
MDMS module which contain boundary master.
egov.service.egov.mdms.masterName
MDMS master file which contain boundary detail.
Attribute Name
Description
tenantId
The tenantId (ULB code) for which the boundary data configuration is defined.
moduleName
The name of the module where TenantBoundary master is present.
TenantBoundary.hierarchyType.code
Unique code of the hierarchy type.
TenantBoundary.hierarchyType.name
Unique name of the hierarchy type.
TenantBoundary.boundary.id
Id of boundary defined for particular hierarchy.
boundaryNum
Sequence number of boundary attribute defined for the particular hierarchy.
name
Name of the boundary like Block 1 or Zone 1 or City name.
localname
Local name of the boundary.
longitude
Longitude of the boundary.
latitude
Latitude of the boundary.
label
Label of the boundary.
code
Code of the boundary.
children
Details of its sub-boundaries.
Title
Link
Local setup
Link
/boundarys/_search
/geography/_search
/tenant/_search
Property
Value
Remarks
egov.user.search.default.size
10
default search record number limit
citizen.login.password.otp.enabled
true
whether citizen login otp based
employee.login.password.otp.enabled
false
whether employee login otp based
citizen.login.password.otp.fixed.value
123456
fixed otp for citizen
citizen.login.password.otp.fixed.enabled
false
allow fixed otp for citizen
otp.validation.register.mandatory
true
whether otp compulsory for registration
access.token.validity.in.minutes
10080
validity time of access token
refresh.token.validity.in.minutes
20160
validity time of refresh token
default.password.expiry.in.days
90
expiry date of a password
account.unlock.cool.down.period.minutes
60
unlock time
max.invalid.login.attempts.period.minutes
30
window size for counting attempts for lock
max.invalid.login.attempts
5
max failed login attempts before account is locked
egov.state.level.tenant.id
pb
Link
/citizen/_create
/users/_createnovalidate
/_search
/v1/_search
/_details
/users/_updatenovalidate
/profile/_update
/password/_update
/password/nologin/_update
/_logout
/user/oauth/token
This section provides technical details about business service setup, configuration, deployment, and API integration.
Details coming soon...
Details will be updated soon...
Indexer service runs as a separate service. This service is designed to perform all the indexing tasks of the digit platform. The service reads records posted on specific kafka topics and picks the corresponding index configuration from the yaml file provided by the respective module. Objective of Indexer service are listed as below.
To provide a one stop framework for indexing the data to elasticsearch.
To create provision for indexing live data, reindexing from one index to the other and indexing legacy data from the datastore.
Before you proceed with the configuration, make sure the following pre-requisites are met -
Prior Knowledge of Java/J2EE
Prior Knowledge of SpringBoot
Prior Knowledge of Elasticsearch
Prior Knowledge of REST APIs and related concepts like path parameters, headers, JSON etc.
Prior Knowledge of Kafka and related concepts like Producer, Consumer, Topic etc.
Performs three major tasks namely: LiveIndex, Reindex and LegacyIndex.
LiveIndex: Task of indexing the live transaction data on the platform. This keeps the es data in sync with the db.
Reindex: Task of indexing data from one index to the other. ES already provides this feature, indexer does the same but with data transformation.
LegacyIndex: Task of indexing legacy data from the tables to ES.
Provides flexibility to index the entire object, a part of the object or an entirely different custom object all using one input json from modules.
Provides features for customizing index json by field mapping, field masking, data enrichment through external APIs and data denormalization using MDMS.
One stop shop for all the es index requirements with easy-to-write and easy-to-maintain configuration files.
Designed as a consumer to save API overhead. The consumer configs are written from scratch to have complete control over the consumer behaviour.
Step 1: Write configuration as per your requirement. Structure of the config file is explained later in the same doc.
Step 2: Check-in the config file to a remote location preferably github, currently we check the files into this folder https://github.com/egovernments/configs/tree/DEV/egov-indexer -for dev
Step 3: 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 egov-indexer's environment manifest file for it to be read at start-up of the application.
Step 4: Run the egov-indexer app, Since it is a consumer, it starts listening to the configured topics and indexes the data.
For Indexer Configuration, please refer to the document in Reference Docs table given below.
a) POST /{key}/_index
Receive data and index. There should be a mapping with topic as {key} in index config files.
b) POST /_reindex
This is used to migrate data from one index to another index
c) POST /_legacyindex
This is to run LegacyIndex job to index data from DB. In the request body the URL of the service which would be called by indexer service to pick data, must be mentioned.
In legacy indexing and for collection-service record LiveIndex kafka-connect is used to do part of pushing record to elastic search. For more details please refer to document mentioned in document list.
Whenever any user logs an authorization token and a refresh token is generated for him. Using the auth token the client can make rest API calls to the server to fetch data. The auth token has an expiry period. Once the auth token is expired it cannot be used to make API calls. The client will have to generate a new authorization token. This is done by authenticating the refresh token with the server which then generates and sends new authorization token to the client. The refresh token avoids the need for the client to again login whenever Auth token expires.
Refresh token also has an expiry period and once it gets expired it cannot be used to generate new authorization token and the user will have to login again to get a new pair of authorization token and refresh token. Generally, the duration before the expiry of the refresh token is much longer compared to that of auth token. If the user logs out of the account both Auth token and the refresh token will become invalid.
`
One of the applications in the Digit core group of services aims to reduce the time spent by developers on writing codes to store and fetch master data ( primary data needed for module functionality ) which doesn’t have any business logic associated with them. Instead of writing APIs, creating tables in every different service to store and retrieve data that is seldom changed MDMS service keeps them at a single location for all modules and provides data on will with the help of no more than three lines of configuration.
Prior Knowledge of Java/J2EE.
Prior Knowledge of Spring Boot.
Prior Knowledge of REST APIs and related concepts like path parameters, headers, JSON etc.
Prior knowledge of Git.
Advanced knowledge on how to operate JSON data would be an added advantage to understand the service.
Adds master data for usage without the need to create master data APIs in every module.
Reads data from GIT directly with no dependency on any database services.
Deploy the latest version of Mdms-service
Add conf path for the file location
Add master config JSON path
The MDMS service provides ease of access to master data for any service.
No time spent writing repetitive codes with no business logic.
To integrate, host of egov-mdms-service should be overwritten in helm chart
egov-mdms-service/v1/_search should be added as the search endpoint for searching master data.
Mdms client from eGov snapshots should be added as mvn entity in pom.xml for ease of access since it provides mdms request pojos.
Java 1.8
Eclipse
Postgres
PhpPgAdmin
Postman (Application)
Respective Git MiddleWare
Kubectl
Kafka
Take the code pull from the git:
Need to consider 2 repositories for code to run locally
Municipal services - where our BPA code exists and some dependency services also available here https://github.com/egovernments/municipal-services.git - Connect to preview
Core Services - Where dependency services exist to run our code locally https://github.com/egovernments/core-services.git - Connect to preview
Import the required projects to eclipse
From municipal-services import bpa-services, bpa-calculator and land-services. From core-services import user service, idgen service, mdms service, location service, localization service, workflow service, egov-persister.
Before running the application make sure the following setups are complete to ensure the application runs smoothly.
kafka set up in your system which is running fine. Download the latest version of kafka from here. https://kafka.apache.org/downloads
Run the below commands based on your system types
For linux: in kafka folder path
Example: D:\kafka_2.13-2.4.0
> bin/zookeeper-server-start.sh config/zookeeper.properties > bin/kafka-server-start.sh config/server.properties
Ref: https://kafka.apache.org/quickstart
For Windows: in windows path
Example: D:\kafka_2.13-2.4.0\bin\windows start zookeeper-server-start.bat ....\config\zookeeper.properties start kafka-server-start.bat ....\config\server.properties
And lombok setup for eclipse For ref: https://www.journaldev.com/18124/java-project-lombok
Kubectl setup based on the requirement To get the pods: kubectl get pods To port forward: kubectl port-forward <<pod name>> <<port number>>:8080 To get the logs: kubectl get logs
After all the setups are done successfully, try to run the application locally.
BPA-Services How to run the application in local:
Check the services which are connected to local and which are connected to dev
Which are connected to dev no need to change anything.
If it is connected to local check the services are in below list IDGEN – can run locally or can point to dev from cmd prompt PERSISTER – can run locally MDMS – can directly point to dev or can run in local LOCATION – can directly point to dev WORKFLOW – can point to dev or can run locally LOCALIZATIONS – we can directly point this to dev USER-SERVICE – need to point to dev from cmd prompt LAND-SERVICE – need to run locally BPA-CALCULATOR – can run locally or can point to dev.
If the changes are from these services follow the below process to run those respective services.
For core services:
IDGEN:
Approach 1: Directly point this to dev from the application.properties in bpa-services Approach 2: Point this to local and give the port forward to dev by using kubctl.
Note: We are not running this service locally.
PERSISTER:
U need to run it in local and need to add respective yaml files in persister resource folder which are bpa-persister.yml and egov-workflow-v2-persister.yml and also land-persister.yml
And need to add these in persister application.properties repo path
Note: Please check whether data is is saving or not in local data base(DB).
MDMS:
to run local: For running this in local need to change in 2 file that is application.properties and MDMSApplicationRunnerImpl
In application.properties need to change the paths for the master-config url as path of master-config.json and for config path as upto pb/bh
In MDMS ApplicationRunnerImpl need to change the data in a function from the path to file.
to point to dev: Approach 1: Directly point this to dev from the application.properties in bpa-services
Approach 2: Give it as local connection in BPA application.properties and port forward to dev by using kubectl.
Postman Collection https://www.getpostman.com/collections/c59b5c6190719ecd306a
LOCATION
Approach 1: Give it a local connection in BPA application.properties and port forward to dev by using kubectl.
Approach 2: Directly point this to dev from the application.properties in bpa-services
Note: Not tried it in local / may got errors so pointing to dev.
Postman collection https://www.getpostman.com/collections/4f6a25a4fb32572af5ff
WORKFLOW
to point to dev: Approach 1: Directly point this to dev from the application.properties in bpa-services
Approach 2: Give it as local connection in BPA application.properties and port forward to dev by using kubectl.
to run local:
can run locally by pointing to the local database, but for this need to create the workflow locally using the workflow create API.
Postman collection https://www.getpostman.com/collections/aa30be8a8b9de4c13aa8
USER-SERVICE Approach 1: Give it as local connection in BPA application.properties and port forward to dev by using kubectl.
Approach 2: Directly point this to dev from the application.properties in bpa-services
Note: In local not able to run the application successfully, so the following dev.
Postman Collection: https://www.getpostman.com/collections/60bbd6aed27605dcc270
LOCALIZATIONS
Approach 1: Directly point this to dev from the application.properties in bpa-services
Approach 2: Give it as local connection in BPA application.properties and port forward to dev by using kubectl.
Postman Collection https://www.getpostman.com/collections/12cc4c3855be9699c278
Changes from Municipal services
BPA-Calculator:
to run local:
can run locally by pointing to the local database.
to point to dev: Approach 1: Directly point this to dev from the application.properties in bpa-services
Approach 2: Give it as local connection in BPA application.properties and port forward to dev by using kubectl.
Land-Service:
to run local:
can run locally by pointing to the local database.
to point to dev: Approach 1: Directly point this to dev from the application.properties in bpa-services
Approach 2: Give it as local connection in BPA application.properties and port forward to dev by using kubectl.
Other than these services can directly by pointing to dev url.
Note: After running the application successfully please check if the data is saving in db or not.
egov-user - (Manage user)
tl-services - Stakeholder Registration (Registration process of Stakeholder is handled by this service)
egov-user-event (What’s New and Events)
egov-filestore (To store the documents uploaded by the user)
egov-idgen (To generate the application No, Permit No)
egov-indexer (To index the BPA data)
egov-localization (To use the localized messages)
egov-location (To store the address locality)
egov-mdms (Configurations/master data used in the application is served by MDMS)
egov-notification-sms (Service to send SMS to the users involved in the application)
egov-persister (Helps to persist the data)
egov-searcher (Search query used to simplify the search)
egov-workflow-v2 (Workflow configuration for different BPA application is configured)
pdf-service (Receipt’s, permitorder etc.. and prepared)
billing-service (Create demands and bills for the fees to be collected)
collection-services (Create a receipt for the payment received for the bills)
bpa-calculator (Calculates the fees to be collected at different stages)
land-services (land information related to BPA application is stored)
dcr-services (get and validate EDCR data)
Technical release notes for DIGIT Trade License module
The above build’s has to be deployed to perform migration. The batch persister config has to be added in config Repo. After adding the file in repo, update the persister path in environment yml file. Make sure the persister.bulk.enabled is set to true. Once done restart the persister pod.
To start the migration call the following API with tenantId as param it will migrate data belonging to that tenantId. The API does not have role action mapping and should be used by port forwarding rainmaker-pgr pod.
*(Last query related to document might need little modification as values in NOT IN clause can be more than the 2 specified)
null value is stored in action for adding comments in old system it’s mapped to COMMENT in new system.
Locality attribute in new eg_pgr_address_v2 table does not allow NULL values whereas the locality attribute in old eg_pgr_address in Punjab prod data has NULL values. Those values are filled in migration with dummy value NOT_AVAILABLE.
For 128 records accountId is NULL and so they won’t be associated with any citizen login.
For some records in media column corrupt data is present. For example on one case instead of fileStore uuid some normal text describing the complaint is present. While some other records have values like no . For data with such text having length greater than 64 are set to null, else DB validation’s are violated.
In old system id is stored for referencing user data. In new systems we use uuid to refer user, therefore all id are mapped to respective uuid which are then migrated to new system. If some user has uuid as NULL default value NOT_SPECIFIED will be used.
Some 1104 complaints has value in column named feedback which seems to be from some set pf predefined values like "Resolution Time","Quality of work",”others” etc. New structure don’t have any such column so we will be storing this in additionalDetails.
Address and landmark column in eg_pgr_service has values in some column they are also stored in additionalDetails.
Phone column contains phone numbers, we are not migrating that column as it has PII data and will be already present in user service as well.
If sla is not found in old config (will only happen if some complaint category is removed from MDMS and complaints are present in system of that category) default SLA value will be used.
DIGIT 2.2 Changes to the Water & Sewerage Module
The latest Water & Sewerage (W&S) release version features two distinct product enhancements. One leverages the ‘open’ search and payment capability of the DIGIT platform. The second enhancement feature relates to the availability of configuration options within W&S to help adoption.
Open search and payment for W&S recurring bill payments
W&S and Property Tax module configuration options for processing new applications
Extending this config to W&S modify the connection.
Enhancing validations and UI put in place for property creation
Param
Description
access.token.validity.in.minutes
Duration in minutes for which the authorization token is valid
refresh.token.validity.in.minutes
Duration in minutes for which the refresh token is valid
API
Description
/user/oauth/token
Used to start the session by generating Auth token and refresh token from username and password using grant_type as password. The same API can be used to generate new auth token from refresh token by using grant_type as refresh_token and sending the refresh token with key refresh_token
/user/_logout
This API is used to end the session. The access token and refresh token will become invalid once this API is called. Auth token is sent as param in the API call
Environment Variables
Description
egov.mdms.conf.path
The default value of folder where master data files are stored
masters.config.url
The default value of the file URL which contains master-config values
egov-mdms-service/v1/_search
Key Feature | Description |
SENDBACKTOCITIZEN | Modified behaviour of SENDBACKTOCITIZEN action in TL |
Doc Links | Description |
Title
Link
egov-mdms sample data
master-config.json
Doc Links | Description |
TL Technical Doc |
Config/Service Name | Path/Build |
Persister yml for bulk migration |
pgr-services | pgr-services-db:pgr-migration-2475ec38-56 |
rainmaker-pgr | rainmaker-pgr-db:pgr-migration-c046a264-20 |
Feature | Service Name | Changes | Description |
Common Pay | Arrears Tax head changes for Common pay |
WS | Updated the one-time fee format for WS |
All | Digit 2.2 Release changes |
PGR | PGR UI V2 navigation URL changes and added pin codes for City A and City B |
Role Action Mapping | Added Workflow Process Count access to TL, Fire NOC, WS and BPA Employees |
DSS | Added mandatory DDRname for all tenants |
Module | Action | PR | Description |
WS | Updated searcher query for W&S in UAT |
WS | WS persister changes and order rearranged for PGR Reports |
All | Digit 2.2 Release changes |
HRMS | HRMS Employee create changes |
Common Pay | Payer details changes in Payment Receipt |
BPA | Collection search endpoint changes |
DSS | Indexer config fix for PGR Services and DSS related config changes for UAT |
PGR | Created PGR migration batch file |
Feature | Feature | Description |
PGR | Digit-ui Configuration |
WS | Digit 2.2 Release changes for UAT |
Filestore | Disabled Minio in UAT |
PGR Service | Path to pgr-services.yml indexer config |
Key Feature | Description |
Open search and payment | Changes in SMS notification:
W&S Connection search in Public Domain:
|
W&S and PT Config | The latest W&S module version now has two configuration options and they can switch between them according to the state’s requirement:
|
DIGIT 2.2 Changes to the eDCR Module
eDCR Service 1.0.2 is a baselined release that has got few enhancements to the existing features.
eDCR 1.0.2: The above feature is useful and required in other states.
The above features are configurable. Users can enable the features if required for the selected state.
Impact: Functionally, the upgrade to eDCR 1.0.2 will not impact the existing environments.
DIGIT 2.2 technical changes to the Public Grievance and Redressal Module
The API contract for PGR module is revamped based on the new contract. The module is now integrated with workflows, which provides flexibility in managing workflow configuration. The API is integrated with the new Digit-UI.
Integration with workflow
Clean and straightforward API structure compared to previous Rainmaker-pgr module
Functionality to migrate from old rainmaker-pgr module to the new version
None
None
,
, , , ,
,
,
, ,
,
,
, ,
S.No. | Feature | Description |
1. | Road Reserve | A road reserve is an area of land within which facilities such as roads, footpaths, and associated features may be constructed for public travel. Earlier extracting the area of the road reserve. In this release, we are extracting the distances from the concerned layer. The distance should have declared as the dimension in the corresponding layer. |
2. | Height of Room | Extract the room type dynamically based on colour code config. The colour codes are used to identify the type of room. |
3. | Vehicle Ramp | In the plan, the vehicle ramp will be drawn using polyline and we were capturing the floor height as a dimension from vehicle ramp layer. The system was calculating the slope based on floor height and length of the vehicle ramp. Along with this, we added a new provision to define slope manually. The slope should be defined as MTEXT in the vehicle ramp layer, ex: SLOPE=1IN12. |
4. | Floor Unit | Currently, in the floor unit, the occupancy type and area values are the system is extracting and providing. From this release, the colour code value also will be available in the floor unit. Different colour codes needed to differentiate EWS, LIG, MIG1 & MIG2 Dwelling Units. |
Key Feature | Description |
Complaint Filing and Tracking | The citizen can file the grievances and track the complaint status easily |
Workflow Integration | PGR is now integrated with workflow service, the workflow for PGR now can be easily configurable |
Migration | API to migrate data from old PGRmodule to the new format |
Details will be updated soon...
Details coming soon...
Details coming soon...
Doc Links | Description |
PGR Service Technical Doc |
PGR migration Doc |
Learn how to configure the DIGIT platform. Partner with us to enhance and integrate more into the platform.
Summary of DIGIT OpenSource GitRepos and it's purpose. If you are a partner/contributor you may choose to fork or clone depending on need and capacity.
Learn how to search, download and print your payment receipts
The citizen pays the fees for miscellaneous services through the CEs or FEs. Once the payment transaction is complete the citizen can access the payment receipts online.
Citizens can
Search receipts
Download receipts
Print receipts
Citizens can search for payment receipts and download or print these online. To search for payment receipts navigate to the Collections option in the sidebar main menu.
Enter the relevant search parameter. The system enables you to search using payment Receipt No. or Service Category, or payee Mobile No. Click on the Search button.
The system will display the relevant search results in the panel below. Click on the relevant record to view the payment receipt.
The system will generate a pdf format of the payment receipt. Click on the download icon on the pdf page to download the receipt.
Click on the Print icon on the pdf page to print the receipt.
Click on the Reset button to renew your search with different parameters.
Details will be updated soon...
Point of Sales (POS) machine is a machine that helps in handling transaction processing. This machine accepts and verifies the payments which are made by citizens for prevailing the services of DIGIT.
POS facilitates a middleware app developed in order to verify the payment process between the DIGIT module and the payment.
In this case, no data is required from the state team.
Not applicable.
Not applicable.
Not applicable.
Not applicable.
DIGIT has modules which require the user to pay for the service that he/ she is availing for example property tax, trade license etc. . In order to achieve the functionality, we have a common payment gateway developed which acts a liaison between DIGIT apps and external payment gateways (which depends on the client requirements).
This module facilitates payments and lookup of transaction status.
Following are the details required from the payment gateway vendor in order to configure the payment gateway:
Data given in the table is a sample data.
The payment gateway is a vendor oriented service that is integrated with different modules in order to facilitate the transactions. Below mentioned are the steps which are followed:
The client has to finalize a payment gateway vendor (for example PAYU, Paytm, HDFC, AXIS atc.) depending upon the requirements.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
After which the details/ documents mentioned in the template would be provided by the vendor.
These details are to be received separately for both prods as well as UAT.
Get the IP address for UAT and Production environments whitelisted from the vendor.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
This is the next step after collating all the boundary hierarchies which are being used in the state. In a hierarchy, there are certain types of boundary classification and in all the levels there will be a mapping which we could define as a parent-child mapping in order to link certain levels of the classification.
For example, a hierarchy could be:
Administration Hierarchy: City/ULB → Zone → Ward → Locality
In the above-mentioned hierarchy, a City/ULB is being divided into different into zones followed by zones into wards and at the end wards into the locality.
Data has to be collected for every boundary hierarchy type and boundary type with a mapping between the boundary code and its parent boundary code. Following is the table which is to be used across all the hierarchy types.
Data given in the table is a sample data.
Following is the definition of the data columns which are being used in the template:
Following are the steps which should be used to fill the template:
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
After Identifying all the boundary hierarchy, get the sub-classification of all the hierarchies.
Figure out the codes for all the sub-classification for a particular city/ULB.
Start filling the template from the top of the hierarchy in a drill-down approach.
A parent-child mapping code has to be created for every boundary level except for the top level.
Follow the steps until you reach the last sub-classification.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
It is a ULB bank account which is operative at least to receive or deposit the day to day revenue collection done by the ULB. It is used by online payment integrator to disburse the amount in ULBs accounts which have been collected through a payment gateway into a pool account managed by the payment gateway.
Below given data table represents the excel template attached. Data given in the table is a sample data.
Data given in the table is sample data.
Download the data template attached to this page.
Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.
Make sure all the headers, its data type, field size and its definition/ description is understood properly. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
Identify the bank account which is to be used to transfer the amount which is collected online for various services.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise until the entire data is filled into a template.
Verify the data once again by going through the checklist and taking care of each and every checklist point/ activity mentioned in the checklist.
The checklist is a set of activities to be performed after the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
To see the common checklist refer to the page Checklist consisting of all the activities which are to be followed to ensure complete and quality data.
This checklist covers the activities which are specific to the entity.
Sr. No
Integration Kit
API Documentation
Redirect Working Key
Merchant Id
Test credential of Debit Card/ Net banking
1.
File Name
File Name
XYZ#123
UDDUK
File Name
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Definition/ Description
1
Integration Kit
Document
NA
Yes
This is a document that is sent by the vendor which contains information on how to integrate the service
2
API Documentation
Document
NA
Yes
This is a separate document which is sent by the vendor in order to help ideally helps us to retrieve the transaction status
3
Redirect Working Key
Alphanumeric
64
Yes
The working key is provided by the vendor for the generation of the redirection URL
4
Merchant Id
Alphanumeric
64
Yes
Merchant id provided by the vendor
5
Test credential of Debit Card/ Net Banking
Document
NA
Yes
These are the details of the debit/credit card or net banking credentials which would help us test the gateway
This contains the card number/Code/Account number etc.
Sr. No.
Checklist Parameter
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Checklist Parameter
Example
1
While finalizing a payment gateway vendor make sure that the vendor should support transactions into multiple bank accounts based on the key( which would be tenantid)
-
2
Do get the details for both the environments separately i.e UAT and Production
-
Sr. No.
Boundary Code*
Boundary Name* (In English)
Boundary Name* ( In Local Language)
Parent Boundary Code*
Boundary Type*
Hierarchy Type Code*
1
W1
Ward no.1
वार्ड नंबर 1
Z1
Ward
ADM
2
W2
Ward no.2
वार्ड नंबर 2
Z1
Ward
ADM
3
W3
Ward no.3
वार्ड नंबर 3
Z2
Ward
ADM
4
W4
Ward no.4
वार्ड नंबर 4
Z3
Ward
ADM
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory?
Description
1
Boundary Code
Alphanumeric
64
Yes
This is a code for the sub-classification for a particular boundary. Should be unique across all boundaries defined
2
Boundary Name (In English)
Text
256
Yes
The name of the boundary that is being defined in the English language
3
Boundary Name (In Local Language)
Text
256
Yes
The name of the boundary that is being defined in the local language of the state e.g. Telugu, Hindi etc.
4
Parent Boundary Code
Alphanumeric
64
Yes
This is the boundary code of the parent which identifies to which parent the child belongs to
5
Boundary Type
Text
256
Yes
The name of the boundary type i.e. Ward, Zone etc.
6
Hierarchy Type Code
Alphanumeric
64
Yes
The code of the Boundary Hierarchies for which this particular boundary is defined
Sr. No.
Activity
Example
1
Make sure that each and every point in this reference list has been taken care of
Sr. No.
Activity
Example
1
Every boundary type of data should be filled separately
-
Sr. No.
Code*
ULB Name*
Bank Name*
Branch Name*
Account Number*
Account Type*
IFSC*
1
dehradun
Dehradun Municipal Corporation
SBI
Rajpur
XXXX0082XX01
Saving
SBIX0921
2
haridwar
Haridwar Municipal Corporation
PNB
Chauk
XXXX9820XX9
Saving
PNBX8320
Sr. No.
Column Name
Data Type
Data Size
Is Mandatory
Definition/ Description
1
Code
Alphanumeric
64
Yes
Unique code is given to the bank detail record e.g. dehradun
2
ULB Name
Text
256
Yes
Name of Urban Local Body
3
Bank Name
Text
256
Yes
Name of the bank where the account exists
4
Branch Name
Text
256
Yes
Name of the bank branch where the account exists
5
Account Number
Alphanumeric
64
Yes
Bank account number to be used to transfer the amount
6
Account Type
Text
256
Yes
Account type. e.g. Saving, Current etc.
7
IFSC
Alphanumeric
64
Yes
IFS code of branch as per FBI guidelines
Sr. No.
Activity
Example
1
Code should not consist of any special characters
E.g. dehradun is allowed but dehradun@1 is not allowed
2
The account number should not consist of any special characters.
As issued by the bank