cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X

What is the different between a product and library at a system level?

DarrenStorey
7-Bedrock

What is the different between a product and library at a system level?

Apart from the omission of End Items in Libraries, the fact that Libraries are of a different object type to Products (in name at least) and separate listing in the UI, are there any other important differences between products and libraries at a system level?


We consider Libraries to be place to put engineering data which is intended to be shared by multiple products, but does not itself make up a product. I would image this approach is not uncommon. Currently however we are struggling to find a way to stop people using products also like libraries. We do not want information from any product to be used in anther other product.


While use of library data in products is permitted, in our organization product to product reuse is not. Does anybody have any ideas how to prevent reuse of information between products, or is willing to share some thoughts on this topic?


Regards Darren

1 REPLY 1

I’ve received a few direct responses on this, so I would like to clarify further.


We are a design consultancy, each product contains data which quite frequently is not our own intellectual property and we are in fact legally forbidden from reusing. When we do own the IP we often don’t make or buy the hardware or have direct responsibility for the finished product. The data is therefore archived in the product “as supplied” to client for ongoing support and legal data retention requirements.


When we do not make/buy it, but do own the IP and want to reuse, then we are only really interested in saving the effort of redesigning and care not for reusing the part number. Frequently the number is client specific anyway. In such cases, reuse amounts to making a copy of the data in a new product with a new number.


When reuse of number is important and appropriate then we use Libraries. Standard fasteners etc being obvious examples.



  • We could potentially restrict download to designers who are working on each specific product via ACL, but that amounts to many products per designer, hence would not really work for us.

  • Product specific logins would also be unmanageable too.

RegardsDarren

Top Tags