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 (10)
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. Notwithstanding whether any particular design or production work is being outsourced or handled by contractors to the company, compliance with the above Rules remains the responsibility of this company. 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 (5)
Robustness Checklist. The following subsections of the Agreement shall be amended as follows:
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: GENERAL IMPLEMENTATION QUESTIONS
Sample 1
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: General Implementation Questions
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. 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 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. 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 1
AutoNDA by SimpleDocs

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, and should be placed on top of the submission. A photocopy of this checklist may be used.

  • Inspection Checklist (check one) ☐ In order to avoid disagreements about the condition of the Premises, at the time of accepting possession of the Premises, Tenant will complete the Inspection Checklist incorporated herein by reference and attached hereto as Exhibit B and record any damage or deficiencies that exist at the commencement of the Term. Landlord will be liable for the cost of any cleaning or repair to correct damages found at the time of the inspection. Tenant will be liable for the cost of any cleaning and/or repair to correct damages found at the end of the Term if not recorded on the inspection checklist, normal wear and tear excepted. ☐ The Tenant is NOT required to complete an inspection checklist.

  • IN CHECKLIST At the time of taking possession of the Premises by the Sublessee, the Sublessor and Sublessee: (check one) ☐ - WILL be required to complete a move-in checklist that provides a detailed account of the condition of the Premises including, but not limited to, repairs needed, water damage, or material defects. ☐ - Will NOT be required to complete a move-in checklist that provides a detailed accounting of the condition of the Premises, unless otherwise required by law.

  • Scheduling Checkout Protocols 35.13.1.1 Both Parties shall require all transaction schedules to be tagged in accord with the NERC tagging standard. For reserve sharing and other emergency schedules that are not tagged, the Parties will enter manual schedules after the fact into their respective scheduling systems.

  • ATTACHMENT C STANDARD STATE PROVISIONS FOR CONTRACTS AND GRANTS

  • Drug Testing Procedures a. The testing procedures and safeguards provided in this policy shall be adhered to by any laboratory personnel administering departmental drug tests.

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopts or introduces for the Employer, management and municipal staff of the Employer.

  • 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.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

Time is Money Join Law Insider Premium to draft better contracts faster.