Garima

Scope and Specifications

Introduction

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 also 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.

About UMC

The Urban Management Centre is a non-profit organisation with a mission to “Make Cities Work for Everyone”. Since 1997, it has strengthened 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.

About Garima

The Housing and Urban Development Department, Odisha, launched the Garima scheme in 2020. It is a one-of-its-kind statewide scheme 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:

1. Provision of ULB/DSO to assign one or more sanitation workers to each request:

a. Sanitation workers will be made available via integration with Garima database via API in the workflow.

b. Since the Garima ID may not be well known to the ULB/DSO, a provision to receive information is to be made available via the entry of a phone number.

c. Preview details of the selected sanitation worker for confirmation.

2. Capture sanitation worker details if a sanitation worker is not available in the Garima database.

3. Provide access to transactional data of requests served by sanitation workers by API to the UMC.

4. Provide access to the database of unregistered sanitation workers to the UMC via API.

5. Provide access to citizen feedback to the UMC via API.

Detailed Solution:

Along with assigning a vehicle, the DSO will assign sanitation workers to a request. The sanitation workers will be assigned either by entering the Garima ID or the phone number of the sanitation worker. If the Garima ID/phone number exists in the database, details of the sanitation worker, that is, name, phone number, Garima ID, and photograph to be displayed on the screen for the DSO to confirm. In case the Garima ID/phone number does not exist, the DSO will manually enter sanitation worker details (name, phone number, address). 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 to UMC via APIs:

• Transactional data of requests served by sanitation workers.

• Database of unregistered sanitation workers.

• Citizen feedback.

Workflow with Garima Integration:

What changes would affect which municipal, business and core services?

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.

Specifications

Updating Application | DSO in Progress

a. Adding Sanitation Worker

Attribute	Type	Mandatory (Y/N)	Comments
Garima ID (8 digits)/Phone number	BIGINT	Y	Post assigning a vehicle, the “Take Action” button will show an option to assign a sanitation worker. Search by entering the Garima ID and the phone number of the sanitation worker. View of details fetched via API: - Name - Garima ID - Phone number. - Photograph Confirm the sanitation worker. It is mandatory to add at least one sanitation worker to a request. The edit of sanitation worker/workers is possible by deleting a sanitation worker.

b. Registering a New Sanitation Worker

Attribute	Type	Mandatory (Y/N)	Comments
Name		Y	Free text field
Phone number	Number	Y	Validated for 10 digits
Pincode	Number	N	Validate
City		Y	Drop down
Locality		Y	Dropdown
Mohalla		N	Free text

Change in Backend

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.

Design

Find the mock-ups below:

The DSO assigns a sanitation worker after assigning a vehicle.

The DSO searches for a sanitation worker using the Garima ID or the mobile number. The available matches are displayed. Once added, they are displayed on the table.

If a sanitation worker is not available, details of the new sanitation worker is added.

Sanitation worker details are displayed in the application.

Validate Garima ID API BMS

URL: http://34.93.46.110:8008/api/v1/validgarimaid

Method: POST

Headers

Content-Type	application/json
Authkey	PROVIDED BY TEAM
Accept	application/json

Parameters

Name	Description
garima_id	Garima ID to check against

Example Body

{
	“garima_id”: “XXXXXXXX”
}

Response Sample
{
    "status": 1,
    "responsedata": [
        {
            "status": 1,
            "message": "valid garimaid",
            "details": {
                "general_info": {
                    "id": 3,
                    "ResponseID": "Responseid of worker",
                    "TransactionID": "45a9942f-fbb0-4c4c-a422-18082a6f0577",
                    "State": "Odisha",
                    "StateCODE": "S21",
                    "District": "Khorda",
                    "DistrictCODE": "S21BHUB01",
                    "SelectCITY": "Bhubaneswar",
                    "Consent": “User Consent”,
                    "WorkerNAME": "Name of worker",
                    "Gender": "Male",
                    "OlderThan18": "Yes",
                    "Age": 38,
                    "UrbanORPeri_urban": "Urban",
                    "BlockName": null,
                    "PanchayatNAME": null,
                    "WardNumber": "53",
                    "HouseLocation": "Other",
                    "HouseLocation_specify": "Kedarpalli basti",
                    "SettlementName": "Kedarpall bapuji nagar Ashok nagar",
                    "HouseNumber": "Kedarpalli basti bapuji nagar road",
                    "AtResidence": "Yes",
                    "GeoLocation": "(accuracy : 1.26  latitude : 20.2549917  longitude : 85.83313  )",
                    "MobileNUMBER": "Mobile Number of worker",
                    "MaritalSTATUS": "Married",
                    "Education": null, 
                    "valid_status": "1",
                    "garima_id": "Garima ID of user",
                    "jobcategory": “Job Categories of worker"
                }
            }
        }
    ],
    "message": " "

Risks/Limitations

• 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 put in 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.

Out of Scope

The above solution should cover the majority of Garima use cases, but there are scenarios (edge cases) that deviate from the options:

Use Cases

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.