Hi,
When working with the piping elements, we always have to refer to a routing library that we have on one of our network's hard disks for the pipe and elbow files. On the other hand we are using PDM for the rest of the project and all our other pipe elements are stored in the PDM server. The problem is that we cannot refer to the PDM server when assigning a library to the pipe and elbow elements.
Is there any way that will enable us to only work with the PDM and place our pipe and elbow elements there?
Thanks!
Guillaume Salomons
When working with the piping elements, we always have to refer to a routing library that we have on one of our network's hard disks for the pipe and elbow files. On the other hand we are using PDM for the rest of the project and all our other pipe elements are stored in the PDM server. The problem is that we cannot refer to the PDM server when assigning a library to the pipe and elbow elements.
Is there any way that will enable us to only work with the PDM and place our pipe and elbow elements there?
Thanks!
Guillaume Salomons
We do have customers that work with routing and PDM with no issues at all. I'm no expert on PDM but I have used Enterprise and set it up with the routing library in the vault with no problem, sadly I no longer have that setup. I'll have a look around and see what I can find out for you.
Regards
Andy
Make sure everyone always has the base Pipe and Elbow parts checked out in their local PDMWorks Directory. If you make a change to them make sure everyone updates there files.
If you have any library parts that are assemblies, you can't drag them out directly from the vault unless you already have the parts that are used in the assembly local, since PDMWorks will only copy down the top level assembly when you do a drag and drop.
The library is set up as non rev controlled. My library is on the network and set read only for all but me. One person may make changes. Clean as a whistle. If I were to keep the library in the vault I would have so many secondary revs on my elbows per use it would be crazy. Remember, PDM saves a version of every rev. Copying projects would also be more complicated.
This works great for me. I see no real reason to have the library in the vault.
My $0.25. (inflation you know).
We looked at keeping our piping library outside of the vault but decided that since Piping can make up a large portion of our Assemblies having to open the files across the network would go against one of the main reasons that we started working with PDMWorks, having all of our files locally to increase speed.
No you can't do what you are thinking. PDM will not let you work with pipe the way other files are used. We have the pipe part on a local network and check out the elbow we will be using on the route. We check it out without taking ownership.
Make sure if anyone updates the elbow that they don't change an existing configuration.
Andy, could you please check this matter with some of your colleagues that work with PDM if there is any possible way?
Guillaume
Yes, I have already had some feedback from the PDMW Enterprise people and they say it shouldn't be a problem. Though there are some general issues with libraries that they are currently working to address. Some nuisance messages etc.
I'll send another query to the workgroups guys.
Cheers
Andy
The attached document describes the recommended setup for use of routing and PDMW Enterprise.
For PDM Worgroups the setup is very different. Workgroup can be setup to use the notion of a non-revision managed file where only the metadata is placed in the vault, not the actual part file.
I would suggest that you contact your reseller for help with this.
I hope this helps.
Regards
Andy
Attachments