Acceptance Testing Procedures. In connection with each Project, the ----------------------------- parties shall mutually agree upon appropriate acceptance testing criteria and procedures for the Developed Software. The applicable acceptance testing criteria and procedures must be successfully satisfied and performed prior to EDS' acceptance of the Developed Software. If any defects or deficiencies are discovered during acceptance testing, EDS shall so notify Chordiant, and Chordiant shall have thirty (30) days from receipt of such notice to correct the deficiencies. If necessary, Chordiant and EDS may mutually agree upon an additional time period in order to continue acceptance testing of the corrected Developed Software. For purposes of an item of Developed Software, the term "Acceptance Date" shall mean the date when the Developed Software successfully satisfies the applicable acceptance testing criteria. Acceptance of an item of Developed Software does not waive any warranty rights provided in this Agreement for Developed Software.
Acceptance Testing Procedures. 65 Section 12.2 Requirements and Notification for Acceptance Testing - Commercial Operation Defined.......66 Section 12.3 Acceptance Testing to Achieve Commercial Operation........................................70 Section 12.4
Acceptance Testing Procedures. In conformance with Exhibit "D," specific test procedures for all Acceptance Testing will be developed by Contractor and shall be jointly reviewed and, if necessary, revised by Owner and Contractor, subject to final approval by Owner and Contractor.
Acceptance Testing Procedures. 2.1 The parties agree that the acceptance testing shall be done for all new Systems and a modified ATP shall be performed for all System Expansions and shall be included in all relevant Purchase Orders. The ATP tests shall be chosen from the GATP, as set forth below, that the parties have agreed to and identified when Customer purchases ATP Services. This ATP is generic in nature and tests operational features. Should a certain feature or option not be purchased then it is agreed that portion of the ATP shall be deleted and will not be performed. Motorola shall supply new sections to cover new products or features Motorola develops. The GATP will be amended to reflect desired practices for testing Systems in Commercial Service. The parties acknowledge that different approaches are required for Systems in Commercial Service and those acceptable for Systems not in Commercial Service. Motorola and the Customer agree and acknowledge that System performance may be affected by local regulatory constrains on System's operation. Since such situation will be beyond Motorola's control, it shall not impact or affect in any way the attainment of Conditional Acceptance or Final Acceptance. Furthermore, any condition derived from such situation shall not become an item on the Punchlist. Motorola and the Customer shall agree upon the ATP. It is understood that in the event Customer uses services of the Consultant for the ATP, Consultant's opinions will be subject to the decisions made by Motorola and Customer.
Acceptance Testing Procedures. Please provide your acceptance and testing procedures available to Purchasing Entities for this Category. Provide your standard of performance for this Category. 1 CSA STAR Self-Assessment documents the security controls provided by an Offeror’s offerings, thereby helping Purchasing Entities assess the security of an Offeror, if awarded a Master Agreement, they currently use or are considering using. ATTACHMENT C CONTRACT MANAGER RESUME TEMPLATE Vendor Name: Proposed Resource Name: Proposed Classification: Contract Manager If Contract Manager is associated with a subcontractor provide name of company: Percentage of time Contract Manager will be allocated to resulting master agreement: Instructions: Provide the skills, experience, education, etc. that qualify the individual for the duties and responsibilities outlined in this RFP for a contract manager. EXPERIENCE & QUALIFICATIONS The experience requirements detailed in the RFP are restated as follows:
Acceptance Testing Procedures. Paragraph 14; Amended Partnership Agreement: Paragraph 16(a); Approved Change: Paragraph 7(a); Approved Clarification: Paragraph 8; Arbitrator: Paragraph 22(c); Business Day: Paragraph 8(a); Change: Paragraph 7(a); Change Control Manager; Paragraph 7(a)
Acceptance Testing Procedures. All Acceptance Testing shall be done in a test environment and not in a production environment.
Acceptance Testing Procedures. In connection with each Project, the parties shall mutually agree upon appropriate acceptance testing criteria and
Acceptance Testing Procedures. If specifically requested by Customer, Developer shall establish mutually agreeable reasonable acceptance testing procedures to be generally in conformity with general industry practices to be performed after delivery of the Deliverables to determine if they meet the Specifications. In the event the Deliverables are rejected, Developer shall use reasonable diligence to correct any deficiencies cited in good faith by the Customer and to resolve any Customer concerns over the Deliverables.
Acceptance Testing Procedures. TCS shall develop an Acceptance Tests Plan which shall cover a comprehensive set of tests for the purpose of ensuring that the Location Server System and other Services conform to the Functional Specification and any service levels. The Acceptance Tests Plan shall, as a minimum, include the following:- • Details of the Acceptance Tests to be conducted by H3G; • Details of what is to be tested, the relevant criteria against which the Supplied Software and all other Deliverables, including the Location Server System, will be tested and a detailed timetable for the performance of such Acceptance Tests; • Acceptance Criteria which, as a minimum, ensure the following:- • The Supplied Software and the other Deliverables, including the Location Server System, deliver the agreed functionality; • Existing functionality is not affected by the new service; • The Supplied Software and the other Deliverables, including the Location Server System, work in H3G’s Environment as required under this Agreement and any Work Package; • The components of the Location Server System and the other Deliverables integrate/interface with each other and integrate/interface with and will have no adverse effect on other systems installed in or services interfacing with H3G’s Environment including, without limitation, any systems or services provided by other H3G Service Providers; • The Supplied Software and the other Deliverables, including the Location Server System, perform within prescribed tolerances; • Any installation/required operating instructions are complete, accurate and usable; • Unless otherwise agreed in writing by the H3G Project Manager, the Supplied Software and other Deliverables can be managed and supported by existing service management tools and systems. The Acceptance Tests Plan shall require the agreement of H3G before being finalised for these purposes. • Testing shall, unless otherwise agreed in writing by the H3G Project Manager, comprise the following:- • Unit testing • Functional testing • Integration/Interface testing • Security testing • Performance testing • Volume/Stress testing • Reliability, recovery and contingency testing Note: Information in this document marked with a “[*]” has been omitted and filed separately with the U.S. Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. SCHEDULE Charges Schedule
