CORE & MAIN LP (#2027021) - Laserfiche WebLink

RFP-2 – Scope of Work RFP# PWD 25.604 City of Pleasanton, CA RFP-2 | Page 8 Internal Use Only D.Integration Testing: The Contractor and the City shall perform integration testing which shall be completed once the City and the Contractor have completed the initial development of both sides of the interface. This testing shall validate the files can be exchanged and consumed using the layouts and formats described in the FDD. Testing shall also include performance under load, error recovery capabilities, and security (e.g., unauthorized access attempts). Test plans shall include simulated failure scenarios. Integration testing is expected to take approximately three (3) weeks. Any defects found shall be documented and resolved. Where required the FDD document shall be updated and reissued. E.Initial User Acceptance testing: With the support of the Contractor, the City will perform the Initial User Acceptance Testing (IUAT) on the City's test systems and will have as many Use Cases as required to test and validate all functionality of the systems and interfaces. The City will be responsible for coordinating and documenting the results and any deficiencies identified with the Use Cases. The Contractor and the City shall be responsible for redevelopment and adjustments based on the results of the Use cases. The IUAT is expected to take three (3) weeks. Any defects found shall be documented and where required the FDD document shall be updated and reissued. F.End to End Test: With the support of the Contractor, the City will perform an end-to-end test that will validate all interfaces are working as intended and the City is able to properly bill for water for all sizes of water meters. End-to-end testing will include Tyler Munis billing cycle processing, customer portal updates, and any other downstream systems that rely on AMI data to confirm true operational readiness. The end-to-end test is expected to take three (3) weeks. Development of all the interfaces may not start at the same time. Documentation, development, or testing work may overlap with each other. The Contractor shall allow two (2) to four (4) weeks of redevelopment in addition to the timelines laid out above. 1.3.3.System and Interface Requirements At a minimum, the Contractor shall perform and support the interface development steps of the following interfaces with the detailed functionality. All integration work is included in scope and cost, including the joint end-to-end testing of billing processes prior to go-live. Where the solution includes additional required interfaces or function0ality not detailed, the Contractor shall include it within the base proposal. All integrations should support secure authentication between systems (e.g., certificate-based or tokenized access). 1.3.3.1 MUNIS to AMI Software The Contractor shall establish a file transfer that is acceptable to the City. The data interface shall include the following types of functionalities: a.On-cycle meter reading requests: where all locations within a billing cycle will be scheduled to be read. b.Off-cycle meter reading request: that will request a single location will be scheduled to be read. c.Configuration files that will install a new meter and radio transmitter or make changes to an existing meter and radio transmitter ensuring the consumption is associated with the correct property. 1.3.3.2 AMI Software to MUNIS a.On-cycle meter reading response: the response to the on-cycle read request. The system can provide a reading based on the last X (City defined) days reading. b.Off-cycle meter reading response: the response to the off-cycle read request. The system can provide a reading based on the last X (City defined) days reading. Docusign Envelope ID: 6AD75F50-8A33-85A5-8039-9E3E1257A838Docusign Envelope ID: 177582DA-4F1C-8834-813C-BC4FD03AA45E