{
  "version": "2026-08-29.1",
  "reviewed": "2026-08-29",
  "scope": "Eight active digital-twin platforms reviewed from official product, developer or transaction sources. This is a requirements map, not a performance ranking.",
  "sources": {
    "cognite-docs": {
      "label": "Cognite Data Fusion documentation",
      "url": "https://docs.cognite.com/cdf"
    },
    "velotic": {
      "label": "Velotic company and portfolio",
      "url": "https://www.velotic.com/"
    },
    "proficy-sale": {
      "label": "GE Vernova Proficy sale completion",
      "url": "https://www.gevernova.com/news/press-releases/ge-vernova-completes-sale-proficyr-software-business"
    },
    "siemens-faq": {
      "label": "Siemens Insights Hub FAQ",
      "url": "https://www.siemens.com/en-us/products/insights-hub/resources/faq/"
    },
    "siemens-dev": {
      "label": "Siemens Insights Hub developer overview",
      "url": "https://developer.siemens.com/insights-hub/overview.html"
    },
    "bentley-platform": {
      "label": "Bentley iTwin platform concepts",
      "url": "https://developer.bentley.com/itwin-platform-concepts/"
    },
    "bentley-api": {
      "label": "Bentley iTwin APIs",
      "url": "https://developer.bentley.com/apis/"
    },
    "ansys": {
      "label": "Ansys Twin Builder",
      "url": "https://www.ansys.com/products/digital-twin/ansys-twin-builder"
    },
    "azure-models": {
      "label": "Azure Digital Twins models",
      "url": "https://learn.microsoft.com/en-us/azure/digital-twins/concepts-models"
    },
    "azure-api": {
      "label": "Azure Digital Twins APIs and SDKs",
      "url": "https://learn.microsoft.com/en-us/azure/digital-twins/concepts-apis-sdks"
    },
    "aws-product": {
      "label": "AWS IoT TwinMaker",
      "url": "https://aws.amazon.com/iot-twinmaker/"
    },
    "aws-pricing": {
      "label": "AWS IoT TwinMaker pricing",
      "url": "https://aws.amazon.com/iot-twinmaker/pricing/"
    }
  },
  "platforms": [
    {
      "slug": "cognite",
      "name": "Cognite Data Fusion",
      "vendor": "Cognite",
      "type": "Industrial data foundation",
      "purpose": [
        "connect",
        "monitor",
        "predict"
      ],
      "infrastructure": [
        "historian",
        "mixed"
      ],
      "deployment": [
        "cloud-edge"
      ],
      "physics": "optional",
      "data": "Contextualises industrial time series, engineering models and documents for applications and twins.",
      "prerequisite": "A data team must connect and contextualise source systems; this is not a turnkey asset model.",
      "focus": "Data-rich industrial assets and processes",
      "standards": "Documented APIs and SDKs; connector support must be checked against the buyer's exact systems.",
      "sources": [
        "cognite-docs"
      ]
    },
    {
      "slug": "ge-proficy",
      "name": "Velotic Proficy",
      "vendor": "Velotic (formerly GE Vernova)",
      "type": "Manufacturing operations stack",
      "purpose": [
        "monitor",
        "optimise",
        "connect"
      ],
      "infrastructure": [
        "proficy",
        "historian",
        "mixed"
      ],
      "deployment": [
        "on-prem",
        "cloud-edge"
      ],
      "physics": "optional",
      "data": "HMI/SCADA, MES, industrial data management and analytics portfolio.",
      "prerequisite": "Confirm the exact Proficy modules, connectors and licences in the proposed architecture.",
      "focus": "Discrete, process and hybrid manufacturing",
      "standards": "Not confirmed in the reviewed sources; request the current API and connector matrix.",
      "sources": [
        "velotic",
        "proficy-sale"
      ]
    },
    {
      "slug": "ptc-thingworx",
      "name": "Velotic ThingWorx and Kepware",
      "vendor": "Velotic (formerly PTC)",
      "type": "Industrial IoT application platform",
      "purpose": [
        "connect",
        "monitor",
        "optimise"
      ],
      "infrastructure": [
        "plc",
        "mixed"
      ],
      "deployment": [
        "cloud-edge",
        "on-prem"
      ],
      "physics": "optional",
      "data": "Industrial connectivity plus an application platform for connected operations.",
      "prerequisite": "Verify the current post-divestiture product boundary and every required protocol in the RFI.",
      "focus": "Connected equipment and industrial applications",
      "standards": "Kepware is the connectivity layer; the current post-divestiture integration contract must be confirmed.",
      "sources": [
        "velotic"
      ]
    },
    {
      "slug": "siemens-insights-hub",
      "name": "Siemens Insights Hub",
      "vendor": "Siemens",
      "type": "Industrial IoT service",
      "purpose": [
        "connect",
        "monitor",
        "optimise"
      ],
      "infrastructure": [
        "siemens",
        "plc",
        "mixed"
      ],
      "deployment": [
        "cloud-edge"
      ],
      "physics": "optional",
      "data": "Connects industrial assets to cloud and edge applications through the Insights Hub ecosystem.",
      "prerequisite": "Map the plant's connectivity, tenancy, data-volume and edge requirements before selecting a package.",
      "focus": "Industrial equipment and Siemens-connected operations",
      "standards": "Developer APIs are documented; exact device and protocol support belongs in the pilot record.",
      "sources": [
        "siemens-faq",
        "siemens-dev"
      ]
    },
    {
      "slug": "bentley-itwin",
      "name": "Bentley iTwin",
      "vendor": "Bentley Systems",
      "type": "Engineering and lifecycle twin",
      "purpose": [
        "lifecycle",
        "monitor"
      ],
      "infrastructure": [
        "cad-bim",
        "mixed"
      ],
      "deployment": [
        "cloud-edge"
      ],
      "physics": "optional",
      "data": "Combines engineering, reality and operational data around infrastructure and industrial assets.",
      "prerequisite": "An engineering-model or reality-data pipeline is normally the starting point.",
      "focus": "Infrastructure and complex engineered assets",
      "standards": "Bentley documents iTwin APIs; test import, change tracking and export with the buyer's real model.",
      "sources": [
        "bentley-platform",
        "bentley-api"
      ]
    },
    {
      "slug": "ansys-twin-builder",
      "name": "Ansys Twin Builder",
      "vendor": "Ansys, part of Synopsys",
      "type": "Physics-based twin builder",
      "purpose": [
        "predict",
        "optimise"
      ],
      "infrastructure": [
        "simulation",
        "mixed"
      ],
      "deployment": [
        "desktop",
        "cloud-edge"
      ],
      "physics": "required",
      "data": "Builds system-level, reduced-order and hybrid twins from simulation models and operating data.",
      "prerequisite": "A suitable physics or system model and modelling expertise are required for the reviewed route.",
      "focus": "Equipment and systems where physics models are available",
      "standards": "The product page documents model and deployment workflows; verify the exact FMI/FMU path for the planned version.",
      "sources": [
        "ansys"
      ]
    },
    {
      "slug": "azure-digital-twins",
      "name": "Azure Digital Twins",
      "vendor": "Microsoft",
      "type": "Twin graph platform",
      "purpose": [
        "connect",
        "monitor",
        "lifecycle"
      ],
      "infrastructure": [
        "azure",
        "cloud-iot",
        "mixed"
      ],
      "deployment": [
        "cloud"
      ],
      "physics": "optional",
      "data": "Models connected environments as a graph using DTDL and Azure APIs.",
      "prerequisite": "A development team must define models, ingestion and applications; this is not a packaged plant twin.",
      "focus": "Custom connected environments on Azure",
      "standards": "DTDL models plus documented REST APIs and SDKs.",
      "sources": [
        "azure-models",
        "azure-api"
      ]
    },
    {
      "slug": "aws-iot-twinmaker",
      "name": "AWS IoT TwinMaker",
      "vendor": "Amazon Web Services",
      "type": "Cloud twin application service",
      "purpose": [
        "connect",
        "monitor",
        "lifecycle"
      ],
      "infrastructure": [
        "aws",
        "cloud-iot",
        "mixed"
      ],
      "deployment": [
        "cloud"
      ],
      "physics": "optional",
      "data": "Builds twin applications from existing data sources and visual models without creating another data store.",
      "prerequisite": "An AWS architecture and application work are required; confirm region, service and data-access costs.",
      "focus": "Custom industrial and building twin applications on AWS",
      "standards": "AWS documents connectors and unified data-access APIs; test every required source and export path.",
      "sources": [
        "aws-product",
        "aws-pricing"
      ]
    }
  ],
  "pilot_checks": [
    {
      "name": "Data ingestion",
      "test": "Connect one approved real source and record tag discovery, timestamp handling, units and update behaviour.",
      "evidence": "Source configuration, sample export, gaps, unit mapping and buyer-defined acceptance criterion."
    },
    {
      "name": "Model creation",
      "test": "Build the smallest useful model of one real asset or process using the buyer's own data or engineering model.",
      "evidence": "Model version, source files, mapping decisions, build effort and buyer-defined state tolerance."
    },
    {
      "name": "Known-event replay",
      "test": "Replay one permitted historical operating event and one clean comparison period.",
      "evidence": "Frozen input window, expected observation, actual output, unresolved differences and adjudicator."
    },
    {
      "name": "System integration",
      "test": "Exchange one agreed asset or work-context record with the target CMMS, historian, ERP or data platform.",
      "evidence": "Field map, direction, timestamps, failed records, retries and exported transaction log."
    },
    {
      "name": "Edge and network boundary",
      "test": "Run the planned edge or gateway route inside the approved network boundary.",
      "evidence": "Ports, components, buffering behaviour, measured latency range and buyer-defined limit."
    },
    {
      "name": "Export and portability",
      "test": "Request a complete export of the pilot's models, data, configuration and audit history.",
      "evidence": "Formats, API endpoints, omissions, licence constraints and re-import result."
    },
    {
      "name": "Operator decision",
      "test": "Give a named role one representative decision using only the pilot interface and approved instructions.",
      "evidence": "Task, completion record, questions, corrections and buyer-defined usability criterion."
    },
    {
      "name": "Quoted scope",
      "test": "Reconcile the architecture and pilot usage against an itemised supplier quote.",
      "evidence": "Licences, connectors, storage, data volume, environments, support, services and excluded costs."
    }
  ]
}