The functions and features most commonly offered by student mobile app platforms (Ellucian Experience, PeopleSoft Campus Mobile, Workday Student mobile, Modo Campus, Ready Education and Anthology Student), and the HERM business capability each one supports. A mobile app is a channel, not a system of record: it shows and acts on data that the SIS, finance, aid, LMS and campus systems keep. That is why it touches so many capabilities and owns so few records. See also the SIS, financial ERP, HRM and research administration functions & features, and the ESU Go prototype. See the HERM Business Reference Model for the full set of capabilities, or its capability wheel.
Shows which parts of the institution a student app 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.
22 HERM capabilities touched across student management, curriculum delivery, support, facilities, communications and ICT, because one front door serves almost every office.
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 student mobile app platforms. 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.
A student app sits on top of many systems. 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 }}