Service RD9A
Research Collaboration Setup
Runs transactional. Starts when an upstream system posts an event. It runs 3,828 times a week across 7 stations. 2 of those stations stop for a person and 5 are done by an agent, 1 of them on the shared spine.
Runs a week
3,828
122 in flight right now.
Stations
7
2 person · 4 agent · 1 spine
Agent share of steps
71%
Autonomy on this service is set at 61% against a ceiling of 70%.
Decisions a person makes
2
Held by Director, External Innovation.
Touchless
65%
Share of runs that complete without anybody opening them.
Timetable against actual
22.8h
Actual 18.1h, 4.7h under the timetable.
Operations
The lane diagram
Read it left to right. more
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.
| # | Station | Lane | Who | Layer | Dwell | Target | In flight | System |
|---|---|---|---|---|---|---|---|---|
| 1 | Identify partner | Agent | Partner Scouting Agent | workflow | 1h 8m | 1h 23m | 20 | Product Lifecycle Management |
| 2 | Scope work | Agent | Agreement Coordination Agent | workflow | 32m | 56m | 45 | Research Notebook and Experiment Data |
| 3 | Agreement Hands over at legal | GBS | Agreement Coordination Agent | gbs | 30m | 59m | 26 | Product Lifecycle Management |
| 4 | IP terms review 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 | Human | Director, External Innovation | policy | 4h 11m | 9h 19m | 8 | Product Lifecycle Management |
| 5 | Sign 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. | Human | Director, External Innovation | policy | 5h 30m | 7h 29m | 8 | Product Lifecycle Management |
| 6 | Kick off | Agent | Partner Strategy Agent | workflow | 2h 22m | 3h 52m | 1 | Product Lifecycle Management |
| 7 | Track milestones | Agent | Collaboration Orchestrator | workflow | 14m | 32m | 14 | Research Notebook and Experiment Data |
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. more
The simulation is arithmetic on the estate, not a queueing model. more
How it runs
Run it again, going wrong
The same unit and the same stations, broken the way the estate already records breaking. more
7 stations, walked twice
Once clean, once with the categories the estate counts
This is the same unit on the same stations, breaking. more
No break below was chosen. more
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
7 stations, nothing waiting, nothing sent back
0 min of 14 hrs
now Identify partner · Partner Scouting Agent · 1.1 hrs
As the ledger has it
the same stations, plus 6 categories the estate already counts
0 min of 42 hrs
now Identify partner · Partner Scouting Agent · 1.1 hrs
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
6 counted categories land on this procedure. more
What this run cannot claim
These breaks are shown together on one unit so the shape of a bad day fits on one screen. more
The separation register records a duty conflict against a sub-function and a named post, not against one procedure. more
Two clocks run. Worked time is the sum of the time the work is actually being done … more
Live observability
Systems this service would touch
Attributed by rule from the function's system list. more
2 systems attributed
0 of 2 returning records
Product Lifecycle Management
Siemens Teamcenter · engineering · inbound · high
5 of 7 stations attributed here · read only
Research Notebook and Experiment Data
Benchling · engineering · inbound · medium
2 of 7 stations attributed here · read only
System attribution is a rule, not a reading. more
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
What this page is and is not
This is a catalogue of the modeled estate. more