The job audit trail in EDGEBIC by User Solutions lives in the Reports hub: pick a manufacturing order and it opens a multi-tab record of that job's entire life, covering its schedules, its change log, its punch adjustments, and the routing versions it was built against. Where most reports scan the whole shop, this one goes deep on a single order and assembles everything that ever happened to it in one place.
It is the report you reach for when a specific job needs explaining, and it draws together threads that also live in the reschedule history and resource replacement audit. The wider case for keeping this record is in audit-ready scheduling. Every task in this library is mapped on the EDGEBIC how-to hub.
Before You Start
- The job exists. The audit trail is per order, so you need at least one manufacturing order to open.
- You know which job you are investigating, or you can recognize it in the picker list.
- Actuals and change history exist if you want the later tabs to be populated. A brand-new job has a thin trail.
Step 1: Open the Audit and Pick the Job
Open Reports from the main navigation and click the Job Audit Trail card. A job picker dialog opens listing your manufacturing orders. Select the order you want and click OK. The audit dialog opens and loads the job's history across several targeted reads. If the dialog looks briefly frozen on open, the data load is in progress; it does no fetching until after it appears.
Step 2: Read the Summary and Schedules
The summary header shows the order and its customer. The schedules tab lists every operation on the job with its planned window and its actual start and end, so you can see at a glance which steps are done, in progress, or still ahead.
Step 3: Walk the Change Log Chronologically
Switch to the change log tab and sort by event time ascending. Each entry records one change to the job:
- Kind, such as a reschedule, a work-center swap, or an actuals update.
- Actor, the person who made the change.
- Reason, the note they recorded.
- The decoded detail: old and new dates for a reschedule, old and new stations for a swap.
Read top to bottom and the job's history assembles into a dated sequence of decisions rather than a vague sense that it slipped somewhere.
Step 4: Check Punch Adjustments and Routing Versions
The punch adjustments tab shows any corrections a supervisor made to logged time through the kiosk edit flow, with the before-and-after values and who made them. The routing versions tab shows the chain of routing snapshots the job was scheduled against, tying it back to the version history. Together these two tabs answer "were the hours edited, and by whom" and "which routing was this built on".
How to Check It Worked
The audit is a read-only record, so nothing is saved. Confirm it worked by cross-checking one known event: a reschedule you remember making should appear on the change log tab with the right dates, and a routing you recently updated should appear on the versions tab. If the change log is empty on a job you know was touched, confirm you opened the correct order in the picker.
Common Mistakes
- Expecting grid-typed actuals to show as punch adjustments. Only kiosk edit-flow corrections appear on that tab. Typing a date on the Job View grid does not create an adjustment record.
- Reading the change log without sorting it. Sort by event time ascending or the sequence of decisions is scrambled and the story is hard to follow.
- Over-trusting the actor column on shared terminals. The actor is the Windows session user. On a shared machine several people can appear under one login.
- Opening the wrong order in the picker. The audit is per job. A thin or surprising trail is often the wrong order selected, not a missing history.
Related Reading
- BOR change history report: the plant-wide view of the routing versions this report shows per job.
- How to run, filter, and export reports: sorting and exporting the change log for a record.
- EDGEBIC platform overview: where the per-job record fits in the wider system.
Expert Q&A: Deep Dive
Q: A job finished late and I need to reconstruct exactly what happened to it. Where do I start?
A: Open the job audit trail for that order and go straight to the change log tab, then sort by event time ascending to read the job's history in order. Each entry names the kind of change, whether a reschedule, a work-center swap, or an actuals update, the person who made it, the reason they recorded, and the before-and-after dates or stations. Read top to bottom and the story assembles itself: the job was on plan, then a reschedule pushed it three days on this date for this reason, then it swapped stations, and so on. If a change lacks a reason, that is your process gap to close. The audit trail turns a vague 'it slipped somewhere' into a dated sequence of specific decisions.
Q: The actor name on every change log entry is a Windows login, not a person I recognize. Is that a problem?
A: It is expected behavior worth understanding rather than a fault. The actor on each entry is captured from the Windows session user at the moment of the change. On a dedicated workstation that maps cleanly to a person, but on a shared terminal several people may appear under one login, which weakens the attribution. If clean per-person accountability matters to you, give planners their own workstation logins so the audit trail records a real name. Until then, read the actor column as the machine session, and lean on the timestamp and reason fields, which are still precise, to reconstruct who was working when.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.
User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.