Other Technical FAQs
What is the difference between a 1752A and 1752B XML?
IPC-1752B is the new industry standard for material declarations that includes all data required for SCIP submissions. IPC-1752A does not include all required fields for communicating SCIP required data and so is not sufficient for SCIP purposes.
Why is my 1752A Class C XML not uploading?
The most common reason for IPC-1752A Class C XMLs failure to upload is that they contain declaration data that indicates an SVHC is contained above the threshold. IPC-1752A does not contain the required fields for SCIP reporting purposes and so, BOMcheck does not support XML upload of IPC-1752A Class C XMLs if an SVHC is contained above threshold. To declare such parts, you must use the RCD/FMD tool to capture the mandatory fields for SCIP reporting.
How does BOMcheck deal with ITAR?
- You and your suppliers control the confidentiality of your RCD/FMD/Assembly details in BOMcheck
- You and your suppliers need to ensure that you use these confidentiality controls appropriately so that you do not give access to sensitive data under ITAR or the multi-Country Export Control Program for Dual-Use Goods & Technologies
Why is there no effective date in assembly XMLs?
There are three date types tracked for declarations:
- Date Added
- Date Effective
- Date Approved
The effective date is only applicable to discrete part declarations made by suppliers. As an assembly declaration is a roll up of discrete part declarations, the effective date is not applicable. The date provided in the Assembly PDF is the approval date which is the last date when the manufacturer creating or uploading a BOM approved this assembly. The approval date cannot be added to the XML as there is not attribute for it and these two date types should not be used interchangeably.