A per-tenant Business Central extension that syncs your CAD/PLM system (SolidWorks PDM, Autodesk Vault, Siemens Teamcenter) with BC items, BOMs, and engineering changes — built, installed, and supported by ECOSIRE. One-time license from $799.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A per-tenant Business Central extension that syncs your CAD/PLM system (SolidWorks PDM, Autodesk Vault, Siemens Teamcenter) with BC items, BOMs, and engineering changes — built, installed, and supported by ECOSIRE.
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
Stop entering every part twice. When your engineers release a design in SolidWorks PDM, Autodesk Vault, or Siemens Teamcenter, that part number, description, unit of measure, and bill of materials should already exist in Business Central — not get re-keyed by a planner days later. The CAD / PLM Integration Connector is a per-tenant AL extension that ECOSIRE builds, installs, and supports directly on your Business Central environment to make that happen, in both directions.
Bi-directional item sync between your CAD/PLM system and the Business Central Item table — part number, description, base unit of measure, item category, and custom attributes via configurable field mappings
Bi-directional BOM sync covering Production BOM headers, lines, versions, and quantities, with structure-level comparison so only true deltas are written
Engineering BOM (eBOM) to manufacturing BOM (mBOM) transformation — phantom expansion, sub-assembly handling, make/buy substitution, and routing-aware structuring
Drawing and document linkage that attaches released CAD documents and revisions to BC items as links or stored references, with revision tracking
Engineering change propagation — PLM ECO/ECR releases flow into BC as controlled item/BOM updates with effective dates and full audit trail
Configuration-driven mapping rules and conflict resolution (last-write-wins, source-of-truth-per-field, or manual review queue) — no code change to adjust behavior
This is not an instant AppSource download. It is a build-to-order engagement. We start from your real CAD/PLM system, your item and routing conventions, and your engineering change process, then deliver a connector tailored to them. Under the hood it uses standard Business Central building blocks: table and page extensions on Item, BOM, and a new sync-mapping table; event subscribers on item and production BOM validation; job queue entries for scheduled polling; and the BC REST/OData v4 API (plus Dataverse where your PLM already integrates with Power Platform) as the integration surface. No core objects are modified — everything ships as an extension so your base app stays upgrade-safe through Microsoft's release waves.
The connector handles the hard parts engineering integrations usually skip: transforming an engineering BOM (eBOM) into a manufacturing BOM (mBOM) with phantom/sub-assembly logic, linking released drawings and documents to BC items, propagating PLM engineering changes (ECO/ECR) to ERP, and resolving conflicts when both sides edit the same record. Mapping rules are configuration-driven, so field mappings and transformation logic stay maintainable instead of buried in code. Dedicated permission sets keep the sync service account least-privileged, and every sync run is logged for audit.
Owns the integration between design tools and the ERP. Wants a single source of truth for part numbers and BOMs, no dual entry, and an upgrade-safe extension they don't have to hand-patch every BC release wave.
Lives in the gap between eBOM and mBOM. Needs released engineering structures to land in Business Central correctly — phantoms expanded, sub-assemblies in place — so production orders and MRP run on accurate data.
Manages ECO/ECR releases and document revisions in the PLM system. Wants approved changes to propagate to ERP automatically with effective dates and a clear audit trail, instead of emailing planners a change list.
Buy the license on ecosire.com and download the CAD / PLM Integration Connector module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for CAD / PLM Integration Connector, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Bi-directional item & BOM sync (CAD/PLM ⇄ BC) | ||||
| eBOM-to-mBOM transformation (phantoms, sub-assemblies, make/buy) | ||||
| Engineering change (ECO/ECR) propagation with effective dates | ||||
| Configuration-driven mapping & conflict resolution | ||||
| Tailored to YOUR specific CAD/PLM system & conventions | ||||
| Per-tenant, upgrade-safe extension (no base-object changes) | ||||
| Installed & supported on your environment by the builder | ||||
| Ongoing support across BC release waves & PLM API changes |
Typical delivery is 4–8 weeks depending on your CAD/PLM system and the complexity of your BOM transformation and field-mapping rules. We start with a discovery workshop, build the AL extension against a copy of your data, install it first on your Business Central sandbox for UAT, then deploy the signed per-tenant extension to production. This is a build-to-order engagement — there is no instant AppSource download; ECOSIRE installs and configures it on your environment.
Every build includes a warranty window after go-live for defect fixes at no extra charge. Because the connector ships as a per-tenant extension with no base-object modifications, it stays compatible across Microsoft's BC release waves — but we offer an ongoing support and maintenance plan that covers compatibility testing against new BC versions, CAD/PLM API changes, mapping adjustments, and enhancements. You always retain the source and the installed .app; support is a service, not a lock-in.
We build the connector for your licensed system — most commonly SolidWorks PDM, Autodesk Vault, and Siemens Teamcenter — using their REST/web service APIs or, where direct API access is restricted, a staging-layer export/import. We confirm the exact integration method for your system during discovery before any build begins.
No. The connector is delivered entirely as an AL extension using table extensions, page extensions, and event subscribers. It adds new objects and subscribes to standard events rather than altering Microsoft's base objects, which keeps your environment upgrade-safe and avoids the maintenance burden of customized core code.
Conflict behavior is configuration-driven per field. You can choose a source-of-truth side per field (for example, PLM owns the engineering structure while BC owns cost and inventory data), last-write-wins by timestamp, or route conflicts to a manual review queue inside Business Central. We tune these rules with you during UAT so the sync reflects your real data ownership.
Yes. If your PLM already syncs to Dataverse, we can bridge through it — reusing existing virtual tables and the BC–Dataverse dual-write rather than standing up a second independent pipe. Where there is no Dataverse footprint, the connector talks directly to the BC REST/OData v4 API. We recommend the right path during discovery.
A per-tenant Business Central extension that syncs your CAD/PLM system (SolidWorks PDM, Autodesk Vault, Siemens Teamcenter) with BC items, BOMs, and engineering changes — built, installed, and supported by ECOSIRE.