LensReading which lens this session carries.

Standard operating procedure · RD6B · Research & Development

Pilot Deployment

Transactional procedure owned by Prototype & Pilot in Research & Development. 6 numbered steps, 2 of them a person deciding and 4 of them agent work …

Procedure code

RD6B

Transactional

Rule versions in force

v1.5 · v3.2 · v4.9 · v4.3

4 governing rules stacked over it

In force since

2026-03-21

Earliest effective date across those rules

Last reviewed

2026-08-12

Latest review date across those rules

Rules approved by

1

Director, Product Development

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 pilot deployment to one repeatable standard inside Prototype & Pilot, part of Research & Development.

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears scale decision, released by Director, Product Development.

In scope

  • Every unit of pilot deployment raised inside Prototype & Pilot, from the trigger below through to the final step.
  • 4 of the 6 steps, which run without a person present.
  • 2 decisions that stop 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.
  • The 1 step carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

Prototype Orchestrator

Accountable person

Director, Product Development

The end of the escalation path. Above them sits R&D Chief of Staff for the function.

That team’s remit

Owns prototype work end to end inside Research & Development.

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

Autonomy

76% now · ceiling 76%

Test execution, iteration tracking and feedback synthesis are agentic.

The procedure, step by step

6 numbered steps · 2 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

Select site

Agentworkflow

Build Planning Agent

Build Planning 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 Management1.6 hrsstandard 2.7 hrs10
02

Prepare

Agentworkflow

Test Plan Agent

Test Plan 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.Research Notebook and Experiment Data26 minstandard 40 min44
03

Approve pilot

HumanpolicyDecision

Director, Product Development

Releases: Director, Product Development

Work stops. Director, Product Development 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 prototype decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Product Lifecycle Management7.3 hrsstandard 11.5 hrs6
04

Run

Agentworkflow

Pilot Site Agent

Pilot Site 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 Management2.8 hrsstandard 3.5 hrs43
05

Measure

GBSgbs

Build Planning Agent

Build Planning Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, 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 Management1.9 hrsstandard 4.3 hrs5
06

Scale decision

HumanpolicyDecision

Director, Product Development

Releases: Director, Product Development

Work stops. Director, Product Development 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 prototype decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Product Lifecycle Management57 minstandard 2.3 hrs3

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.

Person2 stations and 55% of the dwellAgent3 stations and 32% of the dwellShared spine1 station and 13% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Product Lifecycle Management
Research Notebook and Experiment Data
Product Lifecycle Management
Product Lifecycle Management
Product Lifecycle Management
Product Lifecycle Management
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/6
the happy path, worked time0 min of 15 hrs
the same run against its allowance0 min of 25 hrs
Human
decides · 2
Agent
does the work · 3
GBS
shared spine · 1
run log

Nothing has happened yet.

where the worked time goes15 hrs a unit
Person8.3 hrs · 55%Agent4.8 hrs · 32%Shared spine1.9 hrs · 13%4 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 2 of the 6 stations stop for a person and every one of them still does on this run.
  • Every one of the 2 decisions is still taken by the people who hold them. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 76% autonomy ceiling and this run sits at 45% unattended, inside it.
  • 2 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

Nothing moves. 45% of the worked time already runs unattended and the owning team is held to a 76% ceiling, so the next decision cannot be handed over until somebody raises that ceiling.

stays with a person
  • 03 Approve pilot — Handing this over would put 149% of the worked time in the unattended lane, past the 76% ceiling this team is held to.
  • 06 Scale decision — 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

6 stations, nothing waiting, nothing sent back

0 min of 15 hrs

now Select site · Build Planning Agent · 1.6 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 34 hrs

now Select site · Build Planning Agent · 1.6 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

4 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

Prototype Orchestrator

orchestrator

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

Build Planning Agent

agent

A3% autonomy · ceiling A3%

92% clean · 6% overridden

Responsible2Runs the repeatable portion of prototype & pilot inside the shared transaction spine at spine cost and spine controls.Escalates to Director, Product Development when the unit falls outside the decision envelope or confidence drops below the floor.

Test Plan Agent

agent

A3% autonomy · ceiling A3%

88% clean · 2% overridden

Responsible1Executes the prototype & pilot step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Product Development when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Product Development

person

Accountable and responsible2Holds 2 decisions on this line. Accountable to Director, Product Development for the decisions held here.

Pilot Site Agent

agent

A3% autonomy · ceiling A3%

88% clean · 5% overridden

Responsible1Runs the repeatable portion of prototype & pilot inside the shared transaction spine at spine cost and spine controls.Escalates to Director, Product Development when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

2 places this procedure stops

03 · Approve pilot

7.3 hrs

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

Director, Product Development

06 · Scale decision

57 min

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

Director, Product Development

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Prototype & Pilot.

The rules this procedure runs inside

4 governing rules

Prototype & Pilot Decision Envelope

active

RD6-POL-200 · envelope · vv1.5

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

Approved by Director, Product Development · in force 2026-05-20 · reviewed 2026-08-12

Binds Build Planning Agent, Test Plan Agent, Iteration Tracking Agent, Pilot Site Agent, Feedback Synthesis Agent, Scale Readiness Agent

EU · UK · US

Prototype & Pilot Evidence Standard

active

RD6-POL-201 · evidence · vv3.2

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

Approved by Director, Product Development · in force 2026-04-10 · reviewed 2026-06-24

Binds Build Planning Agent, Test Plan Agent, Iteration Tracking Agent, Pilot Site Agent, Feedback Synthesis Agent, Scale Readiness Agent

US · Canada

Prototype & Pilot Escalation Rule

active

RD6-POL-202 · escalation · vv4.9

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 Director, Product Development · in force 2026-06-08 · reviewed 2026-08-09

Binds Build Planning Agent, Test Plan Agent, Iteration Tracking Agent, Pilot Site Agent, Feedback Synthesis Agent, Scale Readiness Agent

Global

Prototype & Pilot Autonomy Ceiling

active

RD6-POL-203 · ceiling · vv4.3

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

Approved by Director, Product Development · in force 2026-03-21 · reviewed 2026-05-26

Binds Build Planning Agent, Test Plan Agent, Iteration Tracking Agent, Pilot Site Agent, Feedback Synthesis Agent, Scale Readiness Agent

Global · EU

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Product Lifecycle ManagementSiemens Teamcenterengineeringhigh5modeled
Research Notebook and Experiment DataBenchlingengineeringmedium1not-connected

0 of the 2 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 0 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

15.0 hrs

Summed from the time each step sits, standard 24.9 hrs — running at 60% of the standard.

Touchless

77%

Agent share

67%

A week

475

In flight

111

Effort a week

497 human minutes · 402 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

Physical experiment authorization

approval

Any laboratory experiment involving materials, equipment or subjectsPrincipal investigator and safety officer2 business daysNo

External data acquisition

approval

Any new external dataset, license or third-party evidence sourceResearch governance and Legal3 business daysNo

Publication or external disclosure

approval

Any material leaving the research boundary, including conference abstractsCSO and General Counsel5 business daysNo

Reproduction sampling

oversight

Independent re-derivation of 15% of reported internal resultsReproducibility boardMonthlyNo

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.