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. The Licensee shall manage and maintain connectivity between its Telecommunications services and its Customers, and provide necessary hardware to provide access to the Fiber System for Licensee’s Customers.
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. 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 (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.
5.2 For Maintenance and Repair, the CMIP transactions referred to as Electronic Bonding - Trouble Administration (EB-TA) will be used. AT&T and U S WEST will use an X.25 transport nexxxxx which is the currently defined standard.
5.3 For Billing, AT&T 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. The Contractor’s design includes all system interfaces, which are required to provide the Works. The Employer provides the relevant information defining the system interfaces. The
System Interfaces. 2.01 The system must be able to import data from other databases, as well as export data to other databases. E
2.02 The system must have the ability to interface with Los Angeles County's eHR System, the Advantage 3.8 Human Resources Suite, developed by CGI, Inc. E
2.03 The system must have the ability to interface, in real time, with other County applications developed by the County's approved vendor CGI using common data base links or XML/Text‐delimited export‐import functions. E
2.04 The system must have the ability to interface with the Countywide electronic web‐based timesheet (TIMEI) to pre‐populate user‐defined time and leave data each pay period. E
2.05 The system must include a built‐in export feature for extracting data in standard formats (e.g. Excel, comma‐delimited text, etc.) for use in importing information to a Countywide Human Resources Suite. E
2.06 The system must include a built‐in import feature for uploading employee information from a Countywide Human Resources Suite, when new employees are added, when changes occur to existing employee records (e.g., promotion, lateral transfer), or when existing employees terminate from the Department/County. E
2.07 The system must be able to integrate with e‐timecards or other time and attendance collection devices ‐ front and back end, and on‐line. E
2.08 The system must provide for the use of multiple payroll labor activity codes to apply consecutively for duties scheduled for, and worked during, the assigned shift (e.g., alternative staff shifts, regular shift and special events, specialized assignments) for labor based on a 24‐hour clock. E
2.09 The system must provide support for Customer‐defined labor activity coding (unlimited) for work scheduled and performed. E
2.10 The system must provide an outbound interface that is able to identify and tag all hours and minutes of a shift with date and time. E
2.11 The system must allow for electronic signatures. E
System Interfaces. Contractor shall:
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. For the avoidance of doubt, the Concessionaire shall deliver System Interfaces in the same manner it delivers the Communications System (and Communications System Components) and System Interfaces shall be in Source Code form or such other form preferred by programmers of reasonable skill in the applicable subject matter area(s) for purposes of using, maintaining, and modifying such System Interfaces. The Concessionaire acknowledges the importance, for example, of the IMS-DMP Interface and shall provide additional assistance and Documentation concerning the IMS-DMP Interface as the MTA reasonably requests.
