Onshape Naming Standards?

The last dedicated discussion I found on this topic occurred 5 years ago: Onshape Part Studio Naming - Technical / Onshape - Chief Delphi

With the explosion in Onshape use since then, I assume teams have gained more insights into good ways to name all the things, and it seems like a topic worthy of a fresh summer CD discussion. While I try to name things descriptively so it’s easy to search & find later, I would not say I have a good standard to recommend… hoping some of you do. Thanks!

3 Likes

The use of “-inator” as a suffix has lessened over the last couple of year.

8 Likes

We use a modified version of the 1678 parts tracking sheet to help with naming.

It’s pretty basic intentionally just

(Mechanism number)-(part number)-(part description as long as needed)

The document+folder tells you which robot it’s for, so we don’t need that in the part name, and we are rarely working on multiple years of robots at once.

10 Likes

We name our assemblies “[insert mechanism here]”. EX: “Elevator”, “Drivetrain”, “Pivot”, etc. We name our Part Studios “[insert mechanism here] PS”. EX: “Elevator PS”, “Drivetrain PS”, “Pivot PS”, etc.

3 Likes

2 Likes