PBCS vs. EPBCS

Planning and Budgeting Cloud vs Enterprise Planning and Budgeting Cloud

PBCS VS EPBCS

If you are considering a migration from Hyperion Planning on-premise to the Cloud, there are two options available from Oracle: PBCS (Planning and Budgeting Cloud) and EPBCS (Enterprise Planning and Budgeting Cloud.)

Wondering which solution is the best fit for your needs?

Oracle PBCS (Planning and Budgeting Cloud Service) enables enterprise-level and departmental-level planning processes by providing both Excel-based and web-based Excel-like modeling, planning, and approval capabilities within one scalable solution.

PBCS uses a powerful calculation engine that can express a range of business logic with in-memory aggregation and instant analysis and reporting. It also provides user-defined task and navigation flows that can be customized based on the needs of the users.

With EPBCS you receive the same features as PBCS in addition to the following out-of-the-box modules: Capital, Workforce, Projects, Financials, and Strategic Modeling. EPBCS includes pre-built content that can be gradually customized to your planning needs, and all modules can be integrated with each other.

Other differences between the two solutions include:

Both PBCS and EPBCS can host only one Planning application per cloud instance. It is within the application that EPBCS can turn on the relevant cubes for the selected frameworks. EPBCS framework cube names cannot be changed and PBCS cube names can be defined during the application/plan type setup.

In PBCS , additional dimensions can be added later provided all artifacts are updated. In EPBCS , dimensions can only be added when configuring each framework for the first time.

Forms, dashboards, business rules, data integration between plan types, etc. are pre-built in EPBCS , and more can be added. All artifacts in PBCS are created as custom development.

While most EPBCS artifacts can be edited, as a general rule, it is recommended that all pre-built content be left as is to avoid dependency issues. However, new artifacts can always be added. PBCS can always be edited due to its custom nature.

Sandboxing is available in both PBCS and EPBCS , but it is not available in the EPBCS pre-built frameworks.

It is important to note that in EPBCS individual framework features can be enabled over time. While you have access to all of these modules, you do not have to use them all or enable them all at one time. So, rather than struggle to make a certain structure work for your needs, you can choose to turn on only the parts that serve your purpose, and as your business process evolves over time the application can evolve with you.

PBCS and EPBCS are both great options if you are looking for an easy to use planning, budgeting, and forecasting solution. Both applications will help you reduce licensing costs, internal support, and infrastructure costs. If you are lacking a dedicated IT department or if you want to try out an EPM application before making the infrastructure investment that comes with having an on-premise application, then these cloud solutions are worth your consideration.

Deciding between these two products may be driven by the nature of each application’s structure. The best practice processes that come pre-built in EPBCS may be a better fit for customers who are new to EPM products, don’t have a well-defined business process, or do not have the need for a highly tailored application, whereas those who need a more customized solution may be better served by PBCS.

Whichever route you choose, MindStream Analytics’ experienced EPM consultants can guide you on your journey to the cloud.

Tags: Business Intelligence Enterprise Performance Management Profitability Analysis

Essbase Cube Oracle Enterprise Planning and Budgeting Cloud Services Predictive Analytics

Hyperion Financial Management Hyperion Software Hyperion Managed Services

Oracle FCCS Oracle OBIEE What is Essbase? What is OneStream? OneStream XF