Fuel system integrity requirements. 5.5.1. In the case of a vehicle propelled by fuel with a boiling point above 0 °C, fuel ballast leakage from the fuel system(s)6 prepared in accordance with paragraph 5.1. of Annex 3 shall not exceed:
Fuel system integrity requirements Sample Clauses
Related to Fuel system integrity requirements
Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”).
Quality Requirements Performance Indicator Heading Indicator (specific) Threshold Method of Measurement Frequency of monitoring Consequence of Breach QUALITY Patient Safety - Incidents I1 Number of incidents Adverse incidents include the following: clinical or non clinical adverse events that have potential to cause avoidable harm to a patient, including medical errors or adverse events related to medical devices or other equipment. Clinical or non- clinical accidents, accidental injuries to staff and members of the public, verbal, physical or psychological abuse or harassment, unusual or dangerous occurrences, damage to trust property, plant or equipment, fire or flood, security, theft or loss, near misses are identified as any event where under different circumstances significant injury or loss may have occurred Number of recorded incidents in the contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed I2 Number of Sis Definition of SUI according to trust policy and national guidance Number of Serious Untoward Incidents reported in contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed S1 Percentage of eligible staff received child safeguarding training at level 2 (as identified in LSCB training strategy) 95% Number received training/ Number of identified staff requiring training Monthly S2 Percentage of eligible staff received adult safeguarding awareness training at level 2 ( as identified in K&M Safeguarding Vulnerable Adults training strategy) 95% Number of staff trained/ Number of identified staff requiring training Monthly
City Requirements Design, construction, materials, sizing, other specifications, permitting, inspections, testing, documentation and furnishing of as-built drawings, and acceptance of completed infrastructure shall be in accordance with City Requirements. Design and construction shall be by professionals licensed in the state of North Carolina to do the relevant work. City approval of the design of the Improvements shall be required prior to construction, as set forth in City Requirements. If Developer is connecting to the County sewer system, the City may require Developer to furnish the contract providing for such connection.
E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.
Technology Requirements The Customer is required to obtain and maintain, at the Customer’s own expense, compatible Electronic Channels, hardware, operating systems, and software approved for such use by Royal Bank, and which are up-to-date and unaltered from manufacturer specifications. Royal Bank is not responsible for, and makes no representations or warranties of any nature, with respect to any such Electronic Channels, hardware, operating systems, and software provided by any other Person. Royal Bank has the right, in its sole discretion, without notice, to make changes to this Service from time to time which may result in the Customer’s Electronic Channels, hardware, operating systems, and software no longer being compatible with this Service, and in such event, Royal Bank will have no responsibility or liability to the Customer or any other Person.
Safety Requirements 18.1.1 The Concessionaire shall comply with the provisions of this Agreement, Applicable Laws and Applicable Permits and conform to Good Industry Practice for securing the safety of the Users. In particular, the Concessionaire shall develop, implement and administer a surveillance and safety program for providing a safe environment on or about the Project, and shall comply with the safety requirements set forth in Schedule-L (the “Safety Requirements”).
Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.
Security Requirements 11.1 The Supplier shall comply, and shall procure the compliance of the Suppliers Personnel, with the Security Policy and the Security Plan and the Supplier shall ensure that the Security Plan produced by the Supplier fully complies with the Security Policy.
