ITS Organizational Announcement

June 27, 2019

As discussed in April, the senior leadership team has been working to finalize the design of the Enterprise Applications (EA) team as well as the IT Shared Service organization.  After several engaged discussions with the Business Systems Group and Campus Community Technologies leadership teams, the structure has been refined as follows:

The Enterprise Applications reporting structure is defined based on the functional and University-wide areas supported, including Web Technologies, Community Engagement, Alumni/Development Systems, Research Administrative Systems, Finance Systems, Human Resource Systems, and Student Systems. A new team, Application Platforms, will provide integration support and application architecture functions across all EA teams. 

Other organizational changes include:

  • The Student Technology Collaborative will be aligned to Campus Technology to more closely tie this work to other forms of support services
  • Facilities Information Systems and Public Safety IT support will align to Foundational Technology Services to benefit from the collaborative work we are doing that significantly overlaps these team’s goals
  • IT Partner Consultation will move to Campus Technology

These changes are beginning to take effect, and we expect changes to be fully completed by the fall.

Concurrent with these changes, we have defined the IT Shared Services team. This team expands on the centralized Portfolio Management and Service Management team and creates an internally-facing support team for all of Information Technology. Specifically, this team will house Quality Assurance, Education, and Training, and Enterprise Architecture functions. In addition, all project managers will have a dual reporting relationship to the Portfolio Management Office. This IT Shared Services organization has been formed to bring together each of the groups that have cross-cutting support roles necessary to advance our strategic goals. 

Details and timing of each move are being worked through the respective management teams. I want to particularly thank the working groups that thoughtfully engaged in these discussions and helped to lead us to this final design.

Thank you,

John