Adhesives, Sealants & Industrial Bonding worked example

Sealant Usage with sealant dispense rate of 600 ml/hr or g/hr: a worked example in adhesives, sealants & industrial bonding

Push sealant dispense rate up to 600 ml/hr or g/hr and the picture changes. This example computes every intermediate figure at that operating point. a packaging engineer or maintenance lead needs to plan sealant quantity for a sealing job

The inputs for this scenario

  • Sealant dispense rate: 600 ml/hr or g/hr (raised for this scenario; the documented default is 240)
  • Sealing runtime: 6.5 hr (unchanged)
  • Sealant unit cost: 0.04 $ / ml or $ / g (unchanged)

Working through the calculation

  • Applying the documented formula (Sealant consumed = sealant dispense rate × sealing runtime) to the inputs above produces each figure below.
  • At this operating point the engine returns 3,900 ml or g for sealant consumed, the number this scenario is built around.
  • At this operating point the engine returns 137 $ for sealant material cost.
  • At this operating point the engine returns 6.5 hr for sealing runtime.
  • At this operating point the engine returns 0.04 $ / ml or $ / g for sealant unit cost.

How this compares with the baseline

  • Against the tool's baseline example, where sealant dispense rate sits at 240 ml/hr or g/hr and the headline result is 1,560 ml or g, this scenario comes in 150% above the baseline at 3,900 ml or g.
  • It multiplies your sealant dispense rate by sealing runtime to get total volume or mass consumed, then multiplies by unit cost to get the material spend. 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

  • Sealant consumed: 3,900 ml or g (headline result)
  • Sealant material cost: 137 $
  • Sealing runtime: 6.5 hr
  • Sealant unit cost: 0.04 $ / ml or $ / g

Run it with your numbers

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

Last reviewed 2026-05-12.