For energy and power systems
In energy hardware the design is rarely the constraint. Certification, grid compliance and the paperwork proving both are what determine when a product can be sold and where.
Compliance as a resolved fact
An inverter sold into three markets meets three sets of grid codes, and the certification that permits each is tied to a specific configuration tested by a specific body on a specific date.
Held as documents, that relationship is a folder and a convention. Held as data, it is a resolvable claim: this certification covers this configuration, and here is what changes if any component in it is substituted.
The rollup is the mechanism. Component-level declarations — RoHS, REACH, conflict minerals, country of origin — resolve upward through the structure so a product-level answer is computed rather than maintained. A customer questionnaire that used to take a week becomes a query against current data.
The part that matters operationally is the inverse question. When a component is substituted, which certifications does that touch? That is where-used run from a component to a certification, and it is the difference between discovering a recertification requirement during change review and discovering it when a shipment is held at a border.
Traceability that reaches the supplier
Energy hardware carries supply-chain obligations that most industries do not: origin documentation, forced-labour compliance regimes, and increasingly customer requirements that reach two or three tiers back rather than stopping at your direct supplier.
Those obligations attach to AML entries and supplier records rather than to items, because they are facts about who makes a thing rather than about the thing. An item with three approved manufacturers has three origin stories, and collapsing them onto the item means answering with one and quietly discarding two.
Certification expiry is the failure that recurs. A supplier's certification lapses, nobody notices because it is a date inside a PDF, and parts received during the gap went into products that shipped under a compliance claim that was no longer supportable.
Held as typed fields with watchers, the same lapse raises a task ninety days out with the affected products named — which converts a disclosure into a scheduling conversation.
The failure it prevents
A power electronics manufacturer substitutes a capacitor during a shortage. The replacement is electrically equivalent, approved through change control, and correctly documented.
Eight months later a certification renewal reveals that the original capacitor was named explicitly in the type-test report for one market. The substitution invalidated the certification for that market on the day it was made. Product shipped there for eight months under a certification that did not cover it.
Nobody could reasonably have known, because the relationship between a component and a certification lived in a test report nobody reads during a change review. Resolving certifications through the structure means the change review shows it, at the moment somebody is deciding.
How it meets the rest of the product
Impact analysis is where this industry gets its value. A proposed substitution reports the affected products, the open orders, the suppliers holding controlled copies — and the certifications whose scope includes the component being changed.
Site-specific as-built records matter for installed systems. A grid-connected installation is commissioned in a configuration, modified over its life, and audited against what is there rather than what was sold, so the same as-built discipline that serves field service also serves regulatory inspection.
Documents carry their relationships, which is what makes a certification pack assemblable rather than curated. The pack for a configuration is generated from the objects it covers rather than maintained as a folder somebody keeps in step by hand.
The change calendar carries recertification lead times, which in this industry run to months rather than weeks. A change effective in six weeks that requires a test-house slot booked twelve weeks out is a scheduling conflict worth seeing at approval rather than at the point somebody tries to book it.
How it meets your ERP
Compliance data belongs here and reaches your ERP as flags rather than as documents. An item marked as restricted for a market, or as requiring origin documentation at receipt, is something the ERP can act on; a REACH declaration PDF is not.
Where an ERP receipt process enforces documentation, that flag is the mechanism, and it originates from the rollup rather than from somebody remembering to set it on an item. A flag set by hand is a flag that is wrong within two substitutions.
Manufacturing PLM does not file regulatory submissions, hold your certification body relationships or track your grid-code approvals as a workflow of their own. It holds the technical facts those processes depend on and makes the dependency visible.
Where the boundary is
Manufacturing PLM does not certify anything and does not decide compliance. It resolves declarations through the structure and reports what a change touches. Whether a configuration meets a grid code is a determination made by people and bodies with the authority to make it.
It also does not replace a compliance management system where you have one. The rollup and the traceability are engineering facts; audit programmes, regulatory correspondence and submission management belong elsewhere and should stay there.
Facts
| The constraint | Certification and grid compliance, not the design |
| A certification | Covers a configuration, not a product name |
| Rollup | RoHS · REACH · conflict minerals · country of origin |
| The inverse question | Which certifications does this substitution touch |
| Obligations attach to | AML entries and suppliers — three manufacturers, three origin stories |
| Expiry watch | Tasks 90 days out, affected products named |
| To the ERP | Flags the ERP can act on, not documents it cannot |
| Never | Certifies · determines compliance · files submissions |
Frequently asked
Why hold certifications as data rather than documents?
Because as a folder the relationship between a certification and the configuration it covers is a convention. As data it is a resolvable claim, which means a change review can show what a proposed substitution would invalidate at the moment somebody is deciding.
What does the compliance rollup actually do?
It resolves component-level declarations — RoHS, REACH, conflict minerals, country of origin — upward through the structure, so that a product-level answer is computed rather than maintained by hand. A customer questionnaire that used to take a week becomes a query against current data.
Why attach origin data to the AML rather than the item?
Because origin is a fact about who makes a thing rather than about the thing itself. An item with three approved manufacturers has three origin stories, and collapsing them onto the item means answering with one of them and quietly discarding the other two.
What is the failure that recurs most?
A supplier's certification lapsing unnoticed, because it is a date inside a PDF. Parts received during the gap go into products shipped under a compliance claim that was no longer supportable, and it surfaces at renewal rather than at receipt.
How would a substitution invalidate a certification?
If the original component was named explicitly in a type-test report. The substitution invalidates coverage for that market on the day it is made, and without the relationship held as data nobody sees it until a renewal eight months later.
What reaches our ERP from all this?
Flags rather than documents. An item marked as restricted for a market, or as requiring origin documentation at receipt, is something the ERP can act on. It originates from the rollup rather than from somebody remembering to set it by hand.
Does Manufacturing PLM determine whether we are compliant?
No. It resolves declarations through the structure and reports what a change touches. Whether a configuration meets a grid code is a determination made by people and bodies with the authority to make it, and software should not imply otherwise.