How to Run the BOR Change History Report in EDGEBIC

The BOR change history report in EDGEBIC by User Solutions lives in the Reports hub: it takes a date range and lists every routing snapshot version created in that window, with its date, reason, step count, and the jobs scheduled against it. It is the version history of your bills of routing, and the answer to "which routing was this job actually built against".

EDGEBIC freezes a routing snapshot every time a job is scheduled, which is what lets a reschedule preserve the plan the job was made against. The concept behind that is covered in the bill of routing explainer, and how snapshots protect regulated builds is in routing snapshots for medical devices. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• Jobs have been scheduled in the window you care about. Snapshots are captured at scheduling time.
• You want a version-level view, not a step-level one. This report catalogs routing versions; the step-level detail lives inside each job.
• You know the product name or the job number you are tracing.

Step 1: Open the Report and Set the Window

Open Reports from the main navigation and click the BOR Change History card. A date range dialog appears. Set the From and To dates wide enough to cover the routing changes you want to see, then click OK. The report queries the routing snapshots captured in that window and matches each to the schedules that reference it.

Step 2: Read a Snapshot Row

Each row describes one routing version:

• Snapshot date, when the version was captured.
• Product, the item the routing belongs to.
• Version number and version tag, the identity of this version.
• Reason, the note recorded when the snapshot was taken.
• Step count, how many operations the routing held at that version.
• Jobs using, the list of job numbers scheduled against this version.

The jobs-using column is what turns a version list into traceability: it ties each frozen routing to the specific work that was built on it.

Step 3: Trace a Job to Its Routing Version

To answer "which routing was this job scheduled against", find the product, read down the snapshot dates, and locate the version dated on or just before the job's scheduled date. Confirm the job number appears in that version's jobs-using list. That row is the routing that was in force when the job was planned, regardless of how the master routing has changed since.

Step 4: Export the Row as Evidence

With the row identified, click Export in the dialog toolbar and save to Excel or PDF. The exported row names the product, version, date, step count, and jobs built against it. For a build record or an audit response, that frozen version is stronger evidence than a view of the current routing, which may no longer match what the job ran.

How to Check It Worked

The report is a read-only snapshot, so nothing is saved. Confirm it worked by finding a product you recently rescheduled and checking that a new version appears with a later snapshot date than the previous one, and that the rescheduled job now sits on the newer version. If a version's job list is unexpectedly empty, the schedule that used it was likely re-saved without keeping the snapshot reference.

Common Mistakes

• Reading an empty jobs-using column as data loss. The version still exists; it simply has no schedule pointing at it, usually because a schedule was re-saved without preserving the reference.
• Assuming the current routing matches the built one. The whole point of snapshots is that they can differ. Always trace to the snapshot dated at scheduling time, not to today's master routing.
• Comparing performance metrics across a version boundary. If a new snapshot changed cycle-time fields, OEE and similar metrics are not like-for-like across the boundary. Keep comparison windows inside one version.
• Setting the date range too narrow. Snapshots are captured at scheduling time, which may predate the period you are investigating. Widen the window if an expected version is missing.

Related Reading

• Job audit trail: the routing versions appear alongside every other event in one job's life.
• Reschedule history report: the date-change record that pairs with routing-version tracking.
• EDGEBIC platform overview: where routing preservation fits in the wider system.