3. SCOPE OF SERVICES REQUIRED a) Technical Requirements The following requirements are absolute minimums that a vendor and their proposed system must meet. If these requirements are not met, the proposal will be removed from consideration. The vendor must provide a detailed description of how each of these requirements will be met by the proposed system. i) Vendor must be an Ellucian Banner collaborative development partner ii) Integration with Banner SIS iii) Support major browsers, specifically IE, FireFox, Safari, and Chrome iv) Integrate with University’s authentication system, CAS or Shibboleth 4 b) Users • There should be no restrictions on the number of users of the system. • User permissions and accesses should be role based. Role-based permissions govern each user’s rights to add, edit, and view information within the system. • Users should be required to log into the system through Central Authentication Service (CAS). Log in should be the same as the user’s login for other CAS systems. c) Reporting/Forms, Custom Fields, Files • Product should include vendor-created dynamic forms for use in proposing and modifying courses and curriculum. Forms should modify dynamically based on fields input, should draw on information from the SIS, and automatically generate multiple dependency workflows based on real-time input. Workflows should be pregenerated based on rule sets provided by the institution. • Product should include embedded accuracy tools that automatically generate accuracy reports that compare catalog and curriculum information to information in the SIS. Product should flag courses in the catalog that are inconsistent with the SIS. • Product should include a progress tracking report to distinguish catalog pages in various stages of workflow and/or editing. • Product should provide a report notifying editors of broken web links found throughout the catalog. • Product should create forms with SIS data modeling rules that pre-populate the forms with information from the SIS. • Product should be highly customizable and able to handle school-specific coding. Vendor should be able to provide a wide range of examples of customizing the product. • Product should include the ability to build and enforce rules and restrictions relative to standard class meeting times. • Product should include the ability to visualize the density of course sections offered at a given point in time. • Product should include a grid of all potential time and instructor conflicts when scheduling course sections. • Product should have the ability to interact with the degree audit software (currently Degree Works).
