LensReading which lens this session carries.
The catalogueResearch & DevelopmentIP Creation & CaptureJudgment

Service RD7C

IP Strategy Position

Runs judgment. Starts when the annual doctrine review opens. It runs 4 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, none of them on the shared spine.

Runs a week

4

87 in flight right now.

Stations

5

1 person · 4 agent · 0 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by Director, IP Capture.

Touchless

48%

Share of runs that complete without anybody opening them.

Timetable against actual

455.0h

Actual 552.4h, 97.4h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 41% of the dwellAgent4 stations and 59% 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
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

AgentInvention Detection Agentstrategy53h 37m69h 22m41Product Lifecycle Management
2

Map portfolio

AgentDisclosure Drafting Agentstrategy10h 56m23h 46m21Product Lifecycle Management
3

Draft position

AgentNovelty Screening Agentstrategy15h 47m28h 37m6Product Lifecycle Management
4

Challenge

AgentInventor Attribution Agentstrategy41h 24m83h 11m16Product Lifecycle Management
5

Ratify

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

HumanDirector, IP Capturepolicy83h 23m141h 52m3Product 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 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 gates10 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
333.5h
4 items at 5,003 minutes of decision each.
Agent time a week
486.9h
7,304 minutes an item, which does not compete for a person.
Gate load
95%
Inside capacity, with 16.5h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
41% waiting on a person
59% in the agent lane
An item now takes 12,307 minutes of worked time end to end against 12,307 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 IP Strategy 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.

5 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

5 stations, nothing waiting, nothing sent back

0 min of 8.5 days

now Frame · Invention Detection Agent · 2.2 days

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 8.6 days

now Frame · Invention Detection Agent · 2.2 days

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

2 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

5 of 5 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
IP Capture Orchestrator
That orchestrator’s remit
Owns disclosure work end to end inside Research & Development. Runs 3 lines across 16 stations, drains the repeatable share into the C2L tower, and holds 3 human gates.
Accountable person
Director, IP Capture
Sub-function
IP Creation & Capture
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

What this page is and is not

This is a catalogue of the modeled estate.