Bookings for Parking Sample Clauses

Bookings for Parking. Spaces existing at the date of termination shall remain unaffected by termination (however caused) of the Agreement.
AutoNDA by SimpleDocs

Related to Bookings for Parking

  • Network Maintenance and Management 36.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result.

  • Conditions for Participation 1. A procuring entity shall limit any conditions for participation in a procurement to those that are essential to ensure that a supplier has the legal and financial capacities and the commercial and technical abilities to undertake the relevant procurement.

  • RECORDS MANAGEMENT AND MAINTENANCE 35 A. CONTRACTOR, its officers, agents, employees and subcontractors shall, throughout the term 36 of this Agreement, prepare, maintain and manage records appropriate to the services provided and in 37 accordance with this Agreement and all applicable requirements.

  • Directory To participate in the MnDOT TGB program, a business must be certified at the time of contract execution. Certified Targeted Group Businesses are listed in the Directory of Certified Targeted Group, Economically Disadvantaged and VET Vendors. MnDOT makes no representation as to any TGB’s technical or financial ability to perform the work. Prime contractors are solely responsible for performing due diligence in hiring TGB firms. A TGB’s failure to perform the work will not be considered justification for a compensation increase or time extension.

  • Operating and Maintenance Expenses Subject to the provisions herein addressing the use of facilities by others, and except for operations and maintenance expenses associated with modifications made for providing interconnection or transmission service to a third party and such third party pays for such expenses, the Interconnection Customer shall be responsible for all reasonable expenses including overheads, associated with: (1) owning, operating, maintaining, repairing, and replacing the Interconnection Customer’s Interconnection Facilities; and (2) operation, maintenance, repair and replacement of the Participating TO’s Interconnection Facilities.

  • Planned Maintenance (a) Sellers may designate up to twenty (20) Days of Planned Maintenance on Sellers’ Facilities during each Contract Year. Sellers shall be entitled to reduce (including down to zero (0)) its Gas scheduling under Clause 8 and Exhibit 3 for each Day of Planned Maintenance.

  • Applications for Payment 9.3.1 At least ten days before the date for each progress payment established in the State- Contractor Agreement, the Contractor shall submit to the Architect an itemized Application for Payment, notarized if required, supported by such data substantiating the Contractor's right to payment as the State or the Architect may require. The application for payment must, at a minimum, reflect retainage and the required waivers of lien and any other support documentation enumerated elsewhere in the Contract Documents.

  • Record Maintenance and Retention A. Grantee shall keep and maintain under GAAP or GASB, as applicable, full, true, and complete records necessary to fully disclose to the System Agency, the Texas State Auditor’s Office, the United States Government, and their authorized representatives sufficient information to determine compliance with the terms and conditions of this Grant Agreement and all state and federal rules, regulations, and statutes.

  • Reservations for Registry Operations 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Operating and Maintenance Manuals 58.1 If “as built” Drawings and/or operating and maintenance manuals are required, the Contractor shall supply them by the dates stated in the Contract Data.

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