The architecture pattern
A
Engineering change order modifies BOM
Component substitution · New supplier · Material change
Gate A
↓
Classification impact assessed before ECO closes
New component ECCN documented · Cannot close without it
BOM gate
B
Production order created for controlled product
ERP release · Manufacturing floor · Controlled item in BOM
Gate B
↓
Classification confirmed current · Open ECOs checked
Cannot release without confirmation · Compliance sign-off required
Production gate
C
Multi-origin BOM enters production
US-origin controlled content · FDPR applicability
Gate C
↓
De minimis calculated · FDPR flag embedded
Country of origin per component · Recalculated at every BOM change
Origin gate
D
Controlled product completes production
Production run complete · Quality inspection passed
Gate D
↓
Compliance-linked production record generated
Classification at production · BOM config · Lot numbers · Test records
Record gate
✓
Evidence generated — product enters shipment workflow
Manufacturing Compliance Register · Timestamped
Record
Control DNA — Engineering fields
| Field | Type | What it governs | Review trigger |
|---|---|---|---|
eccn_current |
text |
The classification that reflects the current BOM configuration — not the original assignment. Must update every time an ECO changes technical attributes or performance. |
ECO closed |
bom_classification_date |
timestamp |
When classification was last confirmed against the current BOM. If this date precedes the last ECO, the classification is stale. |
Any ECO |
component_eccn[] |
text[] |
Classification of every controlled component in the BOM. Aggregate classification cannot be confirmed if any component classification is unknown. |
BOM change |
country_of_origin[] |
char[] |
Country of origin for every component. Required for de minimis calculation and FDPR applicability. Cannot be estimated — documented per component. |
BOM change |
fdpr_applicable |
bool |
Whether the Foreign Direct Product Rule applies based on US-origin controlled content in the BOM. |
Origin change |
production_record_id |
text |
Links the finished product to the compliance-linked production record: classification at production, BOM config, lot numbers. |
Production complete |
open_eco_flag |
bool |
Whether any open ECO affecting this product lacks a classification impact assessment. True blocks production release. |
ECO opened |
Failure modes
ERP carries a stale classification
Product modified through multiple ECOs. None updated the product master. Every downstream system inherits the original ECCN. Fix: classification update required before ECO reaches approved status.
Silent violation
BOM changes bypass the ECO process
Emergency substitutions. Verbal approvals. Supply chain workarounds. Fix: all BOM changes require ECO — no exceptions.
Undetected drift
The MES does not know the ECCN
Production floor operates without visibility into export classification. Fix: classification field in production order — visible to MES.
Blind execution
Country of origin estimated, not calculated
De minimis done once at initial design. Never updated as BOM evolves. Fix: country of origin required field per component — recalculated at every BOM change.
FDPR exposure
Production records are not compliance records
Two separate systems. No connection. Fix: MES completion event triggers compliance register entry automatically.
Reconstructed evidence
Intelligence signals
BOM classification currency rate
Active BOMs with classification reflecting current config · Target 100%
ECO classification review rate
ECOs with documented impact assessment · Target 95%+
Production release compliance rate
Production orders released with confirmed classification · Target 100%
Country of origin coverage rate
BOM components with documented origin · Target 100%
Production record linkage rate
Controlled products with compliance-linked production record · Target 100%
Implementation
01
Two required fields in ECO workflow: new component ECCN and classification impact assessment. ECO cannot close without both.
ECO workflow configuration · No budget required
02
Compliance sign-off required before production order releases for any controlled product.
Production order approval workflow
03
Compliance checklist attached to production traveler for each controlled product. Filed with reference to shipment.
Production traveler · Manual record
ERP
Classification field in product master. BOM gate automated. Production release blocked until classification confirmed.
SAP GTS · Oracle GTM
MES
Production completion event triggers compliance register entry automatically. Lot numbers, BOM config, classification linked.
SAP MES · Siemens Opcenter
PLM
BOM divergence monitored continuously. Classification mismatch flagged before next production run releases.
Windchill · Teamcenter · Arena