HERM describes what the institution runs. Other disciplines add layers on top of that same spine — cost, value, risk — each answering a question the core model raises but doesn't settle. This section collects them.
Every extension attaches to the same HERM spine and answers one question the core model raises. One estate, many lenses.
Tap any layer for a quick summary, or open its full page.
"What does it cost, and is it worth it?"
Adds a cost-and-value layer to the estate — pairing each capability with what it costs to run and deliver, in language the CFO and board already use.
Read it →"How well does it run, and where does it break?"
Adds a performance layer to the workflow maps — cycle time, waste, and defects per step — so a process becomes a measured candidate for improvement.
Read it →"What does this actually feel like for the person?"
Adds the experience layer to the lifecycles — what a constituent thinks, feels, and struggles with at each step, beyond which systems they touch.
Read it →"How do we run these as services, day to day?"
Adds the operational layer — service catalog, incidents, changes, and configuration — so the mapped estate is run with discipline once it is live.
Read it →"What service can I get, and who is it for?"
Adds a customer-facing service taxonomy — a shared, product-agnostic way to name and group IT services across higher ed.
Read it →"How well is each system defended?"
Adds a security-posture layer that maps straight onto the classification and criticality already on every record.
Read it →"Is this data accurate, defined, and trusted?"
Deepens the data model — stewardship, quality, lineage, and master data beneath each source-of-record.
Read it →"Who decides what IT does, and how?"
The governance capstone — directs and monitors IT against institutional goals, and filters which frameworks to adopt.
Read it →