If you're here, you probably just clicked "Run" on a WIP report in CCC ONE and either watched it spin for 10 minutes or crash outright. This is normal. It is also fixable.
Why This Report Specifically Breaks
WIP is one of the heaviest queries CCC can run. Every open RO at every location, joined to labor, parts, sublet, and status history, aggregated into aging buckets. CCC's transactional database is not built for that kind of read pattern — so:
- Single-shop + current month → tolerable (30–60 seconds).
- All shops + current month → 5–10 minutes if you're lucky.
- Multi-shop + trailing 12 months → timeout or crash.
- All-time WIP → effectively impossible.
The Three Things MSOs Actually Need
- WIP aging buckets by shop (0–7, 8–14, 15–30, 30+ days) with dollar value per bucket.
- Daily change — what moved into 30+ days since yesterday, flagged automatically.
- Cross-shop comparison — which location is accumulating WIP fastest right now.
None of those are available out of the box, at MSO scale, from CCC's built-in WIP report.
The Fix
The fix is the same pattern that solves every CCC report problem: move the data out of CCC's transactional system and into a warehouse built for reads. Nightly sync, pre-aggregated tables, dashboard rendered in under two seconds. We wrote up the general architecture here.
Specifically for WIP, we build:
- A daily-updated WIP table with aging bucket, dollar value, shop, estimator, carrier, and last-activity date.
- A single dashboard page — all shops, all buckets, one view.
- An automated alert whenever an RO crosses the 30-day line.
- A daily email summary to leadership with net-new WIP and aging-bucket changes.
Typical build: 1–2 weeks on top of an existing CCC data pipeline.
Also worth reading: WIP Aging: The Hidden Cashflow Killer.