XBRL+SBRM = Improved BI

The combination of XBRL International's global standard technical syntax XBRL plus the clear logical conceptualization of a business report defined by OMG's forthcoming Standard Business Report Model (SBRM) is looking more and more like an improved version of BI (Business Intelligence) software. Here is a prototype you can use to think about my statement:


And so why is XBRL+SBRM based business intelligence better than current OLAP based BI offerings?  Here is a list of the reasons that I see (improved version of my old list):

  1. OLAP is “read” only; XBRL+SBRM is "read-write". Basically, XBRL + SBRM = Semantic Spreadsheet.
  2. OLAP “cubes” don’t interact with each other; Hypercubes in XBRL+SBRM DO, they know about each other and interact with each other.
  3. OLAP is proprietary and different implementations tend to not be interoperable;  XBRL+SBRM is based on global standards and XBRL is interoperable.
  4. OLAP has only limited computations supports, “roll ups” only; XBRL+SBRM supports roll ups, roll forwards, variance (difference between reporting schemes), adjustments (correction of an error), and other information patterns.
  5. OLAP cannot share  rules between implementations; XBRL+SBRM can share rules and in fact let you decouple a report from rules and therefore share rules and use rules for multiple hypercubes.
  6. OLAP cannot import “taxonomy”;  XBRL+SBRM can.
  7. OLAP is restricted to "OLAP" only; whereas XBRL+SBRM does support OLAP, but it does not require OLAP to be used, you can use a plain multidimensional model and ignore OLAP if you want. (Someone coined the term NOLAP, not-only OLAP).
  8. OLAP tends to be for numbers only and has a hard time with text; XBRL+SBRM supports both numbers and text.
  9. OLAP cubes cannot be extended; XBRL+SBRM hypercubes can be extended.
  10. OLAP does not really let you organize cubes much; XBRL+SBRM allows you to organize hypercube line items into the order that you want.  Also, using Inline XBRL you can get "pixel perfect" representations.
  11. OLAP is older and was originally constructed to be used within one enterprise; XBRL+SBRM are built to be used on the internet allowing you to easily combined internal and external information.
  12. OLAP does not have a very powerful rules engine to process information; XBRL+SBRM already has a PROLOG logic engine and two other logic/rules engines.

Additional Information:



Comments

Post a Comment

Popular posts from this blog

Getting Started with Auditchain Luca (now called Luca Suite)

Image
(Note that a newer, production version as opposed to only the development version , of Luca Suite is available) The Innovator's Dilemma points out that disruptive innovations often look like toys that are doing everything wrong. Auditchain Luca , which is part of the Auditchain Suite , is a unique approach to creating a knowledge graph .  To experience using Auditchain Luca, have a look at the Getting Started with Auditchain Luca instructions. Be sure to grab the Excel and JSON import files used for this getting started exercise.   This getting started exercise uses one of several different approaches to getting information into a tool for constructing and viewing professional quality knowledge graphs .  Additional getting started guides will be made available over time. Auditchain Luca might not make sense to you if you don't understand the paradigm shift that is occurring and if you have not shifted your mental map. For the next step in your journey, consider t...
Read more

Relational Knowledge Graph System (RKGS)

Image
Relational Knowledge Graph System (RKGS) is an interesting idea that combines the relational paradigm and the knowledge graph paradigm.  This documentation, Why RKGS , explains the idea. This gets even more interesting with the notion of "relational AI".  RelationalAI is described as follows by the company of the same name, Relational.ai : “RelationalAI is a cloud-based relational knowledge graph management system, with state of the art probabilistic processing and declarative reasoning at scale to make developing Data Applications a superpower for your business.” This notion of knowledge graphs represented in relational databases fits into my belief that knowledge graphs have two aspects: the expression SYNTAX and the logic of what is expressed or SEMANTICS. While the LOGIC of a knowledge graph is always the same regardless of technical syntax used to express that logic; there are many, many different technical syntaxes that can be used to represent a knowledge graph. There...
Read more

Professional System for Creating Financial Reports Leveraging Knowledge Graphs

Image
The document Professional System for Creating Financial Reports Leveraging Knowledge Graphs explains a new approach, a new paradigm, for creating financial reports.  The document provides a practical, nontechnical description of a professional system for creating provably high-quality financial reports where the report creator is using financial reporting schemes (such as US GAAP and IFRS) where report creator is permitted to modify the report model which leverages global standard knowledge graphs represented using XBRL. This new approach is useful, it is highly novel, and the details were highly complicated to pull together.  This is certainly not an incremental innovation.  It is definitely a disruptive innovation and it could very well be a foundational innovation. You can decide which for yourself. Foundational technologies have two dimensions that need to be considered: novelty and complexity. The more novel the technology is, the more effort needed to ensure users ...
Read more