Google Cloud IoT vs. ThingWorx

I consider myself very techy and found Google Cloud IoT platform very challenging to manage. The lack of tutorials and discussions to understand how each section works is very challenging. I specifically made a connection after several hours to Google Nest to third-party integration, Home Assistant. Shortly after Google Cloud upgraded to a new version breaking the connection. This was extremely frustrating. No service should take several hours to figure out, in my opinion, if it does, the platform is doing a poor job of making it easy. I'm personally very discouraged any time I ever have to use this platform. It's very hard to find answers.

Incentivized

ThingWorx is great if you want to create an MES-like solution for your company, but have data coming not only from the plant floor, but also from databases, azure, and others. You can seamlessly integrate those data and create reports like visuals and mashups. It is also a great solution if you have multiple plants and need to monitor everyone simultaneously and even compare results between locations. ThingWorx is not recommended if all you need is a BI solution, it is not a reporting software and it should not be used as it.

Incentivized

• Integration with different brands of microcontrollers including the one currently used by Espresiff.
• The platform is very robust and secure.

Incentivized

• Quick monitoring of extraordinary behaviour of a monitored component
• As the Kepware tools and libraries have become more integrated, the platform has an unrivalled set of interface solutions.
• Modelling is simple enough to explain to non-specialists but very powerful in its expression.

Incentivized

• Not beginner friendly.
• Needs more tutorials and walk throughs on how to get started.
• Very complicated and unless you know what you are doing you will be lost.
• Lack of material found on how to do each section / services.

Incentivized

• The MQTT interface needs improvement, its crashed during development of new entities on a frequent basis.
• The standard time series and trend tools are very basic and dont compare well with Top-end historians but its possible with some relative easy interfacing to use 3rd party applications.
• Care, forethought and experience is required when building complex applications, it's difficult to delete entities once the network becomes large and complex. N+Maintaining synchronicity between multiple dev and productions systems has to be carefully managed.

Incentivized

We started more than a year ago and do not plan to replace it

Incentivized

Experienced and knowledgeable customer support executives, Thingworx is a very large product and contains a myriad of features which is not easy to remember without enough training or hands-on experience

Incentivized

Although comparisons are hateful, even more so when we are talking about leading brands where the quality of their services are indisputable, the general environment of Google was more familiar to me since I use, for example, Google Firebase on a daily basis, where part of the concepts are similar, without Without a doubt, AWS services are excellent, but it was easier for me to go through the functions of Google Cloud IoT.

Incentivized

Azure and Oracle IoT and Thingworx all provide very good support and very easy analytics when it comes to data streams. ThingWorx and Azure both have very good security and provide a robust set of capabilities. However, ThingWorx's main advantage is its built-in templates for custom apps that are industry-agnostic unlike many of its peers.

Incentivized

• The amount of hours to get things integrated is negative.
• The amount of hours researching how to get devices integrated is negative.
• Overall the amount of time and effort getting things working has been a negative experience.

Incentivized

• The use of ThingWorx as a near-complete, full-stack industry 4.0 solution has been at the forefront of recent and ongoing research.