Last week, the forum buzzed with discussions around common challenges and best practices in CAD workflows. Members shared insights into file naming conventions, debated the intricacies of parametric checks in ShipConstructor, and explored how to ensure quality in IFC exports. There was also curiosity around industry standards for drawing revisions, which sparked a lively debate.
This Week’s Hot Topics
When FINAL_v12 meets FINAL_final_v12b
A humorous yet all-too-relatable thread where members shared their struggles with file naming chaos. It’s a reminder of the importance of clear conventions to avoid confusion in project management. Read more here
Parametric SOLAS checks in ShipConstructor
This discussion drilled into the technical details of implementing SOLAS checks in ShipConstructor, offering valuable tips for those working in ship design. Read more here
Lightweight checks before IFC export
Forum members discussed strategies for performing lightweight checks before exporting to IFC formats, emphasizing the balance between thoroughness and efficiency. Read more here
Why drawing revs skip I and O
A curious look at why certain letters are omitted in drawing revision sequences. This thread offers insights into industry practices and standards. Read more here
Thanks for staying connected with our CAD community. Your contributions and curiosity drive the discussions that enrich us all. Until next week.
We cut naming chaos by locking filenames to a simple pattern and keeping revs out — “the filename should never lie” — then using a PDM check‑in rule to reject off‑pattern files. Caveat: for external PDFs we append -RevX on publish so email threads don’t implode; herding cats became herding one cat.
Switched to auto‑generated, ID‑first filenames (PROJ-DS-000123) and keep rev/title in properties, building on @hmoore99’s “filename should never lie” — stops filenames breeding like rabbits. A tiny pre‑check blocks spaces and duplicate IDs; without PDM, the ISO 19650 pattern works in a pinch but gets rigid on multi‑discipline packages (https://www.ukbimframework.org/).
Quick example: for our weekly IFC exports, we run a tiny pre-export script that copies models to a “staging” folder, normalizes names (no spaces, zero‑padded IDs), and aborts if any two would collide. It cut cleanup time a ton and costs nothing to maintain, but it won’t catch broken xrefs across disciplines, so we still do a quick visual pass before publishing.