LensReading which lens this session carries.

Standard operating procedure · EN1B · Engineering

Capacity Rebalance

Analytical procedure owned by Portfolio & Intake in Engineering. 4 numbered steps, 1 of them a person deciding and 3 of them agent work …

Procedure code

EN1B

Analytical

Rule versions in force

v5.6 · v1.0 · v3.5 · v3.8

4 governing rules stacked over it

In force since

2024-12-18

Earliest effective date across those rules

Last reviewed

2026-07-20

Latest review date across those rules

Rules approved by

1

VP Engineering Operations

Rule health

4/4

0 under review · 0 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run capacity rebalance to one repeatable standard inside Portfolio & Intake, part of Engineering.

Entry condition

Runs analytical. Starts when a leader asks the question.

Exit condition

The unit clears leader review, released by VP Engineering Operations.

In scope

  • Every unit of capacity rebalance raised inside Portfolio & Intake, from the trigger below through to the final step.
  • 3 of the 4 steps, which run without a person present.
  • 1 decision that stops the line until a named person releases it.

Out of scope

  • Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
  • Work that belongs to another function. This line records no handoff, so nothing leaves it mid-flow.
  • Shared-spine work. This line has none; every step is done inside the function.

Who owns it

Runs the line

Engineering Intake Orchestrator

Accountable person

VP Engineering Operations

The end of the escalation path. Above them sits Engineering Chief of Staff for the function.

That team’s remit

Owns request work end to end inside Engineering.

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

67% now · ceiling 74%

Triage, estimation and dependency mapping are agentic.

The procedure, step by step

4 numbered steps · 1 of them stop for a person

A step is one station on the line.

No.StepWho does itWhat happensSystem of recordTime on the stepIn flight
01

Model demand

Agentworkflow

Request Triage Agent

Request Triage Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Configuration Management Database13.9 hrsstandard 18.7 hrs8
02

Model capacity

Agentworkflow

Effort Estimation Agent

Effort Estimation Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Materials and Inventory2.7 hrsstandard 3.8 hrs3
03

Draft recommendation

Agentworkflow

Dependency Mapping Agent

Dependency Mapping Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Product Lifecycle Management10.8 hrsstandard 16.4 hrs38
04

Leader review

HumanpolicyDecision

VP Engineering Operations

Releases: VP Engineering Operations

Work stops. VP Engineering Operations reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the request decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Materials and Inventory20.7 hrsstandard 32.4 hrs5

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine.

Person1 station and 43% of the dwellAgent3 stations and 57% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Configuration Management Database
Group ERP — Materials and Inventory
Product Lifecycle Management
Group ERP — Materials and Inventory
Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it.

speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/4
the happy path, worked time0 min of 2.0 days
the same run against its allowance0 min of 3.0 days
Human
decides · 1
Agent
does the work · 3
GBS
shared spine · 0
run log

Nothing has happened yet.

where the worked time goes2.0 days a unit
Person21 hrs · 43%Agent28 hrs · 57%1 crossing between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 4 stations stop for a person and every one of them still does on this run.
  • Every one of the 1 decision is still taken by the person who holds it. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 74% autonomy ceiling and this run sits at 57% unattended, inside it.
  • 3 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
what would have to change

One decision, held by VP Engineering Operations.

stays with a person
  • 04 Leader review — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
what this run is, and what it is not

This is a run, not a forecast.

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations.

The second clock is the allowance.

A decision may be handed to the agent lane only if two things hold …

The run reads the station rows only.

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything.

Run it again, going wrong

The same unit, the same stations, broken the way the estate already records breaking

This is the same unit on the same stations, breaking.

No break below was chosen.

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

4 stations, nothing waiting, nothing sent back

0 min of 2.0 days

now Model demand · Request Triage Agent · 14 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 2.1 days

now Model demand · Request Triage Agent · 14 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

2 counted categories land on this procedure.

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen.

Two clocks run. Worked time is the sum of the time the work is actually being done …

Roles and responsibilities

5 named parties

The responsibility grid is assigned by a rule, not lifted from a chart.

PartyRACIStepsDutyEscalates to

Engineering Intake Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to VP Engineering Operations when a unit falls outside the envelope or confidence drops below the floor.

Request Triage Agent

agent

A4% autonomy · ceiling A4%

97% clean · 9% overridden

Responsible1Executes the corporate services step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Corporate Services when the unit falls outside the decision envelope or confidence drops below the floor.

Effort Estimation Agent

agent

A3% autonomy · ceiling A3%

94% clean · 6% overridden

Responsible1Executes the portfolio & intake step it owns, posts its evidence, and hands the unit to the next stage.Escalates to VP Engineering Operations when the unit falls outside the decision envelope or confidence drops below the floor.

Dependency Mapping Agent

agent

A2% autonomy · ceiling A2%

91% clean · 2% overridden

Responsible1Executes the business continuity step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Business Continuity when the unit falls outside the decision envelope or confidence drops below the floor.

VP Engineering Operations

person

Accountable and responsible1Holds 1 decision on this line. Accountable to VP Engineering Operations for the decisions held here.

Decision points and escalation

1 places this procedure stops

04 · Leader review

20.7 hrs

Held for a named human when the unit exceeds the request decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

VP Engineering Operations

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Portfolio & Intake.

The rules this procedure runs inside

4 governing rules

Portfolio & Intake Decision Envelope

active

EN1-POL-200 · envelope · vv5.6

Agents in this lane may act without a human when the request sits inside the stated value, risk and confidence envelope.

Approved by VP Engineering Operations · in force 2025-04-08 · reviewed 2026-07-20

Binds Request Triage Agent, Effort Estimation Agent, Dependency Mapping Agent, Capacity Modeling Agent, Value Scoring Agent

APAC

Portfolio & Intake Evidence Standard

active

EN1-POL-201 · evidence · vv1.0

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path.

Approved by VP Engineering Operations · in force 2025-05-22 · reviewed 2026-05-18

Binds Request Triage Agent, Effort Estimation Agent, Dependency Mapping Agent, Capacity Modeling Agent, Value Scoring Agent

Global · EU

Portfolio & Intake Escalation Rule

active

EN1-POL-202 · escalation · vv3.5

Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires.

Approved by VP Engineering Operations · in force 2025-08-17 · reviewed 2026-07-11

Binds Request Triage Agent, Effort Estimation Agent, Dependency Mapping Agent, Capacity Modeling Agent, Value Scoring Agent

EU · UK · US

Portfolio & Intake Autonomy Ceiling

active

EN1-POL-203 · ceiling · vv3.8

The ceiling for this lane is 74 on the platform scale.

Approved by VP Engineering Operations · in force 2024-12-18 · reviewed 2026-07-01

Binds Request Triage Agent, Effort Estimation Agent, Dependency Mapping Agent, Capacity Modeling Agent, Value Scoring Agent

APAC

Systems this procedure touches

3 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Group ERP — Materials and InventorySAP S/4HANA MMsupplyhigh2modeled
Configuration Management DatabaseServiceNow CMDBitsmhigh1modeled
Product Lifecycle ManagementSiemens Teamcenterengineeringhigh1modeled

0 of the 3 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 1 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

2.0 days

Summed from the time each step sits, standard 3.0 days — running at 68% of the standard.

Touchless

47%

Agent share

75%

A week

73

In flight

54

Effort a week

1,243 human minutes · 1,650 agent minutes

Volume multiplied by the time on each step.

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level …

GateWhat trips itWho releases itClockWaivable

Production release authorization

approval

Any deployment to a production environmentRelease manager and service owner1 business dayNo

Security-sensitive or public API change

approval

Authentication, cryptography, payment paths or any published interface contractSenior engineer and security engineer1 business dayNo

Database migration

approval

Any schema change or irreversible data operationData owner and CTO delegate2 business daysNo

Agent-authored code sample review

oversight

Weekly review of 10% of agent-authored merged changesEngineering governanceWeeklyYes

Next to it on the same team

Portfolio & Intake

All of Engineering

What this document is and is not

These procedures describe the modeled estate.

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings.

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from.

Current distribution

2,748 steps

Agent, inside the function1,38951%
Agent, on the shared spine85131%
Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date.