Common use of SaaS Software Maintenance Acceptance Period Clause in Contracts

SaaS Software Maintenance Acceptance Period. Unless otherwise agreed to by City on a case-by-case basis, for non-emergency maintenance, City shall have a twenty (20) business day period to test any maintenance changes prior to Contractor introducing such maintenance changes into production. If the City rejects, for good cause, any maintenance changes during the SaaS Software Maintenance Acceptance Period, Contractor shall not introduce such rejected maintenance changes into production. At the end of the Maintenance Acceptance Period, if City has not rejected the maintenance changes, the maintenance changes shall be deemed to be accepted by City and Contractor shall be entitled to introduce the maintenance changes into production.

SaaS Software Maintenance Acceptance Period. Unless as otherwise agreed to by City on a case-by-case basis, for non-emergency maintenance, maintenance City shall have a twenty (20) business day period to test any maintenance changes prior to Contractor introducing such maintenance changes into production. If In the event that City rejects, for good cause, any maintenance changes during the SaaS Software Maintenance Acceptance Period, Contractor shall not introduce such rejected maintenance changes into production. At the end of the Maintenance Acceptance Period, if City has not rejected the maintenance changes, the maintenance changes shall be deemed to be accepted by City and Contractor shall be entitled to introduce the maintenance changes into production.

SaaS Software Maintenance Acceptance Period. Unless otherwise agreed to by City on a case-case- by-case basis, for non-emergency maintenance, maintenance City shall have a twenty (20) business day period to test any maintenance changes prior to Contractor introducing such maintenance changes into production. If the City rejects, for good cause, any maintenance changes during the SaaS Software Maintenance Acceptance Period, Contractor shall not introduce such rejected maintenance changes into production. At the end of the Maintenance Acceptance Period, if City has not rejected the maintenance changes, the maintenance changes shall be deemed to be accepted by City and Contractor shall be entitled to introduce the maintenance changes into production.

SaaS Software Maintenance Acceptance Period. Unless otherwise agreed to by City on a case-by-case basis, for non-emergency maintenance, City shall have a twenty (20) business day period to test any maintenance changes prior to Contractor introducing such maintenance changes into production. If the City rejects, for good cause, any maintenance changes during the SaaS Software Maintenance Acceptance Period, Contractor shall not introduce such rejected maintenance changes into production. At the end of the Maintenance Acceptance Period, if City has not rejected the maintenance changes, the maintenance changes shall be deemed to be accepted by City and Contractor shall be entitled to introduce the maintenance changes into production.

SaaS Software Maintenance Acceptance Period. Unless otherwise agreed to by City on a case-by-case basis, for non-emergency maintenance, City shall have a twenty (20) business -business- day period to test any maintenance changes prior to Contractor introducing such maintenance changes into production. If the City rejects, for good cause, any maintenance changes during the SaaS Software Maintenance Acceptance Periodmaintenance acceptance period, Contractor shall not introduce such rejected maintenance changes into production. At the end of the Maintenance Acceptance Periodmaintenance acceptance period, if City has not rejected the maintenance changes, the maintenance changes shall be deemed to be accepted by City and Contractor shall be entitled to introduce the maintenance changes into production.