← Back to catalogue
Research draft

Operational change and on-call duty

EM-TEC-10 · em-tec-10

Change request, approval decision, window, execution, rollback and on-call schedule. Person assignment and release are delegated to their own models.

Enterprise profiles Enterprise subject EnterpriseTEC

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 4 findings · 9 questions

Change A requested operational change, its approval, windows and execution.

Request and approval

What is to change and which revision was approved.

Approved revision

The change request revision that an approval decision refers to.

  1. Which revision of the change request was approved, by whom and when?
  2. Does the release require an immediate operational change, or can it wait?

Change window

A time slot in which an approved change may run.

  1. In which windows may the change run, and in which time zone is each defined?
  2. Does a window exist without a matching approval?

Execution and rollback

What actually ran and how it can be undone.

Execution record

Each attempt with its outcome and link to the approved revision.

  1. Which approved revision did this execution apply, and with what outcome?
  2. Was the rollback plan invoked, and is its evidence recorded?
On-call duty Who is on duty and how incidents escalate.

Roster and escalation

The duty roster, handovers and escalation rules.

Duty assignment

A person on duty for a period, separate from their access rights.

  1. Who is on duty for this service and period, after the latest handover?
  2. Which escalation rule applies when the person on duty does not respond?
  3. Which access rights does the person hold, independently of being on duty?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseTEC
Industry
Cross-industry
Tags
EM-TEC-10W2subjectOperationalChangeChangeWindowChangeExecutionRollbackPlanDutyRoster

What it is Filled

Change request, approval decision, window, execution, rollback and on-call schedule. Person assignment and release are delegated to their own models.

Why it exists Filled

Change request, approval decision, window, execution, rollback and on-call schedule. Person assignment and release are delegated to their own models.

Distinguishing features Filled

  • A change window is a time slot, not a permission; only an approval decision authorises execution.
  • Every execution points to a specific approved revision, so a later edit to the request cannot rewrite what was authorised.
  • Being on duty assigns responsibility for response and grants no extra access by itself.
  • Distinct from the release record, which describes what is delivered rather than when and how it is changed in operation.

What robots and AI may and may not do Filled

Must not

  • Grant administrative rights to a person because they appear on the on-call schedule.
  • Run a change in a window without an approval for the current revision.
  • Edit an approved change request in place so that the authorised scope can no longer be traced.
  • Mark a change successful when the rollout failed and was rolled back.
  • Reassign duty without recording the handover.

Only with a human decision

  • Approving an operational change or an emergency change.
  • Granting temporary elevated access to the person on duty.
  • Deciding to proceed after a failed rollout instead of rolling back.

May

  • Check that an execution references an approved revision and a valid window.
  • Convert change windows between time zones and flag overlaps or gaps.
  • Report who is on duty for a service at a given time, including after handovers.
  • Record execution outcomes and rollback evidence.

Moral aspects Filled

  • On-call rosters affect working time, rest and pay, so they must be fair and accurately recorded.
  • Unauthorised or untraced changes can cause outages that harm customers and staff alike.

Who is affected

  • Engineers on duty
  • Service owners and approvers
  • Customers of the affected service

Owners Filled

Steward

The chief technology or information officer, or the service owner, who answers for operational changes.

Master systems

  • Software catalogue
  • Source code repository
  • CI/CD pipeline
  • Configuration management database
  • Observability platform

Links to other meta-models Filled

neighbor

  • EM-TEC-05 - Incidents trigger escalation to the on-call roster and may require emergency changes.
  • EM-TEC-04 - Changes apply to environments and service instances.
  • EM-RSK-03 - Access rights for the person on duty are governed by access and delegation records.

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • A change is identified by its change request number and revision; each execution by its own identifier.
  • A duty assignment is identified by roster, service, person and time interval.

Direct properties not applicable Not applicable

Not applicable

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

Recognition optional Filled

  • A change record names a target service, an approved revision, windows and a rollback plan.
  • Often confused with a release, a deployment pipeline run or an incident action.

Capabilities and actions required Filled

  • Executions can be traced back to the approval and revision they relied on.
  • Duty coverage can be checked for gaps across time zones and handovers.

Hazards and failure modes required Filled

  • Privilege creep when on-call membership is wired directly to administrative groups.
  • Window confusion across time zones that runs a change at the wrong local time.
  • Missing rollback evidence after a failed rollout.

Standards and interfaces required Filled

  • ISO/IEC 20000-1 from ISO and IEC for service management, including change management.
  • iCalendar, IETF RFC 5545, for windows and duty schedules.
  • ISO 8601 and the IANA time zone database for dates, times and zones.

Context of use required Filled

  • Used by operations and site reliability teams that run production services.
  • Regulated sectors often require evidence of change approval and segregation of duties.

Sources Filled

  1. AISMM/WM-SFT and ArchiMate: product, system and architecture
  2. CSDM: business application, service and runtime instance
  3. SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary

Open questions

  • When does a release not require an immediate change?
  • How to reconcile windows across time zones?
  • How to verify on-call duty when an assignment changes?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

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

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