Blog / Floor routines
Floor routines · Guide

Short Interval Control: How It Works and Template

OL By OEE Lab Editorial |Updated 1 November 2026 |7 min read
Short answer

Short interval control is a routine where the team compares actual output with the plan in short blocks, usually every hour. Each block ends with a gap, a cause and an action. It beats an end-of-shift report because you can still recover the lost output.

What short interval control is

Short interval control (SIC) is a floor routine. The team checks output against the plan in short blocks, usually one hour. If the block is behind, they name the cause and act before the next block starts.

The point is timing. A shift report tells you at 15:00 that the morning went badly. SIC tells you at 07:00 that the first hour went badly, while there is still a shift left to fix it.

SIC is not a meeting and not a software tool. It is a loop: target, actual, gap, cause, action. You can run it on a whiteboard (see the hour-by-hour production board) or on a screen.

The five steps of the loop

  1. 1
    Set the target for the block. Use the planned output for that hour, not the machine's top speed. Take breaks and changeovers out first.
  2. 2
    Count what was made. Good units only, from a counter, not from memory. Count within 5 minutes of the end of the block.
  3. 3
    Write the gap. Actual minus target, in units. Also keep a running total for the shift.
  4. 4
    Name the cause. One line, in plain words or a code from a short list. "Other" is not a cause. See downtime reason codes.
  5. 5
    Act or escalate. If the team can fix it in this block, fix it. If not, it goes to the supervisor with an owner and a time.

The SIC loop. It repeats every block. Each block ends with either "on plan" or an action with an owner.

Worked example: one line, six hours

Example: a packing line has a planned rate of 960 good units per hour. That is an ideal rate of 1,200 units per hour times a planned OEE of 80%. The supervisor checks each hour.

HourTargetActualGapRunning gapCause written down
1960980+20+20none needed
2960940-200slow start after break
3960720-240-240film splice jam, 15 min
49609600-240none needed
59601,010+50-190none needed
6960900-60-250carton misfeed, 4 stops
Total5,7605,510-2504.3% under plan

Example numbers, not real data. Hour 3 is the one that matters: 240 units at 16 units a minute (960 per hour) is 15 minutes of line time.

Hour 1102%
Hour 298%
Hour 375%
Hour 4100%
Hour 5105%
Hour 694%
Actual output as a share of target for each hour (the full bar is 110%). Red marks the hour that needs a response at once; amber is a small miss to watch.

An end-of-shift report would show the same -250 total. But it would show it at the end, when the film splice problem is old news. With SIC the supervisor sees the 75% at the end of hour 3 and can ask what happened, check the splice station, and decide whether the next hours need a different plan.

After hour 1+20
After hour 20
After hour 3 (splice jam)-240
After hour 4-240
After hour 5-190
After hour 6 (carton misfeed)-250
Running gap in units after each hour, from the table above (the full bar is 250 units). Teal is ahead of plan or on plan, red is behind. Hour 3 opens the hole, and hour 5 recovers only 50 units of it.

How long should the interval be?

There is no standard. The rule of thumb is this: short enough that one bad block is still recoverable, long enough that counting is cheap.

  • Fast lines with many small stops: 30 to 60 minutes.
  • Most discrete lines: 1 hour.
  • Slow, long-cycle work such as large machining or batch steps: 2 hours, or one block per cycle.

This is our judgment, not a published rule. Start with one hour and shorten it only if the team can act on every block.

Decide the escalation rule before the first red hour

A red hour with no rule leads to a long talk. Agree the rule in advance. For example:

  • First red hour: the team lead looks, fixes and writes the cause.
  • Second red hour in a row: the supervisor comes to the line.
  • Same cause twice in a shift: it goes on the list for the daily production meeting.

For stops, Overall Equipment Effectiveness (R. C. Hansen, 2001) describes a clock-based escalation tree. In his example the operator troubleshoots first, a technician is called at 30 minutes, and an engineer at 90 minutes. Build your own times from your best crews, not from a copy.

Template: one row per block

FieldWhat goes in itExample
BlockClock time08:00 to 09:00
TargetPlanned good units960
ActualGood units counted720
GapActual minus target-240
CauseOne line or a codeFilm splice jam
ActionWhat happens nextPre-cut splice tape at the station
Owner and timeName and whenTeam lead, before 10:00
Back on plan?Yes or no, next blockYes, hour 4 at 100%

Copy this onto a whiteboard or a printed sheet. Keep it to these eight fields; every extra column is one more thing nobody fills in.

Common mistakes

  • Target equals ideal rate. The row is red every hour, so nobody looks. Use the planned rate.
  • Counting at the end of the shift. Memory fills the gaps. The loop only works if the count is made in the block.
  • No cause written. A gap without a cause cannot be fixed or added up later.
  • No owner on the action. "We should check the splicer" is a wish, not an action.
  • Using the number against people. If a red hour leads to blame, the numbers will drift to green. Treat each gap as a process problem.
  • Too many measures. Output, gap and cause are enough. Add OEE at the end of the shift, not in every block.

How SIC relates to OEE

OEE is the score for the whole shift. SIC is the gauge you read during the shift. They use the same facts: how long the line ran, how fast, and how much of the output was good.

You can turn a gap in units into minutes. Divide the gap by the planned rate per minute. In the example, the shift gap is 250 units and the planned rate is 16 units a minute, so the line lost about 250 ÷ 16 = 15.6 minutes against plan. At the ideal rate of 20 units a minute (1,200 per hour) the same gap is 12.5 minutes of ideal run time.

Gap in minutes = gap in units ÷ rate per minute
250 ÷ 16 = 15.6 min against plan

This helps the team talk in time, which is easier to picture than units. "We lost 15 minutes in hour 3" is clear. "We are 240 under" needs a calculation.

Three questions for every red block

A red block has three possible sources. Ask which one it is before you decide what to do.

  • Did the line stop? Look at the stop log. If yes, how many stops and how long? This is availability.
  • Did it run slow? If it ran but made too few units, check the speed and the short stops. This is performance. See speed losses.
  • Did it make bad parts? Count the rejects in the block. This is quality.

The answer sets the action. A stop needs a fix or a call to maintenance. Slow running needs a look at the feed, the settings and the small stops. Bad parts need a check at the source. Writing the answer next to the gap is what makes the list useful at the end of the week.

What to do next

Pick one line. Set the hourly target, put a sheet at the line, and run it for two weeks. Then add up the causes you wrote down. That list is your first downtime Pareto, and it tells you what to bring to the gemba walk.

If you do not yet log stops at all, start with how to track downtime. To see where the time goes across the whole shift, use the OEE split into availability, performance and quality.

See it live in Fabrico

Short interval control only works if the count and the stop causes are right. Fabrico takes stops, speed and counts live from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line, so each block has its gap and its reason. See live stop tracking and OEE per line and shift.

Book a Fabrico demo

What people ask next

Is short interval control the same as an hour-by-hour board?

Not quite. The board is the tool, and SIC is the routine around it. You can run SIC on a board, a sheet or a screen, as long as the loop of target, actual, gap, cause and action happens in every block. The board is covered in hour-by-hour production board.

Who should run short interval control?

The team lead or the operator closest to the line should fill in the numbers. The supervisor reacts to red blocks. If only the supervisor does it, it turns into a report and loses speed.

What target should I use for each block?

Use planned output for the block: ideal rate times scheduled minutes in the block times your planned OEE. For example, 1,200 units an hour times 80% gives 960. Take out breaks and known changeovers first. See how to set OEE targets.

How is it different from the daily production meeting?

SIC works inside the shift, hour by hour, and fixes things now. The daily production meeting looks back at the last day and sets actions for the next one. They feed each other: the gaps and causes you write in SIC are the data for the meeting.

Does SIC need software?

No. A whiteboard works. Software helps when counts and stop times come from the machine, because then the actual column does not depend on someone counting. See free shift report software for a low-cost start.

Related guides: OEE Dashboard Examples: 6 Layouts That Work · End of Shift Losses: The Last Hour Pattern · MES Dashboard: What to Show and Who Acts on It · Takt Time Board: What to Show and How to Run It

← More OEE Lab guides · Open the OEE calculator →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES