Interchangeable Parts: Information Lego Blocks

In 1798 a significant shift occurred when the concept of “interchangeable parts” was perfected when Ely Whitney applied that idea to the manufacture of rifles.  Before interchangeable parts, all goods created around the globe where individually created by a skilled craftsmen.

An interchangeable part is a part or component that is created to a specific specification and is identical to other parts and will fit into an assembly that requires that part/component.  No customization was required to make the part/component fit into the assembly. This enables easy assembly, a reduction in the skills required to assemble, easier repair, which minimizes time and cost.

OMG's forthcoming Standard Business Report Model (SBRM) going to be an enabler of “interchangeable parts” for business reporting in the Fourth Industrial Revolution, the Information Age.

While in the 1790s the concept of interchangeable parts enabled to creation of machining tools that could create the precision parts necessary to enable the feature of interchangeability; SBRM will enable to create tools, such as software tools, than enable this information component interchangeability.

This notion of “information component interchangeability” has already been implemented in five software applications that I have helped to create in varying degrees.  The most extensive implementation of this has been in Auditchain’s Pacioli (logic engine and verification tool) and Luca (part of the Auditchain Suite which is an expert system tool for creating financial reports).  The notion of a “jig” was first created and used in Pesseract about 4 years ago with mild success.  Luca fully supports the notion of a “jig” which enables application users to work with higher level logical structures rather than with the individual “atoms” that make up those structures.  All five software applications implemented the notion of the “block” when enables the creation of jigs among other things.

SBRM can enable the creation and exchange of INFORMATION at both the semantic (meaning, logic) level and the syntax (physical format, technical specification) level.  XBRL is one global standard technical syntax that is broadly used.

Today; financial accounting, reporting, auditing, and analysis artifacts are created by costly highly skilled craftsmen.  In the near future, because of SBRM and the interchangeable information parts/components that it enables to be created will revolutionize financial accounting, reporting, auditing, and analysis.  This is but one example of what SBRM could do for general business reporting globally.

Think of it like this.  Think “Lego Blocks”.  Mark Cossey, in a LinkedIn post, provided the graphic shown below.  Data that is sorted, classified, structured, arranged, and represented to be consumable by both humans and machines results in actionable information.

The Lego Blocks will be modern spreadsheets, hooked together with logic rather than layout oriented artifacts like rows, columns, and cells. Modern approaches to building accounting and auditing workpapers will be used.

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

Graph Hairball

Image
Knowledge graph system logic, the "things" and "relations between things" that  graph theory calls "vertices" (a.k.a. nodes, points, entities, things) and "edges" (a.k.a.  links, lines, relations, associations), looks like a big graph hairball as some people call it an example of which you can see here: Why?  This common view of a graph is because there has to be some "general view" of the information provided by the graph.  This is just like a general view of the information within a relational database is a table ; a set of ROWS and COLUMNS for exactly one table at a time. So what is interesting is that with a graph database the default view is everything in the graph of knowledge.  Whereas the default view of everything in a relational database is one table at a time. Further, it does not really matter whether the information that populates your knowledge graph comes from, say, CSV files, Excel, JSON, XBRL, RDF, PROLOG or whateve
Read more

PLATINUM Business Use Cases, Test Cases, Conformance Suite

Image
A brick wall is made of exactly two things: bricks, mortar. But a brick wall created by a master craftsman, or mason, and a brick wall created by a “weekend warrior” with no knowledge of masonry will be very different. Master craftsmen are created and that process takes time and effort. This blog post is a first prototype that brings several things together into one useful resource for business professionals.  It pulls together the human readable information of the Showcase of Reports   and the machine readable information of the Conformance Suite of XBRL-based Financial Reports Prepared using the Seattle Method .  Then, I want to incorporate the information found in these PLATINUM XBRL-based Financial Report Examples . The three resources can be useful and used independently; but they are even more useful when used together.  Business professionals really could not care a less about the technical details of getting some result that they want.  But technical professionals need to under
Read more