System Interfaces Sample Clauses

System Interfaces. The following is a list of interfaces that will be a part of the BSP Services: > Seamless login to the Customer Console > Delivery of ACH file from FIS to Client preferred financial institution for ACH origination > Delivery of statement data file > Dedicated line for file transmissions from Client to FIS and FIS to Client’s secure FTP account. > Delivery of enrollment data/changes > Debit Card interface to FIS partner, Chase > Real-time Post Back Functionality Paymentech consisting of an hourly delivery of remittance information (posting) from FIS to Client (PID # 224877) Page 4 of 9

System Interfaces. SMTC shall be responsible for the expenses related ----------------- to the interface between Cobalt's MRP system and SMTC's systems, including all data transmission lines mutually agreed upon and any related costs for wiring required at the SMTC manufacturing facility. SMTC shall not be responsible for the cost of any Cobalt specific hardware, such as servers, computers and printers.

System Interfaces. 5.1 For Pre-order, Order and Provisioning, an exchange protocol, such as 'that based upon a subset of Common Management Interface Protocol (CMIP) transactions referred to as Electronic Communications-Lite (EC-Lite), will be used to transport Electronic Data Interchange (ED[) formatted content. Pac-West and U S WEST will use a TCP/IP based transport network for the exchange of EDI transactions. Pac-West and U S WEST will translate ordering and provisioning requests from the Ordering and Billing Forum (OBF) forms into EDI transactions using mutually agreed to mappings. The Service Order SubCommittee (SOSC) of the Telecommunications Industry Forum/Electronic Data Interchange (TCIF/EDI) committee interpretations of the 850, 855, 860, 864. 865, 870, and 977 transactions, in accordance with the OBF forms, will be used to convey all the necessary data to connect, modify or disconnect local exchange services. 5.2 For Maintenance and Repair, the CMIP transactions referred to as Electronic Bonding - Trouble Administration (▇▇-▇▇) will be used. Pac-West and U S WEST will use an X.25 transport network which is the currently defined standard. 5.3 For Billing, Pac-West and U S WEST will use EDI 811 and OBF Billing Output Specification (BOS) formats via CONNECT:Direct. Section 13 further defines the conditions when one or the other format will be used.

System Interfaces. Contractor shall: 1. Develop and maintain system interfaces in order to produce data feeds that can be consumed by the County’s CAPS+ Human Resources/Payroll system and other County systems. These data feeds consist of ongoing data updates to the Learning Management Module and Performance Management Module. These data feeds may have different frequencies, including hourly, daily, weekly, monthly, and/or as needed. 2. Develop and maintain the mechanism to update the ITMS with data from the CAPS+ Human Resources/Payroll system and other County systems. These data updates include the initial data load from CAPS+, automatic creation or termination of employee records in ITMS as employee records are added or inactivated in CAPS+. These data feeds may have different frequencies, including hourly, daily, weekly, monthly, and/or as needed.

System Interfaces. For Pre-order, Order and Provisioning, an exchange protocol, such as that based upon a subset of Common Management Interface Protocol (CMIP) transactions referred to as Electronic Communications-Lite (EC- Lite), will be used to transport Electronic Data Interchange (EDI) formatted content. AT&T and U S WEST will use a TCP/IP based transport network for the exchange of EDI transactions. AT&T and U S WEST will translate ordering and provisioning requests from the Ordering and Billing Forum (OBF) forms into EDI transactions using mutually agreed to mappings. The Service Order SubCommittee (SOSC) of the Telecommunications Industry Forum/Electronic Data Interchange (TCIF/EDI) committee interpretations of the 850, 855, 860, 864, 865, 870, and 977 transactions, in accordance with the OBF forms, will be used to convey all the necessary data to connect, modify or disconnect local exchange services.

System Interfaces. Contractor shall:

System Interfaces. Requirements Cannot be Met NONE Deviated Requirements NONE Requirements Met 2.01, 2.02, 2.03, 2.04, 2.05, 2.06, 2.07, 2.08, 2.09, 2.10, 2.11 Please see Section C.2 of this response for more information on TeleStaff’s interfacing solutions, including the export and import of pertinent County information.

System Interfaces. Task Description: Tiburon Responsibilities: a. Install and test interfaces as defined in Attachment C. a. Assume responsibility for any hardware, software licenses, modifications, or additions to any systems not supplied, installed, tested, or licensed by Tiburon. b. Act as the liaison between the agencies and third-party vendors required to support the interfaces. c. Provide Tiburon with the physical connections for each interface, to allow Tiburon to test the functionality of each interface in an appropriate environment. d. If the interfaces are currently in operation, it is the Client's responsibility to disconnect each of the interfaces from the operational environment to facilitate interface testing. Testing may be required more than once during the project to ensure operational readiness. This task is complete when all interfaces have been installed. Delays or unavailability of external systems and/or interfaces not made available to Tiburon shall not delay completion of this task. In those cases where testing is delayed through no fault of either the Client or Tiburon, the Client shall authorize the testing of the interface function at a later date. Such rescheduling of interface testing shall not delay the scheduled go-live or any subsequent tasks. Task completion will be confirmed by the Client’s signature on the task completion letter provided by ▇▇▇▇▇▇▇. .

System Interfaces. If PWL permits Client to request testing or access reports via an interface between PWL and Client's systems, Client is solely responsible for the implementation of, maintenance of, and security of, such interface, as well as the protection of protected health information (as defined in section 10) during transmissions utilizing such interface.