Specifications include, but are not limited to: rovision a generic demo environment to set up and socialize baseline functionality starting with SAE and then SFP. No configurations are anticipated for University processes will be done, and the environment will be hosted in the Respondent’s domain. Load a basic set of demo data. Include data regarding students, their academic schedules, college fees, and mocked up data to represent what would be received from the Department of Education (e.g., ISIR data, NSLDS data, and COD data for PELL and Federal Loan disbursements). Create scenarios (to be worked alone) and instructor led workshops designed to provide University administrators with hands-on end-to-end experience in financial aid solutions. Educate University administrators on where configuration is possible. Collaborate with Oracle on confirming perceived gaps and feature enhancements identified during the socialization of the financial aid solutions. Perform a change impact assessment of the current financial aid processes. Apply the guiding principles to facilitate conversations and establish a change management plan and begin preparing administrators for the change. Be sure to include education activities for the University experts assigned to the project so that they can function as a change champion with colleagues across the system. Assess the need for the University to load historical state financial aid records. Provide a Key Design Document with a recommendation and the pros/cons for each option. Perform a data mapping exercise with each institution to review current campus SIS data definitions and map them to student attributes to support data conversion for implementation of the Student Management Cloud (SMC) solution and Student Financial Planning to the extent possible based on the most recent product release (i.e., 23D). Facilitate discussions as necessary to come to alignment on definitions where needed. Describe your approach to this process in detail. Propose a data governance strategy to ensure the University maintains a common set of data definitions and consistency with use of data. Provide a representation of the future SIS ecosystem for the University with Oracle Fusion Cloud Student solutions as the core platform. Identify any and all integrations that will be needed to connect with existing solutions that could be retired versus those that need to be retained to fill gaps not provided by Oracle solutions. Establish and co-manage a project plan in conjunction with UT project leadership that takes into consideration the deliverables, key milestones, and timeline for this engagement. The SIS Preparation project will operate within the guiding principles endorsed by executive leaders, including but not limited to, the president and campus chancellors: These eight principles will serve as the foundation for decision-making as the UT System explores and then works to deliver a single, systemwide SIS. They will guide program team members as they partner with the University community to achieve the program’s goals and objectives. A new, systemwide SIS will be a key component in the delivery of a more consistent and intuitive student experience focused on service excellence, increased engagement, and enhanced student success outcomes. The system will help us ensure that all students remain strong ambassadors of the University of Tennessee, both during and well after their academic journey.
