25G - AGMT METER INFRASTRUCTURE - Laserfiche WebLink

Home Browse Search

Client Name: City of Santa Ana 1 AMI FEASIBILITY REPORT 13. MOMS must be capable of handling standard meter read files from various AMI vendors. 14. MDMS must have capability to display usage data in graphical and tabular formats 15. MOMS must have the capability to export data in standard file formats 16. MDMS should have the capability to aggregate data based on TOU (Time of Use) bins or customer rate class or any other future requirement for billing, rate design etc. 17. MDMS must provide data aggregation based on district metering or other criteria to calculate loss and for engineering planning and analysis 18. MDMS must provide capability for custom reports and queries 19. MDMS must be capable to support deduct and compound meters Customer Portal / Analytics The customer portal must: 1. Provide validated data from MDMS in hourly intervals 2. Display data in graphical and tabular formats 3. Allow customers to compare water use data from different periods 4. Support alerts (leakage, backflow etc.) and usage limits, sent as email, phone or text message 5. Allow customers the ability to download water usage and other data in standard data formats (PDF, MS Excel, flat files, CSV or other) 6. Be available on multiple devices (e.g., PCs, Laptops, Tablets, Smart Phones) 7. Maintain privacy and security of customer data. Customer verification and authentication must follow industry standards Optional preferences include: 1. Provide customers the choice to compare water usage against similar customers or similar predefined groups 2. Allow customers with multiple accounts to view usage at individual and aggregated level 3. Offer a single sign -on to the customers (same username and password as the customer account for the utility is preferable) 4. Allow customers to estimate water bill amounts BLACK & VEATCH I Appendix D. Functional Requirements for AMI 25G-189 71