/
Process

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.

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

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.

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.

SourceLevelProcess roleProcess (lowest level)ApplicationsAssignmentRequires employment
Engagement type: employedTop levelTime and payroll self-reporterManage pay, time and compensationHR system, Web browserAutomaticYes
Top levelEmployee in development talkPlan strategic talent supplyHR systemAutomaticYes
Top levelEmployee in rehabilitationManage the work environment systematically–AutomaticYes
Top levelEmployee in work environment activitiesManage the work environment systematically–AutomaticYes
Manager codeTop levelPayroll and time approverManage pay, time and compensationHR systemAutomaticYes
Top levelDevelopment talk leadPlan strategic talent supplyHR systemAutomaticYes
Top levelRehabilitation lead (manager)Manage the work environment systematicallyHR systemAutomaticYes
Top levelWork environment lead (manager)Manage the work environment systematically–AutomaticYes
Top levelRecruiting managerRecruit employeeHR systemAutomaticYes
Position in the unitUnitCase workerAssess individual and family supportField work mobile app, Population registerAutomaticYes
UnitReviewerOngoing accounting and appropriation settlementFinance clientAutomaticNo
Unit role assortmentUnitMethod supportPlan strategic talent supply–Manager's choiceNo
UnitCoordinatorCoordinate internships and study placements–Manager's choiceNo
Delegation from managerUnitApprover (delegated, with amount limit)Manage procured purchases and supplier invoicesFinance clientDelegatedYes
UnitOrderer under agreementCall off external resources and services–DelegatedNo
UnitApplication ownerManage application assignment–DelegatedNo
UnitSafety representativeManage union co-determination–DelegatedYes

The table is an example. Each organisation sets its own roles and mappings.