I'm trying to decide how to due manuafacturing effectivity. Engineering will "Release" a drawing but it does become Manufacturing effective until they have implmented the changes which may take several months. I can do this with a state but I thought maybe a checkbox and date field would be better. The shop floor would not see it until it was checked.
Any other alternatives or suggestions?
These are for just the PDF viewables of the engineering drawings, not the native files. We are considering not revision controlling these files, instead we are putting the revision in the file name. There are several reasons for this:
If I add a "Released to Mfg" state, I can control it by the state.....I was just trying to see if I could accomplish it without added another state. The state might be the best way though.
If you are creating .pdf conversions of Solidworks drawings then you could easily put those files in a totally seperate workflow, and use a folder structure to determine who could see what.
Our company is implementing a similar process, for all the reasons you listed.
We have theorized another way of doing this that I didn't want to mention so could see what others thought - and its similar to some of the other posts.
You could have workflow state change loops that generate the pdf and put it outside the vault - with us, manufacturing doesn't really 'need' to be logged into the vault, they only need to see released drawings. Only certain groups will have the rights to use this state change loop, and it becomes basically their approval - if the pdf is there, it is released or accepted. Once Mfg changes the state to accept and make the pdf, it auto transitions back to the original state.
I think you could even add a serial number to the pdf filename to keep older verison (a little dangerous, but for some companies its ok).
This will be relatively difficult. The right way would be write an Add-In to handle it.
I have another concept that I have NOT tested so it might not work at all.
You will need two or more workflow states, each state has a set of permissions that determine who can see it.
You make the transitions to these states automatic. Then you create a dispatch action that blocks all the transitions that you do not want to happen based on the check box variable. You need SEPDM 2009 to do this.
The problem is if the dispatch action doesn't work then you will have two automatic transitions which will likely cause a problem.
You could try it though but I suspect it won't work.
Retrieving data ...