/

Definition

A Unit is a distinct part of the organisation with its own mission.

Description

Units form the structure of the organisation. A unit can have a parent unit, so hierarchies are described with a single self-referencing relationship instead of separate types for department, section and team.

Examples

sales unit, IT unit, HR unit

Identifying key

Key
Unit ID (e.g. HSA ID)
Defined by
The authoritative source of the organisation tree
Example
SE5591428890-E000000000001

Created once in the process that owns the organisation tree and kept when the unit is renamed.

The key identifies the object but is not the object. It should be stable over time and never carry meaning that can change.

Perspectives on the unit

Organisation, activity, classification, economy and responsibility are different perspectives on the same unit. They can change independently of each other without the unit's identity changing.

  • Identity

    • Unit ID
    • Name
    • Status
    • Valid from – valid to
  • Organisation

    • Parent unit
    • Child units
    • Position in the unit tree
  • Activity

    • Description of the unit's mission and activity

    The description is a business-oriented text, not a classification. Example: "The unit is responsible for primary care and offers doctor and nurse appointments for the population within its mission."

  • Classification

    • All external code lists the unit is classified according to
  • Economy

    • Cost center
    • Budget
  • Responsibility

    • Managerial assignment held by an employee

Information pattern

Employee — holds managerial assignment for

Unit

├─ is part of → Unit tree

├─ has → Description

├─ is classified with → Code value → Code list

└─ has → Cost center → Budget

Objects in the classification pattern

Classification
Unit, code list, code value, valid from, valid to, status — enabling historisation
Code value
Code, label, description, code list, parent code (for hierarchical code lists), valid from, valid to, status
Code list
Code list ID, name, description, owner, internal/external, version, valid from, valid to, source, status

Example: two independent classifications

Unit: Vårdcentral Centrum

Code listCodeLabelOwnerValidity
SKR – VI 2000 (activity classification)According to ownerPrimary careSveriges Kommuner och Regioner (SKR)Own period
Socialstyrelsen – Medical areas of activity (MVO)According to ownerGeneral medicineSocialstyrelsenOwn period

Codes are not stated here: they are retrieved from the code list owner's current version. Other internal or external code lists can be added with the same model.

The information chain organisation – responsibility – finance

The manager is never a property of the cost center or budget. Responsibility is derived through the chain below, so a change of manager does not affect the financial structure.

  1. Employee

    ↓ holds

  2. Managerial assignment

    ↓ concerns

  3. Unit

    ↓ has 1..n

  4. Cost center

    ↓ has per budget year

  5. Budget

    ↓ contains

  6. Budget line

    ↓ classified/mapped with

  7. Code value

    ↓ belongs to

  8. External financial code list
  9. Financial system → is source for → Cost center

    SKR / SCB → own → External financial code lists

Data quality

Indicators showing whether the chain holds. Every deviation breaks a business rule.

  • All units have a cost center
  • All cost centers are linked to a unit
  • All cost centers exist in the financial system
  • All current cost centers have a budget for the current budget year

Budget attributes

Budget ID, cost center, budget year, status, version, adoption date, validity, budgeted revenues, budgeted costs. Net budget is derived. Unique: cost center + budget year + version.

External financial code lists

Offers process role

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

Relationships from other areas

Unit is the shared information object that other building blocks point to – the meaning lies in the relationship.

  • AdministrationTop node of unit tree →Unit

    The administration is the top node of the units it comprises.

  • ApplicationManaged by unit →Unit

    The application is owned and managed by exactly one unit in the organisation tree. Its operating, support and base licence costs are charged to the unit's base cost center.

  • Process roleScope →Unit

    The process role applies to one or more units in the organisation tree, by default the employee's own unit, inherited downwards.

  • Business goalAssigned to unit →Unit

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

Reference data

Reference data referring to Unit.

Source Governance

Source governance describes where information should come from. Source rules are defined centrally and shown here where they concern Unit.

Source Rule

Units from the organisation register

Scope
Unit
Condition
Always
Information Source
Organisation register
Governing process (owner)
Decide organisation and delegation
Operational CRUD process
Not established – responsibility is unclear
Origin
Own organisation
Authority
Authoritative
Source Priority
1

Source Rule

Units mirrored in the HR system

Scope
Unit
Condition
Always
Information Source
HR system
Governing process (owner)
Decide organisation and delegation
Operational CRUD process
Not established – responsibility is unclear
Origin
Own organisation
Authority
Secondary
Source Priority
2

Used in information patterns

11..*Cost centerUnitEmployee

Pattern A – Employee, unit and cost center

11..*Cost centerUnitManager

Pattern B – Manager, unit and cost center

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.

UnitEmployeeManager

Pattern D – Employee, manager and unit

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.

1111..*0..*110..*0..*0..1Own organisationExternal organisationReceiving unitEmployee (engagement)Person

Pattern F – Engagement and external organisational affiliation

11..*11..*0..*0..*1..*1..*11..*10..*Municipality or regionElected representativeCommitteeAdministrationProcess roleUnit

Pattern J – Political governance: committee and administration

11..*10..*UnitCost centerBudgetManager

Economy pattern A – Budget and budget responsibility

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.

10..*0..*10..*10..*0..*0..*1..*0..*0..*0..*0..10..*10..*0..*11..*PersonEmployeeUnitDigital identityProcess roleAccess rightAccountApplication

IT pattern A – Applications and access rights

1111..*11..*10..*1..*110..*10..*11..*1111Own organisationExternal organisationOwn unitSupplier workplaceSupplierSupplier managerSupplier contact

Supplier pattern A – Supplier relationship between two organisations

11..*1..*110..*10..*OrganizationBusiness serviceUnitPlaceApplication

Service pattern A – Business service with organisation, place and IT support

0..*0..*11..*10..*ApplicationEmployeeManagerUnitCost center

Service pattern B – Application assignment and access governance

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.

10..*10..*0..*0..*ProducerSupplierProductPlaceBusiness serviceUnit

Product pattern A – Product, producer and supply flow

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

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

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.

Business rules

Lifecycle and processes

The processes in which Unit is created, changed and deactivated. Master data is never physically deleted – history is kept.

Typically involved in business processes