Construction engineering creates a document management problem that product engineering doesn’t have. In a manufacturing shop, a single team owns the CAD model from concept to production, revisions are controlled through PDM, and the end artifact is a set of drawings for a factory with controlled access to your files. In construction, the same drawing passes through a structural engineer, MEP consultants, a general contractor, multiple subcontractors, a building inspector, and eventually the owner — each with different tools, different naming conventions, and different ideas about what “current” means. The DWG file from the structural engineer needs to align with the Revit model from the architect and the IFC export from the MEP team. File management failure in this environment means someone builds from a superseded drawing. ...

You receive a STEP file from a supplier or another team. It opens in SOLIDWORKS as an assembly with hundreds of sub-components. Some of them are clearly bent sheet metal parts—brackets, enclosure panels, mounting clips. Your goal is to get flat-pattern DXF files for the laser shop. When you right-click a component and look for Flat Pattern, it’s not there. SOLIDWORKS treats every STEP-imported body as a dumb solid: geometry only, no feature tree, no bend data, no flat pattern. Even if the body was originally modeled as sheet metal, none of that intelligence survives the STEP format. ...

Dassault Systèmes announced over a dozen AI features for SolidWorks at 3DEXPERIENCE World 2026. The marketing materials show engineers describing geometry in plain English, generating drawings on demand, and having AI explain why a feature failed. Most of that is real — but the gap between what runs on your desktop today and what requires a 3DEXPERIENCE subscription is larger than the announcements suggest. This is a precise breakdown: which features ship, which platform they require, what they can and cannot do, and where API macros still outperform them. ...

A question posted on the 3DEXPERIENCE forum in August 2026 had zero replies after several days: how do you extract the version history stored in the PDM archive’s index.xml files into SQL for reporting or internal tooling? The poster wanted Document ID, archive folder path, actual archived filename (like 00000001), and the full version chain, including entries that use a ref pointer instead of storing their own copy. No answer existed. No Dassault KB article covers it. No public blog post addresses it. This is that guide. ...

A r/SolidWorks thread from August 2026 captures the confusion exactly: an engineer is trying to export a flat pattern DXF from a SolidWorks weldment to send to a tube laser shop. Every suggestion in the thread involves model edits, workarounds, or converting the weldment to sheet metal. Nobody points out the real issue — they are trying to apply a sheet metal export workflow to a part that belongs in a completely different machine category. ...

If bend lines stopped appearing in your DXF exports after a SolidWorks service pack update, you are not alone. The r/SolidWorks threads from August 2026 show multiple engineers hitting this after 2025 SP5 and 2026 SP3. Some had working configurations for years. They installed the update, exported a flat pattern, and the bend lines were gone. The problem is fixable — but only if you understand that bend lines disappear for fundamentally different reasons depending on how you export. Applying the wrong fix wastes time and leaves you thinking the issue is deeper than it is. ...

If you have found a tutorial that includes a line like ogr2ogr -f GFT ... or links to http://www.gdal.org/ogr/drv_gft.html, the tutorial is dead. The GFT driver connected to Google Fusion Tables, which Google shut down on December 3, 2019. The gdal.org/ogr/drv_gft.html URL itself no longer resolves — the entire GDAL documentation was restructured and the GFT driver pages were not preserved. Links to it from GIS community sites still circulate and lead nowhere. ...

A question on the SOLIDWORKS User Forum asks whether there is any way to automatically create an offset rectangle from a drawing view’s bounding box. Kevin Chandler — one of the most prolific responders on that forum — gives the short answer: “Auto? No, unless via the API.” That’s the entire opening for this post. The native UI does not support it. The API does. The use cases are real and recurring: inspection templates with a fixed clearance zone around each view, nesting documentation where each part gets a border at a set offset, supplier drawings where the view boundary needs to be marked explicitly for DXF nesting software. All of them need the same thing: a rectangle drawn in the sheet sketch, offset from the view’s outline, assigned to a controlled layer. ...

Moving CAD data to cloud is not the same as moving documents to cloud. A SolidWorks assembly references its component parts by absolute path. A drawing references a model. A PDM revision history records who checked what out on which date. Generic cloud storage (SharePoint, OneDrive, Dropbox) treats every file as an independent entity and breaks all of this silently — the files land in the bucket, the directory looks right, and then the first engineer to open a top-level assembly watches it rebuild with hundreds of “file not found” dialogs. ...

A SOLIDWORKS forum question asked this week: how do you model a curved sheet metal part, and do stamping structures require forming tools? The answer depends entirely on what “curved” means, because SOLIDWORKS handles three fundamentally different curved-sheet-metal scenarios with three different tools — and forming tools are a separate concern from the geometry of the base body. This post maps the decision tree. The Three Curved Sheet Metal Scenarios SOLIDWORKS sheet metal works by tracking a flat-pattern state for every feature. Every bend is stored with a radius, K-factor, and bend allowance so the flat pattern can be computed by unfolding. Curved geometry complicates this in three distinct ways: ...