SaaS Maintenance Services. The SaaS Software maintained under this Attachment shall be the SaaS Software set forth in Appendix B to this Attachment. The following SaaS Maintenance Services are included as part of this Attachment: Contractor Software Version Upgrades, Software Revisions and Patches. Contractor shall provide and implement ALL SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software Patches to ensure: (a) the functionality of the SaaS Software and SaaS Services, as described in the Documentation, is available to Authorized Users; (b) the functionality of the SaaS Software and SaaS Services in accordance with the representations and warranties set forth herein, including but not limited to, the SaaS Software and SaaS Services conforming in all material respects to the specifications, functions, descriptions, standards, and criteria set forth in the Documentation; (c) the Service Level Standards can be achieved; and, (d) the SaaS Software and SaaS Services work with the non-hosted browser version. Deployment of these revisions will be mutually agreed upon between Contractor and City. Release of software revisions as defined will be conducted on a schedule as determined by Contractor. Contractor shall provide no less than a thirty (30) calendar day prior written notice of when any such revision is scheduled to be released. City will be granted a fifteen (15) calendar day evaluation window to review release documentation regarding software modules being impacted and general revision changes. After the evaluation period, Contractor will conduct a deployment of the revision to the City Test Environment. The software deployment will be scheduled in writing five (5) calendar days prior to actual deployment activities. As part of the upgrade activities within the Test Environment, Contractor may provide nominal testing to ensure all systems are functional and the revision deployment was successful. Post deployment activities include an e-mail or portal post to serve as written notification that this service has been completed. City will be allowed a forty-five (45) calendar day test window in which City has ability to test and raise issues with Contractor. Issue resolution will be managed per the process as described here within. Test Environment deployment activities will be conducted during a mutual agreed to time window and may not necessarily align with the production maintenance windows as described within this document. In the event a SaaS Severity Level 1 or Severity Level 2 Issue has been identified and appropriately triaged and classified by both Contractor and City during the Test Environment deployment test window, Contractor will be required to correct the SaaS Issue. If the SaaS Issue can be corrected and can be redeployed within the remainder of the deployment test window, City will have an additional five (5) testing days in which to evaluate and further test for the SaaS Issue resolution. If the SaaS Issue cannot be corrected within the remainder of the test window, Contractor will deploy immediately upon availability with as much notice as practicable. City will be allowed an additional five (5) testing days to evaluate the correction post the test window if desired. If at any time during the testing window City identifies the presence of multiple SaaS Severity Level 1 or Severity Level 2 Issues that can be shown to materially impact City ability to continue testing, City may in writing elect to suspend testing until corrections for the SaaS Issues can be provided. Contractor will deploy corrections immediately upon availability with as much notice as practicable. Upon release of corrections, City will have five (5) calendar days to commence the testing within the then available remaining testing window. Unless exists outstanding circumstances as described here within, Contractor will promote revision from Test Environment to Production and Back-up environments after the provided test window has elapsed. The software promotion will be scheduled in writing five (5) calendar days prior to actual deployment activities. As part of the promotion activities within the Production and Back-up environment, Contractor may provide nominal testing to ensure all systems are functional and the revision promotion was successful. Post promotion activities include an e-mail or portal post to serve as written notification that this service has been completed. At the point of e-mail or portal posting, the new revision will be considered “in production” and supported under the maintenance service terms described here within. In support of such SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software Patches, Contractor shall provide updated user technical documentation reflecting the SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software Patches as soon as reasonably practical after the SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software Patches have been released. Updated user technical documentation that corrects Errors or other minor discrepancies will be provided to Contractor’s customers when available.
Appears in 1 contract
Sources: Professional Services
SaaS Maintenance Services. The SaaS Software maintained under this Attachment Agreement shall be the SaaS Software set forth in Appendix B to this AttachmentAgreement. The following SaaS Maintenance Services are included as part of this AttachmentAgreement: Contractor Software Version Upgrades, Software Revisions and Patches. Contractor shall provide and implement ALL SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software Patches to ensure: (a) that the functionality of the SaaS Software and SaaS Services, as described in the Documentation, is available to Authorized Users; (b) that the functionality of the SaaS Software and SaaS Services is in accordance with the representations and warranties set forth herein, including but not limited to, the SaaS Software and SaaS Services conforming in all material respects to the specifications, functions, descriptions, standards, and criteria set forth in the Documentation; (c) that the Service Level Standards can be achieved; and, and (d) that the SaaS Software and SaaS Services work with the non-hosted browser version. Deployment of these revisions will be mutually agreed upon between Contractor and City. Release of software revisions as defined will be conducted on a schedule as determined by Contractor. Contractor shall provide no less than a thirty (30) calendar day prior written notice of when any such revision is scheduled to be released. City will be granted a fifteen (15) calendar day evaluation window to review release documentation regarding software modules being impacted and general revision changes. After the evaluation period, Contractor will shall conduct a deployment of the revision to the City Test Environmenttest environment. The software deployment will be scheduled in writing five (5) calendar days prior to actual deployment activities. As part of the upgrade activities within the Test Environment, Contractor may provide nominal testing to ensure all systems are functional and the revision deployment was successful. Post deployment activities include an e-mail or portal post to serve as written notification that this service has been completed. City will be allowed a shall have forty-five (45) calendar day test window in which City has ability to test and raise issues with Contractor. Issue resolution will be managed per the process as described here within. Test Environment environment deployment activities will be conducted during a mutual agreed mutually agreed-to time window and may not necessarily align with the production maintenance windows as described within this document. In the event If a SaaS Severity Level 1 or Severity Level 2 Issue has been identified and appropriately triaged and classified by both Contractor and City during the Test Environment test environment deployment test window, Contractor will be required to shall correct the SaaS Issue. The severity of a SaaS Issue will be initially defined by the City and confirmed by Contractor. Until the SaaS Issue has been resolved, the Severity Level may be raised or lowered based on Contractor’s analysis of impact to business. If the SaaS Issue can be corrected and can be redeployed within the remainder of the deployment test window, City will have an additional five (5) testing days in which to evaluate and further test for the SaaS Issue resolution. If the SaaS Issue cannot be corrected within the remainder of the test window, Contractor will deploy immediately upon availability with as much notice as practicable. City will be allowed an additional five (5) testing days to evaluate the correction post the test window if desired. If at any time during the testing window City identifies the presence of multiple SaaS Severity Level 1 or Severity Level 2 Issues that can be shown to materially impact City ability to continue testing, City may in writing elect to suspend testing until corrections for the SaaS Issues can be provided. Contractor will deploy corrections immediately upon availability with as much notice as practicable. Upon release of corrections, City will have five (5) calendar days to commence the testing within the then available remaining testing window. Unless exists outstanding circumstances as described here within, Contractor will promote revision from Test Environment to Production and Back-up environments after the provided test window has elapsed. The software promotion will be scheduled in writing five (5) calendar days prior to actual deployment activities. As part of the promotion activities within the Production and Back-up environment, Contractor may provide nominal testing to ensure all systems are functional and the revision promotion was successful. Post promotion activities include an e-mail or portal post to serve as written notification that this service has been completed. At the point of e-mail or portal posting, the new revision will be considered “in production” and supported under the maintenance service terms described here within. In support of such SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software Patchespatches, Contractor shall provide updated user technical documentation reflecting the SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software Patches patches as soon as reasonably practical after the SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software Patches have been released. Updated user technical documentation that corrects SaaS Software Errors or other minor discrepancies will be provided to Contractor’s customers when available.
Appears in 1 contract
Sources: Software as a Service Agreement