Higher Ed Enterprise Model Conceptual model Search
Core systems / Childcare functions & features

Childcare functions & features

Features of childcare products (Procare, Brightwheel), mapped to HERM capabilities. The platform runs waitlists and enrollment, child records, check-in and pickup, ratios and staffing, daily reports, incidents, tuition and licensing. The SIS and HR keep parent status, the ERP keeps financial posting, and children’s health records stay with the family. See also student health, campus recreation and HR.

Why map to HERM

Shows which parts of the institution a childcare platform 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

23 HERM capabilities touched, centred on childcare management and accounts receivable (tuition and subsidies), plus compliance (licensing and ratios), communications, health and safety, incident management, identity and access, payroll, reporting and privacy.

Three ways in

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.

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

Which HERM capability each function supports

Browse the HERM Business Reference Model →

{{ xwIntro }}

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

Childcare hierarchy
HERM capability
Definition
{{ tr.hermNote }}
{{ tr.def }}

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.

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 }}