Our organization operates in multiple regions with varying compliance requirements, and we’re struggling to manage MCO configurations effectively in Agile 9.3.5. We have global MCO templates for standard compliance categories (RoHS, REACH, Conflict Minerals), but each region has additional local requirements that need to be tracked.
For example, our EU operations need SCIP database reporting fields, APAC requires additional material declarations for China RoHS, and North America has specific conflict minerals reporting formats. Currently, we’re using separate MCO templates for each region, but this creates duplication and makes it difficult to maintain consistency for global parts.
When a part is used across multiple regions, we end up with multiple MCO records that sometimes have conflicting data. How do other global organizations handle this? Do you use a single global template with regional overrides, or maintain separate regional templates? And how do you ensure compliance-driven configuration changes don’t break existing MCO workflows?
I think the real question is whether your business process supports a single MCO model or genuinely needs regional separation. In most cases, the compliance data itself is universal - a substance is either present or not. What varies is the reporting format and threshold levels. You might be better served by a single MCO template with regional reporting views rather than separate templates. Use custom reports and exports to generate region-specific formats from the common data model.
Have you considered using configuration sets? We define a configuration set for each regulatory region, and parts are assigned to the relevant sets. The MCO template has conditional fields that only appear based on the active configuration set. This keeps everything in a single MCO record but tailors the view and required fields to the region. It works well for us with about 80% field overlap between regions.
The conflicting data issue is tricky. We implemented a data governance rule that designates one region as the “master” for each part based on where it’s primarily manufactured. That region’s MCO is authoritative, and other regions create linked reference MCOs that point back to the master. This prevents duplication while still allowing regional annotations. You need good change management though to ensure updates to the master MCO trigger reviews in dependent regions.