Train Consist Data Sample Clauses
The Train Consist Data clause defines the requirements for providing detailed information about the composition and configuration of a train. This typically includes specifics such as the number and types of cars, their order, cargo details, and any special equipment or hazardous materials present. By mandating the sharing of this data, the clause ensures that all relevant parties have accurate and up-to-date information for operational planning, safety compliance, and efficient coordination, thereby reducing the risk of miscommunication and operational errors.
Train Consist Data. Network Rail shall calculate the Track Charges payable by the Train Operator in respect of each Period using the Train Consist Data supplied by the Train Operator and, to the extent such Train Consist Data is not available to Network Rail, the Default Train Consist Data.
Train Consist Data. The CVL IM shall calculate the Track Charges payable by the Train Operator in respect of each Period using the Train Consist Data supplied by the Train Operator and, to the extent such Train Consist Data is not available to the CVL IM, the Default Train Consist Data.
Train Consist Data. Not used.
Train Consist Data. The CVL IM shall calculate the Track Charges payable by the Train Operator in respect of each Period using the Train Consist Data supplied by the Train Operator and, to the extent such Train Consist Data is not available to the CVL IM, the Default Train Consist Data. Not used. For each Period, the CVL IM or its nominee shall be entitled to invoice the Train Operator for Track Charges in respect of any and all train movements operated by the Train Operator during that Period based on: Train Consist Data provided by the Train Operator in respect of any train movement at or prior to the time that such train movement is completed; not used; and not used. Each such invoice will be payable in accordance with the provisions of paragraph 11.1. Either party shall be entitled, at any time prior to the later of 23:59 hours on the fourteenth day following the expiration of the relevant Period and 7 days following receipt by the Train Operator of the relevant invoice or credit note, to notify the other that it objects to any Train Consist Data on which the whole or any part of the Track Charges included in the relevant invoice or credit note are based and any such notice shall specify in reasonable detail what that party believes to be the Train Consist Data for the relevant train movement(s) ("notice of objection"). For the avoidance of doubt, the Train Operator may serve a notice of objection in which it provides the relevant Train Consist Data where the Track Charges in the relevant invoice or credit note were based on the Default Train Consist Data. In the absence of any notice of objection being served within such time the Train Consist Data used in the relevant invoice or credit note shall be final and binding on the parties. The parties shall seek to agree the Train Consist Data specified in any notice of objection and any consequential financial adjustment required to the relevant invoice or credit note. If the parties are unable to agree such Train Consist Data within 14 days following receipt of a notice of objection, either party may refer the matter for resolution in accordance with the CVL ADRR. Within 14 days of any Train Consist Data being agreed or determined in accordance with paragraph 11.3(d), the CVL IM or its nominee shall, if any consequential or financial adjustment of the relevant invoice is required, issue a further invoice to, or (as the case may be) a credit note in favour of, the Train Operator in the amount of the relevant adjustment. The i...
Train Consist Data. (a) The Train Operator shall, 28 days before the start of each Period, provide to Network Rail details of its Planned Train Movements for that Period, including the Planned Train Consist Data for each train movement (the “Period Plan”);
(b) Network Rail shall, within 14 days of receiving the Period Plan, calculate the Variable Charge payable by the Train Operator in respect of the Period Plan (the “VTUCP”) using the Train Consist Data supplied by the Train Operator and, to the extent such Train Consist Data is not available to Network Rail, the Default Train Consist Data;
(c) The Train Operator shall pay the Variable Usage Charge in accordance with the provisions of paragraph 10.1 of this Schedule 7;
(d) The Train Operator shall, within 7 days of the end of each Period, provide to Network Rail details of its Actual Train Movements for that Period, including the Train Consist Data for each train movement (the “Period Actual”);
(e) Network Rail shall, within 14 days of receiving the Period Actual, calculate the Variable Usage Charge payable by the Train Operator in respect of the Period Actual (the “VTUCA”) using the Train Consist Data supplied by the Train Operator and, to the extent such Train Consist Data is not available to Network Rail, the Default Train Consist Data; and
(f) Network Rail shall, each period, compare the VTUCP with the VTUCA for the same period and:
(i) if the VTUCP exceeds the VTUCA, shall credit the Train Operator with the difference between the VTUCP and the VTUCA on the next following invoice issued in accordance with paragraph 10.1 of this Schedule 7; or
(ii) if the VTUCA exceeds the VTUCP, shall debit the Train Operator with the difference between the VTUCA and the VTUCP on the next following invoice issued in accordance with paragraph 10.1 of this Schedule 7.