LensReading which lens this session carries.
The catalogueResearch & DevelopmentPrototype & PilotTransactional

Service RD6A

Prototype Cycle

Runs transactional. Starts when a scheduled window opens. It runs 4,644 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

4,644

104 in flight right now.

Stations

7

1 person · 5 agent · 1 spine

Agent share of steps

86%

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

Decisions a person makes

1

Held by Director, Product Development.

Touchless

77%

Share of runs that complete without anybody opening them.

Timetable against actual

16.9h

Actual 17.2h, 0.3h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 17% of the dwellAgent5 stations and 68% of the dwellShared spine1 station and 14% of the dwell3 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
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

Define target

AgentBuild Planning Agentworkflow2h 49m6h 34m11Product Lifecycle Management
2

Plan build

AgentTest Plan Agentworkflow2h 30m5h 42m26Research Notebook and Experiment Data
3

Build

AgentIteration Tracking Agentworkflow1h 21m2h 57m12Product Lifecycle Management
4

Test

GBSBuild Planning Agentgbs2h 27m5h 8m9Product Lifecycle Management
5

Synthesize feedback

AgentFeedback Synthesis Agentworkflow2h 59m6h 26m23Research Notebook and Experiment Data
6

Iterate

AgentScale Readiness Agentworkflow1h 57m4h 40m19Product Lifecycle Management
7

Readiness review

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.

HumanDirector, Product Developmentpolicy2h 55m3h 28m4Product 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%
4,644 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 gates387 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
13,545h
4,644 items at 175 minutes of decision each.
Agent time a week
65,248.2h
843 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 0h of headroom.
Stations without a person
86%
1 gate left on 7 stations.
Where an item spends its time
17% waiting on a person
83% in the agent lane
An item now takes 1,018 minutes of worked time end to end against 1,018 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 Prototype Cycle

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 17 hrs

now Define target · Build Planning Agent · 2.8 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 42 hrs

now Define target · Build Planning Agent · 2.8 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
Prototype Orchestrator
That orchestrator’s remit
Owns prototype work end to end inside Research & Development. Runs 3 lines across 17 stations, drains the repeatable share into the C2L tower, and holds 4 human gates.
Accountable person
Director, Product Development
Sub-function
Prototype & Pilot
Shared spine tower
c2l
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Pilot DeploymentRD6BScale Readiness AssessmentRD6C

What this page is and is not

This is a catalogue of the modeled estate.