LensReading which lens this session carries.
The catalogueEngineeringEngineering AnalyticsAnalytical

Service EN11A

Monthly Engineering Read

Runs analytical. Starts when the reporting period closes. It runs 83 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 2 of them on the shared spine.

Runs a week

83

132 in flight right now.

Stations

6

1 person · 3 agent · 2 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Director, Engineering Analytics.

Touchless

75%

Share of runs that complete without anybody opening them.

Timetable against actual

168.1h

Actual 208.6h, 40.5h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 23% of the dwellAgent3 stations and 56% of the dwellShared spine2 stations and 21% of the dwell3 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
Product Lifecycle Management
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

Ingest

GBSDelivery Metrics Agentgbs1h 57m3h 52m37Group ERP — Materials and Inventory
2

Model delivery metrics

AgentCycle Time Agentworkflow12h 57m21h 53m5Configuration Management Database
3

Detect trend

AgentCost per Service Agentworkflow3h 14m5h 4m28Group ERP — Materials and Inventory
4

Draft readout

AgentReliability Trend Agentworkflow5h 17m7h 1m11Product Lifecycle Management
5

CTO 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 Analyticspolicy8h 56m11h 16m6Group ERP — Materials and Inventory
6

Publish

GBSDelivery Metrics Agentgbs5h 57m11h 53m45Group 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%
83 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 gates22 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
741.5h
83 items at 536 minutes of decision each.
Agent time a week
2,437.4h
1,762 minutes an item, which does not compete for a person.
Gate load
96%
Inside capacity, with 28.5h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
23% waiting on a person
77% in the agent lane
An item now takes 2,298 minutes of worked time end to end against 2,298 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 Monthly Engineering 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.

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

now Ingest · Delivery Metrics Agent · 1.9 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 3.0 days

now Ingest · Delivery Metrics Agent · 1.9 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.

3 systems attributed

0 of 3 returning records

The system register

Group ERP — Materials and Inventory

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

modeled

4 of 6 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 6 stations attributed here · read only

Product Lifecycle Management

Siemens Teamcenter · engineering · inbound · high

modeled

1 of 6 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

Cost per Service ReadEN11BMeasurement Doctrine PositionEN11C

What this page is and is not

This is a catalogue of the modeled estate.