Let’s walk through RPI’s offering for a pre-planning engagement. It's a highly structured four-to-eight week engagement, meaning that we know what meetings we need to hold, we know the amount of time they will require, and we have the right plan coming into the pre-planning engagement. This way, someone working with RPI throughout this exercise will know the time and resources they will need to dedicate to the workshops, as well as what outcomes can be expected at the end.
The pre-planning period consists of workshops, stakeholder meetings, and currency discovery, meaning it offers some very high-level design consideration in terms of what the business is looking to get out of CloudSuite. Once you start identifying some of the big-ticket items that need to be focal points within the project, you can begin to draw up a roadmap for success; however, this step is highly dependent on client availability. As the selection phase for an implementation partner begins, clients usually find this roadmap and a handful of other artifacts gathered during this time very useful.
While we have a default set of deliverables that we always put together, we can also work with any organization to provide customized deliverables to meet their needs. This works for just HCM, just FSM, both, or any mix of suites or applications. I feel that RPI’s v11 pre-planning engagement is a great little offering that delivers tremendous value for its input, and our track record with it has shown some great successes for our clients.
In the past, we have presented it as a set of tools and a methodology that an organization could take on by themselves. For the right organization, I stand by that belief and am happy to talk further about this possibility, especially if anybody is looking for advice on leading such an engagement and would like our guidance, or maybe auditing of its results.