WaterWorX - a platform built on ThingWorx
May 30, 2017

WaterWorX - a platform built on ThingWorx

Laurie Reynolds | TrustRadius Reviewer
Score 10 out of 10
Vetted Review

Overall Satisfaction with ThingWorx

We are a specialist systems integrator working in the water sector, developing water and wastewater treatment and distribution system solutions in the industrial, environmental and municipal sectors. I became interested in Thingworx just as the IOT was emerging as a significant transformation technology in industrial automation. I have a background as a senior engineer in the specification of industry 3.0 water monitoring control and automation.

When I first met the Thingworx founding team in late 2011, I was blown away by the performance and concept underlying ThingWorx. As a domain expert, I no longer had to express my requirements in a classical requirements spec, I could develop it in an agile way, continuously improving the data model as my understanding of the application became more sophisticated. The ability to then build a mashup in the same time it took to develop a PowerPoint slide deck was a revelation. I discovered later that I still need an FRS but it became a strategic roadmap rather than customised local solution.

Since those early days, the platform has gone from strength to strength, and now it is past its critical mass and is attracting a strong partner community. As a small, but long-standing partner, I'm confident that the future of our WaterWorX platform will accelerate due to our reliance on ThingWorx to power our smart water applications.
  • The ThingWorx modeling is simple enough to explain to non-specialists but very powerful in its expression.
  • Mashup builder and analytics utilities are strong and the latest version automates some of the complexity, although I haven't used them yet.
  • As the Kepware tools and libraries have become more integrated, the platform has an unrivaled set of interface solutions.
  • 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.
  • Our v-business is built on ThingWorx
  • High impact.
Well-suited - multiple streams from many data sources, highly scalable application scenarios.

Less appropriate - Large complex one-off process plants with complex logic at the edge.