Server Availability Sample Clauses

Server Availability. The System Administrator will strive to maintain continuous availability by design and by practice. Necessary and planned downtime will be scheduled when it will have least impact, for the shortest possible amount of time, and will only come after timely communication to all participants. If a user discovers server is down, the user will report immediately to their Agency Administrator. The System Administrator will notify users by email if they become aware server is down (unplanned). All other procedures for maximizing server availability, recovering from unplanned downtime, communicating, and avoiding future downtime are the responsibility of the System Administrator and Wellsky Information Systems.

Server Availability. MSC production server will be operated with the goal of being available for use by Member Libraries for circulation and other transactions 24 hours a day, 7 days a week, 365 days a year, except for scheduled maintenance and upgrades. Uptime/downtime statistics will be tracked. Availability statistics can be viewed on the MSL website. Downtime will be scheduled so as to cause the least disruption of service. The MSC system administrators agree to provide participants with at least 24 hours prior notice of scheduled system downtime. In cases of downtime due to emergency system maintenance, the system administrators will attempt to provide as much advance notice as possible. Access will be via the Internet; Internet access is the responsibility of each Member Library.

Server Availability. Company’s servers are monitored 24 hours a day, 7 days a week, 365 days per year and support agents are available by phone or email as posted in the support section of Company site. Company is fully committed to providing quality service to all customers. To support this commitment, Company sets a 99.999% uptime benchmark.

Server Availability. 5.1. We shall provide you with sufficient technical information to allow you to connect to and use the Server. 5.2. You cannot, and may not, physically access the Server, nor visit or access the data centre. 5.3. We shall use our reasonable endeavours to make the Server available for you to connect to and use.

Server Availability. Server Availability shall consist of the following components that are provided as part of DYOPATH’s Services:  Virtual Servers provided on DYOPATH High Availability platform,  Storage provided on DYOPATH Storage Area Network (SAN) devices, and  Server primary services/applications which are provided by DYOPATH (e.g. Exchange) Client owned physical servers or other network connected devices co‐located in the DYOPATH cage are not included in this Service Level Category. DYOPATH only provides Infrastructure Availability for these devices. Server Availability including primary services (Metric 16) Server and primary services for the overall virtual data center available 99.5% of the time; excluding scheduled maintenance. Reported monthly. DYOPATH and the Client will jointly identify Critical Server and Critical Server clusters and availability will be reported and tracked accordingly. Critical Servers and related applications include, without limitation, the following (Others may be added from time to time in the form of a contract amendment):

Server Availability. PayByPhone operates on industrial grade hardware and software to maintain a fully redundant and fault tolerant service in a carrier-grade data centre. PayByPhone monitors system loads and will provision new hardware as loads approach threshold levels. Even when loads do not justify additional hardware, PayByPhone ensures that all system functionality is balanced and failed over onto redundant hardware. PayByPhone’s targeted server availability is as follows: Item Function Availability Web servers Back-office, customer web interface 99.0% IVR servers Hosting of IVR applications 99.0% SMS servers Hosting of SMS applications (text reminders etc.) 99.0% The above server availability excludes any downtime for (a) PayByPhone to install product updates or make mutually agreed corrections, (b) scheduled maintenance, and (c) downtime arising due to failure of third parties, including but not limited to utilities and wireless carriers, to provide services. 3.1 System performance benchmarks Item Activity % of responses Response Time Notes: ‘Response Time’ is defined as the elapsed time between PayByPhone’s servers receiving a query request and transmitting the required response.

Server Availability. The table set forth in Schedule 1.2, tab 2.1 sets forth the Service Levels for Server Availability Server Availability percentage will be calculated as follows: • (Total Up-Time divided by (Maximum Up-Time minus Excluded Down-Time)) times 100 where: – Total Up-Time = The maximum up-time minus all down-time. – Maximum Up-Time = The maximum number of minutes available in a month is the number of days in the month × 24 hours × 60 minutes = maximum up-time. – Excluded Down-Time = The number of minutes of any planned or scheduled down-time, plus the number of minutes of any down-time resulting from non the Vendor-supported hardware or software that would be considered outside the control of the Vendor as as described in Schedule 1.2 – Service Level Matrix. – The following table is meant as an example of SLA thresholds. 28 24 60 40,320 201.6 29 24 60 41,760 208.8 30 24 60 43,200 216.0 31 24 60 44,640 223.2 3. 2. 1. 1 S e r v e r A v a il a bility A l e r ts The table set forth in Schedule 1.2, tab 3.1 sets forth the Service Levels for Server Availability. Alerts are further described in Schedule 1.2, tab 3.2.

Server Availability. Letsignit Servers are monitored 24 hours a day, 7 days a week, 365 days per year and support agents are available by phone or email as posted in the support section of the Letsignit website. Letsignit is fully committed to providing quality service to all customers. To support this commitment, Letsignit sets a 99.95% uptime benchmark. When the service is unavailable or malfunctions, an incident ticket is automatically sent through an alert received by the team under Letsignit. The application of the guarantee of the level this service is thus done on the creation of this ticket of the incident.

Server Availability. 6.6.1. The System Administrator will strive to maintain continuous availability of the HMIS. 6.6.2. When possible, necessary downtime will be scheduled when it will have least impact, for the shortest possible amount of time, and after timely communication to all participants. 6.6.3. If a User discovers that the HMIS is not available or accessible, the User will report immediately to their Agency Administrator who will, in turn, investigate and inform the System Administrator. The System Administrator will notify Users by email if they become aware the server is unexpectedly down. 6.6.4. All other procedures for maximizing server availability, recovering from unplanned downtime, communicating, and avoiding future downtime are the responsibility of the System Administrator and WellSky.