Menu
Book a demo
Light MES · Manufacturing performance platform

Downtime video analysis Open the minute a line stopped, then set the cause yourself.

An overhead camera counts output where a machine has no usable signal. From the shift timeline, your team opens the video for the minute of a stop or slowdown at a camera station, streamed on request and not stored in Fabrico, and sets the downtime code. Suggested causes are on our roadmap.

  • Camera only where there is no usable signal
  • Video streamed on request, not stored in Fabrico
  • Your team sets the cause
Illustration, not a camera view

Trusted by FMCG, food and industrial manufacturing groups

ABBSchaefflerHitachi Energykdc/oneLufthansa TechnikAkzoNobelFicosota
Fabrico · Light MES

A short stop at the labeller, seen on video

It is 14:20 on a jar line. The line stops three times in ten minutes, each time for under a minute. The shift log will say "labeller", and the cause would usually be a guess made at the end of the shift.

The infeed conveyor before the labeller has no usable signal of its own, so a camera over it counts output. The supervisor opens the shift timeline, clicks the first stop and watches the video for that minute at the infeed. Jars are arriving skewed from the conveyor. The operator sets the downtime code to "infeed: product skewed" and maintenance looks at the guide rail, not the labeller.

That is the live feature: the video of the stop, and a person who decides the cause.

Live on the camera today, and what stays roadmap

The camera add-on is enabled per plant on request.

CapabilityStatus
Count output at a station where the machine has no usable signalLive
Open the video for the minute of a stop or slowdown from the shift timelineLive
The camera suggests a likely cause for a stop, for the team to confirmRoadmap

Suggested: no material

Suggested: operator waiting

Suggested: broken part

Roadmap feature, example suggestions only, not a screen capture

Your team sets every downtime code. The camera count is output only: it does not inspect quality, detect defects or monitor safety.

Signal or camera: which stations need one

Most machines do not need a camera for their count. Fabrico takes stops and output from the machine signal, or from a Fabrico IoT device with sensors on older machines. The camera is for the stations those cannot count. This table is a first sort before the process review.

What the station hasWhere the count comes fromCamera?
A machine with a usable signalThe machine signalNo
An older machine where sensors can be fittedA Fabrico IoT device with sensorsNot if the sensors count
A machine whose signal gives no usable countA hand tally or estimateYes: the camera counts output
A manual or hybrid station, such as hand packingOperators entering produced items in manual modeAsk in the process review: whether a camera can count there is checked per station

Stop video is available only at camera stations. The number of cameras per line is agreed after a review of your process, one overhead camera above or beside each workstation it covers.

Who opens the stop video, and at which point

Who can open the video is set by role. Typical moments:

  • Line supervisor, right after a stop: opens the video for that minute before asking the crew what happened.
  • Operator, when a stop needs a code: checks the video, then sets or corrects the downtime code.
  • Maintenance technician, before going to the machine: sees whether the problem was the machine or the material feeding it.
  • CI engineer or team leader, in the weekly loss review: watches the video for the short stops that keep coming back.

Four stops where the video ends the argument

Each of these is at a camera station: a station without a usable signal, where the camera counts output.

1. Short stops nobody wrote down

A stop of under a minute rarely gets a good reason from memory. The video for that minute shows what happened.

2. Machine fault or material problem

A station stops and the log says "mechanical". The video shows the material feeding it arriving late. The right team gets the job.

3. Waiting, not breaking

A station stands still with nothing wrong with it. The video shows it waiting for material or for an operator, which is a different fix from a repair.

4. Two shifts, two stories

Two shifts give the same stop different causes. The supervisor opens the video for both and the team agrees one code.

From a stop on the timeline to a downtime code

  1. Fabrico records the stop on the shift timeline.
  2. Someone with access clicks the stop at a camera station and opens the video for that minute, streamed on request.
  3. The operator or supervisor sets the downtime code, or corrects one that was entered from memory.
  4. The coded stop counts in OEE by machine, line and shift, and in the downtime reports.
The stops on a line. Real Fabrico screen, sample data.The stops on a line. Real Fabrico screen, sample data.

What a camera station needs, and the camera's limits

It needsIt does not
The camera add-on, enabled for your plant on requestSuggest a stop cause today: that is on our roadmap
One overhead camera above or beside each workstation it coversGive stop video at stations without a camera: only camera stations have it
A process review that sets the number of cameras per lineInspect quality or detect defects: quality inspection is not part of Fabrico
Roles that set who can open the videoMonitor safety: the camera counts output only
A downtime code list your operators useDecide the cause: your team sets the downtime code

Stop video next to OEE and light MES

The video opens from the same shift timeline where Fabrico shows stops, output and OEE by machine, line and shift: the base of OEE software and light MES, with maintenance built in.

A coded stop feeds the downtime reports in downtime tracking software, and from there a technical stop can become a maintenance task. A code list your operators actually use matters more than the camera: see OEE reason codes. For camera counting itself, see computer vision for OEE, and for the other add-ons the AI add-ons for manufacturing.

The stop list your downtime codes go into. Real Fabrico screen, sample data.The stop list your downtime codes go into. Real Fabrico screen, sample data.

Downtime codes from memory vs from the video

StepCode from memory or paperCode after the stop video
When the cause is setOften at the end of the shiftAfter someone watches the minute of the stop
Short stopsLumped together or left outEach one on the timeline, with video at camera stations
Disputed causesOne person's word against another'sThe team watches the same video
Who gets the jobWhoever the log namesThe team the video points to: maintenance, material or the line

Questions about downtime video analysis

How many cameras does it take?

One overhead camera above or beside each workstation it covers. The number per line is agreed after a review of your process.

Is the video stored?

No. Video for a stop is streamed on request when someone opens it on the timeline and is not stored in Fabrico. Who can open it is set by role, and any other setup is agreed per plant in writing.

Does the system decide the cause?

No. Your team sets the downtime code. Suggested causes from the camera are on our roadmap.

What does the camera count?

Output, at stations where the machine has no usable signal. It does not inspect quality, detect defects or monitor safety.

Do we need a camera on every machine?

No. Where a machine gives a usable signal, Fabrico takes the count from it. The camera is for stations without one.

Can we open the video for a slowdown, not only a stop?

Yes. At a camera station, the team can open the video for the minute of a stop or a slowdown from the shift timeline.

How is the camera add-on switched on?

It is enabled per plant on request.

Book a demo to see the shift timeline, the stop list and how a downtime code is set, and to talk through which of your stations would need a camera.

By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy and Cookies Declaration