Agmt17 Smart Utility Systems, Inc.

Browse Search

4. Change Control: The following process will be followed if a change to this SOS or project plan is required: 4.1. A Project Change Request (PCR) will be the vehicle for Communicating change. The PCR must describe the change, the rationale for the change, and the effect the change will have on the Project. Additionally, the PCR must also provide a recap of the original estimated resources and costs, revised estimated resources and costs and associated cost savings or expenditures. 4.2. The designated Project Manager of the requesting party will review the proposed change and determine whether to submit the request to the other party. 4.3. Both Project Managers will review the proposed change and agree to take steps to implement it, including a signed Change Order, recommend it for further investigation, or reject it. 4.4. Consultant will specify any changes to the fees as per agreed rate in this Scope of Services for such investigation. A Change Order must be signed by authorized representatives from both parties in order to revise the Agreement before any work can commence in regards to such. 5. Risks and Assumptions The following assumptions, which have been accepted by City, have been made in order for Consultant to fulfill its obligations under this Agreement, the failure of which by City may affect Consultant's Project Duration and Timeline under Section 2: 1. City will provide timely responses to Consultant's information needs and timely review of project documents provided. 2. Key personnel at City will be made available to Consultant as required during the project 3. City will provide onsite workspace for Consultant's resources with internet connectivity as necessary. 4. All documents will be jointly reviewed with City staff. 5. The SOS is binding if authorized, and any changes to the SOS will be provided in writing from either the Consultant or the City team and approved by both teams. 6. The City fully acknowledges and understands that any customization to standard features and functionality as described in this SOS will be assessed by Consultant and may impact approved budget and/or schedule. City will have discretion to determine whether to proceed with such customizations. 7. Integration to City source systems and data is dependent on access to said systems, including as well as API allowances from the respective companies. Consultant will work on behalf of City to obtain such APIs within reason, however City is responsible to ensure such access and API allowances are provided. In addition, existing API or SFTP processes for City source system data, including customer, billing, and usage data, will be made available for use or re -use as part of the project. Ability to view bill PDF is dependent on API availability at the start of this project. 8. City agrees to ensure Integration access with City's billing and payment systems provider prior to Milestone 1. Failure to obtain such availability and/or access from City's billing provider shall not affect City's obligations under this Agreement. 9. Standard SLA levels offered by Consultant are acceptable including 99.999% availability and a recovery point objective of 24 hours. Please refer to Consultant's Product Support document. 10. Standard implementation and configuration by Consultant is conducted primarily from Consultant's offices with any included on-site activities to be determined and documented during Milestone One. Additional Consultant resources beyond those so identified will travel to City offices on an as -requested basis if and when practicable. Any such requested on-site implementation activities will be billed to City at a minimum rate of $150 per individual per work hour. Page 21 of 38 ATTY/AGR/2017.104/SMART ENERGY SYSTEMS—CUSTOMER WATER USE PORTAL REV: 05-15-17 MI