1. Required Scheduling Application Capabilities/Features a) Ability to control the registration type for appointments, i.e. through Teams, Zoom, etc. b) Ability to have connected workflows to appointments for notifications and additional communications. c) Ability to have custom & automated communication via email or text for both the user or the person requesting the appointment. d) Ability to integrate with CRM platforms to provide data from the application to the CRM. e) Ability to schedule a group meeting for an appointment. f) Application allows a user to collect custom information from the person requesting the appointment. g) Application must allow for University CAS (Central Authentication Service) Sign In / Two Factor Authentication. h) Application must be able to read an end user’s outlook calendar for scheduling. i) Application must be Ad Free. j) Application must be ADA (Americans with Disabilities Act) compliant [WCAG 2.1AA]. k) Application provides multiple methods, such as page callouts or full page registration pages for scheduling. l) Data collected by the application must be stored and secured in accordance with USC Information Security Policies. m) Ability to establish groups and teams. n) Intuitive Scheduling Interface for the person requesting the appointment. o) Must allow for scheduling preferences such as round robin or availability within a team. p) Role Based Enumeration - Application must allow for users to be granted specific permissions to the different areas of the application. q) The application must allow for custom schedules based on availability by user or a team. r) The application must allow for separate college/department admins since campus wide license is sought after. 2. The Contractor must ensure the following: a) The solution must be able to encrypt all web access (HTTPS). b) The solution should allow users to have multiple roles without requiring multiple login accounts. c) The number of users is unknown and will vary. d) The solution should be cloud based. e) The solution should integrate with current University authentication services and protocols. f) The solution should integrate with university institutional information for user account and profile provisioning and de-provisioning (create, update, and delete operations). g) The solution should integrate with existing University services to manage groups, roles, and permissions. h) The solution’s access control model should be flexible and extensible by the University as required to meet business needs. i) The solution should allow configuration of user session controls that meet University security and privacy needs including dual authentication. j) The solution’s web interface should work with Chrome, Firefox, Safari, Edge browsers. k) The solution should address University standards for ADA. 3. Preferred Scheduling Application Capabilities/Features a) Application should allow for the creation of unique appointment types within a team or with a user. b) Application should be mobile friendly. c) Application should allow for departmental branding. d) Contractor’s Technical Support of the application should be available during business hours and outside of business hours as needed. e) Application should have Embed Calendar into Blackboard Content Site. f) Application should generate reports on fulfilled/non-fulfilled appointments for users and teams. g) Presentation of available appointments should be easy to navigate to schedule in the application. h) Application should have seamless ability for requester of appointments to cancel/reschedule appointments. i) The application should have the ability to potentially embed schedules for departments into OU Campus (the University’s Content Management System) Website.
