Test parameter variation Sample Clauses

Test parameter variation. The manufacturer shall declare the system boundaries to the Technical Service. The Technical Service shall define different combinations of test parameters (e.g. present speed of the ALKS vehicle, type and offset of target, curvature of lane) in order to cover scenarios in which a collision shall be avoided by the system as well as those in which a collision is not expected to be avoided, where applicable. If this is deemed justified, the Technical Service may test additionally any other combination of parameters. If a collision cannot be avoided for some test parameters, the manufacturer shall demonstrate either by documentation or, if possible, by verification/testing that the system doesn’t unreasonably switch its control strategy.
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs
Test parameter variation. 3.1.6.1. The manufacturer shall declare the system boundaries to the Type Approval Authority. The Type Approval Authority shall define different combinations of test parameters (e.g., present speed of the vehicle under test, type and offset of the target, curvature of lane). 3.1.6.2. In order to confirm consistency of the system, base tests shall be carried out at least 2 times. If one of the two test runs fails to meet the required performance, the test shall be repeated once. A test shall be accounted as passed if the required performance is met in two test runs and the manufacturer has provided sufficient evidence according to Annex 3 Appendix 4. The Type Approval Authority may choose to require additional test runs to confirm the declaration thresholds outlined in Annex 3 Appendix 4. 3.1.6.3. When conditions deviate from those specified for the base test, the system shall not unreasonably switch its control strategy. This shall be verified by the extended testing. Each parameter as outlined in the extended tests shall be varied, where variations can be grouped into a single test design. In addition, the Type Approval Authority may request additional documentation evidencing the system’s performance under parameter variations not tested.
Sample 1

Related to Test parameter variation

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.‌ b. A description or identification of the statistical sampling software package used by the IRO.‌

  • Implementation Report Within 150 days after the Effective Date, Halifax shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A.1, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A.2; 3. the names of the Board members who are responsible for satisfying the Board of Commissioners compliance obligations described in Section III.A.3; 4. a copy of Halifax’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be made available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions; and c. with respect to active medical staff members, the number and percentage who completed the training, the type of training and the date received, and a description of Halifax’s efforts to encourage medical staff members to complete the training. 8. a description of: (a) the Focus Arrangements Tracking System required by Section III.D.1.a; (b) the internal review and approval process required by Section III.D.1.e; and (c) the tracking and monitoring procedures and other Focus Arrangements Procedures required by Section III.D.1; 9. a description of the Disclosure Program required by Section III.F;

  • Supplemental Pricing Documents No response Optional. If when completing Pricing Form 1 & Pricing Form 2 you direct TIPS to view additional, alternate, or supplemental pricing documentation, you may upload that documentation.

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

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