So, going back to this thread I wanted to see if the sibling/sibling could somehow accumulate/rollup/sum qty's from siblings or if I should approach strategy differently?
I know that I can always throw sub/lab cost type under mat or vice-versa but I really would prefer to have all cost type resources on same level.
This may go back to the conversation I saw a few weeks ago about assemblies capturing MLESO cost types...

Anyway, just thought I'd throw the question out and see what came out - TIA
Can you throw a screen shot of the takeoff right pane and some of the formulas you used so I can noodle on this more.
The subcontract item/part is empty because I gave up trying...

@Kyle
OK, I took another look and I think I got it now
Probably going to approach differently now, but at least I got the concepts down I was looking for of traversing up/down parent/child. Learning usage was a fun one to wrap my head around this AM!
I appreciate you inspiring me to use the "Other" cost type as an assembly placeholder from another post.

