Required Standard Sample Clauses

POPULAR SAMPLE Copied 1 times
Required Standard. Powermetric will perform the Metering Services in a professional and efficient manner and in accordance with all relevant Australian Standards, authorisations, laws and any relevant processes and procedures under the Rules.
View SourceView Similar (3)
Required Standard all the reasonable skill, care and diligence to be expected of a qualified and experienced member of the CMC's profession undertaking the Services on works similar in scope and character to the Project.
View SourceView Similar (2)
Required Standard. The Carrier shall answer 80% of members’ telephone calls by a live voice (during operating hours) within 30 seconds.
View SourceView Similar (2)
Required Standard all the reasonable skill, care and diligence to be expected of a qualified and experienced member of the Consultant's profession undertaking the Services on works similar in scope and character to the Project. Services: the services referred to in the Professional Appointment, performed by or on behalf of the Consultant under the Professional Appointment.
View Source
Required Standard. The services performed hereunder in connection with the Business shall be performed in good faith, with reasonable care and shall be performed in a timely manner consistent with Healthbanks’ historical practice.
View Source

Related to Required Standard

  • Meets Standard The school materially complies with applicable laws, rules, regulations and provisions of the charter contract relating to health and safety, including but not limited to: • Health clearances and immunizations • Prohibiting smoking on campus • Appropriate student health services • Safety plan

  • Minimum Necessary Standard Business Associate shall apply the HIPAA Minimum Necessary standard to any Use or disclosure of PHI necessary to achieve the purposes of this Contract. See 45 CFR 164.514 (d)(2) through (d)(5).

  • W-9 Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a properly completed Internal Revenue Service (“IRS”) Form W-9. The purpose of the W-9 form is to document the SS# or FEIN# per the IRS. Note: W-9s submitted for any other entity name other than the Grantee’s will not be accepted.

  • 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 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇.▇▇▇. 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 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇.▇▇▇. (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.

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