Manufacturing Industrial IoT on AWS (2026): OPC-UA, SiteWise, and OEE Reference Architecture
Quick summary: For discrete manufacturing (~850 OPC-UA tags, 12 lines), Greengrass + IoT SiteWise anomaly detection moved OEE from 61% to 74% in 90 days, with unplanned downtime down 18% and no MES replacement.
Key Takeaways
- For discrete manufacturing (~850 OPC-UA tags, 12 lines), Greengrass + IoT SiteWise anomaly detection moved OEE from 61% to 74% in 90 days, with unplanned downtime down 18% and no MES replacement
- AWS IoT SiteWise shipped native multivariate anomaly detection in July 2025 (AWS announcement), with up to 300 sensors per model, available in US East (N
- September 2025 updates added automated model retraining (30-day to 1-year schedules) and manual vs automatic model promotion (What's New)
- IoT Greengrass v2 remains the standard edge host for SiteWise Gateway OPC-UA collectors (Edge to Twin blog pattern)
- It is separate from logistics / supply chain, generic IoT patterns, consumer connected devices, and a TwinMaker product tour, though TwinMaker appears in tier 3
Table of Contents
AWS IoT SiteWise shipped native multivariate anomaly detection in July 2025 (AWS announcement), with up to 300 sensors per model, available in US East (N. Virginia), Europe (Ireland), and Asia Pacific (Sydney). September 2025 updates added automated model retraining (30-day to 1-year schedules) and manual vs automatic model promotion (What’s New). IoT Greengrass v2 remains the standard edge host for SiteWise Gateway OPC-UA collectors (Edge to Twin blog pattern).
This post is the manufacturing industrial IoT reference architecture: plant floor to OEE dashboard. It is separate from logistics / supply chain, generic IoT patterns, consumer connected devices, and a TwinMaker product tour, though TwinMaker appears in tier 3.
Artifacts: architecture decision matrix, OEE KPI baseline CSV.
Four tiers from plant floor to boardroom
| Tier | Question | Default AWS path |
|---|---|---|
| Edge ingest | Can PLCs talk safely to cloud? | Greengrass v2 + SiteWise Gateway (OPC-UA) |
| Asset intelligence | What is OEE by line/shift? | IoT SiteWise models + metrics |
| Predictive | Which assets fail next? | SiteWise anomaly detection |
| Visualize | Who consumes insights? | QuickSight (defer TwinMaker until tier 2 stable) |
Opinionated take: Fix tag taxonomy before TwinMaker. Teams that buy 3D twins before OEE baselines rebuild dashboards twice.
Reference architecture
PLC / OPC-UA ──► Greengrass + SiteWise Gateway ──► IoT SiteWise (cloud)
│ │
│ ├── Asset models / OEE metrics
│ ├── Anomaly detection (multivariate)
│ └── Export → S3
│
MES (batch) ──► S3 landing ──► Glue (optional) ──► QuickSight dashboards
│
└──► EventBridge ──► Lambda (maintenance tickets)Edge layer: Greengrass and OPC-UA
Deploy SiteWise Gateway as a Greengrass v2 component per line or cell:
- Buffer telemetry during WAN blips (store-and-forward)
- Keep OPC-UA traffic off corporate IT VLAN: DMZ pattern per OT/IT convergence
- Certificate lifecycle is the #1 ops task: alarm 30 days before expiry
Cloud layer: SiteWise
- Model assets to match physical hierarchy (plant → line → machine → sensor)
- Map OPC-UA nodes in oee-kpi-baseline.csv
- Enable disassociated data ingestion if streams appear missing after gateway sync (SiteWise settings)
When anomaly detection earns ROI
Per SiteWise pricing:
- Training: minimum 1 hour billed, prorated per minute
- Up to 300 sensors per model
- High-frequency inference (5 to 60 min schedules) vs low-frequency count-based options
Target rotating equipment (motors, pumps, compressors) with continuous signals, not discrete reject counts alone.
Measure OEE before building models
| Component | Formula (simplified) | SiteWise source |
|---|---|---|
| Availability | Run time / planned production time | Running BOOL + downtime events |
| Performance | Ideal cycle time / actual cycle time | Cycle time + speed sensors |
| Quality | Good units / total units | Reject count + vision systems |
Baseline every tag in oee-kpi-baseline.csv before enabling anomaly models.
When NOT to escalate
| Situation | Stay lighter |
|---|---|
| < 50 tags, one line | IoT Core → Timestream |
| No OT/network segmentation | Fix VLAN before cloud |
| Logistics / fleet KPIs | Logistics architecture |
| MES replacement project | SiteWise complements; does not replace MES execution |
What to do this week
- Export OPC-UA tag list and fill oee-kpi-baseline.csv.
- Run decision matrix: SiteWise vs custom lake.
- Pilot one line with Greengrass + SiteWise Gateway before plant-wide rollout.
- Set cert expiry alarms on every gateway core.
- Defer TwinMaker until QuickSight OEE dashboard has weekly active users.
What this post doesn’t cover
- Warehouse / WMS / TMS logistics: logistics reference architecture
- Full MES replacement: vendor domain
- Robotics / AMR fleet: separate integration patterns
- HIPAA / FDA validation: healthcare digital health reference architecture (2026) and healthcare hub for regulated subsectors
We have not benchmarked SiteWise anomaly training cost for every asset class. Run a one-line pilot and read billed training hours before plant-wide model rollout.
Related: Manufacturing industry hub · Data analytics services · Managed services
Frequently asked questions
When should we use IoT SiteWise vs a custom S3 data lake for manufacturing telemetry?
When should we NOT deploy IoT TwinMaker on day one?
What breaks when OPC-UA certificates expire at scale?
How does this differ from logistics supply chain architecture?
When should we NOT enable SiteWise anomaly detection?
What could go wrong merging OT and IT networks too early?
AWS Cloud Architect & AI Expert
AWS-certified cloud architect and AI expert with deep expertise in cloud migrations, cost optimization, and generative AI on AWS.
