How to Run the Schedule Reconciliation Report in EDGEBIC

To run the Schedule Reconciliation report in EDGEBIC by User Solutions, open Reports and choose the Schedule Reconciliation card. There is no date prompt: read the verdict headline, then the eight chips, then work the Jobs grid before the Capacity grid. You are finished when both grids are empty.

For what each parameter checks, see the Schedule Reconciliation report explained. The full task library is at the EDGEBIC how-to hub.

Before You Start

• Schedule first, reconcile second. The report reads the current plan, so run it after the day's scheduling rather than before.
• You have report permissions for the scheduling family. The card will not appear otherwise.
• You have somewhere to act. Most rows drill through to the screen where the fix lives, so plan to work from the report rather than take notes off it.
• You know that healthy rows are hidden by default. An empty grid means clean, not broken.

The Steps

1. Open Reports from the main navigation and choose the Schedule Reconciliation card.
2. Read the verdict headline. Either the schedule is reconciled with every parameter passing, or it names the issue count broken down by kind. If it is reconciled, you are done.
3. Read the chip strip left to right. Green chips passed. A chip carrying a number is one click from exactly the rows that produced it.
4. Work the Jobs tab first. Late rows are customer-facing, so they outrank everything internal.
5. Work the Capacity tab second. Over-booked days are the days the plan physically cannot run as printed.
6. For each visible row, read the reason column and do what it says. Every row carries the number that triggered it plus a next step.
7. Double-click to drill through. A job row lands on that job in the schedule view; a capacity row opens the per-day capacity dialog for that machine and date.
8. Re-run the report from the pane and confirm the row has gone.

Reading the Chips

Clicking a chip switches to its grid and narrows it to exactly its rows. Clicking the same chip again restores the full exception view. Amber outlining shows which filter is currently applied, so you always know whether you are looking at everything or at one parameter.

Two counts feed the headline without having chips of their own: work center days loaded past the warning band, and jobs that finished late. Both are information rather than a pass-or-fail question with a fix, so they are colored, sorted and counted but not posed as a checklist item.

The show all toggle reveals the healthy rows. It re-filters what is already loaded rather than re-querying, so it is instant, and it is the right move when you want to confirm a machine is genuinely quiet rather than missing.

Reviewing One Work Center

Pick a machine in the work center dropdown and five things change together.

The second row is the deliberate one. A job that is late because of a downstream step is still late, and suppressing that under a machine lens would make the lens actively misleading in the case where it matters most.

How to Check It Worked

The headline flips. After fixing every row and re-running, the headline should state that the schedule is reconciled and every parameter passes.

Both grids are empty with show-all off. That is the definition of done.

The numbers agree with their sources. The late set should match the Late Jobs report, the hours should match the Job View header, and the adherence figure should match the planner dashboard. If any of them disagree, treat it as a finding rather than a rounding difference.

Common Mistakes

Running it before scheduling. The report reads the plan the last run produced. Reconciling a stale schedule reconciles yesterday.

Working the Capacity tab first. Over-booked days matter, and they matter less than a job that will miss its date. The tab order is the priority order.

Treating an empty grid as a failure. It is the success state. If you expected rows and see none, check the show-all toggle before assuming the report is broken.

Skipping the reason column. The status tells you the category; the reason tells you the number and the fix. Reading only the status turns a two-minute row into a ten-minute investigation.

Assuming green on the actuals chip means the data is perfect. Only critical anomalies change a job's status. Warnings are counted and displayed and are otherwise inert, so a job can carry several warnings and still classify on track. The anomaly report is where those live.

Expecting the thresholds to be configurable. The cutoffs behind pace, the loaded-day band and the horizon are fixed values in this version. There is no settings screen for them, so do not promise a planner a tuning dial that is not there.

Chasing a permanently red over-booked chip on synchronized machines. It should not happen: mirrored parallel operations are exempt from that check by design. If you see one anyway, read why a dependent-parallel child is exempt from the over-booked check before moving any jobs.

Taking It to a Meeting

The report exports to a workbook with four sheets: a summary carrying the checklist and its verdicts, the full jobs dataset, the full capacity dataset, and the raw anomaly evidence behind the data-quality parameters. The export writes every row regardless of which chip is applied or whether show-all is on, so what you take away is the complete picture rather than the filtered view you happened to be reading.

Next Steps

Once the routine is habitual, the useful follow-on is working the rows efficiently rather than merely finding them: how to work the reconciliation exception rows covers the drill-downs and the order to take them in.

If capacity violations are a standing problem rather than a daily one, EDGEBIC daily capacity overrides explained is the setup-side answer.

The takeaway

Open it, read the headline, work left to right, stop when both grids are empty. The report exists so that a plant too large to read can still be reviewed in a few minutes, and the discipline that makes it work is finishing the walk rather than skimming it. See the platform at EDGEBIC.