Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.
Developer Operating Requirements The Developer must comply with the Transmission Owner’s operating instructions and requirements including but not limited to Transmission Owner’s Operation Coordination Agreement, as it may change from time to time. The Developer must comply with all applicable NYISO tariffs and procedures, as amended from time to time. Whether or not the Large Generating Facility is eligible for the Transition Period LVRT Standard set forth in Appendix G will be determined by the Commission. The Large Generating Facility will comply with the Transition Period LVRT Standard pending issuance of an order by the Commission determining the appropriate LVRT standard. For purposes of compliance with Appendix G, the Transmission Owner has determined that the Developer shall maintain the Large Generating Facility in service during a three-phase fault for 7 cycles. Infrastructure security of New York State Transmission System equipment and operations and control hardware and software is essential to ensure day-to-day New York State Transmission System reliability and operational security. The Commission will expect the NYISO, all Transmission Owners, all Developers and all other Market Participants to comply with the recommendations offered by the President’s Critical Infrastructure Protection Board and, eventually, best practice recommendations from the electric reliability authority. All public utilities will be expected to meet basic standards for system infrastructure and operational security, including physical, operational, and cyber-security practices. All personnel working in Transmission Owner’s facilities will require security background checks prior to entering and working in such facilities. New York Independent System Operator, Inc. Attn: Vice President, Operations 0000 Xxxxxx Xxxx Schenectady, NY 12303 Senior Vice President of Transmission New York Power Authority 000 Xxxx Xx. Xxxxx Xxxxxx, XX 00000-0000 Re: Large Generating Facility Dear : On [Date] [Developer] has completed Trial Operation of Unit No. . This letter confirms that [Developer] commenced Commercial Operation of Unit No. at the Large Generating Facility, effective as of [Date plus one day]. Thank you. NYISO:
Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.
Accounting Requirements CONTRACTOR shall comply with all applicable COUNTY, State, and Federal accounting laws, rules and regulations. CONTRACTOR shall establish and maintain accounting systems and financial records that accurately account for and reflect all Federal funds received, including all matching funds from the State, COUNTY and any other local or private organizations. CONTRACTOR’S records shall reflect the expenditure and accounting of said funds in accordance with all applicable State laws and procedures for expending and accounting for all funds and receivables, as well as meet the financial management standards in 45 CFR Part 92 and in the Office of Management and Budget 2 CFR Part 200 “Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards.”
Financial Reporting Requirements The Charter School shall follow the financial requirements of the Charter Schools Section of the Department’s Financial Management for Georgia Local Units of Administration Manual. The Charter School shall submit all information required by the State Accounting Office for inclusion in the State of Georgia Comprehensive Annual Financial Report.
Reporting Requirement (1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at xxxxx://xxxxxx.xxx.xxx. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at xxxxx://xxxxxx.xxx.xxx.
(2) The Contractor shall report the following information pursuant to paragraph (d)(1) of this clause
(i) Within one business day from the date of such identification or notification: the contract number; the order number(s), if applicable; supplier name; supplier unique entity identifier (if known); supplier Commercial and Government Entity (CAGE) code (if known); brand; model number (original equipment manufacturer number, manufacturer part number, or wholesaler number); item description; and any readily available information about mitigation actions undertaken or recommended.
(ii) Within 10 business days of submitting the information in paragraph (d)(2)(i) of this clause: any further available information about mitigation actions undertaken or recommended. In addition, the Contractor shall describe the efforts it undertook to prevent use or submission of covered telecommunications equipment or services, and any additional efforts that will be incorporated to prevent future use or submission of covered telecommunications equipment or services.
Testing Requirements 12.1. Workplaces -
12.2. On workplaces where the value of the Commonwealth’s contribution to the project that includes the building work is at least $5,000,000, and represents at least 50% of the total construction project value or the Commonwealth’s contribution to the project that includes the building work is at least $10,000,000 (irrespective of its proportion of the total construction project value) the following minimum testing requirements must be adhered to.
Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.
Special Reporting Requirements Reports must be prepared using forms and procedures prescribed by OHA. Forms are located at xxxx://xxx.xxxxxx.xxx/OHA/HSD/AMH/Pages/Reporting- Requirements.aspx.
(1) Within 30 calendar days of the County providing A&D 63 Services, County shall prepare and electronically submit a written entry baseline assessment report to xxxxxxxxxxx.xxxxxxxxxxxxx@xxxxxx.xxxxx.xx.
Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and
(b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.
