How to See One Work Center's Schedule in EDGEBIC

To see one work center's schedule in EDGEBIC by User Solutions, open the Schedule tab and select the Workcenter Details sub-tab. It shows a single machine's schedule rather than a single job's operations, and it carries the Excel export you use to hand a machine list to a supervisor. It is the per-machine view that sits between the Resource Calendar, which counts hours, and the Job View, which follows one order through the plant.

Most scheduling screens are organized by job. That is the right default for a planner chasing a promise date, and the wrong one for the conversation you have with the person who runs the mill. He does not want to know where job 0101 goes next. He wants to know what is on his machine this week and in what order.

Before You Start

• Run the scheduler first. The tab reads the current plan. An unscheduled job has nothing to show.
• Know which question you are asking. How many hours does this machine have is a Resource Calendar question. What work is on it is this tab.
• Have the work center identified. The view is per machine, so a pooled operation appears under whichever member the scheduler actually resolved it to.

Step 1: Open Workcenter Details

Open the Schedule tab from the main navigation. Its sub-tab row holds Quote, Drive Schedule, Job View, Schedule View, Resource Calendar, Workcenter Details, Scheduled Job BOR, and Optimizer.

Select Workcenter Details. Choose the work center you want to read.

Step 2: Read the Machine's Schedule

The schedule shows what is booked on that one work center. Read it the way a supervisor reads it: in date order, as a queue.

Three things are worth checking every time.

Sequence. The order operations sit in is the order the scheduler intends them to run. On a changeover-heavy machine, that order is money. If your paint booth or alloy furnace carries a setup matrix, this is where a light-before-dark run looks obviously right or obviously wrong.

Density. Back-to-back operations with no gaps mean the machine is the binding resource for those days. Gaps mean it is waiting on something upstream, not on itself.

Ownership. If an operation you expected here is missing, it went somewhere else. That is normal for a step with an alternate work center or a step bound to a machine pool, both of which resolve to a real machine at scheduling time.

Step 3: Export It for the Floor

Use the Export Excel button, or right-click the grid and choose Export Work Center Schedule. Either gives you the grid as displayed, in its current sort and filter order, as a spreadsheet.

Export after the day's scheduling run, not before. The export is a snapshot, and a run performed afterward makes the printed copy wrong without telling anybody.

Grid exports across EDGEBIC share one rule worth stating plainly: they are for sharing and analysis, not for round-tripping. An exported schedule cannot be edited and imported back in.

Step 4: Set Anchors If This Machine Is the Constraint

Workcenter Details is also where bottleneck anchoring happens. Select the jobs and use Set Anchor for Selected Jobs to pin their operation on this machine to a target date.

That instruction changes how the scheduler plans those jobs. The anchored operation is placed at its target date, everything upstream is scheduled backward from it so material arrives just in time, everything downstream is scheduled forward from its end, and protective buffers are inserted around the split. An anchor is the strongest instruction a job can carry, beaten only by recorded actuals.

Use it on the resource that genuinely sets the pace, and only there. How to anchor a job to a target start date covers the full procedure.

What Changes When You Look

Reading the tab changes nothing. It reports the plan produced by the last scheduling run.

Two actions taken from it do change things: setting an anchor changes how those jobs are planned on the next run, and exporting writes a file. Neither reschedules by itself. Run Drive Schedule after setting anchors to see their effect.

How to Check You Are Reading It Right

1. Pick one operation on the machine's schedule and find the same operation in the Job View for its job. The dates should match exactly. They are two views of one plan.
2. Add up the hours for a single day and compare against the assigned hours for that machine and date on the Resource Calendar. They should agree.
3. If an operation is missing, open its routing step. A step with alternates or a group binding may have resolved to a different machine.

A Short Worked Sequence

The morning routine for a plant whose mill is the constraint.

1. Run Drive Schedule on the Drive Schedule tab so every view reflects last night's actuals.
2. Open the Resource Calendar and scan for red. Thursday on the mill is oversold.
3. Open Workcenter Details for the mill. Read its week as a queue. Four jobs land on Thursday, and one of them is a low-priority order that could sit until next week.
4. Decide the cheapest fix. If the capacity number is wrong because a maintenance window finished early, a per-day override fixes it with one number. If the work genuinely has to move, move the low-priority job.
5. Export and distribute. With the plan settled, use Export Excel on Workcenter Details for each machine whose supervisor wants a printed list.

Order matters here. Exporting before the fix hands the floor a sheet that was already obsolete when it printed.

Common Mistakes

• Reading it before the run. The tab shows the current plan. If you have not scheduled since the change you made, you are reading yesterday.
• Confusing it with the Resource Calendar. One shows work, the other shows hours. Red days are found on the calendar and explained here.
• Exporting first and scheduling second. The floor gets a snapshot that stops being true almost immediately.
• Anchoring on the wrong machine. Anchoring a resource that is not the real constraint forces backward scheduling for every job that touches it and distorts the whole plan. Mark and anchor one genuine bottleneck.
• Expecting a pooled step to appear before scheduling. A step bound to a machine pool carries a pool badge until a run resolves it to a member.

Where to Go Next

For the hours behind the work, how to see a work center's load for next month and how to read the capacity heatmap cover the capacity side. If a machine looks permanently overloaded, the fix is usually calendar or capacity rather than sequencing: start with how to override capacity for one day. Every task is indexed at the EDGEBIC How-To Library, the platform is at EDGEBIC, and the underlying idea is explained in what production scheduling is.