Information patterns
Pattern B – Manager, unit and cost center
Shows how a cost center, unit and manager connect 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 employmentCall off external resources and servicesEnd employment and transition
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
- The manager's business responsibilityVR-ORG-003 · Responsibility rule
- One manager per unitVR-ORG-004 · Cardinality rule
- Units have staffVR-ORG-005 · Mandatory rule
- The manager's organizational employmentVR-ORG-007 · Conditional rule
- A manager must have a manager codeVR-ORG-008 · Value rule
- A manager must be an employeeVR-ORG-013 · Value rule
- Management is shown only by the manager code on the employmentVR-ORG-023 · Value rule
- Delegation is done as a process roleVR-PRC-007 · Responsibility rule
- Managerial position requires exclusive management workVR-ORG-028 · Value rule
- Goal responsibility follows the manager codeVR-GOL-003 · Responsibility rule