...

This where the custom PCBs are stored, the ones designed by the electrical team. If the PCB can be bought OTS then it belongs in the OTS folder. This folder does not need to keep the STEP file, just the optimised PCB sldprt file (Creating Lightweight PCBs)

Renders

This folder stores everything render related with the sub-system

discrepancies

Science

The science mechanism has several sub-categorizations of parts but lack a sub-system assembly. It is best practice that assemblies are always a higher level or same level as part files (in terms of folder directory). Since certain assemblies draw parts from several different component folders the assembly has been moved into the root of the sub-system folder and all the component folders moved to the top level.

In future, all components should be grouped in one components folder, or create a sub-assembly folder with its own isolated assembly.

Image Added

Chassis & Arm

This sub-system is a perfect example of a (relatively) well organized sub-system with its own recursed sub-system.

Below is a screenshot of the chassis folder and then the Frame folder. Note that a recursed sub-system generally only needs the Archive, Components and OTS Components along with the relevant assemblies. This also generally means that there are no components which don't belong to just the sub-system (not sub-sub-system) so no need for a Components or OTS Components folder in the Chassis folder.

Image AddedImage Added

The only difference with Arm is that there are more recursed sub-systems than chassis.

Current limitations of the folder structure

• Little space/freedom for prototyping CAD: setup in a way that all files should be used in the final product. loose/floating parts and assemblies are undesire-able undesirable and archived. - need a space for prototyping
• naming convention (not described here) is not configuration friendly (each part should have its own file name/number)
• nuances in several locations which bugs me. it is not 100% consistent. - this arises from shitty documentation, everyone doing their own thing and no over-arching guidance/coordination