Closed julianstirling closed 5 months ago
I don't think anything in the data flow precludes this, but it will probably be easier to make the shelves into sub-assemblies along with their components, screws, etc, and then have the entire rack be built of shelf-component sub-assemblies along with the odd bits that are left over (top and bottom plates, rails, screws to fasten sub-assemblies to rails, etc). This could imply a matching hierarchy in the data.
into sub-assemblies along with their components, screws, etc, and then have the entire rack be built of shelf-component sub-assemblies
:100:
Totally agree!
I'm closing this as we have have a plan. I'm sure the plan will be updated as we find the issues.
We need to make sure that the correct data is available to each step of generating the hardware and instructions. A first approximation is that the following data is needed for the three main steps:
I think the easiest way to do this is some sort of heptarchical object-based structure. Very simplistically this will look somewhat like:
This way the orchestration can:
Shelf classes