Fault Management and Service Availability Sample Clauses

Fault Management and Service Availability 
AutoNDA by SimpleDocs

Related to Fault Management and Service 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.

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

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

  • Utilization Management Contractor shall maintain a utilization management program that complies with applicable laws, rules and regulations, including Health and Safety Code § 1367.01 and other requirements established by the applicable State Regulators responsible for oversight of Contractor.

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

  • Management and Control Systems Grantee will: 1. maintain an appropriate contract administration system to ensure that all terms, conditions, and specifications are met during the term of the contract through the completion of the closeout procedures. 2. develop, implement, and maintain financial management and control systems that meet or exceed the requirements of Uniform Statewide Accounting System (UGMS). Those requirements and procedures include, at a minimum, the following: i. Financial planning, including the development of budgets that adequately reflect all functions and resources necessary to carry out authorized activities and the adequate determination of costs; ii. Financial management systems that include accurate accounting records that are accessible and identify the source and application of funds provided under each Contract of this Contract, and original source documentation substantiating that costs are specifically and solely allocable to a Contract and its Contract and are traceable from the transaction to the general ledger; iii. Effective internal and budgetary controls; iv. Comparison of actual costs to budget; determination of reasonableness, allowableness, and allocability of costs; v. Timely and appropriate audits and resolution of any findings; vi. Billing and collection policies; and vii. Mechanism capable of billing and making reasonable efforts to collect from clients and third parties.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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

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

  • Measurement and Billing 5.6.1 For billing purposes, each Party shall pass Calling Party Number ("CPN") information on each call carried over the Traffic Exchange Trunks at such time as the originating switch is equipped for SS7 and from all switches no later than December 31, 1998. At such time as either Party has the ability, as the Party receiving the traffic, to use such CPN information to classify on an automated basis traffic delivered by the other Party as either Local Traffic or Toll Traffic, such receiving Party shall xxxx the originating Party the Local Traffic termination rates, Intrastate Exchange Access rates, or Interstate Exchange Access rates applicable to each minute of Traffic for which CPN is passed, as provided in Exhibit A and applicable Tariffs. 5.6.2 If, under the circumstances set forth in subsection 5.6.1, the originating Party does not pass CPN on up to ten percent (10%) of calls, the receiving Party shall xxxx the originating Party the Local Traffic termination rates, Intrastate Exchange Access rates, Intrastate/Interstate Transit Traffic rates, or Interstate Exchange Access rates applicable to each minute of traffic, as provided in Exhibit A and applicable Tariffs, for which CPN is passed. For the remaining up to ten percent (10%) of calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic as Local Traffic termination rates, Intrastate Exchange Access rates, Intrastate/Interstate Transit Traffic rates, or Interstate Exchange Access rates applicable to each minute of traffic, as provided in Exhibit A and applicable Tariffs, in direct proportion to the minutes of use of calls passed with CPN information. 5.6.3 If the originating Party does not pass CPN on more than ten percent (10%) of calls, or if the receiving Party lacks the ability to use CPN information to classify on an automated basis traffic delivered by the other Party as either Local Traffic or Toll Traffic, and the originating Party chooses to combine Local and Toll Traffic on the same trunk group, it will supply an auditable Percent Local Use ("PLU") report quarterly, based on the previous three months' traffic, and applicable to the following three months. If the originating Party also chooses to combine Interstate and Intrastate Toll Traffic on the same trunk group, it will supply an auditable Percent Interstate Use ("PIU") report quarterly, based on the previous three months' terminating traffic, and applicable to the following three months. In lieu of the foregoing PLU and/or PIU reports, the Parties may agree to provide and accept reasonable surrogate measures for an agreed-upon interim period. 5.6.4 Measurement of billing minutes for purposes of determining terminating compensation shall be in conversation seconds.

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