Higher Ed Enterprise Model Conceptual model Search
Overview / Org units & services

Who owns what: org units and the services they run

Two layers beside capabilities and applications. An org unit is accountable for capabilities and owns applications. A service is what someone actually asks for: delivered by one unit, exercising one capability, running on applications. Playbooks, journeys and workflows reuse both.

Illustrative only. The divisions, units and services here are examples for a fictional institution. Every campus organizes differently, so replace them with your own structure; the pattern of linking units to capabilities, applications and services is what carries over.

Where do units overlap? Find redundant capabilities →

{{ unitCount }} Pick a unit to see its capabilities, applications and services.

{{ sel.div }}
{{ sel.name }}
{{ sel.sum }}
Accountable for
{{ c.code }} {{ c.name }}
None recorded.
Business owner of
{{ a }}
No applications. In ecosystems: {{ sel.sys }}
Services delivered
{{ s.name }} · {{ s.who }}
No services recorded.

{{ d.name }}

{{ d.count }}
For
Division

{{ svcCount }}

{{ s.name }}
{{ s.unit }}
{{ s.desc }}
{{ s.herm }}
{{ s.meta }}

Each row is a HERM level-1 capability; each cell names the units in that division accountable for it or one of its children. Rows with no accountable unit are gaps to settle before any project that touches them. {{ ownSum }}

Capability
{{ h.name }}
{{ r.code }} {{ r.name }}{{ r.flag }}
{{ c.txt }}
Decision rights

Owning a service is not the same as deciding its future

Units own and run services day to day. Changing, replacing or retiring one usually needs others to agree. Decision rights record who decides, who must agree and who is consulted for each kind of change.

See decision rights →