The EDGEBIC Timeline Board Explained: A Resource View of the Schedule

EDGEBIC by User Solutions offers a resource-centric timeline board that puts each work center on its own lane and lays every operation booked to it along a shared time axis, so you read the plant by machine rather than by job and see where jobs contend for the same resource at the same hour. Most schedule views are organized around the job: here is this order, here are its steps, here is its finish date. The timeline board rotates that intent to organize around the resource, which is the view you need the moment two jobs start fighting over one machine.

This is the natural companion to the Job Gantt view. The Gantt reads a single job end to end; the timeline board reads a single work center across every job. Same schedule underneath, two ways of looking at it, each answering a question the other cannot.

Rows Are Resources, Not Jobs

On the timeline board the vertical axis is your list of work centers, and each one owns a lane. The horizontal axis is time. Every operation the scheduler has booked to a resource appears as a block in that resource's lane, positioned by its planned window. Read one lane left to right and you have that machine's whole future in order.

That reorganization changes what is easy to see. In a job view, a machine's total load is invisible: it is spread across dozens of separate job rows and you would have to add it up in your head. On the timeline board the load is the lane. A resource that is booked solid shows a continuous run of blocks with no gaps; a resource that is idle shows a lane that is mostly empty. You learn the shape of your plant's demand by scanning down the lanes.

Reading Contention

The single most useful thing the board does is make contention visible. When two operations from different jobs both want the same work center in the same window, they crowd the same slice of that lane. That crowding is the physical fact behind an over-100-percent utilization number, made concrete.

This is why the board pairs so well with the numeric capacity tools. The work center utilization report tells you a resource is at 104 percent on Thursday; the timeline board shows you which two jobs are stacked in that lane on Thursday, so the abstract overload becomes an actual pair of orders you can referee. For the department roll-up of the same load, department capacity analysis aggregates the lanes.

Same Schedule, Different Question

It is worth being precise about the relationship between the board and the other schedule surfaces, because they all read the same committed plan and never disagree.

The Gantt asks, is this job on track. The timeline board asks, is this machine overbooked. The work center dispatch report asks, what should this station run next, and prints the answer. The reports carry the exact numbers and the export trail; the board and the Gantt carry the shape. You reach for the board specifically when your question is about a resource and the jobs competing for it, rather than about one order's health.

A Read Surface for Judgment

Like the other visual surfaces, the timeline board is primarily a read view. It shows you the consequence of the scheduler's decisions so you can judge them. When the judgment is "this bottleneck is stacked wrong," you act through the tools built for changing a schedule: reprioritize and re-run, or make a targeted move on the Gantt and save it. The board is where you decide something is wrong; the reschedule path is where you fix it. For the mechanics of that fix, see how to reschedule safely.

Where the Board Earns Its Keep

Three situations make the resource view the right first screen. Refereeing a bottleneck, where you need the true competing queue on one machine rather than scattered across jobs. Balancing load across similar work centers, where you want to see one lane running hot while its neighbor sits idle. And building the qualitative case for capacity, where a lane that is continuously wall to wall over several weeks is the picture that goes next to the utilization percentage in a machine-purchase conversation.

For machines that are truly interchangeable and pooled, the load story extends into the work center groups feature, where a shared calendar sums the members. And for the whole scheduling system these views observe, the complete EDGEBIC guide is the starting map.

The Point of Turning the Schedule Sideways

A schedule is a relationship between jobs and resources, and you cannot see both truths from one orientation. Job-centric views make an order legible and hide the machine's total load. The timeline board makes the machine legible and lets you referee the fights over it. Keeping both orientations one click apart is what lets a planner move between "is this order fine" and "is this machine drowning" without ever losing the same underlying plan.

Want to see your own machines laid out in lanes? Bring an export to a demo and we will show you where your plant contends.