One-Line Diagrams

[rvellia]

schrodingerscat
jlondenberg
mwiggins

All 3 of you used Revit to draw your singe line diagrams. Look at how different they all look. I agree with some of the earlier comments that stated Revit single line diagrams would only appease 1% of the people. Every firm does their risers/one lines different. Some draw from the bottom and go up through the building.. some put the switchboards at the top and go down. Other use lines to show a bus, others draw the actual size of the switchgear. There are way too many options for Revit users to be forced to settle on one format. Even though it is b**tch to update your singe lines and plans, I think it is still better than being forced to show your riser/one line the way Revit chooses. Just my oppinion.

[Imwezal]

vmiller, I am quite interested on your method on how you did your oneline riser lines

[vmiller.210437]

I started with a detail component line based family. Draw a model line and attach it to the reference planes as well as the reference line. Then create and import shared parameters for size, type, etc.. Then use that component to draw single lines. Create a detail item tag and use the labels to point to your parameters. Similarly you can create detail component symbols that use the same tag and parameters. This is my first time writing any kind of tutorial so please let me know if it is not clear or you need more information.

[dbokmiller]

Just because you are using Shared Parameters does not mean that the information in the model is "linked" to the information in the diagram. You would still have to update the value of the parameters in each entity.

As for how Revit draws diagrams: It's up to you! There is no set way of doing it (just like with ACAD). If you don't like the way it looks out-of-the-box, then set your text and line styles to match your standards...

[vmiller.210437]

Just because you are using Shared Parameters does not mean that the information in the model is "linked" to the information in the diagram. You would still have to update the value of the parameters in each entity.

As for how Revit draws diagrams: It's up to you! There is no set way of doing it (just like with ACAD). If you don't like the way it looks out-of-the-box, then set your text and line styles to match your standards...

That is not true. For instance in my pipe family I have a shared parameter tied to size. If I update the size of the real pipe it tells the tagged one line to be the same size. This is very helpful. it will work with size, types, and equipment names.

[dbokmiller]

True, IF the tagged line in your one-line is the actual pipe.

What people are looking for is a way to build the model and have Revit generate a diagram (with linework) of the design, that is related to the model. This functionality does not exist.

[vmiller.210437]

I'm very close using a detail component as the line work so that is is able to be tagged and receive parameters. The roadblock is that I have not found a way to tie the detail component family parameters back to a schedule or look up table linked to the 3D system family. Any ideas if that is possible. I am still playing with it. I will post back if I get it.

[timsea81]

I do all my details in Revit as well as the 3D design, it is easier to manage if the whole project is in one software if for no other reason than batch plotting.

[sgermano]

I have been playing with this idea via api for a while now. I think it can be achieved via a external app to achieve this, but its a time issue of being able to do it and test it.

Im thinking of using tags that can be specified by the user (similar to making annotation tags now for object) this allows any firm to use their own symbology according to their standards just the way revit works now. Then allow the user to select the type of equipment that exist in the db and it will be linked to that particular piece of equipment.

So if I want to make a dict riser and have a fan at the top, I would drop in my companies 2d fan symbol and tag it by selecting from a list of existing fans in the model (could have filtering options here also). Then start your line work.

The trick is when following the pipe/duct through the api can be a little tricky to get the sizes...but you could always give the user the ability to select the "duct size" from a list of connected ducts sizes to that particular fan or ahu ect.

This will obviously not draw automatic, and nothing ever will, but in theory it could keep both the equipment and its ducts/pipes parametric with the system its connected to....

Im getting excited just thinking about it, now I just have to get time to program it! Anyone have about 3 weeks to program it?? Students maybe??

[timothy.braggs1]

I sometimes take my external objects/one lines/details and paste them into a detail view and drag that to my sheet/s as images.

Faster way?