CITY COUNCIL REGLAR MEETING AGENDA PACKET 6-16-26

RFP-2 – Scope of Work RFP# PWD 25.604 City of Pleasanton, CA RFP-2 | Page 28 SLA credits shall not apply to unavailability or degraded performance caused by: (i) acts of God, fire, flood, earthquake, or other natural disasters; (ii) acts of war, terrorism, or civil unrest; (iii) acts or omissions of the City or its agents; (iv) failure of the broader public internet backbone not specific to Kamstrup's infrastructure or subcontractors; or (v) orders or actions of any governmental or regulatory authority. For the avoidance of doubt, failures of Kamstrup's hosting, cloud, CDN, authentication, database, or other service delivery infrastructure — whether operated directly or through subcontractors — shall not constitute Force Majeure and shall remain subject to the SLA. Kamstrup shall at all times maintain compliance with applicable federal, state, and local laws and regulations, including those obligations specific to the City set forth in Section 20. A change in applicable law shall not excuse Kamstrup from meeting its SLA obligations; provided, however, that if compliance with a specific new legal mandate makes a particular SLA metric technically impossible to achieve, the parties shall negotiate in good faith a revised metric within thirty (30) days of such mandate taking effect. 2.4.2.3 QA Test System The Contractor’s software shall include a QA Test system. The City shall provide four weeks’ notice of when a QA test environment shall be configured and available to the City. The Contractor shall provide a QA Test system until IUAT and FUAT are approved by the City. 2.4.2.4 Security The Contractor shall ensure the security of the application and shall prevent unauthorized access to the City’s information. The application shall support enterprise SSO as described in 2.4.1.3 Identity and Single Sign-on, above. Authentication and authorization events (success, failure, elevation) must be logged and exportable. 2.5. AMI Software 2.5.1. General Requirements 2.5.1.1 AMI Software Definition The Contractor shall ensure that the AMI Software is configured by the Contractor to meet the required functionality. At a minimum, the Contractor shall ensure that the application(s) will include both AMI headend and Meter Data Management software. 2.5.1.2 User Definition The Contractor shall ensure that the AMI Software solution allows for different types of Users with varying levels of system access. At a minimum, the Contractor shall ensure the software allows access to the following types of Users: A. City Administrator: City employee(s) who have administrative access to the AMI Software solution with the authority to set up Users and make system-wide changes. B. City User: City or project consultant personnel who access the AMI Software solutions for the purpose of monitoring various AMI radio transmitters, data collectors, and running various consumption reports. 2.5.1.3 Tyler Munis Customer Information System (CIS) Data The Contractor shall ensure that the AMI Software solution shall store and display key CIS data associated with the service address, AMI radio transmitter, and meter. At a minimum, the Contractor shall ensure that the following CIS data is incorporated into the AMI Software solution: A. Account number Page 236 of 443