Skip to main content

SPADANA / ROI

How much time could you save?

Start with three numbers. Add financial assumptions only if you need ROI.

Machine minutes released / program

24

Machine hours released / year

700

Example inputs — replace with your measured times. Not a guarantee.

Time savings & ROI scenario

Your preparation time

Count only preparation that stops production. Exclude saved-program reloads and unchanged physical setup; use 0 for fully offline work.

Work scheduleNumber of machines: 1 · Shifts / day: 1 · Hours / shift: 8 · Working days / year: 250
Operator effortActive labor person-minutes before / event: 25 · Active labor person-minutes after / event: 1

Active person-minutes, separate from machine time. Do not add the two savings together.

Labor person-hours released / year: 700

Add a financial estimate

Time saved is not automatically money saved. Choose one route.

Calculation details
Eligible events / year
1,750
Machine hours released / year
700
Labor person-hours released / year
700

Events/year = events/machine/shift × machines × shifts × days. Each saved-hours figure = events × its own (before − after) minutes ÷ 60. Cash benefit uses avoidable hours × avoidable rates. Output benefit uses the lower of realizable capacity and additional demand × contribution. Period ROI = (period benefits − all period costs) ÷ all period costs. Hours are never rounded before valuation. Labor hours and machine hours overlap and must not be added together.

Assumptions & definitions

Illustrative inputs, not measured results. Replace them with your plant data. This is a vendor-provided scenario, not a guarantee or independent assessment.

Count only events requiring new or revised programming/preparation. Exclude repeat jobs that simply reload a saved program. Frequency and times are per machine; use comparable machines or assess each group separately.

Machine time: only minutes when preparation blocks production (zero for fully offline work). Labor: total active person-minutes across the people involved; exclude passive waiting. Compare the same tasks before/after, including review and corrections. The 1-minute example covers software preparation, not fixtures, calibration or the entire physical changeover. Negative released hours mean additional work or machine occupation, not a saving. Labor and machine changes can have opposite signs.

Choose one financial path to avoid counting the same released hours twice. Capacity-only mode makes no monetary claim.

One page, in English. No contact details required.

Email a copy
Email assessment (English PDF)
Product demonstration

The video illustrates software preparation. Financial results depend on your measured workflow and the assumptions entered below.