The Job View Cockpit: One Job in Full Depth in EDGEBIC

The Job View tab in EDGEBIC is a single-job cockpit: a summary panel that names the job and its planned window, an hours roll-up of total, actual, remaining, and percent complete, a per-operation grid, and its own Gantt strip, all focused on one job in full depth. EDGEBIC by User Solutions splits the scheduling surface into two tabs on purpose, and where the whole-plant Schedule View answers "what is the factory doing," Job View answers "where exactly is this one job." This post walks through the cockpit and how to read it.

The visual scheduling pillar guide covers the whole-plant Gantt; Job View is its close-up companion.

Two Tabs, Two Questions

EDGEBIC has two main Gantt surfaces, and knowing which to open saves time:

When you are balancing capacity across the floor, you live in Schedule View. When a customer asks about their order, or you need to know exactly which step of one job is running and how many hours are left, Job View is the tab. Pick a job from the Select Job dropdown and the cockpit fills in.

The Summary Panel: Identity and Plan

The top of Job View is a summary panel that states the job's identity and its planned window at a glance:

This is the frame for everything below it: what you are building, how much, and the window the engine planned it into.

The Hours Roll-Up: Real Progress, Not an Estimate

The most-read part of the cockpit is the hours header, and its trustworthiness is the whole point:

A worked snapshot: Total 16.5 hours, Actual 6.0, Remaining 10.5, 36.4 percent complete. Every one of those figures is summed live from the job's scheduled operations, so it moves as the floor logs hours. It is not a static estimate typed at order entry, which means a fully scheduled job never reads zero by mistake. When you quote a customer a percentage, this is the number to quote, because it reflects the real schedule and the real actuals behind it.

The Per-Operation Grid: Plan and Reality, Side by Side

Below the summary sits one row per operation, and this is where a bar's question gets its exact answer. Each row carries scheduled and actual dates, hours, pieces, rates, and completion flags:

• Sched Start / Sched End and Actual Start / Actual End put plan and reality in adjacent columns.
• Sched Hours / Actual Hours / Rem. Hours and the matching pieces columns quantify the work.
• Rate and Percent Complete and the completion flag tell you how each step is tracking.

Because the plan and the actuals sit side by side, the grid is planned versus actual in tabular form. When a bar on the strip raises a question the picture alone cannot answer, this grid answers it with exact timestamps. The same discipline reads across the whole plant in planned versus actual on the Gantt; Job View is that comparison for one job at maximum resolution.

The Gantt Strip and Its Scales

The cockpit includes its own Gantt strip for the selected job, and a View selector switches its timescale between Hour, Day, Week, and Month. Hour scale is for reading a single shift's detail; Month scale is for seeing a long job's whole arc. A Show as Hours toggle and a row-detail selector let you tune what the strip and grid display.

The strip follows the same drawing rules as the main Gantt. Once actual dates exist, a bar draws at its actual position while the scheduled dates stay in the grid columns, so the distance between the bar and its Sched Start column is your variance, visible without a report. A bar that seems to skip a day is usually just skipping a weekend, because bar positions follow the shift calendars.

The Date Window

A Start and End date-range pair above the grid controls which operations are in view. The default window is today minus 7 days through today plus 3 weeks, which frames the recent past and the near future for most jobs. Clear either picker to fall back to the job's own first or last date on that side, which is how you pull a long job's full span into view. Set an End before the Start and the window clamps to a single day.

Job-Level Actions in One Place

Job View is also the home for actions that apply to the whole job, gathered on the header:

• Log Actual to record hours for the job.
• Complete this Job and Reopen Job to mark it done or reverse that.
• Job Audit to see the full change history.
• Capacity Calendar, Import Actuals, and Export Excel for capacity, bulk actuals, and reporting.
• Re-Schedule to re-plan this job, which touches only this job and leaves the rest of the plant alone.

Having these on the same tab as the depth view means you read where the job stands and act on it without switching context. Getting here from a bar on the schedule board is a short path, traced in following a job from the Gantt to its routing. The execution details behind logging and completion belong to the shop-floor workflows, but the cockpit is where a planner sees the whole job and reaches for the right lever.

Why a Dedicated Cockpit

Schedule View is built for breadth: forty jobs, every lane, the balance of the plant. That breadth is the wrong tool when the question is "how far along is this one order and which step is running." Job View gives that question a home with the numbers a planner and a customer actually want, summed from the real schedule rather than an estimate, with plan and actual side by side at every level from the headline percentage down to the individual operation. It is the difference between seeing the whole factory and knowing one job cold, and mature scheduling needs both, exactly as any serious production scheduling practice does.

See the full EDGEBIC platform, or bring a live order to a demo and read its cockpit with US, from the headline percentage down to the operation running right now.