Security Rule Obligations The following provisions of this section apply to the extent that Business Associate creates, receives, maintains or transmits Electronic PHI on behalf of Covered Entity.
Electronic PHI Security Rule Obligations 5.1 With respect to Electronic PHI, Business Associate shall:
Client Obligations 3.1 The Client shall:
Sub-processor Obligations MailChimp shall: (i) enter into a written agreement with the Sub-processor imposing data protection terms that require the Sub-processor to protect the Customer Data to the standard required by Data Protection Laws; and (ii) remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the Sub-processor that cause MailChimp to breach any of its obligations under this DPA.
PROCUREMENT OBLIGATIONS Notwithstanding any other provisions of this Part B, where in this Part B the Customer accepts an obligation to procure that a Former Supplier does or does not do something, such obligation shall be limited so that it extends only to the extent that the Customer's contract with the Former Supplier contains a contractual right in that regard which the Customer may enforce, or otherwise so that it requires only that the Customer must use reasonable endeavours to procure that the Former Supplier does or does not act accordingly.
Security for Obligations This Agreement secures, and the Collateral is collateral security for, the prompt and complete payment or performance in full when due, whether at stated maturity, by required prepayment, declaration, acceleration, demand or otherwise (including the payment of amounts that would become due but for the operation of the automatic stay under Section 362(a) of the Bankruptcy Code, 11 U.S.C. §362(a) (and any successor provision thereof)), of all Obligations with respect to every Grantor (the “Secured Obligations”).
Processor Obligations 4.1 The Processor may collect, process or use Personal Data only within the scope of this DPA.
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.
Customer Obligations Customer shall:
TRANSNET’S OBLIGATIONS 8.1 Transnet undertakes to promptly comply with any reasonable request by the Supplier/Service Provider for information, including information concerning Transnet's operations and activities, that relates to the Goods/Services as may be necessary for the Supplier/Service Provider to provide the Goods/Services, but for no other purpose. However, Transnet's compliance with any request for information is subject to any internal security rules and requirements and subject to the observance by the Supplier/Service Provider of its confidentiality obligations under this Agreement.
