Revit Keyplans – Can I Make This Any More Difficult?

Keyplans are one of those functions that I hope and hope and hope one day will have an easy way to get working in my project.

Right now, we have an 8 step procedure that we try to teach people how to use.  “8 steps,” I hear you saying, “That’s not bad.”  Except that each steps seems crazier than the last, and it involves multiple pieces of software, and the ability to edit families and understand parameters.  These are not easy Revit tasks, and the more I can keep our typical user away from them, the happier I am, but if I don’t show them how to make keyplans, then I have to make them, and that would mean less napping and looking at cats on the Internet!

Basically, our mess involves exporting the plan to DWG, tracing it to get the simple shapes, importing those shapes into a new Revit family, adding filled regions and text, making parameters to control the visibilty of the filled regions and text, putting THAT family into the border family, making parameters in the border family to talk to the plan family, then re-importing the border back into the project.

Still with me?

There are plenty of stops along that wild ride that you could do something different, but ultimately, to get the flexibility we need, the number of steps stays pretty consistent.

I don’t even know how a better tool would work.  Maybe some kind of Area Plan that can live on multiple sheets.  Maybe a view that has a designated area on the border.  Who knows.  All I know is, whenever someone asks me how to make a keyplan for their project, I hit the MUTE button on the phone, let out a deep sigh, and then tell them how to do it.

Then I get angry because I forgot to UNMUTE the phone first.

If someone has a nice easy way of Keyplans, I would love to hear it.

About these ads

9 thoughts on “Revit Keyplans – Can I Make This Any More Difficult?

  1. I couldn’t agree more, I follow more or less the same steps, except for the order maybe: I use a view template for a plan view where I adjust categories visibility using filters and detail lines / detail items when needed; then I put hatches and texts in this view directly; then I export to DWG with a specific keyplan setting -> Import in a Detail component family (I don’t usually put parameters in my keyplan because I already got everything I need as i wanted the moment I exported the plan view, but I see your point) -> last check and then insert the detail component family in a Legend view.

  2. The main problems that you generally have to solve with key plans are:
    1.Have them grouped together in the Project browser
    2.Have the drawing updated when the contour of the building changes to all key plans
    3.Have sections lines showing to keyplans and updating when they move.

    One solution may be to create an ordinary plan view and draw detail lines for the contour of the building and/or any other view specific geometry (eventually attached to peripheral wall geometry). Then you can apply a view template that only shows “section/elevation lines” and annotation lines (in order to have the contour geometry you just created).
    Then you can “Duplicate as dependent” the view to create several equivalent views and hide all individual section lines in order to create specific key plans for each section.
    In addition I create a project parameter for views called (view-use) in order to attribute the value of key plan to the key-plans an be able to group them in the project browser.

  3. It seems like everyone is creating their own “view-use” like parameter. We have a similar one. Your solution would definitely work, but I hate having so many views, especially when this feels like something that should have some built-in functionality in Revit.

  4. I know. I hate having too many views also.
    The idea of having the keyplans “duplicate as dépendent”, make them “stay together” in a way in the project browser. For us the most important issue was not to have to update the contour of the building and the position of the section lines of our keyplans. The disadvantage however of our method is that any new section line that you create will appear in the old keyplans and you have to manually turn it off on each separate keyplan view.
    I think that it will be nice to have:
    a. either a special view type for keyplans or
    b. to be able to put a same view in several sheets.

  5. I usually make a trick that seems to work for me:
    1. create the dwg version of the plan, export it;
    2. import in revit again, in a legend or draft view, with ONE or more region fill objects;
    3. create a detail group with it;
    4. place the detail group in one or more sheets. The Region Fill comes within;
    5. edit the group on the sheet, and remove the pattern from there;
    6. voilà! the region fill can be edited directly in the sheet. I keep the lines in the group, being able to change it everywhere. The Region Fill will be unique, and can be changed individually.

    Please let me know if this trick works for you too…

    Regards,
    João.

  6. I don’t use dwg…I just do a screen capture of the floor plan and use that image to trace over. The rest is the same…filled regions, visibility parameters, nest family in titleblock and connect parameters for control in the project through the titleblocl properties.

  7. I do like this solution for not having to rely on AutoCrap. Something else I will have to test out.

  8. We are in the same boat. Terrible workflow. Heaven forbid the footprint changes during the project and you have to start again. Arghhh!

Comments are closed.