About the Enterprise Software Committee (ESC)
With consideration to our new governance structure and the fiscal state of the university, the UO should strive for the most fiscally efficient choices through the use of broad-based, centralized, and holistic decision making processes for both the enterprise software purchased as well as the Client Relationship Management (CRM) software.
To achieve these goals, the Enterprise Software Committee (ESC) will identify commonality in utilized software, create an inventory of needs, identify possible strategic partnerships and strategic utilization of open source and cloud-based software, which will lead to a leaner and more efficient infrastructure environment. The ESC will identify and make recommendations to:
- Pair down the number of software titles and contracts
- Decrease software expenses by identifying redundant software
- Identify software on more than one contract; consolidate from a single vendor
- Recommend software to be paid for centrally rather than “pass the hat”
- Make recommendations for new software policies to prevent returning to decentralized software purchasing model
The ESC will make recommendations to the IT Governance Committee and in turn to the provost the UO adopt a new vetting process that will ensure all future university software purchase decisions achieve the following objectives:
- Engage all campus stakeholders.
- Eliminate duplicate and redundant purchases.
- Leverage campus buying power to negotiate lowest price.
- Vet and rationalize the number of adopted titles in each software category to meet legitimate business needs and reduce implementation, training and support costs.
- Provide a fair and efficient funding mechanism. For example, the cost of campus site licensed software might be allocated to all campus organizations through a new technology fee based on non-grant funded FTE.
- Reduce infrastructure cost by utilizing cloud software solutions.
- Take advantage of strategic purchasing partnerships and consortiums.
- Take advantage of open and community source software options.
- Favor open APIs and consider evaluating potential ERP integration needs up front.
- Favor software that has become widely adopted/used at other universities, particularly those institutions found in the PAC12.
In fiscal year 15/16 the University of Oregon purchased almost 2000 software titles. In order to find ways to consolidate purchases the ESC has compiled a list of university software purchases and titles and is evaluating opportunities to rationalize our software inventory and reduce software spend. To accomplish these goals we have to put software into “type” categories.
Enterprise Software Committee:
Garron Hale, Director of CASIT, Chair, email@example.com
Stuart Laing, Director of Budget Operations, firstname.lastname@example.org
Mark McCulloch, Director of BAO Information Services, MMcCullo@uoregon.edu
Michael Capelli, Supervising Contracts Officer, PCS, email@example.com