/
Back

Pattern domains

Process

Patterns for how the organisation's processes are structured in levels and how employees, through process roles, get the mandate to do the work and permissions in applications.

Information building blocks

The individual information objects used to build the domain's patterns.

Process

A business process in a hierarchy of levels: process category, process area, process and sub-process. Process roles are linked only to the lowest level.

Examples: Manage payroll, Recruit employee, Handle supplier invoices

Process role

An assignment to perform defined tasks in a process at the lowest level. Held by the employee – not a title, not a position and not a node in the organisation tree.

Examples: payroll approver, case worker, reviewer, application owner, safety representative

Business goal

A decided goal with its own identity, validity period, indicator and target value. The goal is assigned to an organisational unit and responsibility follows the unit's manager code. Strategic goals on the top unit are inherited by all units; tactical and operational goals link to a parent goal.

Examples: No avoidable care injuries (strategic), Standardised medication reconciliation (tactical), Reconciliation before discharge in every case (operational)

Formal competence

A requirement for a licence, authorisation, certification or other competence issued by an external party. Set by a process role and acts as a block: the role may not be exercised without validated competence.

Examples: physician licence, nursing licence, teacher certification, driving licence category, certification

Functional competence

Practical skill in an occupation, method or system required by a process role. Every position has a position competence with the same name as the position. Used for gap analysis and development, not as a block.

Examples: position competence Nurse, triage method, medical records system, procurement methodology

Relationships

The visual language that shows how the building blocks connect.

Part of process

A process is part of a parent process or a process area.

Holds process role

An employee holds zero or more process roles, and a process role can be held by many employees. Assignment can be automatic (employment, manager code), a default from the position or a delegation.

Activates process role

An active manager code automatically activates manager roles for the own unit.

Offers process role

The unit's role assortment: the process roles the unit's mission requires and that the manager can assign to employees.

Performed in process

A process role is performed in one or more processes at the lowest process level.

Grants permission

A process role grants permissions in applications, approved by the application owner.

Contributes to goal

A tactical or operational goal contributes to exactly one parent goal – an inherited strategic goal or a tactical goal higher up in the line.

Assigned to unit

A business goal is assigned to exactly one organisational unit. Strategic goals on the top unit are inherited by all units below it.

Owned by manager

Goal responsibility rests with the holder of the unit's active manager code, not a named person.

Realised in process

The goal is reached through work in one or more processes; the indicator is often measured on the process outcome.

Requires formal competence

A process role requires zero or more formal competences. Without validated competence the role may not be exercised.

Requires functional competence

A process role requires zero or more functional competences. Basis for gap analysis and development talks.

Information patterns

Meaningful combinations of building blocks and relationships.

0..*0..*10..*1..*0..*0..*1..*0..*0..*0..*0..*11..*EmployeeManagerUnitProcess roleProcess (lowest level)Access rightApplication

Pattern G – Process role, employee and process

Shows how employees get process roles and how the roles act in processes at the lowest level and grant permissions in applications. Roles arise automatically through employment and manager code at the top level and through the position in the unit. The manager selects other roles from the unit's role assortment or delegates. The role provides the applications the work requires. The engagement type can block roles.

EmployeeManagerUnitProcess roleProcess (lowest level)Access rightApplication

Employee with a manager code. Manager is not a separate information object. The red ring marks an Employee with a manager code, and the relationships state which unit, cost center or employees the person manages.

0..*10..*10..*10..*10..*10..*1..*Top unitSubordinate unitStrategic goalTactical/operational goalManagerProcess (lowest level)

Pattern H – Goal cascade and goal inheritance through the organisation tree

Strategic goals are set on the top unit and automatically inherited by all units. Managers mandated to set tactical or operational goals link them to a parent goal. Responsibility follows the manager code, and results are aggregated upwards along the same tree. With parallel trees the inheritance splits and responsibility becomes unclear.

Top unitSubordinate unitStrategic goalTactical/operational goalManagerProcess (lowest level)

Employee with a manager code. Manager is not a separate information object. The red ring marks an Employee with a manager code, and the relationships state which unit, cost center or employees the person manages.

0..*0..*0..*1..*0..*0..*0..*0..*EmployeeProcess roleProcess (lowest level)Formal competenceFunctional competence

Pattern I – Competence requirements via process role

Shows how competence requirements are set by process roles in processes at the lowest level. The position only carries its position competence; other requirements arise through the roles. What the employee actually has is retrieved through integration or established in development talks and compared with the requirements. Measurement is in FTE via the employment rate.

EmployeeProcess roleProcess (lowest level)Formal competenceFunctional competence