Following are the steps to assign a sanitation worker and vehicle
The DSO/ULB employee can assign a sanitation worker and vehicle in a single screen.
The DSO can assign the vehicle and search for a sanitation worker using the Garima ID. The exact available match is displayed. Note: When we search with the Garima ID, the API will return name and mobile number along with the searched ID.
-Single driver can be assigned.
-Multiple helpers can be assigned.
If the searched worker is not available, an error message "Worker not found! Please register!" is displayed. The DSO can register the sanitation worker by clicking on “Register New Sanitation Worker”. The sanitation worker can either be added as a driver or helper as per requirement
Once the details are filled , the DSO clicks on “Register and Assign”.
The details of the worker should be auto-populated in the previous screen, that is, “Assign Vehicle and Sanitation Worker”.
The sanitation worker is assigned and the details are displayed in the application page.
Sujog-FSM is implemented as a part of SUJOG for the state of Odisha. Odisha is currently on v1.3 of DIGIT Sanitation. The following is the list of changes made to the product for implementation:
1. Localisations:
The localisation changes are done according to the application flow:
2. Additional Builds: Urban-rural convergence is an initiative that aims to ensure access of sanitation services to all gram panchayats (GPs) via urban local bodies (ULBs) located closest to them. With efforts in implementing decentralised waste management across 114 ULBs as well as enabling the rural population to avail sanitation facilities from urban areas located nearby, eGov with CPR (post-field observations and research) decided to include gram panchayats in SUJOG FSSM as part of this initiative. See details of the customisation here.
3. The following MDMS have been configured.
Property-type
Property Sub-type
Slum Names
GP List
Village List
FSTP details
4. The following user categories/roles have been created:
5. FSM Related builds deployed
6. URL and Credentials of SUJOG-UAT environment for reference.
ULB employee URL : https://sujog-dev.odisha.gov.in/employee/user/login
Citizen URL : https://sujog-dev.odisha.gov.in/citizen/user/login
Credentials:
ULB employee Username : EMP-AND-000167
FSTPO Username : EMP-AND-000168
Password : eGov@123
User
Flow
Step
Changes
Citizen
Apply for emptying of septic tank
Citizen creates application
1.On the Property Location Page, Within ULB Limits and From Gram Panchayat added
2.On Payment Details Page, if the Total Amount is N/A, then additional notification will be displayed: "You will be notified shortly of the total amount once the de-sludging request is accepted."
3."Minimum Amount Payable (₹) and Advance Amount To Be Paid (₹) * are added.
Employee
Septic tank emptying request
When employee creates an application
1.Property Location changed as a mandatory field.
3.Property Location has two fields - Within ULB Limits and From Gram Panchayat.
4.Localisation: Advance Amount To Be Paid (₹) * added.
Submit application
After creating the application
1. Localisation: ‘Application Number’ is changed to “Desluding Request Number’”.
View application
All stages in workflow
1. Seperate sections created for displaying ‘Trips’ And “Amount Details”.
2. Additional fields displayed ‘Advance Amount Paid and Balance Amount Paid.
Assign DSO
Search application after creating
2.Localisation: DSO has been replaced with ‘Cesspool Operator’ across SUJOG.
Entire Workflow
Send Back option
“Send back” as a workflow step has been removed from the workflow.
Update trips
After creating the application
1.Localisation: “Update Trip Details” has been replaced with “Update/Schedule Trips’”.
Complete Request page
Error message added. If the bill is pending, the following error message will be displayed - “"Cannot close the application since bill amount is pending."
Employee Inbox
Inbox
Selecting inbox option in employee portal
1.Locality added as a ‘Filter’ option.
2. Localisation: DSO has been replaced with “Cesspool Operator” across SUJOG FSSM.
FSTP
FSTP Inbox
Update application
"Vehicle In time *,Vehicle Out time *" as input fields are removed and will be auto-capured based on the time of action.
Vehicle Log
1.Localisation: “Add Vehicle Log” has been replaced with “Add new”.
2.Additional Vehicle number format have been added for validation: AB 00 C 1234.
Role in Digit Sanitation v1.3
Role in Sujog
FSM Employee Dashboard Viewer
FSM Employee Report Viewer
FSM Payment Collector
FSM Employee Application Creator
FSM Administrator
FSM Employee Application Editor
ULB Editor
FSM FSTP Opperator
FSTPO
Category
Services
GIT TAGS
Docker Artifact ID
Remarks
FSM v1.3
FSM
fsm:v1.3.0-29c64d6941-24
FSM calculator
fsm-calculator:v1.2.0-01dd6c9b3a-14
Vehicle
vehicle:v1.3.0-5682061fd3-18
Vendor
vendor:v1.3.0-d0ddde9f1b-45
Inbox
inbox:v1.1.1-3d4c447770-60
No changes in this release
Digit-UI fsm v1.3
DIGIT UI
digit-ui:v1.6.0-4332691db5-174
Shared service in DIGIT
DIGIT Dependency Builds
The FSM release is bundled with the DIGIT 2.8 release hence the release builds for the DIGIT 2.8 release can be referred from this link.
Configs v1.3
MDMS v1.3
Localisation v1.3
Urban-rural convergence is an initiative that aims to ensure access of sanitation services to all gram panchayats (GPs) via Urban Local Bodies (ULBs) located closest to them. With efforts in implementing decentralised waste management across 114 ULBs as well as enabling the rural population to avail sanitation facilities from urban areas located nearby, eGov with CPR (post-field observations and research) decided to include gram panchayats in the FSM application as part of this initiative.
Under the urban-rural convergence (U-RC) GPs are tagged to ULBs which will service desludging requests for households in the respective GPs. The process-flow across the value chain, and actors would remain the same. However, the logic of pricing and billing of requests from GPs may vary from requests within the limits of the ULB itself.
Currently, the factors that are being considered to determine pricing are :
Location of the GP
Distance of the GP from ULB
Distance of GP from the FSTP
Considering these pricing inconsistencies, we are designing and releasing a simple version of the urban-rural convergence system. With the success of a statewide rollout, larger populations and households can have access to and benefit from the FSM module and subsequently the service with speed, and at scale.
The users’ needs and the value this feature would provide are as follows:
If we allow households from GPs to raise (or ULBs to record) requests in the FSM application, they will use it responsibly which would result in reduced public dumping with the waste collected and disposed of properly.
If we allow ULB admins to view inputs from GPs in the FSM module on the dashboard, they will use it responsibly and improve the quality of service by making better data-driven decisions.
Using the above, we have outlined modifications in the FSM module to include gram panchayats:
A field/option to select gram panchayats tagged to a locality from a list to be provided while creating a new desludging application. The amount per trip field will be changed to a free text field instead of an auto-calculated and auto-populated amounts field, and the demand will be generated based on the new amount added.
As the actual amount will be known once the DSO/driver reaches the citizens’ location and sees the property + distance, an option to update the amount per trip is provided where the user updates the trip to start the service.
Addressed in the Out of Scope section.
The above solution should cover the majority of U-RC use cases, but there are scenarios (edge cases) that deviate from the options. Workarounds for the same are suggested here.
*assumption to be validated post launch.
From our on-ground research and observations, of the 40-60 requests the ULB receives for desludging, 4-7 of them are from GPs. This implies that approximately 10% of the total requests per month are from GPs. The above percentage of occurrence is within that 10%. These use cases will be handled in future versions.
While creating a New Desludging Application, a radio button to select gram panchayats is provided. The list of GPs is shown in the dropdown and this field will be based on the Locality selected in the "Location Details" section. The radio button is selected by default on “Within ULB Limits”. By selecting gram panchayat and the name of the gram panchayat from the dropdown, the Amount per trip field (in the Payments Details) section is changed to a free text field. The total and advance are calculated based on the same.
Based on field observations, the actual amount is only known once the vehicle reaches the citizens’ location. Hence, an additional field to edit the amount per trip is provided along with the Update Trips in the pop-up before starting the service. The FSM calculator calculates the total amount and balance based on the same, and the billing service generates the demand accordingly.
A new tenant service must be created in the MDMS for gram panchayats. The necessary updates as per the following must be made in fsm-address and fsm-geolocation entity list.
List of entities:
ULB
- Locality
- City
- Gram panchayats
The success criteria for U-RC are:
We will track the metrics below to gather learnings on the impact of these changes on FSM to share it on the FSM dashboards and reports. But more specifically, we will track the metrics to see:
If our hypotheses are correct?
Is the FSM services more accessible(given criteria above)?
What are the unanticipated implications?
Additionally, we must monitor guardrails to ensure there are no major implications on the ULBs’ ability to handle requests (for example, major changes to the volume of requests and difference in SLAs of service between GP and non-GP).
Guardrails
Sanitation worker safety is of national importance. The national mandate for the same is issued under the “Emergency Response Sanitation Unit (ERSU)”. The Urban Management Centre (UMC) is leading the implementation of ERSU across Odisha. As part of ERSU, UMC along with the state of Odisha has rolled out a programme on sanitation worker benefits called 'Garima' whose main objective is to identify, monitor, and support sanitation workers and their families.
eGov is collaborating with UMC on “Sanitation worker safety” for Odisha, which includes building the platform and product capabilities for Garima
The Urban Management Centre is a non-profit organisation with a mission to “Make Cities Work for Everyone”. Since 1997, it has strengthened the local governance through technical support, policy formulation and implementation, and dedicated capacity building. The UMC works closely with the Government of India, as well as state governments across India. The UMC has institutionalised several key innovations in urban governance across India, including a shift towards service-level benchmarking of urban services, evidence-based planning, and capacity building of government stakeholders.
The Housing and Urban Development Department, Odisha, launched the Garima scheme in 2020. The statewide scheme aims to ensure the dignity and welfare of 20,000 core sanitation workers who are exposed to hazardous working conditions, including coming in close contact with faecal sludge in toilets, septic tanks, and sewer treatment facilities.
The scheme highlights that the first step to empower sanitation workers is by recognising them as professionals entitled to safety, benefits, and rights with specific skill-sets and capabilities. To identify the number of sanitation workers, the state has rolled out a robust methodology to create a database of sanitation workers through the generation of unique IDs. The state has been able to create a dynamic database of 15,000-plus informal sanitation workers who can now avail the entitled benefits.
Objective
The objective of the collaboration between eGov and UMC through an integration with Garima is to create a record of service delivery to:
Provide enumeration and benefits to sanitation workers.
Identify the percentage of services with evidence of safe practices.
eGov, through its DIGIT FSM platform - implemented in Odisha - can serve as a data capturing layer for the above and provide access to this information to UMC. The plan is to start with Phase 1. The following will be the scope of work across the partnership:
Scope of Work
The UMC in Odisha has been able to create a unique database of 15,000-plus sanitation workers. This database will serve as a registry integrated with DIGIT FSM, to capture transactional information around data requests served by these workers. This information will further be made available to the UMC. The following will be a part of this:
Provision of ULB/DSO to assign one or more sanitation workers to each request:
Sanitation workers will be made available via integration with the Garima database through API in the workflow.
Since the Garima ID may not be well known to the ULB/DSO, a search functionality is to be made available via the entry of a phone number.
Preview details of the selected sanitation worker for confirmation.
Capture sanitation worker details if a sanitation worker is not available in the Garima database. As per discussions with UMC, details required for the generation of a provisional Garima ID are First name, Last name, DOB, Gender, Mobile number and City details.
Provide aggregated data around how many requests are served by date via unique Garima IDs by API to UMC.
There will be no linking between the Garima worker and vendor done in Sujog FSM.
Detailed Solution
Along with assigning a vehicle, the DSO will assign sanitation workers to a request. The sanitation workers will be assigned by entering the Garima ID. If the Garima ID number exists in the database, details of the sanitation worker, that is, name and Garima ID to be displayed on the screen for the DSO to confirm. In case, the Garima ID does not exist, the DSO will enter sanitation worker details (First Name, Last Name, DOB, Gender, Mobile number). A DSO may assign one to many sanitation workers to a request. However, entering a minimum of one sanitation worker to a request is mandatory.
The following data will be made available from Garima to Sujog via APIs:
Details of sanitation workers registered in Garima (Name, Mobile Number and Garima ID).
The following data will be made available to UMC via APIs:
Aggregated data around how many requests are served by date by unique Garima IDs by API to the UMC.
Workflow with Garima integration:
What changes would affect which municipal, business and core services?
Updating Application | DSO in Progress
a. Adding sanitation worker
b. Registering a new sanitation worker
Find the mock-ups below:
The DSO/ULB employee can assign a sanitation worker and vehicle in a single screen.
The DSO can assign the vehicle and search for a sanitation worker using the Garima ID. The exact available match is displayed. Note: When we search with the Garima ID, the API will return name and mobile number along with the searched ID.
Single driver can be assigned.
Multiple helpers can be assigned.
If the searched worker is not available, an error message "Worker not found! Please register!" is displayed. The DSO can register the sanitation worker by clicking on “Register New Sanitation Worker”. The sanitation worker can either be added as a driver or helper as per requirement
Once the details are filled , the DSO clicks on “Register and Assign”.
The details of the worker should be auto-populated in the previous screen, that is, “Assign Vehicle and Sanitation Worker”.
The sanitation worker is assigned and the details are displayed in the application page.
There is no way to validate the correctness/uniqueness/verifiability of the Garima database.
For sanitation workers not available in the system, the same details will have to be added multiple times for requests assigned to the workers until they are included in the system.
The collection of information on safety equipment used is based on citizen feedback and may not be accurate or complete.
The above solution should cover the majority of Garima use cases. However, there are scenarios that deviate from the options:
Municipal Services
Business Services
Core Services
What?
How?
What?
How?
What?
How?
FSM application
Additional fields to enter sanitation workers.
API integration
API integration with Garima database to pull sanitation worker details.
Dashboard analytics
Vendor driver
No mapping for vendor driver.
API creation
Creation of API to provide access to unregistered sanitation worker database.
Vehicle trip
Driver will not be assigned.
Datamart report
Availability of data on Garima ID(s) tagged against each request.
Attribute
Type
Mandatory (Y/N)
Comments
Garima ID (8 digits)
BIGINT
Y
Assign sanitation worker to request along with vehicle screen.
Sanitation workers will be added at two levels
Driver
Helpers
Search by entering the Garima ID of the sanitation worker.
View of details fetched via API:
Name
Garima ID
Phone number.
It is mandatory to add at least 1 driver to the request.
Multiple helpers can be added, but it is not mandatory.
If a driver/helper is not available in the system, then there has to be an option to register a sanitation worker through provisional API provided by Garima and in response, we will get a provisional Garima ID.
A sanitation worker can be removed post selection by selecting the cross beside the sanitation worker name.
Attribute
Type
Mandatory (Y/N)
Comments
Last 4 digits of AADHAR
Number
Y
Validate only for numbers.
Name
Y
Free text field.
Phone number
Number
Y
Validated for 10 digits.
Date of birth
Date
Y
Gender
Array
Y
Male/Female/ Transgender.
Backend Table
As Is
With Garima
Action
Driver table
Driver details are currently stored in the driver table in FSM.
Driver details will be fetched from the Garima database.
Deactivate the driver table.
Driver vehicle table
Currently, drivers and vehicles are mapped in the driver vehicle table in FSM.
There will be no driver vehicle mapping. Each transaction will be assigned to sanitation workers/drivers from the frontend.
Deactivate the driver vehicle table.
Unregistered sanitation Workers
NA
All details of sanitation workers without a Garima ID entered manually need to be stored in a database.
Create a table to store the information.
A DSO assigns a sanitation worker who has not worked on the request.
Multiple sanitation workers service a request. Only a subset of them are assigned in the system.
Use Case | Chance of Occurrence* | Workaround |
A citizen from GP missed to select GP. | >10% |
|
A citizen from GP missed to select GP and has paid the full amount in advance. | >1% |
Municipal Services | Business Services | Core Services |
What? | How? | What? | How? | What? | How? |
FSM apply | Additional field to enter GP | location | Additional field- GP + impact on geotag. | Billing Service | Bill generates based on the amount entered. |
FSM calculator | Calculation based on the amount entered instead of auto-calculation based on property type, etc. | mdms service | New list of GPs tagged to the respective localities. | collections service | Demand generated based on the amount entered. |
Vendor | Check to see if the vendor is registered to serve the locality. | reports | New inputs from GPs tagged to localities. | Dashboard analytics | New inputs for analysis from GPs tagged to respective localities. |
Vehicle | Check to see if the vehicle is registered to serve the locality. |
|
|
|
|
Attribute | Type | Mandatory (Y/N) | Comments |
Gram Panchayat | Array | Y |
|
Field | Data Type | Mandatory (Y/N) | Comments |
Amount per trip | Numeric | N | Free text field. |
Total Amount | Numeric | N | Calculated based on the above field and the number of trips. |
Advance Amount | Numeric | Y | Minimum amount <= than the amount entered in the free text field. |
Field | Data type | Mandatory (Y/N) | Comments |
Amount per trip | Numeric | Y | Selection of any value apart from N/A must:
|
Total amount | Numeric | Y |
|
Balance amount
| Numeric
| Y
|
Example: Amount per trip updated to = Rs 2,000 in the Update Trips Screen.
|
TRUE NORTH Zero untreated waste | We must ensure that waste is collected and disposed of in the right method, at the right place and at the right time. |
SECONDARY Inclusive sanitation services |
Desludging service requests must be accessible to all citizens. |
Goal/Reason | Metric | Why we are tracking it |
Zero untreated waste | The number of requests received from GPs to # of households per GP. |
|
Zero untreated waste | The number of requests received from GPs reconciled at FSTP. | Due to the distance, chances of open dumping is high. This will help validate/invalidate the assumption. |
Inclusive sanitation services | The number of requests received from the GPs. | No major changes in ULB employee adoption. However, trends in the number of requests can be noted. |
Metric | Why we are tracking it |
The average SLA of GP per request | To understand the time taken to service GPs. Deep-dive to see root causes in case of large gaps or discrepancies. |
The average SLA of non-GP per request to the average SLA of GP per request | We need to enable admins to ensure that the citizens in GPs are receiving services in a timely manner, just like the non-GP citizens. |