/
Back

Pattern domains

Product and service

Patterns for what the organisation delivers externally, with Business service as the first building block.

Information building blocks

The individual information objects used to build the domain's patterns.

Business service

An external or internal service the own organisation provides to customers, citizens or its own units and employees.

Examples: external: compulsory school education, library, building permit assessment, home care; internal: IT workplace, payroll, legal advice

Product

A physical or digital item that is purchased, stocked, consumed or delivered.

Examples: consumables, food, medicines, medical devices, school books, software licence

Relationships

The visual language that shows how the building blocks connect.

Provides service

Shows which organisation is responsible for providing a business service.

Delivers service

Shows which unit or units deliver the business service. Because each unit has its own manager, the service can grow without making employer responsibility unclear.

Delivered at place

Links a business service to the places where it is physically provided. The relationship is optional because many services have no place of their own.

Supported by application

Shows which applications support or digitally deliver the business service.

Assigned application

The employee gets access to the application based on internal position and unit.

Approves access

The manager, derived through the manager code, approves requested access for their employees.

Bears licence cost

The cost center bears the cost of the application's licences.

Produces

The producer owns the product's specification and assigns its barcode.

Supplies

The supplier sells, invoices and delivers the product under an agreement.

Stocked at place

The product is stored or received at a physical place.

Charged to cost center

The cost of the product is charged to a cost center.

Enables service

The product is used to deliver a business service.

Introduced into item catalog

Direct link: the unit introduced the product into the item catalog and is responsible for assortment, item maintenance and lifecycle status.

Information patterns

Meaningful combinations of building blocks and relationships.

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

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

Shows how an organisation provides a business service, how one or more units deliver it, how it can be provided at several places, and how it can be supported by applications. The link to place is optional, so the same pattern works for both place-based and fully digital services.

OrganizationBusiness serviceUnitPlaceApplication
0..*0..*11..*10..*ApplicationEmployeeManagerUnitCost center

Service pattern B – Application assignment and access governance

Shows how the application catalogue and the organisation tree together govern assignment: the employee belongs to a unit, the unit's manager approves access through the manager code and the unit's cost center bears the licence cost. When someone moves or leaves, access follows the change automatically.

ApplicationEmployeeManagerUnitCost 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.

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

Product pattern A – Product, producer and supply flow

The producer (brand owner) creates the product and its barcode; the supplier sells and delivers it. The roles are kept separate even when the same organisation holds both, so a change of supplier never creates a new product. The product is stocked at a place and enables a business service. The product is directly linked to the unit that introduced it into the item catalog; the unit owns the item and is responsible for its lifecycle.

ProducerSupplierProductPlaceBusiness serviceUnit