LensReading which lens this session carries.
The catalogueLegalRegulatory AffairsTransactional

Service LG5A

Regulatory Change Response

Runs transactional. Starts when a request lands in the queue. It runs 5,001 times a week across 7 stations. One of those stations stops for a person and 6 are done by an agent, 1 of them on the shared spine.

Runs a week

5,001

204 in flight right now.

Stations

7

1 person · 5 agent · 1 spine

Agent share of steps

86%

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

Decisions a person makes

1

Held by VP Regulatory Affairs.

Touchless

67%

Share of runs that complete without anybody opening them.

Timetable against actual

7.9h

Actual 9.9h, 2.0h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 43% of the dwellAgent5 stations and 53% of the dwellShared spine1 station and 4% 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
Document and Matter Management
Contract Lifecycle Management
Contract Lifecycle Management
Document and Matter 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

Detect change

GBSRegulatory Affairs Orchestratorgbs53m1h 8m39Contract Lifecycle Management
2

Assess impact

AgentImpact Assessment Agentworkflow30m59m36Contract Lifecycle Management
3

Map affected processes

AgentSubmission Drafting Agentworkflow2h 26m5h 25m22Document and Matter Management
4

Draft response plan

AgentRegulator Correspondence Agentworkflow2h 21m3h 18m32Contract Lifecycle Management
5

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 Affairspolicy8h 56m11h 58m8Contract Lifecycle Management
6

Assign owners

AgentRegulatory Stance Agentworkflow2h 46m4h 10m45Document and Matter Management
7

Track closure

AgentRegulatory Affairs Orchestratorworkflow2h 57m3h 40m22Contract 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%
5,001 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 gates1277 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
44,675.6h
5,001 items at 536 minutes of decision each.
Agent time a week
59,428.6h
713 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 19.4h of headroom.
Stations without a person
86%
1 gate left on 7 stations.
Where an item spends its time
43% waiting on a person
57% in the agent lane
An item now takes 1,249 minutes of worked time end to end against 1,249 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 Change Response

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.

7 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

7 stations, nothing waiting, nothing sent back

0 min of 21 hrs

now Detect change · Regulatory Affairs Orchestrator · 53 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 38 hrs

now Detect change · Regulatory Affairs Orchestrator · 53 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.

2 systems attributed

0 of 2 returning records

The system register

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

5 of 7 stations attributed here · would write back

Document and Matter Management

iManage · legal · inbound · medium

modeled

2 of 7 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

Regulator SubmissionLG5BRegulatory Stance PositionLG5C

What this page is and is not

This is a catalogue of the modeled estate.