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

Related to Forward and Backward Compatibility

  • Year 2000 Compatibility Take all action necessary to assure that its computer based systems are able to operate and effectively process data including dates on and after January 1, 2000, and, at the reasonable request of the Administrative Agent or the Required Lenders, provide evidence to the Lenders of such year 2000 compatibility.

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.

  • Outputs Analogue and digital outputs of protected content are allowed if they meet the requirements in this section and if they are not forbidden elsewhere in this Agreement..

  • Uptime bookinglab shall ensure that the Booking Service will be available, excluding Downtime caused by Scheduled Maintenance, Emergency Maintenance or Force Majeure event, 99.5% of the time in any one calendar month (first day to last day) (the “Service Level”). The Service Level will not apply (and therefore no Service Credits will be applicable) to the extent that any Service Level Failure is caused by: (a) a Penetration Test conducted by Customer without the prior written approval of bookinglab; or (b) Customer’s failure to comply with specific instructions provided by bookinglab; or (c) a failure of the Customer to comply with any Customer responsibility or obligation detailed in a Statement of Work, Order Form or the Master Subscription Agreement; or (d) Customer’s failure to adhere to JRNI’s or bookinglab’s best practice guidelines for the use of the API.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Bandwidth the amount of data (quantified as “Mbps” or “Gbps”) made available to Customer as specified in a Service Order.

  • System for Award Management (XXX) Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a XXX.xxx proof of registration and Commercial and Government Entity (CAGE) number. Grantee will continue to maintain an active XXX registration with current information at all times during which it has an active award under this Agreement.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

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

  • Metrics Institutional Metrics System-Wide Metrics

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