Baker Tilly's Calibrate for success: Navigating the path to Oracle Cloud

As a trailblazer in the engineering and construction industry, Integrated Project Services (IPS) offers their clients a single-source, integrated approach to designing, constructing and validating technically complex research and development, manufacturing, packaging and warehouse facilities. Having moved their financials to Oracle Cloud ERP, they have now set their sights on Oracle Cloud HCM. In preparation for the move, they worked closely with Baker Tilly’s Oracle practice to align the organization and set a strong foundation for Cloud implementation success. One of the most vital steps of an implementation is the preparation beforehand. Baker Tilly guides clients through their “Calibrate” methodology to complete critical pre-implementation planning activities to set the stage for a successful implementation.

Importance of the “Calibration” stage

"Calibrate" is a “phase 0” approach that occurs before implementation activities. This stage is utilized to ensure the alignment between three interdependent parties: Oracle, Baker Tilly and the client.

"Calibrate" is a crucial phase for identifying project timelines and resources, reducing project anxiety, educating on what’s to come, mitigating risk and accelerating time to value all while keeping operations running smoothly.

Calibration activities are broken down into three main areas:

1. Roadmap: This phase focuses on planning the full implementation process, starting with understanding the client’s goals and objectives and reviewing business and functional calendars. The phase then proceeds to establish key milestones and  phasing, as well as identify any potential other overlapping initiatives to ensure that the proposed project timeline can be met without impacting daily operations.
2. Scope: The scoping process helps with the understanding of the organization's current landscape while outlining the future state vision once Oracle Cloud is live. Baker Tilly, along with the client, confirms critical requirements and the desired level of process re-engineering required. At the end of this process, a proposal is drafted that outlines the requirements and specific functionality needed by modules to meet the organization’s needs.
3. Resource plan