Industrial OPC UA to Cloud Telemetry Ingestion Service Specification

Role: Principal Industrial IoT Systems Architect with 15+ years of experience in shop-floor telemetry ingestion, edge computing, and distributed data systems.

Context

• Protocol & Schema: Translating from {{plant_protocol_version}} nodes to cloud-native JSON/Protobuf events.
• Target Infrastructure: Routing telemetry directly into {{target_broker_topology}}.
• Ingestion Scale: Operating under sustained volumes of {{telemetry_throughput_rate}}.
• Edge Durability: Requiring edge buffer survivability of {{offline_buffer_duration_hours}}.
• Regulatory & Security: Strict adherence to {{security_compliance_standard}} across operational and cloud boundaries.

Task

Draft a production-ready technical architecture specification for an edge ingestion gateway microservice that subscribes to industrial telemetry, standardizes variable data types, manages local disk spooling during WAN disconnections, and dispatches authenticated event payloads to cloud message brokers.

Method

1. Define the OPC UA node subscription lifecycle, including monitored item creation, sampling intervals, and deadband filter configurations.
2. Model the internal translation pipeline that maps raw industrial tags and quality bits into normalized semantic telemetry events.
3. Architect the local disk-backed WAL (write-ahead log) queue to guarantee zero data loss during network disruptions.
4. Specify the backpressure management protocol between edge subscribers and the disk-spooling engine.
5. Design the broker publisher client, including batching strategies, compression algorithms, and idempotent message envelope headers.
6. Detail the mTLS and certificate rotation handshake across Purdue Model Level 3 and cloud boundaries.
7. Formulate observability instrumentation covering end-to-end ingestion latency, buffer watermarks, and dropped packet metrics.

Constraints

• MUST guarantee at-least-once delivery semantics for all critical quality tags.
• MUST NOT process unauthenticated edge node subscriptions or drop data during graceful container restarts.
• All timestamp normalizations must enforce UTC ISO-8601 with microsecond precision.
• Payload overhead must remain strictly beneath 1.5 KB per consolidated telemetry frame.
• Memory consumption at the edge container boundary must be bounded by a deterministic ceiling.

Output format

1. Service Overview: Architectural context, SLA boundaries, and protocol flow diagram description.
2. Data Contract & Envelope: JSON/Protobuf schema definitions including metadata, status codes, and payload arrays.
3. Edge Buffer & Sync Engine: Disk spillover mechanics, recovery draining algorithm, and backpressure policies.
4. Security & Network Specification: Purdue model placement, certificate storage, and firewall ingress/egress rules.
5. Failure Modes & Mitigations Table: Markdown table matching 5 failure scenarios to automated mitigation strategies.

Self-review

• Verify that offline edge buffering calculations directly satisfy the {{offline_buffer_duration_hours}} requirement.
• Confirm that the message envelope explicitly includes quality bits from {{plant_protocol_version}}.
• Check that network egress definitions strictly comply with {{security_compliance_standard}}.