LensReading which lens this session carries.
The catalogueLegalLegal Ops & SpendAnalytical

Service LG11C

Capacity Rebalance

Runs analytical. Starts when the reporting period closes. It runs 60 times a week across 4 stations. One of those stations stops for a person and 3 are done by an agent, none of them on the shared spine.

Runs a week

60

109 in flight right now.

Stations

4

1 person · 3 agent · 0 spine

Agent share of steps

75%

Autonomy on this service is set at 83% against a ceiling of 88%.

Decisions a person makes

1

Held by Director, Legal Operations.

Touchless

72%

Share of runs that complete without anybody opening them.

Timetable against actual

205.2h

Actual 194.2h, 11.0h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 61% of the dwellAgent3 stations and 39% 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
Contract Lifecycle Management
Document and Matter 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

Model demand

AgentMatter Data Quality Agentworkflow9h 36m16h 55m29Contract Lifecycle Management
2

Model capacity

AgentSpend Analytics Agentworkflow6h 43m11h 27m32Document and Matter Management
3

Draft recommendation

AgentWorkflow Automation Agentworkflow3h 35m6h 35m46Contract Lifecycle Management
4

Leader review

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

HumanDirector, Legal Operationspolicy30h 39m54h 8m2Contract 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%
60 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 gates53 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
1,839h
60 items at 1,839 minutes of decision each.
Agent time a week
1,194h
1,194 minutes an item, which does not compete for a person.
Gate load
99%
Inside capacity, with 16h of headroom.
Stations without a person
75%
1 gate left on 4 stations.
Where an item spends its time
61% waiting on a person
39% in the agent lane
An item now takes 3,033 minutes of worked time end to end against 3,033 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 Capacity Rebalance

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.

4 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

4 stations, nothing waiting, nothing sent back

0 min of 2.1 days

now Model demand · Matter Data Quality Agent · 9.6 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 2.2 days

now Model demand · Matter Data Quality Agent · 9.6 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

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.

2 systems attributed

0 of 2 returning records

The system register

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

3 of 4 stations attributed here · would write back

Document and Matter Management

iManage · legal · inbound · medium

modeled

1 of 4 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Legal Ops Orchestrator
That orchestrator’s remit
Owns ops item work end to end inside Legal. Runs 3 lines across 14 stations, drains the repeatable share into the LEGAL tower, and holds 3 human gates.
Accountable person
Director, Legal Operations
Sub-function
Legal Ops & Spend
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

Spend ReadLG11AKnowledge CaptureLG11B

What this page is and is not

This is a catalogue of the modeled estate.