Error Correction If an error results from an act or omission of the Custodian in performing the services under this Agreement, the Custodian may take such remedial action as it considers appropriate under the circumstances, which may include effecting corrective transactions involving the Client’s assets, where and to the extent reasonably necessary to place the Client in the position (or its equivalent) it would have been had the error not occurred. The Custodian will be responsible for Losses arising from its errors in accordance with the terms of this Agreement and will be entitled to retain gains arising from its errors or related remedial actions unless otherwise prohibited by Law. Where an error results in a series of related Losses and gains, the Custodian will be entitled to net gains against Losses when permitted by Xxx. The Custodian will have no duty to notify or account to the Client for any Loss or gain associated with an error it has fully remediated.
Correction No corrections shall be made in the tender documents. Any corrections that are to be made shall be made by crossing the incorrect portion and writing the correct portions above with the initials of tenderer.
Correction of Errors Contractor shall perform, at its own cost and expense and without reimbursement from the District, any work necessary to correct errors or omissions which are caused by the Contractor’s failure to comply with the standard of care required herein.
Corrections There may be information on the Services that contains typographical errors, inaccuracies, or omissions, including descriptions, pricing, availability, and various other information. We reserve the right to correct any errors, inaccuracies, or omissions and to change or update the information on the Services at any time, without prior notice.
Equipment Failures In the event of equipment failures beyond the Administrator's control, the Administrator shall take reasonable and prompt steps to minimize service interruptions but shall have no liability with respect thereto. The Administrator shall develop and maintain a plan for recovery from equipment failures which may include contractual arrangements with appropriate parties making reasonable provision for emergency use of electronic data processing equipment to the extent appropriate equipment is available.
Post-Accident Testing a. The City may require a Covered Employee who caused, or may have caused, an Accident, based on information known at the time of the Accident, to submit to drug and/or alcohol testing.
b. Following an Accident, all Covered Employees subject to testing shall remain readily available for testing. A Covered Employee may be deemed to have refused to submit to substance abuse testing if the employee fails to remain readily available, including failing to notify a supervisor (or designee) of the Accident location, or leaving the scene of the Accident prior to submitting to testing.
c. Nothing in this section shall delay medical attention for the injured following an Accident or prohibit an employee from leaving the scene of an Accident for the period necessary to obtain assistance in responding to the Accident or to obtain necessary emergency medical care.
d. If the City requires a Covered Employee to be tested post-Accident, then the employee may ask for representation. Representation may include, but is not limited to, union representatives and shop stewards. If the employee requests representation, the City shall allow a reasonable amount of time from the time the employee is notified that the employee will be tested (a maximum of one hour) for the employee to obtain representation provided that the union representative meet the employee at the Accident site, work location or testing center as determined by the City. Such request shall not delay the administration of the tests for more than one hour from the time the employee is notified that the employee will be tested.
e. As soon as reasonably possible after the occurrence of an Accident, the supervisor or other City representative at the Accident scene shall make best efforts to contact the Department of Human Resources (DHR) or designee, and DHR or designee shall then make best efforts to telephone the union(s) first designated representative on file with DHR representing the Covered Employee(s) involved in the Accident. If the first designated representative does not answer, DHR or designee shall leave a voice mail message notifying the union of the Accident and telephone the union(s) second designated representative on file with DHR. For purposes of this paragraph, a designated representative shall be any union officer or employee whose telephone number is on file with DHR for the purpose of Accident review. The union may change the designated representative, in writing, as necessary from time to time, but it is the sole responsibility of the union to ensure that a current telephone number (with voice mail capability) for two designated representatives are on file with DHR.
Rectification Where the surface irregularity of sub-grade and the various pavement course fall outside the specified tolerances contractor shall be liable .to rectify these in the manner described below and to the satisfaction of the Engineer - in-charge. .
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.
6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1.
6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <xxxxx://xxx.xxx-‐xxxx.xxx/xxxx/xxxx/xxxx>.
6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released.
6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process.
4.2.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for Louisville Telephone when Louisville Telephone serves an end-user with four (4) or more voice-grade (DS-0) equivalents or lines served by BellSouth in one of the following MSAs: Atlanta, GA; Miami, FL; Orlando, FL; Ft. Lauderdale, FL; Charlotte-Gastonia-Rock Hill, NC; Greensboro-Winston Salem-High Point, NC; Nashville, TN; and New Orleans, LA, and BellSouth has provided non- discriminatory cost based access to the Enhanced Extended Link (EEL) throughout Density Zone 1 as determined by NECA Tariff No. 4 as in effect on January 1, 1999.
4.2.3 In the event that Louisville Telephone orders local circuit switching for an end user with four (4) or more DS0 equivalent lines within Density Zone 1 in an MSA listed above, BellSouth shall charge Louisville Telephone the market based rates in Exhibit B for use of the local circuit switching functionality for the affected facilities.
Epidemic Failure Warranty Supplier warrants all Products against Epidemic Failure for a period of three years after DXC’s Acceptance. Epidemic Failure means the occurrence of the same failure, defect, or non-conformity with an Order in 2% or more of Products within any three-month period.
