Skip to main content
D
ddemay1-Visitor
1-Visitor
August 16, 2010
Question

Project, Products and Libraries - how do youdefine their uses?

  • August 16, 2010
  • 9 replies
  • 2767 views
Also to add to this ...Products, Projects, and Libraries can now be soft typed with attributes editable in the OOTB UI meaning you could associate a product template per product soft type - even name them the same.

You can edit the JSP for the product list page (where you see all active or guest member listing of products) to make the showcustomviewlink=true and you can have your product or other container soft attributes displayed.

Anyone who wants to use this on existing products, email me for directions.

Product templates are good for kicking off different configurations, including domains, just be mindful of the level of work to possibly reconfigure existing data should the need arise.

Multi organizations can also be used and can be configured to disallow hosting of products or other containers. Your user's Org I'd ref in principal admin can be used to associate users together and also add them as members to a container, but automatically be read only without further ACL access. This gives you abilty to use guest role to allow different access configuration if desired.

Dave


Sent from my Verizon Wireless BlackBerry

9 replies

D
ddemay1-VisitorAuthor
1-Visitor
August 17, 2010
I totally disagree with one product per engineering group. Overtime you or someone reading this thread may find themselves moving items to new products to solve a business problem.

It is best to find a way to break things down further unless you are such a small comany or do not use Windchill exclusively to manage all of your engineering and or manufacturing data.

if you are happy with that configuration as a solution, great. In my case, I'll be supporting such a large diverse system, it would be a nightmare to go with too few as much as it would be to go with too many. Products and containers are not just about the team. Sometimes it's replication, searching, reporting, to name a few.

One big bucklet causes you to lose functionality. Especially with larger datasets.


Dave




Sent from my Verizon Wireless BlackBerry
R
RussPratt8-Gravel
8-Gravel
August 18, 2010

There is no one answer to this question. The "scope" of any given Product or Library may vary considerably based upon the business needs of an organization. The critical key is to design a solution that creates a Products and Libraries with a balance of the three primary aspects of context design: People, Data, and Processes. The intersection of these three "sets" is where you will find logical Product &Library definition. See the attached image.

One thing to remember is that you should never attempt to use Folders to try and define "Sub-Prod/Lib", This will only lead to problems, as folders only address the "data" aspect of design.

Russ

    P
    Pascal_Brunet14-Alexandrite
    14-Alexandrite
    January 18, 2023

    Thank you @RussPratt. I found many comments about Product definition but yours is probably the most interesting one, even after 13 years !

     

    I like the powerpoint slide you attached, do you have another one more up to date ?

     

    Best regards,

    Pascal

     

     

    R
    RussPratt8-Gravel
    8-Gravel
    January 18, 2023

    The most recent version is in a recently retired Portfolio offering.

    https://ptc-internal.workrails.com/item/40ff9401-fc0b-4fc2-b562-ac77e1ea6e0e

     

    D
    DanielReid12-Amethyst
    12-Amethyst
    August 18, 2010
    This is very helpful to keep in mind. Reading the other updates there
    are lots of good solutions for the specific company and need.

    For example, Kenworth and Peterbilt have one "product": a truck (with
    thousands upon thousands of options). It certainly doesn't make sense
    for us to use just one Product container though. Good timing too as
    we're revisiting a layout that was dominantly defined by Data.

    Thanks!
    Terms & ConditionsAccessibility statement