Acceptance Review Period. For each Milestone Deliverable, DIR shall have either (1) the period of time set forth in the applicable plan, if any, or (2) if no such period is set forth in a DIR-approved plan, thirty (30) days following Service Provider's notification to DIR that Service Provider has completed any Milestone Deliverable, which shall include Service Provider's internal testing as required under this Agreement, to determine whether it Complies with its Acceptance Criteria (such period of time, the "Acceptance Review Period"). The Acceptance Review Period shall begin on the date that Service Provider provides written notification to DIR that the Milestone Deliverable is ready to be reviewed by DIR. Unless otherwise agreed, Service Provider shall perform comprehensive testing (e.g. unit, string, integration, stress, volume, system testing) on each such Milestone Deliverable prior to submitting such item to DIR for Acceptance.
Acceptance Review Period. For each Milestone Deliverable, DIR shall have either (1) the period of time set forth in the applicable plan, if any, or (2) if no such period is set forth in a DIR-approved plan, thirty (30) days following Service Provider's notification to DIR that Service Provider has completed any Milestone Deliverable, which shall include Service Provider's internal testing as required under this Agreement, to determine whether it Complies with its Acceptance Criteria (such period of time, the "Acceptance Review Period"). Unless otherwise specified in the applicable plan, the Acceptance Review Period for Milestone Deliverables identified as Interim Milestones (in the Transition Plan or the Transformation Plan) shall be ten (10) days. The Acceptance Review Period shall begin on the date that Service Provider provides written notification to DIR that the Milestone Deliverable is ready to be reviewed by DIR. Unless otherwise agreed, Service Provider shall perform comprehensive testing (e.g. unit, string, integration, stress, volume, system testing) on each such Milestone Deliverable prior to submitting such item to DIR for Acceptance. The acceptance review process for Milestone Deliverables identified as Checkpoint Deliverables (in the Transition Plan or the Transformation Plan) is defined in the Service Management Manual.
Acceptance Review Period. For determining whether to Accept or reject each Deliverable, OCA shall have either (A) the period of time set forth in the Statement of Work, or (B) if no such period is set forth, ten (10) Business Days following OCA’s acknowledgement of receipt of Contractor’s notification that Contractor has completed such Deliverable (any such period of time, the “Acceptance Review Period”). Contractor shall perform comprehensive testing (e.g., unit, string, integration, stress/performance, volume, system testing, regression, security/intrusion, user acceptance), if applicable, on each such Deliverable prior to submitting such item to OCA for Acceptance.
Acceptance Review Period. Each Customer shall provide written feedback to Contractor by its respective Customer Program Manager stating its respective acceptance or non-acceptance of a Key Milestone within four (4) weeks from notice and delivery of Contractor on completion of a Key Milestone. If a Key Milestone is not accepted by either Customer, that Customer shall provide detailed information on the cause of the non-acceptance and the reason(s) why that Customer contend and reasonably demonstrate that the Contractor did not fulfill its duties and obligations as set forth in this Contract and the applicable Exhibit Set. Non-Acceptance of a Key Milestone by one Customer shall be deemed to be non-acceptance by all Customers. For Key Milestones associated with Product Deliverables, if a Key Milestone is not accepted by Customer(s) due to nonconformance with the Specification (i) Customer(s) shall detail the functionality and test criteria not conforming to the Specification and (ii) Customer(s) shall reasonably demonstrate the nonconformance, enabling the Contractor to reproduce the nonconformance.
Acceptance Review Period. Ten (5) business days total DELIVERABLE 8: HISTORICAL DATA CONVERSION DEVELOPMENT Upon Agency approval of the Historical Data Conversion Specifications document, (Deliverable 7), Accela will provide a program(s) to migrate appropriate historical data into Accela Automation. Upon receipt of the conversion from Accela, the Agency DBA will load the data into the Support Cloud environment for validation. In terms of specific output, the following will be executed for this deliverable: ⮚ Migrated historical data into Accela Automation Support Cloud database environment. Accela Deliverables: • Data conversion Accela Responsibilities: • Provide a program to migrate historical data into the Agency’s AA test database environment. • Each data conversion will include up to three (3) conversion loads for client testing o Load 1 will include Composition to Record Type Mappings, Addresses, Work Description, Summary Costs, Status, and Inspections o Load 2 will include Screen Data Mapped to ASI or XXXX and all other data in Load 1. o Load 3 will include all data in Load 2 plus any mapping adjustments. • Validate the successful completion of the migration of historical data into the Accela Support Cloud. Agency Responsibilities: • Providing the legacy data source in an accepted format • Assist in the execution of the data conversion program and provide access to environments as needed • Provide resources to validate the conversion statistics and the quality of the data converted into Accela Automation Acceptance Criteria: • Historical data has been converted to Accela Automation testing environment according to the Data Conversion Mapping document. Acceptance Review Period: • Ten (5) business days total
Acceptance Review Period. Ten (10) business days total Upon Agency approval of the Historical Data Conversion Specifications document, Avocette will provide a program(s) to migrate appropriate historical data into Accela Civic Platform. Upon receipt of the conversion from Avocette, the Agency DBA will load the data into the Test environment for validation. In terms of specific output, the following will be executed for this deliverable: ⮚ Completion of migrated data into Accela Civic Platform development or test environment. • Provide a program to migrate historical and in-flight data into the Agency’s AA test database environment. • Each data conversion will include up to three (3) conversion loads for client testing. • Validate the successful completion of the migration of historical data into the Agency’s test environment. • Providing the legacy data source in an accepted format. • Assist in the execution of the data conversion program and provide access to environments as needed. • Provide resources to validate the conversion statistics and the quality of the data converted into Accela Civic Platform • Historical and in-flight data has been converted to Accela Civic Platform testing environment according to the Data Conversion Mapping document. • Ten (10) business days total Following the data conversion of the historical and in-flight data the documents attached to the legacy data will be loaded into the Accela system on a record-by-record basis. In terms of specific output, the following will be executed for this deliverable: ⮚ Completion of document migration to the converted records. • Provide an interface to transfer the converted data documents on a record-by-record basis. • Providing the documents on an accessible shared directory with directories for each converted records. • Metadata and documents to be imported will be in the directories. • Provide resources to validate the document conversion. • Historical data has been converted to Accela Civic Platform testing environment according to the Data Conversion Mapping document.
Acceptance Review Period. The City will have 5 business days to conduct an initial review of the Interface Specification document(s.) If no changes or comments are requested within the 5 days, the Interface Specification document(s.) is considered approved by the City. Upon delivery of initial feedback, Avocette will complete the necessary changes and updates. The second and final review will have 3 business days for acceptance. If no changes or comments are requested within the 3 days, the Interface Specification document(s.) is considered approved and eligible for invoicing.
Acceptance Review Period. For agreed to deliverables and milestones (each of the foregoing a Critical Testing Deliverable) and any other established Critical Testing Deliverable, Triad will have either (1) the period of time set forth in the applicable plan or Acceptance Documentation, if any, or (2) [**] if no such period is so established, to determine whether the Critical Testing Deliverable Complies to its Acceptance Criteria (such period of time the “Acceptance Review Period”). The Acceptance Review Period will begin on the date that Supplier provides written notification to Triad that the Critical Testing Deliverable is ready to be reviewed by Triad (a Deliverable clearly marked “Final—Delivery for Acceptance Pursuant to Section 4.6 of the Agreement” and delivered in accordance with this Section 4.6 shall constitute such notification). Unless otherwise agreed, Supplier will perform comprehensive testing (e.g., unit, string, integration, stress, volume, system testing, as appropriate) on each such Critical Testing Deliverable prior to submitting such item to Triad for Acceptance.
Acceptance Review Period. For each Major Milestone or Critical Deliverable, DIR shall have either (1) the period of time set forth in the DIR-approved plan (i.e., Exhibit 3.7 or the applicable Work Order) if any, or (2) if no such period is set forth in a DIR-approved plan, ten
Acceptance Review Period. For each Major Milestone or Critical Deliverable, DIR shall have either (1) the period of time set forth in the applicable plan, if any, or (2) if no such period is set forth in a DIR-approved plan, ten (10) Business Days following Successful Respondent’s notification to DIR that Successful Respondent has completed any Milestone Deliverable, which shall include Successful Respondent’s internal testing as required under this Agreement, to determine whether it Complies with its Acceptance Criteria (such period of time, the "Acceptance Review Period"). Unless otherwise specified in the applicable plan, the Acceptance Review Period for Milestone Deliverables identified as Interim Milestones shall be five (5) Business Days. The Acceptance Review Period shall begin on the date that Successful Respondent provides written notification to DIR that the Milestone Deliverable is ready to be reviewed by DIR. Unless otherwise agreed, Successful Respondent shall perform comprehensive testing (e.g., unit, string, integration, stress, volume, system testing) on each such Milestone Deliverable prior to submitting such item to DIR for Acceptance.
