How to Run the Resource Replacement Audit in EDGEBIC

The resource replacement audit in EDGEBIC by User Solutions lives in the Reports hub: it takes a date range and returns every work-center swap in that window with the job, the old station, the new station, the person who made the move, and the reason. When a job runs on a different machine than the plan first assigned, this is the report that tells you who changed it and why.

It is the routing companion to the reschedule history report, which answers the same who-and-why question about dates rather than stations. Both feed the wider case for audit-ready scheduling. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• Work-center swaps have actually happened in the window. The audit reads swap events; if nobody re-routed a job, the grid is empty by design.
• Your team enters a reason on manual swaps, if you want the reason column to be useful.
• You know the difference between a manual swap and an automatic alternative selection. Only the former is recorded here.

Step 1: Open the Audit and Set the Window

Open Reports from the main navigation and click the Resource Replacement Audit card. A date range dialog appears. Set the From and To dates to cover the period you want to examine, then click OK. The report reads the schedule change log for work-center swap events in that window and builds one row per swap.

Step 2: Read a Swap Row

Each row records a single re-routing decision:

• Job and the operation involved, so you know exactly which step moved.
• Old work center and new work center, the stations the step left and landed on.
• Event time, the timestamp of the change.
• Actor, the person who made the swap.
• Reason, the free text they entered, when they entered it.

Together these columns are a chain of custody for every routing change: which step, from where to where, by whom, when, and why.

Step 3: Group by the New Station to Find Patterns

Right-click the new-work-center column header and choose Group By This Column. The grid collapses into buckets by destination station. A single alternative absorbing most of the swaps is a structural signal: the primary station those jobs belong to is overloaded, and planners are offloading to the same alternative over and over. That is a capacity problem to fix, not a run of unrelated decisions.

Step 4: Filter to One Job for a Customer Question

Right-click the job column header, choose Filter Editor, and set the filter to a single job number. The grid narrows to that job's re-routing history. This is the fastest way to answer "why did this order run on a different machine than we quoted", because the surviving rows are the complete, timestamped account.

How to Check It Worked

The audit is a read-only snapshot, so there is nothing to save. Confirm it worked by checking that a swap you know happened, such as an operation you personally dragged to another machine, appears with the correct old and new stations. If a change you expected is missing, it was almost certainly an automatic alternative selection during a schedule run rather than a manual swap.

What the Audit Does Not Capture

The report records manual work-center swaps only. When the scheduler chooses an alternative work center on its own during a run, because the primary was full, that selection is not logged as a swap event. To trace automatic alternative selection, use the step-level progress views, which preserve the original station each step was replaced from. Keep this boundary in mind: an empty audit does not mean no jobs changed stations, only that no planner manually moved one.

Common Mistakes

• Expecting automatic re-routes to appear. Only planner-made swaps are recorded. Scheduler-chosen alternatives live in the progress reports.
• Reading a blank reason column as a system fault. The reason is entered by a person at swap time. Empty means nobody typed one, which is a policy gap, not a bug.
• Judging a busy alternative as a good thing. One station absorbing most re-routes is a symptom of an overloaded primary, not efficient flexibility. Fix the primary's capacity.
• Forgetting the date angle. A swap that also moved the schedule shows here for the station change and in the reschedule history for the date change. Run both for the full picture.

Related Reading

• Reschedule history report: the same accountability, for dates instead of stations.
• How to run, filter, and export reports: the grid controls that make grouping and filtering fast.
• EDGEBIC platform overview: where the audit trail fits in the wider system.