Skip to main content

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 -
    • no need of holiday import as they are less and can be added manually.
  2. Service area - nilesh said - while giving a demo people were asking a lot of questions which tends to me that they were quite confused with it.- product need to think on it how we can make it easy to understand to the client
  3. Plans and tariff - product need to think how can we fit this in current system
    1. Tariff according to water Pipes
    2. Tariff according to consumer categories
  5. Scenarios for plans - we are workig on it - will get the timeline ready
  6. Can we connect sql for data migration? - it was a question ask by the client to Nilesh
  7. Esri Integration required - suggested open API by client for vehicle tracking for fuels and other things - product need to think on this.
  8. 3-4 sizes of trash cans, billing based on the size. Routes required for collecting cans - We can fit it in the current system
    • Utility Service: Waste Management
      • Rate Type: Fixed Rate
      • Rate Name: Weekly Pickup (Container ≤ 120L) - size wise
      • Base Rate: $32.00
  9. Discover - how we will process 3000 data lines for cans when it is misplaced - Product need to think how we will solve this in current platform or we need to improvise accordingly
  10. RFID on the cans, can be an entity - product need to think how we can use the RFID as an entity to tag with consumer account
  11. The customer asks when the trash cans will be picked then the client doesn't have an answer as of now - Product need to think about this problem which is faced by the client, how can this be address
  12. The consumer account history should be available for the consumer who is moving from one location to another location - this was the requirment given ad ask from the client to Nilesh - product need to think on it
  13. 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 - this problem was given by nilesh in the call - product need to thik on this
  14. Creating a Payment screen is confusing, and needs to be revamped - suggested by nilesh in the call - product need to think on it
  15. GL code wise payment, payments can be split - In the call nilesh has ask to think on it, how it will be working in the system
  16.  One payment can be marked for multiple bills and services - this is the scenario ask by nilesh in the call. - right now its not posible in the curret system.
  17. Paisa lo and attach to the account - Nilesh said how if the customer is on the window and he wants to pay , how the backoffice user will record the payment on the right consumer account without knowing the Account number.
  18. GL code - payment prioritisation rules - should be built - rules based - Nilesh ask this to be implemeted in the system
  19. Account number given after application accepted - ask by Nilesh - product eed to think on it.
  20. Payment should be taken after accepting the application. - suggested by nilesh - product eed to think on it
  21. UI in communication not similar to given requirement - Told by nilesh - product need to review the latest UI
  22. Route and read cycle creation UI is bad - observations given to ajinkya said by nilesh - Filters can be added more - select premise and meters as well - suggested by Nilesh - product need to think on it
  23. 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. - said by Nilesh in the call.
No Comments
Back to top