Hello everyone AND PTC,
The context:
Global numbering scheme for all EPMDocument. Our policy is to automatically allocate a sequential number to any new CAD file created. The EPMDocument get assigned the same number than the cad file without the extension. This is unique across our entire Windchill regardless of the context. Our business process is so that Number (Part number) is generated when creating the CAD. This number is then unique across all other systems such as ERP.
That is, if I start creating a new part for a new design in a project, the Number is allocated "forever".
When we were with Windchill 9.1, everything worked perfectly fine. We could create new CAD/EPMDoc in project, send them to PDM without the number being changed (users could not change it and the system did not change it all).
We upgraded to 10.1 M040 in June 2014. During testing we noticed that Windchill behaved differently. When an EPMDoc is created in ProjectLink and send to PDM, Windchill allocated a new number. This was obviously not good at. As this was the only issue with the upgrade, we went live as planned expecting our VAR to fix the problem.
After 18 months the problem is still unsolved and the only reply we have is that Windchill behaves as expected and it was a bug in 9.1
It does not make anything from a process point of view to change Number as data is moved from container to container when the same Numbering scheme policy is used across the system. In addition, you can imagine the issues this creates when you allocate a partnumber, and later on the system allocate a new one.
This creates overhead as one must remember what was the number so after sending to PDM, we can renumber to the original number. This creates more issues as our policy is so that users cannot play with NUMBER it is locked down. This implies that only admin can renumber.
Why has PTC change Windchill behaviour . Can someone explain the logic is not allowing an EPMDocument to keep the same number when being sent to PDM. If that functionality never existed, it would be different but it worked fine for 4 years with 9.1 and a few datecode update.
Thank you for your feedback and maybe some PTC program can pop in and explain the rational ?. I would love to hear their view on product life cycle.
I am Chris since I was born and changing status (baby, toddler, child, teenage etc...) and even container (changed 3 times countries) my number (first name and first name) never changed. So why is it now different with Windchill.
Thanks a lot
Best regards