Robustness Checklist Sample Clauses

Robustness Checklist. Before releasing any Licensed Product, Adopter must perform tests and analyses to assure compliance with these Robustness Rules. A Robustness Checklist is attached as Exhibit C-1 for the purpose of assisting Adopter in performing tests covering certain important aspects of these Robustness Rules. Inasmuch as the Robustness Checklist does not address all elements required for the manufacture of a Compliant product, Adopter is strongly advised to review carefully the Specification, Compliance Rules (including, for avoidance of doubt, these Robustness Rules) so as to evaluate thoroughly both its testing procedures and the compliance of its Licensed Products. Adopter shall provide copies of the Specification, the Compliance Rules (including, for avoidance of doubt, these Robustness Rules) and the Robustness Checklist to its supervisors responsible for design and manufacture of Licensed Products.
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
Robustness Checklist. Notice: This Checklist is intended as an aid to the correct implementation of the Robustness Rules for hardware and software implementations of the DTCP Specification in a Licensed Product. DTLA strongly recommends that you complete this Checklist for each hardware model or software version of a Licensed Product before releasing any product and at a sufficiently early date in design, as well as during production, to avoid product compliance redesign delays. This Checklist does not address all aspects of the Specification and Compliance Rules necessary to create a product that is fully compliant. Failure to perform necessary tests and analysis could result in a failure to comply fully with the Specification, Compliance Rules or Robustness Rules in breach of the DTLA Adopter Agreement and, as a consequence, in appropriate legal action of DTLA and Eligible Content Participants. DATE: MANUFACTURER: PRODUCT NAME: HARDWARE MODEL OR SOFTWARE VERSION: NAME OF TEST ENGINEER COMPLETING CHECKLIST: TEST ENGINEER: COMPANY NAME: COMPANY ADDRESS: PHONE NUMBER: FAX NUMBER: GENERAL IMPLEMENTATION QUESTIONS
Sample 1Sample 2Sample 3See All (6)
Robustness Checklist. The following subsections of the Agreement shall be amended as follows: 1.9.1 Exhibit G of the Agreement shall be renamed to “Robustness Checklist for Standard Devices”. 1.9.2 Exhibit G “Robustness Checklist for Standard Devices” shall be amended by replacing all occurrences of “Robustness Rules checklist” with “Robustness Checklist for Standard Devices”.
Sample 1Sample 2Sample 3
Robustness Checklist. Notice: This Checklist is intended as an aid to the correct implementation of the Robustness Rules for hardware and software implementations of the HDCP Specification in a Licensed Product. Licensor strongly recommends that you complete this Checklist for each hardware model or software version of a Licensed Product before releasing any product and at a sufficiently early date in design, as well as during production, to avoid product compliance redesign delays. This Checklist does not address all requirements necessary to create a product that is Compliant. Failure to perform the tests and analysis necessary to comply fully with the HDCP Specification, Compliance Rules or Robustness Rules could result in a breach of the HDCP License Agreement and appropriate legal action of Licensor and Eligible Content Participants. If any particular design or production work is being outsourced or handled by contractors to the company, compliance with the Robustness Rules remains the responsibility of this company. For review only - Not valid for execution DATE: MANUFACTURER: PRODUCT NAME: HARDWARE MODEL OR SOFTWARE VERSION: NAME OF TEST ENGINEER COMPLETING CHECKLIST: TEST ENGINEER: COMPANY NAME:
Sample 1
Robustness Checklist. Notice: This Checklist is intended as an aid to the correct implementation of the Robustness Rules for hardware and software implementations of the Referenced Technology in a Licensed Product. This Checklist does not address all aspects of the Referenced Technology and Compliance Rules necessary to create a product that is fully compliant. Failure to perform the tests and analysis necessary to comply fully with the Referenced Technology, Compliance Rules or Robustness Rules could result in a breach of this Agreement and appropriate legal action taken by CableLabs or other parties under the License Agreement. COMPANY ADDRESS: FAX NUMBER: 1 Has the Licensed Product been designed and manufactured so there are no switches, buttons, jumpers, or software equivalents of the foregoing, or specific traces that can be cut, by which the content protection technologies, analog protection systems, output restrictions, recording limitations, or other mandatory provisions of the Referenced Technology or Compliance Rules can be defeated or by which Controlled Content can be exposed to unauthorized copying? 2 Has the Licensed Product been designed and manufactured so there are no service menus and no functions (such as remote-control functions, switches, check boxes, or other means) that can intercept the flow of Controlled Content or expose it to unauthorized copying? 3 Has the Licensed Product been designed and manufactured so there are no service menus and no functions (such as remote-control functions, switches, check boxes, or other means) that can turn off any analog protection systems, output restrictions, recording limitations, or other mandatory provisions of the Referenced Technology or Compliance Rules?
Sample 1
Robustness Checklist. Notice: This Checklist is intended as an aid to the correct implementation of the Robustness Rules for hardware and software implementations of the Specifications in a Host Device. This Checklist does not address all aspects of the Specifications and Compliance Rules necessary to create a product that is fully compliant. Failure to perform the tests and analysis necessary to comply fully with the Specifications, Compliance Rules or Robustness Rules could result in a breach of the CableCARD Interface License Agreement and appropriate legal action taken by CableLabs or other parties under the License Agreement.
Sample 1
Robustness Checklist. Notice: This Checklist is intended as an aid to the correct implementation of the Robustness Rules for hardware and software implementations of the HDCP Specification in a Licensed Product. Licensor strongly recommends that you complete this Checklist for each hardware model or software version of a Licensed Product before releasing any product and at a sufficiently early date in design, as well as during production, to avoid product compliance redesign delays. This Checklist does not address all requirements necessary to create a product that is Compliant. Failure to perform the tests and analysis necessary to comply fully with the HDCP Specification, Compliance Rules or Robustness Rules could result in a breach of the HDCP License Agreement and appropriate legal action of Licensor and Eligible Content Participants. If any particular design or production work is being outsourced or handled by contractors to the company, compliance with the Robustness Rules remains the responsibility of this company.
Sample 1
AutoNDA by SimpleDocs
Robustness Checklist. Notice: This checklist is intended as an aid to the implementation of the Robustness Rules for the Hardware and the Software implementations of the SVR CP Specifications in a Licensed Product. Sony strongly recommends that Licensee complete this Checklist for each Licensed Product before releasing any License Product and at a sufficiently early date in design, as well as during production, to avoid product compliance redesign delays. This Checklist does not address all aspects of the SVR CP Specifications and the Compliance Rules necessary to create a Licensed Product that is fully compliant. Failure to perform necessary tests and analysis could result in a failure to comply fully with the SVR CP Specifications, the Compliance Rules or the Robustness Rules in breach of the Agreement and, as a consequence, in appropriate legal action of Sony and Eligible Content Participants. Notwithstanding whether any particular design or production work is being outsourced or handled by Subcontractors to Licensee, compliance with the above Robustness Rules remains the responsibility of the Licensee. Date: Manufacturer: Product Name: Hardware Model or Software Version: Name of Test Engineer Completing Checklist: Test Engineer: Company Name: Company Address: Phone Name: Fax Number:
Sample 1

Related to Robustness Checklist

  • Checklist The Service will be able to respond more quickly to a VCP request if the request is carefully prepared and complete. The checklist in Appendix C is designed to assist Plan Sponsors and their representatives in preparing a submission that contains the information and documents required under this revenue procedure. The checklist in Appendix C must be completed, signed, and dated by the Plan Sponsor or the Plan Sponsor's representative. A photocopy of this checklist may be used.

  • Inspection Checklist (Check one)

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • ATTACHMENT C STANDARD STATE PROVISIONS FOR CONTRACTS AND GRANTS

  • Money Market Fund Compliance Testing and Reporting Services Subject to the authorization and direction of the Trust and, in each case where appropriate, the review and comment by the Trust’s independent accountants and legal counsel, and in accordance with procedures that may be established from time to time between the Trust and the Administrator, the Administrator will:

  • PERFORMANCE MANAGEMENT SYSTEM 6.1 The Performance Plan (Annexure A) to this Agreement sets out – 6.1.1 The standards and procedures for evaluating the Employee’s performance; and 6.1.2 The intervals for the evaluation of the Employee’s performance. 6.2 Despite the establishment of agreed intervals for evaluation, the Employer may in addition review the Employee’s performance at any stage while the contract of employment remains in force; 6.3 Personal growth and development needs identified during any performance review discussion must be documented in a Personal Development Plan as well as the actions agreed to and implementation must take place within set time frames; 6.4 The Employee’s performance will be measured in terms of contributions to the goals and strategies set out in the Employer’s Integrated Development Plan (IDP) as described in 6.6 – 6.12 below; 6.5 The Employee will submit quarterly performance reports (SDBIP) and a comprehensive annual performance report at least one week prior to the performance assessment meetings to the Evaluation Panel Chairperson for distribution to the panel members for preparation purposes; 6.6 Assessment of the achievement of results as outlined in the performance plan: 6.6.1 Each KPI or group of KPIs shall be assessed according to the extent to which the specified standards or performance targets have been met and with due regard to ad-hoc tasks that had to be performed under the KPI, and the score of the employer will be given to and explained to the Employee during the assessment interview. 6.6.2 A rating on the five-point scale shall be provided for each KPI or group of KPIs which will then be multiplied by the weighting to calculate the final score; 6.6.3 The Employee will submit his self-evaluation to the Employer prior to the formal assessment; 6.6.4 In the instance where the employee could not perform due to reasons outside the control of the employer and employee, the KPI will not be considered during the evaluation. The employee should provide sufficient evidence in such instances; and 6.6.5 An overall score will be calculated based on the total of the individual scores calculated above.

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.

  • Program Monitoring and Evaluation The Recipient shall prepare, or cause to be prepared, and furnish to the Association not later than six months after the Closing Date, a report of such scope and in such detail as the Association shall reasonably request, on the execution of the Program, the performance by the Recipient and the Association of their respective obligations under the Legal Agreements and the accomplishment of the purposes of the Financing.”

  • Standard Operating Procedures Standard Operating Procedures shall not contravene the Canada Labour Code, the Canadian Human Rights Code, or the Collective Agreement, and an allegation of such contravention is subject to the grievance procedure.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!