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.
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.
Commodity Compliance and Compatibility It is the Contractor’s responsibility to ensure that the Commodities supplied are compliant with the Contract requirements, specifications, terms, and conditions. Additionally, the Contractor shall ensure that all Commodities ordered by the Customer are fully compatible with each other and with any associated pre-existing Commodity possessed by the Customer and disclosed to the Contractor by the Customer. The Contractor’s acceptance of the Customer’s order shall indicate that the Contractor agrees to deliver a Commodity that is fully compliant and compatible with the Customer’s order requirements, specifications, terms, and conditions. In the event any ordered Base Equipment, OEM and Non-OEM Option(s), Part(s), Accessory(ies), and Implement(s); and their respective features, equipment, and components are found by the Customer to be missing, incorrect, defective, damaged, non- compatible, or non-compliant, the Contractor shall, at the Customer’s discretion, be required to complete one of the following: • Install or repair the Base Equipment, OEM and Non-OEM Option(s), Part(s), Accessory(ies), and Implement(s), and their respective features, equipment, and components; • Replace the Base Equipment, OEM and Non-OEM Option(s), Part(s), Accessory(ies), and Implement(s); and their respective features, equipment, and components; • Refund the purchase price of the Base Equipment, OEM and Non-OEM Option(s), Part(s), Accessory(ies), and Implement(s); and their respective features, equipment, and components to the Customer. Any changes necessary after the delivery of the Customer’s order that are required to bring a Commodity into compliance or compatibility due to an incorrect order fulfillment by the Contractor shall be accomplished at the Contractor’s expense.
Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.
Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.
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.
Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.
Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).
Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.
