System Availability and Reliability Sample Clauses

System Availability and Reliability. 1.1. The Vendor shall take every precaution to ensure that all systems, files, data, equipment, communications, and facilities are reliable. 1.2. In the event that a disaster does disrupt the System, the Vendor shall have an up-to-date detailed recovery plan that shall be ready to be implemented so that services are restored within a reasonable timeframe. 1.3. The system must be designed to minimize disruption due to failure of one or more components of the system and should be designed in a manner that allows it to be quickly brought back to the state of full operation in the event of a system failure. 1.4. In the event of an outage related to any part of the Vendor-maintained system, the City must immediately inform the Vendor of the following information: 1.4.1. Date and time of the outage 1.4.2. Duration of the outage 1.4.3. What aspects of the system were potentially affected during the outage 1.5. After notification of an outage, the Vendor must respond with the following information: 1.5.1. Cause and resolution of the outage 1.5.2. Any resulting adverse effects on customer transactions or City data after the resolution of the problem
Sample 1
AutoNDA by SimpleDocs
System Availability and Reliability. 1. The System will maintain a grade of service so that no greater than one (1) call attempt per five hundred (500) call attempts during the Average Busy Hour of the busiest four (4) consecutive weeks, of the preceding fifty-five (55) weeks, will encounter a busy condition. 2. The required reliability percentage for the System during any calendar year is ninety-nine point nine-nine-nine percent (99.999%) uptime, defined as the ability to deliver a call properly presented at the ingress demarcation point to an available call taker. 3. The System will be able to deliver the call to a call taker in the designated destination call taker group ninety-nine point nine-nine percent (99.99%) of the time unless the call is re-directed due to all call taker busy or ring-no-answer timeouts in the destination call taker group. 4. The System will provide redundant and diverse connections for call originating network interconnections to the ESInet. 5. Individual Answering Positions shall be available ninety-nine point nine percent (99.9%) of the time. 6. For each PSAP, the System will provide two (or more) IP addresses at the NENA i3 demarcation to which calls can be presented for delivery to the PSAP. The supplied LNG or NG911 services shall be able to fail over to an alternate SIP IP address in the event that the IP- based 911 Call Answering System is busy or does not respond correctly to the initial SIP INVITE. 7. All measurements for compliance with this section 11 shall be based on the calendar year. 8. No more than five (5) minutes of unscheduled downtime (a “Major Failure”) will occur across the State in any 12 month period. 9. No more than five (5) minutes total of scheduled downtime for an entire PSAP (a “Minor Failure”) will occur in any 12-month period. 10. A given instance of System downtime shall start after receipt of notification to the Contractor of a Major Failure or Minor Failure from the CSSPDN NOC, from a PSAP, from the Department, or from the Contractor's own monitoring system(s), and end with notification by the Contractor to the Department and any designee (e.g., the CSSPDN NOC) that such System status has been fully restored to the applicable agreed operational specifications and made ready for 9-1-1 as well as routine use, and upon confirmation of such restoration by the Department.
Sample 1

Related to System Availability and Reliability

  • System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

  • General Availability The commitment to availability specified in the letter of appointment shall be subject to mutually acceptable revision. Such revision will occur once per year, or, if mutually agreed between the Employer and the employee, on a more frequent basis. The Employer will issue a revised letter of appointment to reflect approved changes to employee’s general availability.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • Minimum Availability Borrower shall have minimum availability immediately following the initial funding in the amount set forth on the Schedule.

  • DNS service availability Refers to the ability of the group of listed-­‐as-­‐authoritative name servers of a particular domain name (e.g., a TLD), to answer DNS queries from DNS probes. For the service to be considered available at a particular moment, at least, two of the delegated name servers registered in the DNS must have successful results from “DNS tests” to each of their public-­‐DNS registered “IP addresses” to which the name server resolves. If 51% or more of the DNS testing probes see the service as unavailable during a given time, the DNS service will be considered unavailable.

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

  • High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-­‐level redundancy, end-­‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • Product Availability Under no circumstances shall Company be responsible to Representative or anyone else for its failure to fill accepted orders, or for its delay in filling accepted orders, when such failure or delay is due to strike, accident, labor trouble, acts of nature, freight embargo, war, civil disturbance, vendor problems or any cause beyond Company's reasonable control.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!