System Model Foundation

The Structural Model of Enterprise Representation

Architecture role: Representation Foundation

Canonical architecture: Enterprise Intelligence Architecture

Enterprise vocabulary: Enterprise Intelligence Architecture — Canonical Definitions

Web reconciliation: 11 September 2026 — P0-2I-A v1.0. Structural dependency views and related architectural wording clarified; published source identity and publication provenance retained.

Source baseline: ARQUA-EIA-SMF, Version 1.0, Published Date 2026; the 11 September 2026 reconciliation and former footer Last Updated date are retained as baseline history.

Further web clarification: 17 September 2026 — Representation structures, purpose-specific assembly and qualification, acceptance attribution, governed projection, semantic distinctions, technology bindings and operational evidence clarified. An at-a-glance explanation is added. The existing thirteen representation primitives, Intent Scope classification, both larger responsibility/dependency views and publication provenance are retained.

Accepted architectural clarification: 18 September 2026 — NC-01 through NC-06, Non-Collapse and Typed Relationship Constraints, incorporated following architecture falsification, follow-up and hostile testing. No new SMF primitive, architecture layer or implementation algorithm is introduced. The clarification makes explicit that stronger effects such as equivalence, membership, authority transfer and runtime reliance require governed type, scope, time, standing/authority, evidence and applicable rules; connectivity alone is insufficient.

Paper type: Arqua Architecture Paper

Status: Published

Publication state: Published

Source scope: This paper defines the representation foundation within Enterprise Intelligence Architecture. Its structural conventions support domain models and governed projections without prescribing a complete enterprise vocabulary, universal physical schema or central store. The listed primitives are Arqua architectural constructs, not a claim of an exhaustive or mathematically irreducible account of reality. Shared structural alignment does not confer institutional acceptance, publication standing, current-use qualification or execution authority.

Modern enterprises increasingly depend upon data products, semantic technologies, artificial intelligence and distributed operational platforms to understand and coordinate complex operations.

These capabilities depend upon something more fundamental: the ability to represent enterprise reality consistently.

Most organisations begin with data platforms, information models, ontologies, schemas or integration technologies. Each addresses an important concern, but none independently establishes the minimum structural foundation required for representations created by different systems and domains to participate coherently in Enterprise Intelligence.

The System Model Foundation addresses that gap.

It defines Arqua's structural representation model through which operational reality becomes consistently representable across the enterprise.

It is not a common enterprise schema.

It is not an ontology.

It is not a platform foundation.

It is not an implementation standard.

It is the enduring representational substrate beneath them.

Architectural Role in Enterprise Intelligence

The System Model Foundation defines the structural basis through which operational reality can be represented consistently within Arqua's Enterprise Intelligence Architecture.

SMF defines how relevant enterprise subjects, states, events, claims, evidence and purposes can be represented. It is not a complete enterprise dataset or a declaration of everything that exists. References to a purpose-specific projection describe a bounded representation using those structures, not extraction from a mandatory central SMF store.

Intent expresses the enterprise purpose relevant to a use. Intent Scope operationalises and bounds that purpose; it does not arise from the mere existence of a structural model. Published Enterprise Products provide governed inputs to Runtime Context Assembly.

RCA forms Candidate Operational Understanding and an Assembly Manifest, then performs Context Qualification and records its outcome in a Qualified Context Manifest. Qualified Operational Understanding results only where the assessment supports reliance for the declared use. Structural conformity, relevance and publication standing do not by themselves complete that assessment.

Responsibility distinction: SMF supplies representation structures; Intent provides purpose; Intent Scope bounds the use; RCA forms and qualifies understanding. None of those relationships authorises execution by itself.

The Architectural Question

What is the minimum common structure that independently owned systems must share before they can participate in Enterprise Intelligence?

Arqua’s position is that the answer is not a common technology, centralised data model or universal ontology.

It is a common structural model of representation within the Arqua architecture.

Such a model enables independently governed systems and data products to preserve their operational authority while participating in enterprise-wide reasoning, governance and coordination.

The Problem

Enterprise representations are usually created independently.

Operational systems represent the world according to their local responsibilities.

Data products expose structures derived from source platforms.

Enterprise models describe shared business concepts.

Ontologies establish meaning.

APIs and event streams define exchange structures.

Analytics platforms optimise representations for processing.

AI systems reason over whatever information can be assembled.

Each representation may be valid within its own context.

The difficulty emerges when the enterprise attempts to combine them.

Equivalent things may be represented differently.

Relationships may be implicit or inconsistent.

State may be separated from the events that changed it.

Authority, evidence and time may be difficult to determine.

Context must be reconstructed repeatedly.

The result is representational fragmentation.

This fragmentation cannot be solved through semantics alone, because the problem begins before shared meaning is applied.

The enterprise first requires a stable structural basis through which its reality can be represented.

The Architectural Position

Enterprise Intelligence depends upon distinct architectural responsibilities.

The following responsibility and dependency view separates structural representation, enterprise acceptance, standing records, memory, publication and runtime use. Its labelled relationships are not a deployment topology or a sequence of equivalent processing stages.

The enterprise's governance and acceptance processes confer accepted standing; the System Model Foundation does not create acceptance, authority or permission to execute. Architecture of Record records standing and boundaries; Institutional Memory preserves accepted understanding and associated history. They are distinct responsibilities, not consecutive transformations of the same asset.

Memory preservation is not a prerequisite processing stage for every Enterprise Product. A bounded memory projection may be published through governed Enterprise Product Publication; retention alone does not grant publication standing or suitability for the current intent.

Runtime Context Assembly retains both formation and Context Qualification. Its Assembly Manifest records formation; its Qualified Context Manifest records the qualification outcome and basis for reliance or withholding reliance. Qualified Operational Understanding is not an automatic result of every assembly and does not authorise execution.

Execution Admissibility Architecture governs evaluation of proposed consequence-bearing action; SCIA Runtime is its runtime reference architecture, not an additional admissibility stage. Operational execution occurs only where permitted under the applicable conditions, and outcome learning changes accepted representation through governed revision rather than silent overwrite.

Within Arqua, the System Model Foundation owns the structural representation responsibility. It defines the representation conditions used by institutional acceptance, standing recording, memory, runtime context and execution-governance responsibilities without itself performing or absorbing those responsibilities.

Representation Foundation

Defines how enterprise reality may be structurally represented.

Enterprise Information Models

Define the concepts the enterprise recognises.

Enterprise Semantics

Define what those concepts mean and how they relate.

Data Products

Expose operationally useful representations for consumption.

Technology Bindings

Encode and exchange those representations using particular platforms, languages and formats.

The System Model Foundation owns the first responsibility.

It establishes the structural foundation through which the other layers can participate coherently without collapsing them into a single model or technology.

Representation Primitives

The System Model Foundation uses a defined set of representation primitives through which enterprise reality can be structured within the Arqua model:

• Subjects
• Identities
• Boundaries
• Relationships
• States
• Events
• Contexts
• Claims
• Evidence
• Intent
• Decisions
• Outcomes
• Revisions

These primitives provide the representational source from which higher-order Enterprise Intelligence capabilities derive coherent operational understanding.

Intent

Intent represents the purpose an enterprise seeks to achieve. Within Arqua, it provides the architectural purpose for assembling, qualifying and acting upon enterprise understanding.

Intent exists independently of any technical implementation. It is a fundamental property of enterprise behaviour, not a workflow field, data attribute, platform construct or automation trigger.

Within the System Model Foundation, Intent establishes why enterprise understanding is required before Runtime Context Assembly determines what must be assembled.

Intent Scope

Intent Scope is the operational boundary derived from an Intent. It defines the minimum authoritative context required to perform a specific enterprise purpose.

Intent Scope is not a representation primitive.

It is produced from an Intent.

It operationalises purpose by specifying the bounded understanding required for that use. The requirement does not establish that sufficient understanding is already available or qualified; RCA must form and assess the candidate, retaining explicit reasons where reliance cannot be supported.

Derivation Model

Representational support: SMF supplies structures for expressing Intent, Intent Scope and related enterprise representations; it does not generate the enterprise purpose.

Purpose and inputs: Intent informs an active Intent Scope, which bounds RCA's formation and qualification. Eligible Published Enterprise Products supply the governed inputs; the source of purpose is not a registry, library or complete enterprise store.

Formation and qualification: Formation yields Candidate Operational Understanding and an Assembly Manifest. Context Qualification evaluates that candidate and records the outcome in a Qualified Context Manifest. Qualified Operational Understanding exists only where reliance is supported for the intended use. These are responsibility relationships, not a prescribed service topology or automatic successful result.

Operational Fidelity and Enterprise Interoperability

The System Model Foundation supports a central Arqua principle:

Every authoritative enterprise representation should preserve both operational fidelity and enterprise interoperability.

Operational fidelity means that a representation remains faithful to the system, process or domain from which it originates.

Enterprise interoperability means that the representation can participate coherently in broader enterprise reasoning and coordination.

These requirements are complementary.

Source-aligned products should not discard the structures that make them operationally authoritative.

Nor should operational fidelity require every consumer to interpret an isolated local model independently.

The System Model Foundation creates a controlled relationship between these concerns.

It allows operational representations to remain locally faithful while exposing sufficient structural consistency for enterprise use.

Enterprise Representation Projection and Source-Aligned Data Products

Source-aligned data products are strategically important because they preserve a governed representation of operational reality close to its authoritative source.

However, publishing a native source schema alone does not necessarily create enterprise interoperability.

The source model may remain highly specific to the originating application, technology or operational process.

Enterprise Representation Projection is the governed representation published by a Source-Aligned Data Product that preserves operational fidelity while enabling the product to participate in Enterprise Intelligence.

It is not ETL, canonical transformation, data integration or schema mapping.

It is Arqua's governed participation mechanism through which independently governed products can contribute to Enterprise Intelligence.

The System Model Foundation defines the structural representation conditions through which enterprise representations participate in Enterprise Intelligence.

Enterprise Representation Projection is the implementation pattern through which Source-Aligned Products conform to those structures.

The System Model Foundation defines the architecture.

Enterprise Representation Projection supports governed participation through operationally faithful enterprise representations. Enterprise Participation and Enterprise Product Publication retain responsibility for participation standing under the appropriate enterprise authority.

This view illustrates source-to-projection relationships, not an automatic admission or runtime pipeline. Projection and structural alignment do not establish publication standing, consumer entitlement or fitness for every purpose. Those conditions remain subject to their applicable publication, access and qualification responsibilities.

The precise form of this alignment will vary according to the domain, product and implementation environment.

The architectural responsibility remains stable:

• Preserve authoritative operational representation.
• Expose enterprise-consumable structure.
• Maintain traceability between them.
• Avoid forcing operational systems into a single enterprise schema.

Every Source-Aligned Product should preserve two complementary representations:

• Native Representation — operationally authoritative.
• Enterprise Representation — governed, traceable and suitable for Enterprise Intelligence.

Both remain representations of the same operational reality.

Native and enterprise representations are complementary governed perspectives, not necessarily two materialised copies or separate stores. Their relationship must preserve source scope, meaning, version and provenance; a faithful source view is not automatically a complete or accepted enterprise-wide account.

Enterprise Representation Projection does not replace the Source-Aligned Product. It publishes an enterprise representation while preserving operational fidelity.

Relationship to Enterprise Intelligence

Enterprise Representation Projection exists to enable enterprise participation.

Enterprise interoperability is one consequence.

Enterprise Intelligence is the objective.

Participation includes:

• semantic reasoning;
• enterprise knowledge;
• Runtime Context Assembly;
• Institutional Memory;
• AI;
• governance;
• enterprise interoperability; and
• Execution Admissibility.

The purpose is participation rather than integration.

Knowledge graphs are not the governing representation model.

Knowledge graphs consume Enterprise Representation Projections and provide semantic reasoning.

The projection preserves operational fidelity.

The graph provides enterprise reasoning.

Fabric, warehouses, lakehouses, APIs, semantic technologies and AI are implementation environments or consumers. They should not become the owners of enterprise representation.

Where Microsoft Fabric is used, Fabric may execute Enterprise Representation Projections, but enterprise representation belongs to the Source-Aligned Product. Fabric consumes and serves those representations.

Separation from Semantics

The System Model Foundation is not a semantic model.

It does not define the complete vocabulary of the enterprise.

It does not determine the business meaning of every concept.

It does not replace domain ontologies, enterprise information models or semantic governance.

Instead, it establishes the structural conditions through which those models can be expressed, related and governed consistently.

The distinction is fundamental.

An enterprise information model may define the concepts the institution recognises.

An ontology may establish their meaning and logical relationships.

The System Model Foundation establishes the common representational basis through which those concepts can be identified, related, changed, evidenced and governed across systems.

Representation and semantics therefore remain separate but complementary architectural responsibilities.

Shared structural terms have declared meanings within the representational model. Distinguishing SMF from enterprise business semantics does not make those terms semantically empty or eliminate domain interpretation. Cross-domain equivalence, mappings and any ambiguity or information loss must remain explicit; matching a label or field shape alone does not establish equivalent meaning.

Technology Independence

Enterprise Intelligence should not depend upon a particular representation technology.

Implementation approaches will continue to evolve.

Representations may be encoded through document structures, relational models, graph models, event contracts, semantic standards or other technologies.

The System Model Foundation precedes those choices.

Technologies and formats are bindings through which the architectural model may be implemented.

They are not the architecture itself.

Each concrete encoding or exchange binding needs an explicit account of which structural and semantic distinctions it preserves and which it cannot express. Use of a named technology or standard is not evidence of SMF or standards conformance; that requires a separately defined profile and relevant checks.

This separation allows an institution to modernise platforms, change integration patterns and adopt new AI capabilities without repeatedly redefining the underlying structures through which enterprise reality is represented.

Technology evolves.

The constitutional representation model endures.

Constitutional Responsibility

The System Model Foundation is responsible for structural consistency in enterprise representation.

It is not responsible for:

• Defining the complete enterprise vocabulary.
• Determining business meaning.
• Establishing every governance policy.
• Prescribing operational ownership.
• Replacing domain lifecycle processes.
• Selecting implementation platforms.
• Mandating a universal physical schema.

These responsibilities belong to adjacent architectural, governance and operating-model concerns.

This boundary is deliberate.

The value of the System Model Foundation comes from defining a stable representational substrate without becoming a monolithic enterprise model.

Relationship to Architecture of Record

SMF defines how operational and institutional conditions may be structurally represented. A representation can satisfy those structural conditions without possessing accepted institutional standing.

Enterprise Representation Intelligence forms and evolves representations and supports their evaluation. The appropriate enterprise governance process confers acceptance or reacceptance for a declared scope and purpose. Architecture of Record records that standing, its applicability, obligations and relevant boundaries; it does not grant acceptance through recording alone.

Architectural distinction: structural conformity supports evaluation; enterprise governance confers acceptance; AoR records accepted standing. Institutional Memory preserves accepted understanding and associated history. These responsibilities are related without forming a compulsory storage pipeline.

Relationship to Enterprise Representation Intelligence

Enterprise Representation Intelligence is the continuous institutional function through which representations of the enterprise are formed, evaluated and evolved.

The System Model Foundation provides the structural substrate through which that function operates.

The distinction is between foundation and function.

The System Model Foundation defines the constitutional conditions of representation.

Enterprise Representation Intelligence continuously applies institutional capability to create and maintain representations within those conditions.

Relationship to Institutional Memory

Institutional Memory preserves accepted enterprise understanding over time.

For that memory to remain usable across platforms, organisational boundaries and technology changes, the representations it contains require structural continuity.

The System Model Foundation provides that continuity.

It enables institutional representations to retain identity, provenance, relationships, temporal relevance and institutional context without depending upon the originating application remaining permanently available.

Relationship to Runtime Context Assembly

Runtime Context Assembly receives an active Intent Scope derived from Intent, forms Candidate Operational Understanding from eligible Published Enterprise Products and qualifies it for the declared purpose. Qualification evidence and any supported Qualified Operational Understanding are distinct from the formation result; neither authorises execution.

Its effectiveness depends upon whether representations from different systems can be combined without excessive interpretation and transformation.

The System Model Foundation reduces this burden by establishing common structural expectations across enterprise representations.

It does not eliminate domain translation or semantic reasoning.

It provides a stable basis upon which those activities can occur.

Relationship to Enterprise Control and Execution

Enterprise controls cannot reliably evaluate information that lacks structural clarity.

Continuity and admissibility evaluations use governed representations and evidence. Operational systems and interfaces realise the applicable controls; a successful structural check does not prove that a control was implemented or operated. Evidence of current state, applicable authority and actual enforcement remains necessary for the relevant assessment.

Before an institution can determine whether an action is authorised, compliant, evidenced or admissible, it must be able to determine what is being represented, where it originated, how it changed and under whose authority it is being used.

Within Arqua, those representations must satisfy the structural representation conditions defined by the System Model Foundation.

The System Model Foundation supports the Enterprise Control Plane by making identity, state, authority, evidence, time and structural relationships governable at the representational layer.

It supports controlled enterprise execution by defining what may be represented before meaning, governance or execution are applied.

Relationship to Execution Admissibility Architecture

Execution Admissibility Architecture does not create institutional understanding.

It evaluates whether an irreversible action may legitimately bind the institution.

That evaluation depends upon representations that already possess:

• Identity.
• State.
• Authority.
• Evidence.
• Decision history.
• Temporal validity.
• Structural relationships.

These are structural representation concerns within Arqua.

They must be established before admissibility logic can evaluate whether a proposed action is authorised, evidenced, timely, contextually valid and institutionally accountable.

The System Model Foundation defines these structural representation conditions without becoming a semantic architecture or technology architecture.

It defines the representational substrate upon which execution admissibility can reason.

The System Model Foundation provides the structural representation foundation used by Execution Admissibility Architecture. Structural consistency alone does not establish that a proposed action is admissible.

Strategic Significance

The System Model Foundation enables an enterprise to establish structural coherence without forcing every operational domain onto the same platform or physical schema.

It provides a durable architectural basis for:

• Source-aligned data products.
• Enterprise semantic interoperability.
• Distributed institutional memory.
• Runtime context assembly.
• AI-ready enterprise representation.
• Cross-domain reasoning.
• Governed enterprise coordination.
• Execution admissibility.

Its strategic value lies in separating what must remain stable from what must remain free to evolve.

Operational systems may evolve.

Data platforms may change.

Semantic models may deepen.

AI capabilities may advance.

Control mechanisms may become more automated and consequential.

Within Arqua, the institution uses a consistent structural basis through which its reality can be represented.

Execution Admissibility cannot determine whether an action is permissible unless the enterprise can first represent identity, authority, evidence, state, relationships and time consistently.

The System Model Foundation defines these structural representation conditions.

Execution Admissibility reasons over them.

This is why the System Model Foundation is not simply a data model, canonical schema, semantic architecture or technology architecture.

It is Arqua's structural representational substrate and the representation foundation used by Enterprise Representation Intelligence.

A Foundation for Enterprise Intelligence

The System Model Foundation occupies a distinct position within the Arqua architecture portfolio.

It is neither semantic nor technological.

It is the structural representation foundation within Arqua's Enterprise Intelligence Architecture.

It defines what may be represented before meaning, governance or execution are applied.

These are shared structural dependencies, not a stack in which each capability is created by the preceding one. The System Model Foundation does not contain or assume the responsibilities listed here. Architecture of Record is not an acceptance engine, Institutional Memory is not runtime context, and the Enterprise Control Plane is not a sequential processing stage.

Enterprise Representation Intelligence depends upon the System Model Foundation to define the structural conditions of representation.

Institutional Memory depends upon representational continuity.

Runtime Context Assembly depends upon structurally coherent representations that can be assembled for a decision, interaction or action.

The Enterprise Control Plane depends upon institutional representations that can be evaluated for authority, evidence, state and context.

Execution Admissibility Architecture depends upon those controlled representations before it can determine whether an irreversible action may legitimately bind the institution.

Before an institution can preserve understanding, assemble context, evaluate governance or determine whether an irreversible action may bind, it must first establish how operational reality is represented.

Source-aligned products preserve operational fidelity and remain authoritative representations of operational systems.

The System Model Foundation enables those products to participate coherently in Enterprise Intelligence without requiring a canonical enterprise schema.

Enterprise Representation Projection supports that governed participation without turning the product into a canonical enterprise model; participation standing and suitability for a particular use remain separately established.

The System Model Foundation defines those structural representation conditions.

It provides the representational substrate upon which Enterprise Representation Intelligence, Institutional Memory, Runtime Context Assembly, the Enterprise Control Plane and Execution Admissibility Architecture all depend.

Non-Collapse and Typed Relationship Constraints

SMF distinguishes the existence of a connection from the stronger architectural effects that a connection may support. A relationship, mapping, projection or graph path does not acquire stronger meaning merely through existence or transitive closure. Effects such as equivalence, boundary membership, authority transfer, accepted standing or runtime reliance require the applicable relationship type, scope, time, authority or standing, evidence and governing rules to support that effect.

The following constraints apply:

• NC-01 — Typed relationship non-collapse. An arbitrary relationship does not establish shared boundary membership or identity. A governed relationship may establish membership, containment or identity only where its declared type carries that meaning for the applicable scope and time.
• NC-02 — Mapping non-equivalence. A mapping or successful conversion does not by itself establish equivalence. An accepted equivalence mapping may establish purpose-bounded equivalence where its concepts, direction, versions, scope, purpose, limitations and conditions support it.
• NC-03 — Projection non-transfer. Projection does not transfer source authority, ownership, endorsement or accepted standing. Delegation or authority transfer requires independently evidenced authority with applicable scope and conditions.
• NC-04 — Connectivity non-membership. A graph path or transitive connection does not by itself establish membership in another represented boundary. Connectivity may establish shared component membership only where the governing relation and its closure are explicitly defined to have that effect.
• NC-05 — Temporal membership persistence. Membership valid at one time is not automatically timeless. It may persist under its declared persistence semantics until effective expiry, supersession, invalidation, revision or a boundary-changing event, while historical membership remains preservable.
• NC-06 — Runtime reliance non-transfer. Qualification or reliance established for one Intent Scope does not automatically transfer to another. Prior qualification evidence may be reused only where the second assessment establishes continuing applicability of requirements, scope, versions, temporal conditions, permitted use and consequence sensitivity.

These constraints introduce no new SMF primitive or architecture layer. They clarify how existing structural primitives may participate without collapsing identity, meaning, boundary, authority, standing or runtime responsibility. Runtime Context Assembly remains responsible for intent-scoped formation and qualification; execution permission remains separate under Execution Admissibility Architecture.

Implementation note: DSU / Union-Find and connected-components algorithms are not Arqua constructs. They may be used where a governed relation explicitly has membership/equivalence semantics and valid transitive closure for the applicable scope and time. Arbitrary enterprise graph edges, semantic mappings, projections, evidence links, authority links or contextual associations must not be treated as union operations merely because they are connected.

Read This Paper If

This paper is relevant to leaders and practitioners working in:

• Enterprise architecture.
• Data architecture.
• Semantic architecture.
• AI architecture.
• Data product strategy.
• Domain architecture.
• Information governance.
• Enterprise risk and control.

It is particularly relevant where independently governed platforms and domains must participate in enterprise-wide intelligence without surrendering their operational authority.

Architecture Paper Status

This page introduces the public architectural position of the System Model Foundation.

Detailed representational structures, alignment methods, governance mechanisms and implementation patterns remain part of Arqua’s protected architecture and advisory practice.

Architectural Relationships

Representational inputs: Operational Reality and Source-Aligned Data Products.

Representational outputs: Enterprise Representations that are structurally consistent and traceable; enterprise acceptance, publication and runtime qualification remain separate requirements for their intended use.

Architectural concern: Structural coherence.

Current related architecture: Enterprise Intelligence Architecture, Enterprise Representation Intelligence, Institutional Memory, Runtime Context Assembly, The Enterprise Control Plane, Execution Admissibility Architecture and Architecture of Record (AoR).

Request a Briefing

Begin with one high-consequence enterprise decision.

Identify the operational representations, authority, evidence and context required to support it.

Then determine where structural inconsistency currently prevents the enterprise from reasoning or acting with confidence.

Request an Arqua architecture briefing.

Document ID: ARQUA-EIA-SMF

Version: 1.0

Status: Published

Published Date: 2026

Last Updated: 18 September 2026

Author: Mark Tovey

Owner: Arqua Pty Ltd

Portfolio: Enterprise Intelligence Architecture

Architecture role: Representation Foundation

Architectural responsibility: Define how enterprise reality may be structurally represented

© 2025–Present Arqua Pty Ltd. All rights reserved.

The System Model Foundation defines representation primitives within Arqua's architecture. Architectural capabilities and applied patterns use those structural conditions while retaining their separate responsibilities. Intent provides purpose, Intent Scope operationalises that purpose, and Runtime Context Assembly forms and qualifies bounded operational understanding. Structural representation does not itself confer institutional acceptance, preserve memory or authorise execution.

This publication forms part of the Arqua Enterprise Intelligence Architecture portfolio.

No part of this publication may be reproduced, redistributed, adapted, republished or incorporated into derivative works without the prior written permission of Arqua Pty Ltd, except for brief quotations used with appropriate attribution.

The concepts, architectural models, constitutional frameworks, terminology and diagrams presented on this page constitute original intellectual property developed by Arqua Pty Ltd.