LensReading which lens this session carries.
The catalogueEngineeringEngineering AnalyticsAnalytical

Service EN11B

Cost per Service Read

Runs analytical. Starts when a leader asks the question. It runs 52 times a week across 4 stations. One of those stations stops for a person and 3 are done by an agent, 1 of them on the shared spine.

Runs a week

52

40 in flight right now.

Stations

4

1 person · 2 agent · 1 spine

Agent share of steps

75%

Autonomy on this service is set at 63% against a ceiling of 88%.

Decisions a person makes

1

Held by Director, Engineering Analytics.

Touchless

62%

Share of runs that complete without anybody opening them.

Timetable against actual

171.7h

Actual 142.8h, 28.9h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 31% of the dwellAgent2 stations and 43% of the dwellShared spine1 station and 26% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Materials and Inventory
Configuration Management Database
Group ERP — Materials and Inventory
Group ERP — Materials and Inventory
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

Attribute cloud spend

GBSDelivery Metrics Agentgbs11h 42m21h 58m24Group ERP — Materials and Inventory
2

Rank

AgentCycle Time Agentworkflow14h 40m28h 33m15Configuration Management Database
3

Draft recommendation

AgentCost per Service Agentworkflow5h 5m9h 48m1Group ERP — Materials and Inventory
4

Owner review

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

HumanDirector, Engineering Analyticspolicy14h 3m23h 23m0Group ERP — Materials and Inventory

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%
52 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 gates21 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
730.6h
52 items at 843 minutes of decision each.
Agent time a week
1,635.4h
1,887 minutes an item, which does not compete for a person.
Gate load
99%
Inside capacity, with 4.4h of headroom.
Stations without a person
75%
1 gate left on 4 stations.
Where an item spends its time
31% waiting on a person
69% in the agent lane
An item now takes 2,730 minutes of worked time end to end against 2,730 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 Cost per Service Read

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.

4 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

4 stations, nothing waiting, nothing sent back

0 min of 46 hrs

now Attribute cloud spend · Delivery Metrics Agent · 12 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 3.7 days

now Attribute cloud spend · Delivery Metrics Agent · 12 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.

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

Group ERP — Materials and Inventory

SAP S/4HANA MM · supply · bidirectional · high

modeled

3 of 4 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 4 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Engineering Analytics Orchestrator
That orchestrator’s remit
Owns analysis work end to end inside Engineering. Runs 3 lines across 15 stations, drains the repeatable share into the DATA-ANALYTICS tower, and holds 3 human gates.
Accountable person
Director, Engineering Analytics
Sub-function
Engineering Analytics
Shared spine tower
data-analytics
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Monthly Engineering ReadEN11AMeasurement Doctrine PositionEN11C

What this page is and is not

This is a catalogue of the modeled estate.