IoT Sensor Network for Factory Predictive Analytics

By Jacob Bethell on March 14, 2026

iot-sensor-network-factory-predictive-analytics

Every machine tells a story through data — vibration spectra that reveal bearing wear months before failure, temperature gradients that signal insulation breakdown, current signatures that fingerprint motor health, and pressure traces that detect valve degradation in real-time. But capturing this data reliably at factory scale requires more than bolting sensors onto machines. It requires an end-to-end IoT sensor network designed from the ground up: the right sensor types matched to each failure mode, the right connectivity protocol for each environment, edge gateways that process data locally, time-series databases that handle millions of data points per second, and AI pipelines that convert raw signals into maintenance predictions. Sensors bolted on as an afterthought create data gaps, unreliable connections, and analytics that don't trust the source data. Greenfield design solves this permanently. Plan Your IoT Sensor Network — we design sensor placement, connectivity, gateways, and data pipelines as construction-ready documentation.

Factory IoT Sensor Ecosystem
~VibrationTri-axial MEMS/piezo; 25-100 kHz; bearings, gears, spindles
°TemperatureRTD, thermocouple, IR; process, surface, ambient
PressurePiezoresistive, capacitive; hydraulic, pneumatic, process
ACurrent/PowerCT clamp, Hall effect; motor signature, energy monitoring
FlowUltrasonic, Coriolis, magnetic; coolant, process fluid, compressed air
Oil/ParticleInline particle counter, moisture sensor; gearbox, hydraulic health
Acoustic/UltrasonicLeak detection, bearing defect, cavitation; airborne + structure-borne
All sensor types connected through unified gateways → time-series DB → AI analytics → CMMS

The Afterthought Problem: Why Retrofit Sensor Networks Fail

Data Gaps

Retrofit installations skip hard-to-reach assets because cable routing is too expensive or disruptive. The machines you can't monitor are usually the ones that fail catastrophically. In greenfield, every critical asset has sensor provisions designed into the mechanical and electrical drawings before construction.

Unreliable Wireless

Metal structures, EMI from VFDs, and RF-congested environments create dead zones and packet loss. Retrofit wireless sensors are placed where it's convenient — not where coverage is optimal. Greenfield design maps RF propagation before walls go up and positions access points for guaranteed coverage.

Untrusted Data

Sensors mounted on vibrating surfaces without isolation, cables sharing trays with power lines, and uncalibrated instruments produce data that AI models can't trust. Garbage in, garbage out. Greenfield specifies isolated mounting pads, dedicated signal conduit, and commissioning-time calibration procedures.

Scalability Dead Ends

Retrofit networks grow organically — different protocols, different vendors, different gateways. By the time you reach 500 sensors, you have 5 incompatible ecosystems. Greenfield designs a unified architecture from the start that scales from 100 to 10,000+ sensors on one platform.

Building a new factory and want sensors that work from day one? Plan Your IoT Sensor Network — we deliver sensor maps, protocol selection, gateway architecture, and data pipeline specs as construction-ready documents.

Connectivity Protocol Selection

No single wireless protocol covers every factory IoT requirement. The right network design uses a hybrid of protocols matched to each use case — high-bandwidth wired for critical assets, mesh wireless for dense indoor monitoring, and LPWAN for campus-wide coverage.

ProtocolRangeData RatePowerLatencyBest Factory Use CaseGreenfield Design Note
Wired (4-20mA / HART)1,500mContinuous analogLoop-powered<1msCritical process instruments (T, P, flow, level)Conduit and junction boxes designed into equipment foundations
Industrial Ethernet100m (copper); km (fiber)100 Mbps-10 GbpsPoE available<1msHigh-speed vibration, vision, PLC integrationDedicated sensor Ethernet VLAN; fiber backbone pre-installed
WiFi 6/6E30-50m indoorUp to 9.6 GbpsMedium-High1-10msMobile instruments, tablets, high-bandwidth edge devicesIndustrial AP locations planned for coverage; metal interference mitigated
Bluetooth 5.0/BLE10-30m2 MbpsVery low10-100msSensor configuration, short-range data collection, asset trackingBLE gateways positioned at machine clusters for reliable pairing
Zigbee / Thread10-100m (mesh extends)250 kbpsLow15-30msDense indoor sensor mesh; environmental monitoringMesh topology self-heals; plan initial node density for redundancy
LoRaWAN2-5 km (indoor: 200-500m)0.3-50 kbpsUltra-low (5-10 yr battery)1-10 secCampus-wide: utility meters, tank levels, environmental, non-critical assetsGateway on rooftop or elevated position; 1 gateway covers entire plant
Private 5G / LTE-MPlant-wide10-100 MbpsMedium1-10msMobile robots, AGVs, high-reliability wireless for critical monitoringSmall cell locations designed into facility; licensed spectrum if available

Sensor-to-Machine Mapping

Machine TypeTotal Sensor PointsWiredWirelessKey Parameters MonitoredEst. Cost/Machine (Greenfield)
Large Motor (>100 HP)6-84 (vibration, current)2-4 (temp, environment)Vibration (DE/NDE), current signature, winding temp, bearing temp$800-$1,500
Centrifugal Pump5-73 (vibration, pressure)2-4 (temp, flow)Vibration, suction/discharge pressure, flow, seal temp, motor current$700-$1,200
Gearbox/Reducer5-84 (vibration, oil)1-4 (temp, acoustic)Vibration (I/O bearings), oil particle count, oil temp, acoustic emission$1,000-$2,000
Air Compressor8-126 (vib, P, T, current)2-6 (ambient, leak)Vibration, discharge P/T, oil pressure, current, air leak ultrasonic$1,200-$2,500
Conveyor System4-10 (per drive)2 (motor vib, current)2-8 (roller vib, belt)Drive motor health, roller bearings (sampled), belt tension, tracking$500-$1,500/drive
HVAC/AHU4-61-2 (power)3-4 (temp, humidity, vib)Fan vibration, filter dP, discharge temp, power consumption$400-$800
Utility (Boiler/Chiller)10-158-10 (process instruments)2-5 (supplemental)Pressure, temperature, flow, combustion O2, vibration, level$2,000-$4,000

Gateway & Edge Processing Architecture

Tier 1: Protocol Gateway

Sensor-to-Network Translation

Converts sensor protocols (4-20mA, Modbus RTU, BLE, LoRaWAN) to IP-based data streams (MQTT, OPC UA). One gateway per machine cluster or zone (typically 10-50 sensors per gateway). Greenfield: gateway mounting locations and power/network drops designed into equipment layout.

Tier 2: Edge Processor

Local Analytics & Anomaly Detection

Runs threshold detection, spectral analysis, and basic ML models on-premise. Reduces data volume by 90-95% before cloud transmission (send features, not raw waveforms). NVIDIA Jetson or industrial PC with GPU. Greenfield: edge compute rack space, power, and cooling included in server room design.

Tier 3: Data Broker

Message Routing & Buffering

MQTT broker (Mosquitto, HiveMQ, EMQX) or OPC UA server aggregates all sensor data into unified topic structure. Handles message queuing during network disruptions (store-and-forward). Provides pub/sub architecture for multiple analytics consumers. Greenfield: broker runs on edge server with redundancy.

Tier 4: Time-Series DB

High-Performance Data Storage

InfluxDB, TimescaleDB, or QuestDB for storing sensor data at million-point-per-second ingest rates. 30-90 day high-frequency data retention locally; downsampled data archived to cloud/object storage. Greenfield: storage capacity and IOPS requirements factored into server room design.

Need help selecting the right gateway and edge architecture for your sensor count? Plan Your IoT Sensor Network — we'll specify gateway counts, edge compute requirements, and TSDB sizing based on your asset inventory.

Scaling: 100 to 10,000+ Sensors

ScaleSensor CountGatewaysEdge ComputeTSDB Ingest RateNetwork BackboneTypical Plant Size
Pilot50-1002-51 industrial PC~10K points/secExisting Ethernet + 1 LoRaWAN GWSingle line or critical asset cluster
Department100-5005-201-2 edge servers (GPU optional)~50K points/secDedicated VLAN + 2-3 LoRaWAN GWProduction department or building
Plant-Wide500-2,00020-502-4 edge servers with GPU~200K points/secFiber backbone + campus wirelessFull manufacturing facility
Enterprise2,000-10,000+50-200Edge cluster (4-8 servers)1M+ points/secRedundant fiber + private 5G + cloud syncMulti-building campus or multi-site

Data Pipeline: Sensor to AI to Action

1
Sensor → Gateway

Physical measurement converted to digital signal. Protocol translation (Modbus, BLE, LoRaWAN → MQTT/OPC UA). Data validated, timestamped, and tagged with asset ID. Latency: 1-100ms depending on protocol.

2
Gateway → Edge Broker

MQTT pub/sub distributes data to multiple consumers. Store-and-forward handles network disruptions. Topic structure: plant/area/asset/sensor/parameter. QoS levels configured per criticality.

3
Broker → Time-Series DB

High-speed ingest into InfluxDB/TimescaleDB. Continuous queries calculate rolling averages, RMS, peak values. Retention policies: raw data 30-90 days local, downsampled indefinitely in cloud/archive.

4
TSDB → AI Analytics

ML models consume feature-engineered data. Anomaly detection, RUL estimation, failure classification. Edge inference for real-time alerts; cloud training for model improvement. Results written back to TSDB for dashboarding.

5
AI → CMMS / Dashboard

Predictions trigger auto work orders in iFactory CMMS. Dashboards (Grafana, Power BI) show asset health, trends, and alerts. Mobile app notifies technicians. Closed-loop: repair outcomes feed back to improve models.

Key Benefits & ROI

100%Critical asset coverage — no blind spots, no skipped machines
<1 secData latency — sensor to analytics engine in under a second
99.9%Data availability — redundant paths, store-and-forward, mesh healing
100–10K+Sensor scalability — unified architecture grows without rearchitecting
1 PlatformUnified dashboard — all sensors, all protocols, all assets, one view

Every Sensor Placement Decision Made Now Saves $1,000 in Retrofit Later

iFactory designs complete IoT sensor networks for greenfield factories — sensor types, connectivity protocols, gateway architecture, data pipelines, and CMMS integration — delivered as construction-ready documentation.

Frequently Asked Questions

How many sensors does a typical factory need?
A mid-size factory with 50-100 critical assets typically needs 300-800 sensor points. Large motors need 6-8 sensors each, pumps need 5-7, gearboxes 5-8, and compressors 8-12. Non-critical assets (HVAC, conveyors) need 4-6 each with wireless sensors. The exact count depends on your asset criticality ranking — not every machine needs the same monitoring depth. We perform a criticality assessment during design to optimize sensor count: full monitoring on critical/high-risk assets, basic monitoring on non-critical, and none on run-to-failure assets.
How do you ensure reliable connectivity in high-vibration, high-EMI environments?
Three strategies: wired connections for critical high-frequency data (vibration sensors using shielded cables in dedicated conduit — away from VFD power cables), industrial-grade wireless with metal-optimized antenna placement (LoRaWAN gateways on elevated positions above metal structures), and mesh networks that self-heal around interference (Zigbee/Thread mesh where any single node failure routes through neighbors). In greenfield design, we map RF propagation through the building structure before construction, position access points and gateways for maximum coverage, and specify cable routing that isolates signal cables from power and EMI sources.
LoRaWAN or WiFi — which is better for factory IoT?
They solve different problems and most factories need both. LoRaWAN: ultra-low power (5-10 year battery life), long range (one gateway covers an entire plant), but low data rate (0.3-50 kbps) and higher latency (1-10 seconds). Best for: environmental monitoring, tank levels, utility meters, and non-critical assets that report every 15-60 minutes. WiFi 6: high bandwidth (up to 9.6 Gbps), low latency (1-10ms), but higher power consumption and shorter range (30-50m indoor). Best for: mobile devices, high-bandwidth sensors, edge devices, and any application requiring real-time data. The greenfield advantage: you can plan both networks simultaneously, positioning LoRaWAN gateways and WiFi APs for complete, interference-free coverage.
How do you handle sensor data at scale (1,000+ sensors)?
Purpose-built time-series databases (InfluxDB, TimescaleDB, QuestDB) handle the ingest rates that relational databases cannot. At 1,000 sensors reporting every second, you're ingesting ~1 million data points per second. The architecture uses MQTT brokers for fan-out to multiple consumers, edge processing to reduce raw data volume by 90-95% (sending features, not raw waveforms to cloud), and tiered retention policies (raw data 30-90 days local, downsampled data archived indefinitely). In greenfield, we size the storage, compute, and network for your projected sensor count plus 50% growth headroom — so you never hit a scaling wall.
Which time-series database should we use?
For most factory IoT deployments: InfluxDB is the most widely adopted with strong ecosystem support and native MQTT integration. TimescaleDB is excellent if you need SQL compatibility (runs on PostgreSQL). QuestDB offers the highest raw ingest performance for extreme-scale deployments. For smaller deployments (under 500 sensors), InfluxDB's open-source edition is sufficient. For plant-wide (500-2,000+), enterprise editions with clustering and high availability are recommended. We specify the TSDB selection based on your sensor count, query patterns, retention requirements, and existing IT infrastructure. Book a demo to see the full data pipeline configured for your factory.

Bad Data In = Bad Predictions Out — Start with the Sensor Network

AI analytics are only as good as the data they consume. Design the sensor network, connectivity, gateways, and data pipeline right — and every prediction your AI makes will be trustworthy from day one.


Share This Story, Choose Your Platform!