Product Requirement Document (PRD)

Background

To ensure proper disposal of waste, the Swachh Bharat Mission has approved the building of deep row entrenchments for the disposal of sludge for upto three years. With this mandate, there are approximately 10k+ deep row entrenchments that now exist, and are usually unmanned. To confirm disposal to these legal unmanned dumping sites, there is a need for automated verification of disposal at these sites.

Introduction

India’s FSM ecosystem is made of highly interdependent parts, across the value chain of generation, containment, transport, treatment, and disposal/reuse. This means that there are different actors at each stage of the value chain whose behaviours and business models affect how well the next stage functions, creating a complex mesh of constraints that affect the effective functioning of the sanitation service delivery.

While the linear value chain gives a lucid frame to understand the ideal flow of faecal sludge, there are various points of friction between stakeholders that currently undermine the effectiveness of the sanitation value chain. Illegal dumping remains a challenge in regard to the waste value chain.

We want to improve the verifiability of the transport information on faecal sludge through the implementation of vehicle tracking to drive the following benefits:

1. Improved verification: The service enhances the verification process of the faecal sludge disposal. By accurately tracking the movement of vehicles carrying the sludge, it ensures that the sludge reaches its designated disposal site, providing transparency and accountability in the disposal process.

2. Removal of manual intervention to confirm disposal: The implementation of the vehicle tracking service removes the need for manual intervention to confirm the disposal of faecal sludge. Traditionally, manual methods involve physical confirmation by the treatment plant operator.

3. Identification of Illegal dumping: By closely monitoring the transportation of faecal sludge from the point of containment to disposal, the vehicle tracking service helps in minimising disposal in illegal sites. It facilitates identifying potential inefficiencies, route deviations, or incidents, allowing for prompt corrective actions.

The vehicle tracking service within DIGIT aims to capture real-time spatial data by tracking vehicles from their starting coordinates (longitude and latitude) to their destination point. This service helps in enhancing the credibility of service delivery by providing a reliable means to track and verify the transportation process. The vehicle tracking service can be seamlessly integrated with various service delivery operations, offering the flexibility to configure it for different purposes.

Future Use Cases Apart from the benefits mentioned above, the vehicle tracking functionality can be used to implement the following use cases in the future:

1. Proximity-based discovery: By helping service providers or customers identify the nearest available vehicles for transportation or disposal purposes.

2. Distance-based pricing: Leveraging the tracking data, the vehicle tracking service can support distance-based pricing models.

3. Understanding capacity and capacity utilisation of vehicles: By analysing the metrics around transportation such as average trip time, average distance traveled, number of trips completed per day, idle time, etc., one can arrive at the utilised and available capacity for transportation. Further, these can be used to arrive at the profitability of vendors in transportation.

Features

1. Assigning drivers to the trips: The ULB personnel can assign a driver when assigning the vehicle for a particular trip.

2. Employee form has been enhanced to add geo-location.

3. A standalone mobile application for the drivers: Drivers will be able to see the trips assigned to them with start and end trips provided. With this functionality, the driver can start the trip after reaching the citizen’s location, provide service, and end the trip after reaching the FSTP.

4. Enhancement to the application by introducing end trip: The vehicle tracking service can be leveraged to automate certain aspects of the disposal process.

   1. System Verified: The trip is closed automatically if the vehicle is near the geo-fenced area of the FSTP. In this case, the end type is updated as system verified.

   2. FSTP Verified: If the driver concludes the trip at a location that is not necessarily close to the FSTP, the FSTP staff will need to manually finalise the trip. In this case, the end type is updated as FSTP verified.

5. Defining illegal dumping spots: The vehicle tracking service can help the ULB personnel to identify and input these locations into the system. If a driver stops at one of these spots for an extended period , the system triggers an alert to notify the ULB of potential illegal dumping activity.

6. Alerts: On events where local authorities should be informed:

- Longer waiting of vehicles near farm lands, water sources, etc., could be a possible indication of illegal disposal.

- The popular open disposal spots as generally defined as prohibited zones and any desludging vehicles around those areas are also an indication of open disposal.

How Vehicle Tracking Will Be Integrated With DIGIT FSM:

Actors

Current Actors

Actor	Description
Citizen	A citizen can request for a desludging operation online. The user can check the status of the application online, make the payment for the service online, and post desludging, they can rate the quality of the service online.
ULB employee (Can be assigned roles as creator, collector, editor, report viewer, dashboard viewer, or admin)	A ULB official will act as a regulatory and management authority for the entire desludging process. He/she can receive the request from a citizen online or can create a request on behalf of the citizen online. When the request is received, the user can assign a desludging operator for a request. The official can also update the status of the request on behalf of the DSO after the service is completed at the site, and view the relevant reports.
Transportation vendors	The transportation vendor will receive the requests assigned to them, and update the status of the transaction after the collection of faecal sludge is complete.
Treatment plant operator	This user can view the current demand, that is, the list of planned desludging requests available in the system. He/she can update the vehicle log which enters the FSTP/STP every day.

Proposed Actors

As per the understanding on the field, collection and transportation services are provided by the sanitation workers (usually a driver plus helper). Given that the driver is operating the vehicle, it makes sense for us to add an additional actor in the workflow:

Actor	Description
Driver	A driver is responsible for pickup, and disposal of sludge.

Workflows:

Current workflow (Without vehicle tracking) :

Proposed workflow (With vehicle tracking) :

Actions by User Persona

Persona	Priority	Use Case
Driver	P0	Should be able to start and end the trip.
FSTPO	P0	Should be able to view if the vehicle has reached the FSTP or not via the inbox.
ULB	P0	Should be able to view the route followed by the vehicle and stoppage. They should also be able to view metrics such as movement time and stoppage time.
ULB	P0	Should get alerts for long stoppages, and stoppages near illegal dumping spots.

Assign Driver

The driver will be assigned to a request.

See flow diagram here

Start and End Trip

Trips will be started and ended by the driver using a mobile app.

See flow diagram here View Trip Details ULBs can currently view the applications. This needs to be enhanced with the following:

• Trip details need to be viewable along with status and route of the trip.

• Alerts need to be viewable if there has been an illegal stoppage on the trip.

• The ULB can deep-dive and view the route taken and the number of stops by the vehicle.

See flow diagram here

Mark Illegal Dumping Zones

See flow diagram here

Edit Illegal Dumping Zones

See flow diagram here

Users and Value bundles

Assumptions and Validations:

Serial number	Theme	Assumption
1	Customer persona	The drivers using the application are not digitally literate and need training before being able to use the application independently.
2	Device and services	The drivers using the mobile application must have internet connection to get the trip details in the application.
3	Start trip	The driver is required to click on “Start Trip” before commencing the desludging service.
4	End trip	The driver is expected to click on "End Trip" upon the completion of the desludging process at the FSTP.
6	Geo-tagging precision	The latitude-longitude added within the system are sufficiently accurate to pinpoint the exact locations.
9	Additional fields	All the non-mandatory fields must be taken care of during implementation. This must be done across all the flows.
10	Dropdown	If the field contains only one value, then it must be auto-populated by the system.

1 . Driver Login

Field	Data Type	Data Validation	Required (Y/N)	Comments
User Id	String	Min Length = 2 Max Length = 64	Y
Password	String	Min Length = 2 Max Length = 64	Y

2. Driver Home & Inbox

Field	Data Type	Data Validation	Required (Y/N)	Comments
Start Trip	Button		Y	The "Start Trip" button initiates the tracking and monitoring of the desludging service journey.
Route StartPoi	Text		Y	Captured when the driver starts the trip
End Trip	Button		Y	The "End Trip" button signifies the completion of the desludging service journey and finalizes tracking.
Route EndPoi	Text		Y	Captured when the driver ends the trip
Name	Text		Y	Auto-generated on the creation of trip
Trip ID	String		Y	Auto-generated on the creation of trip
Trip Status	Text		Y	Status of the trip
Vehicle Number	String		Y	Auto-generated on the creation of trip
Route ID	Text		Y	Predefined route id, which has the list of POIs for that the trip should follow
Pick Up Location	String		Y	Auto-generated on the creation of trip
Drop Location	String		Y	Auto-generated on the creation of trip
Date	Date		Y	Auto-generated on the creation of trip , Expected date of completion

3. View Applications: ULB

Field	Data Type	Data Validation	Required (Y/N)	Comments
Vehicle Number	Dropdown		Y	All the vehicle numbers in the registry should be shown in the dropdown
Vehicle Capacity	Numeric	View only	Y	Auto-populated based on what is selected while filling the application
Assign Driver	String		Y	Driver associated with the vehicle number to be shown in the dropdown
Possible Service Date	Date		Y	Expected date of completion
Trip Id	Text		Y
Trip Designated RoutId	Text		N
Trip Expected StartTime	Text		N
Trip Expected EndTime	Text		N
Trip CurrentStatus	Text		Y

4. Add Illegal Dumping Sites : ULB

Field	Data Type	Data Validation	Required (Y/N)	Comments
Site Name	Text	Max character - 256	Y	Name of the illegal dumping site
Site Type	Array	Single select	Y	The dropdown will be auto populated basis the list of possible dumping sites in the MDMS
Alert	Numeric	Min distance = 20m Max distance = 50-100 (TBD)	Y	Generate an alert when the vehicle is within a specified proximity.
LocationDetails	Array		Y	List of locations that are part of a POI. This can be a single LatLong or group of LatLongs (line, polygon)
locationDetails -> latitude	Decimal		Y
locationDetails -> longitude	Decimal		Y
alert	Array of Strings		N	One or more alert codes can be mapped to the point of interest. This is optional and can be set only in cases where the POI is related to some illegal dump yard etc
POI Id	Text		Y
POI Type	Array		Y
POI PositionPoint	Text		Y
POI PositionLine	Text		Y
POI PositionPolygon	Text		Y
POI Alert	Text		Y

Noun Verb Mapping

Entities	Actions
Create	Read	Search	Update	Delete
Add Point Location			X	X	X
Edit Existing Site	X		X
Trip			X	X	X
Anomalies	X		X	X	X

Detailed Scope

Use Case 1: Enhancing Verifiability of Information & Identifying Illegal Dumping Spots

Features

1. Capturing the geo-locations with timestamps of the driver at configurable frequency thresholds.

2. Creating geo-boundaries at particular spots earmarked as illegal dumping spots.

3. Defining anomalies based on rules, and sending alerts to the ULB employee when an anomaly is detected.

Users

ULB employee: To track the locations and cross-verify the alerts received.

Driver: Responsible for pickup and completing disposal, and ensuring proper sludge disposal.

Detailed process diagram for anomaly detection

Description

Driver

After the driver is assigned, they proceed to the pickup location. Before providing any services, the driver must initiate the trip by selecting the 'Start' option. After the service is complete, and the disposal is done, the driver can choose to 'End' the trip. If the end trip is within the geo-fenced area of an FSTP, then the trip automatically gets closed. However, if the driver tries to end the trip outside the FSTP geo-fence area, the FSTPO has to confirm that the disposal is successful. Simultaneously, the DSO gets a notification that the respective trip has ended.

In cases where the actions are performed offline, the system records the timestamps of both the 'Start' and 'End' trips, and the transportation to ensure accurate tracking and documentation.

Tracking Transportation

By utilising the tracking feature, assigned vehicles can be monitored for respective applications. If a vehicle halts near any marked illegal dumping sites on the map or for a duration exceeding the configurable threshold, an alert is promptly sent to the DSO, ensuring timely awareness of potential unauthorised dumping activities.

• Notifications and alerts: The tracking system is configured to generate alerts within the application.

• A new "Trip Details" table is introduced which displays the number of alerts generated during the trip, the trips start and end times, the end type, and offers a link to view the route taken by the driver.

1. Upon initiating the trip, the driver's geo-locations are continuously recorded at a configurable threshold, enabling the DSO or a ULB employee to track each vehicle's movements. If the driver halts at spots apart from the disposal site for a duration exceeding a configurable threshold, the DSO receives an alert. The system records alerts in real-time when the driver is online, while geo-locations are updated once the driver reconnects, generating corresponding alerts for offline periods.

2. The ULB has a centralised inbox to effectively monitor and track the drivers' trips. The inbox shows the alerts raised per trip respective to the application.

3. The application details page needs to be enhanced for the following:

   1. Geo-location to be added on the employee form.

   2. Display driver details.

   3. View route details: This shows the ULB employee a map showing route taken by driver and points of stoppages along with time of stoppage.

      1. Display a map view showing the stops (exceeding a certain time) made during the trip.

      2. Vehicle route: Utilise the tracked geo-location coordinates to generate and display the vehicle's route on the map with respect to each trip.

4. Illegal dumping zones:

   1. ULB defined: ULB personnel/admin can define illegal dumping zones.

Clicking on illegal dumping sites on menu options will allow users to see the illegal dumping sites in the ULB. If no sites are present, then user will only see the option to “Add new site”.

1. Clicking on “Add new site” will allow users to create a new illegal dumping site as an anomaly object.

2. User will need to add following details to create an anomaly object:

   1. Site name - Name of the site (For example, Dhenkanal Lake).

   2. Location category - The type of geographical body (For example, Lake/Road/Highway/Bridge/Old building/Open field/Rainwater pipe, etc.).

   3. Buffer area (in metres) (Distance from these coordinates which can considered an anomaly).

   4. Map UI

      1. For Polygon - (For example, a pond):

         1. Upto 20 points are allowed on the screen.

         2. Each point will have a cross icon.

         3. If two points are already added. User has to remove one point to add a new point.

         4. If a buffer is added. Show a corresponding figure of ‘X’ metres buffer perpendicular to line in all directions, with highlighted colour (even before saving), so that the user is clearly aware of the boundaries he/she is making.

         5. Polygon should be a closed figure.

3. Once saved, the coordinates are saved in the anomaly object.

4. To edit or make changes to an illegal dumping site click on an anomaly object from the list of objects in the menu.

   1. In the next screen, click on actions. Actions will open edit and delete.

   2. Clicking on edit will make the menu editable (until then it will be non-editable).

   3. Users are allowed to edit all options. There is no restriction.

   4. Buttons will be shown as “Save Changes” and 'Cancel'.

   5. Clicking on save changes will save all the changes made to the anomaly object.

   6. Clicking on cancel will take the user to the previous screen.

5. Alerts on Illegal dumping:

   1. If any vehicle is found stopping in these locations, including buffer areas, for more than 'X' minutes, should send an alert immediately. Who to send:

      1. ULB employee - He/she will receive the alerts raised against the trip ID.

Acceptance Criteria

• Alerts should be generated for a ULB employee when vehicles are stationary near the marked illegal dumping spots for a configurable duration.

• The system should provide the ability for the DSO to add illegal dumping zones, allowing flexibility in response to changing circumstances.

Out of Scope

1. There is no other activity tracking of disposal vehicles other than the duration between the start and end trips.

2. No verification of which vehicle is being tracked. For example, if the mobile of the disposal truck driver is given to a two-wheeler driver, then the geo-location of the two-wheeler driver is recorded.

3. No verification of the disposal truck driver for example the registered driver and the actual disposal driver might be different.

Use Case 2: Automation of Disposal and Completion of Requests:

Features

1. Capturing the location of the vehicle at the disposal site.

2. Verification of whether the vehicle location is within the geo-fenced boundary of the disposal site.

3. Automated confirmation of the disposal based on positive verification.

Users

Admin portal: Geo-fencing data need to be added at the backend in the MDMS of disposal spots.

Driver: Responsible for completing disposal requests and ensuring proper sludge disposal.

Workflow

Description

1. The vehicle tracking service in FSM helps to automate the disposal process requests in legal dumping sites. By utilising geo-tagging and proximity data, the system can verify if the driver has disposed off waste at the designated disposal spot.

2. Admin functionality (no UI required):

   1. Allows administrators to view, add, delete, and modify the MDMS at the backend.

   2. Define the proximity radius for verification (for example, 50 meters) at the backend.

3. Driver:

   1. When a driver is completing a disposal request, the system captures their geo-tags (longitude and latitude) at the time of disposal. The system compares the driver's geo-tags with the predefined disposal spots set by the admin. There are two possibilities:

      1. If the driver's geo-tags are within the specified proximity radius (for example, 50 metres) of the disposal spot, the disposal is considered system verified, then the system automatically closes the disposal request, marking it as system verified.

Acceptance Criteria

1. The driver should be able to start the trip, and the system should capture and record the geo-location coordinates (longitude and latitude) at the start of the trip.

2. At a specific configurable frequency (for example, every 2 minutes; this is configurable), the driver's geo-location coordinates should be recorded and stored by the system.

3. The system compares driver geo-tags with the predefined disposal spots.

4. Upon reaching the plant, the driver should be able to end the disposal request from his/her mobile phone and the system should capture the geo-location coordinates at the time of closure.

5. Automated closure at the disposal location:

   1. If the driver's geo-location coordinates indicate that they are within the geo-fenced area of an FSTP, the disposal request should be automatically closed and marked as system verified.

   2. The closure should trigger an automated notification or confirmation to the driver and the admin.

Out of Scope

1. If the driver ends the trip outside a geo-fenced area, the driver uploads a picture and the FSTPO is required to verify the end of trip from their end.

2. Alert for non-closure at the legal disposal site:

   1. If the distance between the driver's coordinates at closure and the designated disposal location is greater than the defined threshold (for example, 50 meters), an alert should be generated.

3. There is no other activity tracking of disposal vehicles other than the duration between the start and the end trips.

4. If the driver goes offline during the trip, the driver application should continue recording the geo-location coordinates at the predefined frequency. The recorded coordinates should be stored locally on the device until an internet connection is available. Once the driver's device regains internet connectivity, the recorded geo-location coordinates should be synced with the server or the backend system.

Design

Find the mock-ups below:

Driver Login Screen After a specific request is generated, the ULB employee assigns a driver, who is then prompted with a login screen. The driver receives a user ID and password from the ULB employee, and has to select the respective city from the dropdown, enabling access to the system. The back button takes the user to the language selection screen. Upon clicking the "Forgot Password" hyperlink, the screen displays a message instructing users to get in touch with the ULB in case they have forgotten their password.
Driver Home & Inbox Upon the driver's successful login, their inbox interface will present a layout featuring both assigned trips and completed ones. The hamburger menu offers options for navigation: Home: This option displays the assigned trips, serving as the central hub for trip management. Language: Drivers have the flexibility to select their preferred language for a more convenient experience. Logout: This option allows the driver to exit the system.
Upon successfully login, the driver gains access to an overview of all assigned trips. The key features of this interface include: Efficient trip search: The inclusion of a search bar empowers the driver to easily locate a specific trip using the applicant’s name and contact number. Organised trip categorisation: The screen presents two distinct tabs: - "In progress" tab: This section shows trips that are pending initiation and assignment. - 'Completed' tab: Here, the driver can view a compiled list of the completed trips.
Upon selecting the "View Details" hyperlink, the driver can see the information of the applicant, including both the pickup location and the designated drop-off point (referred to as the "FSTP plant"). The "Start Trip” button triggers the commencement of the desludging service's tracking and monitoring process.
Upon clicking the "Start Trip" button, the system displays a warning: “Start the trip only after reaching the pickup location. Have you reached the applicant location?”
When the driver clicks on 'Yes', a toast message - “Trip Started Successfully” - is displayed.
After the trip has been initiated and the driver has concluded the desludging process, the driver proceeds to the provided FSTP (to finalise the desludging task and complete the request). After successful completion of the desludging process in the FSTP, the driver has to click on the "End Trip" button to conclude and finalise the request.
Upon selecting the "End Trip" button, the system shows a warning message: "Are you sure you want to end the trip for Locality 1...?" Following the acknowledgment of this warning, the trip reaches its completion status. When the driver clicks on 'Yes', a toast message - “Trip Ended Successfully” - is displayed.
View Applications: ULB The ULB employee can access the trip details and review any raised alerts. Upon selecting the "View Route" option from the new table “Trip Details”, the path taken by the driver is shown. The trip details table also shows- Date: Start date of the trip. Start time: Start time of the trip. End time: End time of the trip. Alerts: The number of alerts raised for the respective trips. Route: Shows the route taken by the driver, which also shows the "Stop Locations", "Alert Locations", "Pickup and End Location".
Add Illegal Dumping Sites: ULB An additional feature has been introduced under the "Faecal Sludge" section, labeled as "Vehicle Tracking". Upon clicking on this, the page is redirected to options such as ‘Alerts’ and "Illegal Dumping Sites". Alerts are set up as an inbox that showcases the application ID, the corresponding vehicle, and the type of generated alert. Upon clicking on illegal dumping sites, the user can add the pint location and define the spots.
Add Point Location By clicking on "Add Point Location", the ULB employee can add a new dumping site. They can then proceed to furnish all the essential particulars, including the Site Name, Site Type, and the distance threshold for triggering an alert when within proximity.

Success Metrics

Goal	How will we know vehicle tracking is successful
Introducing end type - System Verified - FSTP Verified	The percentage reduction in manual intervention required for status updates. Count of applications closed with end type - System verified.
Mobile application for drivers	Driver engagement. The number of trips initiated (in-progress) and completed. The number of trips started by the driver. The number of trips ended by the driver.
Identifying illegal dumping spots	The percentage reduction in unauthorised sludge disposal incidents through the intervention of alerts.
Alerting	The number of alerts triggered per application for longer waiting near marked illegal dumping sites.

Future Roadmap

1. Users to be able to delete and edit the added illegal dumping.

2. Include the process of adding point locations for a polyline, creating a line through the user interface.

3. Incorporate additional alerts for prolonged stops at regular sites when sludge is collected for a duration exceeding 'X' minutes.

4. System generated illegal dumping spots: These are identified based on multiple drivers being stationary at the same location for a predetermined period. The DSO or ULB employee has the authority to designate or remove such zones, enhancing the system's ability to pinpoint areas prone to unauthorised waste disposal.

5. Bringing in the safety measures screen, and making it mandatory in the driver application.

6. Explore on advanced analytics for vehicle tracking, including metrics such as the number of trip requests, average distance covered, and the number of closed applications, with a focus on distinguishing between FSTP verified and system verified cases.