ERP & MRP Planning worked example
Finite Schedule Utilization at 99% target finite utilization: a worked example
What does the result look like when target finite utilization reaches 99%? The full calculation is worked below with real intermediate numbers. a finite scheduler needs to see whether a detailed schedule overloads capacity
The inputs for this scenario
- Loaded finite schedule hours: 390 hr (unchanged)
- Finite available capacity hours: 430 hr (unchanged)
- Target finite utilization: 99 % (raised for this scenario; the documented default is 88)
Working through the calculation
- Applying the documented formula (Finite schedule utilization = loaded finite schedule hours ÷ finite available capacity hours × 100) to the inputs above produces each figure below.
- At this operating point the engine returns 90.7 % for finite schedule utilization, the number this scenario is built around.
- At this operating point the engine returns 8.3 points for gap to finite utilization target.
- At this operating point the engine returns 390 hr for loaded finite schedule hours.
- At this operating point the engine returns 430 hr for finite available capacity hours.
How this compares with the baseline
- Against the tool's baseline example, where target finite utilization sits at 88% and the headline result is 90.7 %, this scenario lands almost exactly on the baseline at 90.7 %.
- A figure at this level is achievable when target finite utilization is genuinely sustained, not just peaked for a shift. It treats all loaded hours as equally valuable and assumes your finite available capacity is accurate; stale calendars, unlogged downtime, or optimistic setup times will make the resource look more available than it really is.
Results at a glance
- Finite schedule utilization: 90.7 % (headline result)
- Gap to finite utilization target: 8.3 points
- Loaded finite schedule hours: 390 hr
- Finite available capacity hours: 430 hr
Run it with your numbers
- Every input above is editable in the live Finite Schedule Utilization calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.