Third Party Interfaces Clause Samples

Third Party Interfaces. Third-party interfaces and associated dates of supply for the Work will be per the EPC Agreement. The following sections address the main Project third-party interfaces: 22.1 FEED GAS SUPPLY INTERFACE WITH RIO BRAVO PIPELINE Contractor shall perform the following:  Exchange of engineering information necessary to define the operating and design conditions for both the Facility and the Rio Bravo Pipeline Company LLC custody transfer battery limit metering station;  Site preparation of the area designated for the Rio Bravo Pipeline Company LLC custody transfer battery limit metering station to the agreed surface elevation, including any required cut, fill and grading of the battery limit site;  Erect temporary and permanent fencing (and gates) around the area allocated for construction of the Rio Bravo Pipeline custody transfer battery limit metering station;  Exchange of engineering information necessary to define the precise locations and details for the following connections between Rio Bravo Pipeline Company LLC and the Project: § Piping (assumed at fence-line perimeter), and § Electrical, instrument and telecommunications cabling, coiled for installation in the local equipment room;  Mount Rio Bravo Pipeline cabinets in the CCB, and connect to ABB-provided operator panels in the Central Control Room; and  Coordinate construction activities with Rio Bravo Pipeline Company LLC to minimize interference between each other’s activities. All other works within the Rio Bravo Pipeline Company LLC custody transfer battery limit metering station shall be performed by Rio Bravo Pipeline Company LLC. 22.2 FRESH WATER SUPPLY INTERFACE WITH BND It will be Owner’s responsibility to arrange with the local utility provider BND for installation of a fresh water pipeline from the local municipal supply to provide fresh water for construction and operation of the Facility. [***]. Contractor shall perform the following:  Exchange of engineering information necessary with the BND, or its contractor responsible for design, construction, commissioning, and start-up of the new fresh water supply main to fully define the operating and design parameters, and precise locations and details for connection to the new line; and  Tie-in to the new line when available in accordance with the agreement reached between the Owner and the BND, and commission and operate the interconnection in accordance with procedure agreed with the water supply company. [***].

Third Party Interfaces. 5.5.1 NAVITAIRE will supply and support defined interfaces to third party systems utilized by Customer only if listed in this Section. 5.5.2 Unless third party software is incorporated into the Hosted Services System and indicated specifically in the specifications included in this Exhibit, neither NAVITAIRE nor such third party shall be liable for the performance or failure to perform of the other in respect to Service Level Targets. 5.5.3 In the event that a Travel Commerce or Content Provider connection causes severe performance issues or downtime to the Hosted Reservation Services System, NAVITAIRE reserves the right to temporarily disable the offending connection. Customer will be notified if such actions become necessary. NAVITAIRE will reestablish the connection once the supplier has resolved the issue. The following pages itemize the basic and optional products and features as of the Effective Date of this Agreement. Depending on the terms of this Agreement, as defined in this Exhibit A, Section 2 Scope of Services, not all optional products and features are included in this Agreement. This functionality list may be modified or expanded in the future based upon new releases, provided that no material functionality will be eliminated unless mutually agreed with Customer and NAVITAIRE. Hosted Services Agreement Customer and NAVITAIRE. • Graphical reservations screens. • Fee entry and payment collection. • On-demand itinerary print capability. • Auto-queue capability. • Role-based user security.

Third Party Interfaces. 5.6.1 NAVITAIRE will supply and support defined interfaces to third party system utilized by the Customer only if listed in this Section or as mutually agreed in a statement of work including any additional charges that may apply. 5.6.2 Unless third party software is incorporated into the Hosted Services System and indicated specifically in the specifications included in this Exhibit or in a statement of work, neither NAVITAIRE nor such third party shall be liable for the performance or failure to perform of the other.

Third Party Interfaces. ‌ The delivery, installation, and integrations of interfaces may be an iterative series of activities depending upon access to third-party systems. If proposed, interfaces will be installed and configured in accordance with the schedule. Connectivity will be established between CommandCentral systems and the external and/or third- parties to which they will interface. Motorola will configure CommandCentral systems to support each contracted interface. The Customer is responsible for engaging third-party vendors if and as required to facilitate connectivity and testing of the interface(s). • Develop interface(s) in accordance with the Solution Description. • Establish connectivity to external and third-party systems. • Configure interface(s) to support the functionality described in the Solution Description. • Perform functional validation to confirm each interface can transmit and or receive data in accordance with the Interface Feature Description (IFD). • Act as liaison between Motorola and third-party vendors or systems as required to establish connectivity with Digital Evidence Management. • Provide personnel proficient with and authorized to make changes to the network and third-party systems to support Motorola’s interface installation efforts. • Provide network connectivity between Digital Evidence Management and the third-party systems. • Provide requested information on API, SDKs, data schema, and any internal and third-party documents necessary to establish interfaces with all local and remote systems and facilities within 10 days of the Interface Engagement Meeting. • Adhere to the requirements presented in the IFD. Contracted Interface(s). Connectivity is established between CommandCentral systems and the external and/or third-parties using said interface. Unknown circumstances, requirements, and anomalies at the time of initial design can present difficulties in interfacing CommandCentral Vault to some third-party applications. These difficulties could result in a poorly performing or even a non-functional interface. At such time that Motorola is provided with information and access to systems, we will be able to mitigate these difficulties. If Motorola mitigation requires additional third-party integration, application upgrades, API upgrades, and/or additional software licenses those costs will need to be addressed through the change provision of the contract.

Third Party Interfaces. Third-party interfaces and associated dates of supply for the Work will be per the EPC Agreement. The following sections address the main Project third-party interfaces: 22.1 NOT USED 22.2 NOT USED 22.3 NOT USED 22.4 NOT USED 22.5 NOT USED 22.6 NOT USED 22.7 NOT USED 22.8 BROWNSVILLE NAVIGATION DISTRICT TARRIF Contractor shall familiarize itself with the Port of Brownsville Tariff No. 6 issued on December 6, 2016 and effective as of March 1, 2017 (as amended) and the authorized rates, rules and regulations governing the use of the BSC. Contractor shall include in its scope the cost of all wharfage, port, harbor and other charges incurred through Contractor and its Subcontractors’ and Sub-subcontractor’s use of the POB facilities to access the Site during construction, Commissioning, start-up and testing of the Facility.

Third Party Interfaces. (a) All interfaces with third party sources will be subject to a separate specification agreement, which may include interface fees and ongoing support and maintenance costs to You. Interface development and testing will commence upon a formal review of this interface specification document with You. Once the interface has been developed, tested and reconciled to the satisfaction of You and Us, it will be deemed ready to go live in production. Interface development is normally done remotely from Our facilities. However, development of certain interfaces may require travel to Your site. These site visits will be done only when deemed necessary by You and Us. (b) For each specified interface, We are responsible for: (1) Providing a detailed specification document that states both message format and communication methodology requirements; (2) Reviewing the specification document with the interface vendor; (3) Creation of a “Technical Design Document (TDD),” outlining the business and technical decisions agreed upon by You and Us regarding the interface as a result of the above analyses; and (4) Validation of the data transmitted from the source system to Quanum, including unit testing of interface. (c) You or Your source system vendor are responsible for establishing data feeds from all source systems; and any fees from source system vendors to establish or modify such feeds. We reserve the right to re-price an interface when the detailed analysis uncovers features outside the scope of the general product capabilities. Rework due to deviations, modifications, and/or additional features after the interface specification has been approved by You are subject to an additional charge.

Third Party Interfaces. Licensee and Licensor mutually agree that the total number of Licensor developed data exchange interfaces or interfaces to third party systems to be provided by Licensor without additional cost to Licensee is limited to ten (10) separate interfaces per Managed Health Plan and/or Health Plan for which Licensee provides information services through a service center arrangement. Licensee may develop an unlimited number of interfaces to third party systems free of any charge by Licensor and such Licensee-developed interfaces shall be the property of Licensee. Subsequent to the execution of this Agreement, utilization of such interfaces by Licensor developed at the expense of Licensee or required by contract of any Managed Health Plan or Licensee serviced Health Plan shall be with the express permission of Licensee where such use shall be made by Health Plans not managed or serviced by Licensee. Licensee and Licensor shall mutually agree upon any compensation to be paid Licensee for utilization of such custom interfaces by third parties.

Third Party Interfaces. The Software may include the ability to electronically interface directly with one or more third party products or services. Customer understands and agrees that, THE MEDICAL MANAGER interface software is part of the Software, but (i) such third party products and services are not part of the Software, (ii) Licensor makes no warranties or representations of any kind with respect to such third party products and services, and (iii) Customer assumes all risk of loss arising from the use of such third party products. The license to use any Optional Module which is a third party interface shall immediately terminate without further notice or obligation of Licensor upon termination of Customer's or Licensor's agreement with such third party. 6

Third Party Interfaces. 5.6.1 NAVITAIRE will only supply and support defined interfaces to third party systems utilized by the Customer if listed in this Section.