Regional Reliability Standard Sample Clauses

Regional Reliability Standard. “Regional Reliability Standard” shall mean a type of Reliability Standard that is applicable only within a particular Regional Entity or group of Regional Entities. A Regional Reliability Standard may augment, add detail to, or implement another Reliability Standard or cover matters not addressed by other Reliability Standards. Regional Reliability Standards, upon adoption by NERC and approval by the Commission, shall be Reliability Standards and shall be enforced within the applicable Regional Entity or Regional Entities pursuant to delegated authorities.
AutoNDA by SimpleDocs

Related to Regional Reliability Standard

  • Quality Standards Each Party agrees that the nature and quality of its products and services supplied in connection with the other Party's Marks will conform to quality standards set by the other Party. Each Party agrees to supply the other Party, upon request, with a reasonable number of samples of any Materials publicly disseminated by such Party which utilize the other Party's Marks. Each Party will comply with all applicable laws, regulations, and customs and obtain any required government approvals pertaining to use of the other Party's marks.

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

  • Safety Standards Performance of the Contract for all commodities or contractual services must comply with requirements of the Occupational Safety and Health Act and other applicable State of Florida and federal requirements.

  • Quality Service Standards Price Services and the Fund may from time to time agree to certain quality service standards, as well as incentives and penalties with respect to Price Services’ Services hereunder.

  • Reliability Reliability targets (Mean Time Between Failures (MTBF)) are defined in the technical specifications as set out in the Contract. Notwithstanding any possible application of penalties relating to reliability defined in the Contract, Goods shall remain covered by the warranty defined in this Article 16 as long as the reliability commitments have not been reached.

  • Standards for Determining Commercial Reasonableness Borrower and Silicon agree that a sale or other disposition (collectively, "sale") of any Collateral which complies with the following standards will conclusively be deemed to be commercially reasonable: (i) Notice of the sale is given to Borrower at least seven days prior to the sale, and, in the case of a public sale, notice of the sale is published at least seven days before the sale in a newspaper of general circulation in the county where the sale is to be conducted; (ii) Notice of the sale describes the collateral in general, non-specific terms; (iii) The sale is conducted at a place designated by Silicon, with or without the Collateral being present; (iv) The sale commences at any time between 8:00 a.m. and 6:00 p.m; (v) Payment of the purchase price in cash or by cashier's check or wire transfer is required; (vi) With respect to any sale of any of the Collateral, Silicon may (but is not obligated to) direct any prospective purchaser to ascertain directly from Borrower any and all information concerning the same. Silicon shall be free to employ other methods of noticing and selling the Collateral, in its discretion, if they are commercially reasonable.

  • 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”).

  • OMB Standards Unless specified otherwise within this agreement, the Subrecipient shall procure all materials, property, or services in accordance with the requirements of 24 CFR 84.40−48.

  • Security Standards The Provider shall implement and maintain commercially reasonable security procedures and practices that otherwise meet or exceed industry standards designed to protect Student Data from unauthorized access, destruction, use, modification, or disclosure, including but not limited to the unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of the Student Data (a "Security Breach"). For purposes of the DPA and this Exhibit G, "Security Breach" does not include the good faith acquisition of Student Data by an employee or agent of the Provider or LEA for a legitimate educational or administrative purpose of the Provider or LEA, so long as the Student Data is used solely for purposes permitted by SOPPA and other applicable law, and so long as the Student Data is restricted from further unauthorized disclosure.

  • Service Standards We provide the Services materially in accordance with the features and functionalities set out in the Specification Documents. We will use commercially reasonable efforts to make the Services available to you subject to operational requirements including maintenance and security.

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