What is OPC-UA and why is it the standard for industrial connectivity?
OPC-UA (OPC Unified Architecture IEC 62541) is the primary vendor-neutral, platform-independent, secure protocol for industrial machine communication. Before OPC-UA, industrial connectivity required vendor-specific proprietary protocols or OPC Classic (Windows COM/DCOM only, poor security). OPC-UA provides built-in authentication, authorisation, and TLS encryption, runs on Linux gateways and cloud services (not just Windows), and includes a semantic information model where data is described with context and structure rather than raw register values. MQTT Sparkplug B extends OPC-UA data to cloud platforms like AWS IoT Core Ignition SCADA with the MQTT module publishes OPC-UA tag values as Sparkplug B payloads, making factory floor data available to cloud analytics pipelines in real time.
What is OEE and what is a good target?
OEE (Overall Equipment Effectiveness) = Availability × Performance × Quality. Availability: actual running time / planned production time. Performance: actual output rate / rated output rate. Quality: good parts / total parts produced. World-class OEE is typically 85%+. The global manufacturing average is approximately 65%. Low Availability indicates unplanned downtime or long changeovers. Low Performance indicates slow running or minor stoppages. Low Quality indicates process parameter issues causing defects. Real-time OEE monitoring with automatic downtime categorisation (operators select the loss reason on an HMI) makes losses visible and drives focused improvement. Moving from 65% to 75% OEE on a production line can increase output by 15% without adding equipment or headcount.
What is the IT/OT convergence challenge?
IT (Information Technology) manages computers, networks, and data. OT (Operational Technology) manages PLCs, SCADA, and physical control systems. They use different protocols (TCP/IP vs Modbus/Profibus), different update cycles (IT patches frequently; OT updates rarely downtime is costly), and different security models (IT assumes patchable systems; OT may run Windows XP on a machine tool that cannot be taken offline). Connecting OT systems to cloud platforms creates real business value but also creates security risk. ClickMasters addresses this with: network segmentation (OT separated from IT by firewall), unidirectional data flow (data diodes prevent attacks from reaching control systems), and OT-specific passive security monitoring (Claroty, Nozomi, or Dragos anomaly detection that does not interfere with industrial protocols that cannot tolerate active scanning).
Can ClickMasters connect to legacy PLCs that are 10-20 years old?
Yes legacy equipment is a primary IIoT use case. Most legacy PLCs support Modbus RTU (serial RS-485) or Modbus TCP (Ethernet). If the PLC has Ethernet or can be reached via RS-485, ClickMasters can read its data. PLCs with proprietary protocols only (Siemens S7, Allen-Bradley DF1) require an OPC-UA gateway an industrial PC running Kepware or Ignition OPC-UA server with vendor-specific drivers that bridge the proprietary protocol to OPC-UA. ClickMasters sizes the gateway to the protocol and polling rate requirements. Key constraints: very old PLCs may have limited concurrent connection capacity (excessive polling frequency can overwhelm the controller ClickMasters configures appropriate polling intervals based on the PLC's specifications) and some legacy Modbus implementations have vendor-specific non-standard behaviour requiring specific configuration.
