{"data":{"slug":"iiot-platform-selection","title":"IIoT Platform Selection: Capabilities and Evaluation Criteria","summary":"The industrial IoT platform market is crowded and loud: every vendor claims edge-to-cloud, digital twins, and AI. Yet the platform decision is one of the most…","category":{"slug":"modern-connectivity","name":"Modern Connectivity"},"url":"https://wiki.aspotomasyon.com/article/iiot-platform-selection","markdown_url":"https://wiki.aspotomasyon.com/article/iiot-platform-selection.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/iiot-platform-selection","published":"2026-08-11T13:05:24+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":5,"word_count":908,"image":"https://wiki.aspotomasyon.com/assets/social/iiot-platform-selection-f8961916d31c.png","html":"<p>The industrial IoT platform market is crowded and loud: every vendor claims edge-to-cloud, digital twins, and AI. Yet the platform decision is one of the most consequential and expensive choices in a digitalization program — platforms are adopted for a decade, and migrating between them is a project in itself. This article cuts through the marketing with a functional view: what an IIoT platform actually does, what the architecture options are, and how to evaluate candidates against the plant's real use cases.</p><figure class=\"article-figure\"><img src=\"https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-context.svg\" width=\"1100\" height=\"460\" loading=\"lazy\" decoding=\"async\" alt=\"A generic industrial messaging path. A network or broker acknowledgment is not necessarily confirmation that a downstream business action succeeded.\"><figcaption>A generic industrial messaging path. A network or broker acknowledgment is not necessarily confirmation that a downstream business action succeeded. <a href=\"https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-context.svg\" target=\"_blank\" rel=\"noopener\">View full size</a></figcaption></figure>\n\n<h2 id=\"what-an-iiot-platform-does\">What an IIoT Platform Does</h2>\n\n<p>An IIoT platform is the software backbone between the plant and the applications that use its data. The functional layers:</p>\n\n<ul>\n  <li><strong>Connectivity</strong> — device/gateway onboarding, protocol support (MQTT/Sparkplug, OPC UA, Modbus, vendor protocols), and connection management at scale.</li>\n  <li><strong>Device and asset management</strong> — device registry, configuration, firmware updates, and the asset hierarchy (site → line → machine → point) that organizes everything else.</li>\n  <li><strong>Data management</strong> — ingestion, time-series storage, quality and context handling, and data access (APIs, SQL, export).</li>\n  <li><strong>Application services</strong> — dashboards, rules/alerts, analytics, and integration interfaces (REST, webhooks, connectors).</li>\n  <li><strong>Administration and security</strong> — identity, roles, multi-tenancy, audit, and the security controls that make the platform trustworthy.</li>\n</ul>\n\n<p>The depth of each layer varies enormously between products — from lightweight dashboards-in-a-box to full industrial data platforms with edge runtimes.</p>\n\n<h2 id=\"architecture-options\">Architecture Options</h2>\n\n<table>\n  <thead>\n    <tr><th>Architecture</th><th>Strengths</th><th>Weaknesses</th></tr>\n  </thead>\n  <tbody>\n    <tr><td>SaaS (multi-tenant cloud)</td><td>Fast start, zero infrastructure, provider-managed security and updates.</td><td>Data leaves the plant (legal/sovereignty checks), recurring cost, provider lock-in.</td></tr>\n    <tr><td>Private cloud / self-hosted</td><td>Data control, custom integration depth.</td><td>You operate it: updates, security, scaling — a small IT department in itself.</td></tr>\n    <tr><td>Edge-first platform</td><td>Data processed at the plant, cloud optional; low latency, resilience to connectivity loss.</td><td>More engineering; the edge is part of the OT surface (see the cloud/edge security article).</td></tr>\n    <tr><td>Hybrid (edge + cloud)</td><td>The industrial standard: edge for collection/control-adjacent processing, cloud for scale and analytics.</td><td>Two environments to operate; integration quality decides the outcome.</td></tr>\n  </tbody>\n</table>\n\n<p>The evaluation should be anchored in the <em>target architecture</em> — where the data must live, who operates what, and how the platform fits the plant's OT security model — before comparing feature lists.</p>\n\n<h2 id=\"evaluation-criteria-that-matter\">Evaluation Criteria That Matter</h2>\n\n<ol>\n  <li><strong>Protocol and integration depth</strong> — native Sparkplug B? OPC UA client/server? Fieldbus gateways? The integration cost with the installed base is the platform's largest hidden price.</li>\n  <li><strong>Data model quality</strong> — can the platform represent the plant's asset hierarchy and data context (units, quality, timestamps), or is it a flat tag bucket? Context is what makes the data usable later.</li>\n  <li><strong>Openness</strong> — export capability (all data and configuration, documented), APIs, and the absence of proprietary locks: assess the exit cost as seriously as the entry cost.</li>\n  <li><strong>Security posture</strong> — the platform's security model (identity, encryption, audit), its certifications, and its fit with the plant's IEC 62443 zoning.</li>\n  <li><strong>Operational model</strong> — who runs it (vendor, plant IT, automation), the update cadence, and the support terms; a platform without an operational owner is a ghost.</li>\n  <li><strong>Cost model</strong> — per-device, per-message, per-user, or bundled; model the bill on the plant's real data volume (see the cloud integration article for the cost drivers).</li>\n  <li><strong>Ecosystem</strong> — the application ecosystem (analytics, visualization, industry solutions) and the community; the platform's ecosystem is its long-term value.</li>\n</ol>\n\n<h2 id=\"the-evaluation-process\">The Evaluation Process</h2>\n\n<ol>\n  <li><strong>Define the use cases first</strong> — the three to five concrete applications (remote monitoring of site X, OEE analytics, alarm notification) with their data needs; the use cases are the platform's acceptance test.</li>\n  <li><strong>Shortlist on architecture</strong> — filter by the target architecture and the integration profile; five candidates is enough.</li>\n  <li><strong>Run a pilot with real data</strong> — connect one real asset (or a simulator) with the actual protocol, build the use case dashboard, and test the operational details: onboarding, alerts, data export.</li>\n  <li><strong>Score against the criteria with evidence</strong> — a weighted scorecard filled from the pilots, not from sales calls; include the exit-cost question.</li>\n  <li><strong>Reference calls</strong> — talk to plants of similar size and industry running the platform for 2+ years; ask about the operational reality, not the features.</li>\n</ol>\n\n<h2 id=\"common-mistakes\">Common Mistakes</h2>\n\n<ul>\n  <li>Choosing by dashboard beauty — dashboards are the cheapest layer to build; data access and integration are the expensive ones.</li>\n  <li>Platform-first, use-case-later — the classic: buy the platform, then search for problems; the result is an expensive dashboard museum.</li>\n  <li>Ignoring the operational cost — the platform's monthly cost is the visible part; the integration, training, and operations effort is usually larger.</li>\n  <li>Lock-in by neglect — no data export tested, no configuration export, and the platform becomes the plant's memory with no way out.</li>\n</ul>\n\n<h2 id=\"summary\">Summary</h2>\n\n<p>IIoT platform selection is architecture first, features second: decide where the data lives and who operates it, then evaluate integration depth, data model quality, openness, security, operations, and cost against concrete use cases with a real pilot. The platform is a decade-long partner — choose it like a hiring decision, with evidence, references, and an exit plan.</p><section class=\"engineering-check\"><h2 id=\"apply-this-to-your-project\">Apply this to your project</h2><ul><li>Specify payload structure, units, identity, time semantics, access permissions, and protocol versions.</li><li>Test backlog growth, connection loss, duplicate delivery, and restart behavior at the consuming application.</li><li>Document how operators see failures and how the system distinguishes replayed data from current process state.</li></ul><p><a href=\"https://wiki.aspotomasyon.com/guides\">Follow an ASP project guide</a> to connect the fundamentals with implementation and acceptance.</p></section><figure class=\"article-figure\"><img src=\"https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-review.svg\" width=\"1100\" height=\"460\" loading=\"lazy\" decoding=\"async\" alt=\"Engineering review sequence: Contract → Connect → Interrupt → Reconcile. Keep the recorded evidence with the accepted configuration.\"><figcaption>Engineering review sequence: Contract → Connect → Interrupt → Reconcile. Keep the recorded evidence with the accepted configuration. <a href=\"https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-review.svg\" target=\"_blank\" rel=\"noopener\">View full size</a></figcaption></figure><h2 id=\"primary-references-and-further-reading\">Primary references and further reading</h2><p>Use the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.</p><ul><li><a href=\"https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html\" rel=\"noopener noreferrer\" target=\"_blank\">OASIS — MQTT 5.0 specification</a></li><li><a href=\"https://www.modbus.org/modbus-specifications\" rel=\"noopener noreferrer\" target=\"_blank\">Modbus Organization — Protocol specifications</a></li><li><a href=\"https://sparkplug.eclipse.org/specification/version/3.0/\" rel=\"noopener noreferrer\" target=\"_blank\">Eclipse Foundation — Sparkplug 3.0 specification</a></li></ul><!-- asp-editorial-202609 -->","markdown":"# IIoT Platform Selection: Capabilities and Evaluation Criteria\n\n> The industrial IoT platform market is crowded and loud: every vendor claims edge-to-cloud, digital twins, and AI. Yet the platform decision is one of the most…\n\n- Canonical URL: https://wiki.aspotomasyon.com/article/iiot-platform-selection\n- Publisher: ASP OTOMASYON A.Ş. (ASP OTOMASYON Wiki)\n- Category: Modern Connectivity\n- Published: 2026-08-11 · Updated: 2026-09-13\n- Reading time: 5 min · Language: English\n\nThe industrial IoT platform market is crowded and loud: every vendor claims edge-to-cloud, digital twins, and AI. Yet the platform decision is one of the most consequential and expensive choices in a digitalization program — platforms are adopted for a decade, and migrating between them is a project in itself. This article cuts through the marketing with a functional view: what an IIoT platform actually does, what the architecture options are, and how to evaluate candidates against the plant's real use cases.\n\n![A generic industrial messaging path. A network or broker acknowledgment is not necessarily confirmation that a downstream business action succeeded.](https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-context.svg)\n\n*A generic industrial messaging path. A network or broker acknowledgment is not necessarily confirmation that a downstream business action succeeded.*\n\n## What an IIoT Platform Does\n\nAn IIoT platform is the software backbone between the plant and the applications that use its data. The functional layers:\n\n- **Connectivity** — device/gateway onboarding, protocol support (MQTT/Sparkplug, OPC UA, Modbus, vendor protocols), and connection management at scale.\n- **Device and asset management** — device registry, configuration, firmware updates, and the asset hierarchy (site → line → machine → point) that organizes everything else.\n- **Data management** — ingestion, time-series storage, quality and context handling, and data access (APIs, SQL, export).\n- **Application services** — dashboards, rules/alerts, analytics, and integration interfaces (REST, webhooks, connectors).\n- **Administration and security** — identity, roles, multi-tenancy, audit, and the security controls that make the platform trustworthy.\n\nThe depth of each layer varies enormously between products — from lightweight dashboards-in-a-box to full industrial data platforms with edge runtimes.\n\n## Architecture Options\n\n| Architecture | Strengths | Weaknesses |\n| --- | --- | --- |\n| SaaS (multi-tenant cloud) | Fast start, zero infrastructure, provider-managed security and updates. | Data leaves the plant (legal/sovereignty checks), recurring cost, provider lock-in. |\n| Private cloud / self-hosted | Data control, custom integration depth. | You operate it: updates, security, scaling — a small IT department in itself. |\n| Edge-first platform | Data processed at the plant, cloud optional; low latency, resilience to connectivity loss. | More engineering; the edge is part of the OT surface (see the cloud/edge security article). |\n| Hybrid (edge + cloud) | The industrial standard: edge for collection/control-adjacent processing, cloud for scale and analytics. | Two environments to operate; integration quality decides the outcome. |\n\nThe evaluation should be anchored in the *target architecture* — where the data must live, who operates what, and how the platform fits the plant's OT security model — before comparing feature lists.\n\n## Evaluation Criteria That Matter\n\n1. **Protocol and integration depth** — native Sparkplug B? OPC UA client/server? Fieldbus gateways? The integration cost with the installed base is the platform's largest hidden price.\n2. **Data model quality** — can the platform represent the plant's asset hierarchy and data context (units, quality, timestamps), or is it a flat tag bucket? Context is what makes the data usable later.\n3. **Openness** — export capability (all data and configuration, documented), APIs, and the absence of proprietary locks: assess the exit cost as seriously as the entry cost.\n4. **Security posture** — the platform's security model (identity, encryption, audit), its certifications, and its fit with the plant's IEC 62443 zoning.\n5. **Operational model** — who runs it (vendor, plant IT, automation), the update cadence, and the support terms; a platform without an operational owner is a ghost.\n6. **Cost model** — per-device, per-message, per-user, or bundled; model the bill on the plant's real data volume (see the cloud integration article for the cost drivers).\n7. **Ecosystem** — the application ecosystem (analytics, visualization, industry solutions) and the community; the platform's ecosystem is its long-term value.\n\n## The Evaluation Process\n\n1. **Define the use cases first** — the three to five concrete applications (remote monitoring of site X, OEE analytics, alarm notification) with their data needs; the use cases are the platform's acceptance test.\n2. **Shortlist on architecture** — filter by the target architecture and the integration profile; five candidates is enough.\n3. **Run a pilot with real data** — connect one real asset (or a simulator) with the actual protocol, build the use case dashboard, and test the operational details: onboarding, alerts, data export.\n4. **Score against the criteria with evidence** — a weighted scorecard filled from the pilots, not from sales calls; include the exit-cost question.\n5. **Reference calls** — talk to plants of similar size and industry running the platform for 2+ years; ask about the operational reality, not the features.\n\n## Common Mistakes\n\n- Choosing by dashboard beauty — dashboards are the cheapest layer to build; data access and integration are the expensive ones.\n- Platform-first, use-case-later — the classic: buy the platform, then search for problems; the result is an expensive dashboard museum.\n- Ignoring the operational cost — the platform's monthly cost is the visible part; the integration, training, and operations effort is usually larger.\n- Lock-in by neglect — no data export tested, no configuration export, and the platform becomes the plant's memory with no way out.\n\n## Summary\n\nIIoT platform selection is architecture first, features second: decide where the data lives and who operates it, then evaluate integration depth, data model quality, openness, security, operations, and cost against concrete use cases with a real pilot. The platform is a decade-long partner — choose it like a hiring decision, with evidence, references, and an exit plan.\n\n## Apply this to your project\n\n- Specify payload structure, units, identity, time semantics, access permissions, and protocol versions.\n- Test backlog growth, connection loss, duplicate delivery, and restart behavior at the consuming application.\n- Document how operators see failures and how the system distinguishes replayed data from current process state.\n\n[Follow an ASP project guide](https://wiki.aspotomasyon.com/guides) to connect the fundamentals with implementation and acceptance.\n\n![Engineering review sequence: Contract → Connect → Interrupt → Reconcile. Keep the recorded evidence with the accepted configuration.](https://wiki.aspotomasyon.com/assets/diagrams/modern-connectivity-review.svg)\n\n*Engineering review sequence: Contract → Connect → Interrupt → Reconcile. Keep the recorded evidence with the accepted configuration.*\n\n## Primary references and further reading\n\nUse the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.\n\n- [OASIS — MQTT 5.0 specification](https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html)\n- [Modbus Organization — Protocol specifications](https://www.modbus.org/modbus-specifications)\n- [Eclipse Foundation — Sparkplug 3.0 specification](https://sparkplug.eclipse.org/specification/version/3.0/)\n\n---\n\nCite the canonical article: https://wiki.aspotomasyon.com/article/iiot-platform-selection (IIoT Platform Selection: Capabilities and Evaluation Criteria, ASP OTOMASYON, updated 2026-09-13).\n","headings":[{"id":"what-an-iiot-platform-does","title":"What an IIoT Platform Does"},{"id":"architecture-options","title":"Architecture Options"},{"id":"evaluation-criteria-that-matter","title":"Evaluation Criteria That Matter"},{"id":"the-evaluation-process","title":"The Evaluation Process"},{"id":"common-mistakes","title":"Common Mistakes"},{"id":"summary","title":"Summary"},{"id":"apply-this-to-your-project","title":"Apply this to your project"},{"id":"primary-references-and-further-reading","title":"Primary references and further reading"}],"faq":[],"references":[{"name":"OASIS — MQTT 5.0 specification","url":"https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html"},{"name":"Modbus Organization — Protocol specifications","url":"https://www.modbus.org/modbus-specifications"},{"name":"Eclipse Foundation — Sparkplug 3.0 specification","url":"https://sparkplug.eclipse.org/specification/version/3.0/"}],"related":[{"slug":"predictive-maintenance-vibration-analysis","title":"Predictive Maintenance with Vibration Analysis","summary":"Vibration analysis is the most widely used and most effective predictive maintenance (PdM) technique for rotating machinery. Studies by the U.S. Department of…","category":{"slug":"process-industries-solutions","name":"Process Industries Solutions"},"url":"https://wiki.aspotomasyon.com/article/predictive-maintenance-vibration-analysis","markdown_url":"https://wiki.aspotomasyon.com/article/predictive-maintenance-vibration-analysis.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/predictive-maintenance-vibration-analysis","published":"2026-05-13T12:07:56+00:00","modified":"2026-09-13T16:44:25+00:00","reading_minutes":8,"word_count":1696,"image":"https://wiki.aspotomasyon.com/assets/social/predictive-maintenance-vibration-analysis-7fe4c22125e1.png"},{"slug":"dcs-vs-plc-selection-guide","title":"DCS vs. PLC — A Comprehensive Selection Guide for Process Applications","summary":"Selecting the right control platform is one of the most consequential decisions in any industrial automation project.","category":{"slug":"automation-systems","name":"Automation Systems"},"url":"https://wiki.aspotomasyon.com/article/dcs-vs-plc-selection-guide","markdown_url":"https://wiki.aspotomasyon.com/article/dcs-vs-plc-selection-guide.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/dcs-vs-plc-selection-guide","published":"2026-05-13T11:58:29+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":7,"word_count":1414,"image":"https://wiki.aspotomasyon.com/assets/social/dcs-vs-plc-selection-guide-5527026a81d5.png"},{"slug":"industry-4-0-implementation-roadmap","title":"Industry 4.0 Implementation Roadmap","summary":"Implementing Industry 4.0 is not a single project — it is a multi-year transformation journey that requires strategic planning, cross-functional alignment, and…","category":{"slug":"digital-transformation","name":"Digital Transformation"},"url":"https://wiki.aspotomasyon.com/article/industry-4-0-implementation-roadmap","markdown_url":"https://wiki.aspotomasyon.com/article/industry-4-0-implementation-roadmap.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/industry-4-0-implementation-roadmap","published":"2026-05-12T12:47:31+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":5,"word_count":1079,"image":"https://wiki.aspotomasyon.com/assets/social/industry-4-0-implementation-roadmap-5af6ee703d9f.png"},{"slug":"control-system-modernization-retrofit","title":"Control System Modernization: Retrofit and Migration Planning","summary":"Industrial plants run on control systems with lifecycles measured in decades, but the underlying platforms age faster: processors reach end of life, operating…","category":{"slug":"automation-systems","name":"Automation Systems"},"url":"https://wiki.aspotomasyon.com/article/control-system-modernization-retrofit","markdown_url":"https://wiki.aspotomasyon.com/article/control-system-modernization-retrofit.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/control-system-modernization-retrofit","published":"2026-08-11T13:05:19+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":794,"image":"https://wiki.aspotomasyon.com/assets/social/control-system-modernization-retrofit-5a290abffcb3.png"}],"citation":"ASP OTOMASYON. IIoT Platform Selection: Capabilities and Evaluation Criteria. Updated 2026-09-13. https://wiki.aspotomasyon.com/article/iiot-platform-selection"}}