LensReading which lens this session carries.
The catalogueResearch & DevelopmentExternal CollaborationTransactional

Service RD9B

Data Sharing Request

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

Runs a week

2,022

124 in flight right now.

Stations

6

2 person · 2 agent · 2 spine

Agent share of steps

67%

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

Decisions a person makes

2

Held by Director, External Innovation.

Touchless

70%

Share of runs that complete without anybody opening them.

Timetable against actual

6.1h

Actual 7.3h, 1.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 43% of the dwellAgent2 stations and 35% of the dwellShared spine2 stations and 22% of the dwell2 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

Request

AgentPartner Scouting Agentworkflow1h 6m2h 10m45Product Lifecycle Management
2

Classify sensitivity

AgentAgreement Coordination Agentworkflow2h 56m5h 3m5Research Notebook and Experiment Data
3

Privacy check

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

Hands over at legal

HumanDirector, External Innovationpolicy19m30m8Product Lifecycle Management
4

Approve

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

HumanDirector, External Innovationpolicy4h 32m10h 32m9Product Lifecycle Management
5

Share

GBSData Sharing Agentgbs2h 3m4h 31m36Product Lifecycle Management
6

Log

GBSPublication Review Agentgbs27m1h 2m21Product 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%
2,022 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 gates281 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
9,806.7h
2,022 items at 291 minutes of decision each.
Agent time a week
13,210.4h
392 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 28.3h of headroom.
Stations without a person
67%
2 gates left on 6 stations.
Where an item spends its time
43% waiting on a person
57% in the agent lane
An item now takes 683 minutes of worked time end to end against 683 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 Data Sharing Request

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

now Request · Partner Scouting Agent · 1.1 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 31 hrs

now Request · Partner Scouting Agent · 1.1 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
Collaboration Orchestrator
That orchestrator’s remit
Owns collaboration work end to end inside Research & Development. Runs 3 lines across 19 stations, drains the repeatable share into no shared tower, and holds 6 human gates.
Accountable person
Director, External Innovation
Sub-function
External Collaboration
Shared spine tower
Not on the shared spine
Hand-over points
legal

Other services in this sub-function

2 alongside this one

Research Collaboration SetupRD9APublication ClearanceRD9C

What this page is and is not

This is a catalogue of the modeled estate.