Specifications include, but are not limited to: The University of Georgia (UGA) is seeking a replacement for the Hyperion budget management application used for budget development. The replacement solution should also have added functionality for budget planning, forecasting, and commitment tracking. The solution for which this RFP is being issued is not intended as a replacement of the financial enterprise resource planning (ERP) software currently in use by UGA (PeopleSoft Financials and PeopleSoft HCM). The budget planning and development solution will provide near-real time insights into a series of financial metrics, utilizing a defined set of data sourced from the HCM and financial ERPs. Below are some baseline requirements and/or assumptions that will need to be maintained in future state business processes. In its current state, UGA’s budget system has approximately 700 distinct users. General Requirements: o Data security: Solution must be able to support complex authentication system integrations including but not limited to Central Authentication System (CAS) for single sign-on and Duo for two-factor authentication. Solution must support compliance with Gramm-Leach-Bliley Act (GLBA) Standards for Safeguarding Customer Information 16 CFR Part 314 section 314.4 Elements. See https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314/section-314.4 for reference. UGA must maintain full ownership of the data. Solution must provide for data privacy and access controls to segregate UGA’s data so that it is only accessible to UGA users. o System should be able to accommodate inbound and outbound integrations with major ERPs such as PeopleSoft, Oracle, and Workday finance and HR/payroll systems. o Business continuity: Vendors maintain and test formal business continuity procedures and protocols. o Enterprise-wide users: Solution must have delivered security that can accommodate role-based access controls. Both row level and component level access controls must be available. o Evidence of system stability, data backup practices and data privacy standards in compliance with AICPA principles. o System must support ad hoc report development. o Solution must be compliant with Web accessibility standards.
