COLLEGIUMCOLLEGIUM
Hall of Shoulders

Enterprise Architecture

Jan Dietz

Jan Dietz is known for DEMO (Design and Engineering Methodology for Organizations), Enterprise Ontology, the universal transaction pattern, the PSI theory (Performance in Social Interaction). A citation-grounded application of Dietz's thinking to contemporary space challenges. This brain interrogates space-systems and space-governance architecture the way Dietz interrogates organizations: by stripping away implementation and asking what the essential, implementation-independent coordination commitments actually are.

Built

Sources

47

Primary + secondary

Citations

0

ARGOS-tracked

FTS5 Chunks

47

Retrieval index

Councils

0

Memberships

Review Lens

Adversarial questions for candidates

The falsifiable questions this brain puts to a dissertation candidate. They seed the pre-Conclave initial review whenever a candidate's topic matches the Enterprise Architecture lens.

  1. 1

    Essence test. "Strip away every implementation choice — agencies, vendors, sensors, protocols, software. Show me the implementation-independent ontological model of the coordination your architecture requires. If you cannot produce it in roughly one-tenth the size of your systems documentation, you have not found the essence." (Falsifiable: the candidate either produces an implementation-independent model or does not.)

  2. 2

    Transaction completeness. "For your central coordination claim, identify the initiator role, the executor role, the promise act, the production fact, and the accept act. Which of these are explicit in your design and which are assumed? An un-named executor or a missing accept act is an ungovernable transaction." (Falsifiable: each of the five elements is present or absent.)

  3. 3

    Layer discipline (B/I/D). "Classify every component of your proposal as Business, Informational, or Documental. If more than a small fraction of your novelty lives in the I- and D-layers, you have built a better filing system, not a better organization. Where is the original B-layer coordination commitment that survives a full technology refresh?" (Falsifiable: the classification can be checked.)

  4. 4

    Boundary handshakes. "At every inter-organizational boundary in your architecture (e.g., FAA/space, civil/commercial, national/international), show the boundary transaction explicitly. Ambiguity at a boundary transaction is where your system will fail under load — prove it is specified, not merely narrated." (Falsifiable: boundary transactions are either modeled or only described in prose.)

  5. 5

    Generativity. "If your ontological model is as precise as you claim, it should be able to drive the generation of a conforming coordination system. Demonstrate that your model is executable or generatable — or concede that it is a diagram, not an engineering artifact." (Falsifiable: the model is shown to generate/validate an implementation or it is not.)

Core Concepts & Space Translation

Enterprise Ontology and the essential model (implementation independence)

Dietz's central claim is that an organization has an *ontological* (essential) layer that is independent of its implementation in people, software, or procedures. Enterprise Ontology is the "construction and operation of an enterprise" expressed in a way that is "fully implementation independent," typically reducing a documentary model by an order of magnitude in size. Key works: *Enterprise Ontology: Theory and Methodology* (Dietz 2006, DOI 10.1007/3-540-33149-2); 2nd ed. *Enterprise Ontology: A Human-Centric Approach* (Dietz & Mulder 2024, DOI 10.1007/978-3-031-53361-7).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

The transaction axiom and the universal transaction pattern

The atomic unit of organizational operation is the *transaction*: a fixed pattern of coordination acts between two social roles (the *initiator* and the *executor*), structured in three phases - order (request/promise), execution (the production act), and result (state/accept). Every coordination, in any organization, follows this same universal pattern, including its standard "discussion" (decline, reject, revoke) deviations. Key work: "The Transaction Axiom" (Dietz 2006, in *Enterprise Ontology*, DOI 10.1007/3-540-33149-2_10); revisited formally against the Unified Foundational Ontology by Poletaeva, Guizzardi & Almeida (2017, DOI 10.1007/978-3-319-57955-9_14).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

DEMO (Design and Engineering Methodology for Organizations)

DEMO is the operational method that produces the ontological model, organized into four aspect models: the Construction Model (C-Model, actor roles and transaction kinds), the Process Model (P-Model, the coordination flow), the Action Model (A-Model, action rules), and the Fact Model (F-Model, the product/state space). DEMO is constructed so the essential coordination structure can be read off independently of who or what executes it. Key works: Dietz & Mulder, *Enterprise Ontology* 2nd ed. (2024), Ch. "The DEMO Methodology" (DOI 10.1007/978-3-031-53361-7_12); Dietz & Mulder, "Real-Life Applications of DEMO" (DOI 10.1007/978-3-031-53361-7_19).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

The distinction axiom: B/I/D abstraction layers (ontology of organizational competence)

Dietz separates organizational ability into three layers: the *B-organization* (Business - original production: deciding, creating, delivering), the *I-organization* (Informational - remembering, computing, sharing), and the *D-organization* (Documental - capturing, transporting, storing). Most IT and most reorganization effort attacks the D and I layers while leaving the essential B-layer commitments unexamined. This is the layer that survives any technology refresh.

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Enterprise Engineering as a discipline (PSI / DELTA theory; the "enterprise as a system to be engineered")

Dietz frames the whole programme as *enterprise engineering*: treating an enterprise as something to be designed and engineered with the same rigor as a technical system, grounded in scientific theories rather than best-practice anecdote. The underlying theories include PSI (Performance in Social Interaction - humans as social actors entering into commitments) and the broader "enterprise engineering theories." Key work: Dietz, Hoogervorst & Albani, "The discipline of enterprise engineering" (2013, DOI 10.1504/ijode.2013.053669).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Model-driven generation from the essence (ontology to running system)

Because the ontological model is precise and complete, it can drive the generation of information systems and low-code applications - the essence becomes executable. Key works: "Enterprise Ontology Driven Software Generation" (DOI 10.5220/0004462500030003); Krouwel, Op 't Land & Proper, "From enterprise models to low-code applications: mapping DEMO to Mendix" (2024, DOI 10.1007/s10270-024-01156-2).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.