Creo Toolkit Applications for CAD Quality, Productivity, AI Readiness and Digital Thread

Check out this video Creo Toolkit Applications for CAD Quality, Productivity, AI Readiness and Digital Thread by Anika Kapoor, Technical Manager at Kalypso.

Overview

This 54-minute PTC Tips and Techniques webcast, recorded on February 12, 2026, features Anika Kapoor, Technical Manager at Kalypso (a Rockwell Automation business), comparing the five Creo customization options (J-Link, VB API, Web.Link, Creo Toolkit, and Object Toolkit) and explaining when to use each one. It is aimed at Creo users, CAD administrators, and developers planning Creo automation, and it also covers why CAD data quality underpins model-based definition (MBD), Windchill migrations, the digital thread, and AI readiness. Tom Quaglia of PTC moderates and answers the Creo Toolkit licensing questions in the Q&A.

Chapters

This video has chapters, which are also available from the player menu.

• 0:00 to 1:51: Welcome, speakers, and housekeeping
• 1:51 to 9:33: PTC Community migration to Gainsight
• 9:33 to 11:32: PTC/USER Global Summit workshops and handoff
• 11:32 to 16:51: About the presenter and Kalypso
• 16:51 to 20:43: Why build custom Creo tools: KBE, automation, integration
• 20:43 to 22:18: Creo customization APIs and languages compared
• 22:18 to 26:10: Execution modes, UI, geometry access, and licensing
• 26:10 to 30:20: Choosing the right Creo API for your use case
• 30:20 to 32:58: Q&A: Python, Object Toolkit Java, and PLM data
• 32:58 to 36:40: CAD data quality, the digital thread, and challenges
• 36:40 to 41:59: CAD quality assessment and cleansing for Windchill
• 41:59 to 44:05: Custom checks for MBD and MBE adoption
• 44:05 to 46:49: Custom tool use cases for the digital thread
• 46:49 to 48:20: AI readiness starts with consistent CAD data
• 48:20 to 54:39: Q&A: Toolkit licensing, AI coding, and Windchill errors

Key Takeaways

• Creo offers five customization options, separated first by language: J-Link (Java), VB API (VB.NET, using the COM component), Web.Link (JavaScript), Creo Toolkit (mostly a C API), and Object Toolkit (C++ wrapper classes that help with memory management).
• Only Creo Toolkit and Object Toolkit can create Creo features or interact with geometry. J-Link, VB API, and Web.Link cannot.
• J-Link, VB API, and Web.Link do not need a Toolkit license to get started. Creo Toolkit and Object Toolkit require a license, and advanced licenses exist for areas such as Mechanica (CAE).
• An application built with Creo Customization Toolkit is written once and unlocked, then anyone in the organization can use it without a runtime license. Object Toolkit Java applications require a runtime license.
• VB API has the shortest learning curve. Pro/Toolkit has the longest, unless you already build tools.
• MBD success depends on consistent, trustworthy CAD, not just the presence of PMI in the models.
• A CAD quality gate can classify each model as pass, conditional, or fail, with a red, yellow, and green scorecard, before data goes into Windchill or a future release.

Why do companies customize Creo, and what counts as customization?

Companies customize Creo because no organization should use CAD exactly out of the box: products, processes, rules, and standards differ, and custom tools enforce those standards, protect intellectual property consistency, and let engineers focus on engineering. Anika Kapoor separates CAD optimization into four overlapping buckets. Knowledge-based engineering (KBE) builds company rules into templates such as drawing templates. Automation removes repetitive work, from mapkeys up to "going from a hundred clicks to one click", while integration connects Creo to CAE, PLM, CAM, SAP, or legacy systems. Customization, in the strict sense, changes how native Creo behaves, for example making Extrude always extrude to a set length, and is used only when there is a real need.

Watch: 16:51 to 20:43 (slides defining the four buckets: KBE, automation, customization, and integration)

What Creo customization APIs are available, and which languages do they use?

Creo provides five customization options, and the first difference between them is the programming language. J-Link uses Java, VB API uses VB.NET through the COM component, Web.Link uses JavaScript, Creo Toolkit is mostly a C API that can be wrapped with C++, and Object Toolkit is the more modern option with C++ wrapper classes that help with memory management. Language matters, but the presenter stresses that execution mode, geometry access, and licensing are bigger differences.

Watch: 20:43 to 22:18 (comparison slide of the five Creo customization options)

How do J-Link, VB API, Web.Link, Creo Toolkit, and Object Toolkit differ in capability and licensing?

The Creo customization options differ most in execution mode, geometry access, and licensing. A synchronous application runs inside Creo and looks like a native Creo tool, while an asynchronous application can be launched from outside Creo. Only Creo Toolkit and Object Toolkit can create Creo features or interact with geometry, and they give the most powerful API coverage. J-Link, VB API, and Web.Link need no Toolkit license to get started, while Creo Toolkit and Object Toolkit need a license, with advanced licenses such as Pro/Toolkit for Mechanica for CAE work.

• User interface: Pro/Toolkit dialogs used to be hand-coded, but a UI editor is now available.
• Stability: Creo Toolkit is C-based, so poor memory management can cause leaks and crashes. Object Toolkit manages memory better, but crashes are still possible.

Watch: 22:18 to 26:10 (comparison table of execution modes, UI integration, feature creation, and licensing)

Which Creo API should I use for my automation project?

Choose Creo Toolkit or Object Toolkit for anything that creates, edits, or cleans up geometry, and choose J-Link, VB API, or Web.Link for parametric, assembly, batch, and integration tasks. Anything J-Link or VB API can do, Creo Toolkit and Object Toolkit can also do, but not the other way around. The presenter's examples:

• Geometry clean-up for CAE, custom valves that behave your way, or geometry from imported point clouds: Creo Toolkit or Object Toolkit.
• A configurator on top of a master model, parameter updates, or material updates: J-Link (VB API can do the same).
• Integrations with COM applications such as Excel: VB API, which is also the quickest to learn.
• Batch PDF generation for drawings: Web.Link.

All of these APIs provide some integration with Windchill, depending on the use case.

Watch: 26:10 to 30:20 (decision slide mapping use cases to each Creo API)

Why does CAD data quality matter for the digital thread?

CAD data quality matters because CAD is the foundation of engineering data and feeds quality, manufacturing, and every downstream process, so weak CAD breaks the digital thread from maturity level zero onward. The presenter's example is a designer who creates a custom welding symbol on a 2D drawing: it looks fine on paper, but downstream systems cannot read it, and the failure is hard to trace. Inconsistent design criteria, inaccurate specifications, and unenforced standards lead to manufacturing defects, rework, delays, and collaboration issues, often because there is no quality-check gate.

Watch: 32:58 to 36:40 (slides on CAD as the foundation of the model-based enterprise and common digital transformation challenges)

How can I assess CAD data quality before or after a Windchill migration?

Assess CAD data quality by running a CAD quality assessment gate that reports problems in the models and scores each one before it is released into Windchill. Kalypso uses its CADac tool for this, both for customers migrating to Windchill and for data already in Windchill. In one client case, models in Windchill kept failing to publish and check in, forcing repeated admin exceptions that stretched product timelines, until an assessment showed exactly where the data was broken.

1. Assess the data: Check modeling robustness, attributes, and MBD readiness, and report missing information, missing links, corrupted files, missing dependencies, failed regenerations, and incorrect metadata.
2. Review the scorecard: See what percentage of models are red, yellow, and green.
3. Apply the gate: Pass means the model is eligible for future MBD and enterprise reuse. Conditional means limit its use and clean it up. Fail means block it until it is fixed.
4. Cleanse: Choose a cleansing approach: the assessment tool itself or a hybrid approach.

Watch: 36:40 to 41:59 (CAD quality assessment reports, the red, yellow, and green scorecard, and the Windchill client example)

Does model-based definition (MBD) need more than PMI?

Yes. MBD success depends on consistent and trustworthy CAD, not just the presence of PMI in the models, because a model-based enterprise connects your models to other functions, systems, and your supplier network. Custom Creo checks can rate PMI completeness and model reusability, and validate models received from suppliers and partners before they are approved. The presenter recommends rolling out MBD step by step, by product team and by supplier, because no organization goes from maturity level zero to four or six quickly.

Watch: 41:59 to 44:05 (slide on custom checks for MBD and MBE adoption)

Which custom Creo tool use cases support the digital thread?

Custom Creo tools support the digital thread by making standards enforceable, moving legacy data, filling integration gaps, and capturing tribal knowledge. If your company follows ISO standards, modeling rules, naming, attributes, and data integrity checks can be built into the system and into workflows instead of relying on manual checks. The presenter describes a past project that converted line-only drawings from a Unix-based system into intelligent CATIA drawings when no out-of-the-box path existed. Small Toolkit applications also bridge systems where out-of-the-box integration is missing, and they keep knowledge in the system when long-serving engineers leave.

Watch: 44:05 to 46:49 (use-case slide: enforceable standards, legacy migration, integrations, and tribal knowledge)

Is my CAD data ready for AI?

Your CAD data is not ready for AI tools unless it is consistent, trusted, and standard, because AI cannot be leveraged on unreliable data. The presenter's advice is to start small: build consistent CAD with the help of Creo Toolkit applications and quality checks, so your systems do not fail when CAD data moves to PLM and downstream systems.

Watch: 46:49 to 48:20 (closing slide on AI readiness and consistent CAD)

Frequently Asked Questions

Q: Can I use Python to automate Creo Parametric?

A: There is no supported PTC method for Python, but a third-party approach exists: the open-source creopyson library. (answered at 30:33)

Q: What is the licensing difference between Object Toolkit Java and the C++ Creo Toolkit?

A: Object Toolkit Java requires a runtime license. With C++, you need the software only to create the application. Once the application is unlocked, anyone in the organization can use it without a runtime license. (answered at 31:19)

Q: What license do I need to develop Creo Toolkit applications?

A: Creo Customization Toolkit. It replaced Creo Application Programming Toolkit, a registered-user license where five programmers needed five licenses. Creo Customization Toolkit is a floating, locked extension that starts with Creo and includes Toolkit for C and C++, the UI editor, and other Toolkit capabilities. A developer may need only one license, used to unlock, test, and debug the tool, which can then be distributed without further licenses. Applications bought from third parties may be licensed differently. (answered at 48:33)

Q: Can a Creo Toolkit application check every part in an assembly against a set of parameters?

A: Yes. You can go recursively through the model, look at each part or subassembly, retrieve its information, and evaluate it against your criteria. (answered at 53:41)

Links & Resources

• creopyson: Python library for CREOSON (github.com)
• CREOSON: open-source Creo automation (creoson.com)
• PTC/USER Global Summit 2026 (ptcuser.org)
• Creo Toolkit Applications for CAD Quality, Productivity, AI Readiness, and Digital Thread (webinar page) (learningconnector.ptc.com)
• CAD Data Quality: The Foundation of the Digital Thread (kalypso.com)