LensReading which lens this session carries.
The catalogueAdministrationEnvironment Health & SafetyJudgment

Service AD8C

Safety Doctrine Review

Runs judgment. Starts when a leadership team frames the question. 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

112 in flight right now.

Stations

6

1 person · 5 agent · 0 spine

Agent share of steps

83%

Autonomy on this service is set at 50% against a ceiling of 54%.

Decisions a person makes

1

Held by Head of EHS.

Touchless

11%

Share of runs that complete without anybody opening them.

Timetable against actual

640.3h

Actual 585.5h, 54.8h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 16% of the dwellAgent5 stations and 84% 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
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
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 question

AgentIncident Intake Agentstrategy50h 55m58h 40m42Group ERP — Financials
2

Gather evidence

AgentRoot Cause Agentstrategy39h 58m85h14Group ERP — Financials
3

Model options

AgentCorrective Action Agentstrategy16h 16m31h 39m1Group ERP — Financials
4

Draft position

AgentInspection Scheduling Agentstrategy59h 27m103h 53m32Group ERP — Financials
5

Challenge

AgentRegulatory Reporting Agentstrategy24h 1m40h 35m21Group ERP — Financials
6

Ratify

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

HumanHead of EHSpolicy35h 9m61h 37m2Group ERP — Financials

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 gates2 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
35.2h
1 items at 2,109 minutes of decision each.
Agent time a week
190.6h
11,437 minutes an item, which does not compete for a person.
Gate load
50%
Inside capacity, with 34.9h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
16% waiting on a person
84% in the agent lane
An item now takes 13,546 minutes of worked time end to end against 13,546 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 Safety Doctrine Review

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 9.4 days

now Frame question · Incident Intake Agent · 2.1 days

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 9.6 days

now Frame question · Incident Intake Agent · 2.1 days

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

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

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
EHS Orchestrator
That orchestrator’s remit
Owns safety case work end to end inside Administration. Runs 3 lines across 19 stations, drains the repeatable share into no shared tower, and holds 3 human gates.
Accountable person
Head of EHS
Sub-function
Environment Health & Safety
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

What this page is and is not

This is a catalogue of the modeled estate.