How To Onboard New Operators Using Caddis Data

Purpose

New operators often experience a steep learning curve. This playbook outlines how to incorporate Caddis data into your onboarding process to reduce variability, shorten ramp-up time, and support long-term accountability.

Outcomes

• Faster and smoother onboarding for new operators
• Standardized expectations based on real machine performance
• Improved first-time quality and reduced work
• Stronger connection between training and actual results

What Caddis Can Show a New Operator

• Real-time machine status and performance indicators
• Cycle counts and expected performance baselines
• Notes from prior shifts or operators
• PM tasks coming due on the equipment they run

Step-by-Step: Caddis-Enabled Operator Onboarding

Step-by-Step: Caddis-Enabled Operator Onboarding

1. Introduce Caddis During Orientation

• Walk the new hire through the Caddis dashboard and equipment views
• Explain the meaning of cycle count, run status, and alarms
• Emphasize how Caddis builds visibility and trust in production data

2. Set Baseline Expectations

• Showthe new operator historical cycle times or output expectations
• Use past Active Runs to demonstrate what "good" looks like
• Explain how tags like Operator, Part Number, and Job Number tie to output and     downtime

3. Pair with a Mentor Operator

• Encourage use of Caddis to review the last completed run on a machine
• Discuss any trends or performance gaps together
• Have the mentor show how to enter notes or complete a PM task if needed

4. Use Caddis to Reinforce Good Habits

• Ask new operators to review their own run performance each day
• Have team leads pull reports on tagged runs and discuss during end-of-week reviews
• Encourage proactive tagging (e.g., "Job1234", "SetupTime") to develop data awareness

5. Close the Loop with Feedback

• Review performance using Caddis at 30-, 60-, and 90-day onboarding checkpoints
• If needed, filter Active Runs by the new operator’s tag to evaluate their improvement
• Tie feedback to both hard metrics (e.g., cycle time) and qualitative notes (e.g., troubleshooting steps entered

‍