VDOT Special Provisions Sample Clauses

VDOT Special Provisions. 1.1.6. VDOT Road and Bridge Specifications
AutoNDA by SimpleDocs
VDOT Special Provisions. 1.1.6. VDOT Road and Bridge Specifications City of Roanoke, VA Hierarchy of Construction Documents

Related to VDOT Special Provisions

  • Special Provisions Check if Required ✔ If checked, the Supplemental State Terms and attached hereto as Exhibit “G” are hereby incorporated by reference into this DPA in their entirety. ✔ If checked, the Provider, has signed Exhibit “E” to the Standard Clauses, otherwise known as General Offer of Privacy Terms

  • SPECIAL PROVISION The failure of the COUNTY to insist upon the strict performance of any provision of this Agreement or to exercise any right based upon breach thereof or the acceptance of any performance during such breach shall not constitute a waiver of any right under this Agreement.

  • Initial Provisions Establishment of a Free Trade Area

  • Financial Provisions 7.1 You are responsible for: (a) the setup of the Merchant Account with the Merchant Acquiring Bank and the bank’s processor; and (b) any and all set up and Bank Charges and other charges associated with the Merchant Account. 7.2 NCR Voyix cannot guarantee that the chosen Merchant Acquiring Bank can accept Transactions via the EMV PSP Service. NCR Voyix reserves the right to charge you an additional development fee to cover costs in the event that the Merchant Acquiring Bank requires NCR Voyix or its third-party suppliers to complete an accreditation procedure with respect to the EMV PSP Service or the Terminal.

  • Final Provisions Clause 16

  • Remedial Provisions Each Grantor covenants and agrees with the Administrative Agent and the other Secured Parties that, from and after the date of this Agreement until the Discharge of Obligations:

  • Transitional Provisions 24.1. As from the official date of entry into force of the 01 series of amendments to this Regulation, no Contracting Party applying this Regulation shall refuse to grant or refuse to accept type approval under this Regulation as amended by the 01 series of amendments. 24.2. As from 12 months after the date of entry into force of the 01 series of amendments to this Regulation, Contracting Parties applying this Regulation shall grant approvals only if the type of components to be approved meets the requirements of Part I of this Regulation as amended by the 01 series of amendments to this Regulation. 24.3. Type approvals of components other than fuel rail, as defined in paragraph 4.72., granted according to the original version of this Regulation or of components granted according to the 01 series of amendments, shall remain valid and shall be accepted for the purpose of their installation on vehicles as long as the requirements for the specific component have not changed by any series of amendments. 24.4. As from 18 months after the date of entry into force of the 01 series of amendments to this Regulation, Contracting Parties applying this Regulation shall grant approvals only if the vehicle type to be approved meets the requirements of Part II of this Regulation as amended by the 01 series of amendments to this Regulation. 24.5. Until 12 months after the date of entry into force of the 01 series of amendments to this Regulation, Contracting Parties applying this Regulation can continue to grant type approvals for the type of components to the original version of this Regulation without taking into account the provisions of the 01 series of amendments. 24.6. Until 18 months after the date of entry into force of the 01 series of amendments to this Regulation, Contracting Parties applying this Regulation can continue to grant type approvals for the vehicle type to the original version of this Regulation without taking into account the provisions of the 01 series of amendments. 24.7. Notwithstanding the provisions of paragraphs 24.5. and 24.6., Contracting Parties applying this Regulation shall not refuse to grant extensions of type approvals for existing types of component or vehicle types which have been issued according to this Regulation without taking into account the provisions of the 01 series of amendments to this Regulation. 24.8. As from the official date of entry into force of the 02 series of amendments to this Regulation, no Contracting Party applying this Regulation shall refuse to grant or refuse to accept type approval under this Regulation as amended by the 02 series of amendments. 24.9. As from 1 September 2017 Contracting Parties applying this Regulation shall grant approvals only if the type of components to be approved meets the requirements of Part I of this Regulation as amended by the 02 series of amendments to this Regulation. 24.10. As from 1 September 2018 Contracting Parties applying this Regulation shall grant approvals only if the vehicle type to be approved meets the requirements of Part II of this Regulation as amended by the 02 series of amendments to this Regulation. 24.11. As from 1 September 2019 Contracting Parties applying this Regulation may refuse to recognize approvals of a type of vehicle which have not been granted in accordance with Part II of this Regulation as amended by the 02 series of amendments to this Regulation. 24.12. Contracting Parties applying this Regulation shall not refuse to grant extensions of type approvals for existing types of component or vehicle types which have been issued according to this Regulation without taking into account the provisions of the 02 series of amendments to this Regulation. 24.13. Notwithstanding paragraphs 24.11. and 24.12., Contracting Parties applying this Regulation shall continue to accept type approvals granted to the preceding series of amendments, which are not affected by the 02 series of amendments.

  • Local Provisions (Local provisions related to these scheduling arrangements are to be set out in this Article and numbered in sequence.)

  • Special Provisions for Affected Systems For the re-payment of amounts advanced to Affected System Operator for System Upgrade Facilities or System Deliverability Upgrades, the Developer and Affected System Operator shall enter into an agreement that provides for such re-payment, but only if responsibility for the cost of such System Upgrade Facilities or System Deliverability Upgrades is not to be allocated in accordance with Attachment S to the ISO OATT. The agreement shall specify the terms governing payments to be made by the Developer to the Affected System Operator as well as the re-payment by the Affected System Operator.

  • Definitional Provisions For purposes of this Agreement, (i) those words, names, or terms which are specifically defined herein shall have the meaning specifically ascribed to them; (ii) wherever from the context it appears appropriate, each term stated either in the singular or plural shall include the singular and plural; (iii) wherever from the context it appears appropriate, the masculine, feminine, or neuter gender, shall each include the others; (iv) the words “hereof”, “herein”, “hereunder”, and words of similar import, when used in this Agreement, shall refer to this Agreement as a whole, and not to any particular provision of this Agreement; (v) all references to “Dollars” or “$” shall be construed as being United States Dollars; (vi) the term “including” is not limiting and means “including without limitation”; and, (vii) all references to all statutes, statutory provisions, regulations, or similar administrative provisions shall be construed as a reference to such statute, statutory provision, regulation, or similar administrative provision as in force at the date of this Agreement and as may be subsequently amended.

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