407. Ready Rate
407.1. Ready Rate (Time-based service level)
The probability that on-hand inventory is positive at any random moment in time. Counts time, not cycles or units.
407.1.1. How it differs from CSL and fill rate
| Metric | Counts | What it means | Sample question |
| CSL () | Cycles | P(no stockout in this cycle) | “What fraction of cycles have a stockout?” |
| Fill rate () | Units | E[demand met] / E[demand] | “What fraction of unit demand is met?” |
| Ready rate () | Time | P(stock > 0 at time ) | “What fraction of time are we in stock?” |
All three are “service level” but answer different questions.
407.1.2. Ready rate = fraction of time with positive stock
In steady state, the inventory level over a (Q, r) cycle alternates:
- Positive on-hand during most of the cycle.
- Zero on-hand during any stockout window (the gap from when stock hits zero to when the order arrives).
If is the average cycle length and is the expected stockout duration per cycle:
For (Q, r) with :
The same expression as fill rate! Under continuous-demand assumptions, ready rate and fill rate coincide. They diverge only when stockout duration and shortage size aren’t proportional (e.g., very lumpy demand patterns).
407.1.3. When ready rate is the right metric
Use ready rate when:
- Server availability: a service desk that can take orders only when stock is on hand. “Are we ready to serve?”
- Compliance: regulations require a minimum % of time in stock (some pharmacies, parts depots).
- Multi-product systems: aggregate ready rate = average of individual ready rates, easier to manage.
Don’t use ready rate when shortages have widely varying severity — use fill rate to capture how much demand was unmet rather than just whether you were stocked out at the moment.
407.1.4. Approximate equivalence to fill rate
Under standard assumptions (continuous time, smooth demand, no lumpy bursts):
In practice, choose whichever is more interpretable for your stakeholders:
- Customer-facing metrics → fill rate (units of unmet demand)
- Operations / compliance → ready rate (time in stock)
- Executive reporting → CSL (binary cycle outcome, simpler)
Example
Given (same (Q, r) policy as CSL/fill rate examples):
- , , , /day
- Reorder point set for CSL = 95%: , .
Step 1 — expected stockout duration per cycle
Stockout occurs only if . Expected shortage in units:
Convert to time: shortage units, daily demand 33, so:
Step 2 — ready rate
Step 3 — compare metrics
At the same reorder point :
- CSL: 95% (5% of cycles have a stockout)
- Fill rate: 99.95% (0.05% of unit demand unmet)
- Ready rate: 99.95% (in stock 99.95% of the time)
Fill rate ≈ ready rate (both unit/time-weighted). CSL is the strict outlier — it’s an event count, blind to severity.
Two stakeholder views:
- CFO: “We hit a 5% stockout-cycle rate at this safety stock level — is that too lenient?”
- Operations: “We’re shipping 99.95% of orders; nobody complains.” — fill rate / ready rate.
Both views are correct; just different denominators.