Industrial protocol connectivity
Use available OPC UA, MQTT, Modbus, REST or WebSocket interfaces to collect and exchange equipment and application data.
INDUSTRIAL IOT
Industrial IoT Platform for Machine Connectivity
Collect and normalize plant signals at the edge so MES, digital twin and operational analytics can use reliable machine context.
Turn equipment signals into operational information
The Industrial IoT layer is for automation engineers, maintenance teams, production teams and IT/OT owners who need consistent data from mixed plant equipment. It connects suitable PLC, CNC, robot, sensor and application interfaces while keeping plant-local reliability and deployment constraints in view.
CNC and controller data
Acquire supported controller states, alarms, counters and process signals, including FANUC FOCAS where the equipment and licence permit it.
Edge collection and buffering
Keep collection close to plant equipment and buffer events through temporary upstream interruptions when the deployment requires it.
Normalized operational signals
Map source-specific tags into usable equipment states, production events and measurements for downstream manufacturing applications.
How the workflow connects
Inventory the sources
Identify equipment, controllers, available protocols, network boundaries, signal ownership and sampling needs.
Collect at the edge
Plant-local connectors read approved signals and preserve source timestamps and equipment identity.
Normalize the context
Raw tags are mapped to meaningful states, alarms, counts and measurements that downstream systems can interpret.
Deliver to applications
Approved data feeds MES, maintenance, dashboards, digital twin or analytics according to security and latency requirements.
Machine signals can support MES production tracking, digital twin views and robotics intelligence. Review protocol and system categories on the integrations page.
What to prepare for an evaluation
- Equipment and controller inventory
- Available protocols, licences and tag lists
- Plant network and security boundaries
- Required states, events and sampling rates
- Destination systems and data-retention needs
Deployment can be reviewed against plant connectivity, data ownership and response-time needs. See the manufacturing platform architecture for edge, cloud and hybrid considerations.
Questions manufacturing teams ask
Can legacy and modern machines be connected?
Potentially, when a supported controller interface, gateway or signal source is available. A connectivity survey should confirm each asset rather than assume universal support.
Why use an edge layer?
Plant-local collection can reduce dependency on internet connectivity, keep protocol access close to equipment and support buffering or low-latency processing.
Does the platform replace PLC control?
No. The public scope is data connectivity and manufacturing intelligence, not replacement of machine safety or deterministic control logic.
What should an IoT pilot include?
Use a small representative set of machines, required signals, one downstream application and clear acceptance checks for data meaning and continuity.
Continue your evaluation
Plan a focused manufacturing software pilot
Bring one workflow, the systems it must connect and the decisions your team needs from it.
Start the assessment