Minimum Service Compliance Standards Sample Clauses

Minimum Service Compliance Standards. In order for Client’s existing environment to qualify for GWT Services, the following requirements must be met or a plan in place to remediate:
Sample 1
AutoNDA by SimpleDocs
Minimum Service Compliance Standards. In order for the Supplier to meet the service obligations we provide minimum service compliance standards. If the Client does not have all of these minimum standards in place before the Client’s agreement start date, the Supplier will work with you on a plan to bring the Client’s environment up to our minimum standards. The Supplier understands that this may take some time depending on timing and budgets so the Supplier will support any items that do not currently meet the Supplier’s minimum standards on a best effort basis outside of SLA. However, if an item requiring support does not meet the Supplier’s Minimum Standards, it will be supported but not covered in the SLA and may be chargeable. The Supplier will advise in advance if any additional charges are applicable. Examples of the Supplier’s minimum standards are as follows; the complete minimum standards policy is available upon request. • All Servers with Microsoft Windows Operating Systems must not be in an End-of-Life state and have all of the latest Microsoft Service Packs and Critical Updates installed. • All Desktop PC’s and Notebooks/Laptops with Microsoft Windows Operating Systems must not be in an End-of-Life state and have all of the latest Microsoft Service Packs and Critical Updates installed. • All Server and Desktop Software must be Genuine, Licensed and Vendor-Supported. • The environment must have a currently licensed, up-to-date and Vendor-Supported Antivirus Solution protecting all Servers, Desktops, Notebooks/Laptops, and Email. • The environment must have a currently licensed, Vendor-Supported Backup Solution. • The environment must have a currently licensed, Vendor-Supported Hardware Firewall between the Internal Network and the Internet. • Any Wireless data traffic in the environment must be secured with a minimum of 128bit data encryption
Sample 1

Related to Minimum Service Compliance Standards

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

  • Noncompliance Standards The AGENCY shall be responsible for adhering to all terms and conditions of this Contract. Noncompliance may result in penalties as stipulated in Attachment “C”.

  • Minimum Standards (a) It is intended that the provisions contained in the Employment Standards Act and Regulations (Act), presently in effect and from time to time amended, are minimum requirements only.

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

  • Maintenance Standards Unless otherwise authorized by the CRC Board, the General Manager shall prepare and submit to the CRC Board proposals (including the Program Maintenance plan submitted pursuant to Section 5(b)) for the performance of such Routine Maintenance and Program Maintenance as is reasonably necessary to keep and maintain the Shared Assets substantially in their condition as of the date of this Agreement. If the CRC Board fails either to approve or disapprove by majority vote any such proposal within 45 days after it was submitted to the CRC Board, the disagreement over the propriety or need for any of the Routine Maintenance or Program Maintenance included in such proposal may be submitted by either Operator for resolution by binding arbitration pursuant to Section 13.

  • Minimum System Requirements The following summarizes the minimum office system requirements for all Contractors and Architect/Engineer to possess in order to participate. It is the responsibility of all Contractors and Architect/Engineer to possess these minimum requirements at no additional cost to Princeton University.

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

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

  • Penalties for Non-compliance to Service Level Agreement Where the Supplier/Service Provider fails to deliver the Goods/Services within the agreed and accepted milestone timelines and provided that the cause of the delay was not due to a fault of Transnet, penalties shall be imposed at …………………………………………………… .

  • Customer Service Standards The Franchising Authority hereby adopts the customer service standards set forth in Part 76, §76.309 of the FCC’s rules and regulations, as amended. The Grantee shall comply in all respects with the customer service requirements established by the FCC.

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