Illustrative previewA 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.
What is CAD / PLM Integration Connector?
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. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
About this Product
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.
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.
What you get
- A per-tenant Business Central AL extension (.app), built and version-controlled, installed on your sandbox then production environment by ECOSIRE
- Configured connection to your specific CAD/PLM system (SolidWorks PDM, Autodesk Vault, or Siemens Teamcenter), including authentication and endpoint setup
- Field-mapping and conflict-resolution configuration captured from a discovery workshop and tuned during UAT
- eBOM-to-mBOM transformation logic implemented to your make/buy and phantom conventions
- Permission sets and a dedicated integration service account configured with least privilege
- Job queue setup for scheduled sync plus admin pages for mapping, logs, and failed-record review
- Deployment runbook, integration architecture document, and an admin/operator guide for your engineering IT team
- UAT sign-off, go-live support, and a defined warranty/support window with options to extend
Who this is for
Engineering IT Lead
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.
Manufacturing / Production Planner
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.
Engineering Change / PDM Administrator
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.
How CAD / PLM Integration Connector Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Dynamics 365 Business Central Native |
|---|---|---|---|---|
| Bi-directional item & BOM sync (CAD/PLM ⇄ BC) | Included | Partial support | Partial support | Not included |
| eBOM-to-mBOM transformation (phantoms, sub-assemblies, make/buy) | Included | Partial support | Not included | Not included |
| Engineering change (ECO/ECR) propagation with effective dates | Included | Partial support | Partial support | Not included |
| Configuration-driven mapping & conflict resolution | Included | Not included | Partial support | Not included |
| Tailored to YOUR specific CAD/PLM system & conventions | Included | Included | Not included | Not included |
| Per-tenant, upgrade-safe extension (no base-object changes) | Included | Partial support | Included | Included |
| Installed & supported on your environment by the builder | Included | Not included | Partial support | Not included |
| Ongoing support across BC release waves & PLM API changes | Included | Not included | Partial support | Partial support |
Frequently Asked Questions about CAD / PLM Integration Connector
How long does delivery take, and how is it installed?
Typical delivery is one working week 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.
What does ongoing support and updates look like after go-live?
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.
Which CAD/PLM systems do you support?
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.
Does this modify my Business Central base application?
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.
How are conflicts handled when both CAD/PLM and Business Central edit the same record?
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.
Can it work with our existing Dataverse / Power Platform setup?
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.
Related Modules
Automotive Dealership & Workshop for Business Central
Vehicle sales, parts inventory and service workshop management for auto dealers and garages, built as a per-tenant AL extension on Microsoft Dynamics 365 Business Central and installed and supported by ECOSIRE.
Bank Reconciliation & Open Banking Feeds for Business Central
Custom-built Business Central extension that pulls bank statements over open-banking APIs, matches transactions with AI, and posts reconciliations and payment journals automatically — installed per-tenant and supported by ECOSIRE.
Central Kitchen & Catering Operations
A build-to-order Dynamics 365 Business Central extension that turns confirmed catering orders and cloud-kitchen demand into costed recipes, day-part production runs, ingredient purchase plans and delivery waves. ECOSIRE builds, installs and supports it against your Business Central tenant after a scoping call.
Cleaning Services Management for Business Central
A build-to-order Dynamics 365 Business Central AL extension that runs recurring cleaning job schedules, site checklists and inspections, supplies consumption, staff hours and contract invoicing inside your existing Business Central company. ECOSIRE scopes, builds, installs and supports it — it is not an AppSource download.
CAD / PLM Integration Connector
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.
- 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