- Home
- Blog
- EDGEBIC Platform
- How to Set Up and Use the EDGEBIC Dashboard Tabs
Setting up the EDGEBIC by User Solutions dashboard is mostly a matter of getting four inputs right and then choosing which tiles you want to see: the cockpit computes everything from your schedule, your shift calendars, and your logged actuals. This guide walks the prerequisites, the settings dialog, the resource calendar controls, and the one place where a dashboard actually writes something back: the per-day capacity override.
For what each tab is for and who should read it, start with the dashboard overview. For the drill-down layer beneath every tile, see the report catalog.
Before You Begin
| Prerequisite | Why it matters |
|---|---|
| Jobs scheduled at least once | Every load, utilization, and status figure derives from the schedule |
| Work centers and shifts configured | Capacity is shift hours times instances; wrong calendars paint wrong pictures |
| Actuals and kiosk punches flowing | Adherence, the andon strip, and cost variance need real start and finish events |
| One work center flagged as the bottleneck | The bottleneck tile and panels read that flag; with none set, the tile shows a dash |
| Every work center assigned to a department | The exec multi-plant roll-up skips work centers without one |
None of these are dashboard settings. They are the master data the whole plan runs on, which is the point: the cockpit has almost nothing to configure because it reads what the scheduler already knows.
Step 1: Read the Capacity Tab
Open Dashboard from the main navigation and you land on capacity, overview sub-tab. Read the hero tiles left to right, and hover the info icon on any of them: the tooltip gives what the tile shows, why it matters, and how it is computed, in a sentence.
Below the tiles sit the work center utilization chart (assigned against available hours per station), the capacity trends chart over time, and an active alerts panel. Three sub-tabs go deeper:
- Capacity: the work center capacity detail grid (identifier, department, type, instances, total hours, assigned hours, available hours, utilization percentage, status) plus a department summary strip.
- Jobs: scheduled jobs and at-risk jobs, where at-risk means a projected end past the due date.
- Shifts: a shift capacity chart and shift detail grid.
Beside the active jobs list sits the job status donut, whose four slices (Late, Overdue, On time, Early) are explained in the overview post. The list sorts worst first, so it doubles as your work queue.
Step 2: Configure Your Tiles and Thresholds
The settings dialog on the capacity tab opens dashboard configuration with three tabs:
| Tab | What you set |
|---|---|
| KPIs | Which tiles appear on your dashboard |
| Thresholds | The green and red bands each tile colors against |
| Display | Colors, and the auto-refresh interval in seconds (zero disables) |
All of it is personal. Your tiles, your thresholds, your refresh interval; nobody else's dashboard and no production data changes. That makes threshold tuning safe to experiment with, and worth doing once properly: a target nobody believes gets ignored, and a tile that is red every single day stops being information.
One deliberate default worth understanding: the cockpit does not auto-refresh. Each tab loads its snapshot when you switch to it, and Refresh now reloads on demand. On a large schedule, continuous background re-querying would cost more than it returns. Build the habit of clicking Refresh now as a meeting starts.
Step 3: Put Standup on a Screen
Navigate to the standup tab on whichever machine drives the floor display, and the dark high-contrast theme applies automatically. The theme swap is scoped to the dashboard, so the rest of the application keeps its normal appearance.
Read it in order during the huddle: the SQDC band (safety, quality, delivery, cost), the andon strip with one tile per work center, the bottleneck card, then the late-job punch list. A clean punch list literally says all orders are on track.
The andon colors are inferred from schedule actuals rather than machine sensors, and that has one operational consequence worth naming at the start: a work center goes red when it is more than ten minutes past its planned start with no actual start recorded. If your board is mostly red by mid-morning, the message is that operators are not punching in at operation start, not that half the plant is broken. Fix the punch discipline and the board becomes trustworthy within a week.
Step 4: Use the Planner Tab Daily
Planner is the tab for whoever owns the schedule. Two tiles measure the plan itself: adherence (operations that started within an hour of plan over the past 14 days, target 90% or better) and attainment (completed jobs that hit their due date, target 85% or better). Read the delta note on adherence as an investigation count rather than a number: "35 ops moved off plan" is a list to work through, not a statistic to report.
The 14-day heatmap colors every work center and day by load, which is assigned hours divided by that day's capacity. Hover any cell for the raw hours. A red cell means oversold. What to do about it is the whole subject of reading a red day.
Step 5: Drive the Resource Calendar
The resource calendar lives in the Schedule area rather than the dashboard, and it is the planner's capacity ledger: work centers by time period. Its controls run across the top:
| Control | Options |
|---|---|
| Mode | All (five stacked rows per work center), Assigned, Backlog, Total, Available Capacity, Utilization |
| View | Day, Week, Month, Quarter column buckets |
| Rounding | Decimal places, zero to three |
| Shift Filter | Restrict figures to a single shift |
| Job | Restrict assigned and backlog figures to one job |
| Start Date and End Date | The reporting range |
| Include Weekends | Show weekend columns |
| Show as Hours | In utilization mode, show hours instead of percentages |
| Refresh and Export | Reload, or export the grid |
In All mode each work center block shows five rows: total capacity, hours assigned, available capacity, backlog, and utilization.
The mode to learn is backlog. Assigned answers "what hours land in this period?"; backlog answers "how much work is still ahead of this station as of this period?". It is a forward sum of remaining hours, so it burns down as work is consumed: a 24-hour step spread over three days reads 24, 16, 8, then 0. A backlog rising week over week is an early warning that a station is receiving work faster than it clears it, which is classic input and output control.
Click any non-zero assigned or backlog cell and the job detail popup lists the allocations behind it, summing back to the cell under the same shift and job filters.
Step 6: Record a Real Capacity Change
The dashboards are read-only with exactly one exception: the per-day capacity override, reachable from three places.
- Capacity overview: double-click a work center's bar in the utilization chart.
- Capacity detail grid: double-click the work center's row.
- Resource calendar: double-click a total capacity cell, which opens the dialog anchored on that date.
Each opens the same day grid: day, shift default hours, capacity hours, loaded hours, an overridden flag, and a reason, with a loaded-against-capacity chart and summary counters for total capacity, loaded, free, over capacity, and overridden days. Type a value into the capacity column to override that day. Overrides are honored by the scheduler and kept for audit; a reset control removes them.
What changes and what does not:
| Action | Changes | Does not change |
|---|---|---|
| Switching tabs or clicking Refresh now | The displayed snapshot | Any data |
| Saving a per-day override | That work center's capacity on those dates, honored on the next scheduling run | Already-scheduled jobs, until you re-run Drive Schedule |
| Dashboard settings | Your tiles, thresholds, colors, refresh interval | Anyone else's view, and all production data |
That middle row is the one people trip over. Adding four overtime hours on Tuesday does not pull work into Tuesday by itself. It changes what capacity exists; re-running the schedule is what plans against it.
A Cadence Worth Adopting
| When | Tab |
|---|---|
| Daily huddle on the floor screen | STANDUP |
| Every morning, for the schedule owner | PLANNER |
| Working default through the day | CAPACITY |
| Weekly or monthly management review | EXEC |
Watch trends rather than ticks. Adherence at 88% once is noise; 88% falling week on week is a process problem, which is exactly what the sparkline on each tile exists to show. And respect the chips: a Plan number is a projection, so do not quote it to a customer as fact, and an Offline dash is honest absence rather than zero.
For the traps that turn a correct tile into a wrong decision, read dashboard misreading mistakes. For the metrics underneath, our manufacturing KPI guide and capacity utilization KPI cover the generic definitions, and the complete EDGEBIC guide covers the system producing them.
Want this cockpit reading your plant's real load? Bring your work centers and open orders to a demo.
Four things, in order. Jobs must be scheduled at least once, because every load and status figure derives from the schedule. Work centers and shifts must be configured, because capacity is shift hours times instances. Actuals and kiosk punches should be flowing, because adherence, the andon strip, and cost variance need real start and finish events. And one work center should carry the bottleneck flag, because the bottleneck tile and panels key off it.
Open the settings dialog from the capacity tab. Its KPIs tab lets you pick which tiles show, its thresholds tab tunes the green and red bands, and its display tab sets colors and the auto-refresh interval in seconds, where zero disables refresh. Every one of those settings applies to your own view only: production data and other users' dashboards are untouched.
Yes. Navigate to the standup tab on the machine driving the display and it switches to a dark, high-contrast theme automatically, built for wall-mounted screens. There is no background auto-refresh on the cockpit tabs, so click Refresh now when the meeting starts. The board reads top to bottom: the SQDC band, then one andon tile per work center, then the bottleneck card, then the late-job punch list.
Three routes reach the same dialog. Double-click a work center's bar in the utilization chart on the capacity overview, double-click its row in the capacity detail grid, or double-click a total capacity cell in the resource calendar, which opens anchored on that date. Type a value into the capacity column for the day, add a reason, and the override is honored by the scheduler on the next run and kept for audit.
Expert Q&A: Deep Dive
Q: I approved four hours of overtime on Tuesday. Where exactly do I record it so the schedule believes me?
A: In the per-day capacity dialog for that work center, not in a note. Double-click the station's bar on the capacity overview, find Tuesday in the day grid, and type the new figure into the capacity column, for example 16 where the shift default is 12, with a reason such as 'OT approved'. The dialog's over-capacity counter drops as you type and the dashboard refreshes when you close it. One thing does not change on its own: the jobs stay exactly where they are until you re-run Drive Schedule, because the override changes what capacity exists, not what has already been planned against it.
Q: The resource calendar shows a big number in one cell and my supervisor wants to know what is in it. Can I show him?
A: Click the cell. Any non-zero hours-assigned or backlog cell opens a job detail popup listing the allocations behind that exact number: job number, product name and number, work center, shift, date, instance, transaction hours, and pieces. The rows sum back to the cell value under whatever shift and job filters the calendar currently has applied, which is the usual explanation when they appear not to add up. That drill-down turns a disputed number into a list of jobs in one click, which is normally where the conversation should have started.
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 an Open EDGEBIC Screen Notices Someone Else's Edit
On a shared database, a change made on one workstation reaches every other open screen within a few seconds, without anybody pressing anything. How the change signal works and why your selection survives it.
What Changes When EDGEBIC Moves to a Shared Database
Moving EDGEBIC from one workstation to a shared SQL Server changes three assumptions at once: who may overwrite whom, how an open screen stays current, and who may run the scheduler.
What the EDGEBIC Refresh Button Actually Does
The refresh button forces a full re-read from the database, which is not the same as closing a screen and reopening it. Why the distinction matters on a shared database, and when to press it.
