ACCEPTANCE AND TESTING PROCEDURES Sample Clauses

ACCEPTANCE AND TESTING PROCEDURES. Specify acceptance procedures and testing criteria, which will be utilized to determine the acceptability of the deliverables and the period of acceptance.

ACCEPTANCE AND TESTING PROCEDURES. 11.1 Where the Services require the testing and Acceptance of Deliverables, the following procedures shall apply: 11.1.1 Inoapps shall where applicable perform the Services against the agreed Acceptance Criteria set out in the Work Order, or otherwise agreed in writing between the Parties. 11.1.2 On completion of the Services, or part thereof, Inoapps shall deliver to Customer a test copy of the Deliverables. Customer shall accept the Deliverables in accordance with the procedures laid out in Clauses 11.1.2 to 11.1.11. 11.1.3 Customer shall test the Deliverables and all parts thereof to ensure it performs in all material respects in accordance with the Work Order and the agreed Acceptance Criteria. 11.1.4 If Customer finds the Deliverables performs in all material respects in accordance with the Work Order and the agreed Acceptance Criteria the Deliverables shall be deemed to have passed the Acceptance Test. Customer shall notify Inoapps that the Deliverables have passed the Acceptance Test by signing an appropriate Acceptance Certificate (attached as Appendix A) withinthirty (30) days of receiving the test copy of the completed Deliverables from Inoapps unless otherwise agreed by both Parties and documented as such in the applicable Work Order. 11.1.5 If Customer finds the Deliverables or any part thereof do not perform in all material respects in accordance with the Work Order and the agreed Acceptance Criteria, Customer shall give notice to Inoapps of such failure and shall specify which parts of the Deliverables fail to meet the Work Order or the agreed Acceptance Criteria. Such notice shall be given to Inoapps within thirty (30) days of receiving the test copy of the Deliverables from Inoapps, unless otherwise agreed by both Parties and documented as such in the applicable Work Order. 11.1.6 If Inoapps has notreceivednotification from the Customer in accordance with Clause 11.1.4 or 11.1.5 then Customer shall have deemed to have accepted the Deliverables in all respects and signed off on any Acceptance Certificate and applicable Payment Milestone. 11.1.7 If Customer is unable to test the applicable Deliverables or otherwise fulfil its obligations under these Acceptance procedures, Customer, acting reasonably shall notify Inoapps accordingly in writing within 7 days of receipt of Deliverables and the provisions of Clause 0 shall apply. 11.1.8 On receiving notification from the Customer pursuant to Clause 11.1.5, Inoapps shall perform further Services w...

ACCEPTANCE AND TESTING PROCEDURES. Unless otherwise agreed to in writing by County:

ACCEPTANCE AND TESTING PROCEDURES. Specify acceptance procedures and testing criteria, which will be utilized to determine the acceptability of the Deliverables and the period of acceptance. FIREEYE’S RESPONSIBILITIES. FireEye deliverables include the following: Equipment and resources to be provided by FireEye: FireEye shall provide and make available to Company, on a loan basis only while Company is performing Services under this SOW, the following materials, documentation and equipment. Company shall return all such materials, documents, and equipment on the earlier of the request of FireEye and final completion of the Services. All such materials, documentation and equipment shall be considered the Confidential Information of FireEye.

ACCEPTANCE AND TESTING PROCEDURES. Component Tests System Tests Acceptance Tests (in each case, involving both quality and function)

ACCEPTANCE AND TESTING PROCEDURES. LOCATION OF WORK FACILITIES Substantially all of the work will be conducted by Consultant at its regular office located in . City will provide the City office space and support as it agrees may be appropriate, at its

ACCEPTANCE AND TESTING PROCEDURES.  The Implementation Plan is to be developed jointly and agreed upon in writing by County and Contractor and shall include a high-level schedule, which is to be created and/or finalized during the Project Kick-Off. Once approved, the Implementation Plan will be deemed part of this Contract and will control the timeline for the Phases and Milestones for the Project.  The Implementation Plan Template is as follows, but may be modified as agreed upon in writing by the County and Contractor: Introduction Call Introduction of project teams Schedule kick-off date Discuss action items to prepare for project kick-off Project Kick-Off (Project Team at Orange County) Contractor Project Team shall be on-site Review Project Implementation Plan and Schedule Meet with County’s Civil Office, IT, Accounting, and other personnel as required Review Statement of Requirements and configuration options Collect any sample papers and reports unique to County Base Hardware & Software Setup County to set up servers for CountySuite Sheriff County provides Sirron backup on server Contractor shall configure servers, test hardware and network connectivity Contractor shall install base configuration of CountySuite Sheriff Initial Data Migration Contractor shall: Perform and verify a complete migration from current system to CountySuite Sheriff Provide matching Trial Balance report to verify accurate conversion Validate ledger balances Validate cases, files, services, reports, accounting, contacts Run as many test migrations as required to approval Initial Training (Project Team at Orange County) On-site training Complete end to end Help Documents for all processes Configuration Updates Review all the configurable options for the settings required for County Acceptance Testing Contractor shall begin acceptance testing Validation Through a provided process, including dual entry, validate county specific features, configuration, and data migration. Final Validation & Training (Project Team at Orange County) Final overview, accounting, and administrative training Review Go-Live plan Go Live (Project Team at Orange County) Contractor shall be on-site Final data migration Project Completion Acceptance sign-off Introduction to support team and processes

ACCEPTANCE AND TESTING PROCEDURES. Unless otherwise agreed to in writing by County, 1) acceptance shall not be deemed complete unless in writing and until the Commissary Operations System has been received, inspected, and tested to the satisfaction of County, and 2) County shall have ninety (90) business days to complete the Acceptance and Testing criteria provided herein. Contractor and County work cooperatively to modify the proposed test plan to a plan suitable for a test region that will be used for the testing to determine compatibility within the County’s IT environment in order to facilitate verification of features provided with Commissary Operations System. County Technical Support staff installs the Commissary Operations System in a test region ready for testing. Testing occurs in accordance with the test plan and results evaluated by County. Contractor must be available to provide support to assist County in executing features. During the Compatibility Testing Period, County shall immediately provide written notice to Contractor if any incompatibility is detected. Upon receipt of such notice, Contractor shall use its best efforts to remedy the failure or install a fix within fourteen (14) business days at no additional cost to County. If such notice is provided by County to Contractor, the Compatibility Testing Period may be extended beyond the ninety (90) day testing period at the sole discretion of the County. If an incompatibility between the proposed Commissary Operations System and the County’s computer infrastructure cannot be remedied within 90 days of installation, the Contractor shall submit a written response to the County indicating as such and the County shall then return the Commissary Operations System to the Contractor and the Contract shall be terminated without any monetary obligation by the County to Contractor.

ACCEPTANCE AND TESTING PROCEDURES