By an “ABC / BI Point Solution” we mean a system, often built atop a 3rd party package, that performs activity-based costing to achieve an activity or process centric view of performance, which exhibits the following characteristics:
1. The system is separate from the data warehouse, even though it is likely linked to it in terms of inbound / outbound data supply.
2. The system does not or is not capable of handling data at the transaction level as allocation input, as source supply for allocation drivers, or as the target grain for allocation output.
The key distinguishing characteristic of such a system is the presence of complicated ETL integration back and forth between the ABC tool and the warehouse.
Numerous ETL streams may be involved extracting and often rolling up transactional data from the warehouse to a different level of granularity (by product or customer, or product-customer combination) prior to loading the ABC tool. Post allocation, the ABC results might only be available at these aggregate levels, or some additional ETL mechanics may be involved to push the Results back down to individual transactions in the warehouse (in a real sense re-allocating the ABC tool's output).
Are a 3rd party ABC package and VDDW therefore mutually exclusive options? Not really. One is a software tool. The other is a design / integration approach. (And the VDDW approach in fact depends on a good ABC engine as one of its core components. See VDDW Architecture for more information.) While it is possible, perhaps likely, that not all commercially available ABC tools can support the VDDW approach, some vendors’ tools have proven scalable enough to handle the transactional detail that the VDDW approach requires. The key comparison being made is not VDDW vs. Vendor, but VDDW versus an aggregated, separately built, and cumbersomely integrated ABC point solution, whomever the supporting vendor.