Information patterns
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.
Pattern diagram
A data-driven diagram of information building blocks and their relationships.
Legend
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.
Pattern ownership
Patterns always arise as a whole in the organisation's processes. The governing process decides that the pattern is the standard; the instantiating processes create, change and end its nodes and relationships.
- Governing process (owner)
- Govern information management and architecture
- Instantiating processes
- Manage employmentPlan strategic talent supply
The whole model is owned by the process Govern information management and architecture with a mandate from top management – never by a single function such as HR, finance or IT.
How process roles arise
The role is always assigned to the employee. Employment and manager code grant roles automatically at the top level, the position grants roles automatically in the unit, and the manager selects the rest from the unit's role assortment or delegates. The role provides the applications the work requires.
| Source | Level | Process role | Process (lowest level) | Applications | Assignment | Requires employment |
|---|---|---|---|---|---|---|
| Engagement type: employed | Top level | Time and payroll self-reporter | Manage pay, time and compensation | HR system, Web browser | Automatic | Yes |
| Top level | Employee in development talk | Plan strategic talent supply | HR system | Automatic | Yes | |
| Top level | Employee in rehabilitation | Manage the work environment systematically | – | Automatic | Yes | |
| Top level | Employee in work environment activities | Manage the work environment systematically | – | Automatic | Yes | |
| Manager code | Top level | Payroll and time approver | Manage pay, time and compensation | HR system | Automatic | Yes |
| Top level | Development talk lead | Plan strategic talent supply | HR system | Automatic | Yes | |
| Top level | Rehabilitation lead (manager) | Manage the work environment systematically | HR system | Automatic | Yes | |
| Top level | Work environment lead (manager) | Manage the work environment systematically | – | Automatic | Yes | |
| Top level | Recruiting manager | Recruit employee | HR system | Automatic | Yes | |
| Position in the unit | Unit | Case worker | Assess individual and family support | Field work mobile app, Population register | Automatic | Yes |
| Unit | Reviewer | Ongoing accounting and appropriation settlement | Finance client | Automatic | No | |
| Unit role assortment | Unit | Method support | Plan strategic talent supply | – | Manager's choice | No |
| Unit | Coordinator | Coordinate internships and study placements | – | Manager's choice | No | |
| Delegation from manager | Unit | Approver (delegated, with amount limit) | Manage procured purchases and supplier invoices | Finance client | Delegated | Yes |
| Unit | Orderer under agreement | Call off external resources and services | – | Delegated | No | |
| Unit | Application owner | Manage application assignment | – | Delegated | No | |
| Unit | Safety representative | Manage union co-determination | – | Delegated | Yes |
The table is an example. Each organisation sets its own roles and mappings.
Business rules that apply to this pattern
- A process role is assigned to the employeeVR-PRC-001 · Mandatory rule
- Process roles and activities attach only to the lowest process levelVR-PRC-002 · Cardinality rule
- Process roles end with the engagementVR-PRC-003 · Conditional rule
- The engagement type can block process rolesVR-PRC-004 · Conditional rule
- Employees get base roles automaticallyVR-PRC-005 · Mandatory rule
- The manager code grants manager roles automaticallyVR-PRC-006 · Responsibility rule
- Delegation is done as a process roleVR-PRC-007 · Responsibility rule
- The position can grant process roles automaticallyVR-PRC-008 · Value rule
- Permissions are granted via process roleVR-PRC-009 · Responsibility rule
- Organisational scope of the process roleVR-PRC-010 · Conditional rule
- Process roles can be reused across multiple processesVR-PRC-014 · Cardinality rule
- Access rights are granted to accountsVR-IT-003 · Responsibility rule
- Automatic assignment at every organisational levelVR-PRC-016 · Conditional rule
- The manager selects from the unit's role assortmentVR-PRC-017 · Responsibility rule
- Automated process roles require CMMI maturity level 4 in all involved processesVR-PRC-018 · Conditional rule
- Exercise of public authority rests on the committee's delegation orderVR-PRC-015 · Conditional rule