What Is a Resource Replacement Audit? EDGEBIC Definition

A resource replacement audit is the report that lists every job whose work center was changed, showing the old machine, the new machine, who made the change, and when. In EDGEBIC by User Solutions, it is built from work-center-swap entries in the schedule change log, and it answers a single accountability question: which jobs had their work center changed, by whom, and to where? It captures both a planner reassigning a step by hand and the scheduling engine choosing an alternate work center during a run.

This entry is part of the EDGEBIC glossary series. For the broader planning vocabulary, see the manufacturing glossary. The audit is a diagnostic sibling of the scheduling anomaly check, which flags data integrity problems rather than routing changes.

How a Resource Replacement Audit Works

Every time a job's step changes work center, EDGEBIC writes a record to the schedule change log with a change type marking it as a work-center swap. The payload on that record carries the old work center identifier and name and the new ones. The resource replacement audit reads the log for a date range, keeps only the swap entries, and lays them out as a readable table.

The result is a list of jobs that left their planned machine for another one, each row naming the old and new work centers, the actor who made the change, and the timestamp. Because the record is written at the moment the swap happens, the audit is a true trail rather than a guess reconstructed after the fact.

This matters because work-center swaps are easy to lose track of. A planner offloading a step from an overloaded bottleneck to an alternate is doing exactly the right thing, but if the swap is invisible, no one can tell an intended relief move from an accidental one. The engine also selects alternate work centers on its own when a primary is full, so swaps can happen without any human touching them. The audit is the one place that gathers all of them, whatever their source.

A Concrete Example

Suppose Mill-1 is the flagged bottleneck and, during a scheduling run last Tuesday, its queue was too deep to take Job 42's Step 3. The engine (or a planner reviewing the run) moves the step to Mill-2, a configured alternate.

Run the resource replacement audit for the week, and the row reads:

That single row confirms the swap was deliberate and tells you exactly where the work went. If Job 42 later runs late, the audit gives you the first thread to pull: the step left the bottleneck for an alternate, so the next question is whether Mill-2's time factor made the operation longer. The audit does not answer that on its own, but it points you at the cause.

How EDGEBIC Uses the Resource Replacement Audit

The audit is one of the panes in EDGEBIC's reports catalog, reached through the report dialog and run for a date range. Its walkthrough is how to run the resource replacement audit in EDGEBIC, which covers opening the pane and reading the columns.

It works best in pairs. Where the resource replacement audit tells you a job's machine changed, the reschedule history report tells you whether its dates changed, and both read the same schedule change log filtered to different change types. A job can swap machines without moving in time, or move in time without swapping machines, so running the two together gives the full story of what happened to a job after it was first scheduled: where the work went, when it moved, and who was behind each change.