Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X
I agree totally withMike,
The Promotion Request was really setup for Pro/Intralink integration (ProE CAD only). Using Change Notices and Change Activitiy Packages/Implementation Planwith Affected (From) and Resulting (To) is the key. You don't have to use individual workflows per WTPart and EPMDocument. Just have the ECN review process set the state of the entire package. You can even have the affected go to obsolete after some effectivity or immediately and the resulting go to Released State immediately.
The only issue I have is the search capabilities of finding objects when adding objects to the affected and resulting. I really hope that PTC adds the advance search, classification search or even browse function. I'm just on Windchill 10.1 M030. After you have found your object, you can then collect with the normal collectors.
The attached may look complicated. But the drivers are now ECN and not a listener for each object (Part or Document) to mature. Most companies review packages of drawings at a time and release the entire package at a time. It becomes very simple to just review the task of a simple workflow from the ECN level that drives the package.
To Mike and All, Have a Merry Christmas and Happy New Year.
We should really all come up with a proposal of how to view released structure based on various criteria (release date, effectivity, ECN, etc) to drill down even to WTPart/material respective drawings. I follow the CMII approach with the document impact matrix and revision matrix.
I mentioned this to PTC of structures with more than 3 levels deep. I don't beleive they really understood what was required that you sometimes don't mass revise the entire structure all the way up. We sometimes follow a 1 level up BOM revise if a WTPart component replacement. Thus, there is no fit, form, function (3f's) change to the 2 level up WTPartBOM. This leads to BOM management which I'm very disapointed in PTC in how their architecture is focused on just a programmatic limitation ofa usage link versus business rules.
It's been like this since day one of Windchill.
That's another issue I had with PTC WTPart Managmentwith supplier management. Adding manufacturer's part types to WTPArts to add/update or change AML and AVL should not change the material or fit, fit form and function and thus should not require a iteration or revision to the "design" WTPart. Hopefully, the person is only allowed to add a AML/AVL link but I bet you have to addd more ACLs to the other attributes so they are not able to modify.
What happens after released state, if you need to add more AML and AVL updates? Some companies (electrical) have the AML on the schematic BOM and some don't.
Since PTC is supposed to now cater to both Electrical, software, mechanical or complete product BOMs, it should have the ability to separate AML/AVL changes to WPart changes. Sourcing status is not a modification to material or fit, form, or function change. It can be a document revision like the schematic or drawing that has the AML report. The WTPart BOM should not revise if it is not part of the design BOM.
But, if it is your business your busness process, then by all means. I would try to prevent mass revising and keeping everything to its functional and business constituents.
Great dicussion! Designing Change Control is next on my plate next year - we are in the prrocess of updating to WC 10.1 as I type.
Merry Christmas also to Mike & all! Kathy