LensReading which lens this session carries.
The catalogueResearch & DevelopmentLab OperationsTransactional

Service RD4B

Consumables Replenishment

Runs transactional. Starts when a request lands in the queue. It runs 1,317 times a week across 4 stations. No station stops for a person and 4 are done by an agent, 4 of them on the shared spine.

Runs a week

1,317

110 in flight right now.

Stations

4

0 person · 0 agent · 4 spine

Agent share of steps

100%

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

Decisions a person makes

0

Nothing on this service waits for a person.

Touchless

87%

Share of runs that complete without anybody opening them.

Timetable against actual

7.5h

Actual 6.3h, 1.2h under the timetable.

Operations

The lane diagram

Read it left to right.

Person0 stations and 0% of the dwellAgent0 stations and 0% of the dwellShared spine4 stations and 100% of the dwell0 crossings 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
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

Detect low stock

GBSScheduling Agentgbs2h 30m4h 9m41Product Lifecycle Management
2

Raise requisition

Hands over at procurement

GBSScheduling Agentgbs2h 16m5h 6m24Product Lifecycle Management
3

Receive

GBSScheduling Agentgbs6m9m31Product Lifecycle Management
4

Stock

GBSScheduling Agentgbs57m1h 8m14Product 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%
1,317 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 gates1 person
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
0h
1,317 items at 0 minutes of decision each.
Agent time a week
7,660.6h
349 minutes an item, which does not compete for a person.
Gate load
0%
Inside capacity, with 35h of headroom.
Stations without a person
100%
0 gates left on 4 stations.
Where an item spends its time
100% in the agent lane
An item now takes 349 minutes of worked time end to end against 349 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 Consumables Replenishment

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.

4 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

4 stations, nothing waiting, nothing sent back

0 min of 5.8 hrs

now Detect low stock · Scheduling Agent · 2.5 hrs

As the ledger has it

the same stations, plus 1 categories the estate already counts

0 min of 7.0 hrs

now Detect low stock · Scheduling Agent · 2.5 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

1 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

Product Lifecycle Management

Siemens Teamcenter · engineering · inbound · high

modeled

4 of 4 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Lab Operations Orchestrator
That orchestrator’s remit
Owns lab request work end to end inside Research & Development. Runs 3 lines across 15 stations, drains the repeatable share into the C2L tower, and holds 1 human gates.
Accountable person
Director, Laboratory Operations
Sub-function
Lab Operations
Shared spine tower
c2l
Hand-over points
procurement

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.