Higher Ed Enterprise Model Conceptual model
Core systems / Conduct & Title IX functions & features

Conduct & Title IX functions & features

The functions and features most commonly offered by the major higher education case management products for student conduct and Title IX (Maxient, Symplicity Advocate and NAVEX EthicsPoint), 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 conduct and Title IX case system does to help it. The SIS stays the system of record for student identity and enrollment, HR for employee cases, and clinical systems for medical and counseling records; they appear here only as feeds and referrals. See also the SIS, housing and student advising functions & features. See the HERM Business Reference Model for the full set of capabilities, or its capability wheel.

Why map to HERM

Shows which parts of the institution a conduct and Title IX case system supports, where it overlaps other systems, and where it stops.

Falls within vs related to

A function's main HERM home vs others it touches. Features narrow to one capability.

What it shows

26 HERM capabilities touched, centred on student misconduct management and compliance, plus investigation, data management, communications and campus security.

Three ways in

Wheel to explore, tree to scan every mapping, CSV or JSON to reuse it.

How this was compiled: two AI assistants (Perplexity and Grok) were each asked to identify the core functions and features of the major higher education case management, conduct and Title IX products. Their lists were reconciled into this single set. Treat it as a starting point, not a vendor-verified specification.

Download ArchiMate
{{ wheel }}
Crosswalk to HERM v3.2.0

Which HERM capability each function supports

Browse the HERM Business Reference Model →

{{ xwIntro }}

Conduct case function
Falls within (HERM)
Also related to
{{ row.label }}
{{ row.relNote }}

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.

Conduct case hierarchy
HERM capability
Definition
{{ tr.hermNote }}
{{ tr.def }}

Conduct and Title IX case work rarely runs 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.

1 · HERM capabilityWhat the institution does. Stable, vendor-neutral.
2 · Function and featureWhat software can do. The reference list on this page.
3 · ApplicationWhat you run, with coverage and role per feature.
{{ ek.l }}
{{ ecoWheel }}

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).

What the links reveal

Conflicts, gaps and workarounds

{{ fd.n }}{{ fd.title }}

{{ fd.desc }}

Calculated HERM coverage

How well each HERM capability is served

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.

HERM capability
Feature coverage
Applications (system of record first)
{{ er.summary }}
{{ pop.kicker }}

{{ pop.title }}

{{ pop.path }}

{{ pop.body }}

{{ pop.listLabel }}
{{ li.label }}