COMPLIANCE WITH BREACH NOTIFICATION AND DATA SECURITY LAWS Contractor shall comply with the provisions of the New York State Information Security Breach and Notification Act (General Business Law § 899-aa and State Technology Law § 208) and commencing March 21, 2020 shall also comply with General Business Law § 899-bb.
Notification of Breach / Compliance Reports The Adviser shall notify the Trust immediately upon detection of (i) any material failure to manage any Fund in accordance with its investment objectives and policies or any applicable law; or (ii) any material breach of any of the Funds’ or the Adviser’s policies, guidelines or procedures. In addition, the Adviser shall provide a quarterly report regarding each Fund’s compliance with its investment objectives and policies, applicable law, including, but not limited to the 1940 Act and Subchapter M of the Code, as applicable, and the Fund’s policies, guidelines or procedures as applicable to the Adviser’s obligations under this Agreement. The Adviser agrees to correct any such failure promptly and to take any action that the Board may reasonably request in connection with any such breach. Upon request, the Adviser shall also provide the officers of the Trust with supporting certifications in connection with such certifications of Fund financial statements and disclosure controls pursuant to the Xxxxxxxx-Xxxxx Act. The Adviser will promptly notify the Trust in the event (i) the Adviser is served or otherwise receives notice of any action, suit, proceeding, inquiry or investigation, at law or in equity, before or by any court, public board, or body, involving the affairs of the Trust (excluding class action suits in which a Fund is a member of the plaintiff class by reason of the Fund’s ownership of shares in the defendant) or the compliance by the Adviser with the federal or state securities laws or (ii) an actual change in control of the Adviser resulting in an “assignment” (as defined in the 0000 Xxx) has occurred or is otherwise proposed to occur.
Procurement from UN Agencies Goods estimated to cost less than $100,000 equivalent per contract may be procured directly from Inter-Agency Procurement Services Office (IAPSO) in accordance with the provisions of paragraphs 3.1 and 3.9 of the Procurement Guidelines.
Liability for Failure to Stop Payment of Preauthorized Transfer If you order us to stop one of these payments 3 business days or more before the transfer is scheduled, and we do not do so, we will be liable for your losses or damages.
NOTIFICATION OF PUBLIC EVENTS AND MEETINGS 2 A. CONTRACTOR shall notify ADMINISTRATOR of any public event or meeting funded in 3 whole or in part by the COUNTY, except for those events or meetings that are intended solely to serve 4 clients or occur in the normal course of business.
5 B. CONTRACTOR shall notify ADMINISTRATOR at least thirty (30) business days in advance 6 of any applicable public event or meeting. The notification must include the date, time, duration, 7 location and purpose of the public event or meeting. Any promotional materials or event related flyers 8 must be approved by ADMINISTRATOR prior to distribution. 9
Optional Xactimate Response Attachment (Part 2)
Notice of Agreement 1. The Institutions agree to provide a copy of this Agreement, with any amendments, to the Maryland Higher Education Commission.
2. The Institutions agree to provide copies of this Agreement to all relevant individuals and departments of the Institutions, including but not limited to students, academic department chairs participating in the transfer, offices of the president, registrar’s offices, and financial aid offices.
Liability for Failure to Stop Payment of Preauthorized Transfers If you order us to stop payment of a preauthorized transfer three (3) business days or more before the transfer is scheduled and we do not do so, we will be liable for your losses or damages.
BREACH DISCOVERY AND NOTIFICATION 17 1. Following the discovery of a Breach of Unsecured PHI, CONTRACTOR shall notify 18 COUNTY of such Breach, however both parties agree to a delay in the notification if so advised by a 19 law enforcement official pursuant to 45 CFR § 164.412.
20 a. A Breach shall be treated as discovered by CONTRACTOR as of the first day on which 21 such Breach is known to CONTRACTOR or, by exercising reasonable diligence, would have been 22 known to CONTRACTOR.
23 b. CONTRACTOR shall be deemed to have knowledge of a Breach, if the Breach is 24 known, or by exercising reasonable diligence would have known, to any person who is an employee, 25 officer, or other agent of CONTRACTOR, as determined by federal common law of agency.
26 2. CONTRACTOR shall provide the notification of the Breach immediately to the COUNTY 27 Privacy Officer. CONTRACTOR’s notification may be oral, but shall be followed by written 28 notification within twenty four (24) hours of the oral notification.
29 3. CONTRACTOR’s notification shall include, to the extent possible:
30 a. The identification of each Individual whose Unsecured PHI has been, or is reasonably 31 believed by CONTRACTOR to have been, accessed, acquired, used, or disclosed during the Breach;
32 b. Any other information that COUNTY is required to include in the notification to 33 Individual under 45 CFR §164.404 (c) at the time CONTRACTOR is required to notify COUNTY or 34 promptly thereafter as this information becomes available, even after the regulatory sixty (60) day 35 period set forth in 45 CFR § 164.410 (b) has elapsed, including:
36 1) A brief description of what happened, including the date of the Breach and the date 37 of the discovery of the Breach, if known;
1 2) A description of the types of Unsecured PHI that were involved in the Breach (such 2 as whether full name, social security number, date of birth, home address, account number, diagnosis, 3 disability code, or other types of information were involved);
4 3) Any steps Individuals should take to protect themselves from potential harm 5 resulting from the Breach;
6 4) A brief description of what CONTRACTOR is doing to investigate the Breach, to 7 mitigate harm to Individuals, and to protect against any future Breaches; and
8 5) Contact procedures for Individuals to ask questions or learn additional information, 9 which shall include a toll-free telephone number, an e-mail address, Web site, or postal address.
10 4. COUNTY may require CONTRACTOR to provide notice to the Individual as required in 11 45 CFR § 164.404, if it is reasonable to do so under the circumstances, at the sole discretion of the 12 COUNTY.
13 5. In the event that CONTRACTOR is responsible for a Breach of Unsecured PHI in violation 14 of the HIPAA Privacy Rule, CONTRACTOR shall have the burden of demonstrating that 15 CONTRACTOR made all notifications to COUNTY consistent with this Subparagraph F and as 16 required by the Breach notification regulations, or, in the alternative, that the acquisition, access, use, or 17 disclosure of PHI did not constitute a Breach.
18 6. CONTRACTOR shall maintain documentation of all required notifications of a Breach or 19 its risk assessment under 45 CFR § 164.402 to demonstrate that a Breach did not occur.
20 7. CONTRACTOR shall provide to COUNTY all specific and pertinent information about the 21 Breach, including the information listed in Section E.3.b.(1)-(5) above, if not yet provided, to permit 22 COUNTY to meet its notification obligations under Subpart D of 45 CFR Part 164 as soon as 23 practicable, but in no event later than fifteen (15) calendar days after CONTRACTOR’s initial report of 24 the Breach to COUNTY pursuant to Subparagraph F.2. above.
25 8. CONTRACTOR shall continue to provide all additional pertinent information about the
General Conditions Applicable to Option to Build If the Interconnection Customer assumes responsibility for the design, procurement and construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades,
(1) the Interconnection Customer shall engineer, procure equipment, and construct the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades (or portions thereof) using Good Utility Practice and using standards and specifications provided in advance by the Participating TO;
(2) The Interconnection Customer’s engineering, procurement and construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades shall comply with all requirements of law to which the Participating TO would be subject in the engineering, procurement or construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades;
(3) the Participating TO shall review, and the Interconnection Customer shall obtain the Participating TO’s approval of, the engineering design, equipment acceptance tests, and the construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades, which approval shall not be unreasonably withheld, and the CAISO may, at its option, review the engineering design, equipment acceptance tests, and the construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades;
(4) prior to commencement of construction, the Interconnection Customer shall provide to the Participating TO, with a copy to the CAISO for informational purposes, a schedule for construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades, and shall promptly respond to requests for information from the Participating TO;
(5) at any time during construction, the Participating TO shall have the right to gain unrestricted access to the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades and to conduct inspections of the same;
(6) at any time during construction, should any phase of the engineering, equipment procurement, or construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades not meet the standards and specifications provided by the Participating TO, the Interconnection Customer shall be obligated to remedy deficiencies in that portion of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades;
(7) the Interconnection Customer shall indemnify the CAISO and Participating TO for claims arising from the Interconnection Customer's construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades under the terms and procedures applicable to Article 18.1
