Client Obligations Client shall fulfill its obligations and responsibilities as set forth in this Agreement and the SOW so that Spirent can perform the Services efficiently and effectively. Client is responsible for the operation and security of its applications and the information technology environment in which the Services are to be performed. Client agrees that it shall have the sole responsibility for protecting and backing up its systems, networks, applications, content, and data used in connection with the Services. Client shall secure and provide to Spirent any rights and licenses necessary to allow Spirent to perform the Services. Client shall ensure the cooperation and performance of its employees and contractors as well as the accuracy and completeness of data and information provided to Spirent that are necessary to perform the Services. Client shall make and be responsible for all decisions and actions based or related to advice and recommendations provided by Spirent in connection with the performance of the Services hereunder. Client shall be liable for all Spirent owned equipment while in Client’s possession or control and, if lost or. damaged or not returned to Spirent upon expiration of the engagement, Client agrees to pay for such equipment upon receipt of an invoice referencing this Agreement. Equipment received by Spirent from Client more than five (5) calendar days after the end of engagement shall be subject to a fifteen (15%) per month late fee based on the list price of the equipment.
SAP OBLIGATIONS 3.1 Instructions from Customer. SAP will process Personal Data only in accordance with documented instructions from Customer. The Agreement (including this DPA) constitutes such documented initial instructions and each use of the Cloud Service then constitutes further instructions. SAP will use reasonable efforts to follow any other Customer instructions, as long as they are required by Data Protection Law, technically feasible and do not require changes to the Cloud Service. If any of the before-mentioned exceptions apply, or SAP otherwise cannot comply with an instruction or is of the opinion that an instruction infringes Data Protection Law, SAP will immediately notify Customer (email permitted).
Surety Obligations No Borrower or Subsidiary is obligated as surety or indemnitor under any bond or other contract that assures payment or performance of any obligation of any Person, except as permitted hereunder.
Third Party Obligations 3.1. The THIRD PARTY shall:-
Contractor Obligations The Contractor is responsible for fully meeting all Contract obligations set forth in the OGS Centralized Contract and for providing services in accordance with the Contract and any Authorized User Agreement, Statement of Work or Purchase Order.
Recipient Obligations 2.1 The Recipient agrees to support the Project in accordance with this Agreement.
Provider Obligations Provider at all times during the term of this Agreement shall:
Perform Obligations Tenant shall perform promptly all of the obligations of Tenant set forth in this Lease; and pay when due the Annual Fixed Rent and Additional Rent and all other amounts which by the terms of this Lease are to be paid by Tenant.
Developer Obligations In accordance with applicable NYISO requirements, Developer shall maintain satisfactory operating communications with Connecting Transmission Owner and NYISO. Developer shall provide standard voice line, dedicated voice line and facsimile communications at its Large Generating Facility control room or central dispatch facility through use of either the public telephone system, or a voice communications system that does not rely on the public telephone system. Developer shall also provide the dedicated data circuit(s) necessary to provide Developer data to Connecting Transmission Owner and NYISO as set forth in Appendix D hereto. The data circuit(s) shall extend from the Large Generating Facility to the location(s) specified by Connecting Transmission Owner and NYISO. Any required maintenance of such communications equipment shall be performed by Developer. Operational communications shall be activated and maintained under, but not be limited to, the following events: system paralleling or separation, scheduled and unscheduled shutdowns, equipment clearances, and hourly and daily load data.
Joint Obligations The following shall apply with equal force to Seller and Purchaser:
