Common use of Interface Control Document Clause in Contracts

Interface Control Document. The Section Developer, at its expense, shall design, install, operate, and maintain the ETCS and interconnections of the ETCS with MDTA's Host. Such design and installation shall be consistent with, and meet all requirements of, the Interface Control Document (the "ICD"). The Section Developer shall collaborate with MDTA and adopt detailed requirements to be set out in the ICD developed by MDTA to ensure the correct processing of each Trip to be sent to MDTA. The ICD shall be based on the current ICD for MDTA's toll systems in the State, and MDTA shall discuss any modifications suggested by the Section Developer to improve the transmission of Trip data for both parties. The ICD applicable to the Section shall be finalized prior to commencement of tolling operations for the Section. The ICD is subject to change with reasonable advance written notice from MDTA. The Section Developer must comply with the new interface requirements set out in any updated ICD at no cost to MDTA. The Section Developer acknowledges that the ICD is intended to be a framework for the interface between a third party and MDTA; it supports many different types of systems with different unique needs, requirements, and contractual obligations; and it is subordinate to, and is not intended to supersede or alter, any of the express provisions of the TSA or the Section P3 Agreement.