Skip to main content
F
Foolish_Monkey4-Participant
4-Participant
June 12, 2025
Question

Windchill org split

  • June 12, 2025
  • 2 replies
  • 304 views

Reference topic: https://community.ptc.com/t5/Windchill/What-are-pros-and-cons-to-set-up-multiple-organizations-over/m-p/166436#M19670 

 

Do you think

"...the migratory configuration to accurately configured multiple organizations are not worth the expense in all likelyhood.

Out of the box product and library templates are the worst enemy for transition to multiple organization system."

still applies?

 

We are in a company of 6 (5 in Windchill) companies. We have 1 org and 5 products (where each product is a context and each one is for a single brand).

We realistically could be split into two groups. We are starting to encounter configuration issues where one group really needs certain settings only available at the org level. Those settings conflict with the other company.

I have proposed splitting us at the Org level. I am a young Windchill Admin but I have read a lot of the docs. We are on 12+. It looks conceptually simple to split off a new org.

 

What could I be missing that makes this org split so difficult and a warning? Has it changed in 10 years?

2 replies

Catalina
CatalinaCommunity Manager
Community Moderator
June 25, 2025

Hi @Foolish_Monkey 

 

Thank you for your question.

 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

 

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

 

Best regards,

Catalina | PTC Community Moderator
avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
June 25, 2025

I think most of us operate with a single org. Perhaps the original concept from PTC never panned out or they opted for simplicity over complexity. What I remember when I was starting out is that you could effectively have multiple entities operating in a single system and not see each other. I think there is an option (but not sure its hard coded this way) that Parts in one org can be unique to that org. That means you can have part XYZ in one org and the other have the same part XYZ and those parts be different. Obviously, workflows, access rights, etc are split and can be different at the org level.  Add in the complexity of file vaulting and locality, adding multiple orgs might be just one more thing to deal with. 

When I re-read this post earlier today, I thought of the larger reason why most installs are single org. For many, the ultimate aim is to have collaboration, data sharing and commonality across sites. Yes, when we brought in new sites, there was that period of integration where they might want a slightly different workflow or access rights. Perhaps their roles were different or CAD system. That can be accommodated easily in a single Org. But, those differences can be broken down over time and in the mean time, you are leveraging the common parts and a methods. Throw in the business changes that occur very often of sites being bought, sold and merged and you want to be as flexible as possible when designing your PLM system.  Just my 2 cents for what its worth.

    Terms & ConditionsCookie settingsAccessibility statement