Versions Compared

Version Old Version 5 New Version 6
Changes made by

damian.hickey

damian.hickey

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

...

These are maintained within the metamodel and visualised within Orthogramic Insights to support exploration and navigation.

Relationship type list

Icon

Relationship Type

Description

Funds node with data.png

funds

Finance provides financial resources to another domain entity to enable its development, operation, or enhancement.

Quantifies node with data.png

quantifies

Finance expresses the activities, outputs, or outcomes of another domain entity in measurable financial terms.

Reports on node with data.png

reports_on

Finance produces formal reports capturing the financial performance, costs, or returns associated with another domain entity.

Forecasts node with data.png

forecasts

Finance projects future financial needs, costs, or revenues associated with another domain entity.

Organization node with data (14).png

supported

One domain entity receives necessary resources, services, or capabilities from another domain entity to deliver its intended outputs or outcomes.

Constrains node with data.png

constrains

One domain entity imposes limitations, standards, or compliance requirements on another domain entity’s design, operation, or evolution.

Enables node with data.png

enables

One domain entity is essential for the successful implementation, operationalisation, or fulfilment of another domain entity.

Mitigates node with data.png

mitigates

One domain entity actively reduces the risks or vulnerabilities associated with another domain entity.

Monitors node with data.png

monitors

One domain entity oversees, measures, or evaluates the performance or effectiveness of another domain entity.

Organization node with data (15).png

governing

One domain entity defines policies, standards, or decision rights that control the operation of another domain entity.

Drives demand for node with data.png

drives_demand

One domain entity generates, influences, or amplifies the demand for another domain entity’s outputs, services, or capabilities.

Responds to node with data.png

responds_to

One domain entity is triggered, adapted, or activated in response to changes in another domain entity or external event.

Organization node with data (12).png

consuming

One domain entity uses, relies upon, or draws from the resources, outputs, or services of another domain entity.

Aligns_with node with data.png

aligns_with

One domain entity is intentionally coordinated or harmonised with another domain entity in purpose, direction, or design without establishing a direct dependency.

Oversee node.png

oversee

For systematic traceability of oversight responsibilities.

Accountable to node.png

accountable_to

For a clear line of responsibility between entities

...

  • Show how elements from different domains relate visually

  • Allow users to follow logical chains from Strategy through to Initiatives and Performance

  • Enable dynamic exploration of organisational alignment

...

Orthogramic uses cross domain relationships to:

  • Identify capability gaps blocking strategic goals

  • Recommend services or stakeholders needed for an initiative

  • Highlight policies or information dependencies that require attention

Info

Difference from inter-domain relationships

Cross domain relationships describe the conceptual and operational connections between different types of elements across domains (e.g. a Strategy influencing a Capability). They are structural to the metamodel and are not confined to any particular organisational unit.

By contrast, inter-domain relationships focus on how these cross-domain connections manifest across different organisational units—for instance, how a Capability in one unit depends on a Service or Initiative governed by another. Inter-unit domain relationships are thus a subset of cross domain relationships, contextualised to show organisational span, dependency, and potential silos

...

Extensibility

New relationship types can be added over time as the metamodel evolves. User feedback and document analysis are both sources for suggesting and validating additional relationship types

.

Related pages