System Interconnection. Introducing a new interconnection changes each system’s technical architecture, and both parties must have a clear understanding of how systems will exchange information in order to properly incorporate changes into current and future network topologies. For this data sharing configuration, there is not a direct system interconnection but rather a sharing of a common Secure File Transfer Protocol (SFTP) server that is the collection point for the data sent by FSA and the data that is extracted by the OIG. The following provides a description of this Extract, Transform, and Load (ETL) process between ODAS and FSA IT systems covered in this agreement. NSLDS/COD/PIN/PEPS OIG Receives Data from NSLDS/COD/PIN/PEPS • Data Description: Defined Data Export of NSLDS/COD/PIN/PEPS data • Protocol used to exchange data: Secure FTP (SFTP) • How often is data transferred: Monthly • Describe the direction of the data flow: OIG will pull data from HPL4/SFTP1 server OIG Processes NSLDS/COD/PIN/PEPS Data • Data Description: NSLDS/COD/PIN/PEPS Extract • Protocol used to exchange data: SFTP • How often is data transferred: Monthly OIG Disposes of the Data • Data Description: NSLDS/COD/PIN/PEPS Extract • Disposal Method: When the information is no longer needed, it will be disposed in accordance with OCIO-15: Handbook for Protection of Unclassified Sensitive Information and applicable Department records schedules. • Notification in the form of an email will be sent to FSA that specified data for the COD and PIN repositories that meet defined retention schedules has been deleted will be forwarded to the designated FSA owner. The referenced data received for the NSLDS and PEPS systems is a fully replace configuration and therefore will not meet this requirement.
System Interconnection. UTILITY shall be responsible, at its expense, for interconnecting the System to UTILITY’s electric distribution facilities. UTILITY will have remote access to System performance data. UTILITY shall own any data collected from the System.
System Interconnection. The Licensee shall use best efforts to provide for the interconnection of one access channel on its residential cable system with one access channel on any or all other adjacent systems upon the written request of the Town. Interconnection of systems or channels may be accomplished by direct cable connection, microwave link, satellite, or other appropriate and economically feasible method. Upon receiving the request of the Town to interconnect a system or channels, the Licensee shall initiate negotiations with the other affected system(s) in order that costs may be shared equally for both construction and operation of the interconnection link. The Town shall rescind its request for interconnection if the Licensee has negotiated in good faith and has failed to obtain an approval from the system or systems of the proposed interconnection, or that the cost of the interconnection would cause an unreasonable or unacceptable increase in subscriber rates, or if the system architectures involved are incompatible for purposes of interconnection. The foregoing is contingent on the willingness of the other Licensee to participate on equitable terms and the foregoing being in accordance with any applicable laws.
System Interconnection. Reference (s) requires “written management authorization, based upon the acceptance of risk to the system, prior to connecting with other systems.” DoD ISs generally satisfy this requirement through compliance with connection management procedures established by the Chairman of the Joint Chiefs of Staff. Separately accredited ISs that communicate directly through tightly coupled mechanisms, such as shared memory or direct code invocation, are not subject to this requirement. In addition, for IA purposes, loosely coupled ISs (e.g., by proxy) communicating via Web services are not considered system interconnections and do not require connection approval, a security memorandum, or written management authorization. Dynamic interaction among accredited software systems that have been designed to interact is not considered a security-relevant event. This includes authorized messaging with non-DoD ISs (e.g., electronic commerce/electronic data interchange transactions with an IS belonging to another department or agency).
System Interconnection. Upon written notice to Pathnet, Incumbent shall have the right to interconnect the System to the Incumbent system developed pursuant to the Fixed Point Microwave Services Agreement, dated September 17, 1997, under the terms and conditions of this Agreement; provided that (i) Incumbent shall pay the costs, which costs shall not apply to the Incumbent Payment Cap, of [***], and (ii) Pathnet shall pay the costs of [***] pursuant to a budget to be agreed upon by the Parties.
System Interconnection a. Means of interconnecting to other facilities:
System Interconnection. DISH will be responsible at its own cost and expense to purchase, deploy and maintain any necessary network and systems connections between the DISH network and systems and the AT&T Mobility network and systems. [***] DISH agrees to utilize AT&T Systems, if applicable, and other systems and interfaces to be reviewed and approved by AT&T Mobility in writing prior to deployment.
