Interesting to see how other people solve seemingly common problems.
Our approach :
Every design, big or small, starts with an assembly with skeleton.
Designers develop their ideas on the skeleton. Only when the design board
approves the concept, the first parts are derived top-down from the
skeleton.
Regards, Hugo.
<ejhlti@verizon.net> wrote in message news:233209@datamgt...
>
> There is a little trick we use in Intralink 3.X to duplicate objects.
> Basicaly we design only object "A" upfront, if object "A" progresses to an
> assembly, we work on the later components and assembly at a later date but
> still use the original object A.
>
>
> Here is how it works:
>
> Lets say we have a "generic" assembly
>
> A.prt
> B.prt
> C.asm
>
> User only at first duplicates object A.prt, so now we have
> A_new.prt If the project progresses to an assembly this what we
> do:
>
> 1) Make sure A_new.prt is checked in and not in WS.
>
> 2) Check out the "generic" and dupliacte all objects so we now have:
>
> A_new.prt
> B_new.prt
> C_new.asm
>
> Since A_new.prt is already in the CS, it reads "same name exist" in the
> WS. By selecting A_new.prt in the WS and using the update function, the
> "real" A_new.prt in the CS is now incorporated into the assembly. We use
> this quite often on many generic models. It
> saves alot of time in that we only design A_new.prt upfront and can
> later work on B_new.prt and C_new.asm when needed. The alternative
> is to duplicate all objects upfront which can create many not needed parts
> and assemblys.
>
>
