CAUDIT Higher Education Reference Models

HERM — a shared blueprint for the whole institution

HERM is a set of vendor-neutral reference models that give every university a common vocabulary for what it does, the data it holds, the applications it runs, and the technology beneath them. Because the models are shared across the sector, systems can be classified consistently and compared institution to institution.

v3.2.0
released 18 Dec 2025
5
models in the set
2016
maintained since
CC BY-NC-SA
4.0 open licence

Curated by CAUDIT with EDUCAUSE / Itana, UCISA, and EUNIS. The five models below stack from strategy at the top to technology at the base — the four reference models each ground one architecture layer of the system catalog.

BMC
Business Model Canvas · strategy & context
BRM →
Business · 185 capabilities
DRM →
Data · 18 topics · 80 entities
ARM →
Application · 126 components
TRM →
Technology · 8 domains · 136 components

BMC

Business Model Canvas Strategy & context

A one-page view of how the institution creates and delivers value — its constituents, value propositions, channels, activities, and cost and revenue logic. The canvas sets the strategic context that the four reference models below make concrete. It ships as an explainer and a poster; it is not a classification dimension for the catalog.

BRM

Business Reference Model Business layer

A hierarchical map of business capabilities — what the institution does, independent of the systems that do it. It is organised into two core value chains plus a set of enabling capabilities. Capabilities stay stable as applications change, which makes them the backbone for planning, investment, and gap analysis.

29
level-1 capabilities
185
capabilities in total
2 + 1
core value chains + enabling
Learning & Teaching — core value chain
Curriculum ManagementStudent RecruitmentStudent AdmissionStudent EnrolmentCurriculum DeliveryStudent AssessmentCompletion ManagementStudent ManagementStudent Support
Research — core value chain
Research Opportunities & PlanningResearch FundingResearch AssuranceResearch ManagementResearch ActivityResearch Dissemination
Enabling capabilities — shared across the institution
Strategy ManagementBusiness Capability ManagementGovernance, Risk & ComplianceLibrary ManagementAdvancement ManagementMarketing ManagementEngagement & Relationship ManagementLegal AffairsICT ManagementHuman Resource ManagementFinancial ManagementInformation ManagementFacilities & Estate ManagementAuxiliary Capabilities
Explore the BRM hierarchy → See the catalog by capability →

DRM

Data Reference Model Data layer

The subject areas the institution holds data about and the entities inside them. Topics are grouped into Core (aligned to core capabilities), Enabling (supporting functions), and Foundation (shared building blocks used everywhere). It answers where each fact lives and who is its authoritative source of record.

18
data topics
80
data entities
3
topic types
Core topics
CurriculumStudent ManagementLearning & TeachingResearch
Enabling topics
Planning & PerformanceGovernance & RiskLegal & ComplianceService & OperationFinanceAssetHuman ResourceEstateAdvancement
Foundation topics
IndividualRoleGroupLocationTime

Local extension: our 4-level data classification crosswalks onto these topics to power the sensitivity view.

Explore the DRM map → See the catalog by data →

ARM

Application Reference Model Application layer

A catalog of application component types — the kinds of systems a university runs, grouped into three domains that mirror the business value chains. It gives every system a consistent "what kind of thing is this" label, so functional overlaps between products become visible.

3
application domains
21
application capabilities
126
application components
Application domains
Learning & TeachingResearchEnabling
Explore the ARM map → See the catalog by system →

TRM

Technology Reference Model Technology layer

The technology domains that host and run the estate — from end-user computing down to infrastructure, security, and operations. Paired with the local criticality extension, it drives the recovery-tier view: what must come back first when something fails.

8
technology domains
136
technology components
End-User Computing
tools and services people use to interact with systems
Communication & Collaboration
information exchange and joint work between people
Digital Identity
identification, authentication, access, and lifecycle
Data & Information
storing and managing structured and unstructured data
Software Delivery & Execution
creating, deploying, and running digital solutions
Infrastructure
compute, storage, networking, and platform services
Cybersecurity
protecting systems, networks, programs, and assets
Technology Operation
administration and observation across the whole stack
Explore the TRM map → See the catalog by criticality →