Two layers that sit beside capabilities and applications. An org unit is accountable for HERM capabilities and is the business owner of applications. A service is what a student, faculty member, staff member or researcher actually asks for; it is delivered by one unit, exercises one capability and runs on applications. Every playbook, journey and workflow can reuse them.
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.
{{ unitCount }} Pick a unit to see its capabilities, applications and services.
{{ svcCount }}
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 }}