Following a Job From the Gantt to Its Routing in EDGEBIC

A bar on the EDGEBIC by User Solutions schedule board is a doorway, not a dead end. From one operation you can reach that operation's daily actuals, the job's full change history, the job's hours and per-step detail, the routing that job is actually running, and a read-only progress view. Planners who know the path answer questions in under a minute. Planners who do not go hunting through tabs.

This post lays out the drill-down routes in the order you tend to need them. For the surface itself, start with the visual scheduling guide.

Level One: The Bar Itself

Before you go anywhere, the bar has already told you several things. Its lane says which work center. Its position says when. Its body color says what state the operation is in, from untouched engine plan through in-progress to saved override. Its status strip can carry the job's own color so you can trace that job across every other lane.

If the caption is configured well, it says more still. The caption pattern is set per work center and can carry planned dates, actual and remaining hours, percent complete, and roll-up totals for the work center or the whole job. Many questions never need a second screen. See reading operation description fields on a Gantt bar.

When you do need more, the right-click menu is the next step.

Level Two: The Right-Click Routes

Right-clicking a bar gives you the operation-level destinations, alongside the edit commands.

The audit trail is the one people forget and then rely on daily. A job that slipped did not slip mysteriously: somebody dragged something, a reschedule ran, or an operation was completed. The history says which, and when, and who. That reading is covered in reading the schedule audit trail, and the rest of the menu in the Gantt right-click operation menu.

Level Three: The Job Cockpit

When the question is about the job rather than the operation, switch to the Job View tab and select the job.

This is where the numbers live. A summary panel identifies the job, its end product, the engine's planned window, the quantity, and how many operations it has. An hours roll-up shows total, actual, remaining, and percent complete for the whole job, sourced from the scheduled operations themselves rather than from an estimate taken at order entry, which is why it stays honest as the job progresses.

Below that, a per-operation grid puts scheduled, actual, and target dates side by side with hours and pieces columns, and a Gantt strip renders the same job at an Hour, Day, Week, or Month scale. Job-level actions sit in the header: log actuals, complete or reopen, audit, capacity calendar, import actuals, export to Excel, and reschedule. Details in the Job View cockpit.

Level Four: The Routing That Job Is Actually Running

Here is the step most people skip, and it is the one that resolves the arguments.

A scheduled job does not run the product's current standard routing. It runs its own frozen copy, taken the moment it was scheduled. Open the Scheduled Job BOR tab, pick the job, and you are looking at what the floor was actually told to do for that job specifically.

That distinction matters the moment engineering changes a standard. The change lands on the product; every job already scheduled keeps running the routing it was given, so paperwork, operator instructions, and reschedules all stay consistent. Adopting the change on a running job is then a deliberate act rather than an accident, and it can be done for that job alone by editing its private copy. See how to work with frozen routings and editing a live job's routing.

The same tab gives you the routing in both shapes: a data grid for reading numbers quickly, and the flow-chart canvas for reading structure. Branches, sub-assembly feeds, and alternate machines are far easier to see drawn than listed, which is the argument in the data grid versus the flow chart view.

Level Five: Progress on the Routing Shape

The last destination is the live actual view, which overlays a job's logged progress onto its routing diagram and compares actual against planned on each operation.

Its defining property is that it is read-only. You can open it in front of a customer, a supervisor, or an auditor, and nothing you click changes the schedule. Monitoring and editing are different acts, and keeping them on different surfaces is what stops somebody dragging a bar during a meeting and discovering it on Thursday. See showing live progress on routing diagram nodes.

The Path, Compressed

Why the Path Matters More Than Any One Screen

Every one of these surfaces is a view of the same scheduled data. Nothing is recalculated per screen and nothing disagrees. What the path buys is speed: a customer question answered from the audit trail in forty seconds carries more authority than the same answer assembled from three people's recollections an hour later.

That is the practical case for visual production scheduling over a list of dates, and it is the habit User Solutions has been building with manufacturers since 1991, in small shops and in organizations including the US Navy, GE, BAE Systems, and Cummins. On the Nimitz refueling program that meant over 26,000 tasks staying traceable. In a job shop it means knowing why one bracket order slipped, before the customer finishes the sentence.

See the full EDGEBIC platform, or bring the job your customers ask about most to a demo and let US walk it from the bar to its routing.