Engineering ERP · BOM and design control
Wrong revisions on the shop floor, parts bought twice and changes nobody signed off cost engineering firms more than they think. TECHTARN BOM and design control keeps multi-level BOMs, revisions and engineering changes in one place, linked to your CAD, purchasing and production.
Every level, quantity and unit is kept. Change the build quantity and see what the shop and stores need, with shared parts like bolts added up across assemblies.
FG-2001 eaAssemblyFB-0011 eaAssemblyFB-0111 eaMakeHW-0164 eaBuyDR-1001 eaAssemblyBO-0771 eaBuyMC-3101 eaMakeHW-1038 eaBuyEK-0501 kitKitEL-2201 eaBuyEL-0256 mBuySM-1041 eaMakeHW-1036 eaBuyEngineers group parts by function. The shop builds by work centre and adds paint, packing and kits. The ERP keeps both structures and links every item between them.
Each revision moves through five states. Only released revisions can be bought or built, and every step records who did what and when.
+ added~ changed− removed
Before you replace or change a part, the ERP lists every assembly, open order and stock location that uses it, so nothing is built from an old design.
When an engineer releases a design in SolidWorks, Inventor or AutoCAD, the BOM, part properties and drawings flow into the ERP. No retyping, no version mix-ups.
Material, bought-out parts, labour and overhead roll up from the lowest level to the finished product. Change the build quantity to see how setup cost spreads.
Most firms we audit find the same part saved under several names. Naming rules, classes and duplicate checks stop it happening again.
Example from a typical audit, not a specific client.
Nine connected features. Each links to the related part of the Engineering ERP.
Not sure how messy your item master is? Start with a free audit.
Take the free ERP auditSend us a sample BOMIf your products are built from parts and sub-assemblies, this is for you. See the ERP pages for each industry.
We connect your design tools and accounts through our API integration work, so data is entered once.
We clean the item master first, because a tidy BOM is worth more than any feature.
BOM and design control feeds every other part of the suite.
Answers for design heads, production managers and owners.
It is how the ERP stores what goes into each product: parts, sub-assemblies, quantities and units, in as many levels as needed. Purchasing, stores, production and costing all read from the same BOM, so everyone builds and buys the same thing.
The engineering BOM (EBOM) shows how the product is designed. The manufacturing BOM (MBOM) shows how it is built: which parts go to which work centre, plus items like paint, packing and kits. The ERP keeps both and links them.
Every part and BOM has a revision letter and an effective date. A new revision goes through draft, review and approval before release, and older revisions stay in history but cannot be used for new orders.
An ECO is a controlled request to change a part or BOM. It records why, what changes, who approved it and when it takes effect, and shows the impact on stock, open orders and cost before release.
Yes. We import BOMs and part properties from SolidWorks, Inventor and AutoCAD, or connect to SolidWorks PDM or Autodesk Vault so released designs flow into the ERP without retyping.
It lists every assembly, product, open order and stock location that uses a part. Before changing or replacing a part, you see exactly what it will affect.
Yes. Material, bought-out, labour and overhead costs roll up from the lowest level to the finished product, using standard, latest or average prices.
Yes. You can set approved alternates for a part, and use phantom or kit items that group parts for planning without being stocked.
About 6 weeks for most firms: part audit and clean-up, setup, import from CAD or Excel, a pilot release and go-live. A large or messy item master takes longer.
Tell us what CAD you use, how BOMs reach the shop today and where mistakes creep in. We reply within 4 business hours and can demo with one of your own BOMs.