Co-Curricular Activity Tracking System

Clemson University is seeking a digital platform to track, assess, and report on student co-curricular activities. The platform should be a Software-as-a-Service (SaaS) solution, accessible via a web-based client and application, and should have features such as student organization management, event management, and student engagement tracking. The platform should also have a user-friendly interface, be customizable, and have a robust set of user tagging and access rights options. The university is looking for a vendor who can provide a comprehensive solution that meets their needs and can be implemented with minimal IT support. Some of the key features required include: • Comprehensive Student Organization, Event Management, and Student Engagement system • Ability to ingest all or selected parts of the dataset • Ability to be implemented with minimal IT support • Ongoing operations should require minimal or no IT support • Support and training provided by the vendor • Company has been serving institutions’ operations equal to or larger than Clemson University for at least four years • Selected demographic & academic data must be imported/synchronized from the campus system at least daily • System must allow for the overall configuration of application processing and workflow on the customer side to be unique to the campus • Customization to enable individual departments to maximize the utilization of the tool • 24/7 customer support • Maintenance and support during the implementation phase • Training for the proposed system will be available from the date of implementation • Periodic large-scale user group events, special ad hoc trainings, etc. • Ability to create a data feed of events to institution websites • Supports automated data set retrieval and import, with appropriate safeguards against record duplication • Provides swift page loading times (less than 3 seconds) to enhance the user experience and reduce the number of users who abandon the site • API option that utilizes industry standards to extend the solution • Ability to schedule maintenance and blackout dates before the start of each semester • System must have a centralized hub with editable components on the homepage and a configurable left-hand menu • Native mobile application available for iOS and Android users • Robust set of user tagging and access rights options to segment communication and customize access to content, forms, events, and groups • Ability to assign a separate user status (e.g., “Suspended Students”) to restrict access • Ability to embed forms into the registration process for review/approval • Ability to require training/event attendance as an automated requirement workflow • Ability to communicate with the organization registration submitter within the platform • Ability to draft and send emails directly within the platform • Single Sign-On Using Clemson issued credentials • Two Factor Authentication (Duo integration required) • Role-based access and permission control, including Read Only, Read/Write access by user or by role • System capability for auditing/audit logs • Ability to track and display the history of information stored in the application • Full encryption of all communications • Secure, encrypted method of transport (e.g., Secure Socket Layer (SSL), VPN, etc.) • Retention of any user activity logs and other system information • Annual review of SOC1 (SSAE16), SOC2 reports for all vendor-hosted solutions • Mechanism to allow CU to receive data files for consumption by the current (or future) CU Data Warehouse and similar systems • Mechanism to review and export security data from the hosted solution • Annual review of the offeror's disaster recovery plan or a SOC2 report • Exit strategy that can be tested annually • Database backup of CU data being recoverable at a CU datacenter • Primary and secondary hosting sites must be located a minimum of 150 straight-line statute miles apart and from Clemson, SC