Specifications include, but are not limited to: .Complete two‐way data interface with Jenzabar EX Vendors should provide a detailed explanation of the operation of the interface and synchronization of data between their proposed solution and the College’s ERP (Jenzabar EX). The interface should be able to handle round‐trip or bidirectional data integration, meaning that changes made to appropriate data fields in the College’s ERP system (Jenzabar EX) should be reflected in the vendor’s system, and vice versa. The interface should be operable in both a bulk load mode and an incremental change mode. The interface should be able to run autonomously, such as a system scheduled job, and should not require human intervention to operate. The interface should provide reasonable logging and troubleshooting capabilities. i.Describe how the product will integrate with the CCCC Jenzabar ERP environment. ii.Describe the method used for data transfer. iii.What types of changes can be sent from the scheduling software back to SIS and vice versa? iv.Users of the system will enter data in one system and the other system will be updated in real time via Application Program Interface (API) Web Services. v.Full documentation of the API Web Service. vi.Vendor should be prepared to demonstrate the operation of their interface with Jenzabar EX in a test or live environment as reflected in Section 2.1, Proposal Timeline. 2.Compatibility with College internal single sign‐on (SSO) authentication protocol. i.Permit multiple users to enter, approve and make changes at the same time. ii.Provide audit trail to determine date, time, action and user who made the change(s) to all events.
