×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Sharing/Updating Feature Palette Library

Sharing/Updating Feature Palette Library

Sharing/Updating Feature Palette Library

(OP)
We (3 users) recently stopped using Toolbox and have been sharing a library of parts thru the Feature Palette on our network. The problem we are having is that we can't update (add a configuration)a Feature Palette part if someone else has inserted it into an assembly and still has the assembly open.

Is there a way to get around this or do I have to ask the person to close their assembly just so I can add a configuration?

Thanks,

DT

RE: Sharing/Updating Feature Palette Library

The other user will have to close it. You can not change a part if it is opened by someone else, only if you each have your own copy of the part.

RE: Sharing/Updating Feature Palette Library

Try having the other person set the part to lightweight or temporarily suppress it in the assembly.

from (the City of) Barrie, Ontario.

Support bacteria - they're the only culture some people have

RE: Sharing/Updating Feature Palette Library

(OP)
That's what I figured...I was hoping since it was coming from the Feature Palette the part might be handled a different way than a regular part.

RE: Sharing/Updating Feature Palette Library

With Toolbox that's not the case on a shared TB enviroment. If your users haven't tried using the multi-user enviroment yet. You should have them try it. the guide is located at the SW website.

Regards,

Scott Baugh, CSWP
http://www.3dvisiontech.com
http://www.scottjbaugh.com

If you are in the SW Forum Check out the FAQ section

To make the Best of Eng-Tips Forums FAQ731-376

RE: Sharing/Updating Feature Palette Library

(OP)
Scott,
We were using Toolbox in a shared environment, problems, problems, problems. We are using a Novell Network (not our choice) and was working with Joy from SolidWorks to remedy our Toolbox problems. So we switched to using the Feature Palette and haven't had any problems.

CorBlimeyLimey,
The lightweight idea seemed to work...Thanks

DT

RE: Sharing/Updating Feature Palette Library

Didn't think of the lightweight....good to know
thanks

RE: Sharing/Updating Feature Palette Library

Quote:

So we switched to using the Feature Palette and haven't had any problems.

Except for updating the parts... right

Have you tried PDM Works?

I messed with it a little bit, but never got too into it.

We use eMatrix for our PDM, but also have 1000's of users world wide...

You might look into using a PDM so you can CHECK IN/OUT models and drawing and lock them, so you don't have to worry about who all has them opened or lightweight...

PDM Works, from my experience with it, should work pretty good for a 3 person team...

Good Luck,
Josh

When dealing with computers, there are 10 things you need to know: one, zero, and the rest is Binary.
-Josh S

RE: Sharing/Updating Feature Palette Library

(OP)
Scott,

Unfortunately PDM Works or any PDM is not an option. Management doesn't seem to think we need it. We've been using SW since 2003 and are just now starting to update drawings created using SW. It's becoming a little painful dealing with what's used/referenced where and what are all the drawings/parts/assemblies that could get changed. We are supposed to update drawings the way we did Autocad. Copy the drawing & part to a Pending folder. When ECN is signed off, move the drawing & part back over the original  files. It sounds easy, but lots of stuff can be affected. Oh well, we're doing the best we can with what we're given.

Thanks for your input,

DT

RE: Sharing/Updating Feature Palette Library

deek05,
We use PDMW and I don't know how we ever did with out it before. It is the best way to handle SW files. We use to handle the files the way you do, until there were too many. I had an engineer tell me before that it was not needed, do it like AutoCad. ACad thinkers live in the past. He no longer works with us. I believe a company with 3 or more users should use it.

RE: Sharing/Updating Feature Palette Library

(OP)
ctopher,

I agree, but how do you convince management who don't use SW that a PDM is needed? They just look at how much $$$ it would cost.

DT

RE: Sharing/Updating Feature Palette Library

(OP)
Josh,

The post about PDM Works I responded to was mistakenly addressed to Scott not you...

DT

RE: Sharing/Updating Feature Palette Library

Do you have users outside your facality deek05? If you did you could get the Advanced server and have those users connect to your server to view files. Or you could have users within your company do the same thing while the files are in the vault. You can put any file inside of PDMworks (As far as I know). Then it will track each file as it comes in and out. Advanced server is more expensive than just PDMWorks but it is going to vary on your needs.

Tracking files and keeping up with their revisions is a full time job. I did it for 5 years at one of my old jobs working with SW. It's not easy doing it by hand. That's what PDM is for. But like you Management thought that we didn't need it. I left before it got worse, don't I know they never presued it. But it's going to be a full time job for one of you to keep a running list of what's going on with what file(s). If Management doens't get something to help you out... Best of luck to you.

Regards,

Scott Baugh, CSWP
http://www.3dvisiontech.com
http://www.scottjbaugh.com

If you are in the SW Forum Check out the FAQ section

To make the Best of Eng-Tips Forums FAQ731-376

RE: Sharing/Updating Feature Palette Library

deek05,
I did a spreadsheet how long it took for 3 of us users to do changes and how big the files were vs how long and file size in PDMW. Enough to convince them.

RE: Sharing/Updating Feature Palette Library

(OP)
ctopher,
You wouldn't still happen to have the spreadsheet would you or even a screenshot?

RE: Sharing/Updating Feature Palette Library

No, sorry. Didn't think I needed it again. It was before I discovered this forum. If I come up with something I'll send it.

RE: Sharing/Updating Feature Palette Library

Deek05,
The way our management finally agreed to PDM Works was this:
Our Engineers (5 total) opened the top level assembly that they wanted to work on that day. Then when someone else (Designer, Engineer or Drafter) wanted to work on a part in any subassembly they would ask the owner to release the part by opening the part as read only. A few rebels would copy whole assemblies off to some place and work on them. When they where done, they would copy them back and sometimes overwrite others work. As a side note: The highest number of the same file found on the network was 27. Management saw enough of this happening and management put up the extra $500. We also got extra benefits from having SolidWorks Office Professional.  

Bradley

RE: Sharing/Updating Feature Palette Library

(OP)
Bradley,
Management sees it as only 3 people using SW and we never work on the same project at the same time. So their thinking is if the users don't work on the same project, what's the need for a PDM. They look at a PDM more for concurrent file sharing rather than managing SW files. We are just now getting into updating parts created in SW and it's becoming a pain moving/copying files around and hoping your not messing up any drawings or assemblies.

RE: Sharing/Updating Feature Palette Library

Deek05,
Looks like we should have started new PDM thread.
I know what you mean. Before PDM we had a drafter overwrite an Engineers work. The Engineer was never the same after that. We have had files overwritten after PDM, easy fix, because the PDM keeps very good history. Of course it should never have happened, but they were honest mistakes. At $85 per hour (company cost) for an Engineer, a few mistakes would cost more than PDM Works.

Bradley

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources