LensReading which lens this session carries.
The catalogueLegalContract LifecycleTransactional

Service LG1C

Obligation Monitoring

Runs transactional. Starts when an upstream system posts an event. It runs 2,484 times a week across 4 stations. One of those stations stops for a person and 3 are done by an agent, 3 of them on the shared spine.

Runs a week

2,484

75 in flight right now.

Stations

4

1 person · 0 agent · 3 spine

Agent share of steps

75%

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

Decisions a person makes

1

Held by Director, Commercial Contracts.

Touchless

83%

Share of runs that complete without anybody opening them.

Timetable against actual

3.6h

Actual 3.9h, 0.3h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 41% of the dwellAgent0 stations and 0% of the dwellShared spine3 stations and 59% of the dwell1 crossing 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
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

Extract

GBSIntake & Triage Agentgbs1h 8m1h 39m15Contract Lifecycle Management
2

Calendar

GBSIntake & Triage Agentgbs2h 46m5h 46m21Contract Lifecycle Management
3

Alert owner

GBSIntake & Triage Agentgbs2h 25m5h 19m38Contract Lifecycle Management
4

Escalate breach risk

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

HumanDirector, Commercial Contractspolicy4h 26m9h 21m1Contract 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%
2,484 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 gates315 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
11,012.4h
2,484 items at 266 minutes of decision each.
Agent time a week
15,690.6h
379 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 12.6h of headroom.
Stations without a person
75%
1 gate left on 4 stations.
Where an item spends its time
41% waiting on a person
59% in the agent lane
An item now takes 645 minutes of worked time end to end against 645 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 Obligation Monitoring

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

now Extract · Intake & Triage Agent · 1.1 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 16 hrs

now Extract · Intake & Triage Agent · 1.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

3 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.

1 systems attributed

0 of 1 returning records

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

4 of 4 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Contract Lifecycle Orchestrator
That orchestrator’s remit
Owns contract work end to end inside Legal. Runs 3 lines across 20 stations, drains the repeatable share into the LEGAL tower, and holds 5 human gates.
Accountable person
Director, Commercial Contracts
Sub-function
Contract Lifecycle
Shared spine tower
legal
Hand-over points
None — this service stays inside its function

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.