How do I do capacity planning with iDBQuery?
Ask iDBQuery 'Do we have enough capacity to meet next month's demand by team?' It compares projected workload to available hours or units across your data, returns the surplus or shortfall per team as a chart, and cites each figure back to its source rows.
Capacity planning checks whether your available resources, people, machines, or fulfilment slots, can meet expected demand, so you can hire, shift, or defer before you hit a wall. iDBQuery lets you model it against real data instead of a static spreadsheet.
- You'd ask iDBQuery: 'Compare next month's forecast demand to available capacity by team, and show where we are short or have slack.'
- It aligns projected workload with available hours or units, computes the gap per team or line, and returns a chart plus a table flagging shortfalls.
- Each figure is cited to its source rows, so 'the fulfilment team is 120 hours short' traces to the demand and roster records used.
The payoff is scenario questions in one thread: 'What if demand rises 15%?' or 'Which week is the tightest?' iDBQuery keeps context and recalculates. Because demand may come from a sales forecast or order book and capacity from an HR or operations system, the one live model joins them with no ETL, and it shows its SQL so a planner can adjust assumptions. Save it as a live report for the operations review, and let the Analyst agent surface the periods and teams most at risk of being overloaded, with the rows behind each warning. This builds on demand forecasting and utilization analysis.
Updated 2026-06-22