LensReading which lens this session carries.
The catalogueLegalRegulatory AffairsTransactional

Service LG5B

Regulator Submission

Runs transactional. Starts when a threshold is crossed. It runs 7,243 times a week across 6 stations. 2 of those stations stop for a person and 4 are done by an agent, none of them on the shared spine.

Runs a week

7,243

83 in flight right now.

Stations

6

2 person · 4 agent · 0 spine

Agent share of steps

67%

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

Decisions a person makes

2

Held by VP Regulatory Affairs.

Touchless

66%

Share of runs that complete without anybody opening them.

Timetable against actual

10.7h

Actual 8.1h, 2.6h under the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 46% of the dwellAgent4 stations and 54% of the dwellShared spine0 stations and 0% of the dwell2 crossings 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
Contract Lifecycle Management
Document and Matter 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

Assemble

AgentHorizon Scanning Agentworkflow2h 3m4h 34m17Contract Lifecycle Management
2

Draft

AgentImpact Assessment Agentworkflow2h 34m3h 20m6Document and Matter Management
3

Counsel review

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 Affairspolicy3h 55m6h 51m0Contract Lifecycle Management
4

Officer sign

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 Affairspolicy2h 46m3h 36m0Contract Lifecycle Management
5

Submit

AgentChange Implementation Agentworkflow2h 22m4h 5m33Contract Lifecycle Management
6

Log

AgentRegulatory Stance Agentworkflow1h1h 46m27Document and Matter 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,243 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 gates1384 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
48,407.4h
7,243 items at 401 minutes of decision each.
Agent time a week
57,823.3h
479 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 32.6h of headroom.
Stations without a person
67%
2 gates left on 6 stations.
Where an item spends its time
46% waiting on a person
54% in the agent lane
An item now takes 880 minutes of worked time end to end against 880 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 Regulator Submission

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 Assemble · Horizon Scanning Agent · 2.0 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 34 hrs

now Assemble · Horizon Scanning Agent · 2.0 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.

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

4 of 6 stations attributed here · would write back

Document and Matter Management

iManage · legal · inbound · medium

modeled

2 of 6 stations attributed here · read only

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 ResponseLG5ARegulatory Stance PositionLG5C

What this page is and is not

This is a catalogue of the modeled estate.