Solidworks – Creating/Using a Custom Design Library

3D Design Library
1

Hello

As part of my use of Solidworks 2015 SP05 (x64), I draw standard or non-standard parts and standard or non-standard assemblies.

Final wish:

  1. Be able to drag an STD element or an assembly of STD and non-STD parts
  2. Create a new assembly with a different name from the assembly in the Design Library.
  3. This new assembly will have STD parts and non-STD parts depending on the original assembly. This new assembly will update automatically if the so-called STD parts are updated.

Questions :

  1. If I have an STD parts library in a specific location (= design library),

    Can I create an STD and non-STD parts assembly?

  2. If I decide to create an STD assembly of STD parts from my design library and other non-STD parts specific to the assembly (which may be editable depending on the project),

    Can I create a new assembly linked only by STD parts by dragging my STD and non-STD parts assembly?

    If I can't, should I use Solidworks Explorer ? If so, will this assembly keep a link with the so-called STD assembly?

Is a design library feasible without PDM and without equations between parts in order to avoid any loss of equation ?

 

Here's an idea of the steps in the future process with the Design Library:


bibliothequeconception2.jpg
1 Like
2

On an assembly you have x standard parts registered with 1 name

You can change parts in this assembly and therefore also change its name

and you'll keep all the links

@+

3

@GT22: Yes, you keep the links with the so-called STD and not STD parts.

For non-STD parts, I want to remove the link so that I don't change the original STD assembly.

That's the complexity of my approach.

1 Like
4

but if you save your new assembly

you don't change your assemblies created in standard

you have 2 assembly files

1 standard

1 standard modify therefore more standard

@+

5

@GT22: You don't understand what I'm getting at.

      For example, the STD assembly is called PPI0012A.Il is composed of 4 STD parts (parts from REXNORD)  and 8 non-STD parts named in order of creation PPI0012A-P01 --> PPI0012A-P08

I want to start from PPI0012A, I drag from my PPI0012A library into my new assembly that I will then save as A003 (in my project, this is the 3rd assembly I make).

If I change the PPI0012A-P02 parts in the A003 assembly then the part will change in the STD PPI0012A assembly. But I want to avoid this link.

On the other hand, if I export with Solidworks Explorer then I lose the link of the 4 STD REXNORD parts.

Do you see what I'm getting at?

Yours truly .

6

@GT22: You don't understand what I'm getting at. (if I think ;-))

      For example, the STD assembly is called PPI0012A.Il is composed of 4 STD parts (parts from REXNORD)  and 8 non-STD parts named in order of creation PPI0012A-P01 --> PPI0012A-P08

I want to start from PPI0012A, I drag from my PPI0012A library into my new assembly that I will then save as A003 (in my project, this is the 3rd assembly I make).

If I modify the PPI0012A-P02 parts (if you modify parts in this assembly then you should in principle change its name PP10012A.1) in the A003 assembly then the part will change in the STD PPI0012A assembly. (so it won't change the assembly PP10012A since it's called PP10012A. A) 

Is it clearer ?.

@+

 

7

I don't know if I understood the need,

 

Ability to "lock" the file in read-only mode (standard ASM).

So if modified, it forces the user to "save as".

 

Possibility also to create DOTASMs to simply make "new file" by the user.

8

@ WG 22: Thank you for your quick answers anyway! :) No, it's not really clearer.

If I modify the PPI0012A-P02 parts (if you modify parts in this assembly then you should in principle change its name PP10012A.1) in the A003 assembly then the part will change in the STD PPI0012A assembly. (so it won't change the assembly PP10012A since it's called PP10012A. A).

 

If I edit PPI0012A-P02 in A003, it doesn't mean that I automatically change my PPI0012A. TP? Because A003 may be a "one-shot" project (<> STANDARD) and specific to this type of client, so there is no need to evolve PPI0012A.

My need is to change PPI0012A-P02 which will become A003-P02, for example.

@ Olivier42 : 

Ability to "lock" the file in read-only mode (standard ASM). Yes, that's it

So if modified, it forces the user to "save as". YES and non-standard parts must register under as well.

Possibility also to create DOTASMs to simply make "new file" by the user.

I don't know what exactly a DOTASM is.

For example, I make desks and office chairs. i.e. they are assemblies of STD manufacturer parts and STD and non-STD internal parts.

Option 1 -> When the user wants to take the standard chair, he takes the model as it is.

Option 2 -> If the user wants to change the chair for an X-Y reason, they should be able to take the model and change only the non-STD internal parts and the chair model remains unchanged.

Option 3 -> The user wants to update one  of the standard desktop templates. It creates a new model and keeps/creates/deletes links of STD and/or non-STD internal manufacturer or internal parts.  

9

your "standard ASM" you save it on the network, then you lock the files (by windows, right click, properties, read-only).

(if you have to make it live, it's always possible, but don't forget to lock the file afterwards).

 

your "special / custom ASM" you make an ASMDOT, from your "standard ASM" (save copy, type ASM DOT),

that users will be able to access by doing "new file"

(create a special "basic part" folder to put it in, and not mix it with the empty parts, and in system options file location add this new folder)

 

And you can also apply this whole principle to PRTs with PRTDOT

(e.g. a chair, a table, etc...)

The user will only have to "replace component" in his "special ASM",

and in addition it should not lose in ASM constraint, or MEP rating.

(DOT files will be made from the original ASM or PRT).

 

See screenshot

(but the list is not very large, because I have only recently started in this company).


capture.png