- Home
- Blog
- EDGEBIC How-To
- How to Read the Capacity Heatmap in EDGEBIC
The capacity heatmap in EDGEBIC by User Solutions colors every work center and every day by load, so an oversold station jumps out of the grid before anyone reads a number. It appears as a 14-day view on the dashboard's Planner tab and in more detail on the Work Center Utilization report's Daily Heatmap tab. Reading it well is a small skill with a large payoff: it turns a wall of numbers into a picture you can act on.
For the playbook once you spot a red cell, read reading a red day on the capacity view. For the dashboard the Planner version lives in, how to set up and use the dashboard tabs. Every task in this library is mapped on the EDGEBIC how-to hub.
Before You Start
- Jobs are scheduled. The heatmap paints assigned hours from the plan, so an unscheduled plant paints nothing.
- Work centers have shifts assigned. Capacity comes from those calendars, and the load percentage divides by it.
- Your computer clock is correct. The heatmap runs from today forward, so a wrong system date paints the wrong days.
Step 1: Find the Right Heatmap
There are two, and they serve different moments.
| Heatmap | Where | Use it for |
|---|---|---|
| Planner load heatmap | Dashboard Cockpit, Planner tab | The morning glance: is anything oversold in the next two weeks |
| Daily Heatmap tab | Work Center Utilization report | The drill-down: scheduled hours, capacity, utilization and job count per cell |
Start on the dashboard for the glance, move to the report when a cell needs explaining.
Step 2: Read a Single Cell
Every cell is one work center on one day. Its color comes from load percent, which is assigned hours divided by that day's capacity. On the report's Daily Heatmap tab the cell also carries the raw numbers: scheduled hours, the day's capacity, the utilization percent, and how many jobs are on the station that day.
The color is a fast signal, not the whole story. A red cell is oversold, above 100%, but whether that is a one-hour problem or a crisis is the number behind the color, and the number is right there on the report cell or under the hover on the dashboard.
Step 3: Tell a Holiday From an Idle Day
Two kinds of blank look similar and mean opposite things.
- An empty cell is a day with capacity and no work booked. That is idle capacity, a gap you could fill.
- A holiday cell is a day with no capacity at all, marked as a holiday with zero capacity hours. That is not idle time; there was never any time to use.
Confusing the two leads to trying to schedule work into a holiday, which the plan will refuse. Read the capacity figure, not just the color: zero capacity is a holiday, positive capacity with no load is a genuine gap.
Step 4: Hover for the Numbers
On the dashboard heatmap, hover any cell for its assigned-versus-total hours and its load percent. This is the quickest way to size a problem before deciding whether it is worth a drill-down. A cell at 103% is worth a note; a cell at 140% is worth acting on today, and the hover is how you tell them apart without leaving the screen.
Step 5: Drill Into the Jobs
Color and percent tell you a station is overloaded. They do not tell you what to move. For that, open the Resource Calendar under Schedule and click that station's Hours Assigned cell for the period. A job detail popup lists every allocation behind the number with job, product, shift, date, instance and transaction hours, and the rows sum back to the cell.
The Work Center Utilization report gives the same answer through its per-work-center backlog drill-down if you are already in the report. Method for the whole report is in how to run the work center utilization report.
What Changes When You Read It
Nothing. Both heatmaps are read-only views of the plan.
Acting on a red cell is what changes things, and none of those actions happen from the heatmap itself: a per-day capacity override, a job moved on the Gantt, or a scheduler run. Completed work is never moved by any of them, so a fix lands on remaining work only.
How to Check You Read It Right
The clearest confirmation comes after you act. Fix an overload (add capacity for the day, or move the least urgent job off the station), re-run the schedule, and re-open the heatmap. The red cell should turn a cooler color or the number should fall below 100%. If the same station is red every week no matter what you move, you are reading a real constraint rather than a scheduling wrinkle, and that is a capacity conversation rather than a heatmap one.
Common Mistakes
- Reading color without the number. Red means oversold, but the size of the overload decides whether it is a note or an emergency.
- Treating a holiday cell as an idle day. Zero capacity is not spare time. Check the capacity figure, not the color.
- Reconciling the heatmap with the monthly rating. The heatmap is per day and the utilization report averages a range. Both are right; use each for its own question.
- Ignoring a wrong system clock. The grid runs from today. A wrong date paints the wrong days, and every cell reads for the wrong day.
See how the plan behind every cell is built on the EDGEBIC product page.
Expert Q&A: Deep Dive
Q: The heatmap shows one station red on Tuesday but the utilization report rates it GOOD for the month. Which do I believe?
A: Both, because they answer different questions over different windows. The heatmap is per day, so a single oversold Tuesday shows red even if the surrounding month is comfortable. The utilization report averages the whole range, so that one hot day disappears into a healthy monthly figure. Neither is wrong, and the mistake is trying to reconcile them into one number. Use the heatmap for the day-level truth, which is what you act on when you are planning the week, and use the monthly rating for the trend, which is what you take to a capacity conversation. If you need to settle a specific day, open the per-day capacity dialog for that station and date, which shows the loaded-versus-capacity chart for each day individually.
Q: A cell is red and I want to know which jobs made it red without leaving the screen for long. What is the shortest path?
A: Hover the cell first for the raw assigned-versus-total hours and the load percent, which tells you how big the gap is before you commit to a drill-down. Then, for the jobs themselves, open the Resource Calendar under Schedule and click that station's Hours Assigned cell for the period; a job detail popup lists every allocation behind the number with job, product, work center, shift, date, instance and transaction hours, and the rows sum back to the cell under the same filters. The Work Center Utilization report gives the same answer through its per-work-center backlog drill-down if you are already in the report. Either way you go from a colored square to a named list of jobs and hours in one click, which is the difference between knowing a station is overloaded and knowing what to move.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
