The BPC 10.

0 sizing guide

Significant changes were introduced with the BPC 10.0 NW release

The .NET layer was removed and its function was taken over by the ABAP server.
The BW 7.3 platform removes the 100 user limit per application server.

The 7.5 guide was mainly based on read, write and load operations,
The efforts for the 10.0 guide went way beyond and included other items not accounted
for in the 7.5 guide.

Namely:

Business Process Flows

Change Work Status (EPM Addin Client)

Dimension processing

Upload Transactional Data (DataManager)

Transactional Data Transfer Between Cubes (DataManager)

Logic calculations

Work Status (Web Client)

Web Reporting

User Input Data via the Web Client

There are two main installation paths that can be chosen for your SAP Business Objects
Planning and Consolidation 10.0, version for Netweaver (BPC10NW) implementation:

The "Add On" method

Install BPC10NW within your current BW system (the "Add On" method)

The "Stand Alone" method

Install BPC10NW on a separate BW system (the "Stand Alone" method).

SAP Business Objects Planning and Consolidation 10, version for Netweaver (BPC10NW),
must be installed on a suitable Net weaver platform.

BPC10NW, the Netweaver platform version must be Netweaver 7.3.

The factors that need to be evaluated for each implementation:

Hardware Investment
Performance
Administration Costs
Integration Development and Maintenance
Upgrade Considerations
Support Pack Considerations
BWA Investment
Data Movements

Hardware Investment

There is typically some increase in hardware investment when implementing any

BPC10NW project.
The Stand Alone scenario will lead to some additional cost for servers required for
creating the new instance of BW that will be used to support the BPC10NW application.

The Add-On" implementation scenario will also require additional application servers to
accommodate the anticipated incremental BPC10NW user load on the existing BW
system.
The net hardware cost differences between "Stand Alone" and "Add-On" may be
negligible.
Performance
On initial reflection, the Stand Alone scenario may be presumed to inherently have
superior performance;
However this is not necessarily the case if the Add-On scenario is properly sized.
In addition, load balancing is also an important consideration to ensure overall system
responsiveness (for example, BPC10NW processes can be isolated from BW processes,
from a load balancing perspective, if desired).

Integration Development and Maintenance

There are a variety of ETL tools to pull master and transactional data into BPC10NW, but
these tools typically point to BW objects (info cubes and info objects) within the hosting
BW for source input.
Following a Stand Alone implementation path, additional processes will need to be
developed to load the source data into the BPC10NW supporting NW environment. This
additional configuration will need to be developed and, of course, maintained.

Upgrade Considerations
In a Stand Alone deployment, it may be easier to upgrade your main BW system while
leaving your BPC10NW hosting BW system at an earlier revision.
One of the main benefits to the stand alone path is the elimination of many of the
dependencies between BW upgrades and BPC10NW upgrades.
This decoupling may be a significant consideration since currently BPC10NW is currently
only supported by Netweaver 7.3

Recognize that system upgrades depend on a number of business environmental

factors:

Corporate politics,

The needs and schedule of the end user work streams (i.e.: Finance, Sales,
Marketing, HR, etc.)

The technical capacities to perform the work.

Support Pack Considerations

BWA Investment
Data Movements

Most customers will load master/transactional data into their main BW systems
for general reporting purposes.

A Stand Alone process will require at least two sets of data to be generated (one
for the main BW system, and a second set for the host BW system).

When data is pulled into the BPC10NW application a third set of data can be
generated as well.

Other Considerations

Creating and installing a "system copy" (i.e.: to establish a quality test

environment) will be incrementally easier with Stand Alone approach. The copied system
will be much smaller due to its segregation from the main BW processes.

The creation of an environment copy in BPC10NW can be significantly streamlined

via the introduction of the transaction code UJBR (Backup and Recovery). This
transaction allows the backup of configuration and data that can be easily moved from
one system to another. Using UJBR decouples the need for a BW backup for BPC
recovery, thereby allowing for an easier, less risky, implementation using the Add In
approach.

Data Manger is by design constrained to one BW instance (the instance upon

which BPC10NW is installed), so the ability to create a master process chain to update all
data will require additional separate steps for a stand-alone system. Additional BW
configuration, such as additional staging cubes and the potential for redundant data with
both BW systems should be anticipated.