How downtime tracking without sensors works
The camera sees the stop and the count, not the cause. Determining why a machine stopped requires additional information.
A fixed camera at each machine views the work area. FactoryVision counts visible finished parts, tracks downtime and compares station output with the day's target. The models run on a small computer in the factory, not in our cloud.
The system shows one status light per station:
- **Green:** Output is on track against the day's target.
- **Yellow:** The target is at risk.
- **Red:** Output is behind the target.
What the camera sees—and what it does not
FactoryVision counts finished parts that are visible to the camera and tracks downtime. The camera sees the stop and the count, but it does not identify the cause.
Examples of downtime reasons include machine faults, changeovers and waiting for material. Establishing the reason requires information beyond the camera view.
Which production processes fit?
FactoryVision fits countable, discrete parts that the camera can see, including doors, furniture and metal parts. Continuous output, such as extrusion, is outside its stated scope.
The camera counts what is in view. Seeing the back of a part requires a second camera, while shiny or transparent parts need lighting work.
FactoryVision runs in a Turkish door and furniture factory.
Setting up a station
- **Mount and aim the camera.** Use a fixed mount. Check the live view and adjust the angle and focus.
- **Place the printed marker.** Place the printed marker in the camera’s view.
- **Teach the cycle.** Teaching a cycle takes ten parts.
The setup target is under an hour per station. There are no sensors to fit and no wiring into the machine.
How FactoryVision fits with factory software
FactoryVision counts finished parts, compares station output with the day's target and tracks downtime. It is not an ERP, MES or SCADA system.
Sources and claims
| Claim or number | Source |
|---|---|
| One camera per machine; ten parts to teach a cycle | Supplied house-style sample, `count-finished-work-with-one-camera` |
| Setup target under an hour per station | Supplied house-style sample |
| Green, yellow and red station lights reflect progress against the day's target | Supplied house-style sample |
| Models run on a small computer in the factory; no sensors or wiring into the machine are required | Supplied house-style sample |
| Discrete-part scope, examples, continuous-process exclusion and camera-view limits | Supplied house-style sample |
| FactoryVision tracks downtime; the camera sees the stop and count, not the cause | Supplied founder facts and Topic T09 notes |
| FactoryVision runs in a Turkish door and furniture factory | Supplied founder facts, 2026-11-13 |
| FactoryVision is not an ERP, MES or SCADA system | Supplied house-style sample |
| Buying starts with an introductory call; the setup is fitted to the company's machines and processes | Supplied founder facts, 2026-11-13 |
Frequently asked questions
Do I need sensors or a PLC connection to track downtime?
FactoryVision tracks downtime from visible production activity without fitting additional machine sensors or wiring into the machine.
Does the camera identify the cause of a stop?
No. The camera sees the stop and the count, not the cause. Determining the reason requires additional information.
How many parts does it take to teach a cycle?
Teaching a cycle takes ten parts.
Where do the models run?
The models run on a small computer in your factory, not in our cloud.
How long does setup take?
The setup target is under an hour per station.
Next step
Book an introductory call with FactoryVision. After the call, we get to know your company so the setup fits your machines and processes.