Forward and Backward Compatibility Sample Clauses

Forward and Backward Compatibility. Except as set forth in an Authorization Letter, Supplier represents and warrants that, for a period of **** following the commercial release of any new supported Wireless Device (such timeframe with respect to each release, the “Rolling Window”), new versions of Software other than Custom Software with respect to which Verizon has waived in writing Supplier’s obligations under this Section 15.8 (Verizon acknowledges that execution of an SOW that expressly excludes support for Custom Software shall be deemed such waiver and Custom Software may require additional fees to maintain compatibility as provided in an applicable Authorization Letter), shall be forward and backward compatible, contain materially similar functionality to and be substantially compatible with such Wireless Device and their operating environment(s). If set forth in an Authorization Letter, new versions of Software, that do not otherwise compromise or break the functionality of the Software on Wireless Devices released prior to the Rolling Window, are not required to incorporate all new incremental feature enhancements contained in such new Software release. The Rolling Window shall apply to any Wireless Device commercially released after **** and supported by the Platform. In the event Supplier deploys a server side Software change that causes Supplier to breach the above warranty in this Section 15.8 with respect to Wireless Device client Software, Supplier shall upgrade the Software used on the affected Wireless Device at no additional fee, provided Verizon is current on its Maintenance payments. 15.9
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Forward and Backward Compatibility. Motricity represents and warrants that where it has agreed to provide new versions of Software on an on-going basis such new versions shall be forward (i.e. that as new data formats are deployed, updates will modify or patch Software for compatibility with such new data formats) and backward (i.e., that as Software is modified and Matter Number AGR-002829-2010 updated, it will continue to be compatible with the data formats, environments and systems with which it previously was used) compatible and shall contain materially similar functionality to and will be substantially compatible with the preceding version of the Software and its operating environment.”
Sample 1

Related to Forward and Backward Compatibility

  • Year 2000 Compatibility Borrower shall take all action necessary to assure that Borrower's computer based systems are able to operate and effectively process data including dates on and after January 1, 2000. At the request of Bank, Borrower shall provide Bank assurance acceptable to Bank of Borrower's Year 2000 compatibility.

  • Compatibility The Spacecraft Bus shall be compatible with standard GPS interfaces as defined in [**Redacted**].

  • WHEXXXX xs xxxx of a plan of reorganization, RESTART PARTNERS, L.P., a Delaware Limited Partnership ("Restart"), may acquire an ownership interest in Elsinore Corporation ("Elsinore") or the Four Queens, Inc. ("FQI");

  • Year 2000 The Borrower has made a full and complete assessment of the Year 2000 Issues and has a realistic and achievable program for remediating the Year 2000 Issues on a timely basis (the "Year 2000 Program"). Based on such assessment and on the Year 2000 Program the Borrower does not reasonably anticipate that Year 2000 Issues will have a Material Adverse Effect.

  • Speed (a) The Contract Price shall not be affected or changed by reason of the trial speed (as determined according to the SPECIFICATIONS being less than the guaranteed speed, if such variation is not more than Two-Tenths (2/10) of One (1) knot.

  • Traceability Distributor agrees to maintain access to records allowing Micrus the ability to determine all customers who were shipped specific product lots. Product Identification and traceability requirements are defined in ISO 9001 : 1994 (E) requirement 4.8 as : “...the supplier shall maintain documented procedures for identifying the product from production, delivery and installation.” Traceability in ISO 8402 Vocabulary is defined as : “ability to trace the distribution and location of the product after delivery”.

  • Network 2.7.1 DCH will provide to the Contractor up-to-date changes to the State’s list of excluded Providers, as well as any additional information that will affect the Contractor’s Provider network.

  • Feedback Distributor shall provide Company with prompt written notification of any comments or complaints about the Products that are made by Customers, and of any problems with the Products or their use that Distributor becomes aware of. Such written notification shall be the property of Company, and shall be considered to be part of Company’s Confidential Information.

  • Quality Service Standards/NAV Errors Price Associates and the Fund may, from time to time, agree to certain quality service standards, with respect to the Services hereunder. In the event Price Associates is the party responsible for causing an error in the computation of the net asset value for a Fund or share class of a Fund (“NAV Error”), the actions that are required to be taken as to such NAV Error shall be made in accordance with the Fund’s Net Asset Value Error Correction Policy and Procedures (“NAV Error Policy”) attached hereto as Schedule II.

  • Virus Management Transfer Agent shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within the Transfer Agent environment.

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