LensReading which lens this session carries.
The catalogueResearch & DevelopmentExperiment DesignTransactional

Service RD3B

Protocol Deviation

Runs transactional. Starts when a request lands in the queue. It runs 7,292 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 2 of them on the shared spine.

Runs a week

7,292

72 in flight right now.

Stations

5

1 person · 2 agent · 2 spine

Agent share of steps

80%

Autonomy on this service is set at 59% against a ceiling of 72%.

Decisions a person makes

1

Held by Director, Research Methods.

Touchless

67%

Share of runs that complete without anybody opening them.

Timetable against actual

22.2h

Actual 19.7h, 2.5h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 31% of the dwellAgent2 stations and 48% of the dwellShared spine2 stations and 21% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Product Lifecycle Management
Product Lifecycle Management
Research Notebook and Experiment Data
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.

Operations

Every station in order

The same stations as a list, with the dwell the estate records against each one and the system a station of that shape would touch.

#StationLaneWhoLayerDwellTargetIn flightSystem
1

Detect

GBSProtocol Drafting Agentgbs1h 19m2h 2m10Product Lifecycle Management
2

Classify

AgentPower Analysis Agentworkflow2h3h 38m21Product Lifecycle Management
3

Assess validity impact

AgentControl Design Agentworkflow1h 41m3h 8m8Research Notebook and Experiment Data
4

Scientist decide

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

HumanDirector, Research Methodspolicy2h 21m4h 22m9Product Lifecycle Management
5

Document

GBSProtocol Drafting Agentgbs18m30m24Product Lifecycle Management

Operations

Run it

Change the volume, move the autonomy line, release a gate, and watch what happens to the hours in each lane and to the time it takes one run to get through.

Move something
Demand100%
7,292 a week is what the estate records.
Decisions handed to agents0 of 0
This service has at most one gate, so there is nothing to hand over without removing the last human decision.
People on the gates490 people
Each one is assumed to have 2,100 productive minutes a week, which is 35 hours.
Agent speed100%
100% is the dwell the estate records today.
Person time a week
17,136.2h
7,292 items at 141 minutes of decision each.
Agent time a week
38,647.6h
318 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 13.8h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
31% waiting on a person
69% in the agent lane
An item now takes 459 minutes of worked time end to end against 459 in the recorded estate, a change of +0%. This is worked time, not calendar time: nothing here models a queue or a weekend.
What this model is, on Protocol Deviation

The simulation is arithmetic on the estate, not a queueing model.

How it runs

Run it again, going wrong

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

5 stations, walked twice

Once clean, once with the categories the estate counts

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

5 stations, nothing waiting, nothing sent back

0 min of 7.7 hrs

now Detect · Protocol Drafting Agent · 1.3 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 23 hrs

now Detect · Protocol Drafting Agent · 1.3 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.

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

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

Live observability

Systems this service would touch

Attributed by rule from the function's system list.

2 systems attributed

0 of 2 returning records

The system register

Product Lifecycle Management

Siemens Teamcenter · engineering · inbound · high

modeled

4 of 5 stations attributed here · read only

Research Notebook and Experiment Data

Benchling · engineering · inbound · medium

not-connected

1 of 5 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Experiment Design Orchestrator
That orchestrator’s remit
Owns protocol work end to end inside Research & Development. Runs 3 lines across 16 stations, drains the repeatable share into the C2L tower, and holds 4 human gates.
Accountable person
Director, Research Methods
Sub-function
Experiment Design
Shared spine tower
c2l
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Protocol DevelopmentRD3ADesign Standard RefreshRD3C

What this page is and is not

This is a catalogue of the modeled estate.