Specifications include, but are not limited to: 4.3.1 Strategic Goals 4.3.1.1 Reduce cost 4.3.1.2 Improve efficiency 4.3.1.3 Make better use of resources, increase throughput, and reduce cost per transaction. 4.3.1.4 Increase the ability to be compliant with laws and regulations. 4.3.1.5 Improve our ability to get meaningful data from the system that is relevant to the whole organization. 4.3.1.6 Understand, plan, and execute organizational changes needed to support a system-wide ERP for the University by optimizing resources, eliminating redundancies, and streamlining business department structures. 4.3.2 Tactical Goals 4.3.2.1 Re-implement a single instance of PeopleSoft Financials and PeopleSoft Human Capital systems for all campuses by starting with the delivered version of PeopleSoft. This is not a consolidation where we would move one campus into an existing system used by another campus. This is a brand new “green-field” reimplementation of PeopleSoft that should take advantage of delivered functionality and eliminate as many customizations, bolt-ons, duplicative processes and third party systems as possible. Data from two HCM and Financial systems currently used by the two campuses must be ported into the newly developed single instances of HCM and Financials. OU would either implement the currently licensed version listed in the table on page four, or possibly reengage Oracle support and implement the most recent version. 4.3.2.2 Standardize business processes across the University system by conforming, redesigning, and eliminating campus-specific, disparate methods for performing standard business functions. 4.3.2.3 Re-design chart of accounts to work across the University system. 4.3.2.4 Refactor payroll processes to improve effectiveness and remove redundancies. 4.3.2.5 Establish uniform eProcurement system and accounts payable processes university-wide. 4.3.2.6 Examine and understand options for implementing Position Control as an approved/authorized budgetary tool. 4.3.2.7 Examine and understand options for implementing Position Management. 4.3.2.8 Use software as close to original design and intent as possible. (a.k.a. “Vanilla”) 4.3.2.9 Make use of existing PeopleSoft modules that are already licensed, but may have not been implemented or are under-utilized.