Authorization Required Prior to Parallel Operation 2.2.1 The NYISO, in consultation with the Connecting Transmission Owner, shall use Reasonable Efforts to list applicable parallel Operating Requirements in Attachment 5 of this Agreement. Additionally, the NYISO, in consultation with the Connecting Transmission Owner, shall notify the Interconnection Customer of any changes to these requirements as soon as they are known. The NYISO and Connecting Transmission Owner shall make Reasonable Efforts to cooperate with the Interconnection Customer in meeting requirements necessary for the Interconnection Customer to commence parallel operations by the in-service date.
2.2.2 The Interconnection Customer shall not operate its Small Generating Facility in parallel with the New York State Transmission System or the Distribution System without prior written authorization of the NYISO. The NYISO, in consultation with the Connecting Transmission Owner, will provide such authorization once the NYISO receives notification that the Interconnection Customer has complied with all applicable parallel Operating Requirements. Such authorization shall not be unreasonably withheld, conditioned, or delayed.
State Approval of Replacement Personnel The Engineer may not replace the project manager or key personnel without prior consent of the State. The State must be satisfied that the new project manager or other key personnel is qualified to provide the authorized services. If the State determines that the new project manager or key personnel is not acceptable, the Engineer may not use that person in that capacity and shall replace him or her with one satisfactory to the State within forty-five (45) days.
Acknowledgement and Consent to Bail-In of EEAAffected Financial Institutions Notwithstanding anything to the contrary in any Loan Document or in any other agreement, arrangement or understanding among any such parties, each party hereto acknowledges that any liability of any EEAAffected Financial Institution arising under any Loan Document, to the extent such liability is unsecured, may be subject to the write-down and conversion powers of an EEAthe applicable Resolution Authority and agrees and consents to, and acknowledges and agrees to be bound by:
(a) the application of any Write-Down and Conversion Powers by an EEAthe applicable Resolution Authority to any such liabilities arising hereunder which may be payable to it by any party hereto that is an EEAAffected Financial Institution; and
(b) the effects of any Bail-in Action on any such liability, including, if applicable:
(i) a reduction in full or in part or cancellation of any such liability;
(ii) a conversion of all, or a portion of, such liability into shares or other instruments of ownership in such EEAAffected Financial Institution, its parent undertaking, or a bridge institution that may be issued to it or otherwise conferred on it, and that such shares or other instruments of ownership will be accepted by it in lieu of any rights with respect to any such liability under this Agreement or any other Loan Document; or
(iii) the variation of the terms of such liability in connection with the exercise of the write-down and conversion powers of any EEAthe applicable Resolution Authority.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:
(1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute;
(2) Limit unsuccessful logon attempts;
(3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions;
(4) Authorize wireless access prior to allowing such connections;
(5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity;
(6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions;
(7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles;
(8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services;
(9) Enforce a minimum password complexity and change of characters when new passwords are created;
(10) Perform maintenance on organizational systems;
(11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance;
(12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1;
(13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital;
(14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse;
(15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas;
(16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems;
(17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems;
(18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception);
(19) Protect the confidentiality of Student Data at rest;
(20) Identify, report, and correct system flaws in a timely manner;
(21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems;
(22) Monitor system security alerts and advisories and take action in response; and
(23) Update malicious code protection mechanisms when new releases are available.
Authorization to File Financing Statements; Ratification Such Grantor hereby authorizes the Collateral Agent to file, and if requested will deliver to the Collateral Agent, all financing statements and other documents and take such other actions as may from time to time be requested by the Collateral Agent in order to maintain a first priority perfected security interest in and, if applicable, Control of, the Collateral owned by such Grantor. Any financing statement filed by the Collateral Agent may be filed in any filing office in any UCC jurisdiction and may (i) indicate such Grantor’s Collateral (1) as all assets of the Grantor or words of similar effect, regardless of whether any particular asset comprised in the Collateral falls within the scope of Article 9 of the UCC or such jurisdiction, or (2) by any other description which reasonably approximates the description contained in this Security Agreement, and (ii) contain any other information required by part 5 of Article 9 of the UCC for the sufficiency or filing office acceptance of any financing statement or amendment, including (A) whether such Grantor is an organization, the type of organization and any organization identification number issued to such Grantor, and (B) in the case of a financing statement filed as a fixture filing or indicating such Grantor’s Collateral as as-extracted collateral or timber to be cut, a sufficient description of real Property to which the Collateral relates. Such Grantor also agrees to furnish any such information to the Collateral Agent promptly upon request. Such Grantor also ratifies its authorization for the Collateral Agent to have filed in any UCC jurisdiction any initial financing statements or amendments thereto if filed prior to the date hereof.
Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.
Engineer Payment of Subproviders No later than ten (10) days after receiving payment from the State, the Engineer shall pay all subproviders for work performed under a subcontract authorized hereunder. The State may withhold all payments that have or may become due if the Engineer fails to comply with the ten-day payment requirement. The State may also suspend the work under this contract or any work authorization until subproviders are paid. This requirement also applies to all lower tier subproviders, and this provision must be incorporated into all subcontracts.
Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements
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.
Acknowledgement and Consent to Bail-In of EEA Financial Institutions Notwithstanding anything to the contrary in any Loan Document or in any other agreement, arrangement or understanding among any such parties, each party hereto acknowledges that any liability of any EEA Financial Institution arising under any Loan Document, to the extent such liability is unsecured, may be subject to the write-down and conversion powers of an EEA Resolution Authority and agrees and consents to, and acknowledges and agrees to be bound by:
(a) the application of any Write-Down and Conversion Powers by an EEA Resolution Authority to any such liabilities arising hereunder which may be payable to it by any party hereto that is an EEA Financial Institution; and
(b) the effects of any Bail-in Action on any such liability, including, if applicable:
(i) a reduction in full or in part or cancellation of any such liability;
(ii) a conversion of all, or a portion of, such liability into shares or other instruments of ownership in such EEA Financial Institution, its parent undertaking, or a bridge institution that may be issued to it or otherwise conferred on it, and that such shares or other instruments of ownership will be accepted by it in lieu of any rights with respect to any such liability under this Agreement or any other Loan Document; or
(iii) the variation of the terms of such liability in connection with the exercise of the write-down and conversion powers of any EEA Resolution Authority.
