A workflow is the path a task takes end to end — crossing several capabilities and touching more than one system. Each step names the capability it exercises and the systems that carry it. Click any workflow for its full sequence.
These are process maps at the level leadership needs: each step tied to a capability, a system, and an owner. Detailed swimlane or BPMN diagrams of how an office does a step can sit underneath each one, and link back here.
Not the whole catalog of processes — a starter set, one for each way a workflow cuts across the estate. Between them they cover every journey and the shared IT and identity work. A seed to grow, not a fixed list.
Read left to right: the task moves step by step. Read top to bottom: each step exercises a capability, uses software functions, and touches one or more systems. No single system owns the whole flow, which is why it has to be mapped. Pick a workflow; tap any capability or function for detail.
{{ dg.caption }} Solid chips are systems of record; dashed chips sit outside the four core systems. Open {{ dg.name }} in full →
{{ capPop.desc }}
A function is something the software does to support a capability. Capabilities say what the institution does; functions say how software helps; applications are what this campus actually runs.
{{ detail.summary }}