Industrial Edge Telemetry Architecture Specification

Role: Principal IIoT Systems Architect with 15+ years designing mission-critical industrial edge-to-cloud architectures.

Context

• Manufacturing site: {{plant_facility_name}}
• Legacy industrial communication protocols: {{legacy_protocols}}
• Target edge compute footprint: {{edge_hardware_profile}}
• Target ingestion volume and rate: {{ingestion_throughput_target}}
• Upstream enterprise cloud target: {{cloud_target_platform}}
• Industrial network latency constraint: {{network_latency_sla}}

Task

Produce an exhaustive edge-to-cloud telemetry architecture specification for {{plant_facility_name}} that ingests, translates, filters, and securely delivers machine telemetry from {{legacy_protocols}} to {{cloud_target_platform}} within {{network_latency_sla}} limits.

Method

1. Map physical asset connectivity across the OT network boundary, detailing protocol normalization nodes for {{legacy_protocols}}.
2. Formulate the edge gateway compute allocation on {{edge_hardware_profile}}, detailing memory caching, deadband filtering, and local buffering mechanisms.
3. Design the store-and-forward persistence scheme ensuring zero data loss during wide-area network partition events.
4. Define edge-to-cloud network transport security, mutual TLS authentication, and x509 certificate rotation pipelines.
5. Specify cloud-side ingestion stream processing to handle peak traffic defined by {{ingestion_throughput_target}} without message throttling.
6. Detail schemas for unified industrial time-series payloads with ISO-8601 millisecond timestamps, asset UUIDs, and quality flag metadata.
7. Architect the disaster recovery failover path and degraded-mode edge operations.

Constraints

• MUST guarantee local edge persistence capable of buffering 72 hours of uninterrupted telemetry during upstream outages.
• MUST NOT route unencrypted operational technology (OT) payloads across the enterprise Demilitarized Zone (DMZ).
• System topology MUST align with ISA-95 and Purdue Enterprise Reference Architecture level segmentations.
• All edge payload formats MUST adhere strictly to Apache Avro or Protobuf specifications.

Output format

Generate a structured engineering specification with the following exact headers:

1. Architectural Overview & Purdue Model Mapping
2. Edge Compute & Protocol Normalization Engine (specifying allocations on {{edge_hardware_profile}})
3. Ingestion Pipeline & Store-and-Forward Topology
4. Data Contracts & Serialization Schemas
5. Network Security & DMZ Traversals
6. Operational Resilience & Recovery SLAs Limit total response to 700-1100 words.

Self-review

• Verify every legacy protocol in {{legacy_protocols}} has an explicit mediation pattern.
• Confirm that store-and-forward edge buffering logic accounts for the memory constraints of {{edge_hardware_profile}}.
• Ensure all Purdue level boundaries and zero-trust controls are explicitly documented.