LensReading which lens this session carries.
The catalogueResearch & DevelopmentDiscovery ResearchAnalytical

Service RD1A

Discovery Sprint

Runs analytical. Starts when the cycle calendar fires. It runs 40 times a week across 7 stations. One of those stations stops for a person and 6 are done by an agent, 1 of them on the shared spine.

Runs a week

40

175 in flight right now.

Stations

7

1 person · 5 agent · 1 spine

Agent share of steps

86%

Autonomy on this service is set at 71% against a ceiling of 78%.

Decisions a person makes

1

Held by Director, Discovery Research.

Touchless

61%

Share of runs that complete without anybody opening them.

Timetable against actual

82.2h

Actual 80.0h, 2.2h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 23% of the dwellAgent5 stations and 62% of the dwellShared spine1 station and 15% of the dwell4 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
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

Frame question

AgentLiterature Synthesis Agentworkflow7h 56m11h 21m22Product Lifecycle Management
2

Synthesize literature

GBSLiterature Synthesis Agentgbs12h 20m26h 29m34Product Lifecycle Management
3

Generate hypotheses

AgentPrior Work Agentworkflow14h 29m17h 17m34Research Notebook and Experiment Data
4

Screen feasibility

AgentFeasibility Screening Agentworkflow4h 27m8h 34m27Product Lifecycle Management
5

Draft findings

AgentResearch Direction Agentworkflow11h18h 40m24Research Notebook and Experiment Data
6

Scientist review

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

HumanDirector, Discovery Researchpolicy19h 19m28h 29m3Product Lifecycle Management
7

Log

AgentLiterature Synthesis Agentworkflow14h 16m28h 19m31Product 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%
40 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 gates23 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
772.7h
40 items at 1,159 minutes of decision each.
Agent time a week
2,578.7h
3,868 minutes an item, which does not compete for a person.
Gate load
96%
Inside capacity, with 32.3h of headroom.
Stations without a person
86%
1 gate left on 7 stations.
Where an item spends its time
23% waiting on a person
77% in the agent lane
An item now takes 5,027 minutes of worked time end to end against 5,027 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 Discovery Sprint

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 3.5 days

now Frame question · Literature Synthesis Agent · 7.9 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 6.1 days

now Frame question · Literature Synthesis Agent · 7.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

5 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

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
Discovery Orchestrator
That orchestrator’s remit
Owns research thread work end to end inside Research & Development. Runs 3 lines across 17 stations, drains the repeatable share into no shared tower, and holds 2 human gates.
Accountable person
Director, Discovery Research
Sub-function
Discovery Research
Shared spine tower
Not on the shared spine
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Research Direction PositionRD1BPrior Work SweepRD1C

What this page is and is not

This is a catalogue of the modeled estate.