We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Blog: Lyndsay Wise Subscribe to this blog's RSS feed!

Lyndsay Wise

Hi and welcome to my blog! I look forward to bringing you weekly posts about what is happening in the world of BI, CDI and marketing performance management.

About the author >

Lyndsay is the President and Founder of WiseAnalytics, an independent analyst firm specializing in business intelligence, master data management and unstructured data. For more than seven years, she has assisted clients in business systems analysis, software selection and implementation of enterprise applications. Lyndsay conducts regular research studies, consults, writes articles and speaks about improving the value of business intelligence within organizations. She can be reached at lwise@wiseanalytics.com.

Editor's Note: More articles and resources are available in Lyndsay's BeyeNETWORK Expert Channel. Be sure to visit today!

May 2010 Archives

Using dashboards to get broad visibility into business is gaining popularity.  Because of advancements in technology, organizations can use BI without a full business intelligence infrastructure.  For organizations that want to keep historical records of operations, meet compliance, identify risk, implement governance initiatives, etc. implementing a data warehouse becomes essential.  When companies look for their first data warehouse, they may not know where to start. Some general considerations include:

  1. Identifying the business purpose - Any BI project or data warehouse evaluation needs to start with a business pain or the identification of a gap within the business.  Whether this includes the ability to identify trends over time, increase analytics capabilities, or meet compliance requirements, it is impossible to successfully implement a data warehouse without defining a business need. 

  1. Data sources - Looking at where data comes from and how many sources are required may affect overall solution choiceIn addition to the purposes behind implementing a data warehouse mentioned above, many companies require a full view of what is happening within the organization that the use of operational systems doesn't give them.  For instance, information related to customers and their overall lifecycle might reside in multiple systems.  Within a data warehouse, this data can be consolidated so that decision makers can see customer actions over time and link them to marketing campaigns, identify general trends in demographics, or identify potential gaps in operations.

  1. Data volumes - How much data and how often data needs to be updated can affect solution choice.  Some data warehousing solutions are optimized for larger data sets, while others pride themselves on query performance.  There really is no one size fits all solution when it comes to data warehousing so organizations should try to match their business requirements to the solutions available in the market without trying to implement something that is outside the scope of their needs.

  1. Outputs - Identifying the output required means looking at whether the data warehouse will be used as a business intelligence back-end, to stream operational data for general analytics, or to perform extensive analytics.  Information requirements for general reporting or dashboards will be different than those used for predictive analytics or risk identification and mitigation.

These four items don't represent all of the considerations when looking at a data warehousing solution, but do identify some preliminary requirements that should be considered to identify the right solution for the organization.

Posted May 24, 2010 4:29 PM
Permalink | No Comments |

Due to a recent move and getting settled, I have been far from up to date in regards to my blog posts. Hence, this one will also be fairly borrowed (or I should say - referenced material) until I get back into the swing of things next week. One of the big news items from last week has been SAP's acquisition of Sybase, which was conveniently announced just in time for SapphireNow 2010.  Although not many in-depth details related to roadmap, etc. are known at this point, an article was recently posted on businessweek about what people can expect at a first glance.  It provides a general glimpse into what people can expect.

Overall, unlike other companies that take awhile to get their act together regarding planning and publicly announcing their roadmaps after an acquisition, SAP tends to get the ball rolling fairly quickly - with a good example being their acquisition of Business Objects a couple of years ago.  The interesting area for those in BI will be how much of Sybase's database solutions remain independent or end up being slowly integrated into the SAP stack.  Even though Business Objects is still technically it's own entity in relation to product offerings, their focus in relation to marketing and product design is heavy integration with SAP and a focus on providing solutions for SAP data.

Looking at the acquisition more broadly, Prakash Kannoth, Technology executive at ITQuadrant recently posted a blog on ebizQ mentioning the importance of mobile infrastructure and CEP technologies.  Consequently, this will probably be the areas of most benefit to SAP over time.

Posted May 17, 2010 6:55 AM
Permalink | No Comments |