LensReading which lens this session carries.
The catalogueAdministrationRecords & Information ManagementTransactional

Service AD6A

Classify to Dispose

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

Runs a week

2,484

173 in flight right now.

Stations

7

2 person · 2 agent · 3 spine

Agent share of steps

71%

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

Decisions a person makes

2

Held by Chief Records Officer.

Touchless

71%

Share of runs that complete without anybody opening them.

Timetable against actual

11.0h

Actual 12.5h, 1.5h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 67% of the dwellAgent2 stations and 7% of the dwellShared spine3 stations and 25% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
IT Service 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

Ingest

AgentClassification Agentworkflow23m29m35Group ERP — Financials
2

Classify

GBSClassification Agentgbs1h 36m2h 56m19Group ERP — Financials
3

Apply retention

GBSClassification Agentgbs40m56m39Group ERP — Financials
4

Hold check

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

HumanChief Records Officerpolicy7h 25m17h 35m6Group ERP — Financials
5

Disposition approve

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

HumanChief Records Officerpolicy1h 14m2h 17m5Group ERP — Financials
6

Execute

GBSClassification Agentgbs1h2h 6m34Group ERP — Financials
7

Certificate

AgentRecords Policy Agentworkflow31m44m35IT Service 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 2
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates614 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
21,486.6h
2,484 items at 519 minutes of decision each.
Agent time a week
10,350h
250 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 3.4h of headroom.
Stations without a person
71%
2 gates left on 7 stations.
Where an item spends its time
67% waiting on a person
33% in the agent lane
An item now takes 769 minutes of worked time end to end against 769 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 Classify to Dispose

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

now Ingest · Classification Agent · 23 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 40 hrs

now Ingest · Classification Agent · 23 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

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

6 of 7 stations attributed here · would write back

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

1 of 7 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Records Orchestrator
That orchestrator’s remit
Owns record set work end to end inside Administration. Runs 4 lines across 23 stations, drains the repeatable share into the R2R tower, and holds 5 human gates.
Accountable person
Chief Records Officer
Sub-function
Records & Information Management
Shared spine tower
r2r
Hand-over points
None — this service stays inside its function

Other services in this sub-function

3 alongside this one

What this page is and is not

This is a catalogue of the modeled estate.