ESUP: What's Changing?

Since the Enterprise Systems Upgrade Program (ESUP) kicked off in October 2012, people have wanted to know what is going to change when the new system goes live. Users of the University's enterprise student system expect the look and feel of the system to change, but they also know that this is the first time that there has been a comprehensive examination of the related business processes since 1999. The question on everyone's mind is: what will change as a result of that examination and how?

Until the Interactive Design and Prototyping (IDP) activity for business processes was complete and the team recommendations made their way through ESUP governance, it was difficult to discuss the changes that might be happening. With the Student work stream nearing the end of the IDP phase, a picture of the new system and its associated processes is becoming more clear.

The Student work stream has done a tremendous job of following the three principles of their system's upgrade:

1. Utilize delivered "Self-Service" functionality for students, faculty, and staff.


2. Wherever possible, use delivered PeopleSoft functionality without customization or implement the industry-standard, best-practice approach.


3. Improve or retain U of M business process best-practice solutions not delivered in PeopleSoft.

The work of IDP was centered on an entire business process and as the recommendations for those business processes are approved through ESUP governance, they are being made available on the ESUP What's Changing? website. On that page, you will see a list of approved changes that are now being communicated to the University community. A short description of the recommendation for the process is on the page, as well as a link to more detailed information.

This will not be the only venue for communicating these changes. More opportunities, including training, will be available as we near go-live in fall 2014. If you have questions or feedback on the information available on the page, please email esup@umn.edu.