Purpose

Help teams identify, measure, and reduce the time it takes to change from one job, part, or setup to another — using data captured in Caddis to drive structured improvements and accountability.

“Setup times dropped from 14 minutes to 9 just by focusing weekly and assigning ownership.”

— Manufacturing Engineer, Aluminum Manufacturer (LeClaire Meeting)

Outcomes

Tools You’ll Use in Caddis:

Timeline:

4–6 weeks initial improvement sprint, then ongoing weekly follow-up

Who’s Involved:

Step-by-Step Execution

Step 1: Tag All Active Runs by Job or Part

Make sure every active run in Caddis includes tags like:

This allows you to compare average setup times by:

Caddis tags are applied at the start of an active run, grouped by category. Use these to build production context.

Step 2: Identify Setup Events Through Downtime Analysis

Use Caddis to locate excessive downtime periods between tagged runs:

Use this to:

Step 3: Create a Changeover Checklist

Use 5 Why’s to identify barriers in long setups:

Design a standard checklist for pre-setup and execution:

Use root cause findings to define new checklist items.

Step 4: Assign Setup Ownership and Start Weekly Standups

Each high-variation setup should have an owner:

Start a 30-minute weekly review meeting:

Attendees: Operators, Caddis Champion, Production Lead

Agenda:

  1. Review average and longest setup times by job
  2. Investigate any excessive events
  3. Identify one improvement for the next week
  4. Validate checklist use and prep actions

Build weekly momentum and celebrate wins.

Step 5: Add a PM if the Setup Delay Was Mechanical

If a root cause is related to:

Use your 5 Why’s worksheet to:

Example: "Fixture bolts loose" → PM every 60 hours: Inspect bolt torque

Metrics to Track

Metric Why It Matters
Avg Setup Time Per Part/td> Less than 10 minutes
Excessive Setups Zero repeat occurences
Setup Time Variation by Operator Decreasing trend
Pms created from setup issues 1+ per month

Common Challenges (and Solutions)

Challenge Solutions
We don't know when changeovers start Use run end + tag transitions to infer setups
Setups vary widely by shift Tag by Operator + Job to identify gaps
Checklist isn’t used consistently” Review usage weekly and re-train if neccessary

What Success Looks Like