Garima Release Notes
Last updated
Last updated
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
The urban-rural convergence is an initiative that aims to ensure access to sanitation services to all gram panchayats (GPs) via urban local bodies (ULBs) located closest to them.
A ULB employee creates applications to cater to the sanitation needs of local communities in urban areas. In the same way, they should also cater to the same sanitation needs of rural bodies near that urban region.
They need a provision in a system while creating a new application to either choose local municipalities or urban-supported villages.
Based on their choice they would be able to select either a locality/mohalla or a GP area from the respective master data drop-down list.
The caveat here is that if a ULB employee chooses GP, then the trip amount field should be editable where he/she can fill in any logical amount based on the offline calculation instead of the auto-calculated amount already there in an application in the case of urban bodies.
ULB employees or DSO operators should also be able to edit the number of trips. The final amount should be multiple of the initial amount entered into an application with the number of trips.
Update the MDMS data: boundary-data.json
- Add a new children hierarchy for GP under city which will be parallel to locality. A sample MDMS is attached below:
By default, the 'Urban' option will be pre-selected in the radio button in the above wireframe and the drop-down will have the locality/mohalla master data. If an employee selects “ULB supported village”, then the locality/mohalla drop-down will be replaced by GPs and village drop-down data on the fly.
The system will use the below URL to fetch the localities or GPs and their corresponding villages.
- In the case of localities, one needs to pass boundaryType as “Locality”.
https://dev.digit.org/egov-location/location/v11/boundarys/_search?hierarchyTypeCode=REVENUE&boundaryType=Locality&tenantId=pb.amritsar
- In the case of GP/villages, one needs to pass the boundaryType as “GP”.
https://dev.digit.org/egov-location/location/v11/boundarys/_search?hierarchyTypeCode=REVENUE&boundaryType=GP&tenantId=pb.amritsar
Introduction of a new string column (boundary_type) in the FSM_APPLICATION table to capture (locality or GP) to determine if the application created is for rural or not so that in the near future it will be helpful for the analytics and statistics in dashboards.
- The default value for this column will be locality to support backward compatibility
Adding a vehicle log would also have the option to select urban (default option) or rural. If rural gets selected the text name of an element would be replaced from 'locality' to “Gram Panchayat” for a text field.
Introduction of a new column of string type (boundary_type) in the vehicle_trip table to capture if the vehicle log is created for the GP or not.
- The default value for this column will be Locality to support backward compatibility.
boundary-data.json
UrcConfig.json
To enable URC feature in the UI:
We are keeping the locality hierarchy under the city as it is [No change there]. And the ‘location api’ with boundaryType as 'locality' will be used the same way it's being called currently to get the localities. Below are the API details: https://dev.digit.org/egov-location/location/v11/boundarys/_search?hierarchyTypeCode=REVENUE&boundaryType=Locality&tenantId=pb.amritsar Response:
To get a list of gram panchayats and corresponding villages, pass the boundaryType as 'GP'. Below are the API details: https://dev.digit.org/egov-location/location/v11/boundarys/_search?hierarchyTypeCode=REVENUE&boundaryType=GP&tenantId=pb.amritsar
Table Name | Column Name | Comments |
eg_fsm_application | boundarytype | To capture (locality or GP) to determine if the application created is for rural or not based on the radio button selection. |
eg_fsm_address | additionaldetails.gramPanchayat | To store the selected GP while creating an application. |
eg_fsm_address | additionaldetails.village | To store the selected village while creating an application. |
eg_vehicle_trip | boundarytype | To capture (locality or GP) if the vehicle log is created for GP or not. |
To analyse the impact, we deployed a different module (property tax) which points to the same boundary-data mdms.
Expectation:
For FSM Module: Non-URC flow: The locality drop-down should show all the localities as it is (there should be no impact). URC flow: The gram panchayat and village drop-down should show as per the new GP and village added to the MDMS.
For Property Tax Module: The locality drop-down should show all the localities as it is (there should be no impact).
Property Tax Screen:
The locality dropdown in property tax displays the values from the existing location hierarchy itself (there is no impact).
SUJOG FSM (NON-URC)
In FSM, for non-URC, the locality drop-down shows the values from the existing hierarchy itself (there is no impact)..
SUJOG FSM (URC)
GP drop-down In the case of FSM (URC), the gram panchayat and village drop-downs are showing values from the new hierarchy we have configured in the existing MDMS.
Village Dropdown
Pricing
Pricing per trip will be entered by “ULB employees” for each request.
ULB employees will have a free text entry field to enter the price for a request.
In FSTP, there are two scenarios -
Selects a gram panchayat from drop-down but the village is not in the list. In this case, select 'other' in the village and a free text field appears.
Select 'other' in the GP list. In this case, 2 free text fields appear - one for GP and one for village.
If the locality or GP is located outside the city, then select “Outside ULB Limits” and provide the locality/gram panchayat name in the text field.
In the dashboard, add the following chart:
Add pie chart: Applications by source
Pie chart value: Ratio of applications from GP: Ratio of requests from urban areas.
Add toggle for applications and sludge.
Pie chart value: Ratio of sludge disposed from GP: Ratio of sludge from urban areas.
Tooltip: Show total applications and total sludge (See design). Tooltip value to be responsive to toggle between unit, lakh, and crore.
The chart should filter based on the period, district, ULB (dashboard filters).
Add bar chart: Number of applications per month from the GP.
Bar chat value: The total number of applications from the GP.
Add toggle for applications and sludge disposed.
Tooltip: Show the total applications and total sludge (See design). Tooltip value to be responsive to toggle between unit, lakh, and crore.
The chart should filter based on the period, district, ULB (dashboard filters).
The chart should have export, share, and download options.
The chart should have export, share, and download options.
