Exit Criteria. 3.1 The Provider must disenrol a Service User from the CPAM Service if:
Exit Criteria. 4.1 The Provider may stop providing Smoking Cessation Services to or for a Service User if:
Exit Criteria. Completion of all work within this SOW; or · Re-engagement of AeroVironment under a new Work Order. Deliverables: · None [***] Information has been omitted pursuant to Item 601(b)(10) of Regulation S-K.
Exit Criteria. 2.3.1. [***]
Exit Criteria. Supplier and SWCO will agree in writing to the validity of baseline switch statistic data and drive test data.
Exit Criteria. The Performance Criteria is as follows: CONFIDENTIAL & PROPRIETARY General Purchase Agreement 3/98
Exit Criteria. Completed Business Requirements Review o Solectron approved business requirements o completed Systems Requirements Review • Documented and Agreed Project Plan o detailed plan for Plan Phase o outline for Qualify and Rollout Phases
Exit Criteria. The results of the System Test are to be presented to the State for approval before the development Contractor’s System status can be promoted to UAT stage for end User testing. This presentation shall take the form of a live demonstration of Contractor’s System functionality as outlined below. The State shall define, no less than 20 business days before the start of System Test phase, the criteria necessary for State approval of test results, including requirements for presentation of the results to the State and timeframes for State review.
Exit Criteria. The requirements for release from UAT are zero Severity 1 and zero Severity 2. The default State requirement for Severity 3 is zero. However, if actual Severity 3 defects are greater than zero, the Release Committee will review the defects and make a recommendation to the State whether to release to production or not. The State and Contractor Project Managers will meet and mutually agree on an acceptable level of Severity 4-5 defects in order to move forward. Defect levels of severity are as defined above.
Exit Criteria. The Exit Criteria are defined below as P0’s and P1’s. P0s are an ‘absolute must’ to be able to ship the product as per mutually agreed to schedule. P1s are ‘high wants’ and every effort must be made to meet these criteria before being ship ready, however if these criteria are not met then both teams can mutually agree to defer them to a later date with a documented deviation plan. P2’s are post-launch items and are targeted for shipment +60 days after initial launch. P0 Criteria • Meet or exceed all hardware & software technical specifications and requirements for the [**] as outlined in the mutually agreed Product Requirements Document (PRD) for Phase under execution of the program • Zero open severity 0 (showstopper/critical) & severity 1 (high) issues. Severity 2/3 (Medium/Low) issues must have an action plan for closure defined. [**] Certain information on this page has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. • Needs to pass Continuous Hours of Operation (CHO) tests listed below o Hazard C8 (72 hours continuous I/O) on Windows & Linux or Medusa or any other I/O stress tool o Hazard C16 (24 hours continuous I/O) on Windows & Linux or Medusa or any other I/O stress tool • [**] test execution across all functional areas as per the mutually agreed to shift left test plan • [**] test pass across all functional areas as per the shift left test plan. [**] test fail cannot contain any severity 1 and severity 2 issues. • [**] test execution across all functional areas of HP’s Audit test plan • [**] test pass across all functional areas of HP’s Audit test plan • All P0 (MUST) requirements as per the Product Requirements for the phase under execution must be met • Any P1 (HIGH WANT) requirements as per the Product Requirements Document (PRD), Support Matrices and (Qualification Request Forms) QRFs for the phase under execution that are mutually agreed to be deferred have to be properly documented, reviewed & approved • Performance criteria with respect to parameters such as throughput and IOPS across different I/O sizes must meet mutually agreed to benchmarks, performance requirements that are defined within the Product Requirements for the phase under execution • Scaling criteria with respect to parameters such as capacity, number of LUNs per host, number of paths from a host etc must be met across all functional areas. Scaling requirements will...
