MCO Functionality in Windchill for Agile PLM Migrated Customer

[LM_12507976]

Version: Windchill 13.0

Use Case: Our customer has recently migrated from Agile PLM to Windchill and is looking for similar Manufacturing Change Order (MCO) functionality. Specifically, they are interested in understanding how Windchill handles scenarios such as: Attribute modifications Addition of AML (Approved Manufacturer List) parts …after a part has been released, without requiring a change in the part revision. Could you please confirm if such changes can be managed in Windchill without revising the part? This will help us guide the customer appropriately.

Description:

Our customer has recently migrated from Agile PLM to Windchill and is looking for similar Manufacturing Change Order (MCO) functionality.

Specifically, they are interested in understanding how Windchill handles scenarios such as:

• Attribute modifications
• Addition of AML (Approved Manufacturer List) parts

…after a part has been released, without requiring a change in the part revision.

Could you please confirm if such changes can be managed in Windchill without revising the part? This will help us guide the customer appropriately.

[avillanueva]

If you are looking for managing AML, look at the Supplier Management module. This allows for management of the AML/AVL without check in/out. It does not have a formal MCO but does keep track of changes to the entries. 

https://support.ptc.com/help/wnc/r12.0.2.0/en/#page/Windchill_Help_Center%2FSUMA_PartRelationAbout.html%23

[LM_12507976]

"Thank you for the input.

How can we manage minor attribute changes after a part has reached the Released state? The customer prefers not to follow the formal change management process for such minor updates. Does Windchill provide any capability to handle these changes without requiring a revision or state change?"

[avillanueva]

Yes but this involves special access rights and administrative changes. We have roles setup who are authorized to make modifications to released parts without formal change management or revision. This is a business process you would define but practically in Windchill, it might involve a role with a limited set of folks, say a small configuration management team, who has modify rights on Released objects. Your business rules would document what they are allowed to change and what they are not. 

For example, we carry attributes for export control. Since those can change with export control reform, we allow for administrative changes which do require check out and in of Parts to update attributes. Those changes can be noted in check in comments for any audit purposes. Changes like BOM changes would require formal CM workflows but nothing would stop that privileged users for making edits to the BOM when they made a change to the attributes. It all goes together but this is where your business process would see this as a no no.

[Catalina]

Hi @LM_12507976,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution or please feel free to detail in a reply what has helped you and mark it as the Accepted Solution. It will help other members who may have the same question.

Of course, if you have more to share on your issue, please pursue the conversation.

Thanks,