The Vehicles Delivered report is the single most-run report in CCC. It is also the one most likely to time out or crash the moment you try to pull more than one shop or more than a few months of data.
Why It Breaks
CCC recomputes Vehicles Delivered live, across workfiles, labor, parts, and close dates — with no caching and no pre-aggregation. At 20+ shops and 12 months, the join load exceeds what CCC's transactional database can serve. Typical failure modes:
- 30 shops × trailing 12 months → reliable crash.
- All-time delivered → impossible.
- Compare two periods side by side → run the report twice, paste it together by hand.
- Filter by carrier or severity → not supported in the stock report.
What MSOs Actually Need
- Weekly vehicles-delivered per shop over 12+ months, trended.
- Revenue per RO, severity, labor mix, all side-by-side across shops.
- A refresh that runs overnight, not a dashboard that blocks when a GM clicks Run.
- Slice by carrier, estimator, damage severity, or vehicle age without building a new report.
The Fix
Move the data. Nightly CCC sync into a warehouse, pre-aggregated vehicles-delivered fact table keyed by shop, date, carrier, and estimator. Dashboard renders in under 2 seconds regardless of date range. See the general architecture.
Typical build: 1–2 weeks on top of an existing CCC pipeline.