This sounds like a profoundly dumb thing to do, but we are
attempting to document designs that went out the door before we
began using SW and PDMW.
This is part of an effort to demonstrate to the extended enterprise, the power of SW and PDM to track what customer has which version of a product.
A current part design, and a single previous iteration of the part are now checked in.
Can I create an assembly configuration, and tell SW to use an earlier part revision from the vault ?
Thanks in advance for any advice that you can offer.
This is part of an effort to demonstrate to the extended enterprise, the power of SW and PDM to track what customer has which version of a product.
A current part design, and a single previous iteration of the part are now checked in.
Can I create an assembly configuration, and tell SW to use an earlier part revision from the vault ?
Thanks in advance for any advice that you can offer.
Additionally, once the assembly is checked in, and then when being checked back out, the user has to know that they must click the "since revised" part in the check-out table, and select the previous revision. So this effort is unacceptably susceptible to risk of human error, IMHO.
I was hoping that I could do this without rolling back the "since revised" part, and I pulled it off, but it isn't fool-proof. This could turn into a major mess in a hurry.
I'm going to try to talk my boss out of using this approach for documenting old design revisions that went out the door prior to our SW and PDMW implementation. I finished the first of the three designs that he wanted to address. He now has what he needs for demomstration purposes, but I hope I can talk him out of continuing this effort, because this is not a "best-practice".
Kenneth, thanks for posting. I appreciate the benefit of your experience.