LensReading which lens this session carries.
The catalogueResearch & DevelopmentTechnology ScoutingAnalytical

Service RD10A

Scouting Cycle

Runs analytical. Starts when a drift signal breaches tolerance. It runs 25 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 2 of them on the shared spine.

Runs a week

25

84 in flight right now.

Stations

6

1 person · 3 agent · 2 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Director, Technology Scouting.

Touchless

67%

Share of runs that complete without anybody opening them.

Timetable against actual

151.9h

Actual 174.8h, 22.9h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 40% of the dwellAgent3 stations and 42% of the dwellShared spine2 stations and 18% of the dwell3 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
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

Scan landscape

GBSTechnology Scouting Orchestratorgbs1h 56m4h 26m24Product Lifecycle Management
2

Screen candidates

GBSLandscape Monitoring Agentgbs4h 31m8h 12m21Product Lifecycle Management
3

Match to needs

AgentCapability Match Agentworkflow6h 46m15h 58m22Product Lifecycle Management
4

Draft shortlist

AgentBuild-Buy-Partner Agentworkflow5h 44m7h 20m9Research Notebook and Experiment Data
5

Leader review

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

HumanDirector, Technology Scoutingpolicy14h 10m18h 54m3Product Lifecycle Management
6

Engage

AgentTechnology Scouting Orchestratorworkflow2h 39m4h 26m5Product 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%
25 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 gates11 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
354.2h
25 items at 850 minutes of decision each.
Agent time a week
540h
1,296 minutes an item, which does not compete for a person.
Gate load
92%
Inside capacity, with 30.8h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
40% waiting on a person
60% in the agent lane
An item now takes 2,146 minutes of worked time end to end against 2,146 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 Scouting 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.

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

now Scan landscape · Technology Scouting Orchestrator · 1.9 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 2.7 days

now Scan landscape · Technology Scouting Orchestrator · 1.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

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.

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 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
Technology Scouting Orchestrator
That orchestrator’s remit
Owns candidate work end to end inside Research & Development. Runs 3 lines across 16 stations, drains the repeatable share into no shared tower, and holds 3 human gates.
Accountable person
Director, Technology Scouting
Sub-function
Technology Scouting
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

Build-Buy-Partner PositionRD10BTechnical DiligenceRD10C

What this page is and is not

This is a catalogue of the modeled estate.