Frequently asked questions

The Mock Person API, which only contains mock data that you can play around with, can be found here, https://developer.wisc.edu/apis. In the future, there will also be a mock HR API.

Building your outbound integration from SIS is not something that the ATP integrations team would help with. However, there is a central resourcing ask to assist those student information systems with the development work that they need. This resourcing should cover the development you’re looking for.

Currently PeopleSoft. Person API is sourced from Person Hub. Person Hub is then going to integrate with Workday and we hope to obfuscate the data source transition, so that the data consumers via the API do not need to make changes.

Yes, absolutely.

Ultimately, we are trying to make the workflow as similar as possible between the two systems.

Any IT team, including Distributed IT, responsible for supporting an Ancillary System will be engaged to help determine its final disposition. There will be cases where the IT team will be asked to take on some of the work to transition to the new environment. An example includes integrations to new sources of data.

IT Teams can start with providing information about ASP by directing them to the high-level information on our ASP website and ATP’s website.

We send updates the 3rd week of every month. If you are interested in staying up to date on this program, and wish to receive our monthly emails, please join the mailing list.

Send an email to Patrick Hare (ASP Program Manager), Morgan Andersen (ASP Assistant Program Director) or Adam Paulick (ASP Program Director). You can also use the ERP Ancillary Systems Program feedback form.

An ancillary system consists of any system or application that uses or provides HR or financial data or utilizes UDDS (Unit-Division-Department-Sub-Department). An example ancillary system might be as simple as a spreadsheet that pulls in financial data.

• AIP = Administration, Innovation, and Planning – department within VCFA
• ASP = Ancillary Systems Program
• ATP =  Administrative Transformation Program (https://atp.vcfa.wisc.edu/)
• EAP = UW System’s Enterprise Analytics Platform effort
• ERP = Enterprise Resource Planning
• ODMAS = Office of Data Management & Analytics Services (https://data.wisc.edu/)
• UDDS = Unit, Division, Department, Sub-department

The UW–Madison ERP Ancillary Systems Program Metrics (Source: app.smartsheet.com) gives a list of schools, colleges, institutes and divisions that we need to talk with as well as a list of ancillary systems that we currently know about. You may need to request access to view this dashboard.

 We’re working with ATP, AIP, EAP, Badger Analytics (ODMAS) and other programs to try and minimize the impact to campus staff.

Visit the Ancillary System Program dashboard (Source: app.smartsheet.com) to read the latest news and insights on this massive initiative.

Your level of required effort will depend upon the systems you use and their final-state disposition. The ASP team is actively reaching out to system owners as we step through the initial disposition process, coordinating needs and next steps based on your specific scenario(s).

To standardize finance, HR, and research administration processes and improve your work experience, the Administrative Transformation Program (ATP) is implementing Workday, a new, integrated technology system, and retiring many of the on-premise systems we use now. If you would like to learn more about ATP, please visit the ATP website (Source: atp.wisconsin.edu). To view a comprehensive list of identified ancillary systems and their final disposition, please visit the Ancillary Systems Disposition (Source: secure.atp.wisconsin.edu) page on ATP’s secure website (NetID login required).

Activity values will be replaced with the Function Code in Workday.

This will be made accessible by the Reference ID. The naming convention will include the hierarchical level.

We don’t have a final answer on this yet. The purposes for multiple hierarchies could be related to reporting, compliance, academic tracking, etc.

View the January 18 FDM presentation here

Unit, Division, Department, Sub-department (UDDS) will be replaced with several flexible Workday organization structures. Instead of using one set of UDDS codes to indicate academic, supervisory, and financial structures – there will be separate structures for each. This will allow for greater flexibility and adaptability when organizations change.

ERP is an acronym that stands for Enterprise Resource Planning.

Workday will replace Shared Financial System (SFS) and Human Resource System (HRS) at all UW System campuses. ATP will implement 17 Workday modules to manage HR, finance and select research administration processes across the system. The Workday ERP is called Financial Management (FIN) and the human resources ERP is called Human Capital Management (HCM).

Low/no code tools are visual application development tools where those with little to no IT development skills can quickly and easily automate workflows and create applications. This can save time, boost productivity, reduce costs, and increase flexibility for certain applications particularly when IT development skills or staff may not be readily available.

Phase 1 is understanding campus needs, researching various low/no code tools, and recommending how campus might support such a tool(s). A top priority is finding a safe and secure tool(s) that campus departments want to use that make it easier to comply with regulations and campus policy. Phase 2 will acquire and implement any low/no code tool(s) and set-up support structures.

Add your name to our sign-up sheet if you haven’t already done so.

There are 2 main audiences for these tools: Those that will automate workflows and create applications, and those constituents and partners that will benefit from using those workflows and applications.

No. Our intent is to provide tools that folks want to use. This effort will not remove tools already in use.

You do not have to use the selected low/no code tool and no tools will be removed as part of this initiative. We encourage using campus provided tools to better assure your applications and data are safe, secure, compliant with policy, and can leverage other campus IT and data infrastructure. Using tools not provided by campus comes with risks where the benefits need to be compared to the risks and potential impacts.

Financials will be part of the options and recommendations to campus IT leadership. Some factors on how this will be funded include how licensing works, the licensing costs, and potential service labor costs.

They are related as this initiative is under the ASP umbrella and ASP deadlines are driving the timeframe. However, this initiative is looking beyond ASP needs for what’s needed in a campus low/no code tool(s).

Over 180 people on campus signed-up to get updates or provide input. We have met with many to get that input and will continue to do so along with keeping those interested up-to-date.

We are evaluating and will present options to campus IT leadership.   Please reach out with your ideas on what type of support or services will be most valuable to your organizations.

We will recommend the skills and training needed to be proficient with the selected tool.

A recommendation will go to campus IT leadership by December 2022.  Once approved, time would be needed to align resources, acquire a tool, and thoughtfully enable it for campus use.

Campus stakeholders have expressed interest in storing sensitive/restricted data. This need will have high visibility as finalist tools are evaluated.