SystemsText → ImageMid creditEN

IoT Sensor → Edge → Cloud Pipeline

Three-tier IoT data path with sensors at the edge, gateway aggregation, and cloud analytics.

When to use this prompt

For IoT / industrial-AI / smart-infrastructure papers and engineering deck figures.

The prompt

A three-tier IoT pipeline drawn left-to-right.

Tier 1 — Edge (left):
- Multiple field sensors (temperature, vibration, pressure) drawn as small device icons.
- An on-device inference module on a microcontroller (TinyML model), filtering raw signals into events.

Tier 2 — Edge Gateway (center):
- A gateway box aggregating events from N sensors over Bluetooth / Wi-Fi.
- Local buffering and protocol translation (MQTT, OPC UA).
- Optional secondary on-gateway model for anomaly screening.

Tier 3 — Cloud (right):
- A cloud-region cylinder hosting a stream-processing layer (Kafka / Pub-Sub) feeding two parallel sinks: a time-series database for dashboards and a model-serving service for higher-fidelity analytics.
- A web dashboard icon at the far right.

Two control / feedback arrows:
- Cloud -> Gateway: model updates pushed back to the edge.
- Gateway -> Edge: configuration changes pushed down to sensors.

Style: clean engineering schematic, navy / teal / amber palette, white background, thin connectors with labeled protocols. Suitable for industrial-AI conference papers.

Variations

With privacy/security annotations

Add lock icons on each tier and label the security boundaries: TLS between tiers, on-device encryption at rest, and access-control list at the cloud ingress.

Tips

  • Keep three tiers distinct in vertical bands or columns. Mixing them visually loses the architecture story.
  • Label protocols on arrows (MQTT, OPC UA, gRPC). Generic arrows are less informative.
  • Always include feedback arrows (model updates, config). One-way pipelines miss the operational story.

FAQ

Try this prompt now

Open it inside the generator with the prompt pre-filled.

Try this prompt

Related prompts