Comparison

OCOM vs ArchiMate

Executive summary

ArchiMate is a graphical modeling language for enterprise architecture: standardized notation, layers (business, application, technology), and viewpoints designed so human architects can draw and read consistent diagrams. OCOM is not a diagramming language; it defines its own notation at the Language tier, including a graphical form, and is a specification for describing operating reality; a model built with it is the governed record, maintained as data that humans, software systems, and AI agents read the same way. ArchiMate draws the architecture for people; OCOM governs the record of what is operationally true for people, systems, and agents.

Scope

Compared

  • Whether each is a drawing notation or a governed data record
  • How each treats ownership, currency, and evidence of a statement
  • Where responsibility for accuracy lives

Not compared

  • ArchiMate's viewpoint catalog or certification scheme
  • Specific enterprise architecture tooling
  • ArchiMate's exchange format (Open Group Exchange Format)

Terminology mapping

OCOMArchiMateEquivalent
ObjectBusiness ObjectPartial
OwnershipBusiness Role / ActorPartial
CapabilityCapability (Strategy layer)Similar
PolicyRequirement / PrinciplePartial
Workflow (Models tier)Business ProcessPartial

Conceptual differences

AspectOCOMArchiMate
Centre of gravityObject-centric: what is governedViewpoint-centric: how architecture is modeled and drawn
TimeObject state over the whole lifecyclePlateaus and gaps model coarse architecture states; no per-object lifecycle
GovernanceFirst-class: ownership, policy, constraintImplied by modeled relationships, not enforced
ScopeSpans systems via a governed recordBounded to the modeled architecture view

Concept coverage

ConceptOCOMArchiMate
Architecture diagramsPartialCovered
Object identityCoveredPartial
LifecycleCoveredPartial
GovernancePartialPartial
OwnershipCoveredPartial
EvidencePartialOut of scope
AI retrievalPartialOut of scope

Four OCOM cells read Partial rather than Covered (Architecture diagrams, Governance, Evidence, AI retrieval), and the reason for each is recorded in the specification's own register: Architecture diagrams is Partial because Language/Notation.md defines a notation, including a graphical form, but states that the specification prescribes no symbol library, and no canonical Scope list says whether adopting the notation is required (AO-049); Governance is a Core Characteristic of every Object that no document defines as one (AO-023); Evidence has no Meta, Models or Language definition, its Definition being reserved for a future version (AO-021); AI retrieval is disclaimed by AI/Context/Context Assembly.md, which prescribes no retrieval algorithms (AO-048). Workflow and Event are defined normatively at the Models tier and carry no Core Vocabulary term record.

Covered: the model defines the concept explicitly. Partial: the concept appears indirectly or by convention. Out of scope: the model does not set out to describe it; a boundary, not a deficiency.

Interoperability

References