NPI, DFM/DFA & Engineering Change worked example

ECO Workload at 9.2% engineer utilization target: a worked example

Push engineer utilization target up to 9.2% and the picture changes. This example computes every intermediate figure at that operating point. Use it when eco workload in npi, dfm/dfa and engineering change is being sized against an asset rating.

The inputs for this scenario

  • Pending ECO hours in queue: 100 units (unchanged)
  • Change-board hours available per week: 1.2 units (unchanged)
  • Engineer utilization target: 9.2 % (raised for this scenario; the documented default is 8)

Working through the calculation

  • Applying the documented formula (Required eco workload load = eco workload demand รท eco workload utilization target) to the inputs above produces each figure below.
  • At this operating point the engine returns 120 hr for total load, the number this scenario is built around.
  • At this operating point the engine returns 13.04 hr / hr for hourly equivalent.
  • At this operating point the engine returns 100 hr for input load.
  • At this operating point the engine returns 1.2 x for load factor.

How this compares with the baseline

  • Against the tool's baseline example, where engineer utilization target sits at 8% and the headline result is 120 hr, this scenario lands almost exactly on the baseline at 120 hr.
  • It converts a pool of pending ECO hours and a utilization target into the total effective load required and the gap against available change-board capacity. The value of this scenario is the size of the gap it exposes: that gap, priced out over a year, is the budget you can justify spending to close it.

Results at a glance

  • Total load: 120 hr (headline result)
  • Hourly equivalent: 13.04 hr / hr
  • Input load: 100 hr
  • Load factor: 1.2 x

Run it with your numbers

  • Every input above is editable in the live ECO Workload calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.