Higher Ed Enterprise Model Conceptual model Search
Core systems / Disability resources functions & features / Ecosystem views

Disability resources ecosystem: matrix and flow

Two more ways to read the application map behind the ecosystem wheel. The matrix lines every feature up against every application, so gaps and competing systems of record stand out. The flow traces each link from HERM capability, through the Disability functional area, to the application that delivers it.

Sample data: Example State University is a fictional campus with 15 applications. Every count here is calculated from its application-to-feature links.

Rows
Show
Coverage {{ k.l }}
Role System of record Contributes Reads only
{{ focus.name }} {{ focus.meta }}
{{ focus.sum }}
{{ rowHead }} Click an application to focus on it
Status
{{ c.n }}
{{ g.sum }}
{{ r.id }} {{ r.name }} {{ r.sub }}
{{ r.tag }}
Nothing matches this filter.

Shaded group rows count how many of the group’s features each application touches; the darker the cell, the larger its share. In the HERM view each row is a capability, and its cells show the best coverage and strongest role any of the capability’s features has in that application.

Colour by
Reads-only links
{{ k.l }}
Showing only flows through {{ flowFocus.name }} · {{ flowFocus.sum }}
{{ sankey }}

Band width is the number of feature-to-application links. A feature delivered by two applications flows twice; a feature with no application flows to No application, so gaps carry weight instead of disappearing. Click any bar to isolate the flows that pass through it.

Cost of workarounds

20 features here are done by hand, in spreadsheets or by email. At 60 staff hours a year each and $55 an hour, that is about $66k a year of staff time that no invoice shows. All twenty ecosystems →