LensReading which lens this session carries.
The catalogueLegalLitigation & DisputesTransactional

Service LG7B

Discovery Production

Runs transactional. Starts when a request lands in the queue. It runs 4,774 times a week across 6 stations. 2 of those stations stop for a person and 4 are done by an agent, 3 of them on the shared spine.

Runs a week

4,774

64 in flight right now.

Stations

6

2 person · 1 agent · 3 spine

Agent share of steps

67%

Autonomy on this service is set at 55% against a ceiling of 58%.

Decisions a person makes

2

Held by VP Litigation.

Touchless

62%

Share of runs that complete without anybody opening them.

Timetable against actual

5.3h

Actual 6.7h, 1.4h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 56% of the dwellAgent1 station and 21% of the dwellShared spine3 stations and 23% 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
Contract Lifecycle 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

Scope

GBSLitigation Orchestratorgbs36m42m8Contract Lifecycle Management
2

Collect

GBSMatter Intake Agentgbs1h 55m3h 4m24Contract Lifecycle Management
3

Review

AgentDocument Review Agentworkflow2h 52m5h 48m11Contract Lifecycle Management
4

Privilege check

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

HumanVP Litigationpolicy20m35m3Contract Lifecycle Management
5

Produce

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

HumanVP Litigationpolicy7h 15m9h 56m9Contract Lifecycle Management
6

Log

GBSExposure Modeling Agentgbs32m49m9Contract 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%
4,774 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 gates1035 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
36,202.8h
4,774 items at 455 minutes of decision each.
Agent time a week
28,246.2h
355 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 22.2h of headroom.
Stations without a person
67%
2 gates left on 6 stations.
Where an item spends its time
56% waiting on a person
44% in the agent lane
An item now takes 810 minutes of worked time end to end against 810 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 Discovery Production

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

now Scope · Litigation Orchestrator · 36 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 44 hrs

now Scope · Litigation Orchestrator · 36 min

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 …

Live observability

Systems this service would touch

Attributed by rule from the function's system list.

1 systems attributed

0 of 1 returning records

The system register

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

6 of 6 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Litigation Orchestrator
That orchestrator’s remit
Owns matter work end to end inside Legal. Runs 3 lines across 20 stations, drains the repeatable share into no shared tower, and holds 6 human gates.
Accountable person
VP Litigation
Sub-function
Litigation & Disputes
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

Matter LifecycleLG7ASettlement PositionLG7C

What this page is and is not

This is a catalogue of the modeled estate.