Laserfiche WebLink
70 <br />AMI Feasibility Report I Client Name: City of Santa Ana <br />4. AMI headend system must be capable of managing and monitoring all network devices for <br />routine maintenance/replacement or identifying issues (e.g. monitoring status of backup <br />battery in Data collector or assigning replacement of battery after the normal life is over) <br />5. AMI headend system must be capable of integration with other utility system like CIS, GIS, <br />SCADA, MDMS, customer portal etc. through standard integration interfaces <br />6. AMI headend system will manage scheduled reads for all meters on a daily basis and also <br />provide the capability to read any meter on demand with very low latency (real time) <br />7. AMI headend system must be able to collect alarms or events transmitted by the MTU and <br />generate reports <br />8. AMI headend system must be capable of providing data in standard meter read file formats (as <br />specified by City in addition to flat file, XML etc.) <br />9. Time synchronization between AMI headend and field devices (MTU, DCU, repeaters etc.) must <br />be maintained to avoid errors in meter read timestamps <br />10. It is preferable to have mapping capability in the AMI HES to display meter/MTU, data <br />collectors, repeaters and network status details on the map <br />MDMS <br />In case AMI HES can store meter read data and provide hosting services to City, then MDMS is not <br />required (in this case AMI vendor should specify if the system can do VEE on data or not). However, <br />if the AMI vendor can provide AMI HES and MDMS hosted service for a nominal charge, then it <br />would be an advantage to City. In this case, City can bring data from all pilots in this MDMS and <br />conduct evaluation. City needs a place to store the data that would be collected by PG&E pilot. This <br />can be a small database or MDMS. <br />1. MDMS will process the meter reads received from the AMI Headend system and conduct VEE as <br />per the rules. Cleansed data would be stored in the MDMS for pilot evaluation <br />2. In case, data is manually edited or estimated data is replaced by actual reads (received at a later <br />date), all versions of data must be maintained by MDMS <br />3. Billing data provided by MDMS to CIS should be clearly identified from the various data <br />versions available <br />4. MDMS will handle the meter history related to the customer account <br />S. MDMS must provide leakage, tamper/theft detection, meter alarms (like backflow etc.) <br />obtained from the AMI HES in reports <br />6. MDMS will have the capability to identify High/low usage or abnormal usage (usage in a vacant <br />property etc.) and generate reports <br />7. MDMS will identify meters not reporting reads <br />8. MDMS will identify meters registering zero usage <br />9. MDMS will be capable of meeting billing requirements from the CIS/billing system <br />10. MDMS will identify meters/accounts which do not have the bill ready data available in the <br />billing window and generate a report of such meters/accounts <br />11. MDMS will provide manual (graphical if possible) tools for data editing in addition to the <br />automated estimation algorithms <br />12. Auditing capability must be provided to keep track of users editing the data <br />25G-188 <br />