Individualized Degree Design Tool

The Vendor is required to provide individualized degree design tool that supports ease of use, accessibility, reporting, and system integration.
- Requirement:
1. Functional
•    The user may be able to upload multiple attachments, including word, pdf, image, text files.
•    The system may be able to display forms and information in both English and Spanish.
•    They system may be able to be branded with state empire colors and logos.
•    Administrators may be able to impersonate other user roles. 
•    Technical staff may need to be able to see the student perspective of the system.
•    The system may have a responsive design and be accessible from mobile devices. 
•    Students must be able to create multiple versions at the same time.
•    The system must be able to accommodate the entry and storage of notes and comments, including history with date/time/user notations. 
•    It must be able to manage notes and comments from different user roles. 
•    The system must be able to manage electronic notifications (including automated based on workflow).
•    The primary interface for the system must be web based.
•    The system must be able to customize multi-step workflows.
•    The vendor must be able to conduct business in state.
•    The vendor must have been in business for at least 3 years.
2. Reporting
•    The system must be able to generate reports on demand. 
•    The reports must be able to be exported out of the system via csv file. 
•    Sample reports include numbers of programs by type and date, average of time to complete a workflow, etc...
•    The system may have dashboard functionality based on user roles. 
•    They may include but are not limited to the list of items in workflow queues, degree programs by mentor - date - discipline, ability to filter on multiple data points - including submission date and status, etc.…
3. Security
•    The system must be able have role-based access control, managed at the university level. User roles includes student, administrator, advisor, etc.…
•    The system must allow certain user roles field level edit access.
•    The system must be FERPA compliant.
•    The system must be GDPR compliant.
•    The system must be GLBA compliant.
4. Support
•    The vendor must provide product documentation, training and ongoing maintenance.
•    The vendor must provide an implementation plan, including timeline.
•    Describe in detail what type and level of support is available during implementation.  
•    Your ticketing system and process of managing issues submitted and reported.  Please provide all your service level agreements (SLA).
5. Technical
•    The system may allow for the flow of special characters.
•    The vendor may have experience working with Ellucian banner.
•    The vendor may have experience working with state institutions.
•    The vendor must have certifications appropriate to the technology platform used to develop the solution.
•    The system must be able accommodate APIS via ethos. The data must integrate bi-directional between the system and Ellucian banner. 
•    It must also push data to degree works.
•    Operates in a cloud-based solution (SaaS).  
•    The vendor must manage data migration from lotus notes to the new system for all active student data.
•    The software must manage change control tracking functionality 
•    Platform provides secure authentication methods through single sign-on (SSO) with industry standard protocols
•    The system may include version control at the document level. 
•    We would like the ability to revert back to a previous version of a document throughout the document's lifecycle.
•    System uptime must be 99.5%. 
•    Provide details on the performance of your application that is directly related to your system uptime being 99.5%.