End-to-end outcomes · one chain
OI-RTR-0172 — Req to receipt
One requisition followed from a requisition is raised against a cost center to the goods or service is receipted against the order, across every function and tower it touched. more
State
Closed
Every stage of the service was found and the last one finished inside the sampled week.
Chain cycle
2.6 d
Wall clock, first stage start to last stage end
Of which waiting
2.4 d
92% of the chain was queue, not work
Cost to serve
$4.56
0 touches over 3 stages
A person intervened
0×
No stage on this chain needed a person
Match confidence
0.92
Mixed
What this chain is, and how sure we are it is one chain
Identity, counterparty and the correlation key
The unit
Barenholt Technology
India · Asia Pacific · INR
Started Wed, Aug 12, 17:08, ended Sat, Aug 15, 06:55.
How the stages were joined
Mixed · 0.92
The chain used more than one matching regime across its stages, so it is only as strong as its weakest join.
A chain is only as sure as its weakest join, so the figure above is the minimum across the 2 joins below, not their average.
How much of the service ran
3 / 3
2 functions · 1 tower
Every stage the service defines was found for this unit.
The chain, stage by stage
3 stages · 2.4 d waiting · 5.1 h in work
01Requisition raised
CG-S2P-003008Purchase requisitions2p-suiteProcurementS2P
The chain starts here. more
In work
2.5 h
Touches
0
Handling
touchless
Join
Origin
On the document
$11,640
Handoff wait before this stage: 21.1 h — nothing was being done to the requisition for that time.
02Order placed
CG-S2P-002931Purchase ordererp-mmProcurementS2P
The document crosses from s2p-suite into erp-mm, where no reference survives. more
In work
33 min
Touches
0
Handling
touchless
Join
Inferred 0.92
On the document
$36,685
Handoff wait before this stage: 35.5 h — nothing was being done to the requisition for that time.
03Receipt posted
CG-S2P-002600Goods receipterp-mmSupply ChainS2P
Both documents live in erp-mm, so the system reference carries across and the link is keyed.
In work
2.0 h
Touches
0
Handling
touchless
Join
Keyed 1.00
On the document
$4,068
The amounts in the right-hand column are what each document carried, and they are deliberately not added up — the same money is written down once at each of the 3 stages this requisition passed through. This service counts value once, at order placed, which puts $36,685 against this chain.
Where a person intervened
0 of 3 stages were not touchless
No stage on this chain was handled by a person — every one ran touchless. That is unusual for req to receipt: across its complete chains the median is 1 stage with a person in it.
What the time and the money went on
The chain decomposed
Waiting
2.4 d
92% of elapsed time
In work
5.1 h
8% of elapsed time
Waiting and work are an exhaustive split of the 2.6 d this chain took — every hour is in one bucket or the other. The longest single wait was 35.5 h before receipt posted.
Cost to serve, $4.56
0 touches at 11 minutes of loaded time each$0.00
3 stages of inference and system cost$4.56
Cost to serve is modeled from the touches the ledger recorded, not billed from a timesheet. more
No stage on this chain raised an exception.
The same chain for the whole week, as a distribution
96 complete req to receipt chains, 10–16 August 2026
this chain sits at the 39th percentile
3
17
22
26
17
7
2
1
1
26.8 hten equal bands of chain cycle time6.6 d
Median chain
2.9 d
p25 2.3 d · p75 3.4 d
Slowest tenth
3.9 d
worst seen 6.6 d
Median waiting
2.4 d
82% of the median chain is queue
Median cost
$15.19
p90 $47.09
The mean of 2.9 d sits below the median of 2.9 d, which is why the distribution is drawn rather than reported as an average: the gap between the median and the slowest tenth is 22.1 h, and it is that tail, not the average, that customers of this service actually feel. The commitment is 96 hours; 135 of the chains started early enough to be judged broke it.
The ledger behind these chains is one week, 10 to 16 August 2026, which is 168 hours. A chain that had not finished when the week ended is open, not late: the week simply stopped watching it. A chain whose commitment falls after the end of the week could never have been seen to miss, so its service level reads not measurable rather than holding. Nothing on these pages should be read as a monthly or annual attainment. This chain both started and finished inside that week, so its cycle time is a measurement.