Hi, I am trying to figure out by myself what is a good folders' structure to use with PDMworks. From what I have read on this newsgroup, trying to reproduce a Windows folders' structure into PDMworks' vault is not a good practice. For example, the way we work now is that a top-level assembly is stored into one folder and all the different sub-assemblies are stored into their own sub-folders by types of equipment. Is this kind of system appropriate for the vault structure or should all the sub-assemblies be put together with the top-assembly? And If I choose to separate everything, when I check the top-level in, is there a way to make PDMworks place every sub-assemblies into their respective sub-folders? From what I understand so far (I could be wrong), it needs to be done manually. So then, isn't it more efficient to put everything together in one single folder and not try to create any kind of structure. I know you should use the custom properties and a basic Excel register to make enquiries. But then, what is the kind of folders' structure that should exist in the vault and what is the goal of this structure? I also don't understand why PDMworks gives the name "project" for what seems to be folders. Does it mean we need to work by projects? We don't. Could someone gives a simple example of a transition from a Windows structure to a PDMworks vault structure so I can start to understand how to set up things. Even though a set-up is really company-specific, I know there is general guidelines and I would like to hear about them. I don't have preconceived ideas of how it should work. I just want to have the picture of a good implementation scenario. SW2005 SP3.0, PDMworks2005 Thanks JC
- posted
18 years ago