LensReading which lens this session carries.
The catalogueLegalIP PortfolioTransactional

Service LG6B

Annuity & Renewal

Runs transactional. Starts when a scheduled window opens. It runs 7,581 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 3 of them on the shared spine.

Runs a week

7,581

153 in flight right now.

Stations

6

1 person · 2 agent · 3 spine

Agent share of steps

83%

Autonomy on this service is set at 64% against a ceiling of 74%.

Decisions a person makes

1

Held by Chief IP Counsel.

Touchless

68%

Share of runs that complete without anybody opening them.

Timetable against actual

15.0h

Actual 12.5h, 2.5h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 9% of the dwellAgent2 stations and 32% of the dwellShared spine3 stations and 60% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Contract Lifecycle Management
Contract Lifecycle Management
Document and Matter Management
Contract Lifecycle Management
Contract Lifecycle Management
Contract 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

Detect due

GBSIP Orchestratorgbs3h 9m7h 21m32Contract Lifecycle Management
2

Assess value

AgentPrior Art Search Agentworkflow1h 56m3h 34m35Contract Lifecycle Management
3

Recommend

AgentFiling Calendar Agentworkflow2h 46m3h 11m32Document and Matter Management
4

Approve

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

HumanChief IP Counselpolicy1h 17m2h 59m2Contract Lifecycle Management
5

Pay

Hands over at finance

GBSRenewal & Annuity Agentgbs3h 4m6h 21m13Contract Lifecycle Management
6

Record

GBSInfringement Watch Agentgbs2h 39m6h 4m39Contract 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%
7,581 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 gates278 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,729h
7,581 items at 77 minutes of decision each.
Agent time a week
102,848.9h
814 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 1.1h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
91% in the agent lane
An item now takes 891 minutes of worked time end to end against 891 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 Annuity & Renewal

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

now Detect due · IP Orchestrator · 3.1 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 31 hrs

now Detect due · IP Orchestrator · 3.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.

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

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

5 of 6 stations attributed here · would write back

Document and Matter Management

iManage · legal · inbound · medium

modeled

1 of 6 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
IP Orchestrator
That orchestrator’s remit
Owns IP matter work end to end inside Legal. Runs 3 lines across 19 stations, drains the repeatable share into no shared tower, and holds 4 human gates.
Accountable person
Chief IP Counsel
Sub-function
IP Portfolio
Shared spine tower
Not on the shared spine
Hand-over points
finance

Other services in this sub-function

2 alongside this one

Invention to FilingLG6APortfolio Strategy PositionLG6C

What this page is and is not

This is a catalogue of the modeled estate.