Rail Operator Request for New or Varied Clause Samples

Rail Operator Request for New or Varied. Core Train Path or Ad Hoc Train Path (a) The Rail Operator may request a new or varied Core Train Path or an Ad Hoc Train Path at any time by submitting an 'Application for New or Varied Train Path' in accordance with the Operations Protocol. (b) RailCorp must deal with that request in accordance with the procedures set out in the Operations Protocol. (c) RailCorp must use its reasonable endeavours to provide to the Rail Operator any new or varied Core Train Path or Ad Hoc Train Path requested by the Rail Operator subject to: (i) availability of capacity on the Network; (ii) the reliability of the Network; (iii) the bona fide requirements of existing and/or prospective users of the Network for the requested Train Path; (iv) the agreement or determination on revised Access Charges in accordance with clause 4.2; (v) Passenger Priority; and (vi) compliance with the Train Operating Specifications. (d) A new or varied Core Train Path requested by the Rail Operator in accordance with clause 5.7(a) and allocated by RailCorp to the Rail Operator in accordance with this clause 5.7 shall be incorporated into the Standard Working Timetable.

Related to Rail Operator Request for New or Varied

  • LOAN SERVICES ADDENDUM If a Fund directs the Custodian in writing to perform loan services, the Custodian and the Fund will be bound by the terms of the Loan Services Addendum attached hereto. The Fund shall reimburse Custodian for its fees and expenses related thereto as agreed upon from time to time in writing by the Fund and the Custodian.

  • Attachment A, Scope of Services The scope of services is amended as follows:

  • Attachment  C_ CONTRACT AFFIRMATIONS For purposes of these Contract Affirmations, HHS includes both the Health and Human Services Commission (HHSC) and the Department of State Health Services (DSHS). System Agency refers to HHSC, DSHS, or both, that will be a party to this Contract. These Contract Affirmations apply to all Contractors and Grantees (referred to as “Contractor”) regardless of their business form (e.g., individual, partnership, corporation). By entering into this Contract, Contractor affirms, without exception, understands, and agrees to comply with the following items through the life of the Contract:

  • Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.

  • Emergency Operator Access Registry Operator shall provide bulk access to the zone files for the TLD to the Emergency Operators designated by ICANN on a continuous basis in the manner ICANN may reasonably specify from time to time.