Data templates for data collection

The data templates contains Annexures which will be provided by the Program Team.

  • Annexure -1 : ULB and FSTP data.

  • Annexure -2 : Cesspool Vehicles

  • Annexure -3 : Slum Within ULB

  • Annexure -4 : Zero Pricing Property

  • Annexure -5 : GP Tagging and Pricing

  1. Annexure -1 : ULB and FSTP data This Annexure contains the names and contact details provided for -

    FSM Executive(Sl. No. A6) : CREATOR, COLLECTOR, EDITOR, DASHBOARD VIEWER, FSSM REGISTRY

    FSM TRP(Sl. No. B7) : SUBMIT/DECLINE TRIPS, ADD VEHICLE LOG

    Sl. No. A1 - A4 : ULB Details added in tenant/tenants.json file in mdms

    Sl. No. B1 - B6 : FSTP Details added in FSM/FSTPPlantInfo.json file in mdms

  1. Annexure -2 : Cesspool Vehicles

The Contractor Details are the DSO/Vendor/Cesspool Operator details can be added from vendor api or FSM Registery to add dso in the portal.The driver and vehicle is assigned to the dso.

Vehicle Make,Model and Vehicle Tank capacity is added in MDMS under VehicleMakeModel.json file within Vehicle folder in mdms-repo.

According to Tank Capacity,Property Type,Sub-property Type and Slums,the pricing is defined in billing-slab.

  1. Annexure -3 : Slum Within ULB The ULB can configure zero pricing for slums at a ULB level - all applications raised from slums would be required to pay zero application fees When creating an application, the default Slum Name is set to 'NONE'. If the user resides in a slum area, they have the option to select a specific Slum Name as follows:

    1. Open the Septic tank emptying request.

    2. In the 'Slum Name' field, you will find 'NONE' as the default value.

    3. If you live in a slum area, click on the 'Slum Name' field to open a dropdown menu.

    4. From the dropdown menu, select your specific slum area from the available options.

    By selecting the appropriate slum name, you can accurately specify your residential location within the application.

The slum details are added in specific ulb folder(anandapur/FSM/Slum.json).

  1. Annexure -4 : Zero Pricing Property In Zero Pricing Property,ULB can opt for zero-price application based on some criteria(like slum, property, sub-property, capacity etc.) which is configurable in MDMS & billing_slab table .In case of zero-pricing, no demand will be generated and collection step will get skipped.

    Eg. For Institutional.Temple,the price will be 0.

  1. Annexure -5 : GP Tagging and Pricing When creating a new application, users can choose between local municipalities or urban supported villages. Based on their choice, they can select either a locality/mohalla or a Gram Panchayat (GP) area from the respective dropdown list. If a ULB employee selects GP, they can manually input a trip amount based on offline calculations, instead of using the auto-calculated amount available for urban areas. ULB employees and DSO Operation personnel should also be able to edit the number of trips, and the final amount must be a multiple of the initial amount entered in the application based on the number of trips.

The data related to Gram Panchayat are added in mdms under specific ulb folder(Example. anandapur/egov-location/boundary-data.json to show in the ui.

Last updated

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Change request #103: Taniya's Nov 8 changes