Standards for GRRC Approval Sample Clauses

Standards for GRRC Approval. GRRC cannot approve a rule unless:
AutoNDA by SimpleDocs

Related to Standards for GRRC Approval

  • Standards for Network Elements 1.8.1 BellSouth shall comply with the requirements set forth in the technical references, as well as any performance or other requirements identified in this Agreement, to the extent that they are consistent with the greater of BellSouth’s actual performance or applicable industry standards.

  • Human and Financial Resources to Implement Safeguards Requirements 6. The Borrower shall make available necessary budgetary and human resources to fully implement the EMP and the RP.

  • Standards of Conduct Whenever the Member is required or permitted to make a decision, take or approve an action, or omit to do any of the foregoing, then the Member shall be entitled to consider only such interests and factors, including its own, as it desires, and shall have no duty or obligation to consider any other interests or factors whatsoever. To the extent that the Member has, at law or in equity, duties (including, without limitation, fiduciary duties) to the Company or other person bound by the terms of this Agreement, the Member acting in accordance with the Agreement shall not be liable to the Company or any such other person for its good faith reliance on the provisions of this Agreement. The provisions of this Agreement, to the extent that they restrict the duties of the Member otherwise existing at law or in equity, replace such other duties to the greatest extent permitted under applicable law.

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference. Adherence to these accessible technology standards is one way to ensure compliance with the College’s underlying legal obligations to ensure that people with disabilities are able to acquire the same information, engage in the same interactions, and enjoy the same benefits and services within the same timeframe as their nondisabled peers, with substantially equivalent ease of use; that they are not excluded from participation in, denied the benefits of, or otherwise subjected to discrimination in any College programs, services, and activities delivered online, as required by Section 504 and the ADA and their implementing regulations; and that they receive effective communication of the College’s programs, services, and activities delivered online.

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

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

  • SUPPLIER STANDARDS OF CONDUCT Accenture is committed to conducting its business free from unlawful, unethical or fraudulent activity. Supplier will act in a manner consistent with the ethical and professional standards of Accenture as described in the Accenture Supplier Standards of Conduct, including prompt reporting of unlawful, fraudulent or unethical conduct. A copy of these standards can be found at xxxxxxxxx.xxx/xx- en/company-ethics-code.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • REGULATORY FILINGS AND CAISO TARIFF COMPLIANCE 3.1 Filing

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