Business layer · Workflows

How work flows across capabilities and systems

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.

{{ count }}
workflows
{{ stepTotal }}
steps mapped
cross-cutting
each spans multiple systems
Why these six

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.

The idea

One workflow threads across many capabilities and many systems

Read left to right: the task moves step by step. Read top to bottom: each step exercises one capability and touches one or more systems. No single system owns the whole flow — which is exactly why it has to be mapped.

WF01 Example — Student onboarding
The workflow →
1
Offer accepted
→
2
Identity created
→
3
Course registration
→
4
Tuition set up
→
5
LMS access
Capability it exercises
Student Admission
Identity & Access Management
Student Enrolment
Student Liability Management
Curriculum Delivery
Systems it touches
Slate
OktaActive Directory
Banner SIS
TouchNet
Canvas LMS

Five steps · five capabilities · six systems — and not one system spans the whole workflow. Open any card below for its full sequence.

No workflows match “{{ query }}”.

Workflows are a local extension of the HERM Business layer. Steps reference HERM Business Reference Model capabilities and representative systems from the catalog.

{{ detail.code }} · Workflow

{{ detail.name }}

{{ detail.journey }} {{ detail.sysCountLabel }}

{{ detail.summary }}

{{ st.num }}
{{ st.label }}
{{ st.capability }}
{{ sy }}
Open the systems catalog →