Technology failures Sample Clauses

Technology failures. The success of e-ScienceTalk will depend in part on the new technologies used to deliver the online content, both the existing elements and the planned new features, such as increased user generated content and interactive online environments. If the wrong technologies are chosen, or advances in web use make these obsolete, there is a risk that the expected growth of the media outputs and the launch of the new products will not be achieved. This risk will be mitigated by using the partners’ expertise in new media and regularly reviewing the channels used. The probability of such failure is low (about 10%), given the expertise and experience available to the project. The impact of such technological failure should also be minimal, since the core communication efforts rely on more established technologies.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Technology failures. In the event the Product experiences significant technical issues that arise out of or relate to the MDTS system, including failure of the MDTS system to deliver testosterone, or another Androgen added to the Field in accordance with this Agreement, in a manner suitable for development or commercialization of a Product in the Field and Territory, inadequate physical or chemical stability of any portion of the MDTS system, issues arising out of any Acrux Penetration Enhancer or any other formulation developed by FemPharm and used in an MDTS system, or other issues that significantly impact the efficacy, toxicity, safety, or ability to obtain approval, then, to the extent that Vivus reasonably concludes that the issue would likely prevent the approval of the Product in the Field and Territory by the FDA or other appropriate regulatory authority or cause the Product to not be commercially viable, Vivus shall have the right, subject to the terms of Section 5.19(b) below, to select for addition to the Field, and development and commercialization in the Territory under this Agreement as an alternate Product, an alternate Androgen (excluding any Androgen (other than a Restricted Androgen) for which FemPharm or its Affiliate has commenced Clinical Trials, or which FemPharm or its Affiliate has licensed to a non-Affiliate third party in a fully arms length transaction, in conformance with Section 2.5(b)) or alternate configuration of the MDTS technology.
Sample 1

Related to Technology failures

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

  • Technology Upgrades Notwithstanding any other provision of this Agreement, Verizon shall have the right to deploy, upgrade, migrate and maintain its network at its discretion. The Parties acknowledge that Verizon, at its election, may deploy fiber throughout its network and that such fiber deployment may inhibit or facilitate PNG’s ability to provide service using certain technologies. Nothing in this Agreement shall limit Verizon's ability to modify its network through the incorporation of new equipment or software or otherwise. PNG shall be solely responsible for the cost and activities associated with accommodating such changes in its own network.

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

  • Technology Discoveries, innovations, Know-How and inventions, whether patentable or not, including computer software, recognized under U.S. law as intellectual creations to which rights of ownership accrue, including, but not limited to, patents, trade secrets, maskworks and copyrights developed under this Agreement.

  • Power Failure Power Failure means the failure of power or other utility service if the failure takes place off the "residence premises". But if the failure results in a loss, from a Peril Insured Against on the "residence premises", we will pay for the loss caused by that peril.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.1.3.1 Definition 4.1.3.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for <<customer_name>> when <<customer_name>> serves end-users with four (4) or more voice-grade (DS-0) equivalents or lines in locations served by BellSouth’s local circuit switches, which are in 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.1.3.3 In the event that <<customer_name>> orders local circuit switching for a single end user account name at a single physical end user location with four (4) or more 2-wire voice-grade loops from a BellSouth central office in an MSA listed above, BellSouth shall charge <<customer_name>> the market based rate in Exhibit C for use of the local circuit switching functionality for the affected facilities. 4.1.3.4 A featureless port is one that has a line port, switching facilities, and an interoffice port. A featured port is a port that includes all features then capable or a number of then capable features specifically requested by <<customer_name>>. Any features that are not currently then capable but are technically feasible through the switch can be requested through the NBR/BFR process. 4.1.3.5 BellSouth will provide to <<customer_name>> customized routing of calls: (i) to a requested directory assistance services platform; (ii) to an operator services platform pursuant to Section 10 of Attachment 2; (iii) for <<customer_name>>’s PIC’ed toll traffic in a two (2) PIC environment to an alternative OS/DA platform designated by <<customer_name>>. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers. 4.1.3.6 Remote Switching Module functionality is included in Switching Capability. The switching capabilities used will be based on the line side features they support. 4.1.3.7 Switching Capability will also be capable of routing local, intraLATA, interLATA, and calls to international customer’s preferred carrier; call features (e.g. call forwarding) and Centrex capabilities. 4.1.3.8 Where required to do so in order to comply with an effective Commission order, BellSouth will provide to <<customer_name>> purchasing local BellSouth switching and reselling BellSouth local exchange service under Attachment 1, selective routing of calls to a requested directory assistance services platform or operator services platform. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers, but obtain a <<customer_name>> branded service.

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