With version 26.2, Stages serves as your process backbone for AI in engineering and beyond. While Stages 26.2 continues to provide process knowledge for human users, it adds new features to do the same for AI agents. With these new capabilities, AI agents can be governed to execute their tasks according to the organizational standard processes and in compliance with standards and regulations.

MCP and Use Cases

Please note, that Stages 26.2 is not yet a Long Term Support (LTS) release, but will become LTS at a later point in time. Until then, Stages 7.12 will continue to be the LTS version.

Release 26.2 is currently only available for Stages Managed Service instances. On-premise usage will be made available at a later point in time.

When process modules are integrated into other workspaces or whole processes or single elements are copied into new workspaces, the creation of process interfaces is now solely controlled through workspace collections. Only processes in any workspace collection of the current workspace are being searched for potential process interface target elements. If a target is found in multiple workspaces, multiple interfaces are being created. If a workspace is updated that is not contained in any workspace collection, no process interfaces will be created.

The group and common elements workspace settings do not have any influence on the process interface creation anymore.

As a result, process interface creation should be much more consistent, transparent, and easier to control.

See here for more info on how to transition to the new mechanisms.

MCP (Model Context Protocol) has established itself as the universal way to connect LLMs (Large Language Models) and other AI systems with data sources. It's a common way to integrate Stages into your enterprise chatbots, so that your development processes are taken into consideration in those systems.

Through our new MCP Server, AI systems can access process data managed in Stages for various purposes and use cases. You can therefore adjust the MCP configuration to control the amount of information revealed via the MCP interface.

See here for more info on MCP with Stages.

Java SDK has been upgraded to the latest LTS version 25.

The ability to export a process description for translation through external tools is not yet supported with this release. The feature will be supported in a future release upon customer request.

In the meantime, the AI-assisted translation is available for automated translations.

The “transferMappings” script that copies compliance mappings from an older reference model version to a newer one is not available yet, but will be in a future release.

Due to changes in PTC partner agreements, the integrations with Windchill RV&S (ex Integrity) and Codebeamer are not yet included in this release.

They are planned to be included in a future release.

The new Use Case element subtype provides a modeling capability to

tbd

With this release, we share adjustments to our standard metamodel strategy. We strive to support new modeling requirements more quickly while minimizing the number of delivered standard metamodel variants.

Read here for details of the new strategy.

We also made new reference models available to manage compliance.

Please reach out, if you are interested to use one or more of the following standards in Stages.

• tbd

See here for the full list of available reference models.

Please let us know if you have additional compliance requirements. Our teams are ready to implement them for you.

Version 26.2 is currently only available on Stages Managed Service instances. On-premise usage will be made available later this year.

Please contact our customer care team to request an upgrade of your Stages Managed Service instance.

Note: all process release automations have to be finished before an upgrade can be performed.

For topics marked with *: please contact your product consultant for more info on how to integrate those enhancements into your configuration.