100 lines
5.6 KiB
Markdown
100 lines
5.6 KiB
Markdown
# Target Operating Model
|
|
|
|
Turns a description of a solution into a reviewed target operating model: who runs it, through which processes, with which tools, to which service levels, at what cost, and how the organisation gets there.
|
|
|
|
Accepted by the owner on 2026-10-13.
|
|
|
|
Terms of the engine this agent runs on (Execution, Phase, Approval, Deliverable, Workflow, Skill and the rest) are defined in `../orchestration_engine/CONTEXT.md` and mean the same here.
|
|
|
|
## Language
|
|
|
|
### What it starts from
|
|
|
|
**Operating spec**:
|
|
The structured statement an Execution starts from: what the customer wants from operations, the facts an operating model depends on, and the solution to be operated, as one file. It may arrive complete or partly filled, and a value it states is the customer's decision.
|
|
_Avoid_: intent file, brief, scope spec (which is the architecture agent's)
|
|
|
|
**Item**:
|
|
One thing to be operated, listed in the Operating spec: a network, a database, a pipeline. When the spec was digested from a solution architecture it is that architecture's Element, and keeps its id as a reference.
|
|
_Avoid_: Element (which is the architecture's), asset, component, resource
|
|
|
|
**Condition**:
|
|
Something that must be kept true of an Item while it is run, listed in the Operating spec: logs retained for a period, recovery within a time.
|
|
_Avoid_: Check (which is this agent's own, on its operating model), control, SLA
|
|
|
|
**Source**:
|
|
Anything a caller supplies for an Operating spec to be digested from: a solution architecture agent's files, a design document, a sentence.
|
|
_Avoid_: input, upload, baseline
|
|
|
|
### The operating model
|
|
|
|
**Target operating model**:
|
|
The operating organisation to be established, as one explicit graph of Parties, Roles, Capabilities, the Responsibilities between them, and the Checks each must meet. It is established before any process, organisation design or tooling is written in detail.
|
|
_Avoid_: TOM (in prose), blueprint, to-be state
|
|
|
|
**Business outcome**:
|
|
What the customer's business wants from the solution, in their words, such as getting new products to customers sooner. Every Measure shows one.
|
|
_Avoid_: goal, KPI (which is a Measure), objective, benefit
|
|
|
|
**Measure**:
|
|
Something measured to show a business outcome is being served, at one layer: delivery outcome, productivity guardrail, leading signal of friction, service level or cost. Taken by a Capability someone is responsible for.
|
|
_Avoid_: metric (alone), KPI, Check (which is a condition that holds or not)
|
|
|
|
**Operational requirement**:
|
|
A numbered statement of what running the solution must achieve, traced to a requirement the customer stated, a Condition, or a field of the Operating spec.
|
|
_Avoid_: NFR, service requirement
|
|
|
|
**Capability**:
|
|
Something the operating organisation must be able to do, such as manage incidents or recover from loss. It comes from the capability catalogue, names the Operational requirements it serves and the Items it covers.
|
|
_Avoid_: process (which is how a Capability is carried out), function, practice, service
|
|
|
|
**Capability catalogue**:
|
|
Our own list of Capabilities, in our own words, each citing the industry frameworks it draws on.
|
|
_Avoid_: framework, library, ITIL (which is one source)
|
|
|
|
**Party**:
|
|
An organisation with a part in operating the solution: the customer, the service provider, a supplier, the Cloud provider.
|
|
_Avoid_: team (which is inside a Party), vendor, stakeholder
|
|
|
|
**Role**:
|
|
A position in a Party, with its skills, the hours it works, and, for pricing, a country and a level.
|
|
_Avoid_: person, resource, job title
|
|
|
|
**Team**:
|
|
A group of Roles within one Party, of one of the four kinds Team Topologies names: stream-aligned, platform, enabling or complicated-subsystem. Optional: an operating model need not have teams.
|
|
_Avoid_: squad, unit, department, Party (which is the organisation the team is in)
|
|
|
|
**Interaction**:
|
|
How two Teams work together, in one of Team Topologies' three modes: collaboration, X-as-a-Service or facilitating. A collaboration is a stage with a stated end.
|
|
_Avoid_: dependency, handoff, relationship (which is the architecture's)
|
|
|
|
**Responsibility**:
|
|
A Role's part in a Capability: accountable, responsible, consulted or informed.
|
|
_Avoid_: RACI (which is a view of all of them), ownership, assignment
|
|
|
|
**Check**:
|
|
A numbered, verifiable condition that a Capability, Role or Responsibility must meet, traced to the Operational requirement it comes from. Validation gives each a verdict.
|
|
_Avoid_: Condition (which is in the spec, about an Item), control, test
|
|
|
|
**Finding**:
|
|
Something operating the solution needs that the solution, as the Operating spec describes it, does not provide. It is recorded and returned to whoever owns the design. This agent never repairs the design.
|
|
_Avoid_: gap, issue, defect, recommendation
|
|
|
|
**Scenario**:
|
|
An event the operating model must be able to handle, generated from the graph and the spec and traced through it by code: an incident on a named Item out of hours, the loss of a region.
|
|
_Avoid_: test case, use case, dry run
|
|
|
|
### Cost
|
|
|
|
**Rate card**:
|
|
The service provider's prices: a day rate by country and level, with the facts needed to turn effort into people and people into cost. It is a Skill, and only the service provider sets what is in it.
|
|
_Avoid_: price list, overlay, the customer's rates
|
|
|
|
**Staffing**:
|
|
The number of people each Role needs, computed from the effort of its Capabilities and the hours it must cover. Never written by an agent.
|
|
_Avoid_: headcount (which is a limit the customer may state), FTE count, resourcing
|
|
|
|
**Transition plan**:
|
|
The Deliverable that divides establishing the Target operating model into work packages and activities, with a computed timeline that fits the solution's build.
|
|
_Avoid_: roadmap, project plan
|