Capabilities say what the institution does. Workflows show the steps of one piece of work. Process architecture is the structure between them: which processes exist, how they nest, where they hand off, and who owns each one.
Process architecture is the high-level blueprint of an institution’s processes. It lists the major end-to-end processes, arranges them in a hierarchy, and records how they connect to each other, to capabilities, and to the people who own them.
It is not process mapping. A process map or BPMN diagram describes how one process runs, step by step. Process architecture sits above those diagrams and shows how they fit together.
The Business layer already holds capabilities and workflows. Process architecture is the piece that links them.
Stable functions from the HERM BRM, delivered by people, process, information and technology.
The landscape of processes, their hierarchy, hand-offs and owners, aligned to capabilities and lifecycles.
Ordered steps and hand-offs for a specific piece of work, each tied to a capability and a system.
Most process architectures use four levels. The HERM value chains supply the top level, and the workflows on this site sit at the bottom. The APQC Process Classification Framework is a common reference for the middle two.
An end-to-end flow of value to a constituent. Lifecycles export as value streams.
A family of related processes with one accountable owner.
A repeatable process with a clear start, end and output.
The ordered steps, systems and hand-offs. Detailed BPMN sits below this.
The major end-to-end processes, such as the student lifecycle, hire to retire, and grant award to closeout.
Value streams broken into process groups, processes and workflows, so every diagram has a place.
Where work crosses a team, office or system boundary, and what passes across.
A named owner per process, decision rights, standards, and how changes are approved.
Links to capabilities, measures, enabling systems and the data topics each process uses.
Without it, institutions collect process diagrams that never add up. Each office improves its own piece, and the end-to-end flow a student or researcher experiences gets worse at the seams.
A process architecture gives leaders one map for spotting gaps and overlaps, assigning owners, and deciding what to standardize, improve or automate. It also matters for AI: an agent can only act safely on a process that is explicit, bounded and owned.
It pairs with two extensions already on this site. Lean Six Sigma measures how well each process runs. COBIT governs the IT processes that support them.
Start with one value stream, such as Learning & Teaching. List its process groups, name an owner for each, and attach the workflows you have already mapped. The groups with no workflow and the hand-offs with no owner are your first gaps.
Process architecture is not part of HERM v3.2.0. This page describes it as a local extension of the Business layer; the hierarchy and owners are for each institution to define.