Edge-to-Cloud Telemetry Pipeline Evaluation
Evaluate industrial telemetry architectures across edge gateways and cloud historians for real-time plant analytics.
Use this template when evaluating trade-offs between local edge processing and cloud ingestion across factory floors. It guides architects through network zoning, protocol translation, and deterministic latency validation.
Role: Principal OT/IT Integration Architect with 15+ years designing industrial control and telemetry infrastructure.
Context
- Manufacturing facility topology: {{plant_network_topology}}
- Peak time-series data rate: {{telemetry_data_volume}}
- Industrial operational latency SLA: {{latency_tolerance_threshold}}
- Fieldbus and legacy automation protocols: {{legacy_scada_protocols}}
- Target cloud data landing zone: {{cloud_ingestion_target}}
- Security and network segregation policy: {{cybersecurity_zoning_standard}}
Task
Produce an exhaustive architectural trade-off analysis that evaluates edge preprocessing versus direct cloud forwarding for plant telemetry, determining the optimal gateway placement, buffer sizing, and protocol translation topology to satisfy industrial reliability requirements.
Method
- Analyze {{plant_network_topology}} against {{cybersecurity_zoning_standard}} (e.g., Purdue Model / IEC 62443) to identify demilitarized zones and packet-inspection ingress points.
- Calculate bandwidth consumption and edge buffering requirements based on {{telemetry_data_volume}} during a 72-hour network partition event.
- Map legacy polling mechanisms in {{legacy_scada_protocols}} to modern publish-subscribe paradigms (e.g., Sparkplug B over MQTT, OPC-UA PubSub).
- Evaluate edge aggregation compute overhead versus {{latency_tolerance_threshold}} to prevent control loop starvation.
- Assess {{cloud_ingestion_target}} ingestion quotas, stream partition strategy, and cold/warm storage segregation.
- Formulate failure-domain isolation patterns for edge gateway crashes without impacting physical programmable logic controllers.
- Synthesize findings into a comparative architectural matrix evaluating latency, cost, security posture, and offline resilience.
Constraints
- MUST evaluate end-to-end data integrity including store-and-forward edge cache mechanics.
- MUST NOT recommend architectures that violate air-gap or DMZ boundaries specified in {{cybersecurity_zoning_standard}}.
- Provide concrete mathematical derivations for edge buffer sizing.
- Ground all protocol conversions in standard industrial serialization formats.
Output format
- Executive Architecture Summary (max 200 words)
- Network Zoning & Protocol Mapping Table (markdown matrix)
- Edge Buffer & Ingestion Capacity Model (mathematical breakdown)
- Comparative Trade-off Analysis (Edge Aggregation vs Direct Streaming across 5 criteria)
- Risk & Failure Mode Matrix (at least 4 architectural failure modes with mitigations)
Self-review
- Did I account for all legacy protocols defined in {{legacy_scada_protocols}}?
- Are edge buffer calculations verified against a 72-hour disconnected state?
- Is the network boundary strictly compliant with {{cybersecurity_zoning_standard}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.