Organisations & Services (ORG)

Layer ORG of Public Framework Modelling Language 1.0 answers the question “What does the institution offer, and to whom?”. This page describes the layer's concepts, how they relate, and its 30 element types.

Describes specification v1.0

What the layer describes

The ORG layer answers the question “What does the institution offer, and to whom?”. It describes public organisations (PublicOrganisation), their services (PublicService), whom these are for and through which steps they are delivered. The software that supports services belongs to APP.

Concepts and how they relate

The organisational participants are the public organisation, the organisation unit (OrganisationUnit), the external organisation (ExternalOrganisation) and the target group (TargetGroup). A governance body (GovernanceBody) is made up of such participants, which it names in a field. A participant or a role (Role) is assigned to a procedure (Procedure) or a public service, through the “is assigned to” relationship (assignment).

A procedure contains the organisational steps. Where needed, it realises the public service through the “realises” relationship (realisation). A procedure may also realise a capability (Capability), that is, an ability independent of how it is implemented. The steps of the procedure are drawn, where needed, on its detail diagram with the BPMN tools. These tools are available on the detail diagrams of elements in ORG, APP and CNT.

A life event (LifeEvent) creates the need for services; where needed, it aggregates the matching public services through the “aggregates” relationship (aggregation). The “serves” relationship (serving) links a service channel (ServiceChannel) or a service to the target group it is meant for. Where needed, a procedure accesses the service evidence (ServiceEvidence) and the service output (ServiceOutput) through the “accesses” relationship (access).

Optionally, the service also links to the other layers through the relationships below. It shows its basis, a legal resource (LegalResource), through the “has legal basis” relationship (legalBasis). A procedure accesses a dataset (Dataset), and a software system (SoftwareSystem) serves the service. A disruption scenario (DisruptionScenario) affects the service through the “affects” relationship (affects). The service, channel or procedure then falls back to a fallback procedure (FallbackProcedure) or to another channel, through the “falls back to” relationship (fallsBackTo).

Element types

The layer has 30 element types, in these families: structure (8), service (3), behaviour (6), access (3), information (4), event (2), intent (3), decision (1). Each type's own fields are listed under its definition; the fields common to every element are described under the core concepts.

PublicOrganisationPublic organisation · structure family
A public body that owns responsibilities and delivers public services.
Key attributes: classificationidentifier
OrganisationUnitOrganisation unit · structure family
An internal organisational unit with defined responsibilities.
Key attributes: parentActor
ExternalOrganisationExternal organisation · structure family
An organisation outside the modelled public body.
Key attributes: kind
GovernanceBodyGovernance body · structure family
A body responsible for oversight, direction or architecture decisions.
Key attributes: kindmeetingCadencebodyTypecompositiongovernscompetencejurisdictionadopts
RoleRole · structure family
A named responsibility that can be performed by an organisation or participant.
Key attributes: versionstatuslifecycleStatesourceReferenceisAccountableForperformsstewards
CapabilityCapability · service family
An ability required to achieve an organisational outcome, independent of its implementation.
Key attributes: maturityversionstatuslifecycleStatesourceReferencebusinessValue
PublicServicePublic service · service family
A service delivered to people or organisations to meet a public need.
Key attributes: identifierprocessingTimecostAmountcostCurrencylanguagesstatusthematicAreaversionbusinessStatuslifecycleStatesourceReferencevaluePropositioncommitsTorealisesdelivers
ServiceChannelService channel · access family
A way a person or organisation accesses a public service.
Key attributes: channelTypeavailabilityurl
LifeEventLife event · event family
A situation in a person's life that creates needs for public services.
Key attributes: kind
TargetGroupTarget group · structure family
A group for whom a public service is intended.
Key attributes: kindestimatedSize
EligibilityCriterionEligibility criterion · intent family
A condition used to determine entitlement to a service or outcome.
Key attributes: criterionText
ServiceEvidenceService evidence · information family
Evidence requested or considered when delivering a public service.
Key attributes: evidenceType
ServiceOutputService output · information family
A result or document delivered by a public service.
Key attributes: outputType
ProcedureProcedure · behaviour family
The organisational steps followed to deliver a service or fulfil a responsibility.
Key attributes: triggerstatutoryDeadlineversionstatuslifecycleStatesourceReferencecontributesTorealisesconsistsOfproduces
BusinessActivityBusiness activity · behaviour family
A unit of organisational work within a process or procedure.
Key attributes: versionstatuslifecycleStatesourceReferenceworkInstructions
BusinessCollaborationBusiness collaboration · structure family
A grouping of participants working together on shared behaviour.
Key attributes: memberspurposeperforms
BusinessContractBusiness contract · information family
An agreement defining rights and commitments around a service.
Key attributes: versionstatuslifecycleStatesourceReferencetermsvalidFromvalidTobindsgoverns
BusinessDecisionBusiness decision · decision family
A choice made within organisational behaviour.
Key attributes: versionstatuslifecycleStatesourceReferencequestionoutcomesapplies
BusinessEventBusiness event · event family
An occurrence that starts or changes organisational behaviour.
Key attributes: versionstatuslifecycleStatesourceReferenceeventDescriptiontriggers
BusinessFunctionBusiness function · behaviour family
A grouping of organisational behaviour by responsibility or purpose.
Key attributes: versionstatuslifecycleStatesourceReferencerealisesgroups
BusinessInteractionBusiness interaction · behaviour family
Behaviour carried out jointly by multiple participants.
Key attributes: versionstatuslifecycleStatesourceReferenceinteractionPurpose
BusinessRuleBusiness rule · intent family
A rule governing an organisational decision or behaviour.
Key attributes: versionstatuslifecycleStatesourceReferenceruleStatementconstrainsderivesFrom
ServiceCatalogueService catalogue · information family
An organised collection of available service offerings.
Key attributes: versionstatuslifecycleStatesourceReferencelists
ServiceLevelService level · intent family
A measurable commitment associated with a service or offering.
Key attributes: versionstatuslifecycleStatesourceReferencetargetunitmeasurementWindowmeasuredBy
ServiceOfferingService offering · service family
A packaged way of obtaining a service under defined terms.
Key attributes: versionstatuslifecycleStatesourceReferencetargetAudienceincludes
ValueStageValue stage · behaviour family
A stage that contributes a defined increment of value.
Key attributes: versionstatuslifecycleStatesourceReferenceentryCriteriaexitCriteriavalueStreamprecedes
ValueStreamValue stream · behaviour family
A sequence of value-creating stages leading to an outcome.
Key attributes: versionstatuslifecycleStatesourceReferencevaluePropositionconsistsOf
ActorGroupActor group · structure family
A group of participants considered together for modelling responsibilities.
Key attributes: memberspurpose
ProcessInterfaceProcess interface · access family
An access point to an organisational process or procedure.
Key attributes: regionhorizonProfiledirectioncontractboundary1boundary2
ServiceInterfaceService interface · access family
An interface through which an organisational service is offered.
Key attributes: regionhorizonProfiledirectioncontractboundary1boundary2providesAccessTo

In the “Family support benefit” example

Figure 4.3 (page 25) shows the ORG layer in the example, with six elements of its own and five neighbours. The public organisation “Social benefits agency” is assigned to the procedure “Assess benefit application”. The procedure realises the public service “Family support benefit” and accesses the dataset “Benefit case records”, from INF.

The service has the law “Family support law”, from LEG, as its legal basis. The software system “Benefits case platform”, from APP, serves the service. The disruption scenario “Portal unavailable”, from CNT, affects the service, and the service falls back to the fallback procedure “Assisted paper intake”.

The governance body “Policy board”, the role “Case platform owner” and the channel “Public benefit portal” have no relationships. Their links are fields: the body is made up of the agency, and the role is responsible for the platform and the dataset. The service's detail diagram, “Eligibility decision detail”, is not shown in the figure. It contains the eligibility criterion (EligibilityCriterion) “Eligibility evidence check”.