Let's see. I'm sitting in front of a workstation with about ten gigabytes of data. It stores all manner of projects, from pure mechanical to pure electronics

Let's see. I'm sitting in front of a workstation with about ten gigabytes of data. It stores all manner of projects, from pure mechanical to pure electronics as well as software-only products. They are organized quite well by product or project as required. Each product lives in a stand-alone directory that is fully self-contained. Need to work on that project on another workstation? Clone it or fork it onto that workstation and you have all files relevant to that project and nothing else. This method works very well and has been in use for quite some time across multiple workstations, operating system revisions, tools and software revisions as well as a number of engineers. The only effort required in order to maintain this system is to abide by common sense agreed-upon directory structures. For example, if working on an electro-mechanical project, the fasteners might go in the "Fasteners" directory under the "Mechanical" folder and the embedded software might go under "Software", which, in turn, lives within the "Electronics" directory. Not tagging. Nothing that can get lost or royally FUBAR'ed if tags are lost or corrupted, etc. Just a darn simple file cabinet analog that works very well and is perfectly usable, easy to understand and fully searchable. Don't get me wrong, I like tags. They are great for certain applications. I just don't see them as practical for anything I've ever touched in terms of project or file management.