LensReading which lens this session carries.
The catalogueLegalCorporate & GovernanceTransactional

Service LG3B

Statutory Filing

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

Runs a week

625

161 in flight right now.

Stations

6

1 person · 1 agent · 4 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Company Secretary.

Touchless

65%

Share of runs that complete without anybody opening them.

Timetable against actual

25.0h

Actual 23.8h, 1.2h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 35% of the dwellAgent1 station and 3% of the dwellShared spine4 stations and 62% 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

Detect due date

GBSEntity Register Agentgbs1h 18m1h 56m18Contract Lifecycle Management
2

Assemble

GBSEntity Register Agentgbs3h 5m6h 23m39Contract Lifecycle Management
3

Verify

AgentMinute Drafting Agentworkflow21m41m35Contract Lifecycle Management
4

Officer sign

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

HumanCompany Secretarypolicy4h 1m6h 51m3Contract Lifecycle Management
5

File

GBSEntity Register Agentgbs1h 2m2h 26m32Contract Lifecycle Management
6

Evidence

GBSEntity Register Agentgbs1h 51m3h 40m34Contract 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%
625 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 gates72 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
2,510.4h
625 items at 241 minutes of decision each.
Agent time a week
4,760.4h
457 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 9.6h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
35% waiting on a person
65% in the agent lane
An item now takes 698 minutes of worked time end to end against 698 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 Statutory Filing

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

now Detect due date · Entity Register Agent · 1.3 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 28 hrs

now Detect due date · Entity Register Agent · 1.3 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

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
Corporate Secretariat Orchestrator
That orchestrator’s remit
Owns corporate action work end to end inside Legal. Runs 3 lines across 18 stations, drains the repeatable share into the LEGAL tower, and holds 4 human gates.
Accountable person
Company Secretary
Sub-function
Corporate & Governance
Shared spine tower
legal
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Board Meeting CycleLG3AAuthority Register UpdateLG3C

What this page is and is not

This is a catalogue of the modeled estate.