The Vehicles Delivered / Production report is the single most-run report in CCC ONE. It's also the report most likely to crash on any multi-shop or multi-year pull. If you're waiting 8 minutes per location and then copying into Excel, you are not doing it wrong — CCC is.
What's Actually Going On
Production reports hit the workfile, labor, parts, status-history, and closing tables in one query. CCC recomputes it fresh every time — no caching, no pre-aggregation. The more shops and months you add, the longer the join, until it times out.
Typical failure modes we see:
- 30+ shops × trailing 12 months → reliable crash.
- All-time production → impossible.
- Running the same report twice → same 8-minute wait. No cache.
- Comparing two date ranges side by side → you have to run it twice and paste it together.
What MSO Leadership Actually Wants
- Vehicles delivered per shop per week, trended over 12+ months.
- Revenue per RO, severity, and labor mix — side by side per shop.
- A same-day update, not a next-morning static PDF.
- The ability to filter by carrier, estimator, or damage severity without running a new report.
CCC's built-in production report was not designed to do any of this at MSO scale.
The Fix
Move the data. Nightly sync of CCC production data into a warehouse, pre-aggregated into a production table keyed by shop + date + carrier + estimator. From there, a dashboard renders in 1–2 seconds no matter how many shops or months you're looking at.
Typical build: 2 weeks once a CCC pipeline exists; 3–4 weeks if we're starting from scratch.
Related: Why CCC ONE Reports Take 10 Minutes and Real-Time Visibility Across 50+ Shops.