Coatings, Inks & Specialty Chemical Production worked example

Resin Usage with resin or binder charge rate of 280 lb / hr: a worked example in coatings, inks & specialty chemical production

What does the result look like when resin or binder charge rate reaches 280 lb / hr? The full calculation is worked below with real intermediate numbers. planning resin pulls, checking binder usage, or comparing resin-rich formulation options

The inputs for this scenario

  • Resin or binder charge rate: 280 lb / hr (raised for this scenario; the documented default is 110)
  • Resin charge or cook time: 4 hr (unchanged)
  • Resin cost per pound: 3.85 $ / lb (unchanged)

Working through the calculation

  • Applying the documented formula (Resin Usage consumed = resin or binder addition rate × resin addition time) to the inputs above produces each figure below.
  • At this operating point the engine returns 1,120 lb for resin usage consumed, the number this scenario is built around.
  • At this operating point the engine returns 4,312 $ for resin usage cost.
  • At this operating point the engine returns 4 hr for resin addition time.
  • At this operating point the engine returns 3.85 $ / unit for resin cost per pound.

How this compares with the baseline

  • Against the tool's baseline example, where resin or binder charge rate sits at 110 lb / hr and the headline result is 440 lb, this scenario comes in 155% above the baseline at 1,120 lb.
  • A figure at this level is achievable when resin or binder charge rate is genuinely sustained, not just peaked for a shift. It assumes a steady charge rate and full incorporation, so it won't capture line losses, off-ratio additions, or resin held up in the reactor or transfer lines.

Results at a glance

  • resin usage consumed: 1,120 lb (headline result)
  • resin usage cost: 4,312 $
  • resin addition time: 4 hr
  • resin cost per pound: 3.85 $ / unit

Run it with your numbers

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

Last reviewed 2026-05-12.