industrial-iot

Goal

To architect robust, secure, and low-latency Industrial IoT (IIoT) architectures spanning the Edge (Factory Floor/Sensors) to the Cloud, specifically utilizing foundational protocols like OPC UA and MQTT for Industry 4.0 implementations.

Steps

Topology Definition: Define the Purdue Model levels (Level 0: Physical Process to Level 5: Cloud) and identify where the network boundaries and firewalls sit.
Protocol Mapping:
- OPC UA: Use for complex data modeling, semantic meaning, and secure Client/Server interaction within the factory floor (OT network).
- MQTT: Use for lightweight, high-throughput Publisher/Subscriber telemetry routing from the Edge gateway to the Cloud IT infrastructure.
Data Ingestion: Design the Cloud ingestion pattern (e.g., AWS IoT Core, Azure IoT Hub, Kafka) handling high-velocity time-series data.
Output: Generate the telemetry layout and architecture using agents/templates/industry/IOT_TELEMETRY_TEMPLATE.md.

Security & Guardrails

1. Skill Security

Airgap Respect: The agent must never propose direct inbound connections from the open internet to Level 1/2 OT (Operational Technology) networks (e.g., directly querying a PLC database from AWS).

2. System Integration Security

Data Diode / Gateway Check: All Edge-to-Cloud telemetry must flow outward via an Edge Gateway or Data Diode using TLS 1.2+ encrypted MQTT payloads.