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

Service RD3A

Protocol Development

Runs transactional. Starts when a threshold is crossed. It runs 430 times a week across 7 stations. 2 of those stations stop for a person and 5 are done by an agent, 1 of them on the shared spine.

Runs a week

430

122 in flight right now.

Stations

7

2 person · 4 agent · 1 spine

Agent share of steps

71%

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

Decisions a person makes

2

Held by Director, Research Methods.

Touchless

70%

Share of runs that complete without anybody opening them.

Timetable against actual

10.2h

Actual 12.0h, 1.8h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 62% of the dwellAgent4 stations and 31% of the dwellShared spine1 station and 8% of the dwell2 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
Research Notebook and Experiment Data
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.

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

Frame question

AgentProtocol Drafting Agentworkflow1h 52m2h 35m27Product Lifecycle Management
2

Draft protocol

AgentPower Analysis Agentworkflow2h 44m4h8Research Notebook and Experiment Data
3

Power analysis

AgentControl Design Agentworkflow1h 9m1h 59m9Product Lifecycle Management
4

Bias review

AgentBias Detection Agentworkflow55m1h 26m45Research Notebook and Experiment Data
5

Scientist review

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 Methodspolicy5h 58m8h 34m9Product Lifecycle Management
6

Ethics clearance

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 Methodspolicy7h 23m9h 51m7Product Lifecycle Management
7

Register

GBSProtocol Drafting Agentgbs1h 38m3h 36m17Product 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%
430 a week is what the estate records.
Decisions handed to agents0 of 2
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates165 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
5,740.5h
430 items at 801 minutes of decision each.
Agent time a week
3,569h
498 minutes an item, which does not compete for a person.
Gate load
99%
Inside capacity, with 34.5h of headroom.
Stations without a person
71%
2 gates left on 7 stations.
Where an item spends its time
62% waiting on a person
38% in the agent lane
An item now takes 1,299 minutes of worked time end to end against 1,299 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 Development

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.

7 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

7 stations, nothing waiting, nothing sent back

0 min of 22 hrs

now Frame question · Protocol Drafting Agent · 1.9 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 41 hrs

now Frame question · Protocol Drafting Agent · 1.9 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 …

Live observability

Systems this service would touch

Attributed by rule from the function's system list.

2 systems attributed

0 of 2 returning records

Product Lifecycle Management

Siemens Teamcenter · engineering · inbound · high

modeled

5 of 7 stations attributed here · read only

Research Notebook and Experiment Data

Benchling · engineering · inbound · medium

not-connected

2 of 7 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

What this page is and is not

This is a catalogue of the modeled estate.