The four ecosystem maps (SIS, Finance, HRM, Research) merged into one list of applications. Each one appears once, measured against the HERM capabilities it supports. Footprint shows where each application reaches across HERM. Lifecycle compares how much each one carries with how well it carries it, and with what the institution plans to do with it.
Sample data: Example State University is a fictional campus. Applications that appear in more than one ecosystem (Banner Finance, Okta, Ethos, spreadsheets) are counted once here.
Columns are HERM Business Reference Model capabilities, grouped by value chain. A cell counts the features this application is linked to under that capability, across every ecosystem in scope. Sole record counts features where no other application holds the record: what you would lose by switching it off.
HERM breadth is the number of distinct HERM capabilities the application holds the record for or contributes to. Fit is the average quality of those links: full counts 100%, partial 60%, planned 30%, workaround 0. The dashed lines mark the median breadth and 70% fit. An application's lifecycle plan should match its quadrant. Where it doesn’t, the cards on the right list them.