The functions and features most commonly offered by the major research core facility and LIMS products used in higher education (iLab and Stratocore PPMS), and the HERM business capability each one supports. These are system functions, not HERM capabilities: HERM describes what an institution does; this page describes what a core facilities platform does to help it. The platform runs the core and instrument catalog, booking and service requests, training-based access, usage logging, recharge rates and billing, research sample tracking and results delivery. Proposals, awards and compliance stay in the research administration system, recharge posting stays in the ERP, HPC job scheduling and storage stay in research computing infrastructure, and clinical LIMS for patient samples is out of scope. See also the research administration and finance ERP functions & features. See the HERM Business Reference Model for the full set of capabilities, or its capability wheel.
Shows which parts of the institution a research cores 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.
24 HERM capabilities touched, centred on research resource management, research data management and research infrastructure management, plus accounts receivable, price modelling, service management, 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) were each asked to identify the core functions and features of the major research core facility and LIMS products used in higher education. Their lists were reconciled into this single set. 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.
Campus services rarely run on 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 }}