The Actual Live Screen Explained in EDGEBIC

In EDGEBIC by User Solutions, the Actual Live screen is a read-only view that draws a job's routing diagram and overlays a live actual-versus-planned progress card on every step, so you can watch a job move without ever touching the plan. It is the monitoring counterpart to the kiosk: operators punch the data in, and Actual Live is where a planner or supervisor watches those punches land on the job's own flow diagram. This is shop floor data collection turned into a live picture rather than a grid of numbers.

Most progress screens make you read a table and reconstruct the flow in your head. Actual Live keeps the flow in front of you: the same nodes, the same layout as the routing designer, each one wearing its current state. This article explains what it shows, what it deliberately refuses to do, and how it stays current.

The Third Mode of the Routing Tab

The Scheduled Job routing tab has three modes. The data grid lists steps as rows. The designer lets you lay out and edit the routing. Actual Live is the third, and it borrows the designer's exact diagram: the same nodes in the same stored positions, built through the same conversion pipeline, so the picture you monitor matches the picture you planned.

What changes is the payload on each node. Instead of an editable step, every node carries a progress card:

• A status badge: Queued, Running, or Complete.
• Logged hours against planned hours.
• A progress bar filling toward the plan.

Around the diagram sit a header strip, a completion-ring sidebar, and a legend, so a glance tells you both the whole-job state and each step's share of it.

Read-Only by Design

Actual Live watches, it never edits. You can drag a node to declutter a busy diagram, but those drags are in-session only and are never persisted to the routing. Reload the job, by reselecting it or hitting refresh, and every node snaps back to the designer's stored positions. Connector editing and node deletion are switched off entirely.

That restraint is the point. The plan is a contract, and a monitoring screen that could quietly nudge it would undermine the whole separation of actuals from plan that the rest of the platform depends on. If you want to change the routing, you use the designer. If you want to watch the routing, you use Actual Live.

How a Node Knows Its Progress

Each node joins to the schedule data that describes its real progress:

Alternative and parallel work-center child nodes are not drawn in this view. The primary node carries the actuals, consistent with how a parallel sibling's actuals always follow its primary elsewhere in the platform. That keeps the diagram readable and the progress unambiguous.

The Completion Rule

A step shows Complete when its remaining hours reach zero, meaning logged hours have caught up to planned, or when its actual end date is set. Both paths count for a reason: the planner's Log Actuals grid records hours without stamping an end date, so a fully logged step judged on the end date alone would sit at Running forever. A single shared rule decides completion for the node cards, the sub-assembly picker, and the job rollup, so every surface agrees on what "done" means.

The end-product node is special. It carries no schedule of its own, so its state is derived from the steps that feed it. When the last upstream work center completes, the end item flips to Complete and its inbound path renders as a finished connector. It is a summary, not a counted step.

Staying Current Without Hunting

Actual Live reads its schedules fresh from the database on every load, with no cache in the way, so reopening a job always shows the latest numbers, whatever the kiosk or another planner just logged. On top of that, saving an actual anywhere broadcasts a change notification, and an open Job View listens for it and reloads on its own. The practical result: an operator logs three hours at the machine, and the card on your screen updates without you reaching for a refresh button.

Logging From the Screen You Are Watching

Monitoring often turns into action, so Actual Live lets you log without leaving it. Double-click a node and the shared Log Actuals flow opens, the same one the Job View uses from its right-click menu, complete with the closed-operation check, the actual-start capture, and the prior-step prompt. A sub-assembly node first shows a step picker so you choose which child step you are recording against. Because it is the same launcher, both surfaces behave identically, and anything you log flows straight back into the cards you were watching.

Where It Sits in the Loop

Actual Live is the watching end of a loop that starts at the kiosk. Operators capture a production punch, those punches roll up into daily hours, and Actual Live paints them on the diagram. When the work is done, the plan only changes on the next reschedule, with completed steps frozen. For the planner-side path to enter the very same actuals, see logging actuals from the planner in EDGEBIC, and for the concepts underneath it all, what is production scheduling.

To see how this monitoring view fits the wider kiosk and actuals story, start at the EDGEBIC shop floor guide or the EDGEBIC product overview.