CORE & MAIN LP (#2027021) - Laserfiche WebLink

RFP-2 – Scope of Work RFP# PWD 25.604 City of Pleasanton, CA RFP-2 | Page 31 Internal Use Only L. The Contractor shall ensure that the AMI Software allows the Utility User to review and close or resolve the status codes such that a resolved code does not continue to show up in the display or report. 2.5.2.9 AMI Network Monitoring The Contractor shall ensure that the AMI Software solution allows City Users to view details of the Data Collection Equipment and their current status. It should provide a summary of the Data Collection Equipment performance (battery, communication to headend software, devices being heard, etc.). 2.5.2.10 Event Management The Contractor shall ensure that the AMI Software solution allows for tracking and prioritizing different types of meter and AMI events either at the software level or using the radio transmitter. Events may include various types of maintenance, high consumption, cut wire, zero consumption, non-numeric readings, continuous consumption, non-zero consumption on fire line meters, and conservation initiatives (consumption restrictions, letters, low flow device installations, meter replacements, etc.). The City should be able to prioritize events that allow more serious events to be resolved sooner. The Contractor shall ensure that the meter event handler will allow the City to: A.Filter all meter events by multiple criteria including the type of event, severity of the event, event type, or status of a device. B.Create event groups. C.Create roles for Users. D.Send events to a person of a specified group. 2.5.2.11 Property Side Leak Detection The Contractor shall ensure that the system or software allows for User-defined continuous or high consumption leaks to be flagged. The size of the leak should be User definable and activated if the water meter has registered a volume above a programmable threshold each hour for 24 consecutive hours or as defined by the user, if available. 2.5.3.Data Interfaces The Contractor shall define all data interfaces that will be required for all software and systems. The Contractor shall be responsible for planning, developing, documenting, and testing the proposed AMI Software (AMI headend software, MDM) side of the data interface. The City will be responsible for the existing system side of the data interface. Testing of the interface will be performed jointly. The Contractor shall work within the City’s interface and testing approach as described in Project Overview section 1.7 Integration and Testing Process. 2.5.3.1 Data Transfer File Type The AMI Software may use flat file interfaces for billing purposes. The AMI headend and Meter Data Management software shall be either a flat file, a Real-time Application Programming Interface (API) or a REST API of a format agreed to during the start up to transfer data between systems. Costs for the API shall be included in the support and maintenance or SaaS fees. If an API is not available, the Contractor should specify when an API will be made available. Docusign Envelope ID: 6AD75F50-8A33-85A5-8039-9E3E1257A838Docusign Envelope ID: 177582DA-4F1C-8834-813C-BC4FD03AA45E