Severe Weather Resilience and Service Disruption Sample Clauses

Severe Weather Resilience and Service Disruption. Without prejudice to the Franchisee’s obligations in paragraphs 8 and 9, any obligation in this Schedule 1.2 on the part of the Franchisee to use all reasonable endeavours to operate railway passenger services shall include an obligation to:- 10.1 co-operate with the Authority in its resilience planning including without prejudice to the foregoing generality: - (a) making an appropriately trained manager available to attend (whether in person or remotely), at the Authority’s request, meetings of the Multi-Agency Response Team (or similar response group) at the Scottish Government’s Resilience Room or otherwise; and (b) engaging with the Scottish Government’s preparedness initiatives relating to Winter conditions and severe weather; 10.2 make such adaptations to the Train Fleet, other equipment or facilities essential to the provision of railway passenger services and Stations as are reasonably necessary to respond to repeated and prolonged periods of severe weather (be it winter weather or otherwise); 10.3 put in place arrangements for emergency staff availability to respond to repeated and prolonged periods of severe weather (be it winter weather or otherwise); 10.4 use weather reports and forecasts to plan for disruption and to make decisions on when to implement its Resilience Plan; 10.5 co-operate with Network Rail, Associates and other Train Operators to provide support to each other, make staff available to each other and pass timely, accurate and detailed information about disruption to each other including attendance at Gold and Silver Command locations; 10.6 use best practice with regards to planning for severe weather including such adaptations as referred to in paragraph 10.2; 10.7 ensure that each Station and Depot is equipped with the necessary equipment to help railway passenger services to continue in severe weather; 10.8 comply with its Resilience Plan and any information Published and provided to passengers as to how the Franchisee will operate in such events save where the best interests of the passengers would be better served by departing from the same; and 10.9 comply with the obligations in paragraph 11.
AutoNDA by SimpleDocs

Related to Severe Weather Resilience and Service Disruption

  • Vulnerability Management BNY Mellon will maintain a documented process to identify and remediate security vulnerabilities affecting its systems used to provide the services. BNY Mellon will classify security vulnerabilities using industry recognized standards and conduct continuous monitoring and testing of its networks, hardware and software including regular penetration testing and ethical hack assessments. BNY Mellon will remediate identified security vulnerabilities in accordance with its process.

  • Availability of Verizon Telecommunications Services 3.1 Verizon will provide a Verizon Telecommunications Service to Z-Tel for resale pursuant to this Attachment where and to the same extent, but only where and to the same extent, that such Verizon Telecommunications Service is provided to Verizon’s Customers. 3.2 Except as otherwise required by Applicable Law, subject to Section 3.1, Verizon shall have the right to add, modify, grandfather, discontinue or withdraw, Verizon Telecommunications Services at any time, without the consent of Z-Tel. 3.3 To the extent required by Applicable Law, the Verizon Telecommunications Services to be provided to Z-Tel for resale pursuant to this Attachment will include a Verizon Telecommunications Service customer-specific contract service arrangement (“CSA”) (such as a customer specific pricing arrangement or individual case based pricing arrangement) that Verizon is providing to a Verizon Customer at the time the CSA is requested by Z-Tel.

  • Emergency Maintenance LightEdge reserves the right to perform emergency Service maintenance as needed outside the Scheduled Maintenance window, in which case LightEdge will make a reasonable effort to notify the Customer if feasible under the circumstances. Any such maintenance will be considered an “Emergency Maintenance”. All Service SLAs will apply during Emergency Maintenance.

  • Unbundled Network Terminating Wire (UNTW) 2.8.3.1 UNTW is unshielded twisted copper wiring that is used to extend circuits from an intra-building network cable terminal or from a building entrance terminal to an individual End User’s point of demarcation. It is the final portion of the Loop that in multi-subscriber configurations represents the point at which the network branches out to serve individual subscribers. 2.8.3.2 This element will be provided in MDUs and/or Multi-Tenants Units (MTUs) where either Party owns wiring all the way to the End User’s premises. Neither Party will provide this element in locations where the property owner provides its own wiring to the End User’s premises, where a third party owns the wiring to the End User’s premises.

  • Disturbance Analysis Data Exchange The Parties will cooperate with one another and the NYISO in the analysis of disturbances to either the Large Generating Facility or the New York State Transmission System by gathering and providing access to any information relating to any disturbance, including information from disturbance recording equipment, protective relay targets, breaker operations and sequence of events records, and any disturbance information required by Good Utility Practice.

  • Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.

  • Disruption to Payment Systems etc If either the Agent determines (in its discretion) that a Disruption Event has occurred or the Agent is notified by the Company that a Disruption Event has occurred: (a) the Agent may, and shall if requested to do so by the Company, consult with the Company with a view to agreeing with the Company such changes to the operation or administration of the Facility as the Agent may deem necessary in the circumstances; (b) the Agent shall not be obliged to consult with the Company in relation to any changes mentioned in paragraph (a) if, in its opinion, it is not practicable to do so in the circumstances and, in any event, shall have no obligation to agree to such changes; (c) the Agent may consult with the Finance Parties in relation to any changes mentioned in paragraph (a) but shall not be obliged to do so if, in its opinion, it is not practicable to do so in the circumstances; (d) any such changes agreed upon by the Agent and the Company shall (whether or not it is finally determined that a Disruption Event has occurred) be binding upon the Parties as an amendment to (or, as the case may be, waiver of) the terms of the Finance Documents notwithstanding the provisions of Clause 39 (Amendments and Waivers); (e) the Agent shall not be liable for any damages, costs or losses whatsoever (including, without limitation for negligence, gross negligence or any other category of liability whatsoever but not including any claim based on the fraud of the Agent) arising as a result of its taking, or failing to take, any actions pursuant to or in connection with this Clause 33.11; and (f) the Agent shall notify the Finance Parties of all changes agreed pursuant to paragraph (d) above.

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

  • H5 Disruption The Contractor shall take reasonable care to ensure that in the performance of its obligations under the Contract it does not disrupt the operations of the Authority, its employees or any other contractor employed by the Authority.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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