Content Center library vs library folder

[Anonymous]

What are the pros and cons of using a custom Content Center library vs a project-defined library folder? From what I understand one basic idea is that you enforce a homogeneous material definition on all family members, but anything else?

[johnsonshiue]

Hi! I am sorry I am not sure I understand the question. The two, "Content Center Library" folder and "Library" folder are for different purposes. I am not sure there is pro and con here.

Many thanks!

[Anonymous]

which "different purposes"?

Thanks again

Joe

[johnsonshiue]

Hi Joe,

CC Library folder is to store all CC parts (standard or custom). You can certainly place custom CC parts elsewhere but you may lose the editability like change size.

Library folder is a general folder to store all reusable components. The folder is considered read-only in an active project. The files stored there cannot be edited or updated. They are treated like read-only files.

Many thanks!

[Anonymous]

So the basic idea with content center (as opposed to library folder) is to store only some "relative geometry" without enforcing even fixed sizes (as in "normal" model files, like the ones placed in library folder?

[SBix26]

Content Center allows the user to choose from a large number of discreet sizes of a part.  For example, a hex head bolt could potentially be many hundreds of different combinations of size, thread pitch, material specification, length, surface treatment/coating, etc.  A library folder would need to have all of those parts available unless you're going to model them individually as needed, whereas the Content Center has the basic "recipe" and a table of possible combinations and can produce the exact variant required when called upon.

There are lots of different things in the Content Center, so it might be worth your time to browse through it and see what might be useful to you.  Inventor has the tools to create your own content, or to copy and modify existing content.

---

Sam B
Inventor Pro 2020.0 | Windows 7 SP1
LinkedIn

[Anonymous]

OK, now it begins to make more sense. But how are these "discrete sizes" different from iParts?

Thanks again

Joe

[SBix26]

They are very similar to iParts; in fact, iParts is one way to create content for the Content Center.  I can't tell you all the differences between iParts and Content Center families, but one important difference is control-- since an iPart factory is just another file, anyone can accidentally (or otherwise!) mess it up, delete it, move it, etc.  Content Center is better controlled.

I think there are some other benefits to CC over iParts, but I can't recall those at the moment.  Maybe @Mark.Lancaster can pop in here and fill in the gaps.

---

Sam B
Inventor Pro 2020.0 | Windows 7 SP1
LinkedIn

[Anonymous]

Ok, now it begins to make even more sense :). I browsed he prepackaged content center a while back, and I think that the prebuilt 3d solids are very handy, but I could never wrap my head around what the idea was with the library folder vs content center library. If Mark doesn't sop by I will accept your answer.

[Frederick_Law]

CC is available to all Inventor user.

You need to share iPart with anyone that will use your assembly.

You'll still need to Pack and Go CC files.

CC Library contain definition of all CC parts.  It doesn't contain parts.

CC parts are stored in "Content Center Files" Folder.  This is like a library folder in project.

[Mark.Lancaster]

@Anonymous 

@SBix26  thanks for tagging and inviting me to this party..  Sorry I'm a little late.. 

A couple years ago I did a presentation on Content Center vs Library..  Granted it was geared more toward the setup process but I did cover the pros and cons of the library vs content center concept.   I have attached a few slides for additional information and perhaps that will help answer some of your questions.  Let me know if you have questions

[jtylerbc]

I would add that there is no reason why your setup has to be based entirely on either option.  The best solution may be a mix of the two.

At my company, we use Content Center for "general" hardware (bolts, washers, nuts, etc. where we aren't specifying a particular manufacturer), and for structural steel members. 

We use library folders for most models of purchased components where we specify a manufacturer.  Some of these are iParts that we either modeled ourselves or downloaded and modified.  Those theoretically could have been added to Content Center, and I simply chose to keep them separate as an organizational convention.  However, a large portion of the parts in the libary are individual models obtained from the supplier, which would not be very conducive to adding them to CC.  And a few are actually assemblies, which are not possible to add to CC.

[johnsonshiue · Accepted solution]

Hi Joe,

I guess your question is about the difference between publishing iPart to CC or keeping iPart in Library folder. There are indeed differences. Certainly, they are all "library" parts with pre-defined definitions. Let me list a few differences and you can see which one fits your need better.

CC: Each part is an unique part, belonging to a CC family. These parts can be placed independently or as custom content for Frame Gen, Tube&Pipe, Cable&Harness, and Bolted Conn workflows. You can manage the families within one CC library or multiple libraries. You can also have them stored in Vault and use remote content.

But, CC is only limited to parts; assemblies are not supported.

iPart (iAssembly) in Library folder: You have to manage iPart (iAssembly) on a per factory basis. Each factory is independent, not supposed to have relationship or dependency. iPart (iAssembly) factory dictates its members. There isn't much you can change on an iPart member file (except custom iPart). Everything should be defined on the author table. To extend the factory, if you edit the iPart (iAssembly), all members may need to be updated unless the change is limited to one particular member.

Many thanks!

[Anonymous]

Thanks, I also completely forgot about the various subsystems (frame generator, duct and pipe, etc) that can _only_ use material from content center

[johnsonshiue]

Hi Joe,

One additional point to the Library folder. It is not limited to iPart/iAssembly. You can put any pre-defined parts or assemblies in the folder for reuse purpose.

Many thanks!

[Anonymous]

Yea, I got that far. The only other thing I'm unclear on, can you make a library folder managed by Vault?

[johnsonshiue]

Hi Joe,

Absolutely! Although I am not Vault expert, I am sure this is doable. All folders under Inventor Project can be managed by Vault.

Many thanks!

[ABHUT_9090]

Hello,

CC is only limited to parts; assemblies are not supported. 

Is it possible now or not yet ?

Thanks

[SharkDesign]

CC is only parts.

Library can be anything. 

[johnsonshiue]

Hi! Inventor CC Library is still for parts only. It has not been extended to assemblies. I have not heard any near-term plan to make it happen.

The request is definitely legitimate and it would be a powerful workflow. However, there are technical challenges. For example, at the moment, there is still no way to create an iam template with all referenced parts. When you start from scratch, everything will need to be redone.

Many thanks!