control & saw cut joints in concrete slabs

[cbaze]

How are you guys handling these & distinguishing between the two? Just a model line? Would there be any way to put a void in the floor & schedule the length?

[Ben-May]

Model lines are generally enough to show the layout in plan view

If you do want to goto that level of detail with showing the joint in 3D, with 2011 you can now cut elements with nested voids within a family

So with a line based generic model based family you can have a void sweep

Once in the project you will just need to cut the floor to the line based family

If you add a shared reporting parameter into the line based family you can then schedule the length of the joints

You could also use this same workflow without cuting the slab, with simply a model line built into the family which will still allow you to schedule the length

See attached for a quick workup of the idea

[Twiceroadsfool]

We use a line Based Family. Best of both worlds. You dont want to technically REMOVE the Concrete, because it IS getting poured. And... you can schedule its length, and it shows up as a modeled element. Perfection.

[jh75]

I was looking at doing this to ie using a line based family and then embed a detail component for my sections. The problem is when you have warped slab.

J

[Twiceroadsfool]

I was looking at doing this to ie using a line based family and then embed a detail component for my sections. The problem is when you have warped slab.

J

Warped slabs are going to be a problem with every solution, excluding Symbolic (detail) lines, and a void tearing through the thickness of the entire warped floor...

[cbaze]

I'm buying into line based families for Saw Cut Joints. How about construction joints though? It seems that parts are perfect for this because the geometry will already be divided up for visualization/scheduling. One big limitation is that you can't schedule the length of the part cuts (bulkheads). A workaround may be to calculate part perimeters somehow? Then you could add them, subtract the original family perimeter, and divide by two.

[Twiceroadsfool]

Parts are great, in theory, but the way they were incorporated in to the program sucks. Parts should have been their own tab: Model, Annotations, Imports, Parts. Them being an all encompassing category, with subcats for "originating category" makes them a chore to deal with, since they are ALSO to be dealt with at the View PROPERTIES level.

Besides, we typically dont bother splitting up construction joints in Revit, since we use Synchro for our Scheduling, and Synchro works off a DWF export, and can split individual components up on its own. Plus, we can do it in a DWF export with a section box, which has proven to be the fastest way period, for slabs, anyway.