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.