====== 6. The SIP-RA Architectural Separation ======

[[public:00-sip-ra:99-annexes:annex-d-pitch-deck:05-islands-of-automation|◀ Previous]] | [[public:00-sip-ra:99-annexes:annex-d-pitch-deck:start|Top]] | [[public:00-sip-ra:99-annexes:annex-d-pitch-deck:07-high-level-architectural-context|Next ▶]]

----

===== Five Architectural Concerns =====

  * **Data** — the values, observations, and assertions being processed
  * **Structure** — how Data is organized, identified, related, and constrained
  * **Semantics** — what the Data and structural elements mean within a defined context
  * **Interpretation** — the rules, calculations, classifications, and reasoning applied to the Data
  * **Governance** — the Authority to define, approve, change, and apply the other concerns

===== Why Separation Matters =====

  * Each concern can be governed and versioned independently
  * Relationships among the concerns remain explicit and traceable
  * Changes can be evaluated before they affect operational outcomes
  * Different technologies can implement the same governed models
  * Independently governed Domains can cooperate without surrendering Authority

===== Two Related Flows =====

  * **Operational information flow** carries Data among participating Systems
  * **Governance control** manages the Structures, Semantics, rules, Policies, and Authorities applied to that Data

<WRAP centeralign>

**NOTE: SIP-RA makes the relationships explicit without requiring a single implementation, platform, or governing Authority.**

</WRAP>

<WRAP centeralign>
| 13 September 2026 | Page: 6 |
</WRAP>

----

[[public:00-sip-ra:99-annexes:annex-d-pitch-deck:05-islands-of-automation|◀ Previous]] | [[public:00-sip-ra:99-annexes:annex-d-pitch-deck:start|Top]] | [[public:00-sip-ra:99-annexes:annex-d-pitch-deck:07-high-level-architectural-context|Next ▶]]

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>