Retail Business Intelligence - The performance perspective
It doesn't take much to figure that your needs will increase with time. So, what happens to your toolkit-based BI during this time?
<ul><li>BI is almost always initially bought for a department or specific group whose needs justify the initial investment. </li></ul><ul><li>The BI Toolkit, the database, marts are all implemented to serve these needs. </li></ul>You began smart and compact. Then of course, you soon had to accommodate a 'few' additional needs.
Soon, it is time to accommodate a 'few' more. <ul><li>Needs change and evolve over time. With new requirements requiring new data sources to be connected to the existing BI. New groups and new users also come into the BI fold. </li></ul><ul><li>Sadly, each of these, are piecemeal additions. </li></ul><ul><li>The underlying architecture is ignored for many reasons. Restructuring the architecture is expensive. Organisations rarely have in-house restructuring capabilities. Some reports could be critical and hence need to be left untouched. </li></ul>
And soon, you are travelling in reverse. <ul><li>Soon the underlying piecemeal architecture becomes unwieldy, slow, unproductive (and prohibitively expensive to rebuild from scratch). </li></ul><ul><li>Reports take hours/days to run – business loses time-sensitive market opportunities. </li></ul><ul><li>Data inaccuracies and inconsistencies creep in – business loses faith in the numbers reported. </li></ul><ul><li>Impossible to drill down or perform analysis on the data – business cannot understand or investigate issues. </li></ul><ul><li>Database/warehouse size becomes too big to handle; loaded with redundant data. </li></ul><ul><li>Large IT team needed to maintain the system. At high support and maintenance costs. </li></ul>
You would be on the highway. <ul><li>Everything you need today and in the future is already available. </li></ul><ul><li>When your BI requirements evolve, you start using more of the capabilities of the system. Or configure changes to accommodate new needs. </li></ul><ul><li>There's no tedious build process involved. </li></ul><ul><li>As more users and data come into the fold, the underlying architecture and processing is not disrupted; remains at peak performance. </li></ul><ul><li>Data quality is maintained at the highest standards. </li></ul><ul><li>You see more users, usage and real value from BI – because now you have a decision support system you can depend on. </li></ul><ul><li>You would be putting the time on your hands to better use, like hitting the highway. </li></ul>
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.