Job History
Job History is the OEE Jobs page for reviewing job runs across the selected date range. It combines a group-primary job table with batch, station, and operator timelines.
Job Runs Summary
The Job Runs header summarizes the filtered table:
| Metric | Meaning |
|---|---|
active / total | Active jobs with current operator labor, shown against the total number of unique jobs in the filtered range. |
idle | Open jobs with no current operator labor. This appears when at least one filtered job is open but nobody is clocked in. |
over std | Active jobs whose operator time is at or above earned standard hours. |
An Active job is not just an open job record. It has at least one open oee_time_entries row for a person: batch_id matches the job, user_id IS NOT NULL, and end_ts IS NULL. Open jobs without active operator labor are Idle. See Job Time Tracking for how person-hours accumulate on jobs.
Standard-Hours Threshold
The over std count uses the same standard-hours threshold family used by Process Flow and station active-job views:
| Level | Condition |
|---|---|
| None | Operator time is below earned standard hours, or the job has no usable standard. |
| Over standard | Operator time is greater than or equal to earned standard hours. |
| Severe | Operator time is greater than or equal to 2x earned standard hours. |
The Job Runs header counts both over-standard and severe active jobs in over std; severe jobs use the danger styling.
Expanding Job Runs
The Job Runs table is grouped by job number. Expanding a job shows one row per station run for that job. This is the right surface when the question is “where did this job have a station instance, and when did that station run start and end?”
The selected date range decides which job numbers appear in the table. Once a job number is visible, expanding it shows the job’s full non-archived machine-event history, including station visits outside the selected range. Expanded rows may include staging, queue, receiving, or other station visits that have no operator labor. If the same station name appears more than once, those rows are separate station-run instances for the same job, not duplicate shifts. Archived machine events are excluded from both the Job Runs expansion and the job focus page’s machine-event journey.
The group row’s Last Station (N stations) label, the expanded station-run rows, and the job focus page use the same full-journey scope for any job selected by the current range.
Each station run row uses the same metric columns as the parent job row:
| Metric | Meaning |
|---|---|
| Dwell | Wall-clock time for that station run. |
| Labor Hrs | Operator labor hours recorded on that station run. |
| Standard Hrs | Standard hours earned for that station run. |
| Effectiveness | Standard hours divided by operator labor hours for that station run. |
Expanding a station run shows the operator shifts recorded under that station run. Shift rows show the operator, whether the person is still on shift, the station, the shift duration, and the clock-in to clock-out window. Editing a running shift from Job History or the job focus page allows the user to set a Clock Out time for that entry. If no shifts are recorded for the station run in the selected range, the expanded row states that directly.
Job Focus Station Counts
The job focus page at /oee/job-history/:jobNumber shows a Station visits table. That table is machine-event-first: it shows the same full non-archived station-run journey as the Job Runs expansion, including queue or receiving rows that have no operator labor. The Total Labor KPI sums operator labor across those station visits, and its sublabel counts station visits.
Use these surfaces for different station questions:
| Question | Use |
|---|---|
| Which job numbers had any station visit in the selected date range? | Use the Job Runs table and the selected date range. |
| Which station visits belong to this job number? | Expand the job in the Job Runs table or open the job focus page. |
| Which station visits had operator labor and effectiveness metrics? | Read the Labor Hrs, Standard Hrs, and Effectiveness columns. |
The station-visit counts match between the Job Runs expansion and the job focus page. Labor, Standard, and Effectiveness can still be empty for a visit when no operator time or no standard exists for that station run.
Job Focus KPI Row
The job focus KPI row summarizes the selected job:
| Metric | Meaning |
|---|---|
| Turnaround | Wall-clock time from the job’s first start to completion, or the current in-progress duration for open jobs. |
| Total Labor | Sum of operator labor time across the job’s station visits. |
| Longest Dwell | Longest wall-clock station visit in the job journey. |
| Parts | Good and scrap part counts for the job. |
Job Focus Timeline
The job focus page includes a Timeline section with two modes:
| Mode | What it groups |
|---|---|
| By station | Job activity grouped by station or equipment. |
| By operator | Operator labor entries grouped by technician. |
The timeline range automatically fits the bars visible in the active mode. Switching between By station and By operator recalculates the range for that mode, and hiding or showing rows with no entries recalculates the station timeline range without changing the underlying job data window.