Industrial Telemetry Pipeline Modernization Plan

Role: Principal Industrial IoT Systems Architect with twenty years of experience in distributed SCADA and cloud telemetry systems.

Context

• Facility identifier: {{plant_site_name}}
• Legacy industrial protocols in scope: {{legacy_plc_protocols}}
• Target broker architecture: {{target_cloud_broker}}
• Daily data throughput and peak frequency: {{telemetry_data_volume}}
• End-to-end latency constraint: {{latency_sla_target}}
• Edge compute constraints: {{edge_hardware_profile}}

Task

Generate an end-to-end engineering execution plan to modernize the shop-floor data ingestion pipeline for {{plant_site_name}}, transitioning from {{legacy_plc_protocols}} to an enterprise-grade {{target_cloud_broker}} topology while ensuring continuous high availability and meeting {{latency_sla_target}}.

Method

1. Map physical register schemas and tags across {{legacy_plc_protocols}} to a unified normalized time-series payload structure.
2. Design an edge-tier adapter architecture optimized for {{edge_hardware_profile}} that handles bidirectional protocol adaptation and connection pooling.
3. Formulate a local disk-buffered queue strategy to guarantee zero telemetry loss during factory WAN disconnects spanning up to 48 hours.
4. Define the ingress serialization pipeline, schema registry enforcement, and payload compression algorithms to handle {{telemetry_data_volume}}.
5. Specify downstream dead-lettering, payload deserialization benchmarks, and routing rules to target storage tiers in {{target_cloud_broker}}.
6. Architect security perimeters covering mTLS handshake verification, field-device isolation, and rotating secret lifecycle management.
7. Detail a canary validation, rollback matrix, and parallel-run verification benchmark against active production lines.

Constraints

• All transport layers MUST enforce mTLS 1.3 encryption and device-level certificate pinning.
• The plan MUST NOT propose cloud roundtrips for local safety-critical feedback loops.
• Edge buffering mechanics must operate within the memory limits of {{edge_hardware_profile}}.
• Every architectural phase must include explicit rollback triggers and fallback criteria.

Output format

Provide a technical implementation plan structured into exactly four sections:

1. Architecture Specification (maximum 400 words detailing edge and cloud topologies)
2. Data Ingestion & Buffering Blueprint (detailed numbered logic for network partitions and backpressure)
3. Security & Protocol Adapter Matrix (table mapping protocols, edge adapters, and encryption standards)
4. Phased Rollout Schedule (step-by-step milestones with acceptance criteria and rollback thresholds)

Self-review

• Confirm that all 6 variables are referenced and contextualized within the plan.
• Verify that network partition and WAN outage recovery mechanics are explicitly detailed.
• Ensure no generic IoT advice is provided; all steps must strictly address industrial PLC translation.