An In-Depth Look at the PBCS 4 Weeks Implementation Process

Follow us on Twitter & LinkedIn for more tutorials, case studies, and articles.

Publication Date: 06/10/2019
Share This Article

Oracle's Planning & Budgeting Cloud Service (PBCS) is a service that offers Hyperion Planning (which includes planning, budgeting, and forecasting) through cloud. PBCS is a good fit for most companies because of the more accurate planning (which is void of human error), quickness to install/start working, customization abilities, and its cost-saving expenses.

For a case study showing the amazing results from our implementation process, please visit the article "The PBCS 4 Weeks Implementation Process".

A LOOK AT OUR IMPLEMENTATION PROCESS

The initial first week of implementation will focus mainly on requirement gathering and initial application building. This is when our consultants will discuss with subject matter experts (SMEs) and gather information for the design of the application.

We will also configure the application for test and production, as well as configure security settings or grant access to users (so they may view the application and offer insight as we start building).

We will keep the end users engaged starting from week 1 all the way to week 4. This way, once training and user acceptance testing (UAT) begins, end users will not be surprised or shocked.

As we progress to the second week, our consultants will design the application and start loading metadata. This data will include information such as Accounts, Entity, Cost Center, and other hierarchies. We will then extract data from source systems to ensure effortless future load process.

Data forms will be created for manual data input such as Topside adjustments, Planning & Budgeting input or adjustments, and so forth. This week will also see the start of designing and creating business rules to run calculations based on business processes.

Week 3 is when we begin to finalize business rules and start the data load process. Our consultants will first load the current year data as it’s easier to validate and create reports and dashboards on. Once the current year has been validated, we then start loading historical data.

The last week of the implementation process is when our consultants will migrate the application into the production environment. This is also the phase where we perform user testing.

Once the user testing part is complete, Paradigm SES is available to provide further training on documentations and knowledge transfer sessions. We will also be able to provide another Q&A if necessary to answer any additional questions from the user.

After the process is completed, Paradigm SES offers 30 days of support after production sign-off, so users can still contact us if any questions or issues arise.