Data and Interface Sample Clauses

Data and Interface. AR-23 The Contractor shall be fully capable of accepting and implementing enrollment and other data files via a secure file transfer protocol (SFTP) on or before October 30, 2022. AR-24 The Contractor shall not use, or otherwise disseminate, sell, copy or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract. AR-25 Enrollment File Transfers from the Department The Contractor shall maintain an information system capable of electronically receiving and updating Participant enrollment information (e.g., eligibility, name, address, coverage code). The Contractor shall accurately convert and load the Department’s enrollment files. The Contractor shall also:
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Data and Interface. 24 Service Provider shall be fully capable of accepting and implementing eligibility and other data files via FTP on or before October 30, 2014. 25 The Vendor shall not use, or otherwise disseminate, sell, copy or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract.
Sample 1Sample 2
Data and Interface. AR-12 In the performance of the post payment claims audit, the Contractor shall use the data from the Department's HIMIS system as the official record. The Contractor shall be provided access to the Department's HIMIS system for retrieval of claims data. AR-13 Contractor must exchange weekly and monthly data and file transfers between the Contractor and third parties and/or the Department using asecure method, format, and frequency required by the Department. AR-14 The Contractor or any of its Subcontractors shall notify the Department immediately in the event of lost data or security breach. Notice to the Department may be made by phone or email. AR-15 Contractor shall be responsible for recreating or retrieving such lost data ina manner and schedule determined by the Department. AR-16 The Contractor is required to ensure confidential information is completely protected from unauthorized access. AR-17 The Contractor shall ensure that their equipment will not compromise the Department's data.
Sample 1
Data and Interface. 19. Contractor shall be fully capable of accepting and implementing eligibility and other data files via FTP on or before October 1, 2015.
Sample 1
Data and Interface. The Contractor shall not use, or otherwise disseminate, sell, copy, or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract.
Sample 1
Data and Interface. The Contractor shall be fully capable of accepting and implementing enrollment and other data files via secure portal on or before December 1, 2022 or another date mutually agreed upon between the Contractor and the Department. The Contractor shall not use, or otherwise disseminate, sell, copy or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract. Enrollment File Transfers from the Department The Contractor shall maintain an information system capable of electronically receiving and updating Participant enrollment information (e.g., eligibility, name, address, coverage code). The Contractor shall accurately convert and load the Department’s enrollment files. The Contractor shall also:
Sample 1
Data and Interface. Service Provider shall be fully capable of accepting and implementing eligibility and other data files via FTP on or before October 30, 2014. The Vendor shall not use, or otherwise disseminate, sell, copy or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract.
Sample 1
AutoNDA by SimpleDocs
Data and Interface. 28. Contractor shall be fully capable of accepting and implementing eligibility and other data files via a secure file transfer protocol (sFTP) on or before October 30, 2017.
Sample 1

Related to Data and Interface

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

  • Data Access Access to Contract and State Data The Contractor shall provide to the Client Agency access to any data, as defined in Conn. Gen Stat. Sec. 4e-1, concerning the Contract and the Client Agency that are in the possession or control of the Contractor upon demand and shall provide the data to the Client Agency in a format prescribed by the Client Agency and the State Auditors of Public Accounts at no additional cost.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Network Interface Device 2.7.1 The NID is defined as any means of interconnection of the End User’s customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single line termination device or that portion of a multiple line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the End User’s premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the End User each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

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

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • SS7 Network Interconnection 9.7.1 SS7 Network Interconnection is the interconnection of Global Connection local signaling transfer point switches or Global Connection local or tandem switching systems with BellSouth signaling transfer point switches. This interconnection provides connectivity that enables the exchange of SS7 messages among BellSouth switching systems and databases, Global Connection local or tandem switching systems, and other third-party switching systems directly connected to the XxxxXxxxx XX0 network.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!