Integration With Your Bank's Existing Analytics Infrastructure

FlowTracker was designed from the very beginning to resolve a specific information challenge faced by banks, with an absolute minimum of effort.

This design principle drove our decisions from the initial logical design through to the selection of programming languages. We have made every effort to ensure that FlowTracker can be implemented into your bank's existing infrastructure with as little effort as possible.

For example, the data requirements for FlowTracker are minimal, to ensure rapid deployment in even the most complex data environments. If your bank has a data mart, a data warehouse or customer information file of virtually any design, it will likely contain the account data that is needed.

Similarly we designed the business rules and product hierarchy functionality of the FlowTracker solution with no presets other than that some products are deposits and others are loans. Every other aspect of product definition and business rule construction is 100% tailored to your bank's conventions.

To ensure that FlowTracker works in your physical environments we chose to construct the code using the SAS Base System's programming language. Virtually all banks already have licensed Base SAS installations, so FlowTracker will run within an environment you are already supporting.

All of this adds up to minimization of cost, time and effort required to deploy FlowTracker in your bank. FlowTracker can be up and running in as little as a few weeks in your bank.

Multi-Dimensional Customer Behaviour Analysis

FlowTracker data can written back into your datamart and joined with all of the other rich information you have about customers, products, the market and your bank.

This chart illustrates some of the typical reporting dimensions where FlowTracker data illuminates new insights into behaviour and performance. For example it is possible to summarize and report FlowTracker information about sales by branch, salesperson, territory, company, city and so forth, provided the hierarchies defining the groupings exist within your data mart. Because FlowTracker data is created and stored at the lowest possible level - flow event by account - it can be summarized with complete integrity on any basis that is linked to accounts.