Twelve machined parts laid out in a grid: gears, bearings, bolts and a gasket

Integrates with all the major platforms

EnCad sits beside your system of record. It reads; it never writes back. No migration, no new vault, no change to how engineers check in. Most deployments are live in three weeks.

How EnCad connects

Read-only EnCad

Database connection

An account on the system database (Oracle, SQL Server, PostgreSQL) brings in part records, revisions, BOMs and attributes, kept current through re-indexing.

CAD file access

EnCad works from the files themselves: native CAD, STEP and drawings, read from the vault file store. Geometry drives search, tagging and duplicate detection, so file access is always part of a deployment.

Mirrored share

For air-gapped and ITAR environments, your team syncs the vault files and part records to a share EnCad can read, on a schedule you control. No access to production systems.

Supported systems

SolidWorks PDM

Connects through the SQL Server database and the archive server file store. Reads parts, configurations, revisions, variables and BOMs.

Siemens Teamcenter

Connects through a database read replica and the Teamcenter volume file store. Handles multi-site, item revisions, dataset relationships and classification.

PTC Windchill

Connects through the Windchill database (Oracle or SQL Server) and file vault. Reads WTParts, CAD documents, EPM structures and lifecycle states.

Autodesk Vault

Connects through the Vault SQL Server database and file store. Reads items, files, revisions, properties and BOMs.

Autodesk Fusion

Connects through Fusion's API and design files. Reads designs, items and BOMs.

Onshape

Connects through Onshape's API and document access. Reads documents, parts, versions and release states.

Other systems

Aras, home-grown systems, network drives and generic file storage work too. If EnCad can read the CAD files and the part records behind them, it can index them.

What we need from you

  • Read access to the CAD file vault or a mirrored share
  • An account on the vault database for part records and BOMs
  • One IT contact to work with our engineers during week 1

That is the full list. No API keys, no vendor professional services, no changes to your system configuration.

Enterprise setups

Multiple instances, acquired libraries and multi-site deployments are indexed into one searchable library with cross-system part mapping. On-prem and customer-VPC deployments keep all data inside your network.

Not sure how your system would connect?

Book a 30-minute technical call with our integration team.