Operational Design

During the Enterprise Project’s early stages, an Operational Design workgroup was established to develop a post-deployment support model, referred to as Enterprise Operations. The workgroup members have accomplished a great deal in beginning to define how Ohio State will effectively manage the technology being implemented by the Enterprise Project. To allow workgroup members to focus on their primary project areas, the Business Advocates have been charged with driving the Operational Design efforts moving forward.

Strategic Direction for Enterprise Operations

Enterprise Operations (a central support organization) will be created within the Office of the Chief Information Officer to enable the institution to fully leverage and manage Workday and other enterprise technologies.

At the end of the Plan and Foundational Design phase (August 2017), the Executive Sponsors established the following as the strategic direction for Enterprise Operations and other technology and data areas of the Enterprise Project:

  • Integrate Workday with other systems using modern integration technology
  • Implement business intelligence, analytics and reports needed to run the operations of Ohio State, capitalizing on Workday and reporting and analytics technologies
  • Deliver a new business intelligence, analytics and reports platform to advance the use of data and analytics and reduce duplication
  • Stand up governance functions across data, systems operations and reports
  • Operationalize a support structure that leverages the agility of cloud software and ensures clear, secure, effective and efficient support
  • Reduce the number of shadow systems utilized within the university community
  • Simplify the user support and call center functions for institutional operations
  • Develop the Foundation Data Model that will support the finance, HR, payroll and student functional areas
  • Shift towards the mindset of data as an institutional asset



The high level Operational Design Vision Guiding Principles include:

  • Simplifed and streamlined support
  • Engaged and informed users
  • Service availability and quality support
  • Up-to-date process and product support
  • Proactive workforce management
  • Quality data outcomes
  • Alignment to university goals


The Operational Design workgroup met frequently over the past year to develop guiding principles, agree on scope and make initial recommendations to the Enterprise Project Executive Sponsors. The following recommendations were accepted by the Executive Sponsors in August 2017:

  • Enterprise Operations will be a central unit to support Ohio State’s enterprise-wide, cloud solutions.  Enterprise Operations will include (but is not limited to):  Training and Communications Management, Technical Operations, Vendor Relationship Management and Governance Facilitation. 
  • Enterprise Operations will report to the university’s Chief Information Officer. The expertise from the Office of Chief Information Officer is needed to manage the relationship with Workday and to be the primary support for enterprise technology. 
  • Enterprise Operations will have a strong focus on service delivery, and it will continuously evolve and improve over time. 
  • A governance model, including Service Level Agreements, will be developed to ensure long-term alignment with business needs. 

Since August 2017, subgroups of the Operational Design workgroup formed to operationalize the above recommendations. The effort underway includes defining processes, roles and work; creating options for organizational structure, staffing and budget; and coming to agreement with Executive Sponsors on the Enterprise Operations organizational structure and budgets. The ultimate goal is to have Enterprise Operations in place before the end of the project’s Testing phase, or approximately three months before the initial Workday deployment (see Project Timeline).


Do you have specific Operational Design questions? Please contact Dave Kieffer, Associate Vice President for Administrative Systems.