Multiple Organizations - Windchill 9/9.1

[sdrzewiczewski]

Our system is currently only utilizing one Organization. It is becoming more evident that we need to split our implementation into at least two Organization contexts. What I'm wondering is:

• Can you move a Product/Library/Project from one Organization to another Organization?
• If you can't move a Product/Library/Project, can you move the contents from a Product/Library/Project to a new Product/Library/Project in a different Organization?

Thanks,
Steve D.

[AL_ANDERSON]

Unless you are planning to rent PDMLink to another company to use
concurrently with your own use, I don't think you want to make more than
one organization. As I understand it, you can't share users across
organizations, or libraries, or documents, or anyting.

Somebody please let me know if I've got this wrong.

Al Anderso







"Stephen Drzewiczewski" <->
08/18/2009 08:55 AM
Please respond to
"Stephen Drzewiczewski" <->


To
-
cc

Subject
[solutions] - Multiple Organizations - Windchill 9/9.1




Caterpillar: Confidential Green Retain Until: 09/17/2009



Our system is currently only utilizing one Organization. It is becoming
more evident that we need to split our implementation into at least two
Organization contexts. What I'm wondering is:
Can you move a Product/Library/Project from one Organization to another
Organization?
If you can't move a Product/Library/Project, can you move the contents
from a Product/Library/Project to a new Product/Library/Project in a
different Organization?
Thanks,
Steve D.

[sdrzewiczewski]

Al, from my understanding those are some limitations from older versions of Windchill, pre 8 or maybe even 7.

On my dev 9.1 instance, I was able to create a new organization, add a new product into it. When you create the organization there is a checkbox that allows you to either see users from all orgs, or just that organization, so I was able to add team members from another organization to it. I was also able to cut a file from a product in org 1 and paste it into a product in org 2.

[tweathe]

Al,

This can be done in 9.1.

Thanks,


Timothy J. Weatherford

TWeatherford, Inc.

3148 Beach Blvd

Cicero, IN 46034

www.tweatherford.com



866 936-2756 x 301

317 710 9747 mbl

419 821-5765 fax

Read our latest newsletter by clicking here

"If you continue to ignore PLM, you will learn about it from your biggest competitor"

[ZacharyAlexande]

It is generally a bad practice to move that kind of data from one Org to
another but in the recent Windchill 9.1 update it is possible using
Packages. Packages allow for large bits of information to grouped together
and sent to a different location, I believe within Windchill or externally.
Allowing access between users in the two Orgs is also another method that
could work but it would have to be done in a way to allow all the relevant
users in one Org to see the other.

On Tue, Aug 18, 2009 at 10:56 AM, Stephen Drzewiczewski <
-> wrote:

> Our system is currently only utilizing one Organization. It is becoming
> more evident that we need to split our implementation into at least two
> Organization contexts. What I'm wondering is:
>
> - Can you move a Product/Library/Project from one Organization to
> another Organization?
> - If you can't move a Product/Library/Project, can you move the
> contents from a Product/Library/Project to a new Product/Library/Project in
> a different Organization?
>
> Thanks,
> Steve D.
>
>

[sdrzewiczewski]

From my experimentation, you can Move, Cut and Paste between products/libraries/projects that reside in different Organizations. Packages are for a completely different purpose.

Our goal would be to take our mono-organization configuration and split it to a multi-organization system. Once that split is done, there is no need to share data between the organizations. Users, maybe, but not data, they each have their own libraries and don’t share any common cad parts.

From what I’ve seen testing this out today are issues/p.i.t.a.

· Can’t move a Checked Out item

· To create a product/library/project in an organization your user account must belong to that organization, so this would add a necessity for extra admin accounts for just myself to create the products in the other org… Not convinced of this, but this was my initial testing conclusion.

· Can’t move the initially created End Item of a Product to a new Product, no big deal if it’s not used, but some of our products use this end item in the product structure as the top level item. (not sure how many, but have seen it done at least once)

Steve D.

[HerbertMiller]

For sharing users across multi Orgs, create a Group at the Site level and then add users to that group and then you can add the Groups to products in multi Orgs. Herb MillerTWeatherford, Inc.3148 Beach BlvdCicero, IN 46034www.tweatherford.com 866 936-2756 x 305502 552-7179 mbl419 821-5765 faxRead our latest newsletter by clicking here"If you continue to ignore PLM, you will learn about it from your biggest competitor"______________________________________________________________________Confidential or privileged information may be contained in this message.Information may not be shared or re-used without prior written consent.

[sdrzewiczewski]

The issue I'm seeing is not adding users to a Product/Library, that
works fine.

My issues is adding a Product/Library Creator, the user must be a
member of that Organization. I haven't found a way around that.

Steve D.

Quoting Herb Miller <herbm@tweatherford.com>:

> For sharing users across multi Orgs, create a Group at the Site level
> and then add users to that group and then you can add the Groups to
> products in multi Orgs. Herb Miller TWeatherford, Inc. 3148 Beach
> Blvd Cicero, IN 46034 www.tweatherford.com[1] 866 936-2756 x 305
> 502 552-7179 mbl 419 821-5765 fax Read our latest newsletter by
> clicking here "If you continue to ignore PLM, you will learn about it
> from your biggest competitor"

[HerbertMiller]

I agree. There should be some kind of way to assign a Admin user to be a admin or creator in Multi orgs. Herb MillerTWeatherford, Inc.3148 Beach BlvdCicero, IN 46034www.tweatherford.com 866 936-2756 x 305502 552-7179 mbl419 821-5765 faxRead our latest newsletter by clicking here"If you continue to ignore PLM, you will learn about it from your biggest competitor"______________________________________________________________________Confidential or privileged information may be contained in this message.Information may not be shared or re-used without prior written consent.

[ZacharyAlexande]

This may seem overly simple, but you could set the one user to have 2
different user profiles, one for each organization? I believe this would
count as using only 1 license.

On Tue, Aug 18, 2009 at 3:33 PM, Stephen Drzewiczewski <
-> wrote:

> The issue I'm seeing is not adding users to a Product/Library, that
> works fine.
>
> My issues is adding a Product/Library Creator, the user must be a
> member of that Organization. I haven't found a way around that.
>
> Steve D.
>
> Quoting Herb Miller <herbm@tweatherford.com>:
>
> > For sharing users across multi Orgs, create a Group at the Site level
> > and then add users to that group and then you can add the Groups to
> > products in multi Orgs. Herb Miller TWeatherford, Inc. 3148 Beach
> > Blvd Cicero, IN 46034 www.tweatherford.com[1] 866 936-2756 x 305
> > 502 552-7179 mbl 419 821-5765 fax Read our latest newsletter by
> > clicking here "If you continue to ignore PLM, you will learn about it
> > from your biggest competitor"

[sdrzewiczewski]

You can move this End Item, you just need to create another End Item, set it as the Primary End Item for that Product. (Only applies to Products created prior to 9.0)

In Reply to Stephen Drzewiczewski:

· Can’t move the initially created End Item of a Product to a new Product, no big deal if it’s not used, but some of our products use this end item in the product structure as the top level item. (not sure how many, but have seen it done at least once)

[sdrzewiczewski]

I don't believe Profiles address which Organization the user is a Member of.

When you create a user on the Principal Admin tool, you define which
Organization that user is a member of. If you don't select an
Organization it is placed in the Unaffiliated User domain.

If you are not a member of the an Organization, you cannot be added to
that Organizations Product/Library/Project Creators list(s).

That is the issue that I'm trying to solve. If Profiles can do that,
I'd love to hear how.

Thx
Steve D.

Quoting Zachary Alexander <zalexander@productspace.com>:

> This may seem overly simple, but you could set the one user to have 2
> different user profiles, one for each organization? I believe this would
> count as using only 1 license.
>
> On Tue, Aug 18, 2009 at 3:33 PM, Stephen Drzewiczewski <
> -> wrote:
>
>> The issue I'm seeing is not adding users to a Product/Library, that
>> works fine.
>>
>> My issues is adding a Product/Library Creator, the user must be a
>> member of that Organization. I haven't found a way around that.
>>
>> Steve D.
>>
>> Quoting Herb Miller <herbm@tweatherford.com>:
>>
>> > For sharing users across multi Orgs, create a Group at the Site level
>> > and then add users to that group and then you can add the Groups to
>> > products in multi Orgs. Herb Miller TWeatherford, Inc. 3148 Beach
>> > Blvd Cicero, IN 46034 www.tweatherford.com[1] 866 936-2756 x 305
>> > 502 552-7179 mbl 419 821-5765 fax Read our latest newsletter by
>> > clicking here "If you continue to ignore PLM, you will learn about it
>> > from your biggest competitor"

[ZacharyAlexande]

I checked the Business Administrator Guide and it confirmed that you cannot
be a Creator unless you are a member of the Organization. Is there a reason
you cannot have the person you want to be a Creator in both Organizations be
a user in each of them?

On Tue, Aug 18, 2009 at 4:09 PM, Stephen Drzewiczewski <
-> wrote:

> I don't believe Profiles address which Organization the user is a Member
> of.
>
> When you create a user on the Principal Admin tool, you define which
> Organization that user is a member of. If you don't select an
> Organization it is placed in the Unaffiliated User domain.
>
> If you are not a member of the an Organization, you cannot be added to
> that Organizations Product/Library/Project Creators list(s).
>
> That is the issue that I'm trying to solve. If Profiles can do that,
> I'd love to hear how.
>
> Thx
> Steve D.
>
> Quoting Zachary Alexander <zalexander@productspace.com>:
>
> > This may seem overly simple, but you could set the one user to have 2
> > different user profiles, one for each organization? I believe this would
> > count as using only 1 license.
> >
> > On Tue, Aug 18, 2009 at 3:33 PM, Stephen Drzewiczewski <
> > -> wrote:
> >
> >> The issue I'm seeing is not adding users to a Product/Library, that
> >> works fine.
> >>
> >> My issues is adding a Product/Library Creator, the user must be a
> >> member of that Organization. I haven't found a way around that.
> >>
> >> Steve D.
> >>
> >> Quoting Herb Miller <herbm@tweatherford.com>:
> >>
> >> > For sharing users across multi Orgs, create a Group at the Site level
> >> > and then add users to that group and then you can add the Groups to
> >> > products in multi Orgs. Herb Miller TWeatherford, Inc. 3148 Beach
> >> > Blvd Cicero, IN 46034 www.tweatherford.com[1] 866 936-2756 x 305
> >> > 502 552-7179 mbl 419 821-5765 fax Read our latest newsletter by
> >> > clicking here "If you continue to ignore PLM, you will learn about it
> >> > from your biggest competitor"

[ptc-113113]

Would it be fair to say of the concept of Windchill “organizations” is WORTHLESS as executed by PTC, unless you can map it to corporate entities that will NEVER collaborate on a product or project?

just wondering….

Andrew Amsden
CAD\PDM Administrator
Midmark Corporation
937-526-8770

[LewisLawrence]

My interpretation of the intended use of organizations is to allow entirely separate entities to share the same Windchill installationhardware, Organizations allow you to do that without fear of anyone accessing anything they shouldn’t and makes management of the segregation easy from an administrative perspective. From that view point Organizations in PDMLink are far from worthless, and meet their intended use case.

I think the only issue is if you have users who need to be members of more than one organization, it seems they might need a user account for each. Admin user’s aside, if that is a common requirement, probably you shouldn’t be using organizations to divide your data and should invest more time in access control rules and better utilizing Products and Libraries instead.

-----

Lewis

[FeofilovIvan]

I too have porblem with 2 organization. If user have access to each of 2 organisatin and in each of them exist library with name "TEST".

When user clik on link library list he see to name and he can't understand which library corresponds to a organization. How I can can select with diferent color library label with same name?

Ivan Feofilov owner 4customizer.com

[#17]

Another user for Organizations is to set up a training and/or testing environement. In this case you will want (and need) all new usernames and dataset. This allows you to test custom workflows, OIR's etc and to set up user training scenarios (though resetting this data becomes troublesome).

~Dan Harlan

-----End Original Message-----

[patrick.chin1]

What issues did you guys have with working with multiple organization containers?

I see someone stated rules. How were these rules applied to have issues?

[patrick.chin1]

In response to my own question, the reason why I'm asking because there are cases where you apply OIRs and ACLs at all levels from SITE, Organization, Program, Project, Product, Library and Domain (folder) level for fine tuning, standardizing and globalizing your controls.There are cases where OEMsand partners may have their own information that specifically belong to them and your internal assemblies call out the the top assemblies. If you efficiently use Supplier Management, they can check into their ownorganization context and ORGID tied/associatedto thier own MFG or supplier part. Or you can call itin your internal ProE BOM without any conflicts of number and organization. Hence, full collaboration. Sometimes using the ProjectLink workspaces are confusing because ProE users just like to check in their top assemblies.

I haven't had issues with multiple orgs.