CORE & MAIN LP (#2027021) - Laserfiche WebLink

RFP-2 – Scope of Work RFP# PWD 25.604 City of Pleasanton, CA RFP-2 | Page 9 Internal Use Only 1.3.3.3 AMI Software to Smart Energy Water (SEW) Customer Portal The Contractor shall establish a near real-time API interface between the AMI software and the City’s SEW customer portal. The Contractor shall work with the City’s selected CEP application provider to develop a data Interface between the AMI Software and the SEW portal. This shall include business requirements meetings, development of the Interface and support of the Interface testing. The interface must support regular updates of hourly consumption data. 1.3.4.Type of Data Transfer The Contractor shall support both secure file and API data transfers, with preference for the use of APIs, where feasible. File format will be defined during the project start-up phase. SFTP with encryption in transit (SSH-based) is adequate for batch data transfer. The City requires that SFTP connections use key-based authentication and not password-only. All file transfers shall meet minimum encryption standards (e.g., SFTP with AES-256, TLS 1.2+). Data at rest on the SFTP server should also be encrypted. Contractor is to provide IP whitelisting options. Contractor will post daily files to the SFTP site and must define the file posting schedule (ie. time of day), file naming conventions, validation rules and provide documentation of file formats prior to project kick-off. Contractor must also provide monitoring/alerting if daily files fail to post. City will post return files to the same SFTP site. Coordination between Contractor and City during project kick-off to establish file exchange protocols will be required. Contractor shall deliver complete file layout/format specifications — including required fields, data types, field lengths, naming conventions, validation rules, and sample files — no later than thirty (30) calendar days prior to the start of data exchange testing. City shall have a minimum of thirty (30) calendar days from receipt of final specifications to develop and test the required export processes from the City's Tyler Munis system. Any changes to file format specifications after go-live shall require thirty (30) calendar days' written notice from the initiating party. No format changes shall take effect until both parties have confirmed successful testing. Detailed data transfer specifications are set forth in Appendix [A] — Data Transfer Specifications, which is incorporated below. 1.3.5.User Acceptance Testing 1.3.5.1 Testing Plan When changes to the system are completed, the Contractor shall develop and submit a testing plan for Integration Testing, Acceptance testing for the City’s review and approval by City team members from IT and Utilities. The testing plans shall include roles/responsibilities for defect resolution, retest procedures, acceptance criteria for functional and security testing, and timelines of all development steps discussed above. Test plans shall establish documentation and communication protocols, define a detailed list of Use Cases for each scenario that will need to be tested and what the expected result should be. A Use Case shall be deemed passed if the actual results match the expected result. Test plans shall include security, role-based access control, logging/audit functions, in additional to functional correctness. City team members will review the submitted testing plan and add any Use Cases that are missing or require more detail. The test plan will be submitted for initial review two (2) weeks after FDD approval and will be approved prior to Integration testing to begin. Docusign Envelope ID: 6AD75F50-8A33-85A5-8039-9E3E1257A838Docusign Envelope ID: 177582DA-4F1C-8834-813C-BC4FD03AA45E