Common use of Sustained Planned Disruption Clause in Contracts

Sustained Planned Disruption. (a) If either party reasonably believes that a Sustained Planned Disruption has occurred then that party will be entitled to require that the costs and losses for the Restrictions of Use for the relevant services during the relevant SPD Period be calculated in accordance with paragraph 8 by serving a notice on the other (an "SPD Notice") in accordance with paragraph 2.10(b). (b) Unless otherwise agreed in writing, an SPD Notice must be served no later than the day falling 56 days after the issue of the Day 42 Statement which followed the end of the relevant SPD Period and must include a short explanation of why it reasonably believes a Sustained Planned Disruption has occurred and a statement of when the SPD Period commenced. (c) Following the issue of an SPD Notice, either party may serve a notice (an "SPD Termination Notice") stating that it reasonably believes that the relevant Sustained Planned Disruption is no longer occurring, such notice to include a short explanation of why the party serving it reasonably believes that the Sustained Planned Disruption has ceased and stating the Period in which such cessation has occurred. A party receiving an SPD Termination Notice shall within 30 days of its receipt by notice to the serving party either accept or reject the SPD Termination Notice and where it rejects the notice it shall include with its rejection notice a short explanation of why it reasonably believes the Sustained Planned Disruption is continuing. If the parties fail to reach agreement within 30 days after service of a rejection notice, or if prior to that date both parties agree that agreement is unlikely to be reached prior to that date, either party may notify the other that the dispute resolution procedure set out in paragraph 13.3 is to apply (save that references to paragraph 13.2 shall be construed as being references to this paragraph). (d) Following the issue of an SPD Notice the party that issued that notice must serve a claim (an "SPD Claim"): (i) no later than the day falling 112 days after the issue of the Day 42 Statement for the last Period in the relevant SPD Period; or (ii) where an SPD Period has exceeded 13 consecutive Periods in length or upon the termination or expiry of this contract, whichever comes first, unless otherwise agreed in writing, no later than the day falling 112 days after the issue of the Day 42 Statement which followed the 13th consecutive Period or the termination or expiry of this contract (as applicable), whichever is the earlier. (e) Provided a party has issued an SPD Notice in accordance with paragraph 2.10(b), nothing in paragraph 2.10(d) shall prevent that party from issuing more than one SPD Claim in respect of the same Sustained Planned Disruption, provided that: (i) each such SPD Claim relates to a different period within the said SPD Period (so there is no double-counting); and (ii) no SPD Claim can be issued after the last day for serving notice specified under paragraph 2.10(d). (f) An SPD Claim must include details of when and why that party reasonably believes that a Sustained Planned Disruption has occurred and in particular: (i) if the claim is made by the Train Operator, such details as may reasonably be available of the RoU Liability which the Train Operator has incurred or reasonably expects to incur in respect of the relevant Restrictions of Use during the SPD Period; or (ii) if the claim is made by Network Rail, the reasons why Network Rail reasonably believes that the Train Operator has been overcompensated or may be overcompensated by more than the relevant amount. (g) Following the service of an SPD Claim, if and to the extent it is agreed or determined that a Sustained Planned Disruption has occurred in the period covered by the claim then the relevant party shall make payments to the other (in accordance with the procedure in paragraph 13) calculated in accordance with paragraph 8 in respect of the SPD Period (or where applicable the part of the SPD Period) covered by the SPD Claim.

Appears in 34 contracts

Samples: Track Access Contract (Passenger Services), Track Access Contract (Passenger Services), Track Access Contract (Passenger Services)

AutoNDA by SimpleDocs

Sustained Planned Disruption. (a) If either party reasonably believes that a Sustained Planned Disruption has occurred then that party will be entitled to require that the costs and losses for the Restrictions of Use for the relevant services during the relevant SPD Period be calculated in accordance with paragraph 8 by serving a notice on the other (an "SPD Notice") in accordance with paragraph 2.10(b). (b) Unless otherwise agreed in writing, an SPD Notice must be served no later than the day falling 56 days after the issue of the Day 42 Statement which followed the end of the relevant SPD Period and must include a short explanation of why it reasonably believes a Sustained Planned Disruption has occurred and a statement of when the SPD Period commenced. (c) Following the issue of an SPD Notice, either party may serve a notice (an "SPD Termination Notice") stating that it reasonably believes that the relevant Sustained Planned Disruption is no longer occurring, such notice to include a short explanation of why the party serving it reasonably believes that the Sustained Planned Disruption has ceased and stating the Period in which such cessation has occurred. A party receiving an SPD Termination Notice shall within 30 days of its receipt by notice to the serving party either accept or reject the SPD Termination Notice and where it rejects the notice it shall include with its rejection notice a short explanation of why it reasonably believes the Sustained Planned Disruption is continuing. If the parties fail to reach agreement within 30 days after service of a rejection notice, or if prior to that date both parties agree that agreement is unlikely to be reached prior to that date, either party may notify the other that the dispute resolution procedure set out in paragraph 13.3 is to apply (save that references to paragraph 13.2 shall be construed as being references to this paragraph). (d) Following the issue of an SPD Notice the party that issued that notice must serve a claim (an "SPD Claim"): (i) no later than the day falling 112 days after the issue of the Day 42 Statement for the last Period in the relevant SPD Period; or (ii) where an SPD Period has exceeded 13 consecutive Periods in length or upon the termination or expiry of this contract, whichever comes first, unless otherwise agreed in writing, no later than the day falling 112 days after the issue of the Day 42 Statement which followed the 13th consecutive Period or the termination or expiry of this contract (as applicable), whichever is the earlier. (e) Provided a party has issued an SPD Notice in accordance with paragraph 2.10(b), nothing in paragraph 2.10(d) shall prevent that party from issuing more than one SPD Claim in respect of the same Sustained Planned Disruption, provided that: (i) each such SPD Claim relates to a different period within the said SPD Period (so there is no double-counting); and (ii) no SPD Claim can be issued after the last day for serving notice specified under paragraph 2.10(d). (f) An SPD Claim must include details of when and why that party reasonably believes that a Sustained Planned Disruption has occurred and in particular: (i) if the claim is made by the Train Operator, such details as may reasonably be available of the RoU Liability which the Train Operator has incurred or reasonably expects to incur in respect of the relevant Restrictions of Use during the SPD Period; or (ii) if the claim is made by Network Railthe CVL IM, the reasons why Network Rail the CVL IM reasonably believes that the Train Operator has been overcompensated or may be overcompensated by more than the relevant amount. (g) Following the service of an SPD Claim, if and to the extent it is agreed or determined that a Sustained Planned Disruption has occurred in the period covered by the claim then the relevant party shall make payments to the other (in accordance with the procedure in paragraph 13) calculated in accordance with paragraph 8 in respect of the SPD Period (or where applicable the part of the SPD Period) covered by the SPD Claim.

Appears in 7 contracts

Samples: Track Access Contract, Track Access Contract, Track Access Contract

Sustained Planned Disruption. (a) If either party reasonably believes that a Sustained Planned Disruption has occurred then that party will be entitled to require that the costs and losses for the Restrictions of Use for the relevant services during the relevant SPD Period be calculated in accordance with paragraph 8 by serving a notice on the other (an "SPD Notice") in accordance with paragraph 2.10(b). (b) Unless otherwise agreed in writing, an SPD Notice must be served no later than the day falling 56 days after the issue of the Day 42 Statement which followed the end of the relevant SPD Period and must include a short explanation of why it reasonably believes a Sustained Planned Disruption has occurred and a statement of when the SPD Period commenced. (c) Following the issue of an SPD Notice, either party may serve a notice (an "SPD Termination Notice") stating that it reasonably believes that the relevant Sustained Planned Disruption is no longer occurring, such notice to include a short explanation of why the party serving it reasonably believes that the Sustained Planned Disruption has ceased and stating the Period in which such cessation has occurred. A party receiving an SPD Termination Notice shall within 30 days of its receipt by notice to the serving party either accept or reject the SPD Termination Notice and where it rejects the notice it shall include with its rejection notice a short explanation of why it reasonably believes the Sustained Planned Disruption is continuing. If the parties fail to reach agreement within 30 days after service of a rejection notice, or if prior to that date both parties agree that agreement is unlikely to be reached prior to that date, either party may notify the other that the dispute resolution procedure set out in paragraph 13.3 is to apply (save that references to paragraph 13.2 shall be construed as being references to this paragraph). (d) Following the issue of an SPD Notice the party that issued that notice must serve a claim (an "SPD Claim"): (i) no later than the day falling 112 days after the issue of the Day 42 Statement for the last Period in the relevant SPD Period; or (ii) where an SPD Period has exceeded 13 consecutive Periods in length or upon the termination or expiry of this contract, whichever comes first, unless otherwise agreed in writing, no later than the day falling 112 days after the issue of the Day 42 Statement which followed the 13th consecutive Period or the termination or expiry of this contract (as applicable), whichever is the earlier. (e) Provided a party has issued an SPD Notice in accordance with paragraph 2.10(b), nothing in paragraph 2.10(d) shall prevent that party from issuing more than one SPD Claim in respect of the same Sustained Planned Disruption, provided that: (i) each such SPD Claim relates to a different period within the said SPD Period (so there is no double-counting); and (ii) no SPD Claim can be issued after the last day for serving notice specified under paragraph 2.10(d). (f) An SPD Claim must include details of when and why that party reasonably believes that a Sustained Planned Disruption has occurred and in particular: (i) if the claim is made by the Train Operator, such details as may reasonably be available of the RoU Liability which the Train Operator has incurred or reasonably expects to incur in respect of the relevant Restrictions of Use during the SPD Period; or (ii) if the claim is made by Network Rail, the reasons why Network Rail reasonably believes that the Train Operator has been overcompensated or may be overcompensated by more than the relevant amount. (g) Following the service of an SPD Claim, if and to the extent it is agreed or determined that a Sustained Planned Disruption has occurred in the period covered by the claim then the relevant party shall make payments to the other (in accordance with the procedure in paragraph 13) calculated in accordance with paragraph 8 in respect of the SPD Period (or where applicable the part of the SPD Period) covered by the SPD Claim.

Appears in 2 contracts

Samples: Track Access Contract, Track Access Contract

Sustained Planned Disruption. (a) If either party reasonably believes that a Sustained Planned Disruption has occurred then that party will be entitled to require that the costs and losses for the Restrictions of Use for the relevant services during the relevant SPD Period be calculated in accordance with paragraph 8 by serving a notice on the other (an "SPD Notice") in accordance with paragraph 2.10(b). (b) . Unless otherwise agreed in writing, an SPD Notice must be served no later than the day falling 56 days after the issue of the Day 42 Statement which followed the end of the relevant SPD Period and must include a short explanation of why it reasonably believes a Sustained Planned Disruption has occurred and a statement of when the SPD Period commenced. (c) . Following the issue of an SPD Notice, either party may serve a notice (an "SPD Termination Notice") stating that it reasonably believes that the relevant Sustained Planned Disruption is no longer occurring, such notice to include a short explanation of why the party serving it reasonably believes that the Sustained Planned Disruption has ceased and stating the Period in which such cessation has occurred. A party receiving an SPD Termination Notice shall within 30 days of its receipt by notice to the serving party either accept or reject the SPD Termination Notice and where it rejects the notice it shall include with its rejection notice a short explanation of why it reasonably believes the Sustained Planned Disruption is continuing. If the parties fail to reach agreement within 30 days after service of a rejection notice, or if prior to that date both parties agree that agreement is unlikely to be reached prior to that date, either party may notify the other that the dispute resolution procedure set out in paragraph 13.3 is to apply (save that references to paragraph 13.2 shall be construed as being references to this paragraph). (d) . Following the issue of an SPD Notice the party that issued that notice must serve a claim (an "SPD Claim"): (i) ): no later than the day falling 112 days after the issue of the Day 42 Statement for the last Period in the relevant SPD Period; or (ii) or where an SPD Period has exceeded 13 consecutive Periods in length or upon the termination or expiry of this contract, whichever comes first, unless otherwise agreed in writing, no later than the day falling 112 days after the issue of the Day 42 Statement which followed the 13th consecutive Period or the termination or expiry of this contract (as applicable), whichever is the earlier. (e) . Provided a party has issued an SPD Notice in accordance with paragraph 2.10(b), nothing in paragraph 2.10(d) shall prevent that party from issuing more than one SPD Claim in respect of the same Sustained Planned Disruption, provided that: (i) : each such SPD Claim relates to a different period within the said SPD Period (so there is no double-counting); and (ii) and no SPD Claim can be issued after the last day for serving notice specified under paragraph 2.10(d). (f) . An SPD Claim must include details of when and why that party reasonably believes that a Sustained Planned Disruption has occurred and in particular: (i) : if the claim is made by the Train Operator, such details as may reasonably be available of the RoU Liability which the Train Operator has incurred or reasonably expects to incur in respect of the relevant Restrictions of Use during the SPD Period; or (ii) or if the claim is made by Network Railthe CVL IM, the reasons why Network Rail the CVL IM reasonably believes that the Train Operator has been overcompensated or may be overcompensated by more than the relevant amount. (g) . Following the service of an SPD Claim, if and to the extent it is agreed or determined that a Sustained Planned Disruption has occurred in the period covered by the claim then the relevant party shall make payments to the other (in accordance with the procedure in paragraph 13) calculated in accordance with paragraph 8 in respect of the SPD Period (or where applicable the part of the SPD Period) covered by the SPD Claim.

Appears in 2 contracts

Samples: Track Access Contract (Passenger Services), Track Access Contract

Sustained Planned Disruption. (a) If either party reasonably believes that a Sustained Planned Disruption has occurred then that party will be entitled to require that the costs and losses for the Restrictions of Use for the relevant services during the relevant SPD Period be calculated in accordance with paragraph 8 by serving a notice on the other (an "SPD Notice") in accordance with paragraph 2.10(b).2.10(b).‌ (b) Unless otherwise agreed in writing, an SPD Notice must be served no later than the day falling 56 days after the issue of the Day 42 Statement which followed the end of the relevant SPD Period and must include a short explanation of why it reasonably believes a Sustained Planned Disruption has occurred and a statement of when the SPD Period commenced.commenced.‌ (c) Following the issue of an SPD Notice, either party may serve a notice (an "SPD Termination Notice") stating that it reasonably believes that the relevant Sustained Planned Disruption is no longer occurring, such notice to include a short explanation of why the party serving it reasonably believes that the Sustained Planned Disruption has ceased and stating the Period in which such cessation has occurred. A party receiving an SPD Termination Notice shall within 30 days of its receipt by notice to the serving party either accept or reject the SPD Termination Notice and where it rejects the notice it shall include with its rejection notice a short explanation of why it reasonably believes the Sustained Planned Disruption is continuing. If the parties fail to reach agreement within 30 days after service of a rejection notice, or if prior to that date both parties agree that agreement is unlikely to be reached prior to that date, either party may notify the other that the dispute resolution procedure set out in paragraph 13.3 is to apply (save that references to paragraph 13.2 shall be construed as being references to this paragraph).paragraph).‌ (d) Following the issue of an SPD Notice the party that issued that notice must serve a claim (an "SPD Claim"):Claim"):‌ (i) no later than the day falling 112 days after the issue of the Day 42 Statement for the last Period in the relevant SPD Period; oror‌ (ii) where an SPD Period has exceeded 13 consecutive Periods in length or upon the termination or expiry of this contract, whichever comes first, unless otherwise agreed in writing, no later than the day falling 112 days after the issue of the Day 42 Statement which followed the 13th consecutive Period or the termination or expiry of this contract (as applicable), applicable),‌ whichever is the earlier. (e) Provided a party has issued an SPD Notice in accordance with paragraph 2.10(b), nothing in paragraph 2.10(d) shall prevent that party from issuing more than one SPD Claim in respect of the same Sustained Planned Disruption, provided that:that:‌ (i) each such SPD Claim relates to a different period within the said SPD Period (so there is no double-counting); andand‌ (ii) no SPD Claim can be issued after the last day for serving notice specified under paragraph 2.10(d).2.10(d).‌ (f) An SPD Claim must include details of when and why that party reasonably believes that a Sustained Planned Disruption has occurred and in particular:particular:‌ (i) if the claim is made by the Train Operator, such details as may reasonably be available of the RoU Liability which the Train Operator has incurred or reasonably expects to incur in respect of the relevant Restrictions of Use during the SPD Period; oror‌ (ii) if the claim is made by Network Rail, the reasons why Network Rail reasonably believes that the Train Operator has been overcompensated or may be overcompensated by more than the relevant amount.amount.‌ (g) Following the service of an SPD Claim, if and to the extent it is agreed or determined that a Sustained Planned Disruption has occurred in the period covered by the claim then the relevant party shall make payments to the other (in accordance with the procedure in paragraph 13) calculated in accordance with paragraph 8 in respect of the SPD Period (or where applicable the part of the SPD Period) covered by the SPD Claim.Claim.‌

Appears in 1 contract

Samples: Track Access Contract

Sustained Planned Disruption. (a) If either party reasonably believes that a Sustained Planned Disruption has occurred then that party will be entitled to require that the costs and losses for the Restrictions of Use for the relevant services during the relevant SPD Period be calculated in accordance with paragraph 8 by serving a notice on the other (an "SPD Notice") in accordance with paragraph 2.10(b). (b) . Unless otherwise agreed in writing, an SPD Notice must be served no later than the day falling 56 days after the issue of the Day 42 Statement which followed the end of the relevant SPD Period and must include a short explanation of why it reasonably believes a Sustained Planned Disruption has occurred and a statement of when the SPD Period commenced. (c) . Following the issue of an SPD Notice, either party may serve a notice (an "SPD Termination Notice") stating that it reasonably believes that the relevant Sustained Planned Disruption is no longer occurring, such notice to include a short explanation of why the party serving it reasonably believes that the Sustained Planned Disruption has ceased and stating the Period in which such cessation has occurred. A party receiving an SPD Termination Notice shall within 30 days of its receipt by notice to the serving party either accept or reject the SPD Termination Notice and where it rejects the notice it shall include with its rejection notice a short explanation of why it reasonably believes the Sustained Planned Disruption is continuing. If the parties fail to reach agreement within 30 days after service of a rejection notice, or if prior to that date both parties agree that agreement is unlikely to be reached prior to that date, either party may notify the other that the dispute resolution procedure set out in paragraph 13.3 is to apply (save that references to paragraph 13.2 shall be construed as being references to this paragraph). (d) . Following the issue of an SPD Notice the party that issued that notice must serve a claim (an "SPD Claim"): (i) ): no later than the day falling 112 days after the issue of the Day 42 Statement for the last Period in the relevant SPD Period; or (ii) or where an SPD Period has exceeded 13 consecutive Periods in length or upon the termination or expiry of this contract, whichever comes first, unless otherwise agreed in writing, no later than the day falling 112 days after the issue of the Day 42 Statement which followed the 13th consecutive Period or the termination or expiry of this contract (as applicable), whichever is the earlier. (e) . Provided a party has issued an SPD Notice in accordance with paragraph 2.10(b), nothing in paragraph 2.10(d) shall prevent that party from issuing more than one SPD Claim in respect of the same Sustained Planned Disruption, provided that: (i) : each such SPD Claim relates to a different period within the said SPD Period (so there is no double-counting); and (ii) and no SPD Claim can be issued after the last day for serving notice specified under paragraph 2.10(d). (f) . An SPD Claim must include details of when and why that party reasonably believes that a Sustained Planned Disruption has occurred and in particular: (i) : if the claim is made by the Train Operator, such details as may reasonably be available of the RoU Liability which the Train Operator has incurred or reasonably expects to incur in respect of the relevant Restrictions of Use during the SPD Period; or (ii) or if the claim is made by Network Rail, the reasons why Network Rail reasonably believes that the Train Operator has been overcompensated or may be overcompensated by more than the relevant amount. (g) . Following the service of an SPD Claim, if and to the extent it is agreed or determined that a Sustained Planned Disruption has occurred in the period covered by the claim then the relevant party shall make payments to the other (in accordance with the procedure in paragraph 13) calculated in accordance with paragraph 8 in respect of the SPD Period (or where applicable the part of the SPD Period) covered by the SPD Claim.

Appears in 1 contract

Samples: Track Access Contract

AutoNDA by SimpleDocs

Sustained Planned Disruption. (a) If either party reasonably believes that a Sustained Planned Disruption has occurred then that party will be entitled to require that the costs and losses for the Restrictions of Use for the relevant services during the relevant SPD Period be calculated in accordance with paragraph 8 by serving a notice on the other (an "SPD Notice") in accordance with paragraph 2.10(b). (b) Unless otherwise agreed in writing, an SPD Notice must be served no later than the day falling 56 days after the issue of the Day 42 Statement which followed the end of the relevant SPD Period and must include a short explanation of why it reasonably believes a Sustained Planned Disruption has occurred and a statement of when the SPD Period commenced. (c) Following the issue of an SPD Notice, either party may serve a notice (an "SPD Termination Notice") stating that it reasonably believes that the relevant Sustained Planned Disruption is no longer occurring, such notice to include a short explanation of why the party serving it reasonably believes that the Sustained Planned Disruption has ceased and stating the Period in which such cessation has occurred. A party receiving an SPD Termination Notice shall within 30 days of its receipt by notice to the serving party either accept or reject the SPD Termination Notice and where it rejects the notice it shall include with its rejection notice a short explanation of why it reasonably believes the Sustained Planned Disruption is continuing. If the parties fail to reach agreement within 30 days after service of a rejection notice, or if prior to that date both parties agree that agreement is unlikely to be reached prior to that date, either party may notify the other that the dispute resolution procedure set out in paragraph 13.3 is to apply (save that references to paragraph 13.2 shall be construed as being references to this paragraph). (d) Following the issue of an SPD Notice the party that issued that notice must serve a claim (an "SPD Claim"): (i) no later than the day falling 112 days after the issue of the Day 42 Statement for the last Period in the relevant SPD Period; or (ii) where an SPD Period has exceeded 13 consecutive Periods in length or upon the termination or expiry of this contract, whichever comes first, unless otherwise agreed in writing, no later than the day falling 112 days after the issue of the Day 42 Statement which followed the 13th consecutive Period or the termination or expiry of this contract (as applicable), whichever is the earlier., (e) Provided a party has issued an SPD Notice in accordance with paragraph 2.10(b), nothing in paragraph 2.10(d) shall prevent that party from issuing more than one SPD Claim in respect of the same Sustained Planned Disruption, provided that: (i) each such SPD Claim relates to a different period within the said SPD Period (so there is no double-counting); and (ii) no SPD Claim can be issued after the last day for serving notice specified under paragraph 2.10(d). (f) An SPD Claim must include details of when and why that party reasonably believes that a Sustained Planned Disruption has occurred and in particular: (i) if the claim is made by the Train Operator, such details as may reasonably be available of the RoU Liability which the Train Operator has incurred or reasonably expects to incur in respect of the relevant Restrictions of Use during the SPD Period; or (ii) if the claim is made by Network Rail, the reasons why Network Rail reasonably believes that the Train Operator has been overcompensated or may be overcompensated by more than the relevant amount. (g) Following the service of an SPD Claim, if and to the extent it is agreed or determined that a Sustained Planned Disruption has occurred in the period covered by the claim then the relevant party shall make payments to the other (in accordance with the procedure in paragraph 13) calculated in accordance with paragraph 8 in respect of the SPD Period (or where applicable the part of the SPD Period) covered by the SPD Claim.the

Appears in 1 contract

Samples: Track Access Contract

Sustained Planned Disruption. (a) If either party reasonably believes that a Sustained Planned Disruption has occurred then that party will be entitled to require that the costs and losses for the Restrictions of Use for the relevant services during the relevant SPD Period be calculated in accordance with paragraph 8 by serving a notice on the other (an "SPD Notice") in accordance with paragraph 2.10(b). (b) Unless otherwise agreed in writing, an SPD Notice must be served no later than the day falling 56 days after the issue of the Day 42 Statement which followed the end of the relevant SPD Period and must include a short explanation of why it reasonably believes a Sustained Planned Disruption has occurred and a statement of when the SPD Period commenced. (c) Following the issue of an SPD Notice, either party may serve a notice (an "SPD Termination Notice") stating that it reasonably believes that the relevant Sustained Planned Disruption is no longer occurring, such notice to include a short explanation of why the party serving it reasonably believes that the Sustained Planned Disruption has ceased and stating the Period in which such cessation has occurred. A party receiving an SPD Termination Notice shall within 30 days of its receipt by notice to the serving party either accept or reject the SPD Termination Notice and where it rejects the notice it shall include with its rejection notice a short explanation of why it reasonably believes the Sustained Planned Disruption is continuing. If the parties fail to reach agreement within 30 days after service of a rejection notice, or if prior to that date both parties agree that agreement is unlikely to be reached prior to that date, either party may notify the other that the dispute resolution procedure set out in paragraph 13.3 is to apply (save that references to paragraph 13.2 shall be construed as being references to this paragraph). (d) Following the issue of an SPD Notice the party that issued that notice must serve a claim (an "SPD Claim"): (i) no later than the day falling 112 days after the issue of the Day 42 Statement for the last Period in the relevant SPD Period; or (ii) where an SPD Period has exceeded 13 consecutive Periods in length or upon the termination or expiry of this contract, whichever comes first, unless otherwise agreed in writing, no later than the day falling 112 days after the issue of the Day 42 Statement which followed the 13th consecutive Period or the termination or expiry of this contract (as applicable), whichever is the earlier. (e) Provided a party has issued an SPD Notice in accordance with paragraph 2.10(b), nothing in paragraph 2.10(d) shall prevent that party from issuing more than one SPD Claim in respect of the same Sustained Planned Disruption, provided that: (i) each such SPD Claim relates to a different period within the said SPD Period (so there is no double-counting); and (ii) no SPD Claim can be issued after the last day for serving notice specified under paragraph 2.10(d). (f) An SPD Claim must include details of when and why that party reasonably believes that a Sustained Planned Disruption has occurred and in particular: (i) if the claim is made by the Train Operator, such details as may reasonably be available of the RoU Liability which the Train Operator has incurred or reasonably expects to incur in respect of the relevant Restrictions of Use during the SPD Period; or (ii) if the claim is made by Network Rail, the reasons why Network Rail reasonably believes that the Train Operator has been overcompensated or may be overcompensated by more than the relevant amount. (g) Following the service of an SPD Claim, if and to the extent it is agreed or determined that a Sustained Planned Disruption has occurred in the period covered by the claim then the relevant party shall make payments to the other (in accordance with the procedure in paragraph 13) calculated in accordance with paragraph 8 in respect of the SPD Period (or where applicable the part of the SPD Period) covered by the SPD Claim.

Appears in 1 contract

Samples: Track Access Contract (Passenger Services)

Sustained Planned Disruption. (a) ­ If either party reasonably believes that a Sustained Planned Disruption has occurred then that party will be entitled to require that the costs and losses for the Restrictions of Use for the relevant services during the relevant SPD Period be calculated in accordance with paragraph 8 by serving a notice on the other (an "SPD Notice") in accordance with paragraph 2.10(b). (b) ­ Unless otherwise agreed in writing, an SPD Notice must be served no later than the day falling 56 days after the issue of the Day 42 Statement which followed the end of the relevant SPD Period and must include a short explanation of why it reasonably believes a Sustained Planned Disruption has occurred and a statement of when the SPD Period commenced. (c) ­ Following the issue of an SPD Notice, either party may serve a notice (an "SPD Termination Notice") stating that it reasonably believes that the relevant Sustained Planned Disruption is no longer occurring, such notice to include a short explanation of why the party serving it reasonably believes that the Sustained Planned Disruption has ceased and stating the Period in which such cessation has occurred. A party receiving an SPD Termination Notice shall within 30 days of its receipt by notice to the serving party either accept or reject the SPD Termination Notice and where it rejects the notice it shall include with its rejection notice a short explanation of why it reasonably believes the Sustained Planned Disruption is continuing. If the parties fail to reach agreement within 30 days after service of a rejection notice, or if prior to that date both parties agree that agreement is unlikely to be reached prior to that date, either party may notify the other that the dispute resolution procedure set out in paragraph 13.3 is to apply (save that references to paragraph 13.2 shall be construed as being references to this paragraph). (d) ­ Following the issue of an SPD Notice the party that issued that notice must serve a claim (an "SPD Claim"): (i) ­ no later than the day falling 112 days after the issue of the Day 42 Statement for the last Period in the relevant SPD Period; or (ii) ­ where an SPD Period has exceeded 13 consecutive Periods in length or upon the termination or expiry of this contract, whichever comes first, unless otherwise agreed in writing, no later than the day falling 112 days after the issue of the Day 42 Statement which followed the 13th consecutive Period or the termination or expiry of this contract (as applicable), whichever is the earlier. (e) ­ Provided a party has issued an SPD Notice in accordance with paragraph 2.10(b), nothing in paragraph 2.10(d) shall prevent that party from issuing more than one SPD Claim in respect of the same Sustained Planned Disruption, provided that: (i) ­ each such SPD Claim relates to a different period within the said SPD Period (so there is no double-counting); and (ii) no ­no SPD Claim can be issued after the last day for serving notice specified under paragraph 2.10(d). (f) ­ An SPD Claim must include details of when and why that party reasonably believes that a Sustained Planned Disruption has occurred and in particular: (i) ­ if the claim is made by the Train Operator, such details as may reasonably be available of the RoU Liability which the Train Operator has incurred or reasonably expects to incur in respect of the relevant Restrictions of Use during the SPD Period; or (ii) if ­if the claim is made by Network Rail, the reasons why Network Rail reasonably believes that the Train Operator has been overcompensated or may be overcompensated by more than the relevant amount. (g) Following the service of an SPD Claim, if and to the extent it is agreed or determined that a Sustained Planned Disruption has occurred in the period covered by the claim then the relevant party shall make payments to the other (in accordance with the procedure in paragraph 13) calculated in accordance with paragraph 8 in respect of the SPD Period (or where applicable the part of the SPD Period) covered by the SPD Claim.

Appears in 1 contract

Samples: Track Access Contract (Passenger Services)

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