Waterloo Call observation

Nilesh 

1. Import holidays - ask by the client - not priority -> this is done. - Customer is asking can i import the holiday list
2. Service area - while demoing people were asking a lot of questions which tends to me that they were quite confused with it.
3. Plans and tariff
4. 1. Tariff according to water Pipes
   2. Tariff according to consumer categories
4. Scenarios for plans
5. Can we connect sql for data migration
6. Esri Integration required - suggested open API by client for vehicle tracking for fuels and other things.
7. 3-4 sizes of trash cans, billing based on the size. Routes required for collecting cans
8. Discover - how we will process 3000 data lines for cans when it is misplaced.
9. RFID on the cans, can be an entity
10. The customer asks when the trash cans will be picked then the client doesn't have an answer as of now.
11. The consumer account history should be available for the consumer who is moving from one location to another location
12. How can we identify the customer who has applied for a NSC, whether the customer is old with an outstanding payment history or a new customer
13. Creating a Payment screen is confusing, and needs to be revamped.
14. GL code wise payment, payments can be split
15.  One payment can be marked for multiple bills and services
16. Paisa lo and attach to the account
17. GL code - payment prioritisation rules - should be built - rules based
18. Account number given after application accepted.
19. Payment should be taken after accepting the application.
20. UI in communication not similar to given requirement
21. Route and read cycle creation UI is bad - observations given to ajinkya - Filters can be added more - select premise and meters as well
22. Readings are not visible correctly, confusing Ui, whitespace, data issues. Add contextual help, guidelines. Revamped UI - all detail views in MX should be revamped for ui and ux.