← Back to catalogue
Published

Service and Service Model

EM-PRD-02 · em-prd-02

The service, the expected outcome, the terms of provision and consumption. The running service instance and the service level agreement are delegated.

Enterprise profiles Enterprise subject EnterprisePRD

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 4 findings · 9 questions

Service definition The service and the outcome it is expected to produce.

Service and outcome

What the service does for its consumer.

Expected outcome

The outcome the service promises to produce.

  1. Which outcome is the service expected to produce, and for which consumer?
  2. How does this service differ from a product or a process with the same name?

Terms of provision

Conditions under which the service is provided.

  1. Under which terms is the service provided, and is there a price?
  2. Can an internal service here have no price, and how is that recorded?
Consumption and dependencies Who consumes the service and what it relies on.

Consumption

The consumer as a party, not a technical client.

Consumer identity

Business consumers separated from API clients.

  1. Who is the business consumer of the service, as opposed to the technical client calling it?
  2. Is the measured outcome recorded separately from the expected one?

Implementation

Providers and implementations behind one service.

Provider binding

Several providers or implementations for one service.

  1. Which providers and implementations realise this service?
  2. Does the service record copy runtime details that belong to the running instance?
  3. Which other services does this service depend on?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterprisePRD
Industry
Cross-industry
Tags
EM-PRD-02W1subjectServiceServiceOfferingServiceConsumptionServiceDependency

What it is Filled

The service, the expected outcome, the terms of provision and consumption. The running service instance and the service level agreement are delegated.

Why it exists Filled

The service, the expected outcome, the terms of provision and consumption. The running service instance and the service level agreement are delegated.

Distinguishing features Filled

  • The service consumer is a business party, not the technical API client.
  • A service definition does not contain a copy of its runtime.
  • The expected outcome is recorded apart from the measured one.
  • Distinct from products, which are offered and priced, and from service level agreements, which are delegated.

What robots and AI may and may not do Filled

Must not

  • Declare an API endpoint to be a business service by default.
  • Treat the technical client of an API as the service consumer.
  • Copy runtime configuration into the service definition.
  • Report a measured outcome as if it were the expected one.

Only with a human decision

  • Introducing or retiring a service for consumers.
  • Changing the terms of provision for existing consumers.

May

  • Map services to their providers, implementations and dependencies.
  • Compare expected and measured outcomes per period.
  • List consumers of a service with the terms that apply.

Moral aspects Filled

  • Consumers rely on services for essential work, so unclear outcomes shift harm onto them.
  • Accountability is lost when a service has no identifiable provider.

Who is affected

  • Service consumers
  • Service providers and operators
  • Dependent teams

Owners Filled

Steward

The service owner who answers for the service definition and its outcome.

Master systems

  • Service catalogue
  • Product catalogue
  • Configuration management database

Links to other meta-models Filled

neighbor

  • EM-PRD-01
  • EM-RSK-04
  • EM-TEC-04
  • EM-TEC-05
  • EM-TEC-06

references

  • WM-ACT-004 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by a service identifier in the service catalogue, independent of any endpoint or implementation.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A record names an expected outcome, a provider, consumers and terms.
  • Often confused with an API endpoint, an application or a process.

Capabilities and actions required Filled

  • Describe internal and external services in one way.
  • Link one service to several implementations and providers.

Hazards and failure modes required Filled

  • Endpoint catalogues mistaken for service catalogues.
  • Runtime details duplicated and drifting from the live system.

Standards and interfaces required Filled

  • ISO/IEC 20000-1 service management system requirements.
  • TM Forum Information Framework (SID) for service entities.
  • ArchiMate modelling language from The Open Group for business and application services.

Context of use required Filled

  • Used in service catalogues, IT service management and shared service centres.
  • HR, finance and digital platform services can share the same description.

Sources Filled

  1. TM Forum SID: product/service/resource and commercial roles
  2. IDTA AAS: physical assets and composite descriptions
  3. Product management and engineering configuration; compare selected PLM and software practices
  4. Service - Carried over from the published world model wm-act-004-service-definition; checked live (HTTP 200) on 2026-10-09.
  5. Offer - Carried over from the published world model wm-act-004-service-definition; checked live (HTTP 200) on 2026-10-09.
  6. Reference Model for Service Oriented Architecture 1.0 - Carried over from the published world model wm-act-004-service-definition; checked live (HTTP 200) on 2026-10-09.

Open questions

  • How does a service differ from a product and a process?
  • Can an internal service have no price?
  • How is one service linked to several providers and implementations?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-prd-02/brief.json, ver-cy/world-models/card-supplements/em-prd-02.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.