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.
Human and Financial Resources to Implement Safeguards Requirements The Borrower shall make available necessary budgetary and human resources to fully implement the EMP and the RP.
Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.
Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.
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.
PROCUREMENT ETHICS Contractor understands that a person who is interested in any way in the sale of any supplies, services, construction, or insurance to the State of Utah is violating the law if the person gives or offers to give any compensation, gratuity, contribution, loan, reward, or any promise thereof to any person acting as a procurement officer on behalf of the State of Utah, or who in any official capacity participates in the procurement of such supplies, services, construction, or insurance, whether it is given for their own use or for the use or benefit of any other person or organization.
Standards Compliance 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”).
Financial Viability and Regulatory Compliance 2.6.1 Contractor warrants and represents that its corporate entity is in good standing with all applicable federal, state, and local licensing authorities and that it possesses all requisite licenses to perform the services required by this contract. Contractor further warrants and represents that it owes no outstanding delinquent federal, state or local taxes or business assessments. 2.6.2 Contractor agrees to promptly disclose to the MPHA any IRS liens or licensure suspension or revocation that may adversely affect its capacity to perform the services outlined within this contract. The failure by Contractor to disclose such issue to the MPHA in writing within 5 days of such notification received will constitute a material breach of this contract. 2.6.3 Contractor further agrees to promptly disclose to the MPHA any change of more than 50% of its ownership and/or any declaration of bankruptcy that Contractor may undergo during the term(s) of this contract. The failure of Contractor to disclose any change of more than 50% of its ownership and/or its declaration of bankruptcy within 5 days of said actions shall constitute a material breach of this contract. 2.6.4 All disclosures made pursuant to this section of the contract shall be made in writing and submitted to MPHA within the time periods required herein.
