Interoperability Testing Clause Samples

The Interoperability Testing clause establishes requirements for verifying that different systems, products, or software components can work together effectively. Typically, this clause outlines the procedures, standards, and responsibilities for conducting tests to ensure compatibility between the parties' respective technologies, such as specifying test environments, timelines, and criteria for success. Its core practical function is to minimize integration issues and ensure seamless operation between interconnected systems, thereby reducing the risk of technical failures or incompatibilities after deployment.
POPULAR SAMPLE Copied 1 times
Interoperability Testing. 5.1 If requested by the Customer, KCOM will use its reasonable endeavours to provide information or carry out testing on interoperability issues affecting equipment or related services provided to End Users by the Customer. KCOM reserves the right to make additional charges on a time and materials basis for providing such assistance.
View SourceView Similar (3)
Interoperability Testing. 9.1 Prior to any sales referral activity between Lucent and Company for any Product, such Product must have completed successful interoperability testing at Lucent's Wireless Innovation Lab(SM) testing facility and satisfy all requirements of interoperability. Except as the Parties may otherwise agree in writing, such testing shall be performed pursuant to a separate written agreement setting forth Lucent's standard terms and conditions and charges for such testing, as they exist from time to time. When a Product previously successfully tested is modified and/or changed in any way that might render the previous test results invalid or uncertain, Company must inform Lucent and such Product must repeat interoperability testing to validate that the modifications and/or changes do not compromise interoperability status. 9.2 If Lucent Wireless Network Equipment undergoes modification and/or change, Lucent will notify Company. Each impacted Product must repeat interoperability testing, if Lucent determines that the modifications and/or changes could compromise interoperability status of such Product.
View SourceView Similar (3)
Interoperability Testing. It is a condition precedent of this Agreement that the Parties shall have conducted Interoperability Testing of the Operator’s Equipment, if it is required. For the avoidance of doubt, the conduct of Interoperability Testing does not oblige BT to provide Services to the Operator, and BT reserves its rights to terminate this Agreement immediately without penalty if the Operator’s Equipment is not Compatible, in BT’s reasonable opinion. The process for Interoperability Testing is set out in the Product Handbook. The Charge for Interoperability Testing is set out in Carrier Price List. The Parties will ensure that the required resource is available during the Interoperability Testing Slot to carry out Interoperability Testing. If through no fault of a Party, Interoperability Testing of the Operator Equipment is not carried out during the Interoperability Testing Slot, that Party may raise an Abortive Test Charge as set out in the Carrier Price List for each day or part thereof, if that Party is unable to carry out Interoperability Testing during the Interoperability Testing Slot.
View SourceView Similar (2)
Interoperability Testing. Novatel Wireless will provide, *** the interoperability Testing services described in Exhibit H hereto in a manner consistent with the requirements of Exhibit B, except for Sections 3 and 4 thereof. The Statements of Work developed by the parties and governed by Exhibit B will be based on Exhibit H.
View SourceView Similar (2)
Interoperability Testing. 5.1. Upon completion of the steps set out in Paragraph 4 above, WhatsApp and the Partner shall commence service establishment discussions for Interoperability and Parties will cooperate in testing (“Interoperability Testing”) of the implementation in accordance with the Developer Documentation to determine (a) if Interoperability is functioning properly (i.e., that Partner is able to successfully send and receive Messages between its Partner Users and WhatsApp Users) and (b) that Partner has fulfilled all of its obligations in this Annex 1. 5.2. If WhatsApp or Partner identifies any issues with the Partner’s implementation during the Interoperability Testing, WhatsApp may, acting reasonably, restrict the Partner activation status and work with Partner to resolve any issues before permitting a public launch of the Interoperable Messaging Services. In the event that the Partner, using all reasonable endeavours, is unable to resolve the issues identified by WhatsApp and/or the Interoperability Testing fails, WhatsApp may (in its discretion) continue to extend the testing period until Partner has resolved the issue and is able to demonstrate a working test model, provided that Partner is able to demonstrate continued progress towards resolution of the issue during that extension period. 5.3. If the Interoperability Testing is successful, WhatsApp will notify the Partner and inform the Partner of an upcoming public launch date (in accordance with an agreed launch and rollout timeline) (“Acceptance”).
View Source
Interoperability Testing. (A) Level 3 and Customer shall jointly conduct interoperability testing of the (3)VoIP EnhancedSM Local Service with the Customer VoIP Application(s) to ensure Customer's call flows can be supported by the ▇▇▇▇▇ ▇ ▇▇▇▇▇▇▇. ▇▇▇▇▇ ▇ and Customer shall mutually agree in writing on entrance and exit requirements for such interoperability testing, and Customer will be required to successfully complete interoperability testing for each Customer VoIP Application prior to Level 3's certification of any such Customer VoIP Application as Network Ready. (B) Customer is required to obtain re-certification through additional interoperability testing prior to implementing a software or call flow upgrade, enhancement or modification to any Customer VoIP Application on the Level 3 network that was previously certified as Network Ready. Level 3 reserves the right to cancel (without liability) any Customer Order(s) for (3)VoIP EnhancedSM Local Service in instances where Customer has implemented a software or call flow upgrade, enhancement or modification without successfully completing additional interoperability testing. During any re-certification process, Customer shall continue to use (3)VoIP EnhancedSM Local Service under the previously certified Customer VoIP Application.
View Source
Interoperability Testing. As part of its support of its OEM and ODM customers and certain other third parties, Intel shall support and coordinate IOT on the Clearwire Communications Network to ensure Qualifying Intel Devices, infrastructure equipment, and services interoperate pursuant to a mutually agreed upon IOT schedule, which IOT schedule the Parties will use good faith efforts to accomplish promptly after execution of THIS DOCUMENT AND ITS CONTENTS CONSTITUTE THE PROPRIETARY AND CONFIDENTIAL INFORMATION OF CLEARWIRE COMMUNICATIONS LLC AND INTEL CORP. – DO NOT DISCLOSE TO THIRD PARTIES this Agreement. Clearwire Communications shall coordinate with Intel to facilitate any required IOT with the OEMs and ODMs that manufacture Qualifying [*****] that are intended to operate on the Clearwire Communications Network, and upon Intel’s reasonable request, Clearwire Communications shall make its personnel reasonably available to discuss the Clearwire Communications Network with OEMs that manufacture Qualifying [*****] in an effort to reasonably assist Intel in meeting its Embedding Rate commitments.
View Source
Interoperability Testing. Licensor shall perform such tests and provide Cisco with the test results in accordance with the interoperability testing guidelines addressed in the Interoperability Testing Agreement between the parties dated September 9, 2013 (the “Interoperability Testing Agreement”).
View Source
Interoperability Testing. Motorola agrees to have every revision of the Product delivered to Telular interoperability tested for standard CDG stage 2 on a minimum of Motorola and Lucent infrastructure. Completed results from these tests and any CDG stage 2 interoperability tests with other infrastructure providers which Motorola may undertake in its sole discretion will be forwarded to Telular. This Agreement is initially based on Rev 2.3 including analog fax.
View Source

Related to Interoperability Testing

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

  • Stability Testing Patheon will conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within [***], after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications and cGMPs. Patheon will give Client all stability test data and results at Client’s request.

  • ODUF Testing 6.6.1 Upon request from TWTC, AT&T shall send ODUF test files to TWTC. The Parties agree to review and discuss the ODUF file content and/or format. For testing of usage results, AT&T shall request that TWTC set up a production (live) file. The live test may consist of TWTC’s employees making test calls for the types of services TWTC requests on ODUF. These test calls are logged by TWTC, and the logs are provided to AT&T. These logs will be used to verify the files. Testing will be completed within thirty (30) days from the date on which the initial test file was sent.

  • Performance Testing (a) All performance tests of the Project, including any Initial Performance Test required in Section 2 of Appendix VIII, will be performed in accordance with the test procedures set forth in Appendix VIII (“Performance Test”), including additional procedures and protocols related to Performance Testing as mutually agreed between Buyer and Seller (“Test Procedures”). Seller shall bear all costs and receive all revenues, if applicable, associated with all Performance Tests. (b) After the Initial Delivery Date and during the Delivery Term, Buyer will have the right to conduct a Performance Test (“Buyer Performance Test”) no more than once a calendar year to demonstrate whether the Project is capable of delivering the Distribution Services at the Contract Capacity. Within 30 calendar days following a Buyer Performance Test, Seller will have the right to retest the Project with a Performance Test (“Seller Retest”). For the avoidance of doubt, the results of any Seller Retest will supersede the results of the preceding Buyer Performance Test. (i) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is capable of delivering Distribution Services at or above ninety-nine percent (99%) of the Initial Contract Capacity, the Contract Capacity will remain the Initial Contract Capacity; (ii) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is capable of delivering Distribution Services at more than or equal to eighty-five (85%) of the Initial Contract Capacity, but less than ninety-nine percent (99%) of the Initial Contract Capacity (“Testing Band”), the Contract Capacity will be automatically adjusted (upwards or downwards) to the capacity commensurate with the amount of Distribution Services the Project delivered during the Performance Test within the Testing Band. (iii) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is not capable of delivering Distribution Services of at least eighty-five percent (85%) of the Initial Contract Capacity, an Event of Default shall occur in accordance with Section 7.1(a)(viii).

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.