Steps for calculating total cost objects and transactions per cost object
Follow the steps below to calculate the key measures of your anticipated data volumes.
Step 1: Estimate the total number of projects (root cost objects).
Step 2: Estimate the average number of WBS elements (sub cost objects) per project.
Step 3: Multiple to compute Total Cost Objects (use value in the table below)
Step 4: Estimate the average months (minor periods) of duration per project.
Step 5: Estimate the average number of cost line items (transactions) per WBS, per
month (across all versions, for example, actuals, budget, forecast, and so forth).
Step 6: Multiply to compute Transaction per Cost Object (use value in the table below).
Table of Data Volume Classes
Use the graphic below to identify into which data volume class your implementation falls. This table assumes you have less than eight custom fields and/or category assignments per transaction. If you will have more than that on average, select the next highest class.
|
Data Volume Class and Total Database Rows |
Transactions Per Cost Object |
|||||
|---|---|---|---|---|---|---|
|
1-10 |
10-100 |
100-500 |
500-1,000 |
1,000+ |
||
|
Total Cost Objects |
1-40,000 |
CLASS A 3 MM |
CLASS A 30 MM |
CLASS B 150 MM |
CLASS C 350 MM |
CLASS D* |
|
40,000- 200,000 |
CLASS A 16 MM |
CLASS B 150 MM |
CLASS C 80 MM |
CLASS D 1,600 MM |
CLASS E* |
|
|
200,000- 750,000 |
CLASS A 60 MM |
CLASS C 600 MM |
CLASS D 3,000 MM |
CLASS E 6,000 MM |
CLASS E+* |
|
|
750,000- 2,000,000 |
CLASS B 150 MM |
CLASS D 600 MM |
CLASS D 600 MM |
CLASS E+* |
||
|
2,000,000- 20,000,000 |
CLASS E 1,500 MM |
CLASS E+* |
||||
|
20,000,000+ |
CLASS E+* |
|||||
* Custom sizing exercise recommended