Use of Railway Code Systems Sample Clauses

Use of Railway Code Systems. (A) The parties shall use the Railway Code Systems in their dealings with each other in connection with matters provided for in this Agreement. Both parties shall observe and comply with the provisions of the Systems Code. (B) Nexus consents to the use by Network Rail of any data or information supplied by Nexus to Network Rail in the course of complying with its Safety Obligations for the purpose of monitoring Nexus’ performance of its obligations under this Agreement and calculating the amount of Track Charges.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Use of Railway Code Systems. 6.1 [Not used] 6.2 [Not used] 6.3 [Not used] 6.4 [Not used]
Sample 1Sample 2See All (4)
Use of Railway Code Systems. The parties shall: use the Railway Code Systems and any other applicable System in their dealings with each other in connection with matters provided for in this Agreement; and comply with the Systems Code on the CVL, provided that for the purposes of this clause, the CVL IM shall only be required to comply with limb (a) of the definition of the Systems Code on the CVL as a "User" (as such term is defined in the Code of Practice relating to the Management and Development of Railway Information Systems). Without prejudice to Clause 7.4(A), the Train Operator shall: provide to the CVL IM train consist data; and ensure that such data is true and accurate as far as is reasonable in the circumstances. The Train Operator shall notify the CVL IM of any movement onto the CVL and off the CVL of any railway vehicle under the control of the Train Operator by promptly making a full and accurate train release or acceptance entry to the appropriate Railway Code Systems or Applicable System. The Train Operator consents to the use by the CVL IM of any data or other information supplied by the Train Operator to the CVL IM in the course of complying with its Safety Obligations for the purpose of monitoring the Train Operator's performance of its obligations under this Agreement. INDEMNITIES AND LIABILITY FOR PERFORMANCE
Sample 1Sample 2
Use of Railway Code Systems. Track Charges and other payments‌ Schedule 7 shall have effect.
Sample 1Sample 2
Use of Railway Code Systems. (A) The parties shall: (1) use the Railway Code Systems and any other applicable System in their dealings with each other in connection with matters provided for in this Agreement; and (2) comply with the Systems Code on the CVL, provided that for the purposes of this clause, the CVL IM shall only be required to comply with limb (a) of the definition of the Systems Code on the CVL as a "User" (as such term is defined in the Code of Practice relating to the Management and Development of Railway Information Systems). (B) Without prejudice to Clause 7.4(A), the Train Operator shall: (1) provide to the CVL IM train consist data; and (2) ensure that such data is true and accurate as far as is reasonable in the circumstances. (C) The Train Operator shall notify the CVL IM of any movement onto the CVL and off the CVL of any railway vehicle under the control of the Train Operator by promptly making a full and accurate train release or acceptance entry to the appropriate Railway Code Systems or Applicable System. (D) The Train Operator consents to the use by the CVL IM of any data or other information supplied by the Train Operator to the CVL IM in the course of complying with its Safety Obligations for the purpose of monitoring the Train Operator's performance of its obligations under this Agreement.
Sample 1
Use of Railway Code Systems. 6.5.1 General (a) use the Railway Code Systems and any other Applicable System in their dealings with each other in connection with matters provided for in this contract; and (b) comply with the Systems Code. 6.5.2 Provision of train consist data (a) provide to Network Rail such train consist data as shall be necessary to enable Network Rail to calculate the amount of Track Charges; and (b) ensure that such data is true and accurate as far as is reasonable in the circumstances. 6.5.3 Notification of movement on to and off the Network 6.5.4 Network Rail audit (a) carry out checks and inspections necessary to establish whether the Train Operator is complying with its obligations under this Clause 6.5; and (b) carry out such inspections of the books and records kept by or on behalf of the Train Operator in connection with the Services as Network Rail may reasonably consider to be necessary for such purpose. 6.5.5 Notice of audit (a) give to the Train Operator reasonable written notice of the checks and inspections to be carried out in accordance with Clause 6.5.4; and (b) ensure that the checks and inspections are carried out between 09:00 hours and 17:00 hours on a Working Day. 6.5.6 Material discrepancy (a) the Train Operator shall pay the reasonable costs incurred by Network Rail in carrying out the checks and inspections in accordance with Clauses 6.5.4 and 6.5.5; and (b) Network Rail shall: (i) $ make the appropriate and consequent adjustments to the Track Charges; and (ii) $ provide to the Train Operator evidence of such costs as the Train Operator may reasonably request. 6.5.7 Consent to use information (a) monitoring the Train Operator’s performance of its obligations under this contract; and (b) calculating the amount of Track Charges.
Sample 1
Use of Railway Code Systems. The parties shall: (a) use the Railway Code Systems in their dealings with each other in connection with matters provided for in this contract; and (b) comply with the Systems Code.
Sample 1
AutoNDA by SimpleDocs
Use of Railway Code Systems. Track Charges and other payments
Sample 1
Use of Railway Code Systems 
Sample 1Sample 2Sample 3See All (150)

Related to Use of Railway Code Systems

  • Use of Facilities 34.1. In situations where the CLEC has the use of the facilities (i.e., local loop) to a specific customer premise, either through resale of local service or the lease of the local loop as an Unbundled Network Element, and Sprint receives a good faith request for service from a customer at the same premise or from another carrier with the appropriate customer authorization, the procedures below will apply. 34.1.1. Sprint will process such orders and provision services consistent with the terms contained in Section 82, of this Agreement. 34.1.2. Where CLEC is using a single facility to provide service to multiple end user customers, Sprint will not disconnect that facility as a result of the following procedures. 34.1.3. Sprint will follow methods prescribed by the FCC and any applicable state regulation for carrier change verification. 34.1.4. Customer with Existing Service Changing Local Service Provider 34.1.4.1. In situations where a CLEC submits an order for an end user customer that is changing local service providers for existing service, and is not adding service (i.e., an additional line), Sprint will process the service request without delay, and provide the losing local service provider a customer loss notification consistent with industry standards. 34.1.5. Customer with Existing Service Adding New Service 34.1.5.1. In situations where an order is submitted for an end user customer adding service to existing service (i.e., an additional line), the order should be marked as an additional line and CLEC’s facilities will not be affected. 34.1.6. Customer Requesting New Service where Previous Customer has Abandoned Service 34.1.6.1. In the case where an end user customer vacates premises without notifying the local service provider and a new end user customer moves into the vacated premises and orders new service from a local service provider neither Sprint nor the previous local service provider are aware that the original end user customer has abandoned the service in place. 34.1.6.2. When a carrier requests service at a location and marks the order as abandoned and CLEC is the previous local service provider, Sprint shall notify CLEC via fax that it has had a request for service at the premise location that is currently being served by CLEC; 34.1.6.3. If available to Sprint, Sprint shall include the name and address of the party receiving service at such locations, but at a minimum shall provide local service address location information; 34.1.7. If CLEC does not respond within twenty-four (24) hours after receiving Sprint’s notification or if CLEC responds relinquishing the facilities, Sprint shall be free to use the facilities in question and Sprint shall issue a disconnect order with respect to the CLEC service at that location. If CLEC responds stating that the service is working and should not be disconnected, Sprint will notify the carrier ordering service and request verification of the address and location or the submission of an order for an additional line.

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