LensReading which lens this session carries.

Standard operating procedure · RD7A · Research & Development

Invention Capture

Transactional procedure owned by IP Creation & Capture in Research & Development. 6 numbered steps, 1 of them a person deciding and 5 of them agent work …

Procedure code

RD7A

Transactional

Rule versions in force

v4.8 · v4.4 · v5.8 · v2.8

4 governing rules stacked over it

In force since

2024-10-12

Earliest effective date across those rules

Last reviewed

2026-07-26

Latest review date across those rules

Rules approved by

1

Director, IP Capture

Rule health

3/4

1 under review · 0 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run invention capture to one repeatable standard inside IP Creation & Capture, part of Research & Development.

Entry condition

Runs transactional. Starts when a scheduled window opens.

Exit condition

The unit clears track.

In scope

  • Every unit of invention capture raised inside IP Creation & Capture, from the trigger below through to the final step.
  • 5 of the 6 steps, which run without a person present.
  • 1 decision that stops the line until a named person releases it.

Out of scope

  • Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
  • Work that belongs to another function. This line hands off to legal and does not follow the unit there.
  • The 2 steps carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

IP Capture Orchestrator

Accountable person

Director, IP Capture

The end of the escalation path. Above them sits R&D Chief of Staff for the function.

That team’s remit

Owns disclosure work end to end inside Research & Development.

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

66% now · ceiling 80%

Detecting patentable work inside research output is something agents do continuously and people forget to do.

The procedure, step by step

6 numbered steps · 1 of them stop for a person

A step is one station on the line.

No.StepWho does itWhat happensSystem of recordTime on the stepIn flight
01

Detect novel work

GBSgbs

Inventor Attribution Agent

Inventor Attribution Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Product Lifecycle Management2.4 hrsstandard 4.3 hrs9
02

Draft disclosure

Agentworkflow

Disclosure Drafting Agent

Disclosure Drafting Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Product Lifecycle Management2.5 hrsstandard 4.1 hrs29
03

Novelty screen

GBSgbs

Inventor Attribution Agent

Inventor Attribution Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Product Lifecycle Management2.9 hrsstandard 3.8 hrs28
04

Inventor confirm

HumanpolicyDecision

Director, IP Capture

Releases: Director, IP Capture

Work stops. Director, IP Capture reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: 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.Product Lifecycle Management4.8 hrsstandard 7.7 hrs2
05

Route to Legal

Agentworkflow

Trade Secret Agent

Trade Secret Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Hands off to legalResearch Notebook and Experiment Data2.1 hrsstandard 3.2 hrs34
06

Track

Agentworkflow

IP Strategy Agent

IP Strategy Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Product Lifecycle Management2.5 hrsstandard 5.7 hrs13

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine.

Person1 station and 28% of the dwellAgent3 stations and 42% of the dwellShared spine2 stations and 31% of the dwell4 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
Research Notebook and Experiment Data
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.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it.

speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/6
the happy path, worked time0 min of 17 hrs
the same run against its allowance0 min of 29 hrs
Human
decides · 1
Agent
does the work · 3
GBS
shared spine · 2
run log

Nothing has happened yet.

where the worked time goes17 hrs a unit
Person4.8 hrs · 28%Agent7.2 hrs · 42%Shared spine5.3 hrs · 31%4 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 6 stations stop for a person and every one of them still does on this run.
  • Every one of the 1 decision is still taken by the person who holds it. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 80% autonomy ceiling and this run sits at 72% unattended, inside it.
  • 2 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
what would have to change

One decision, held by Director, IP Capture.

stays with a person
  • 04 Inventor confirm — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
what this run is, and what it is not

This is a run, not a forecast.

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations.

The second clock is the allowance.

A decision may be handed to the agent lane only if two things hold …

The run reads the station rows only.

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything.

Run it again, going wrong

The same unit, the same stations, broken the way the estate already records breaking

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

now Detect novel work · Inventor Attribution Agent · 2.4 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 36 hrs

now Detect novel work · Inventor Attribution Agent · 2.4 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

5 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 …

Roles and responsibilities

6 named parties

The responsibility grid is assigned by a rule, not lifted from a chart.

PartyRACIStepsDutyEscalates to

IP Capture Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to Director, IP Capture when a unit falls outside the envelope or confidence drops below the floor.

Inventor Attribution Agent

agent

A3% autonomy · ceiling A3%

91% clean · 6% overridden

Responsible2Runs the repeatable portion of ip creation & capture inside the shared transaction spine at spine cost and spine controls.Escalates to Director, IP Capture when the unit falls outside the decision envelope or confidence drops below the floor.

Disclosure Drafting Agent

agent

A3% autonomy · ceiling A3%

95% clean · 7% overridden

Responsible1Executes the ip creation & capture step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, IP Capture when the unit falls outside the decision envelope or confidence drops below the floor.

Director, IP Capture

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Director, IP Capture for the decisions held here.

Trade Secret Agent

agent

A3% autonomy · ceiling A3%

88% clean · 5% overridden

Responsible1Executes the ip creation & capture step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, IP Capture when the unit falls outside the decision envelope or confidence drops below the floor.

IP Strategy Agent

agent

A2% autonomy · ceiling A3%

89% clean · 16% overridden

Responsible1Authors positions on ip creation & capture. Escalates when two options sit inside the confidence band and the evidence cannot separate them.

Decision points and escalation

1 places this procedure stops

04 · Inventor confirm

4.8 hrs

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.

Director, IP Capture

Handoffs out of this procedure

Step 05 Route to Legal passes the work to legal.

The rules this procedure runs inside

4 governing rules

IP Creation & Capture Decision Envelope

active

RD7-POL-200 · envelope · vv4.8

Agents in this lane may act without a human when the disclosure sits inside the stated value, risk and confidence envelope.

Approved by Director, IP Capture · in force 2025-05-21 · reviewed 2026-07-19

Binds Disclosure Drafting Agent, Novelty Screening Agent, Inventor Attribution Agent, Trade Secret Agent

LATAM · US

IP Creation & Capture Evidence Standard

active

RD7-POL-201 · evidence · vv4.4

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path.

Approved by Director, IP Capture · in force 2025-06-22 · reviewed 2026-07-04

Binds Disclosure Drafting Agent, Novelty Screening Agent, Inventor Attribution Agent, Trade Secret Agent

EU · UK · US

IP Creation & Capture Escalation Rule

under review

RD7-POL-202 · escalation · vv5.8

Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires.

Approved by Director, IP Capture · in force 2025-12-04 · reviewed 2026-06-24

Binds Disclosure Drafting Agent, Novelty Screening Agent, Inventor Attribution Agent, Trade Secret Agent

EU · UK · US

IP Creation & Capture Autonomy Ceiling

active

RD7-POL-203 · ceiling · vv2.8

The ceiling for this lane is 80 on the platform scale.

Approved by Director, IP Capture · in force 2024-10-12 · reviewed 2026-07-26

Binds Disclosure Drafting Agent, Novelty Screening Agent, Inventor Attribution Agent, Trade Secret Agent

EU · UK · US

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Product Lifecycle ManagementSiemens Teamcenterengineeringhigh5modeled
Research Notebook and Experiment DataBenchlingengineeringmedium1not-connected

0 of the 2 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 0 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

17.3 hrs

Summed from the time each step sits, standard 28.8 hrs — running at 60% of the standard.

Touchless

73%

Agent share

83%

A week

634

In flight

115

Effort a week

287 human minutes · 749 agent minutes

Volume multiplied by the time on each step.

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level …

GateWhat trips itWho releases itClockWaivable

Physical experiment authorization

approval

Any laboratory experiment involving materials, equipment or subjectsPrincipal investigator and safety officer2 business daysNo

External data acquisition

approval

Any new external dataset, license or third-party evidence sourceResearch governance and Legal3 business daysNo

Publication or external disclosure

approval

Any material leaving the research boundary, including conference abstractsCSO and General Counsel5 business daysNo

Reproduction sampling

oversight

Independent re-derivation of 15% of reported internal resultsReproducibility boardMonthlyNo

What this document is and is not

These procedures describe the modeled estate.

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings.

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from.

Current distribution

2,748 steps

Agent, inside the function1,38951%
Agent, on the shared spine85131%
Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date.