5018 Storm Watch compliance Sample Clauses

5018 Storm Watch compliance. Subject to the exceptions that follow, NYISO will be “Compliant” at the 5018 interface when either of the following two conditions are satisfied, otherwise it will be “Non-compliant”: Flow on the 5018 interface was at or above the sum of the Target values for each Available Ramapo PAR described in Section 7.2.1 of this Schedule D at any point in the trailing (rolling) 15-minutes; or NYISO took at least two taps on each Available Ramapo PAR in the direction to increase flow into New York at any point in the trailing (rolling) 15-minutes. If PJM denies NYISO’s request to take one or more taps at a Ramapo PAR to increase flow into New York and achieve compliance at the 5018 interface, then NYISO shall be considered “Compliant” at the 5018 interface.
AutoNDA by SimpleDocs
5018 Storm Watch compliance. Subject to the exceptions that follow, NYISO will be “Compliant” at the 5018 interface when either of the following two conditions are satisfied, otherwise it will be “Non-compliant”:

Related to 5018 Storm Watch compliance

  • PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.

  • Xxxxxx Compliance The Union shall comply with the requirements set forth in Chicago Teachers Union x. Xxxxxx, 475 U.S. 292 (1986) for the deduction of agency shop fees. Annually, the Union shall certify in writing to the City that the Union has complied with the requirements set forth in this section and in Xxxxxx, 475 U.S. 292.

  • Statutory Compliance ‌ The Union and the Employer agree to cooperate fully in matters pertaining to the prevention of accidents and occupational disease and in the promotion of the health and safety of all employees. There shall be full compliance with all applicable statutes and regulations pertaining to the working environment.

  • OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

  • CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.

  • Law Compliance In providing the SOLID WASTE HANDLING SERVICES required by this AGREEMENT, CONTRACTOR shall observe and comply with all applicable federal and, state laws, regulations and codes regarding the provision of the SOLID WASTE HANDLING SERVICES described herein, as such may be amended from time to time, including where required by such laws, the funding and maintenance of sufficient closure and post-closure maintenance financial assurances for any landfill operated or utilized by CONTRACTOR for disposal of the SOLID WASTE. Any violation of this Paragraph shall constitute a major breach.

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • ETHICS COMPLIANCE All Bidders/Contractors and their employees must comply with the requirements of Sections 73 and 74 of the Public Officers Law, other State codes, rules, regulations and executive orders establishing ethical standards for the conduct of business with New York State. In signing the Bid, Bidder certifies full compliance with those provisions for any present or future dealings, transactions, sales, contracts, services, offers, relationships, etc., involving New York State and/or its employees. Failure to comply with those provisions may result in disqualification from the Bidding process, termination of contract, and/or other civil or criminal proceedings as required by law.

  • PCI-DSS Compliance Merchant shall be in full compliance with rules, regulations, guidelines and procedures adopted by any Card Association or Payment Network relating to the privacy and security of Cardholder and Card transaction data, including without limitation the most up-to-date version of the Payment Card Industry Data Security Standard (PCI-DSS), as amended from time to time by the Payment Card Industry Security Standards Council. Detailed information pertaining to aforementioned requirements may be found at xxxxx://xxx.xxxxxxxxxxxxxxxxxxxx.xxx. Additional information regarding security requirements may be found on the Card Association’s respective web sites.

Time is Money Join Law Insider Premium to draft better contracts faster.