Microgrid & Distributed Energy Equipment worked example
Service Parts Buffer with daily spare parts usage of 3,000 parts / day: a worked example in microgrid & distributed energy equipment
What does the result look like when daily spare parts usage reaches 3,000 parts / day? The full calculation is worked below with real intermediate numbers. Use it when a microgrid and distributed energy spare parts pool is being sized for a service contract or uptime commitment.
The inputs for this scenario
- Daily spare parts usage: 3,000 parts / day (raised for this scenario; the documented default is 1,200)
- Replenishment lead time: 85 days (unchanged)
- Safety stock: 1.1 parts (unchanged)
Working through the calculation
- Applying the documented formula (Spare parts cycle stock = daily spare parts usage × replenishment lead time) to the inputs above produces each figure below.
- At this operating point the engine returns 32.09 days for protected days of supply, the number this scenario is built around.
- At this operating point the engine returns 35.29 days for unprotected days.
- At this operating point the engine returns 3,000 pieces for inventory.
- At this operating point the engine returns 85 pieces / day for daily usage.
How this compares with the baseline
- Against the tool's baseline example, where daily spare parts usage sits at 1,200 parts / day and the headline result is 12.83 days, this scenario comes in 150% above the baseline at 32.09 days.
- A figure at this level is achievable when daily spare parts usage is genuinely sustained, not just peaked for a shift. It uses a single average daily usage; bursty failures or a recall-driven demand spike will exhaust a buffer sized on the mean, so stress-test high-criticality parts against peak usage.
Results at a glance
- Protected days of supply: 32.09 days (headline result)
- Unprotected days: 35.29 days
- Inventory: 3,000 pieces
- Daily usage: 85 pieces / day
Run it with your numbers
- Every input above is editable in the live Service Parts Buffer calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.