CCB Obligations
CCB Obligations Sample Clauses
Related to CCB Obligations
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.
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).
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.
Provider Obligations Provider at all times during the term of this Agreement shall:
USER OBLIGATIONS As a user of the Website or Services, You may be asked to register with Us. When You do so, You will choose a user identifier, which may be Your email address or another term, as well as a password. You may also provide personal information, including, but not limited to, Your name. You are responsible for ensuring the accuracy of this information. This identifying information will enable You to use the Website and Services. You must not share such identifying information with any third party, and if You discover that Your identifying information has been compromised, You agree to notify Us immediately in writing. Email notification will suffice. You are responsible for maintaining the safety and security of Your identifying information as well as keeping Us apprised of any changes to Your identifying information. Providing false or inaccurate information, or using the Website or Services to further fraud or unlawful activity is grounds for immediate termination of this Agreement.
Guaranty Obligations Unless otherwise specified, the amount of any Guaranty Obligation shall be the lesser of the principal amount of the obligations guaranteed and still outstanding and the maximum amount for which the guaranteeing Person may be liable pursuant to the terms of the instrument embodying such Guaranty Obligation.
ERISA Obligations All Employee Plans of the Borrower meet the minimum funding standards of Section 302 of ERISA and 412 of the Internal Revenue Code where applicable, and each such Employee Plan that is intended to be qualified within the meaning of Section 401 of the Internal Revenue Code of 1986 is qualified. No withdrawal liability has been incurred under any such Employee Plans and no “Reportable Event” or “Prohibited Transaction” (as such terms are defined in ERISA), has occurred with respect to any such Employee Plans, unless approved by the appropriate governmental agencies. The Borrower has promptly paid and discharged all obligations and liabilities arising under the Employee Retirement Income Security Act of 1974 (“ERISA”) of a character which if unpaid or unperformed might result in the imposition of a Lien against any of its properties or assets.
Supplier Obligations At all times during the Term, the Supplier is required to:
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.
