Features of dining products (CBORD, Atrium, Transact), mapped to HERM capabilities. The platform runs meal plans and balances, access and point of sale, mobile ordering, menus and allergens, production and catering. The SIS keeps student identity, housing feeds the meal plan, and financial posting and procurement stay in the ERP. See also housing, campus recreation and finance ERP.
Shows which parts of the institution a dining platform 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.
30 HERM capabilities touched, centred on retail management, membership management (meal plans) and event management (catering), plus health and safety, accounts receivable, procurement, reporting and security.
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) drafted lists, reconciled into one set. 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.
Campus services rarely run on one system. Here the features are mapped to the applications fictional Example State University runs, from vendor core to spreadsheets. Each link records coverage and role; HERM coverage is calculated from the links.
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 }}