Our ERP (Enterprise Resource Planning) system is what runs the University’s business of educating students. It provides the tools to run the financials, human resources, and student records and curriculum aspects of a university.\u00a0 The current system’s name is Unit4 ERP (formerly Agresso).<\/span><\/p>\n In the end, a recommendation was brought by IT leadership (Scott Krajewski, AVP for IT and Chris Jacobsen, Director of Enterprise Solutions) and the Project Steering Committee to the President’s Leadership Team. That recommendation was informed by community input in various forms – departmental meetings, open campus meetings, and surveys. A short list of 3 vendors visited campus in the spring and presented demonstrations of their systems<\/a> and met with departments to learn about our needs.<\/span><\/p>\n This<\/span> high level process outline<\/span><\/a> visualizes the process.<\/span><\/p>\n The project began in 2024 with the decision to move to a new ERP and the entire process will take through 2028 with distinct phases. This<\/span> high level timeline<\/span><\/a> visualizes the major project phases from start to finish. The timeline may be adjusted depending on the specifics of the selected vendor.<\/span><\/p>\n Our current ERP, Unit4, runs on campus and the vendor is moving all customers to their cloud. Additionally the student records module will be at end of life in 2026 and would need to be replaced. The benefits of having a modern comprehensive single ERP platform are worth the time and cost to move to a new solution.<\/span><\/p>\n There are three major goals of this project.<\/span><\/p>\n What is our ERP? Our ERP (Enterprise Resource Planning) system is what runs the University’s business of educating students. It provides the tools to run the financials, human resources, and student records and curriculum aspects of a university.\u00a0 The current system’s name is Unit4 ERP (formerly Agresso). For students, Records and Registration will be replaced … Continue reading “Cloud ERP FAQs”<\/span><\/a><\/p>\n","protected":false},"author":1247,"featured_media":0,"parent":1748,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-1763","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/sites.augsburg.edu\/it\/wp-json\/wp\/v2\/pages\/1763","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sites.augsburg.edu\/it\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.augsburg.edu\/it\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.augsburg.edu\/it\/wp-json\/wp\/v2\/users\/1247"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.augsburg.edu\/it\/wp-json\/wp\/v2\/comments?post=1763"}],"version-history":[{"count":8,"href":"https:\/\/sites.augsburg.edu\/it\/wp-json\/wp\/v2\/pages\/1763\/revisions"}],"predecessor-version":[{"id":1930,"href":"https:\/\/sites.augsburg.edu\/it\/wp-json\/wp\/v2\/pages\/1763\/revisions\/1930"}],"up":[{"embeddable":true,"href":"https:\/\/sites.augsburg.edu\/it\/wp-json\/wp\/v2\/pages\/1748"}],"wp:attachment":[{"href":"https:\/\/sites.augsburg.edu\/it\/wp-json\/wp\/v2\/media?parent=1763"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
Who is deciding which product we will change to?<\/h2>\n
What is the project timeline?<\/h2>\n
Why are we changing ERPs?<\/h2>\n
What are the goals of this project?<\/h2>\n
\n
\n
\n
\n
\n
\n