I think the main difference is that Industrial Edge is an Open Ecosystem and WinCC OA IOT Suite just for WinCC Systems only. See also the following descriptions:

WinCC OA IoT Suite: Apps and Management for WinCC System only! No open ecosystem:

Central distribution of software and updates works right out of your plant infrastructure, with fully automatic and time-controlled deployment. There is an available cloud connection via IOT-Repository, which is however optional and not required for operation.

A variety of IOT apps enable easy and intuitive operation without specialized knowledge or training. The base installation includes apps for PLC configuration, data mapping and dashboarding, other digital functions, e.g. for equipment efficiency calculations (OEE) can be installed via IOT-OPA. Additionally, SIMATIC WinCC OA partners can distribute their own individually adapted solutions via IOT-Repository.
Enjoy the benefits of reliable data acquisition directly at the machine, a secure, fault-free linking connection of IT and OT, and data-based optimization of production and maintenance.

Industrial Edge:Industrial Edge represents an open, ready-to-use Edge computing platform consisting of Edge devices, Edge apps, Edge connectivity, and an application and device management infrastructure.It is an infrastructure to centrally manage and deploy ANY application (not tied to product family) to the shopfloor and machines. Applications can be either purchased ready to use from Marketplace (input by Siemens and 3rd Party providers) or written by customer or solution providers themselves. Applications can reach from simple IoT use case such as data collection and cloud connectivity to Analytics of e.g. performance, energy or drives data, and last but not least to advanced AI use cases to optimize product quality or production processes. Plus, Industrial Edge offers customers a scalable infrastructure to run many different ioT use cases simultaneously.

I do not know why WinCC OA IOT Suite is only for WinCC systems. Nor why it has no open ecosystem. As the name (WinCC Open Architecture) already suggests it is open and as stated before partners are can distribute own apps via the IOT-repository. It has a special API for developers and surely they can offer a training for creating own apps.

It has support for various systems outside WinCC, among others: Industrial Edge, docker, SQL and OPC UA.

Gertjan van Schijndel

It has support for various systems outside WinCC, among others: Industrial Edge, docker, SQL and OPC UA.

 Thank you. But this exists for Siemens Industrial Edge as well. So what is the difference between these two platforms offered by Siemens?

I am not an expert, but the difference is in the implementation, which apps are available and how custom app can be developed.

To my knowledge industrial edge (custom) apps run in a docker container. Do not know in which environment custom app can be developed.

The WinCC OA IOT Suite runs completely native/directly on the OS. Custom apps are developed with WinCC OA and become part of the running WinCC OA project, so it could even change the standard functionality and/or how it complete application looks.

Thank you for the response. Just curious if the plan is to discontinue WinCC OA IoT Suite since there hasn't been any major updates to it since 2021 (After Siemens Industrial Edge was released).

Also there has been no promotion on WinCC OA IoT Suite in any of the recent trade shows, where as Siemens Industrial Edge is being marketed widely. Would be nice to get a clarity on the roadmap of the two platforms from somebody from Siemens Industrial Edge group. 

Thanks.

To put simply, one is a pure software solution (WinCC OA) and the other a combination of hardware and software (Industrial Edge Machine/Device = IEM/IED).

The synergy here is that it is easy to flood OA (or any SCADA in the market) with excessive data, so you will need an IPC to collect and filter that data first before it reaches the OA system.

Implementation type 1:
- Most of the UI will be Industrial Edge-based.
- The setting up of the IED 427E by a PC with an IEM is a prerequisite.
- Info: Here's an implementation.Please find attached screenshot.
Field machine ----> IED 427E ----> WinCC OA server [shows embedded IEM/IED webpage]

Implementation type 2:
- Takes advantage on the fact that WinCC OA has a tiny footprint and can be stored in any system.
- Most of the UI would be OA-based.
- Info:Detail :: SIMATIC WinCC Open Architecture Portal (winccoa.com)
Field machine ----> IOT 2050 [WinCC OA installation]

Implementation type 3:
- Uses the Flow Creator / Node-Red IED app with nodes for MQTT and a range of connectors including OPC UA and S7 Siemens Connector.
Field machine ----> IED 427E [Flow Creator app]

Implementation type 4:
- OA has MQTT driver, explorer, and publisher.
- Tags are generating strings.
- You may post process with "substring" function blocks within the Node-Red app.
Field machine ----> WinCC OA server [embedded Node-Red]

Thank you for the detailed explanation. 
I think you are comparing it with WinCC OA. Not WinCC OA IOT Suite. Both are different. 
Could you please compare Industrial Edge with WinCC OA IOT Suite?

AutoGen_6355352

To put simply, one is a pure software solution (WinCC OA) and the other a combination of hardware and software (Industrial Edge Machine/Device = IEM/IED).

The synergy here is that it is easy to flood OA (or any SCADA in the market) with excessive data, so you will need an IPC to collect and filter that data first before it reaches the OA system.

Implementation type 1:
- Most of the UI will be Industrial Edge-based.
- The setting up of the IED 427E by a PC with an IEM is a prerequisite.
- Info: Here's an implementation.Please find attached screenshot.
Field machine ----> IED 427E ----> WinCC OA server [shows embedded IEM/IED webpage]

Implementation type 2:
- Takes advantage on the fact that WinCC OA has a tiny footprint and can be stored in any system.
- Most of the UI would be OA-based.
- Info:Detail :: SIMATIC WinCC Open Architecture Portal (winccoa.com)
Field machine ----> IOT 2050 [WinCC OA installation]

Implementation type 3:
- Uses the Flow Creator / Node-Red IED app with nodes for MQTT and a range of connectors including OPC UA and S7 Siemens Connector.
Field machine ----> IED 427E [Flow Creator app]

Implementation type 4:
- OA has MQTT driver, explorer, and publisher.
- Tags are generating strings.
- You may post process with "substring" function blocks within the Node-Red app.
Field machine ----> WinCC OA server [embedded Node-Red]