Skip to content
Industry reportsAll articles

PLM Software: What It Is, eBOM vs mBOM, ECO Flow & 36-Month TCO

PLM software manages the product definition: CAD data, the engineering and manufacturing BOMs, and engineering change. Here is what it is, how the eBOM becomes the mBOM, how change flows through ECR-ECO-ECN, where the ERP boundary sits, and when to build instead of buy.

Artem Zaitsev
Artem ZaitsevCTO · Idealogic
Author: Artem ZaitsevPublished: Updated: Reading time: 23 minHow we write →
On this page
Idealogic guide to how PLM software works and how it is built

PLM software, or product lifecycle management software, manages the definition of the product itself: what it is, how its parts combine, and how that changes. A PLM system keeps the authoritative record (the CAD models, the part masters, the bills of materials, and the documents) across the product's whole life, from first sketch through engineering, manufacturing, service, and retirement. Every other manufacturing system depends on that record, and none of them owns it. When a maintenance, planning, or quality system asks what the product is, the answer should come from one place, and that place is PLM.

This guide is written for the team deciding how to manage product data and engineering change. It covers where PLM stops and PDM starts, the CAD vault at the core, how the engineering BOM becomes the manufacturing BOM, how a change flows through the ECR-ECO-ECN chain, where the line with ERP sits, what the digital thread requires, and what PLM software costs to buy or to build around.

The short version

  • PLM software is the system of record for a product's definition: the CAD data, item masters, bills of materials, and documents that say what a product is, held under version control across its whole life.
  • PDM is the subset of PLM that runs the CAD vault and document control; PLM wraps the lifecycle around it, adding the BOM transformation, engineering change, configuration, and the release of the definition downstream.
  • The eBOM to mBOM transformation is PLM's signature job: it restructures the as-designed engineering BOM into the as-built manufacturing BOM and maintains the mapping between them so change can propagate later.
  • Engineering change runs through a controlled ECR to ECO to ECN chain, where an effectivity date decides which units keep the old revision and which take the new one.
  • PLM and ERP meet at the released mBOM: PLM authors and approves it, ERP and MES consume a specific approved revision, and editing BOMs directly in the ERP is how definitions drift.
  • Buy or configure a commercial PLM when your process is standard. Build a custom layer ($95,000 to $220,000 in CEE at $75/hr vs $209,000 to $484,000 in the US at $165/hr, by our estimate) when eBOM-to-mBOM restructuring, ECR/ECO/ECN effectivity, or CAD-to-ERP integration is where your process differs. In our modelled 95-user scenario that layer comes out $72,700 to $454,300 cheaper over 36 months than the packaged PLM suites.

What is PLM software, and what does it manage

PLM software is the system of record for a product's definition. A PLM system knows what every part and assembly is, which revision is current, how the parts combine into a product, and what changed when. Everything physical a company makes starts as data (a model, a drawing, a specification), and PLM is where that data lives under control instead of scattered across engineers' drives and shared folders. The defining job is authority. When the floor, the planners, and the buyers each need to know what the product is, PLM holds the version they should all be working from.

What PLM manages is narrower and deeper than a feature list suggests. It holds the item master, the canonical list of parts with their attributes and current revision. It holds the bills of materials that say how parts combine. It holds the documents and CAD data that specify each part. And it governs the process of change, so a revision doesn't diverge between engineering and the floor. That change control is how a manufacturer meets the design and development controls of ISO 9001:2015 Clause 8.3. In medical-device manufacturing it also maintains the design and development records required under the FDA 21 CFR Part 820 Quality Management System Regulation (QMSR), in force since February 2, 2026. The QMSR incorporates the ISO 13485 Clause 7.3 design controls and replaced the legacy 21 CFR 820.30. Across the lifecycle PLM adds configuration management, where-used and where-referenced traceability, and the release of the definition to the systems that build and sell the product. Underneath the screens, PLM is a controlled graph of parts, documents, and revisions.

Why run a PLM system at all? Because the definition gets one owner. The floor stops building from a superseded revision, since only released revisions leave PLM. Changes take less time to assess, because the where-used graph shows what a change touches before anyone approves it. And an auditor can trace a shipped unit back to the revision, the BOM, and the change order behind it.

PLM vs PDM: what PLM software adds

PLM vs PDM is the first distinction to settle, because the two terms get used interchangeably and don't cover the same scope. Product data management is the CAD and document core: the vault that versions design files, the check-in and check-out that stop two engineers overwriting each other, the item master, and the links that tie documents to the parts they describe. PDM answers a focused question well, what the current design is and who is working on it, and for a small engineering team that is often enough on its own.

PLM contains PDM and wraps the lifecycle and process around it. It takes the vaulted design data and adds the eBOM-to-mBOM transformation, engineering change management, configuration and variant control, and the release of the product definition downstream to ERP and MES. The clean shorthand is that PDM manages the files; PLM manages the product and the processes that change it. The practical path reflects the relationship: many organizations adopt PDM first to get the vault under control, then grow into full PLM as change, manufacturing structure, and integration become the problem. Knowing which one you need, the vault alone or the full lifecycle, saves you from buying a platform to solve a filing problem, or a vault to solve a process one.

The CAD vault at the core of PLM software

Under every PLM system sits the vault, the controlled store that turns design files into managed data. CAD files are not ordinary documents: a single assembly references dozens of part files, and editing one can ripple through many, so a plain shared folder loses track of which version is current and lets two engineers overwrite each other's work. The vault exists to make that impossible. Its mechanics are the part of PLM most people use first and understand least.

Check-out, check-in and versions

The core operations are check-out and check-in. An engineer checks a file out, which locks it for editing and signals to everyone else that it is in use. On check-in, the vault stores a new version, keeps the prior ones, and releases the lock. Every check-in creates an immutable version, so the history of a design is recoverable and a mistaken change can be rolled back.

References and where-used

The vault also tracks references, the web of which assemblies use which parts and which drawings document them. A where-used query answers the question that decides every change: if I revise this part, what else does it affect? On top of that sits the item master and revision control. Each part has one canonical record, a current revision, and a state, and the vault enforces that a released revision can't be edited in place. This is the same controlled-document discipline that quality management software applies to procedures, applied here to the product's own data. If the vault is wrong, every downstream BOM and change inherits the error.

eBOM vs mBOM: the transformation PLM software owns

The bill of materials is where a PLM system does work no other system does, because a product has at least two BOMs and something has to translate between them. That is also where PLM goes further than bill of materials software, which stores one structure: PLM keeps two in step. The engineering BOM, the eBOM, is the as-designed structure: the parts and assemblies as engineering conceives them, organized by function and design intent, generated straight from the CAD assembly. It answers what the product is, in the terms of the people who designed it.

The manufacturing BOM, the mBOM, is the as-built structure: the same product reorganized for how it is assembled. The two diverge for real reasons. The mBOM follows the process and plant structure, grouping parts by the sequence and the line that builds them rather than by design function. It adds manufacturing-only items the eBOM never mentions: adhesives, fasteners bought in bulk, packaging, consumables, and phantom assemblies that exist only to structure the build. It may split one engineering assembly across several work centers, or merge several into one buildable sub-assembly. The BOM also carries component-level material declarations (IPC-1752) and XML supply-chain packages (IPC-2571 PDX), both standards published by IPC. PLM uses this structure to roll up substance weights for EU RoHS Directive 2011/65/EU and for Substances of Very High Concern (SVHC) under EU REACH Regulation (EC) No 1907/2006. The same data model prepares Digital Product Passport (DPP) disclosures under the EU Ecodesign for Sustainable Products Regulation (EU) 2024/1781, which apply once a product-specific delegated act covers your product group. The mBOM is what production, planning, and purchasing run from, and it is the structure that connects to the consumption logic we cover in manufacturing inventory software.

PLM owns the transformation: restructuring the assemblies, inserting the manufacturing items, and maintaining the mapping from each eBOM part to its mBOM position so the link survives. That mapping is what makes change propagation possible later, because when engineering revises an eBOM part, PLM can find every mBOM place it touches. Done by hand in spreadsheets, the eBOM and mBOM drift apart and the floor builds from a structure engineering no longer recognizes. The mBOM that PLM releases is the one that feeds production planning software and the ERP, so the transformation belongs in PLM and not in a downstream system.

PLM transforms the as-designed eBOM into the as-built mBOM and keeps the mapping between them
ViewStructureWho owns it
eBOM (as-designed)By function and design intent, straight from CADEngineering authors it in PLM
TransformationRestructure, add manufacturing items, map partsPLM owns and maintains the mapping
mBOM (as-built)By process, plant, and line; adds consumables and packagingPLM releases it to ERP and MES

How PLM software runs engineering change: ECR, ECO, ECN

Once a product is released, the question is no longer what it is but how it changes, and uncontrolled change is how the floor ends up building a revision engineering abandoned. PLM runs change through a disciplined chain, usually three linked stages, so a revision gets proposed and authorized before anyone acts on it. The names are common, though some organizations use ECO and ECN interchangeably.

It starts with the engineering change request, the ECR: a proposal that captures the problem, a defective part, a cost reduction, a supplier change, a field failure, and justifies why the product should change, before anyone touches a model. The ECR is assessed, costed, and either approved or rejected. An approved ECR becomes an engineering change order, the ECO: the authorized instruction that defines exactly what changes, on which parts and which BOMs, and from what effectivity date or serial or lot. Effectivity matters most here, because most changes are not retroactive: units already built or in transit keep the old revision while new builds take the new one, and the system has to know the cutover. Finally the engineering change notice, the ECN, communicates the released change to everyone who must act, purchasing, planning, the floor, suppliers.

The hard part to engineer is propagation. A change to one eBOM part has to reach every mBOM that uses it, the open orders mid-flight, and the inventory on hand, with effectivity deciding what applies from when, and the where-used graph deciding what is even affected. This is distinct from the change process quality management software runs: a quality CAPA drives change control over a document or procedure, while engineering change governs the product definition itself, the parts, the BOMs, the revisions. The two interlock, a CAPA can trigger an ECR, but conflating them puts product changes in a document system that cannot model effectivity or BOM propagation.

The change chain proposes, authorizes, and communicates a revision, with effectivity deciding what applies
StepWhat it capturesOutput
ECR (request)The problem and the justification to changeAn assessed, approved or rejected proposal
ECO (order)What changes, on which parts and BOMs, and effectivityThe authorized instruction to revise
ECN (notice)The released change, communicated to all affectedPurchasing, planning, floor, and suppliers act
Need PLM that fits your BOM structure and change process?
We build the product-data model, the eBOM-to-mBOM transformation, and the engineering change engine around how your product is actually defined, integrated to your ERP and MES.
Scope the product-data build

Configuration and variant management in PLM software

Configuration management defines a product as options, baselines, and rules instead of a separate BOM per variant. The discipline is described in SAE EIA-649C, and it matters because few products are a single fixed design. Most ship as a family of variants, and how PLM models that family decides whether engineering maintains one product or fifty near-copies. Done well, the definition stays maintainable and auditable as choices multiply.

The mechanism most PLM systems use is the superset BOM, often called the 150% BOM: a single structure that contains every part that could appear in any variant, with each part governed by a rule saying which options select it. A specific configuration is then a valid selection across those options, and the system resolves the superset down to the 100% BOM for that unit, the exact parts that build it. The rules carry the logic, this engine requires that controller, that trim excludes this bracket, so impossible combinations cannot be ordered. Effectivity threads through here too, since variants and revisions both change what a unit contains over time, and the same engine that resolves options resolves which revision applies. The payoff is that engineering changes the rules and the superset once, not every variant by hand. Good configuration management lets a product line scale without the BOM count exploding; poor configuration management leaves a separate BOM for every variant, and those go out of step the moment a part changes.

PLM vs ERP: how a PLM system releases the mBOM

The boundary that confuses the most evaluations is the one between PLM and ERP, and getting it wrong is how stale BOMs and quality escapes start. The line is clean once stated: PLM owns the product definition; ERP owns the transactions. PLM holds the design, the eBOM, the as-built mBOM, and the engineering change that revises them. The ERP, whose modules we cover in manufacturing ERP and will not re-explain here, runs purchasing, inventory, work orders, costing, and finance. One answers what the product is; the other runs the business of building and selling it.

They meet at the released mBOM. PLM authors and approves the manufacturing BOM, then releases it to the ERP, which consumes it to explode material requirements, raise purchase orders, and cost the build. The same released definition, along with target cycle times and tolerance specifications that establish the baseline for OEE, flows to the execution layer, the MES, which builds against it and reports back. The release is a one-way, controlled handoff: the definition is authored and changed in PLM, and ERP and MES are consumers of a specific approved revision, not co-editors of it. Editing BOMs directly in the ERP breaks that handoff: the change never returns to engineering, the eBOM and mBOM diverge, and the next ECO propagates from a definition the ERP altered without engineering knowing. Define the boundary as PLM-authors, ERP-and-MES-consume, with the released mBOM as the contract, and the floor builds the revision engineering approved.

PLM authors and releases the mBOM; ERP and MES consume a specific approved revision
SystemOwnsAt the boundary
PLMThe product definition: design, eBOM, mBOM, changeAuthors and releases the approved mBOM downstream
ERPTransactions: purchasing, inventory, orders, costingConsumes the released mBOM to plan and buy
MESShop-floor execution against the definitionBuilds the released revision, reports actuals back
Most BOM escapes on the factory floor start at the seam between CAD and the ERP, not inside the vault. When engineers export CSVs by hand and buyers edit phantom sub-assemblies inside the ERP, the eBOM and mBOM often diverge silently within a few ECO cycles. Owning the associative eBOM-to-mBOM contract and effectivity gate is what keeps the digital thread honest.
Artem Zaitsev · CTO at Idealogic

The digital thread and the model-based enterprise

The digital thread is the connected flow of product data across the lifecycle, from requirements and design through a connected smart factory and out to field service, the maintenance records in CMMS software, and predictive maintenance software, so each stage works from the same authoritative model instead of re-creating it. The idea has a standards body behind it. The NIST Model-Based Enterprise program frames the model-based enterprise, or MBE, around integrating product, process, and logistics models across the enterprise and using the digital thread to link the lifecycle phases. PLM is the backbone of the thread, because it owns the definition every other stage references.

Two ideas make the thread practical. The first is model-based definition, MBD: putting the full product definition, including dimensions and tolerances, into the 3D model itself rather than a separate 2D drawing, so there is one authoritative source. ASME Y14.41 is the standard that defines this digital product definition, letting the model carry the product and manufacturing information downstream systems consume. The second is a neutral exchange format, because CAD comes from many tools and the thread cannot break at every handoff. ISO 10303-242 (STEP AP242) for Managed Model-Based 3D Engineering is the modern standard; as NIST describes in its STEP tooling, STEP represents parts, assemblies, and semantic product and manufacturing information (PMI) for exchange between CAD, CAM, CAE, and CMM inspection software. Integrating MCAD and ECAD, mechanical and electronic design, into one thread is part of the same problem. For a build decision the consequence is simple: a digital thread is only as continuous as the integrations under it, and those integrations have to be engineered.

Build, configure, or buy PLM software

With the vault, the BOMs, change, configuration, and the thread in view, the decision is which parts to buy, configure, and build. It comes down to one question: how standard is your product process? The parts that look like every other manufacturer's are well served by a package. The parts that are yours alone are where a package fights you. The commercial market is mature. CIMdata, which tracks it, put the PLM market at about $88.3 billion in 2025 under its broad definition, and Siemens Teamcenter, PTC Windchill, Dassault ENOVIA, Oracle (Fusion Cloud PLM, with Agile PLM in a support-sunset transition), SAP's PLM capabilities, Arena, and Aras all cover the standard ground.

When to buy

Buying or configuring a commercial PLM is the right default for that common ground. If your CAD vaulting, BOM structure, and change process resemble the norm, a mature product gives you CAD integrations and a roadmap that someone else maintains. The discipline is to stay close to standard, because every customization is a thing you re-test forever.

When to build

Building custom, or more often a custom engineering-data layer on top of your existing PDM vault, wins for the differentiators: a nonstandard 150% configuration or effectivity model no package fits, deep synchronization into a specific ERP or MES, or regulated substance and traceability rollups a generic vault handles thinly. We price those eBOM-to-mBOM, ECR/ECO/ECN, and CAD-to-ERP layers tier by tier in the 36-month TCO section below.

The hybrid pattern

The pattern most teams land on is hybrid: keep a commercial PLM or PDM vault and build the integration, configuration, and traceability layers around it, the shape of work we do in our custom software development, product development, and manufacturing practices. AirpartChain anchors aircraft-part records and their traceability to a tamper-evident ledger, the same product-data and as-built-history problem PLM solves from the engineering side. HaulBreeze and the Conveya transportation-management rebuild are both layers engineered around existing systems of record. Idealogic doesn't sell a packaged PLM. We build the product-data and integration layers that make product-lifecycle software fit a manufacturer that does not run like the template.

PLM software cost: 36-month TCO of Teamcenter, Windchill, Arena, Duro vs a custom layer

What drives PLM software cost

Evaluating PLM on author seat price alone hides two cost multipliers. One is downstream consumer and supplier seats: the buyers, quality engineers, shop-floor leads, and contract manufacturers who read released BOMs and redlines. The other is system-integrator (SI) schema customization, which you pay for whenever your eBOM-to-mBOM or ERP handoff deviates from the out-of-the-box templates. The vendor prices below are indicative. All four vendors sell by quote, and pricing varies by role, deployment, and contract.

  • Siemens Teamcenter (including Teamcenter X) and PTC Windchill (Windchill+). Enterprise MCAD/ECAD backbones. Indicative pricing is $3,000 to $5,000+ per author per year, plus consumer tiers, cloud or server infrastructure, and 1x to 2x certified-partner implementation and version-upgrade budgets. A strong fit for multi-CAD automotive and aerospace enterprises, expensive to customize for mid-market discrete plants.
  • Dassault Systèmes ENOVIA (3DEXPERIENCE). Role-based 3DEXPERIENCE licensing. Costs grow as change-governance, BOM-transformation, supplier-exchange, and ERP-connector roles are added to core CAD seats.
  • Arena PLM (by PTC). Cloud BOM, ECO, and integrated QMS suite, sold by quote (indicatively $1,200 to $2,500+ per user per year above a $10,000+ annual minimum). Electronics and medical-device teams favor it (compare standalone quality management software), though it's limited on 150% super-BOM rule solvers and multi-plant ERP/MES effectivity cutovers.
  • Duro PLM. Cloud SaaS priced by seat and ERP connectors, by quote. It suits hardware teams that want part-number generation and CAD BOM sync without a dedicated PLM administrator, and it gives up deep multi-plant mBOM restructuring and custom STEP AP242 or Digital Product Passport pipelines.

36-month TCO table

The worked 36-month TCO comparison below models a discrete or electromechanical manufacturer with 95 users: 35 mechanical, electrical, and manufacturing engineering authors plus 60 purchasing, QA, shop-floor, and contract-manufacturer consumers. The manufacturer keeps an existing CAD/PDM vault (SolidWorks PDM, Autodesk Vault, or Onshape) and needs closed-loop eBOM-to-mBOM release into ERP and MES. It's a modelled scenario with indicative vendor pricing, so treat it as a planning model.

36-Month TCO Line Item (35 authors + 60 consumers)Siemens Teamcenter / PTC WindchillDassault ENOVIA (3DEXPERIENCE)Arena PLM EnterpriseDuro PLM EnterpriseCustom eBOM-to-mBOM, ECO & CAD-to-ERP Layer
1. Implementation, data migration & CAD/ERP connector CapEx$145,000 (SI rollout + ERP bridge)$130,000 (partner role/schema setup)$42,000 (onboarding + ERP connector)$28,000 (cloud setup + ERP sync)$165,000 (2,200 hrs CEE at $75/hr; $363k US)
2. 36-mo author, consumer, supplier & ERP-bridge subscriptions$468,000 ($13,000/mo x 36)$432,000 ($12,000/mo x 36)$288,000 ($8,000/mo x 36)$216,000 ($6,000/mo x 36)$28,800 ($0/seat; $800/mo AWS/S3 over existing PDM)
3. 36-mo version upgrades, SI admin & manual mBOM workarounds$75,600 (PLM admin + upgrade packs)$68,400 (role/connector SI ops)$54,000 (20 hrs/mo manual mBOM/ERP ops)$63,000 (multi-plant mBOM scripting)$40,500 (15 hrs/mo connector & rule ops at $75/hr)
Total 36-Month All-In TCO$688,600$630,400$384,000$307,000$234,300 (100% of $165k CapEx included)
Years 4 to 5 Annual Run-Rate$181,200/yr$166,800/yr$114,000/yr$93,000/yr$23,100/yr (unlimited plant & CM supplier seats)

The custom column excludes the cost of the existing CAD/PDM vault, which you already pay for, and assumes the packaged suites replace it.

In this scenario, keeping your engineers' existing CAD/PDM vault and building a custom eBOM-to-mBOM transformation, ECR/ECO/ECN approval workflow, and CAD-to-ERP middleware in CEE saves $454,300 against Siemens Teamcenter or PTC Windchill, $396,100 against Dassault ENOVIA, $149,700 against Arena PLM, and $72,700 against Duro over 36 months. Buyers, operators, and external contract manufacturers read live released revisions with no per-seat fee.

Custom PLM layer tiers

Idealogic's 2026 manufacturing and custom software development engineering tiers compare senior CEE squads at a blended $75/hr, our own billing rate, against an illustrative US systems-integrator rate of $165/hr blended (see also our custom software development cost guide). For context, Eurostat puts the 2025 EU-27 average labour cost at about EUR 34.90 per hour, which is wage and non-wage cost before overhead, utilization, and margin.

2026 Custom PLM Data Backbone TierCore BOM, Change-Control & CAD-to-ERP DeliverablesTimelineCEE Build (at $75/hr)US Agency (at $165/hr)
1. CAD/PDM-to-ERP Released mBOM Bridge & Effectivity GateAutomated PDM check-in listener (SolidWorks PDM, Vault, Onshape), canonical item-master sync, one-way released mBOM handoff to ERP & serial/date effectivity validation (1,267 to 1,800 hrs)10 to 14 weeks$95,000 to $135,000$209,000 to $297,000
2. Associative eBOM-to-mBOM Engine, ECR/ECO/ECN & CM PortalGraph-backed eBOM-to-mBOM restructuring, where-used impact analyzer, multi-signoff ECR/ECO/ECN workflow linked to QMS CAPA & contract-manufacturer redline portal (1,800 to 2,400 hrs)14 to 20 weeks$135,000 to $180,000$297,000 to $396,000
3. 150% Super-BOM Configurator, STEP AP242 & DPP-Ready Data ModelBoolean 150% variant resolver (SAE EIA-649C), IPC-1752 RoHS/REACH rollups, DPP-ready data model for EU ESPR, STEP AP242 PMI parser & closed-loop ERP/MES genealogy sync (2,400 to 2,933 hrs)20 to 26 weeks$180,000 to $220,000$396,000 to $484,000
PLM software is worth getting right because every other system builds from what it releases. If your process is standard, buy a PLM system and stay close to its defaults. If the eBOM-to-mBOM mapping, effectivity, or the ERP handoff is where you differ, keep the vault and build that layer, which is the work our manufacturing practice does.
Need the product-data layer a packaged PLM cannot give you? We build it
Share your CAD/PDM vault, ERP/MES stack, and eBOM-to-mBOM or ECO bottlenecks. Our manufacturing engineers will return an associative BOM architecture and 36-month PLM TCO plan.
Scope a manufacturing build with us

Occasional field notes on building software, no spam

Protected by Cloudflare Turnstile · Privacy · Terms

Artem Zaitsev
Artem ZaitsevCTO · Idealogic Development OÜ

CTO and Co-founder at Idealogic. Directing engineering, systems architecture, security, and full-stack delivery across web, mobile, and blockchain.

Frequently asked questions

  • PLM software, short for product lifecycle management software, is the system of record for a product's definition from concept through engineering, manufacturing, service, and retirement. A PLM system manages CAD models, drawings, item masters, engineering and manufacturing bills of materials, and technical specifications under version control. It also routes engineering changes through controlled workflows before it releases approved revisions to ERP and MES.

  • Product data management (PDM) is a subset of PLM focused on the CAD vault and document control. It manages file check-in and check-out, revision histories, item masters, and CAD assembly references. PLM includes PDM and adds the lifecycle processes around the vault: eBOM-to-mBOM transformation, engineering change management (ECR, ECO, ECN), variant configuration, environmental compliance, and automated release to ERP and MES.

  • PLM owns the product definition. ERP owns the commercial and operational transactions. PLM manages CAD designs, the engineering BOM (eBOM), the manufacturing BOM (mBOM), and the engineering change workflows that revise them. Once PLM approves and releases an mBOM revision, the ERP consumes that specific revision to run material requirements planning, purchasing, inventory valuation, work orders, and financial accounting.

  • The engineering BOM (eBOM) reflects the as-designed product structure generated from CAD, organized by functional systems and design intent. The manufacturing BOM (mBOM) reorganizes that same product into the as-built structure required by the factory floor, adding routing sequence groupings, packaging, adhesives, bulk fasteners, consumables, and phantom sub-assemblies where the planning system uses them. PLM maintains the associative mapping between eBOM and mBOM so design revisions propagate to every place they apply.

  • Engineering change management is the closed loop that revises a released product definition, usually in three stages. An engineering change request (ECR) documents a field issue, cost reduction, or component obsolescence and justifies the change. An approved ECR becomes an engineering change order (ECO), which specifies the exact part and BOM updates plus effectivity dates or lot cutovers. An engineering change notice (ECN) then tells purchasing, production, and suppliers. Some organizations use ECO and ECN interchangeably.

  • Buy and configure a commercial PLM suite when your CAD vaulting, BOM management, and ECO workflows match standard industry patterns, because native CAD connectors are expensive to build from scratch. Build custom software, or a hybrid integration layer on top of a commercial vault, when your differentiation depends on complex 150% variant configuration, multi-plant effectivity propagation, regulatory compliance automation, or deep ERP and MES synchronization.

  • A 150% super BOM is an overloaded product structure that contains every possible component, sub-assembly, and option across an entire product family, governed by boolean selection and exclusion rules. When a customer order or build specification selects specific options and effectivity dates, the PLM configuration engine resolves the 150% super BOM down to a 100% unit-specific BOM that ERP and MES can build.

  • PLM owns the item master and the bill of materials, so it can track material declarations and substance composition at the component level using standards such as IPC-1752. Engineering teams roll up restricted-substance weights across the whole BOM to check compliance with EU RoHS Directive 2011/65/EU and REACH Regulation 1907/2006 before release. The same data model prepares Digital Product Passport disclosures under the EU Ecodesign for Sustainable Products Regulation (ESPR 2024/1781), which apply once a product-specific delegated act covers your product group.

  • Siemens Teamcenter, PTC Windchill, and Dassault ENOVIA are the usual choices for complex enterprise MCAD and ECAD environments. They bring deep vault governance, and they tend to come with integrator-led deployments and per-role fees. Arena PLM serves mid-market electronics and medical-device manufacturers with cloud BOM and QMS workflows. Duro PLM is quicker to onboard for hardware startups but lighter on multi-plant mBOM restructuring and 150% super-BOM configuration. All of them sell by quote, so compare on a modelled total cost, not on list price.

  • By Idealogic's estimate, a custom eBOM-to-mBOM sync engine, ECR/ECO/ECN approval workflow, and CAD-to-ERP middleware costs $95,000 to $220,000 in Central and Eastern Europe at $75 per hour, versus $209,000 to $484,000 at an illustrative US rate of $165 per hour. In our modelled scenario of 95 engineering, purchasing, and plant users over 36 months, a custom layer over an existing PDM vault comes to $234,300 all-in. The indicative totals for the packaged suites are $307,000 on Duro, $384,000 on Arena PLM, $630,400 on ENOVIA, and $688,600 on Teamcenter or Windchill.

Still unanswered
Ask us directly

A senior engineer replies under 4 hours.