When a company thinks that a BI system will benefit their ability to access and analyze data, a great door of opportunity is opened. Through that door will come many vendors and products that may or may not be a match for your company’s needs and abilities. From the beginning, the success of a system is establishing the needs or requirements and the proposed benefits to the company. Without these, every product can be made to look like it fits and is “just what you are looking for.”
One thing to keep in mind is that these requirements are going to change throughout the life cycle of the design process as requirement-gathering processes uncover additional application issues. Benefits can be directly related to monetary issues (such as cost savings though eliminating unsuccessful spending) as well as non- monetary benefits (such as reducing the time it takes to analyze the last month’s sales trends).
How then does a company choose which product is right-one that will match the current needs and also support the requirements of future applications? There are some simple processes that can help in this decision. The first is to break the requirements into their separate entities. These entities will separate the kinds of questions that need to be asked of the products you are considering and identify your expectations of the application.
The primary classifications are simply by data related issues and by application functionality. While other factors exist (such as corporate relationships as well as vendor characteristics) and are influential, these should be viewed as external forces on the decision process. Other external forces, such as staffing requirements, should also be considered.
This topic will be continued…..
