Insights and KPIs
The analytics dashboard — KPI cards, utilization and conflict trends, request-status history, and the bottlenecks and critical path that constrain the plan.
Insights (“Conflicts and utilization analytics”) is the health check for your operation: how much is scheduled, how well resources are used, and where plans collide — over a period you choose.
Filters
Two selectors drive the tabs:
- Date range — presets from “Last 6 months” to “Next 12 months”, including the combined “Last 6 / next 12 mo” view for planning across the present.
- Bucket — Weekly, Monthly, Quarterly, or Yearly aggregation for the trend charts.
The critical path on the Bottlenecks tab is the one exception. It covers the whole dependency network, so neither selector applies to it.
Overview
KPI cards summarize the period at a glance:
- Total requests, Scheduled, Unscheduled — the state of the backlog.
- Conflicts — how many placements currently violate the model.
- {Type} utilization — one card per active resource type, so Mill utilization and People utilization sit alongside a card for every type you defined yourself (Resource types). Aggregate usage against configured capacity.
Below the cards, a Request status trend chart puts the backlog in motion (New, In progress, Done, Deferred, Canceled).
Utilization
One {Type} utilization trend chart per active resource type — Mill utilization trend, People utilization trend, Car utilization trend — shows how usage develops across the buckets you selected. Add a resource type and its chart appears here; deactivate one and it disappears. “No capacity configured for this period.” means exactly that: utilization is a ratio, and it needs configured capacity (working hours, availability) to be meaningful — see Scheduling and availability.
Conflicts
The conflicts tab lists every current conflict as a card, each labeled by kind — Scheduling Overlap, Capacity Exceeded, Capability Mismatch, Load Exceeded, Below Minimum Duration, Before Earliest Start, After Latest End, Size Mismatch, Dependency Violation — with the affected schedule and a link to the other request involved where relevant (“View other request”). The summary line keeps score: “No conflicts detected. All scheduled requests meet their requirements.” is the state to aim for. Above the list, the Conflict trend chart stacks the period’s conflicts by category — Overbooking, Criteria mismatch, Resource unavailable, Outside availability, Missing resource, and Sequence violation.
What each kind means and how to resolve it is covered in Understanding conflicts and the hands-on guide Find and resolve conflicts.
Bottlenecks
The bottlenecks tab answers a different question from the other three: not how the period trends, but what constrains the plan right now.
Two rankings sit at the top: Most overloaded stations and Most overloaded assets. Each lists the resources booked past their capacity, worst first, with the hours of overspill and the peak day as a percentage.
The split matches the rest of the app. A station has a fixed location and goes on a floorplan; an asset moves, and availability rather than position is how it gets planned (Stations, Assets). Ranked together, one busy class fills every place in the list and hides the other.
Each ranking has its own resource type selector. Keep it on “All stations” or “All assets” to see the class as a whole, or choose one type to see only mills, or only tools. People are assets, so they compete with your other assets for places in that list — select the type to look at one on its own.
The ranking is measured per day, whatever period you select. Overbooking is a spike: a machine slammed on nine days of a month and idle for the rest averages out to something comfortable, and a monthly figure hides exactly the days that hurt. An empty list means nothing was overbooked, which is the healthy state rather than missing data.
Below it, Critical path shows the chain of work that decides the finish date, with the earliest and latest dates each request can take and its Float — how long it can slip, in days and hours, before it costs something. Zero float carries a Critical badge. Select a row to open that request.
This table covers the whole dependency network and ignores the date range, because a chain of work does not stop at the edge of the period you are looking at. The header says so. Requests with no dependencies do not appear: they have nothing to be early or late against. See Dependencies and the critical path.
Insights vs the board
The Utilization board is where you act; Insights is where you assess. Use Insights to spot the pattern — a chronically overbooked machine, a quarter with rising conflicts — then jump to the board to fix the instances.