Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Document Version Control

Name

Publish Date

Author

Riddhi Kalaria

15.03.2023

Version

FSM v1.3 (Bundled with DIGIT 2.8)

 

Revision

 

 

Overview

FSM v1.3 release supports Advance payment and Zero pricing payment for the citizens and the ULBs. Further, the product now supports adding, editing, disabling and deleting a vendor, vehicle and a driver in the FSM Registry. A vendor can be assigned any vehicle or a driver.

Release Highlights

  • Advance payment functionality for the citizens and the ULBs

  • Zero Pricing payment functionality for the citizens and the ULBs

  • Vendor, Vehicle and Driver addition, modification, and deletion in the FSM registry

  • Assignment of a vehicle or a driver to a vendor

  • Enabling and disabling of vendor, vehicle and driver

Release Features

Key Features

Description

Advance payment functionality for the citizens and the ULBs

User can make partial payments. The amount for the partial payment is fixed by the ULBs

ULBs need to fix the partial payment criteria from the MDMS

Zero Pricing payment functionality for the citizens and the ULBs

User can opt for zero pricing payments which is fixed by the ULBs

ULBs need to fix the zero pricing payment criteria from the MDMS

Zero pricing is set for all slums, property and sub-property type mapping

Vendor, Vehicle and Driver in the FSM Registry

New UI for Vendor, Vehicle, Driver tab

Admin can create, edit and delete any vendor, vehicle or driver

Admin can assign any vehicle or driver to any vendor

Admin can disable or enable any vendor, vehicle or driver

 

Enhancements

Features

Description

 

 

 Unrestricted assignment of service requests to a single vehicle 

ULB employee flow

Multiple service requests assignment to same DSO

Multiple service requests assignment to same vehicle

Capability to close multiple service requests assigned to the same vehicle in randomized order.

Vehicle logging at FSTP decoupled from FSM module

Logging the service request the vehicle is fulfilling from the FSM module in TPMS. 

Vehicle log:

  1. In and out time 

  2. Waste deposited

  3. Additional information

  4. Attachments

Logging the service request the vehicle is fulfilling is made outside the FSM module in TPMS.

Vehicle log:

  1. Vehicle Number

  2. DSO name

  3. Locality the vehicle is servicing

  4. In and out time 

  5. Waste deposited

  6. Additional information

  7. Attachments

Other

  1. Display of photos added by ULB employee/DSO while closing request in the application in the ULB interface.

  2. Date range search of applications

Upcoming Release Features

  • FSM V1.4

Note:

  1. Vehicle log captured at FSTP for service requests outside of FSM module vehicles will not be reflected in the current dashboard and will be incorporated in the FSM Dashboards release.

  2. During updation of multiple trips for different service requests, the system cannot perform this activity within seconds and the user may encounter an error. This will be resolved if they refresh and try to update the trips again.

Doc Links

Description

FSTP- User Manual

Revamp of the FSTP UI: This will now act as a stand alone module where vehicles entering the FSTP can be logged in the system irrespective of servicing a request from FSM module.

ULB Employee- User Manual

The overall process remains the same. Now we have the option to open multiple applications and assign the same vehicle to them.

  • No labels