Deliverable Acceptance Process Clause Samples

Deliverable Acceptance Process. 2.6.1 All Deliverables prepared by Contractor shall have the written approval of Owner’s project director or his or her written designee that such Deliverables comply in all material respects with the requirements of the relevant SOW, which approval shall not be unreasonably withheld. Upon delivery of a Deliverable, Owner shall have the number of business days that is specified in an SOW for Owner review of such Deliverable. If not specifically identified in the SOW, then the number of calendar days for such review shall be no more than ten (10) calendar days for document based deliverables and a longer, reasonable time for acceptance of software (in either event the “Acceptance Period”) to accept or reject the Deliverable, based on the Acceptance Criteria established for that Deliverable in the applicable SOW. Owner shall provide Contractor (i) with approval of the Deliverable or (ii) with a written statement, as provided below, of the deficiencies preventing approval. Such calendar days shall be counted from and include the first business day following the delivery of the Deliverable to Owner. 2.6.2 Owner's review and approval of Deliverables shall be for the purpose of determining compliance in all material respects with the applicable Acceptance Criteria set forth in an SOW; or in the absence of Acceptance Criteria, compliance with industry standard practices. Approval shall be granted if the Deliverable conforms in all material respects to the applicable Acceptance Criteria set forth in the SOW. In the event of Owner's rejection of a Deliverable, Owner shall provide a written statement that identifies in reasonable detail, all deficiencies within the applicable Acceptance Period, specifying the basis of the deficiency. 2.6.3 If Owner notifies Contractor that Owner has rejected the Deliverable within the applicable Acceptance Period, Contractor shall promptly begin to remedy the deficiency and shall work diligently and continuously thereafter to correct the deficiency in order for such Deliverable to conform, in all material respects with the applicable Acceptance Criteria or industry standard practices. 2.6.4 Upon delivery of the remedied Deliverable, Owner shall recommence its Acceptance Testing review of that Deliverable and shall notify Contractor in writing of acceptance or rejection. Owner's review and approval of such corrected or changed Deliverable shall be solely for the purpose of determining that corrections have been made to bring the Deli...

Deliverable Acceptance Process. Deliverables shall be accepted or rejected by the State within five (5) days from the time of Contractor submittal for acceptance. Deliverables shall be deemed not accepted in the absence of review or response for acceptance within this specified time. The use or partial use of any Deliverable constitutes acceptance of that Deliverable. Feedback supplied after the review period will be evaluated as a potential change of scope and shall follow the Change Order Process. The Deliverable Acceptance Process is described as follows:

Deliverable Acceptance Process. Each Deliverable shall follow the Deliverable submission process as follows: A. Contractor shall submit each Deliverable to CDOT for review and approval. B. CDOT will review the Deliverable and may direct Contractor to make changes to the Deliverable. Contractor shall make all requested changes within five (5) Business Days following CDOT’s direction to make the change unless CDOT provides a longer period in writing, which cannot be after the end of the term of the Contract. C. Once CDOT has received an acceptable version of the Deliverable, including all changes directed by CDOT, CDOT will notify Contractor of its acceptance of the Deliverable in writing. A Deliverable shall not be deemed accepted prior to CDOT’s written notice to the Contractor of its acceptance of that Deliverable.

Deliverable Acceptance Process. Contractor must provide each draft deliverable to the HCA Contract Manager and allow at least five (5) business days for review and comment, highlighting any deficiencies that need to be addressed prior to acceptance by HCA.

Deliverable Acceptance Process. The assigned ATOS shall perform all work associated with acceptance of Deliverables of the TO as a matter of high priority. The length of time to review such deliverables for acceptability shall be commensurate with the scope, complexity, need for verification of contents, and volume of work to review. TO Deliverables shall be sent to the Procurement Manager in electronic format on the due date as agreed upon in the TO. The deliverables must be checked for quality prior to delivery and must be accompanied by a deliverable certification form that contains a summary of the deliverable. Acceptance of the Deliverables by the ATOS and AEA is a prerequisite to approval by OIT. The State will require a ten (10) business day review period for the deliverables defined and received as a result of any TO associated with this IDIQ. Deliverables will be reviewed for completeness based on achievement of their purpose and objectives, inclusion of required contents, volume and thoroughness of their contents, and accuracy of their information. Artifacts created in support and development of deliverables must support the contents of the deliverables. Deliverables must meet the criteria described in the TO and specific ATOS approval of the deliverables to be deemed acceptable. All required payments will be made in 45 days in accordance with the contract. Offeror Response: 3.1.9

Deliverable Acceptance Process. The CITY and UNIVERUS will conduct review and acceptance of deliverables in accordance with the following procedure: UNIVERUS will work with the CITY personnel to gather input and review draft deliverables as they are developed. The CITY personnel involved with a deliverable will be the CITY team members or persons authorized to approve a specific deliverable. When a deliverable is complete, the UNIVERUS consultant will conduct a detailed walkthrough of the deliverable with the CITY team members that are appropriate to the deliverable length and complexity. The intent of this walkthrough is to confirm that the deliverable is correct and complete. Walkthroughs can consist of document reviews, design reviews, presentation reviews, program demos, or other activities to confirm that the deliverable is ready for the CITY acceptance. After the walkthrough with the CITY, the CITY will have up to ten (10) business days or mutually agreeable timeframe to accept the deliverable. The CITY must provide UNIVERUS with a date on which the deliverable will be given a disposition within the five (5) business day timeframe. The Acceptance Form should be physically signed by the CITY Project Manager and archived with the project documentation. If the CITY is not willing or able to approve a deliverable, the CITY will provide UNIVERUS with a description of what the deficiencies of the deliverable are, via the issue-tracking tool. If required, the parties will meet to discuss the deficiency of the deliverable in detail. UNIVERUS will then provide a plan to remedy the deficiencies within five business days (5) and this process will start again. If this deliverable is not remedied and or approved within the agreed-upon time frame then this process will start the Conflict Resolution Process as defined section 5.3 of this SOW.

Deliverable Acceptance Process. For those Transition Milestones Deliverables designated in Exhibit D to the applicable Country Agreement as requiring Federal-Mogul approval (e.g., final Transition Plan, final DRP, final Policies and Procedures Guide), the following approval process shall apply:

Deliverable Acceptance Process. During the term of this SOW, when CMC submits a deliverable for Customer’s acceptance, within ten (10) business days of the date of submittal, Customer is required to: • Accept the deliverable by signing off on the service deliverable acceptance form, or other form provided by CMC (which would indicate return and signature procedures as applicable), or by using (or partially using) the deliverable Or • Reject the deliverable by notifying CMC in writing and specifying how the deliverable does not meet the specifications set forth in this SOW. If a rejection notification is received, CMC will correct issues with a deliverable that is in scope of this SOW, after which the deliverable is deemed accepted. Issues that are outside the scope of this SOW, and feedback provided after a deliverable has been accepted, will be addressed as a change request and managed as described in the Change Control Process in this SOW. In the absence of an acceptance or rejection from Customer within ten (10) business days of submission by CMC to Customer, CMC shall provide notice to Customer that a response is required, and if Customer does not respond within two (2) business days of such notice, the deliverable will be deemed approved.