Information patterns
Pattern C – Employee, manager and cost center
Shows how an employee and manager connect to a cost center and to each other.
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 employmentDecide organisation and delegation
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.
Business rules that apply to this pattern
- Appropriate number of employees per managerVR-ORG-001 · Conditional rule
- One employment in the organizationVR-ORG-002 · Cardinality rule
- The manager's business responsibilityVR-ORG-003 · Responsibility rule
- The employee is employed by their managerVR-ORG-006 · Mandatory rule
- A manager must have a manager codeVR-ORG-008 · Value rule
- Occupation, position and occupation grouping are kept apartVR-ORG-009 · Value rule
- A process role is not a positionVR-ORG-010 · Value rule
- Not a consultant and an employee at the same timeVR-ORG-011 · Uniqueness rule
- All staff have a position – an engagement type is not a positionVR-ORG-012 · Value rule
- A manager must be an employeeVR-ORG-013 · Value rule