Agenda Packet_2025-08-05 - Laserfiche WebLink

Home Browse Search

vii. Work begins as agreed upon to incorporate change; or, viii. MERIDIAN Project Manager works with the CLIENT Project Manager to either adjust the requirements or revise the workload distribution, documenting all changes on a revised Change Request Form. Change Management Criteria are as follows: i. Any change that is outside the scope of effort defined in Schedule 1 ; ii. Any additional deliverable or service not defined in Schedule 1, or changes to an accepted deliverable; iii. Any subsequent modifications to an approved Change Request; iv. Modifications to the technical or management approach defined in Schedule 1; v. Any change in workload or environment or application inventory; vi. Any additional activity or task not defined in Schedule 1 for a planned deliverable; vii. A contradiction to items, assumptions or responsibi lities stated in Schedule 1; viii. A delay in turnaround of approvals, information , answers to questions; and ix . Time lost due to reas ons such as unavailability of equipment, software, or access to environmenUinfrastructure needed by the project team. H. Acceptance Management In an effort to avoid schedule delays stemming from delayed approvals of dependent tasks, MERIDIAN and CLIENT will mutually define a reasonable acceptance review period that does not jeopardize the project duration as outlined within the project management support period Delays in accepting project deliverables could result in a schedule slippage equaling as much as one day for every day acceptance review is delayed. Below are the methods used to verify and validate each of the defined deliverable(s). i. Deliverable Review and Approval. MERIDIAN wi ll provide deliverables to the CLIENT. Documentation deliverables will be provided to CLIENT in electronic form. A Deliverable Acceptance Form will be submitted to the CLIENT Project Manager fo r each deliverable. CLIENT will provide MERIDIAN with one set of consolidated comments. MERIDIAN will provide a CLIENT Qual ity Control (QC) sheet that may help the CLIENT collate all co mments prior to delivering to MERIDIAN. The deliverable will be deemed acceptable when it satisfies the acceptance criteria specified for each deliverable or service or within ten ( 10) calendar days if no response is received. The Deliverable Acceptance will be signed and returned to MERIDIAN upon rev iew of the deliverable within the mutually defined period as stated upon under acceptance ma nagement. In the event that the CLIENT rejects a deliverable , MERIDIAN will resu bm it the deliverable to the CLIENT with the required changes within a mutually agreed upon timeline. ii. Acceptance Authority. CLIENT will specify a single point of contact w ith deliverable acceptance/sign off authority. Sign off acceptance is required for deliverab le by the approving authority, prior to moving any custom iza tions to the production site. iii. Withholding Acceptance. CLIENT shall not unreasonably withhold acceptance . If Acceptance is not granted or reje cted within the mutually agreed upon timeframe, automatic Saas Agreement: Multi-Tenant meridianks.com City Council 14 – 42 8/5/2025