Let me start off by saying I've been reading some pretty interesting threads in here on getting shop floor users in EPDM. We are starting down that path to replace a network drive that contains duplicate pdf copies of 2D drawings. Our plan is to have a search card that allows the users to search by part number only for the part they are machining or finished product they are assembling. We are doing this because there are complaints that trying to navigate through a folder structure is too difficult and time consuming for the guys on the floor (not my words, operations).
Anyway aside from the search card what else has been successful for you folks and on the flip side what hasn't worked?
How do you ensure the guys on the floor are working with the correct released print? I realize I can make it clear the local cache on log out but the PC's n question are rarely if ever restarted. It sounds like some people are having success with a script ran by windows task scheduler to clear the cache on a regular basis and that helps.
How are you dealing with files that are currently involved with an ECN? Do you make them disappear from view with workflow permissions or do something else? When we do make certain states unreadable by the shop floor what boxes do I need to check to enable them to see the last released version of the file?
I'm just looking for ideas from the crowd here on what worked for you and what didn't.
I would make sure they are their own "group". Set the permissions so they cannot move, delete, etc. Only read. In the group permissions, you can always check the box of "always work with latest version" as well. (under group/settings/reference dialog).
Our prints are attached to the "Job" that the floor sees through our production software. So we generally do not have the floor going through PDM anyways. That way we know they have the "latest" and our Production control people take care of all that. If a drawing changes mid "Job", (all departments notified through PDM Notifications), then that job is cut short (if cant be reworked) and new job is created to new rev. Something of that sort.