Ayush Tiwari serves as Director of Product Management at ThingWorx, bringing over a decade of expertise from his tenure at PTC. His key focus area is to continuously enhance ThingWorx platform and applications to enable manufacturers to improve their operations, quality, performance, and service at scale as part of their Digital transformation efforts. A recognized industry leader, Ayush is currently working on advancing the platform for low-code development powered by Gen-AI capabilities to maintain its competitive edge and leadership in IIoT space.
One of the recurring frustrations customers face is that their systems don't talk to each other well. Data sits in silos. Integrations are expensive to build and even more expensive to keep alive through upgrades. A project that works well at one site turns into a rebuild at the next one. None of this is new, and the industry has never really solved it in a systematic way.
What has changed is the cost of leaving it unsolved. Most of the IT and operations leaders I talk to are under pressure to put AI to work in production this year. AI agents and assistants are only as good as the context they are given, and context is exactly what a fragmented architecture destroys. When the relationship between an asset, a line, a work order and a quality result lives in four systems with four naming conventions, the agent returns a confident answer that happens to be wrong. That is where a lot of AI pilots stall, and it is rarely a model problem. It is a data context problem.
That is a large part of why we have been working with CESMII, the Smart Manufacturing Institute, and why we support what they are building around interoperability.
What CESMII is actually standardizing
CESMII organizes its work around three architectural imperatives. Smart Manufacturing Profiles, or SM Profiles, cover information modeling, so equipment and process definitions are shared rather than reinvented at every site. The Smart Manufacturing Interoperability Platform sets out what a platform must support in order to participate. Smart Interfaces, delivered today as i3X, and the Industrial Information Interoperability eXchange, give applications one common API for reaching contextualized manufacturing data instead of a different one for every vendor.
These are not aspirational concepts. i3X reached its 1.0 release this summer with a published conformance test suite and more than forty technology providers behind it. For a VP of IT within a manufacturing enterprise, the conformance suite matters more than the specification does. It means vendor claims about interoperability are now testable rather than something you take on faith during a procurement cycle.
What Velotic built
Figure 1: How Kepware, ThingWorx and Proficy integrate with CESMII SM Profiles and the i3X APIs.
The ThingWorx team has shipped a set of CESMII integration Building Blocks that make this framework practical to use rather than something you read about. All of it is anchored on ThingModel, the ThingWorx digital twin model, so SM Profiles arrive as first class model objects instead of as an import you have to own and maintain.
The first piece is SM Profile import. You pull a CESMII SM Profile into ThingWorx through a UI, browse the object type hierarchy, select what is relevant to your environment, and generate the Thing Model from it. There is no manual mapping between the standard and the platform, which saves real modeling time and keeps your model aligned with the profile instead of drifting away from it over the next two years. Details here.
The second is the ThingWorx i3X Connector, a reusable abstraction layer over the standard i3X REST APIs. ThingWorx applications call strongly typed services rather than hand building HTTP requests, which means less code to write now and far less to repair when an endpoint changes. Details here.
The third is the ThingWorx i3X Adapter, a Building Block plus a node applet that exposes the standard i3X REST endpoints from your own ThingWorx environment. Any i3X compatible client can query your contextualized ThingWorx data with no custom integration work on either side. This is the piece that lets ThingWorx participate in a wider ecosystem instead of being one more endpoint somebody has to write a connector for. Details here.
All three run on ThingWorx v10.1 and later and install through the standard Composer extension import process. Getting them running is straightforward.
On the MES side, Proficy Smart Factory is among the first MES platforms to ship a working i3X adapter. Production execution data is queryable today through the CESMII standard, with no custom connectors and no lock-in, and any i3X compatible client including ThingWorx can reach it out of the box. We are extending coverage next to real-time event subscriptions and write back, which closes the loop from consuming data to controlling execution. Details here.
Why this matters in practice
Standards adoption takes time, and interoperability across the broader ecosystem is still a work in progress. But there are three situations where this support changes the math today.
The first and most common is multi-site rollout. You deploy a condition monitoring or OEE application at one plant, it works, and the plan is to replicate it across ten more. Without a shared information model, replication turns into a rebuild every time, because the underlying data structures are different at every site. When the original application is built on an SM Profile and the platform supports that profile natively, the rollout should get considerably less complicated and considerably less expensive.
The second is modeling effort. Building a ThingWorx model that accurately reflects your production assets and processes across systems with standardized and contextualized data is real work, and it is usually the less visible line in the project plan. When a CESMII SM Profile already exists for your equipment type or your industry, importing it directly removes a large share of that upfront effort. Your team starts from a model the industry already agrees on rather than from a blank page, and you are not the one maintaining the mapping.
The third is interoperability. Velotic gives you the convenience of a single vendor across connectivity, HMI/SCADA, MES and AIoT, but interoperability is a deliberate part of our product strategy at every layer across Kepware, ThingWorx and Proficy. ThingWorx 10.0 already added IoT Streams, and i3X support now exposes the ThingWorx model and its contextualized data over REST for upstream access. Your data lake, your advanced analytics, your cold storage and whatever you add next can consume plant context without a bespoke integration each time. If you are accountable for AI-led transformation, that interoperability is the difference between an architecture you can keep evolving and one you are locked into.
For anyone running multiple plants, or working with integrators and partners who have also standardized on CESMII, the consistency this creates is genuinely useful.
Where this leaves us
ThingWorx remains an open, standards-based enterprise AIoT platform, built to accelerate time to value by taking advantage of the systems and data you already have instead of asking you to replace them. On top of that sits an AI ready portfolio with a built in Agentic AI platform, MCP server, AI tooling, and data foundation that delivers use case specific agents and enterprise applications out of the box. And with the SM Profile Importer, the i3X Connector Thing Template and i3X REST adapters for both ThingWorx and Proficy Smart Factory, plug and produce interoperability across OT and IT is something your team can install and test this quarter rather than something to wait for.
Next steps
If you are early in this process and still working out where CESMII fits in your architecture, come talk to us. Reach out at velotic.com to learn more about what we offer and how we work with CESMII technology solutions to support smart manufacturing.
Up Next