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

Service RD6B

Pilot Deployment

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

Runs a week

475

111 in flight right now.

Stations

6

2 person · 3 agent · 1 spine

Agent share of steps

67%

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

Decisions a person makes

2

Held by Director, Product Development.

Touchless

77%

Share of runs that complete without anybody opening them.

Timetable against actual

12.0h

Actual 11.6h, 0.4h under the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 55% of the dwellAgent3 stations and 32% of the dwellShared spine1 station and 13% of the dwell4 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
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

Select site

AgentBuild Planning Agentworkflow1h 36m2h 42m10Product Lifecycle Management
2

Prepare

AgentTest Plan Agentworkflow26m40m44Research Notebook and Experiment Data
3

Approve pilot

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 Developmentpolicy7h 20m11h 30m6Product Lifecycle Management
4

Run

AgentPilot Site Agentworkflow2h 46m3h 28m43Product Lifecycle Management
5

Measure

GBSBuild Planning Agentgbs1h 54m4h 16m5Product Lifecycle Management
6

Scale decision

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 Developmentpolicy57m2h 15m3Product 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%
475 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 gates113 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
3,934.6h
475 items at 497 minutes of decision each.
Agent time a week
3,182.5h
402 minutes an item, which does not compete for a person.
Gate load
99%
Inside capacity, with 20.4h of headroom.
Stations without a person
67%
2 gates left on 6 stations.
Where an item spends its time
55% waiting on a person
45% in the agent lane
An item now takes 899 minutes of worked time end to end against 899 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 Pilot Deployment

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

now Select site · Build Planning Agent · 1.6 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 34 hrs

now Select site · Build Planning Agent · 1.6 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

The system register

Product Lifecycle Management

Siemens Teamcenter · engineering · inbound · high

modeled

5 of 6 stations attributed here · read only

Research Notebook and Experiment Data

Benchling · engineering · inbound · medium

not-connected

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

Prototype CycleRD6AScale Readiness AssessmentRD6C

What this page is and is not

This is a catalogue of the modeled estate.