What databases add to CAD
- Standard part catalogues: fasteners, bearings, profiles, valves with all sizes and properties.
- Design rules: allowed combinations, clearances and material limits.
- Project data: equipment lists, tag numbers, cable and pipe schedules.
- Asset and facility data: linking drawings to physical assets.
- History and reporting: what was designed, when and by whom.
Architecture options
| Option | How it works | Best for |
|---|---|---|
| Direct connection | CAD add-in queries the database directly | Internal networks, small teams |
| Web API layer | Add-in calls a REST API in front of the database | Remote users, security, multiple apps |
| Local cache | Data synced to a local store for offline use | Field or site engineers |
Example: tag-based equipment placement
1. Process engineer maintains equipment list in database
2. Designer opens "Place equipment" in AutoCAD / Revit
3. Add-in lists unplaced tags with sizes and data
4. Designer places block / family; attributes filled from database
5. Database records drawing, location and status
6. Reports show placed / missing equipment per areaTechnology choices
We typically use Microsoft SQL Server, PostgreSQL or MySQL, accessed through .NET (Entity Framework, Dapper) or a REST API built with ASP.NET Core or Node.js. For small single-user tools, SQLite is often enough.
Good practices
- Give every CAD object a stable ID that links to database records.
- Keep the database as the source of truth for non-geometric data.
- Handle conflicts when several users edit related data.
- Back up and version reference data.
Geometry lives in CAD, information lives in the database, and integration keeps them in step.
Database integration with ENGIMANDI
We build CAD add-ins backed by SQL databases and APIs. See API development, web applications and CAD integration.