LensReading which lens this session carries.
The catalogueLegalRegulatory AffairsJudgment

Service LG5C

Regulatory Stance Position

Runs judgment. Starts when the annual doctrine review opens. It runs 1 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, none of them on the shared spine.

Runs a week

1

133 in flight right now.

Stations

6

1 person · 5 agent · 0 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by VP Regulatory Affairs.

Touchless

35%

Share of runs that complete without anybody opening them.

Timetable against actual

372.6h

Actual 278.7h, 93.9h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 34% of the dwellAgent5 stations and 66% 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
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

Frame

AgentHorizon Scanning Agentstrategy32h 22m47h 56m37Contract Lifecycle Management
2

Gather precedent

AgentImpact Assessment Agentstrategy68h 26m103h 47m15Contract Lifecycle Management
3

Model options

AgentSubmission Drafting Agentstrategy49h 41m113h 58m42Contract Lifecycle Management
4

Draft position

AgentRegulator Correspondence Agentstrategy31h 30m67h 10m6Contract Lifecycle Management
5

Challenge

AgentChange Implementation Agentstrategy63h 53m131h 5m29Contract Lifecycle Management
6

GC ratify

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

HumanVP Regulatory Affairspolicy128h 43m251h 16m4Contract 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%
1 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 gates4 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
128.7h
1 items at 7,723 minutes of decision each.
Agent time a week
245.9h
14,752 minutes an item, which does not compete for a person.
Gate load
92%
Inside capacity, with 11.3h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
34% waiting on a person
66% in the agent lane
An item now takes 22,475 minutes of worked time end to end against 22,475 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 Regulatory Stance Position

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.6 days

now Frame · Horizon Scanning Agent · 32 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 15.8 days

now Frame · Horizon Scanning Agent · 32 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

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
Regulatory Affairs Orchestrator
That orchestrator’s remit
Owns regulatory item 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
VP Regulatory Affairs
Sub-function
Regulatory Affairs
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

Regulatory Change ResponseLG5ARegulator SubmissionLG5B

What this page is and is not

This is a catalogue of the modeled estate.