Introduction

Spider Schema Data Model

The Spider Schema Data Model is the future of Business Intelligence / Analytical Reporting.  The Spider Schema Data Model is a robust alternative to the OLTP, OLAP, Star and Snowflake data modeling techniques used in today’s modern ERP, CRM, and Analytical Systems.

Because the Spider Schema Data Model replaces both OLTP / OLAP data models, only one system is needed.  Can you imagine a CRM or ERP system that not only processes the daily business needs, but also provides true Self-Service Analytical Reporting with no further data processing?  Imagine: no scheduled process that runs to rebuild the data warehouse.  Imagine up to the minute data that can be analyzed by just refreshing an analytical report, dashboard, or spreadsheet when you need it.

When one considers the budget in: purchasing the software and hardware, setting it up, importing historical data, and then training users on a new ERP / CRM System, the amount of time and money is staggering.  Then imagine when one realizes that’s just the beginning because once all that’s done, someone will need to create a custom Analytical Reporting system.

Every day business owners around the world try to find a way to compete in today’s market place.  Millions upon millions of dollars each year are invested into innovative new ways to analyze the data businesses capture and process.  However, after 30 plus years, not much has really changed in the way systems store and process data.

Companies that consider purchasing a new ERP or CRM system to improve and manage business processes are typically disappointed when they find out that the new system cannot even do basic financial reporting, let alone self-service data analytics or business intelligence.

Once the truth is discovered, more developers are hired, more software and hardware is purchased based on the promise that a new Analytical Reporting System will provide them with true self-service reporting.  When done, the business may have many new reports, but outside of those recently created reports, the promise of self-service reporting seldom materializes.

While attending a board meeting that ended up starting a new project, the CEO made this statement: “Is it too much to ask, seriously here; to create a system where data is not only painstakingly entered in by competent staff, but then to use that same system to do normal analytical reporting?  I mean why we do need one system to put the data into, and then another system that does the reporting?

What no one seems to understand is that the problem is in how the data is related as it is stored in the underlying database system.  The key words are how the data is RELATED.  ERP and CRM systems are built to provide On Line Transactional Processing or OLTP.

There are literally no ERP systems that can do self-service Analytic Reporting.  There may be a few that have a “built in Data Warehouse” that reporting is done from, but when you “look under the hood”; the data is not related for self-service reporting.

A solution to these problems do exist.  But in order to accomplish this, one must first understand the needs of both systems; then to combine those needs together, and create a new Data Model that supports the needs and relationships of both the Transactional and Analytical data models.  This is where the Spider Schema Data Model comes into play.