LensReading which lens this session carries.
The catalogueSupply ChainSales & Operations PlanningAnalytical

Service SC3A

Monthly Planning Cycle

Runs analytical. Starts when a drift signal breaches tolerance. It runs 71 times a week across 8 stations. 2 of those stations stop for a person and 6 are done by an agent, none of them on the shared spine.

Runs a week

71

175 in flight right now.

Stations

8

2 person · 6 agent · 0 spine

Agent share of steps

75%

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

Decisions a person makes

2

Held by VP Integrated Business Planning.

Touchless

46%

Share of runs that complete without anybody opening them.

Timetable against actual

156.1h

Actual 174.1h, 18.0h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 45% of the dwellAgent6 stations and 55% of the dwellShared spine0 stations and 0% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Enterprise Data Warehouse
Group ERP — Materials and Inventory
Supply and Demand Planning
Product Lifecycle Management
Indirect Tax Engine
Group ERP — Materials and Inventory
Group ERP — Materials and Inventory
Transportation 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

Consolidate plans

AgentScenario Modeling Agentworkflow4h 11m9h 21m33Enterprise Data Warehouse
2

Reconcile to financials

Hands over at finance

AgentGap Analysis Agentworkflow3h 15m5h 24m15Group ERP — Materials and Inventory
3

Model scenarios

AgentFinancial Reconciliation Agentworkflow14h 35m28h 35m33Supply and Demand Planning
4

Identify gaps

AgentMeeting Pack Agentworkflow5h 55m9h 8m13Product Lifecycle Management
5

Draft pack

AgentDecision Tracking Agentworkflow8h 45m11h 46m33Indirect Tax Engine
6

Executive review

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

HumanVP Integrated Business Planningpolicy20h 51m39h 10m6Group ERP — Materials and Inventory
7

Decisions

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

HumanVP Integrated Business Planningpolicy13h 13m21h 11m4Group ERP — Materials and Inventory
8

Track closure

AgentScenario Modeling Agentworkflow5h 25m10h 37m38Transportation 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%
71 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 gates70 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,418.7h
71 items at 2,044 minutes of decision each.
Agent time a week
2,989.1h
2,526 minutes an item, which does not compete for a person.
Gate load
99%
Inside capacity, with 31.3h of headroom.
Stations without a person
75%
2 gates left on 8 stations.
Where an item spends its time
45% waiting on a person
55% in the agent lane
An item now takes 4,570 minutes of worked time end to end against 4,570 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 Planning Cycle

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.

8 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

8 stations, nothing waiting, nothing sent back

0 min of 3.2 days

now Consolidate plans · Scenario Modeling Agent · 4.2 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 4.0 days

now Consolidate plans · Scenario Modeling Agent · 4.2 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.

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.

6 systems attributed

0 of 6 returning records

Group ERP — Materials and Inventory

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

modeled

3 of 8 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 8 stations attributed here · read only

Supply and Demand Planning

Kinaxis RapidResponse · supply · bidirectional · high

modeled

1 of 8 stations attributed here · would write back

Product Lifecycle Management

Siemens Teamcenter · engineering · inbound · high

modeled

1 of 8 stations attributed here · read only

Indirect Tax Engine

Vertex · tax · inbound · high

modeled

1 of 8 stations attributed here · read only

Transportation Management

Blue Yonder TMS · supply · inbound · medium

modeled

1 of 8 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Integrated Planning Orchestrator
That orchestrator’s remit
Owns planning cycle work end to end inside Supply Chain. Runs 3 lines across 17 stations, drains the repeatable share into the P2P tower, and holds 4 human gates.
Accountable person
VP Integrated Business Planning
Sub-function
Sales & Operations Planning
Shared spine tower
Not on the shared spine
Hand-over points
finance

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.