How IoT Connects to Existing Factory Machines

Connecting IoT to existing factory machines starts with a site survey, not with a dashboard mockup. Older machines, mixed controllers and locked panels need a clear map of what can be read safely and what needs an additional sensor.

Optiwise uses OptiEdge for machine data collection and edge processing where access is available. We support common industrial approaches such as Modbus and OPC-UA when the machine environment allows it.

Direct answer

IoT connects to existing machines through a checked connection map: controller, protocol, signal, access point, edge device, sampling need and installation constraint.

Factory example

One line has a PLC with usable Modbus data, another has an old relay panel, and a third needs an external power sensor. The connection map prevents one integration method from being promised for every machine before the site survey is complete.

Implementation path in Optiwise

1. Survey controller, protocol and accessible signals.
2. Choose PLC read, meter read or external sensor based on evidence.
3. Document constraints before installation starts.

Worksheet for your factory

Use this as the working checklist before you change software settings, write SOPs or ask the team to follow a new report.

Record	What to capture	Why it matters
Machine identity	Asset code, line, model and location	Prevents anonymous signals
Controller/protocol	PLC, meter, Modbus, OPC-UA or sensor route	Defines integration method
Accessible signal	Run, stop, alarm, count, power or vibration	Connects data to the use case
Access point	Panel, controller, meter or external sensor	Controls installation work
Sampling need	Seconds, minutes or event-based capture	Matches data rate to decision
Edge device	OptiEdge or approved device location	Handles local processing and buffering
Constraint	Permission, safety, warranty or panel access issue	Avoids unsafe assumptions

How Optiwise supports this workflow

• Survey each machine before promising a connection method.
• Use OptiEdge for local collection, processing and buffering.
• Connect accepted signals to production, OEE, downtime, load and energy reports.
• Keep unsupported or inaccessible signals visible as gaps so the project plan stays honest.

Explore the connected Optiwise workflows for production, inventory, purchasing, quality, IoT, and AI agents.

Checks before you use the number for decisions

• Confirm the owner of the record and the person who reviews exceptions.
• Write the unit of measure, time period and source system beside every number.
• Mark missing, stale or manually corrected data instead of hiding it inside the final score.
• Keep approval evidence for changes that affect stock, production, quality or customer commitments.

Reference source

For general manufacturing ERP and MRP context, compare this workflow with Deskera MRP resources, then adapt the records to your own factory process.

FAQs

Can IoT connect to every old machine?

Not automatically. Some machines expose usable signals, some need external sensors and some require vendor approval or panel access before integration.

What is the first signal to capture?

Start with the signal tied to the decision: running or stop state for utilization, count for cycle analysis, power for energy, or vibration for condition monitoring.