My company intends to invest in the EPDM Software.
We are manufacturer of robotic machines and special machines for pharma and cosmetic laboratories.
I am in charge of drawing up a " Specifications ".
Before all this, I would have liked to know how far we can push EPDM.
Know how can you manage the versions of drawings automatically, possibility or not? Nomenclatures with personality properties? Anything that can be interesting and everything it can do...
I would have liked to have a user opinion, and examples of how it works in other companies.
Additional tips and interesting things to integrate to make EPDM a really great tool, in terms of use.
Thank you in advance for your help.
I've already managed to install a number of things in the file management between part numbering, commercial products... and a rather interesting nomenclature with interesting custom properties.
But as we are all in search of perfection and this site could allow us to find together by exchanging solutions and interesting avenues.
I sincerely think that a community of users could have interesting examples and cases to communicate and that it could be of interest to more than one. I searched a little on the internet for testimonials and style of use but without much success.
However, I know that Axemble, which is the service provider that I think we will choose for the integration of this software, will guide us as best as possible.
To help you understand the use, you will find attached a POWERPOINT presentation that I made at the time to explain to neofites (my leaders at the time!!) what does the EPDM stand for?
I think this will give you some answers on the functioning and the (non-exaustive) capabilities of the EPDM.
If you have any other questions, don't hesitate, we're here.....
Very nice flegendre presentation (did you sell it to axemble?) ;-)
Joking aside, do you store all the exported files at each revision index (one file at revision A, one at revision B...) or do you overwrite the obsolete files?
If you overwrite files, how do you deal with the problems of windows access rights that block the writing of a file when a user has already opened the file?
Our US site puts links to pdfs in its CAPM, and the link must always point to the right version (so the latest one because we don't recreate an article when the revision changes). This allows CAPM users to have access to the plans with a single click.
To avoid errors/omissions, the easiest way for us is to have a pdf file with the same name always stored in the same place (but then we cannot use the automatic generation via EPDM because it will not work the day a user has a pdf file open on his computer).
I had thought of using a buffer directory where EPDM puts its files and a replication tool to sync the user and the buffer directory (which allows you to overwrite the obsolete file as soon as the user no longer has it open on his computer) but it seems cumbersome to me.