Delays and Recovery Plan Sample Clauses

Delays and Recovery Plan. Without prejudice to any rights or remedies the Eurosystem may have under this Contract or applicable law, failure by the Network Service Provider to reach a Milestone by the respective Target Date or to otherwise meet any timeline agreed between the Parties or set forth in this Contract with respect to the design, development, implementation and making available of the Network and the Connectivity Services (each such failure a "Delay") shall not relieve the Network Service Provider of its obligation to design, develop, implement and make available, as the case may be, the Network or the Connectivity Services. In the event of a Delay, the Parties shall, without undue delay, agree and implement a plan to recover any lost time (the "Recovery Plan"). The Network Service Provider shall be required to make available any additional resources required to implement the Recovery Plan.
AutoNDA by SimpleDocs

Related to Delays and Recovery Plan

  • Disaster Recovery Plan Contractor agrees that upon request of System Agency, Contractor shall provide copies of its most recent business continuity and disaster recovery plans.

  • DISASTER RECOVERY AND BUSINESS CONTINUITY The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • Disaster Recovery PFPC shall enter into and shall maintain in effect with appropriate parties one or more agreements making reasonable provisions for emergency use of electronic data processing equipment to the extent appropriate equipment is available. In the event of equipment failures, PFPC shall, at no additional expense to the Fund, take reasonable steps to minimize service interruptions. PFPC shall have no liability with respect to the loss of data or service interruptions caused by equipment failure, provided such loss or interruption is not caused by PFPC's own willful misfeasance, bad faith, gross negligence or reckless disregard of its duties or obligations under this Agreement.

  • Procurement Plan 8. The Borrower shall update the Procurement Plan as needed throughout implementation of the Project, and on each anniversary of the Effective Date, the Borrower shall in consultation with ADB determine whether the Procurement Plan needs to be updated. The Borrower shall implement the Procurement Plan in the manner in which it has been approved by ADB.

  • Project Implementation 2. The Borrower shall:

  • Development Plans 4.3.1 For each Licensed Indication and corresponding Licensed Product in the Field, Licensee will prepare and deliver to Licensor a development plan and budget (each a “Development Plan”). The initial Development Plans for each Licensed Indication will be delivered within […***…] after the Grant Date for such Licensed Indication.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic DHCS PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than 24 hours.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • BUSINESS CONTINUITY PLAN The Warrant Agent shall maintain plans for business continuity, disaster recovery, and backup capabilities and facilities designed to ensure the Warrant Agent’s continued performance of its obligations under this Agreement, including, without limitation, loss of production, loss of systems, loss of equipment, failure of carriers and the failure of the Warrant Agent’s or its supplier’s equipment, computer systems or business systems (“Business Continuity Plan”). Such Business Continuity Plan shall include, but shall not be limited to, testing, accountability and corrective actions designed to be promptly implemented, if necessary. In addition, in the event that the Warrant Agent has knowledge of an incident affecting the integrity or availability of such Business Continuity Plan, then the Warrant Agent shall, as promptly as practicable, but no later than twenty-four (24) hours (or sooner to the extent required by applicable law or regulation) after the Warrant Agent becomes aware of such incident, notify the Company in writing of such incident and provide the Company with updates, as deemed appropriate by the Warrant Agent under the circumstances, with respect to the status of all related remediation efforts in connection with such incident. The Warrant Agent represents that, as of the date of this Agreement, such Business Continuity Plan is active and functioning normally in all material respects.

Time is Money Join Law Insider Premium to draft better contracts faster.