# What is PTC ThingWorx? Modules, integrations and alternatives > Source: https://netray.co/software/ptc-thingworx > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Manufacturing Software Encyclopedia ## Short answer PTC ThingWorx is an industrial IoT application platform used to connect equipment, model it as Things, and build dashboards and applications on top of the data. It is commonly paired with PTC's Kepware connectivity and PLM products such as Windchill. ## Vendor PTC ## Category integration-data ## Aliases - ThingWorx - ThingWorx IIoT platform - ThingWorx Foundation ## Overview ThingWorx lets developers model machines, lines and other assets as Things with properties, services and events, then build applications that display and act on that data. Its low-code tooling includes a composer for the model and a mashup builder for screens, with server-side logic written in JavaScript services. Typical users are manufacturers building custom monitoring and operations apps, PTC partners and integrators delivering solutions, and product companies connecting their own installed products. The platform is application oriented, so it suits cases where a team wants a tailored operator or manager screen rather than a fixed off-the-shelf dashboard. In a manufacturing stack it sits above device connectivity, for example Kepware or other agents and edge SDKs, and next to MES, historian, ERP and PLM. It does not replace those systems, but it can combine their data in one place. Because it is a development platform, outcomes depend heavily on the quality of the data model and the people building on it. ## Best For - Manufacturers wanting custom operations or monitoring apps without full custom coding - Organisations already using PTC Kepware, Windchill or Creo that want a connected platform - Machine and product makers connecting installed products for remote monitoring - Integrators delivering repeatable IIoT solutions across several plants - Teams that need to combine data from machines, MES and enterprise systems in one app ## Modules ### Thing model and Composer **Description:** Defines Things, Thing templates and shapes with properties, services and events, plus data storage options. ### Mashup Builder **Description:** Low-code environment for building dashboards and application screens from model data and services. ### Connectivity **Description:** Connection options including Kepware for industrial devices, edge SDKs and agents, and standard protocols. ### Services and scripting **Description:** Server-side JavaScript services and subscriptions for logic, calculations and automation inside the platform. ### Analytics **Description:** Optional analytics capabilities for trends, anomaly detection and predictive models, packaged separately from the core platform. ### REST APIs and extensions **Description:** Platform APIs and an extension mechanism for integrating with other systems and adding functionality. ### Industrial solutions **Description:** Packaged applications for areas such as operator guidance and asset monitoring that run on the platform. ## Deployment Available as customer-managed software for on-premises or private cloud installation and as vendor-hosted cloud options. Exact hosting offerings and packaging change, so confirm the current options with PTC. ## Integrations ### Kepware **Detail:** Kepware connectivity is a common route for bringing PLC and device data into ThingWorx. ### REST and extensions **Detail:** REST APIs and extensions connect ThingWorx to ERP, MES, historians and databases. ### PTC PLM **Detail:** Integration patterns exist with Windchill and other PTC products for product and configuration context. ### Edge SDKs and agents **Detail:** Edge components let devices or gateways connect to the platform directly. ### Databases and files **Detail:** Data can be loaded from or exported to relational databases and file based sources via services. ## Strengths - Flexible model and low-code tools let teams build tailored industrial apps - Works naturally with PTC Kepware, Windchill and related products - Can run on premises or in a private cloud, which suits restricted environments - Supports both monitoring and action logic through services and events - Extensible through APIs and extensions ## Limitations - Requires skilled developers and a deliberate data model, so it is not a plug and play dashboard - Solutions can become bespoke and costly to maintain without governance - Packaging, naming and licensing have evolved, so confirm what is included - Not a historian, MES or ERP, so those roles need other products - Performance planning is needed for high volume time series data ## Alternatives - Siemens Insights Hub - AWS IoT SiteWise - Litmus Edge - Ignition (Inductive Automation) - Azure IoT based solutions - GE Proficy ## Ai Opportunities - Generating Thing templates and property definitions from equipment documentation - Drafting ThingWorx service scripts and mashup layouts that developers then review - Anomaly detection and failure prediction on sensor data feeding the platform - Natural language summaries of asset status and alarms for operators and managers - Retrieval over service manuals and maintenance records alongside live asset data ## Selection Tips - Decide whether you need a development platform or a packaged monitoring product - Plan staffing for model design, development and long term maintenance - Confirm the connectivity path to your PLCs and whether Kepware licences are needed - Check hosting options against data residency and air-gap requirements - Define the data model and naming conventions before building many apps - Pilot one use case with measurable outcomes before expanding ## Faq ### What is PTC ThingWorx used for? **Answer:** It is used to build industrial IoT applications. Teams model machines and assets as Things, connect data from equipment, and create dashboards, alerts and workflows on top. Common uses include equipment monitoring, remote service of installed products and operator screens combining machine and enterprise data. ### How is ThingWorx different from Kepware? **Answer:** Kepware is a connectivity server that reads data from PLCs and devices. ThingWorx is the application platform that models that data and builds apps on it. They are often deployed together, but Kepware can also feed other systems and ThingWorx can use other connectivity sources. ### Can ThingWorx run on premises? **Answer:** Yes, customer-managed deployments on premises or in a private cloud have been offered, alongside vendor-hosted options. This makes it a candidate for restricted environments, though you should confirm current packaging, supported platforms and any dependencies with PTC for your version. ### Does ThingWorx replace MES or a historian? **Answer:** No. It can display and combine data from those systems and add application logic, but it is not a full MES with execution and genealogy, nor a purpose built historian. Many plants use it alongside both, with clear boundaries on which system owns which data. ### What skills does a ThingWorx project need? **Answer:** Typically a developer familiar with the Thing model, JavaScript services and Mashup Builder, an engineer who understands the machines and data, and someone to own the architecture and governance. Partner support is common. Without that discipline, solutions can drift into hard to maintain custom builds. ## Search terms what is ptc thingworx, thingworx alternatives, thingworx modules, thingworx api, thingworx vs kepware, thingworx vs insights hub, thingworx mashup builder, thingworx on premises, thingworx windchill integration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json