A hot-strip mill or blast furnace crew can hit its shift-end tonnage number and still have quietly lost four hours of pace somewhere in the middle of the shift — a slow changeover here, an unplanned idle stretch there, none of it visible until the shift log is reconciled the next morning. By then the root cause is a guess, not a fact, and the next shift inherits the same gap without knowing it exists. Tracking target versus actual output hour by hour, rather than only at shift-end, is what turns a pace problem from a mystery into a fixable pattern operators and maintenance can act on together. Book a demo to see hourly pace tracking running against your own mill's shift data.
Steel Shift Target vs Actual Software: The Hourly Pace Guide
How hot-strip mills, blast furnaces, and casters track hourly pace against plan, catch the gap before shift-end, and turn variance into a defensible record instead of a shift-log argument.
Why Shift-End Totals Hide the Real Story
Shift-end tonnage is the number that goes on the board, but it is the least useful number for actually fixing a pace problem. A crew that finishes a shift at 92 percent of target could have been running dead on pace for six hours and then lost the equivalent of two full hours to a single changeover or a minor equipment stoppage nobody flagged in real time. Without an hourly breakdown, that loss gets absorbed into a single end-of-shift variance figure, and the next planning meeting spends more time debating whose fault the shortfall was than fixing what caused it. Multiply that pattern across three shifts a day, seven days a week, and a mill can lose thousands of tons of annual capacity to gaps that were never individually large enough to trigger a formal investigation, yet collectively represent a meaningful share of the plant's total output potential.
A shift that averages 92 percent of target across eight hours can still have a single hour that dropped to 44 percent — the number every root-cause conversation should start from, not the shift average.
Building the Pace Board: What an Hourly Target vs Actual System Actually Tracks
An hourly pace board is only as useful as the categories behind it. Log too little detail and every gap looks the same regardless of cause; log too much and operators stop entering data accurately because it slows down the job. The table below breaks down the core data points a target-versus-actual system needs to capture every hour, and what decision each one supports once the shift is over, based on the categories that consistently prove useful across hot-strip mills, blast furnaces, and continuous casters without overloading the person entering the data mid-shift.
| Data Point Logged Each Hour | Captured From | Decision It Supports |
|---|---|---|
| Planned tonnage or units for the hour | Production schedule loaded at shift start | Sets the baseline every actual hour is measured against |
| Actual tonnage or units produced | Automated line counter or operator entry at hour-close | Calculates real-time pace percentage against plan |
| Downtime minutes and stated reason code | Operator-logged stoppage entry tied to a standard reason list | Separates mechanical loss from process or material loss |
| Changeover or grade-change duration | Timestamp between last coil of one grade and first of the next | Flags changeovers running longer than the standard allowance |
| Speed or rate deviation from set point | Mill control system feed where available | Identifies conservative running versus a genuine equipment constraint |
Stop Explaining Shift Variance. Start Tracking It Hour by Hour.
OxMaint's shift pace tracking logs target versus actual output every hour, ties downtime and changeover loss to a maintenance work order automatically, and gives every shift a record that survives the handoff to the next crew.
The Four Root-Cause Categories Behind Every Pace Gap
Once hourly variance is visible, the next step is sorting the cause into a category the plant can actually act on. Steel plants that track pace well generally converge on the same four buckets, because each one points to a different owner and a different fix.
From Pace Gap to Work Order: The Shift Handoff Workflow
The value of hourly tracking compounds when a logged pace gap automatically becomes an actionable record instead of a line in a shift log that the next crew has to rediscover on their own. The sequence below shows how a single hour of lost pace should move from the floor to a documented fix, so that the fifteen minutes an operator spends flagging a stoppage in real time saves a maintenance planner an hour of reconstructing the same event from a paper log the following morning.
Setting Hourly Targets That Are Actually Achievable
Hourly tracking only produces useful data if the hourly target itself is realistic. A target built from a single best-ever hour of production sets every crew up to look like they are underperforming, while a target padded too generously to avoid friction hides real losses inside a comfortable-looking average. The plants that get this right typically build the hourly target from a rolling trailing average of actual good-run hours for that specific product mix, adjusted for known constraints like scheduled changeovers or grade transitions built into that shift's plan. That target then gets reviewed on a fixed cadence — monthly or quarterly is common — so a genuine equipment upgrade or process improvement gets reflected in a higher target, rather than the plant quietly running better than plan for a year without anyone updating the baseline. Getting this calibration right matters more than the software itself, because even the most detailed hourly pace board produces noise instead of insight if the target it is measuring against does not reflect what the line can actually do on a normal day.
It also matters who sets the target and who can see it change. When operators have visibility into how the hourly number is calculated and a channel to flag when a target does not account for a known constraint — a scheduled inspection, a documented material quality issue, a planned partial-speed run — the pace board becomes a shared reference point rather than a management scorecard used against the crew after the fact. That distinction is often what determines whether a shift team actively logs accurate reason codes in real time or waits until the report is due and reconstructs the shift from memory, which defeats the purpose of hourly tracking entirely.
Expert Perspective
Frequently Asked Questions
Turning Hourly Data Into a Weekly and Monthly Pattern
A single shift's hourly breakdown tells you what happened yesterday. The real payoff arrives once hourly entries accumulate into weeks and months of history, because patterns that are invisible at the shift level become obvious across a longer window. A mechanical reason code that shows up on the same asset three times in two weeks stops looking like a series of unrelated stoppages and starts looking like a bearing or a drive component that needs a planned replacement before it fails again during a production run. A changeover that consistently runs ten minutes over standard across every shift, not just one crew, points to a process step that needs to be re-timed rather than a training gap with a single team. And a rate deviation that only appears on the night shift, night after night, often points to a lighting, staffing, or communication issue that a day-shift manager would never otherwise see, because they are not on the floor when it happens.
This is also where hourly pace data earns its place in front of plant leadership and, in many operations, the corporate finance team reviewing capital allocation. A maintenance manager asking for budget to replace an aging drive system has a far stronger case with six months of hourly downtime data tied to that specific asset than with a general statement that the equipment is old and unreliable. The same is true for a scheduling change — a production planner proposing to group similar grades together to cut changeover time has hard numbers to back the request instead of an anecdotal sense that changeovers take too long. Hourly target-versus-actual tracking, in other words, is not only a floor-level tool for the current shift; over time it becomes the evidence base for the capital and process decisions that actually move the plant's baseline performance forward.
Give Every Shift the Hourly Record the Next Crew Actually Needs.
OxMaint tracks target versus actual output hour by hour, sorts variance into mechanical, changeover, material, and rate categories automatically, and turns every mechanical pace gap into a work order the maintenance team can act on before the next shift starts.
