The functions and features most commonly offered by student housing and residence life systems (StarRez, Adirondack The Housing Director and RMS Mercury), and the HERM business capability each one supports. The system covers the resident’s path from housing application to move-out: room and bed inventory and rates, applications and eligibility, assignments and roommates, contracts and the charge feed, move-in, room condition and occupancy, incidents, work orders, programming and desk services, conference housing, resident and staff self-service, and integration, security and operations. The SIS remains the system of record for student identity and enrollment status and the ERP for financial posting. The student mobile app is a channel, not the record for housing operations.
Shows which parts of the institution the housing system supports, where it overlaps other systems, and where it stops.
A function's main HERM home vs others it touches. Features narrow to one capability.
32 HERM capabilities touched, centred on housing and accommodation, student liability and integration. Most features sit in Enabling capabilities.
Wheel to explore, tree to scan every mapping, CSV or JSON to reuse it.
How this was compiled: three AI assistants (Claude, Perplexity and Grok) were each asked to identify the core functions and features of the major higher education housing and residence life platforms. Their lists were reconciled into this single set, using the Claude draft’s structure; source letters on each feature show which drafts named it. Treat it as a starting point, not a vendor-verified specification.
{{ xwIntro }}
The full hierarchy: areas, functional areas, functions and features, each with its HERM mapping and definition. Select any HERM capability or feature to see its full definition.
Housing is rarely one system. Here the same functions and features are mapped to the applications a fictional Example State University actually runs: a vendor core, add-on modules, third-party products, homegrown tools and spreadsheets. Each link records how well the application covers the feature and its role. HERM coverage is then calculated from those links, not mapped by hand.
Also see this ecosystem as a capability × application matrix or a HERM-to-application flow.
Inner rings: area and functional area. Outer ring: one slice per feature, split into bands when more than one application provides it. Marks outside the ring flag gaps (red) and competing systems of record (violet).
{{ fd.desc }}
The executive view. Each bar is the capability’s features, coloured by the best coverage any application gives them. Select a capability for its HERM definition, or an application to see its footprint.
{{ pop.body }}