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

Service RD1B

Research Direction Position

Runs judgment. Starts when a break condition on a live position fires. It runs 5 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, none of them on the shared spine.

Runs a week

5

155 in flight right now.

Stations

6

1 person · 5 agent · 0 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Director, Discovery Research.

Touchless

40%

Share of runs that complete without anybody opening them.

Timetable against actual

334.7h

Actual 293.1h, 41.6h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 32% of the dwellAgent5 stations and 68% 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
Product Lifecycle Management
Product Lifecycle Management
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.

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

AgentLiterature Synthesis Agentstrategy29h 34m62h 5m4Product Lifecycle Management
2

Map field

AgentHypothesis Generation Agentstrategy28h 46m55h 56m41Product Lifecycle Management
3

Model options

AgentPrior Work Agentstrategy28h 42m42h 23m39Product Lifecycle Management
4

Draft position

AgentFeasibility Screening Agentstrategy61h 28m94h 8m26Product Lifecycle Management
5

Challenge

AgentResearch Direction Agentstrategy56h 30m81h 59m45Product Lifecycle Management
6

Chief Scientist ratify

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 Researchpolicy94h 30m218h 4m0Product 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%
5 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 gates14 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
472.5h
5 items at 5,670 minutes of decision each.
Agent time a week
1,025h
12,300 minutes an item, which does not compete for a person.
Gate load
96%
Inside capacity, with 17.5h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
32% waiting on a person
68% in the agent lane
An item now takes 17,970 minutes of worked time end to end against 17,970 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 Research Direction Position

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.

6 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

6 stations, nothing waiting, nothing sent back

0 min of 12.5 days

now Frame · Literature Synthesis Agent · 30 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 12.7 days

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

3 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.

1 systems attributed

0 of 1 returning records

The system register

Product Lifecycle Management

Siemens Teamcenter · engineering · inbound · high

modeled

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

Discovery SprintRD1APrior Work SweepRD1C

What this page is and is not

This is a catalogue of the modeled estate.