Engineering leads · Project managers · Purchasing
A new engineering export can change quantities, add components and move work between assemblies. Keep that change visible in the project where the team reviews release and purchasing decisions.
A spreadsheet sent by email gives purchasing a snapshot. It does not, by itself, explain what changed since the previous import or whether the new demand is ready to order. MeshWorks keeps imported BOM iterations in the project so engineering and purchasing can review the same working context.
Choose the project and check the source columns and part identities before bringing in the next BOM. Review parent relationships and quantities as well as descriptions; a familiar description alone is not a reliable part identity.
Use the iteration selector and change cues to identify new parts and increased or decreased quantities. Check the assembly hierarchy and project quantity before interpreting a change as new purchasing demand.
Inspect release status alongside purchasing information. A newly imported component or quantity change needs an engineering review; its presence in the BOM is not approval to buy it.
Use the current project BOM when preparing an RFQ or reviewing remaining quantities for a supplier order. Keep project records in the Dossier so the team can find the relevant commercial history.
No. The source CAD revision describes the engineering source. A MeshWorks iteration records an import into the project. Review both contexts when deciding which data is ready for release.
No. Review the changed demand and the applicable release and purchasing permissions before preparing or recording an order.
Yes. Spreadsheet BOM imports support a review workflow without requiring every reviewer to work inside CAD. Check the import mapping and part identities before relying on the result.
Review your actual handover
Walk through the project BOM, release and purchasing steps with the MeshWorks team and check which parts fit your process.
Talk to the team