How to Run the Scheduler Anomalies Report in EDGEBIC

The Scheduler Anomalies report in EDGEBIC by User Solutions lives in the Reports hub under Diagnostics: it runs 22 automated health checks across seven categories against your current schedule and shows one green or red chip per check. It is the report you open before you ever say "the scheduler got it wrong," because most of the time a red chip names the real cause in a single line. Here is how to run it and act on what it finds.

For running reports in general, see how to export a report to Excel. Every task in this library is mapped on the EDGEBIC how-to hub, and the wider idea sits in what is production scheduling.

Before You Start

• Jobs have been scheduled at least once. The report reads the current schedule, so an empty plan has nothing to check.
• You know whether you want a plant-wide scan or a job-scoped one. Leave the filter blank for everything, including the inventory and setup-matrix checks that only run on a full scan.
• You are ready to act elsewhere. The report only flags; the fixes happen in master data or the routing, followed by a scheduler run.

Step 1: Open It and Choose a Scope

Open Reports from the main navigation and click Scheduler Anomalies in the Diagnostics group. The report window opens and runs immediately.

At the top is a job filter. Leave it blank for a plant-wide scan, which is what you want most of the time, and which is required for the inventory and setup-matrix families of checks (those read global tables and only evaluate on a full scan). To narrow the report to one problem job, type its job number, or a comma-separated list, and re-load.

Step 2: Read the Chip Strip First

Across the top sits one chip per check. A green chip means zero rows: that check passed. A red or amber chip means the check found rows, and the chip carries the count.

Read the strip before the grid. It is the fastest way to see whether the schedule is healthy at a glance, and which of the seven categories is unhappy. The categories cover the ground you would check by hand: over-utilization, instance collisions, wasted idle gaps, dependency violations, off-calendar bookings, plan inversions, and configuration gaps. The Job View keeps its own running count of the collision case, read in how to find scheduling conflicts in the Gantt.

Step 3: Click a Red Chip to Filter

Click a red chip. The grid below filters to just that check's rows. Click the same chip again to clear the filter and show everything.

Each row belongs to a specific schedule or routing step, and clicking a row navigates you straight to the owning object in the relevant view, so you can see the offending booking in context instead of hunting for it.

Step 4: Sort by Severity and Fix Critical First

Every check carries a severity, and the grid groups by check and sorts by severity so the worst rows sit at the top.

A Critical row is never "working as designed." A Warning often is, which is why the report shows you the row rather than silently suppressing it.

Step 5: Use Column Details When a Row Puzzles You

Click Column Details in the report footer for the built-in glossary. Every column and check has a plain-English description, and often a worked example, so you can read your own flagged row against a known-good and known-bad value. It is the same glossary that powers the rest of the reports, covered in how to find out what a report column means.

What Changes When You Run It

Nothing. The report is read-only and queries fresh each time it opens or re-loads. It never edits a schedule, moves a booking, or touches your data.

What clears a red chip is the work behind it: assign a shift to the work center with no capacity windows, clear a FlowStep on a step now running on an alternate machine, restore a deleted work center, or fix an inverted actual date. Then re-run the scheduler and re-open the report.

How to Check It Worked

Re-run the report after your fix and watch the specific chip you targeted turn green. If you fixed a work center's missing shift, the configuration-gap chip for that check should drop to zero rows. If the chip is still red, either the fix did not land or a second row trips the same check, so click the chip and read the remaining rows. A chip that stays amber after a real fix usually means a different row of the same kind, not a failed edit.

Common Mistakes

• Job-scoping when you needed the whole plant. The inventory and setup-matrix checks only run on a blank filter. Scope to a job and those chips simply do not evaluate.
• Reading every Warning as a fault. A booking on a holiday or an idle gap can be legitimate. Confirm the story before you change the plan.
• Skipping the report and blaming the engine. After a bulk import or a big routing edit, run this first. A red chip usually explains the surprise faster than staring at the Gantt.
• Fixing the symptom on the Gantt. Dragging a bar hides an anomaly for one run. Fix the underlying master data or routing so the next run stays clean.

Next Steps

• Confirm a suspicious change with how to check what a scheduling run changed.
• For authoritative capacity numbers behind an over-utilization chip, open the work center utilization report.
• See how the whole plan reads on the EDGEBIC product page.