Reliability Risk / Epidemic Failures Sample Clauses

Reliability Risk / Epidemic Failures. In the event a defect in material or workmanship or failure to meet Specifications is discovered in any Product, including any defect that is not identified by the requisite Product test screens, sort or final testing, and such defect would indicate an unacceptable reliability risk to the performance or expected life of such Product, the Parties will promptly cooperate by doing a failure analysis to ascertain the root cause for such defect. SCI will make all commercially reasonable efforts to implement appropriate manufacturing changes to prevent the reoccurrence of any such defects. For the purposes of this Agreement, “Epidemic Failure” will be deemed to have occurred if more than [*] of any Wafer Lot, shipment, or Order should fail in substantially the same manner. In the case of Epidemic Failure, SCI and LSI will promptly cooperate to resolve the Epidemic Failure and implement the following procedure:
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Reliability Risk / Epidemic Failures

  • Epidemic Failure “Epidemic Failure” for any particular Product shall mean a failure resulting from defects in material, workmanship, and manufacturing process, including but not limited to the use of Components with known defects. The Epidemic Failure clause shall be invoked [***]. The failure rate may be calculated [***], as determined by BUYER. Epidemic failures do not supersede the requirements of any expressed or implied warranty defined herein. In the case of an epidemic failure, SUPPLIER’s obligation is to propose an action plan to fix the failure of any affected Product within seventy-two (72) hours of discovery. SUPPLIER shall implement this action plan upon BUYER’s acceptance thereof. If the action plan is not acceptable to BUYER, BUYER can require SUPPLIER to repair or replace, at BUYER’s option, the affected Product. In addition to bearing the costs associated therewith, if requested by BUYER, SUPPLIER shall support and provide at SUPPLIER’s expense a sufficient number of units of the Product to permit the field exchange or “hot swap” of Products at customer sites. The parties agree to make all reasonable efforts to complete the repair or replacement of all affected Products within eight (8) Business Days after written notice of epidemic failure by BUYER to SUPPLIER. SUPPLIER also agrees that BUYER will be supported with accelerated shipments of replacement Product to cover BUYER’s supply requirements. If an Epidemic Failure is caused by (i) a design, including a BUYER-provided test process, as required by the Specifications or (ii) a failure by a Component required by the Specifications, (iii) misuse or damage during transit or damage by a third party at no fault of SUPPLIER, SUPPLIER shall perform the obligations in this Section 10.5 and BUYER shall pay to SUPPLIER the fees mutually agreed upon by the parties in writing. If an Epidemic Failure is caused by any other reason other than as set forth in the immediately preceding sentence, SUPPLIER shall perform the obligations set forth in this Section free of charge. Confidential treatment is being requested for portions of this document. This copy of the document filed as an exhibit omits the confidential information subject to the confidentiality request. Omissions are designated by the symbol [***]. A complete version of this document has been filed separately with the Securities and Exchange Commission.

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

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

  • Shortages Claims for shortages in the amount of Products shipped by Patheon will be dealt with by reasonable agreement of the parties.

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.

  • Weather User understands and agrees that during the term of this agreement, User will strictly adhere to the Weather Protocols set forth in the Grand Park Emergency Management Plan. The Grand Park Emergency Management Plan is made available on the Grand Park website or by request a copy may be provided by the Commission. In the event of inclement weather, the Commission will retain final determination as to the ability of the facility to support the Event. a. If the facility is unable to support the event due to an "Act of God" the Commission will not provide a refund or credit to the User. User may obtain event insurance through a vendor of their choosing to cover the "Act of God" scenario. b. If the facility is deemed unable to support the event by the Commission, the Commission will work with the User to reschedule such activity as was affected by the facility closure. In such case that the activity may not be rescheduled, Commission will credit the User for such activity as was affected by the closure and allow the credit to be utilized toward a future event. c. If the facility is deemed unable to support the event by the User, the Commission will work with the User to reschedule such activity as was affected within the general time constraints of the User's Event. In such case that the activity may not be rescheduled, Commission will not credit the User.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.

  • Inclement Weather 24.1 This Inclement Weather clause sets out the full rights, obligations and entitlements of the parties and establishes the conditions under which payment for periods of inclement weather shall be made. 24.2 This Inclement Weather clause is to be read and observed in lieu of the provisions of the award and VBIA. 24.3 Definition – inclement weather Inclement weather shall mean the existence of rain or abnormal climatic conditions (whether they be those of hail, snow, cold, high wind, severe dust storm, extreme high temperature or the like or any combination thereof) by virtue of which it is either not reasonable or not safe for employees exposed thereto to continue working whilst the same prevail.

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