Using Difference Between CAD/CAM and BIM to Understand How to Create Financial Reporting Expert Systems

The expert systems that I have helped to create thus far have been more similar to CAD/CAM type systems than BIM system.  But, the future of financial reporting will be more like BIM than CAD/CAM.

Now, most people will not understand the above statement.  I don't really expect them to.  That statement is not for you.  That statement is for those trying to understand and figure out how to build those tools.  But if you want to understand, you can.  You just need to do the work.

CAD/CAM is older technology, developed in the 1960s but took off in the 1980s and 1990s. See this History - and Future - of CAD/CAM Technology.  See this information about CAD/CAM on Wikipedia.

BIM, or Building Information Modeling, was developed beginning in about 1992.  See this History of BIM. Also see this information about BIM on Wikipedia.

This video, CAD vs BIM - The Fundamental Difference, explains the fundamental difference between CAD/CAM and BIM.  As I understand it, CAD/CAM is more about working with lines and perspectives whereas BIM is about working with objects of a building and information about a building.

This video, BIM is the Future of Engineering, explains that...well...BIM is the future of engineering.  This video, What is BIM, Understanding Building Information Modeling, helps you get a sense of what BIM is and why it is useful. For a little more detail see this video, Introduction to BIM.

Now, you probably have a question: "What the heck does all this have to do with financial reporting?" The answer is...a lot.  Those implementing digital financial reporting can use the difference between CAD/CAM and BIM to understand what they might want to build and what such coordinated digital systems are an improvement over existing approaches to financial accounting, reporting, auditing, and analysis.

XBRL is a technical syntax, it is not a system. Using the current evolution of software for representing financial information using XBRL, you work with very low level objects.  In the next evolution of such software you will use higher level objects in the ways the objects were intended to be used.  Current software tends to be a stand alone silo; future software will be coordinated systems.  Current evolution software has rather low quality; the next evolution of software will have an exponential increase in quality.  The current evolution of software is not really model based; the next evolution of financial reporting software will  be model based.

The future will be more of a coordinated system that the currently uncoordinated silos of effort.  How will we get there? Read The Great Transmutation.

Comments

Post a Comment

Popular posts from this blog

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

Getting Started with Auditchain Luca

Image
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 trying creating a report using a financial reporting scheme template . If you are struggling to figure out how to register or
Read more

Evaluating the Quality of XBRL-based Financial Reports

Image
From the time public companies started submitting XBRL-based financial reports to the U.S. Securities and Exchange Commission, I have been looking at those reports, trying to understand the XBRL-based reports, and trying to figure out how to get them right.  That information was used to figure out how to create software applications that help professional accountants get these reports right. Here is information that summarizes my testing and results which I stopped doing March 31, 2019: Analysis of the high level accounting relationships in the 10-Ks of about 5,716 financial reports  (5,063 public companies, about 89.1% got all these high level accounting relationships consistent with expectation, 623 were inconsistent and manual confirmation revealed the inconsistency was an error) Documentation that helps you understand 26 different types of errors in XBRL-based reports High quality documentation of hundreds of errors in XBRL-based reports submitted by public companies to the SEC Doc
Read more