Question 1

What is ProChangeover?

Accepted Answer

SMED-based changeover software for the shop floor. Operators follow a live digital task list, each step gets a timestamped sign-off, and every run produces a Gantt timeline. One shared execution record instead of paper and verbal handoffs.

Question 2

How long does setup take?

Accepted Answer

Most teams run the first live changeover within a day. Define products, map the task sequence for each product pair, start a run. Web app — no install, no IT project.

Question 3

Do operators need to learn new software?

Accepted Answer

No. Checklist UI: large taps, no login friction on the floor, no typing for standard execution. Works like paper — live and digital.

Question 4

Does it work on tablets?

Accepted Answer

Yes. Web app, no install. Tablets and desktops, with large touch targets and high-contrast status for the floor.

Question 5

How much does ProChangeover cost?

Accepted Answer

$49/month. Unlimited lines and changeovers, real-time sync, timestamped sign-off, run history, and a Gantt per completed run. No per-seat pricing.

Question 6

What is SMED?

Accepted Answer

Single Minute Exchange of Die — lean method to cut changeover time by separating internal tasks (machine must stop) from external (can run while producing), then converting internal to external where possible. Typical gains: 30–50%.

Question 7

What's the difference between internal and external changeover tasks?

Accepted Answer

Internal need the machine stopped (e.g. mould swap, certain setpoints). External can run while producing (staging tools, pre-heat, prep materials). SMED finds work that is unnecessarily internal and moves it out.

Question 8

How does ProChangeover implement SMED?

Accepted Answer

Task sequences per product pair. Right list on run start, enforced order, timestamp at each sign-off, Gantt of where time was lost. Use that data to classify internal vs external and tighten standards.

Question 9

Can we have different task lists for different product changeovers?

Accepted Answer

Yes. Separate sequences per product pair. The system picks the right list from the from/to products you select when the run starts.

Question 10

How do supervisors know a changeover is running long before it ends?

Accepted Answer

Live board shows all active changeovers. Delays flag as they happen — step, owner, device — without walking the floor.

Question 11

How does sign-off work?

Accepted Answer

Operators mark assigned steps complete. Timestamp, task, and role land on the run record. Gaps and late completes show on the timeline.

Question 12

Can operators leave notes during a run?

Accepted Answer

Yes. Plain-text comment before complete — e.g. torque took three passes. Timestamped on the task and run; visible in post-run review.

Question 13

What does the post-run Gantt show?

Accepted Answer

Task-level timeline: who, order, duration vs standard, missing overlap. Searchable across runs; filter by line and shift.

Question 14

Can we access historical records for audits?

Accepted Answer

Yes. Timestamped, searchable sign-off records — permanent and tamper-evident. Pull six-week-old runs in seconds.

Question 15

Can ProChangeover manage changeovers across multiple lines at the same time?

Accepted Answer

Yes. No line limit. One dashboard for all active changeovers — each with its own live board, progress, and delay flags.

Question 16

Our operators will not use an app. Is this realistic?

Accepted Answer

It is a checklist, not ERP. No typing for standard steps, no floor login friction. Common pre-rollout fear; post-rollout, teams often prefer it to paper because everyone sees the same board.

Question 17

Do we need to roll it out across all lines at once?

Accepted Answer

No. One line, one product pair, one shift. After a logged run and a timeline, decide whether to expand.

Question 18

What if our changeovers are too different to standardise?

Accepted Answer

Product-pair config handles that. Each from→to gets its own list, sequence, and specs — not one template for every switch.

Question 19

What does getting started look like — is there onboarding support?

Accepted Answer

Self-serve: products, first pair, first run — usually live in a day. Optional onboarding call via contact after signup. No IT project, no implementation fee.

Question 20

How do we measure whether changeover time actually improved?

Accepted Answer

Gantt sets a baseline after run one. Later runs compare automatically — by step, role, and shift — so you see if standard changes stick.

Question 21

How much time do manufacturers typically save?

Accepted Answer

SMED often cuts 30–50%. ProChangeover shows where time goes and whether fixes hold. Larger early gains when there was no prior standard.

Question 22

What is OEE and how does changeover time affect it?

Accepted Answer

Overall Equipment Effectiveness = Availability × Performance × Quality. Changeovers hit Availability. Cutting a 40-minute changeover to 25 on a line that switches twice per shift recovers 30 minutes of capacity every shift.

Question 23

How do we calculate what a slow changeover is costing us?

Accepted Answer

Overrun minutes × line output value per minute. Example: $500/hour line, 20 min over → ~$167 lost capacity per run. Task-level data shows which step drives the overrun.

Question 24

Does ProChangeover integrate with our ERP or MES?

Accepted Answer

Not yet — standalone web app. ERP/MES integration is on the roadmap; contact us if it is a must for evaluation.

Common questions about ProChangeover

Getting started

SMED and the methodology

Features

Adoption and rollout

ROI and measurement

Integration and security

Run your first standardized changeover this week.