Specifications include, but are not limited to: A. The System must meet the following specifications: 1. Must be web-based. 2. Must be able to allow for collection of data and artifacts used in assessing student achievement. 3. Must be able to generate longitudinal reports of student achievement as it relates to General Education requirements, University competencies, program outcomes, and multiple accrediting agency standards including but not exclusive to: SACSCOC, NCATE/CAEP, AACSB, ACS, ABET, MPCAC, and CCNE. 4. Must be able to integrate and amalgamate student achievement data to create reports at the academic program, unit (departmental level), and institutional levels. 5. Must be flexible enough for USCA to customize and build rubrics, assessments, surveys, and forms within the system. 6. Must be able to facilitate and manage outcomes across all units of a campus, both academic and non-academic. 7. Must be flexible enough to allow both academic units and non-academic units to develop, manage, and track unit goals, objectives, and outcomes. 8. Must be able to generate planning and tracking reports by unit, by college, and by campus. 9. Must be able to collect faculty and staff credentialing information and produce outputs formatted as resumes/curriculum vitas, annual performance reports, and tables relevant to accreditation reporting. 10. Must be able to generate reports that include SACSCOC faculty rosters, including uploading faculty transcripts and identifying faculty with missing transcripts. 11. Must be able to allow the development and generation of curriculum maps and their alignment to various standards (see 3 above). 12. Must be able to archive and organize evidentiary documents as well as house responses to all accrediting standards for fifth year, QEP, and reaffirmation reports for both regional and professional accrediting bodies. 13. Must be flexible enough to allow display of interactive dashboards within created forms in support of strategic, tactical, and budgetary planning cycles. 14. Must be able to export assessment and accreditation reports into well-formatted PDF files. 15. Must provide assessment and accreditation report completion tracking reports or dashboards. 16. Must provide training to end-users during implementation. 17. Must include the ability to maintain and update user accounts. 18. Security compliance requirement with SOC2 or equivalent for assessment. 19. Accessibility compliance, with VPAT for assessment. 20. The system must be able to encrypt all web access (HTTPS). 21. The system should allow users to have multiple roles without requiring multiple login accounts. 22. The number of users is unknown and will vary. 23. The system should preferably be cloud based. 24. The system should integrate with current University authentication services and protocols. 25. The system should integrate with university institutional information for user account and profile provisioning and de-provisioning (create, update, and delete operations). 26. The system should integrate with existing University services to manage groups, roles, and permissions. 27. The system’s access control model should be flexible and extensible by the University as required to meet business needs. 28. The system should allow configuration of user session controls that meet University security and privacy needs including dual authentication. 29. The system’s web interface should work with Chrome, Firefox, Safari, Edge, and IE Browsers. 30. The system should address University standards for ADA.
