Deliverable Acceptance. Where the Agreement requires the submission of deliverables to Citizens, mere receipt or a lack of response by Citizens shall not be construed to mean or imply acceptance of those deliverables. It is specifically intended by the parties that acceptance in writing of the required deliverables shall constitute a separate act. The submitted deliverables will be considered accepted once approved, in writing, by Citizens’ Contract Manager or designee. Citizens reserves the right to reject deliverables as incomplete, inadequate, or unacceptable according to the parameters set forth in this Agreement. Citizens, at its option, may allow additional time within which the Vendor may remedy the objections noted by Citizens.
Deliverable Acceptance. Contractor will deliver completed work products and services (“Deliverables”) to the designated ITS approver who has been authorized to accept Deliverables, using the "Deliverable Acceptance Form" attached to the RFP. Deliverables must meet Contract and, where applicable, DED requirements. The ITS approver will accept or reject the Deliverable. Deliverables will not be automatically accepted in the event of New York State failure to act. If the ITS approver rejects a Deliverable, the cause for rejection and all defects to be addressed will be documented by ITS and provided to the Contractor and the Contractor will correct all identified deficiencies, and resubmit the Deliverable for acceptance. There shall be no verbal acceptance or acceptance by default of a Deliverable.
Deliverable Acceptance. If testing of Deliverables identifies that a Deliverable has failed to meet its Acceptance Criteria for any reason, DSHS may:
i. reject the Deliverable and the Contractor shall re-supply the Services or Deliverable to rectify any non-conformance;
ii. accept the Deliverable notwithstanding any non-conformance; or
iii. partially accept the Deliverable and require Contractor to correct any non-conformances as part of a subsequent Deliverable or new Deliverable as appropriate.
Deliverable Acceptance. Completed work products (“Deliverables”) will be delivered to the designated ITS approver who has been authorized to accept Deliverables. Deliverables mustmeet Contract and/or Transaction Document requirements. Contractor must use Appendix G – Deliverables Acceptance Form to request written approval and acceptance by ITS of Contract Deliverables. The ITS approver will accept or reject the Deliverable. Deliverables will not be automatically accepted in the event of New York State failure to act. If the ITS approver rejects a Deliverable, the cause for rejection and all defects to be addressed will be documented by ITS and provided to the Contractor and the Contractor will correct all identified deficiencies, and resubmit the Deliverable for acceptance. There shall be no verbal acceptance or acceptance by default of a Deliverable.
Deliverable Acceptance. The following procedures will govern Customer’s acceptance of the deliverables provided by HRC pursuant to an SOW (each a “Deliverable” and collectively the “Deliverables”).
2.1 Customer will have 5 business days (the “Acceptance Period”), following the date of the initial delivery of a completed Deliverable, to verify that such Deliverable materially conforms to specifications set forth in the design document(s).
2.2 By the end of the Acceptance Period, Customer will notify HRC in writing of any material non-conformities that cause rejection of the Deliverables. HRC will then have 10 business days (the “Cure Period”) to correct all nonconformities. Upon receipt of HRC’s corrections, Customer will then have 5 more business days to retest the Deliverables to determine if such nonconformities have been corrected.
2.3 The process of acceptance testing by Customer, correction by HRC and re-testing by Customer will continue until the earlier of (i) acceptance of the Deliverables by Customer or (ii) termination of this SOW by Customer; provided, however, that HRC will be entitled to not less than 2 opportunities to correct non-conformities in a Deliverable and submit such Deliverable for re-testing by Customer before Customer may terminate the SOW due to such continued non-conformity.
2.4 Customer will notify HRC in writing of its acceptance. In the event that any Acceptance Period or the Cure Period expires without Customer notifying HRC of its rejection of a Deliverable, such Deliverable will be deemed accepted.
Deliverable Acceptance. The client has thirty (30) business days to review each deliverable and submit review comments. Woolpert will review each comment and together with the client determine the appropriate action. If it is determined that Woolpert needs to re‐submit a deliverable or portion of a deliverable, that deliverable or portion will be completed and resubmitted within thirty (30) business days after the appropriate action has been determined. Any deliverable not submitted by the client for review within thirty (30) business days will be deemed as accepted, therefore Woolpert will not be obligated to change, correct, or resubmit that deliverable. Xxxxxxxx, Inc. Professional Service Agreement March 15, 2022 Xxxxx County, Ohio 5PSA‐04/17
Deliverable Acceptance. All Contractor deliverables are subject to review by the State prior to final approval, acceptance, and payment. Acceptance of all Contractor deliverables shall be completed via a Deliverables Acceptance Document (DAD) to be drafted by the State. Deliverables must be tracked in a tracking tool approved by the State. The dates reflected in the table below assume a May 1 start date for DDI. Due dates are rolled up to the milestone/Task level; exact start and end dates for each deliverable will be determined during JAD sessions and documented in the approved Project Work Plan. All deliverables must be completed on, or prior to, the assigned due date. Task 1 — Project Initiation and Planning Deliverable 1 — Project Kick-off Presentation 05/13/2014 Deliverable 2 — Project Management Plan 06/15/2014 Deliverable 3 — Project Work Plan and Schedule 06/15/2014 Deliverable 4 — Weekly Project Status Reports 06/15/2014 Task 2 — Requirements Validation Deliverable 5 — Requirements methodology and Template 08/01/2014 Deliverable 6 — Cross-Walk of contract Requirements against Contractor’s proposed PBMS 08/01/2014 Deliverable 7 — Detailed Functional and Non- Functional Requirements Traceability Matrices 08/01/2014 Task 3 — System Design Deliverable 8 — Configuration Design Document 08/15/2014 Deliverable 9 — Data Integration and Interface Design Document 08/15/2014 Deliverable 10 – Demonstration of successful data conversion, transformation and loading from all associated incumbent systems (e.g. PBM claims and history, MMIS rebate) To be determined based on discussions with current vendor(s) Task 4 — Configuration and Development Deliverable 11 — Client Review of Configuration 09/30/2014 Deliverable 12 — Unit Testing Scripts and Results 09/30/2014 Task 5 — Testing Deliverable 13 — Documented System Test Results 10/31/2014 Deliverable 14 — User Acceptance TBD Task 6 — Training Deliverable 15 — Training Plan 11/15/2014 Deliverable 16 — Training Materials 11/15/2014 Deliverable 17 — Documented Evidence of Successful End-User Learning 11/15/2014 Task 7 — Deployment Deliverable 18 — Deployment Plan 01/01/2015 Deliverable 19 — CMS Certification Plan 01/01/2015 Deliverable 20 — System Documentation 01/01/2015 Deliverable 21 — Performance SLAs Reporting Tools and pre go live results 01/01/2015 Deliverable 22 – Final Data Conversion 01/01/2015 Deliverable 23 — Rollout (Go Live) 01/01/2015 Task 8 –Transition to Deliverable 24 - Post go live support plan 02/01/2015 Operations/Produc...
Deliverable Acceptance. 1) Unless otherwise noted in this Contract or agreed upon in writing by both parties, acceptance testing will be performed on-site, on NDUS’s platform.
2) Prior to acceptance testing, CONTRACTOR will furnish NDUS with documentation of the deliverable item, the expected performance, and agreed upon acceptance criteria.
3) Upon completion of a deliverable or sub-deliverable, NDUS will have five (5) working days in which to accept or reject it in writing. NDUS will accept by signature. If NDUS rejects it, NDUS will specify in writing its grounds for rejection and CONTRACTOR shall use its best efforts to revise any issues for the deliverables to be acceptable to NDUS within the following five (5) working days. If NDUS rejects it a second time, NDUS will have the option of repeating the procedure as described in this acceptance statement above, escalating the issue to the Executive Steering Committee, or terminating this Contract upon written notice to CONTRACTOR.
Deliverable Acceptance. Contract Manager notifies Contractor via email that the Deliverable is approved.
Deliverable Acceptance. Customer will notify Slalom in writing within five (5) business days of receiving a Deliverable whether it accepts or rejects that Deliverable. If no notification is delivered to Slalom within this period, the Deliverable will be considered accepted. Notwithstanding the foregoing, Customer may provide written notice to Slalom of errors, inaccuracies, or other deficiencies in products or Services provided by Slalom under this SOW within thirty (30) calendar days of receipt of an invoice for such products or Services. Slalom shall correct such errors, inaccuracy, or other deficiencies at no additional cost to Customer.
