iFactory OEE Analytics vs Point85 OEE
iFactory OEE Analytics
ifactoryapp.comPoint85 OEE
point85.github.ioSide by side
| Figure | iFactory OEE Analytics | Point85 OEE |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| iOS | Yes | Yes |
| Android | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 3 | 0 |
| Spec score · Overall Equipment Effectiveness Software | 7.6 (#12) | 7.3 (#18) |
| Data collection | The product collects machine data from PLCs, IoT sensors, SCADA systems, and manual inputs. | Applications collect equipment data from multiple sources for OEE calculations or general-purpose data acquisition. |
| Deployment | The maker lists cloud SaaS, on-premise server and hardware, and Greenfield deployment models; cloud pricing is a custom quote based on users, modules, and production lines. | The web operator application is distributed as a WAR file for deployment to a web server that supports WAR deployment, such as Tomcat. |
| Integrations | The page lists PLC, SCADA, and sensor data feeds, plus ERP production synchronization with SAP, Oracle, and Dynamics. | Listed data sources include OPC DA, OPC UA, HTTP/S, RabbitMQ, JMS, MQTT, Kafka, WebSocket, email, database tables, file shares, Modbus, cron jobs and GE Proficy Historian. |
| Purpose | OEE Analytics tracks Availability, Performance, and Quality in real time across production lines and identifies production losses. | Point85 OEE quantifies manufacturing-equipment utilization using availability, performance and quality rates. |
Plans
iFactory OEE Analytics
- Cloud-Based SaaSPriced on request
- Greenfield PlantPriced on request
- On-Premise Server & HardwarePriced on request
In their own words
iFactory OEE Analytics
iFactory OEE Analytics has no write-up on Specifiction yet; its figures are above.
Point85 OEE
Point85 OEE is a free, open-source suite for collecting manufacturing equipment data, calculating overall equipment effectiveness, and monitoring availability, performance, and quality events. Its OEE calculation combines availability, performance rate, and quality rate in a nine-category time-loss model. The Designer configures equipment, data sources, event-resolution scripts, schedules, availability reasons, materials, and units of measure. The Monitor shows equipment metrics, collector notifications and status, event timelines, trends, time-loss charts, and Pareto charts. Listed data sources include OPC DA/UA, HTTP/S, RabbitMQ, JMS, MQTT, Kafka, WebSocket, email, database interface tables, file shares, Modbus, cron jobs, and GE Proficy Historian. The suite includes Designer, Collector, Monitor, desktop and web operator applications, and operator apps for iOS, Android, macOS, Windows, Linux, and Chrome/Edge. Collector runs as a Windows service or Unix daemon and stores equipment events in a relational database for OEE, MTBF, and MTTR calculations. Supported databases include Microsoft SQL Server, Oracle, MySQL, PostgreSQL, and HSQLDB. The web operator application is distributed as a WAR file for a compatible web server, such as Tomcat. The OEE-Designer repository identifies its license as MIT.