160 likes | 306 Views
Enterprise Systems: A Brief Update. Ken Wozniak August 19, 2013. Background on Enterprise Systems. 2006 goal: replace 3 of USC’s 25-year-old home-grown administrative systems Finance HR/Payroll Research Administration Late 2006: CFO approved joining the Kuali Foundation as partner
E N D
Enterprise Systems:A Brief Update Ken Wozniak August 19, 2013
Background on Enterprise Systems • 2006 goal: replace 3 of USC’s 25-year-old home-grown administrative systems • Finance • HR/Payroll • Research Administration • Late 2006: CFO approved joining the Kuali Foundation as partner • 4 USC developers joined peers to develop the Kuali Financial System 2
Background on Enterprise Systems • 2009: proposal was made to the Finance Committee to replace USC’s administrative systems • Finance Committee endorsed a replacement concept estimated at $75 million • Included those 3 administrative systems, plus Student Information System • Funding to be requested at the commencement of each project 3
Where We’ve Been • KFS implemented, TARA research administration suite is being implemented (due for completion in about a year). • TARA: Kuali Coeus; Click Commerce for compliance, and CORES for lab recharges. • SaaS-based Workday hr/payroll system: go live at the end of 2013. 4
Where We’ve Been • Business Intelligence, SciQuest e-Procurement system, and T2 in production. • USC suspended participation in Kuali Student project in June 2013 • 4-year, $5 million obligation fulfilled • no deployable modules • completion still at least 4 years away. 5
What is Different? • Added efficiency. Consider cashiering: • Deposits with multiple payment types • Secure deposit process • efficiency in bank rec, document routing verification • long queues reduced • BI system addressed : the inability to access and analyze data to produce business projections that enable sound business decisions. 6
What is Different? • Internal audit report “concern over the amount of paperwork that certain school and department staff are required to complete due to a lack of automation or workflows.” • Greater level of process automation • KEW apps • Kuali Coeus post-award in production. Linked with KFS: improved financial management of research awards 7
Where We’re Going –Administrative Systems and Beyond • SaaS-based Microsoft Office 365 • Email encryption • Students to Google Apps • Student System strategy • Faculty Affairs Suite (FAS) • Faculty Application Manager (FAM) in production on AWS • Dossier evaluation and offer letters 8
Where We’re Going –Administrative Systems and Beyond • Learning Management System Review • Mobile apps for routing and approval • Kuali Financial System • Kuali Coeus • DV/QE 9
Developing the Roadmap • Admin system replacement, email/ calendaring, the faculty suite, and LMS - pragmatic need: aging systems. Not driven by a strategic vision. • Enterprise systems not at the finish line; just the starting point. • Task: envision the future of enterprise systems, and move toward it. • Guided by the university’s strategic vision. 10
Developing the Roadmap • Consider : “This strategic vision is a call to action, a call to think boldly and to enact the transformations envisioned here. . . . We challenge our entire university community to use this vision to guide strategic planning and action for the coming decade.” 11
Developing the Roadmap • Strategic Vision - three objectives: • Transformation of education • Scholarship with impact in all academic areas • Engagement in society at a global level • Constant, recurring theme: research • The research university in general • Basic research • Translational research • Health-related research 12
Developing the Roadmap • Research – the element that guides enterprise systems in the future • Consider the following: • What IT centers of excellence will be required to achieve the research goals outlined in the strategic vision? • How will the system development task be approached within the context of research goals? 13
Developing the Roadmap • How can the enterprise systems function protect institutional resources while ensuring personal privacy and respecting intellectual freedom? • In developing enterprise systems focused on research, what are the appropriate roles of governance, multi-sourcing, outsourcing, collaborative development, local innovation, and the pragmatic exploitation of technology? 14
Developing the Roadmap • Where shall the enterprise systems function be set on the risk continuum, and how will this level of risk tolerance be aligned with USC’s research culture? • Shall the enterprise systems function be viewed as a research support effort, or as a partner in defining research goals? 15
For More Information • For more information on some of the current enterprise systems efforts, look at the following: • http://fbs.usc.edu/depts/kuali • http://www.usc.edu/dept/hr/workday • http://www.usc.edu/its/office365 16