Specifications include, but are not limited to: SECURITY AND ACCESS CONTROL REQUIREMENTS R The solution shall allow secure login leveraging LDAP, SAML, Active Directory or Shibboleth security integration and determine level of access via identified fields within LDAP. R The solution shall allow for granular control of access to profile data and workflows; including full access, limited access, and view only access; based on user. R The solution must allow the administrator to assign security roles to users R System must provide logging of user management, administrative activity, and of user activity. R The solution must allow the university admistrator to view user data on system use, (logins, uploads, modifications, etc). R If the system is doing any authentication, it must not use or provide default credentials. R The cloud service must have implemented FedRAMP low baseline controls (though does not need to have Authorization To Operate). INTERFACE/ACCESSABILITY REQUIREMENTS R The solution will allow faculty to enter data via web browser R The solution must allow bulk import of data from spreadsheets in CSV format R The solution must allow for import of data from Peoplesoft through the use of an API or other means R All proposed systems shall allow data integration between systems if appliciable R The solution must have a convenient method for faculty to import activity data from legacy documents such as CVs/resumes R The solution must allow faculty to upload supporting documentation to activity fields in typical formats (CSV, Word, PDF, JPEG, etc.) R The solution must allow for integration with our course evaluation system (currently EvaluationKit) R Application Program Interface (API) information shall be made available to USM to allow possible in-house programming of data interchange to and from third party applications. R Web content shall meet ISO/IEC 40500:2012 -Web Content Accessibility Guidelines (WCAG) 2.0 AA at a minimum. R The solution must be accessible through the certified standard web browsers (Safari, Mozilla Firefox, Google Chrome, Microsoft Edge, etc.) Provide a list of all web browsers and associated versions that are usable. DATA REQUIREMENTS R The solution must allow for data field customization within each activity type R The solution must have the ability to include faculty HR data such as education, date of hire, rank, etc. R The solution must allow faculty to track activities in teaching, research, creative activity, and service R The solution must have the capability to lock certain data fields from modification by anyone other than an admin R The solution shall capture and store profile information in searchable data fields customized and defined by USM, including, but not limited to: • • General Information Personal and Contact Information Biography/Expertise/Web Profile •• Administrative Data Permanent Data Yearly Data Administrative Assignments Appointments Awards and Honors Consulting Education Graduate/Post-Graduate Training Faculty/Professional Development Activities Attended Licensures and Certifications Media Appearance, Reviews, and Interviews Professional Memberships References Work History Workload Information Annual Evaluation •• Teaching Academic Advising Directed Student Learning (e.g., theses, dissertations) Mentoring Non-Credit Instruction Taught Scheduled Teaching Teaching Innovation and Curriculum Development Teaching Qualifications •• Scholarship/Research/Creative Activities •• Biographical Sketch NIH NSF Contracts, Fellowships, Grants and Sponsored Research Creative, Artistic and Professional Writings, Performances and Exhibits Intellectual Property (e.g., copyrights, patents) Presentations Publications Research, Creative, Scholarly Activity in Progress •• Service University Professional Public FUNCTIONAL REQUIREMENTS R The solution must have the ability to manage faculty approval process such as tenure and promotion and annual evaluation R The solution must allow for changes in university structure (college, department, etc.) R The solution shall include customizable workflows for routing faculty information for review and approval. R The solution shall allow user-defined fields in the routing and approval document. R The solution shall allow a workflow step to be flagged as under review or in the process of being reviewed. R The solution shall display workflow tasks as they are completed. R The solution shall provide the ability to define automatic trigger alerts for notifications in the review and approval workflow process. R The solution shall trigger alerts or task notifications to appropriate reviewers/approvers as faculty evaluation documentation progress through designated workflows.
