Factory Camera System Design Guide

Factory camera system design: zone-based scenarios, harsh-environment equipment, IT/OT network separation, OHS analytics, incident review and a maintenance plan.
Technical summary
Technology
IP cameras, IT/OT, analytics, VMS
Topic
Industrial design
Level
Intermediate
In this article8 sections

When cameras are installed in a factory with office logic, the first six months go smoothly, then the complaints start: lenses cloud over with oil vapor, the camera next to the press records blurry footage from vibration, the pallet label isn’t readable in the dock footage, and camera traffic strains the network the PLCs are on. When high ceilings, dust, temperature differences, forklift traffic and shift work all come together, the design must be done area by area, purpose by purpose. The approach below follows the order that works on site, from zone scenarios to equipment selection, from IT/OT separation to incident review and the maintenance plan.

Divide the factory into zones

Treating the facility as a single area ends with the same camera mounted at the same angle everywhere. The right way is to write down, for each zone, “what question will this camera answer?”. As the answer changes, so do resolution, lens, recording mode and retention requirements.

Zone Primary purpose Typical image goal Recording mode
Main entrance, gatehouse, turnstiles Person and vehicle logging Identification (spot), plates Continuous
Car park and vehicle yard Entry–exit, damage Observation + LPR Continuous / event
Goods receiving and shipping docks Loading and damage evidence Recognition, pallet/label detail Continuous
Warehouse and rack aisles Movement flow, forklift–pedestrian Observation Mainly event-based
Production lines OHS incidents, process evidence Observation / recognition By purpose
Technical rooms, server room Unauthorized access Recognition Continuous
Perimeter Intrusion detection Detection + analytics Event + continuous

Areas with a high expectation of privacy, such as rest areas, changing rooms, prayer rooms and toilets, are kept out of scope. This table is the scenario matrix described in the system design guide, adapted to a factory.

A common mistake at docks is mounting the camera at an angle wide enough to see the whole dock. The truck body is visible, the pallet label isn’t. When a claim comes in, the question is usually “which pallet was loaded with what damage?”, so the dock camera should look at the trailer door and the loading line, with two cameras (overview + detail) planned per dock if needed.

Equipment suited to harsh environments

Office-type dome cameras work on a factory ceiling but don’t last long. If environmental conditions aren’t written into the equipment list as specification items, purchasing will bring the cheapest model.

  • Dust and moisture: IP66/IP67 housings; in dusty areas, cleaning access should be part of the design.
  • Oil vapor and chemical environments: Lenses get dirty quickly; housing material and cleaning interval are set accordingly.
  • Vibration: Near presses and heavy machinery, sturdy brackets, short-arm mounting and fixed-focus lenses are preferred.
  • Temperature: Near casting, furnaces or cold storage, the operating temperature range and, if needed, cooled/heated housings.
  • High ceilings: As mounting height increases, target pixel density drops; lens selection and maintenance access (platform, lift) are planned together.
  • Electromagnetic noise: Fiber or shielded cable instead of copper near welding and large motors.

A motorized varifocal lens makes installation easier on high ceilings, but can drift out of focus in vibrating zones. Models whose focus can be locked after adjustment, or fixed-lens models, generate fewer service calls in these areas. Field cabling needs the same discipline: camera cable doesn’t share a tray with welding machine and VFD motor cables. If PoE switches are exposed to dust and heat inside a panel, industrial-grade models with a wide temperature range are chosen; an office switch inside a 50 °C panel fails sooner than expected.

IT/OT network separation

In production facilities, having cameras on the same network as PLC, SCADA and machine networks is an unacceptable risk. Camera traffic is kept in a separate VLAN, and only mandatory, documented connections are allowed between it and the OT network. NIST SP 800-82 recommends a zones and conduits approach in OT environments. The camera network itself is also separated according to the segment model in the camera VLAN guide.

In practice, the risk runs both ways. First, when multicast or heavy unicast video streams land on an unmanaged OT switch, delays and packet loss can occur in machine communication. Second, an unpatched camera, once compromised, becomes a jump point into the OT network. Routing from the camera VLAN to OT segments should be closed, cameras’ direct internet access blocked and management access opened only from the VMS server and the administrator network. If even one rule isn’t documented, it’s the first topic raised in an audit.

Analytics scenarios: what to realistically expect?

  • Forklift–pedestrian proximity and hazardous zone entry: Useful for near-miss data and instant alerts; doesn’t replace a machine safety system (hazardous zone analytics).
  • After-hours person detection: Turns motion alarms in empty areas into meaningful events.
  • PPE detection: For large equipment such as hard hats and vests; not reliable for small equipment.
  • Smart search: The analytics that gives the fastest return in customer claim and OHS investigations.

Camera analytics isn’t a safety function. Light curtains, safety relays and machine interlocks are designed according to the relevant machine safety standards; a camera alert is an extra layer added on top of them. State this clearly in the project documentation. Every scenario should be measured with a pilot; for acceptance metrics, see the AI person detection guide.

Design the incident review process

The moment a camera creates the most value in a factory is after an incident: a customer claim, a lost shipment, a workplace accident, machine damage. The recording exists, but nobody can find it. So the design must answer these questions:

  1. Who requests a review, and who approves it?
  2. What information is the recording searched by? (time, dock, shipment number, plate)
  3. How is the integrity of the exported recording preserved, and who is it handed to? (chain of custody guide)
  4. How is an incident recording protected from looped deletion, and when is it destroyed?

Clock synchronization of cameras and recording servers is the invisible prerequisite of this process. If NVRs and cameras aren’t tied to the same NTP source, the shipment time in the ERP and the time in the video drift by several minutes, and the review starts with the wrong scene. Integration with ERP/WMS can noticeably shorten review time by jumping directly from the shipment number to the relevant video (ERP/MES integration).

A note for automotive suppliers

TISAX assessments examine the physical protection of prototype areas, delivery zones and security areas. Video surveillance provides evidence for these controls but isn’t enough on its own; the recordings themselves must also be protected with access and retention rules (TISAX / ISO 27001 camera controls).

What the camera shouldn’t see in a prototype area is also a design decision. A camera recording the prototype part in detail becomes a confidentiality risk itself if broad access to its recordings is granted. The field of view focuses on entry and door movement, and recording access is limited to named users.

Maintenance plan

In dusty and oily environments, lens cleaning may be needed every three months or more often. Mounting, cabling and PoE checks, along with monitoring of recording continuity and disk health, are part of the plan. When the site layout changes (new line, rack, wall), coverage is rechecked.

Track maintenance in the monitoring system, not on paper. Minimum checklist:

  • Are “no recording” and “video loss” alarms enabled in the VMS and sent to a responsible person?
  • Is the oldest recording date checked weekly for each camera group?
  • Do disk SMART warnings and RAID status generate notifications?
  • Are lens cleaning and bracket checks scheduled by zone?
  • Are camera fields of view reviewed after rack or line layouts change?

Spare parts stock is also part of the plan. Waiting for a delivery to replace a failed camera at a dock or on the perimeter means leaving that zone unrecorded for weeks. For your facility, see our factory camera system service.

Frequently asked questions

Does putting cameras on a production line count as employee monitoring?

It depends on the purpose and setup. Cameras placed proportionately for OHS, quality evidence and security are different from individual performance tracking. The Turkish Personal Data Protection Authority emphasizes avoiding general performance monitoring in workplaces and informing employees; you should make the legal assessment with your legal team.

How many days of recordings should a factory keep?

There’s no fixed mandatory period. The organization sets it taking into account how long it takes for customer claims and incidents to surface, internal review processes and legal assessment; incident recordings are preserved separately.

Is it necessary to run separate fiber for the cameras?

If there’s distance between buildings, electromagnetic noise and grounding differences, fiber is usually the most reliable solution; spare cores in the existing fiber infrastructure can be used if available. If video or event data will be connected to production systems, map the existing network and data flows with a factory OT infrastructure survey.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Video Surveillance

IP cameras, recording and central management infrastructure. We plan blind spots, retention periods and the camera network around the risks of each site.

Knowledge Center

Other articles