Model-driven Enterprise Architecture

Often, when you are deeply immersed inside a system you cannot see the problems of that system. The system I am talking about is "the enterprise".  

By enterprise I mean any economic entity, entity, business, business entity, commercial venture, undertaking, firm, industrial organization, company; small, medium, and large that is organized and has some purpose or "mission" or "mandate".  Could be a for profit business, a not-for-profit organization, a government agency.

The "problem" was less of a problem until artificial intelligence came along.  But artificial intelligence is exposing  the "problem".  And, it is less of a problem and more of an inability to take advantage of an important opportunity.

What causes the inability to take advantage, the real advantage, of  artificial intelligence is messy data.  The AI Ladder points this out:

"AI is one of the greatest challenges and opportunities of our time. It is poised to change the way people work, how enterprises operate, and how entire industries transform."

And yet, 81% of business leaders don't understand the data and infrastructure required for taking advantage of artificial intelligence.

But some leaders do understand what is necessary.  One of those leaders is Object Management Group (OMG) which has been building out that infrastructure for years and years.

To harness the power of artificial intelligence, we need to give artificial intelligence a chance to succeed.  Step 1 is to separate the information artificial intelligence will need to succeed from the "costume" that information wears called the document. We need to "think beyond the document". We need to think more about the model.

We need to move to a model-driven enterprise architecture. We need to explain the enterprise digitally. Some people call this a "digital twin". Some refer to this as the "enterprise knowledge graph".

Lots of work to create something like this? You bet.  But what about the upside?

To move away from fragile, craft-based information management and traditional electronic spreadsheets; modern enterprise architecture should rely on open, standardized, modular, and machine-interpretable frameworks.  And OMG has those frameworks.  ISO has others. XBRL International has yet others. Even the Department of Defense has others.

By unifying the Object Management Group’s (OMG) "Triple Crown" of business process management (BPMN, DMN, CMMN), with the "digital twin" or enterprise knowledge graph (EKG), and providing a model-driven semantic-oriented global standard artificial intelligence enabled digital reporting mechanism like Standard Business Report Model (SBRM); enterprises can build a completely model-driven digital twin.

This architecture separates human visual presentation from deterministic machine execution, ensuring absolute logical integrity and epistemic traceability. You can always take the machine interpretable graph and reliably project it as a human interpretable rendering.

Structured information has an advantage. By separating the information and the “costume” that information wears (i.e. the document); representing the information as a machine interpretable graph which a computer based process can reliably interpret (i.e. treating these graphs as semantics-oriented structures known as models); organizations eliminate the traditional "human bucket brigade"; the fragile (and costly) practice of humans manually moving text from one document to another document. Instead, the model is the "code" which enables reliable automation.

Sure, probability based machine learning like that provided by LLMs will help out.  But because LLMs are not 100% reliable 100% of the time; LLMs have limitations.  We need to use the right tool for the job.

Here are additional details so you can see what I am getting at.

The Execution Layer: The Triple Crown (BPMN, DMN, CMMN)

These three specifications, the triple crown, represent the behavior and operational logic of an enterprise. Crucially, they are both machine-interpretable and semantics-oriented.

They are not mere drawing tools; they strictly separate the visual diagram interchange metadata (shapes and coordinates) from the semantic elements (the execution logic). The underlying files are structured XML schemas that can be ingested and executed directly by compliant workflow engines without requiring developers to manually recode the diagrams into software.

This video, BPMN, DMN & BPM Engines Explained | A Beginner’s Introduction to Business Process Automation, explains.

While they share this machine-executable philosophy, each targets of each  part of the triple crown play different roles, completely distinct semantic domain of business logic:

  • BPMN (Business Process Model and Notation): prescriptive sequences, the  "recipe": maps the sequential flow of predictable, repeatable work; its structural metaphor is the assembly line, where tokens move deterministically through sequence flows and gateways.
  • DMN (Decision Model and Notation): declarative business logic, the "smart rulebook": isolates operational decisions and complex business rules entirely from the process flow; its structural metaphor is the truth table; it ingests inputs, evaluates them via FEEL (Friendly Enough Expression Language), and outputs a structural data result cleanly, keeping BPMN maps uncluttered.
  • CMMN (Case Management Model and Notation): dynamic context, deals with things that cannot be fully automated; manages unpredictable, ad-hoc, or human-driven activities dependent on evolving events; its structural metaphor is medical triage; it uses Event-Condition-Action (ECA) rules to dynamically activate tasks based on changing case contexts, stepping in where rigid BPMN flows fail.

The Semantic Foundation: Enterprise Knowledge Graphs (EKG)

If the Triple Crown standards represent the operational verbs of an enterprise, the Enterprise Knowledge Graph (EKG) provides the nouns.

Without an EKG, individual BPMN, DMN, or CMMN models operate in a data vacuum, referencing local variables without any inherent understanding of what that concept means relative to the rest of the enterprise.

An EKG uses semantic web standards (RDF, RDFS, OWL, SHACL) to build a unified web of meaning across disconnected siloes. When integrated, the XML metadata of the Triple Crown models points directly to the persistent Uniform Resource Identifiers (URIs) of concepts defined inside the EKG ontology.

DMN Input Mapping: DMN decision tables query graph nodes dynamically. If a regulatory definition or a product class changes inside the graph, the DMN logic processes it automatically without requiring a redesign of the model.

CMMN Event Triggers: The CMMN engine monitors the graph. If a new node or relationship is populated anywhere in the enterprise graph, the engine instantly detects the contextual shift and flags a task for an auditor or case manager.

BPMN Data Lineage: When a process executes a task, it alters data. Writing these changes back to the EKG creates an immutable record of provenance—capturing exactly which process step modified which attribute under what operational context.

The Output Layer: Standard Business Report Model (SBRM)

The Standard Business Report Model (SBRM) completes this lifecycle. It serves as the logical blueprint for information exchange and structured reporting, governing how data is packaged and validated when it leaves the enterprise or moves between business units.

Historically, financial and business reporting relied on presentation-centric tools (like PDFs or complex electronic spreadsheets) that are prone to high error rates and difficult for machines to interpret. SBRM provides a platform independent model that formalizes the logical conceptualization of a business report; defining components like reporting envelopes, report structures, and document components using OWL and SHACL.

SBRM ensures that the data generated by the Triple Crown and housed within the EKG adheres to rigid structural and mathematical constraints (e.g., enforcing that Assets must equal Liabilities + Equity). Because it is entirely decoupled from physical technical syntax, an SBRM model can be bi-directionally translated without any loss of data semantics into multiple target formats, such as XBRL (eXtensible Business Reporting Language), JSON, CSV, GQL, SQL, or RDF.

Architectural Synthesis

When combined into a single, cohesive framework, these five standards eliminate the "human bucket brigade"; the fragile practice of humans manually translating ambiguous documents, diagrams, and disconnected spreadsheets into software code or regulatory filings.

This unified approach guarantees end-to-end mechanical integrity. If an auditor or regulator questions a specific fact inside an SBRM-compliant XBRL file, they can trace it cleanly backward: from the report component, through the EKG provenance path, straight to the specific DMN rule and BPMN process step that generated it. The semantic model remains unbroken; traceability and provenance are intact.

Seem impossible? It is not impossible. What exists today is not normal; it just seems normal. What exists today is a hairball.  There is a better way.



Additional Information:

Comments

Post a Comment

Popular posts from this blog

Inhabiting Babel, A Manifesto for Responsible Meaning Engineering

Image
Inhabiting Babel, A Manifesto for Responsible Meaning Engineering is a book written by Nicolas Figay . This book is very practical and easy for a motivated business professional to read. For me, this book has both tempered my expectations as to what is possible and also reassured me of the real possibilities that exist if you do the required work. Accountants and auditors tend to be on the conservative side of the spectrum.  Me included. I am  actually rather conservative in terms of what technology might bring to the table for accounting, reporting, audit, and analysis. I have learned how to "cut the cards" when dealing with sales people and software vendors. What this book does is bring the wisdom from the experiences of an expert in system interoperability, enterprise architectures, and complex systems to helps motivated business professionals and technical professionals that truly want to understand artificial intelligence, cutting through the rhetoric and hype. This boo...
Read more

Rethinking Financial Reporting: the Model-driven Financial Statement

Image
It is time to rethink the design of financial statements. Clay tablets worked well and they had a good run which ended many years ago when the clay tablets were replaced by papyrus and then ultimately paper.  Paper had a good run also but paper financial statements were ultimately replaced by what amounted to an electronic version of that paper; PDF, HTML, and such. We can do better.  Today's demands call for more modern accounting tools . Idealized design  (a.k.a. greenfield project ) is the notion of designing a system without imposing constraints of prior work.  This technique may, or may not, work for rethinking the financial statement. Idealized design might be a harder path in the short term, but taking this approach has very positive long term ramifications. Here are a number of ideas that I would throw at the wall if I were in charge of rethinking the financial statement to make such tools modern: Digital first : The first thing that I would do is abandon the...
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 pro...
Read more