A common challenge at manufacturing sites in India is rushing into visualization while leaving equipment connectivity for later. This article explains whether you should use Kepware Server, ThingWorx, or both within the Velotic product portfolio.
Kepware Server connects shop-floor equipment, PLCs, and applications, standardizes the data, and passes it to upper-level systems. ThingWorx is an IIoT platform that handles visualization, analysis, and application development using collected data to support operational improvement. The difference is whether the focus is on collecting data or using it.
| Comparison Item | Kepware Server | ThingWorx |
|---|---|---|
| Main role | Connects equipment, PLCs, and applications | Visualizes, analyzes, and uses data |
| Main users | Site engineers and maintenance staff | Factory managers and DX leads |
| Implementation purpose | Data collection and standardization | Operational improvement and decision support |
| Best-fit scope | Multi-vendor connectivity | Visualization, analysis, and application development |
| Role in implementation | Connection-layer foundation | Utilization-layer foundation |
Kepware Server helps shop-floor teams establish connections with equipment, while ThingWorx helps managers analyze data and use it for operational improvement. Keep in mind that they are used in different phases and by different users.
| Comparison Item | Kepware Server | ThingWorx |
|---|---|---|
| Approach to mixed equipment | Easy to connect different equipment | Easy to manage collected data across equipment |
| How it works on site | Easy to collect data across manufacturers | Easy to compare conditions across equipment |
| Use across multiple sites | Easy to standardize the connectivity foundation | Easy to expand into comparison and monitoring |
| Implication when Japanese-made PLCs are mixed in | Japanese-made OPC servers can also be considered | Choosing the right connectivity foundation becomes important |
In mixed environments, the two products come into play at different stages. Kepware Server is strongest at the stage of extracting data from equipment made by different manufacturers. ThingWorx creates value at the stage of visualizing collected data across the plant and linking it to comparison and improvement actions. When Japanese-made PLCs are part of the mix, there may also be room to consider a Japanese-made OPC server at the connection layer.
| Comparison Item | Kepware Server | ThingWorx |
|---|---|---|
| Main purpose of the PoC | Confirm connectivity first | Confirm the intended use case |
| Starting point for validation | Check communication with PLCs and equipment | Check screens, analysis, and operational design |
| Suitable initial validation | Validating shop-floor data acquisition | Validating the feasibility of digital transformation initiatives |
| How to run the PoC | Easy to start with a short connectivity check | Easy to design and validate data-use scenarios |
Even in a pre-implementation PoC, you need to separate the objectives. For Kepware Server, which handles communication, validation focuses on confirming whether data can be acquired stably. For ThingWorx, validation checks whether visualized screens and analysis results are useful for shop-floor operations and business improvement.
The answer depends on whether your challenge is connecting equipment or using the data after it is connected. If you want to move seamlessly from connectivity through visualization and analysis, consider combining both products.
| When Kepware Server Is a Good Fit | When you first want to establish equipment connectivity / connect PLCs from multiple manufacturers (for example, automotive or electronics factory projects in Chennai or Pune) |
|---|---|
| When ThingWorx Is a Good Fit | When you want to move into visualization, analysis, and improvement / expand digital transformation initiatives (for example, major manufacturing or pharmaceutical projects in Bengaluru or Hyderabad) |
| When Both Are a Good Fit | When you want to proceed end to end from connectivity to utilization (for example, a new EV factory project in Sanand, Gujarat) |
Kepware Server is an industrial connectivity tool, while ThingWorx is an IIoT utilization tool. Understanding each product’s area of strength is a practical shortcut to project success.
Both products had been offered under the PTC brand, but in March 2026 the Kepware and ThingWorx businesses were sold to a TPG affiliate and incorporated into the portfolio of Velotic, an independent industrial software company formed by combining them with GE Vernova’s former Proficy business*.
When Japanese-made PLCs are installed on the shop floor, adopting a Japanese-made OPC server at the communication layer can often make configuration work and later maintenance smoother. The article below explains how to choose an OPC server that fits your project requirements and introduces recommended products. Please use it when comparing and evaluating options.
Connects with PLCs, robots, and machine tools from 100+ manufacturers and 400+ device series.
Existing control devices can stay in use, even in mixed-generation environments.
Without modifying equipment, you can use OPC server-side scripting to shape data and apply equipment recipe data.
The scripting function is available at no additional cost.
Packaged licensing* for large-scale standardization reduces the need to procure licenses when adding new sites or manage updates site by site. This supports scaling while maintaining the management framework.
With add-on options, OPC servers running at different sites can be centrally managed from the main site.
Collects oil and gas drilling data via OPC. Secure transmission across firewalls and redundancy help maintain an audit-ready data foundation over time.
All servers include diagnostic logging with log-level settings and filtering. The logs can also serve as a foundation for audit trails.