SYSTEM HOSTING Clause Samples

SYSTEM HOSTING. The Service Provider will host all perimeter networking and security hardware supported under this SLA in a secure and fire-protected environment, with temperature control and UPS.
View SourceView Similar (2)
SYSTEM HOSTING. The Contractor shall provide system hosting in a DoD-approved hosting environment with minimal dependencies on entities outside the Contractor’s team. The environment shall support mature Infrastructure as a Service & Software as a Service capabilities for the Contractor and Government technical teams. The hosting environment must be agile, responsive, and easy to reconfigure server, network, and environment specs. Authorized Cloud Service Providers through the Federal Risk and Authorization Management Program (FedRAMP) are approved provided they prove the ability to meet all applicable Army and DoD Information Assurance and Information Technology regulations, standards, policies, and best practices and enable the MDMS to maintain its RMF accreditation.
View Source
SYSTEM HOSTING. 6.1 If the Supported Software is hosted by You under separate third part support agreement, You shall be responsible for all aspects of the System Hosting. You shall take all reasonable steps required to resolve problems affecting, or likely to affect the Service, which are the result of any faults, errors or deficiencies in the System. We shall have no liability for unavailability of the Service due to problems with the System.
View Source
SYSTEM HOSTING. 7.1 The Service Provider utilises a Microsoft Azure cloud server environment. 7.2 The services provided under this agreement shall be hosted primarily within the United Kingdom (UK) regions. The primary hosting region shall be UK South, located in data centres situated in London. In the event of a failover, services shall be transitioned to the UK West region, located in Wales. 7.3 All disaster recovery procedures shall be initiated and executed within UK regions. 7.4 Full backups for databases are performed every night at midnight. 7.5 The Service Provider shall maintain backups according to the following retention schedule: Daily backups shall be retained for a period of 14 days. Monthly backups shall be retained for a period of one month.
View Source
SYSTEM HOSTING. 7.1 The Service Provider utilises a cloud server environment provided by Rackspace (▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇.▇▇). The Service Level Agreement with Rackspace is annexed to this Agreement as Schedule 7.
View Source
SYSTEM HOSTING. Clever Devices hosted solutions provide the following: Managed Services Clever Devices will provide system administration and troubleshooting, apply system patches, manage data backup and retention, maintain network uptime, guarantee that the software application and the server will be up and running, and respond to configuration issues quickly and correctly. High Availability VMware virtualization will provide high availability across the County’s entire virtualized IT environment. Bandwidth Dedicated servers come with a specific amount of included bandwidth, and additional bandwidth is available at pre-paid rates. The hosted solutions provide enough bandwidth to support the County’s IT environment and ensure optimal performance and availability. Backups Daily server snapshots and database backups are performed and stored offsite. Scalability The hosting solutions provide the capacity to run the County’s solution and scalability to support future growth. Above Hosting Pricing is based on 80 buses. Any changes to that will reflect into change in the pricing.
View Source

Related to SYSTEM HOSTING

  • ▇▇▇ Hosting 10.1 ▇▇▇ Hosting is not required for resale in the BellSouth region.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Hosting 44.7.4.1 At CLEC’s request, SBC-10STATE shall perform hosting responsibilities for the provision of billable message data and/or access usage data received from CLEC for distribution to the appropriate billing and/or processing location or for delivery to CLEC of such data via SBC-10STATE’s internal network or the nationwide CMDS network pursuant to the applicable Appendix HOST, which is/are attached hereto and incorporated herein by reference.

  • System Use (a) An electronic site access system may be used on site, subject to the requirements of this statement. (b) The system operates via: (i) a facial recognition device; and (ii) an electronic gate. (c) The system will be installed at the access and egress point/s of the site and will only be utilised to identify presence on site. (d) The purpose for which the electronic site access system will be implemented is to ensure: (i) avoiding unauthorised access to site; (ii) confirmation and co-ordination of effort in emergency situations; and (iii) confirmation that all entrants to site have received a site specific induction; (e) The only personal data collected by the system is a site entrant’s: (i) image; (ii) first & last name; (iii) mobile phone number; (iv) email address; and (v) employer’s name. (the Collected Data) (f) The Collected Data will only be held or used for the purposes specified above, unless otherwise by consent or required by law. (g) The Employer will not use the electronic site access control system to verify who was on a site at a particular time for the purpose of: (i) evaluating whether a variation claim regarding labour costs made by a subcontractor can be substantiated; (ii) taking disciplinary action against an Employee, or assisting a subcontractor to take disciplinary action against its own employees, regarding their start and finish times; or (iii) otherwise generally tracking a worker’s movements whilst on the site.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2