IIoT Solutions – from Field Device to Cloud
IIoT by ICS Schneider connects sensors, actuators, and controllers to edge gateways, MQTT/HTTPS, and your IT/OT systems. We integrate vendor-agnostically (e.g., WIKA, Siemens SITRANS, etc.) over RS-485/Modbus RTU, HART, IO-Link, OPC UA, or Ethernet — wired or via LoRaWAN/LTE/5G/Wi-Fi. The edge aggregates, scales, and timestamps measurements, handles local alarms, and publishes securely via TLS/VPN to SCADA/cloud. The result: real-time dashboards, threshold notifications, reporting, and traceability — for greenfield and brownfield sites.
We deliver architecture, device selection, register mapping/data model, topic design, commissioning, and documentation — compliant with ISO 9001:2015. This transforms field devices into transparent, maintenance-friendly IIoT assets that secure quality, reduce downtime, and cut costs.
FAQ on IIoT Solutions
The key questions on architecture, protocols, connectivity, security, operations, scaling, and practical rollouts.
What does a typical IIoT architecture include?
Field devices (sensor/actuator) → Edge gateway (drivers, preprocessing, alarms) → MQTT/HTTPS → SCADA/cloud/BI. Optional OPC UA/REST for brownfield integration.
Which protocols matter in practice?
| Layer | Protocol | Purpose |
|---|---|---|
| Field | Modbus RTU (RS-485) | Robust polling, long distances |
| Field | IO-Link | Parameterization, events, diagnostics |
| Field | HART (4–20 mA) | Analog + digital variables |
| Edge↔IT | MQTT | Lightweight telemetry, pub/sub |
| Edge↔IT | HTTPS/REST | Configuration, batch, integrations |
| OT | OPC UA | Models, browsing, SCADA coupling |
How do I choose connectivity (Ethernet, Wi-Fi, LTE/5G, LoRaWAN)?
| Technology | Strengths | Considerations |
|---|---|---|
| Ethernet/PoE | Stable, low latency, PoE power | Cabling/control cabinet |
| Wi-Fi | Fast deployment | Roaming/EMC/shielding |
| LTE/5G | Remote sites, redundancy | Tariffs, antenna planning |
| LoRaWAN | Long range, battery-friendly | Low data rate, duty cycle |
What does a clean MQTT topic scheme look like?
Hierarchical and ID-stable, e.g.:
site/{plant}/area/{line}/device/{id}/sensor/{name}/value
site/{plant}/area/{line}/device/{id}/status
site/{plant}/area/{line}/device/{id}/alarm
Publish metadata (unit, scaling, firmware, calibration date) as retained properties.
Which QoS/retain settings do you recommend?
QoS 1 for measurements/alarms, QoS 0 for high-frequency trends; use retain for metadata/last status, not for events.
Can I retrofit brownfield plants?
Yes. Edge gateways ingest Modbus/HART, normalize into a unified model, and publish via MQTT/OPC UA. Existing SCADA remains untouched.
What happens to alarms if the cloud link is down?
Run alarm logic locally at the edge (thresholds, hysteresis, rate-of-change). Buffer with timestamps; after reconnection use store-and-forward.
What sampling/publish rates make sense?
Process-dependent. Rules of thumb: slow 10–60 s, moderate 2–10 s, fast 0.5–2 s. Add publish-on-change (delta/timeout) to reduce traffic.
How do I secure communications and access?
TLS/MQTTS, device certificates, VPN/zero-trust, RBAC/roles, API keys, audit logs, signed firmware, and patch & certificate management.
Which data belong in the historian/BI?
Raw values/downsampling, min/max/avg, alarms/acknowledgements, status/diagnostics, maintenance/calibration, and version states (firmware/config).
How is time synchronization handled?
Sync edge and broker via NTP/PTP; payloads include UTC timestamps and quality flags (e.g., ts, qos, quality=good/bad).
Do you support dashboards and reports out of the box?
Yes. Typical path: MQTT → time-series DB → dashboard (e.g., Grafana/SCADA) with templates, alarm panels, reports (PDF/CSV), and roles/permissions.
What does a pilot project look like?
Workshop → edge + 3–5 measuring points → data model/topics → dashboards/alarms → security baseline → acceptance & ROI review → roll-out plan.
Which KPIs are useful for IIoT?
Availability (MTBF/MTTR), alarm precision, energy per lot, process stability (std. dev.), edge→IT latency, data quality (plausibility/drift).
How do you approach data modeling?
Unified fields (e.g., value, unit, status, alarm), semantic IDs, and versioning of strapping/scaling.
Any rules of thumb for RS-485 lines?
Daisy chain, 120-Ω termination at both ends, biasing, short stubs, clean addressing, documented baud rate/parity.
What are common edge functions?
Drivers, filtering/smoothing, unit/scaling conversion, local alarms, buffering, OTA updates, VPN client, certificate handling.
How is device/fleet management handled?
Inventory with stable IDs, groups/sites, templates (topics/alarms), remote parameterization, staged firmware rollouts, and an audit trail.
What cost ranges are realistic?
| Scope | Deliverables | Effort (estimate) |
|---|---|---|
| ≤ 10 points | Edge, wiring, basic dashboard | 1–3 person-days |
| 10–50 | Segments, alarms, roles | 3–10 person-days |
| 50+ | Fleet mgmt, templates, reporting | PoC → phased roll-out |
Which compliance/security topics should be covered?
ISO-aligned processes (e.g., ISO 9001), GDPR-compliant storage, roles/permissions, gateway hardening, logging, and clear responsibilities/SLAs.
Does it work in hazardous areas?
Yes — with suitable Ex approvals (ATEX/IECEx), intrinsically safe barriers/isolators, and proper enclosures; place gateways in safe zones where possible.
How do you integrate multi-vendor environments?
Driver library (Modbus/IO-Link/HART/OPC UA), mapping to a unified model, validation/testing, and full register/parameter documentation.