Showing posts with label Efficiency. Show all posts
Showing posts with label Efficiency. Show all posts

Wednesday, October 24, 2012

Why Use So-Called Working Views

When I get to work with people that have recently joined a firm that has been using Revit for quite some time the notion of working and sheet (or production) views is often confusing to them at first. When I first started to use Revit it was just me working on models alone. I didn't compete with anyone for other views.

Enter worksharing (worksets) and now we are sharing all the views of the project with any number of other people. The first view we fight over is the Default 3D view. I want it to show shadows in hidden line with ghost surfaces and Tony wants it in wireframe with all the walls off. The first one of us to make these changes will become the borrower of the view. The other will lose out, sort of. They'll get to see their changes (some kinds of changes, not all) too but Revit won't let them save the changes. They'll see a message declaring this too.

Revit was changed to deal with this conflict better by giving us our own 3D view, adding our Revit username to the default 3D when we create one, by clicking on the Default 3D button. They saw that users were creating and specifically naming their own 3D views that way so they figured, "Hey we can code that in!".

Over time we've learned that having some specific views for modeling activities versus those that we want to rely on for putting on sheets worked to our advantage. It also led me to write about the notion of Revit Roles that I've discussed here before (Modeler, "Documenter", Detailer, and Content Maker)

If I want to change the way a specific floor plan looks I really don't want to have to remember everything that was done to make it correct for the sheet it belongs to. It is easier to just work in a separate floor plan view instead, after all a floor plan is nothing more than a specialized report of the model. Of course View Templates make it much easier to restore a view's settings.

With 2013 View Templates get more aggressive too because they can be assigned to a view and take over many of the things we can alter, forcing users to edit a template instead of just using Visibility/Graphics overrides directly. The change actually enhances or increases the likelihood that working (modeling or personal) views will be useful. Working views don't need to be assigned to a view template because they aren't intended for sharing with others, putting on sheets.

Do you have to use working views and sheet views? No. Can it help improve your project experience, sharing it with others? Probably. It is more complicated, more views to deal with (check out the post by Phil Pleiss about managing views in the project browser), but it does provide the freedom to do certain tasks without the fear of messing up things that people often feel.

Friday, May 08, 2009

Clicking and Clicks

There has been some rather strong criticism in various places about the new user interface for Revit 2010. With regard to the number of "clicks" it takes to do something I'm afraid it is difficult to find fault with the logic that the new UI is less efficient compared with the same task in the previous release. Of course that is focusing on a single task as opposed to overall but still users get frustrated at very subtle things when they keep "poking them in the eye".

One example is the Objects Styles Dialog. This is where we control the overall appearance of the elements in our projects. We don't have to visit this dialog endlessly but we do visit it at various times during a day/week/month.

Old UI - Settings menu > Objects Styles (click count 2)
New UI - Manage tab > Settings button > Object Styles (click count 3)

Another example is the Export Settings for a dwg file. Again not a frequent stop for every user but some users like a BIM manager will visit this very frequently.

Old UI - File menu > Import/Export Settings > Export Layers DWG/DXF (Click count 3)
New UI - Application menu > Export > CAD Formats > DWG > DWG Properties tab > Build Button (Click count 6)


Note that this build button has no tool tip or explanation for what it does, no label. The click count is technically (6) six, though you don't have to click if you just hover over the Application menu items and move your mouse over the other options as they eventually display. So you don't HAVE to click but you ARE waiting.

I'm sure that "metrics" said that the typical user opened this dialog once in a "blue moon". So that user isn't affected or annoyed. The data leader for a project, the one who has to export to cad every couple days or the BIM manager who is setting up office standards for ten (10) offices and has to revisit them much more often won't find this new process very efficient. Considering that you have to start the Export process to get to the file to edit it in the first place!

In my view everything we manage, like these two, should be under the Manage Ribbon tab. Object Styles is, but it is under a pull down menu style selection which reintroduces a concept that the ribbon was supposed to eliminate?

Compare with Office 2007 and Word. The Ribbon in Word continues to grow toward the right when panels exceed the available space and an arrow appears at the right end of the Ribbon to allow you to scroll for more. This means there is no reason for a pull down type UI on the ribbon (yes it takes a click to scroll though)...every tool that we need to "manage" Revit settings/rules could have its own button and place on a panel.

It is too easy to dissect the user interface, at this level, and find examples. It should have been hard to find such things. Inefficiencies ideally should have been the exception, not the rule.

Last, I'm not an icon guy. I don't remember what little picture is which tool. If you turn off the labels for the tool bars in 2009 I'm lost, for a bit. I still can't tell you which picture is for which tool unless I'm looking at it right now. The fact that the Ribbon tools have words too is, for me, a life saver.