Tuesday, November 25, 2014

SCRUG 11/20/14

The maturity of SCRUG has become a recurring topic at recent meetings. The South Coast Revit User Group was founded and had its first meeting in December 2000. At that time the meetings were held quarterly and nearly every presentation was given by one guy, Jim Balding. Autodesk was the sole sponsor, thank you Chuck Healy. SCRUG was the second Revit User Group formed and it has lasted. The one group that was formed earlier has since disbanded.The meeting this month was a sort of celebration of usergroups and what this particular group has become.

Autodesk demonstrated the Point Layout system using a Total Station, Prism and Ipad. The main benefit being that one can now create points in the Revit software or in the field. One can use the real world to create layout points. Revit now has the ability to embed layout points inside families. One may authorize users to create or control points. Thus a group could divide the work and record site conditions or create a layout for walls, or grids. The information could be combined with project Glue

Part of the meeting included extolling the benefits of user groups and user conferences. 

Nicholas Kramer presented Tips and Tricks and Jokes from the Revit Technology Conference North America. The RTC events are like trying to present four years of user group meetings over three days. Some highlights included SCAN to BIM tip to keep your section box small to increase performance, adding required clearances in families to a sub category (and standardizing on the naming of the subcategory company wide, i.e. "clearance", "Clearance" and "CLEARANCE" are all considered different in the software), shared coordinates, combining model with drafting patterns, using components with tags to do detailing vs lines and notes, organizing your groups with prefixes, locking the profiles in your mass families, using sub parameters for formulas (like a mini spreadsheet), an override summary for Revit object visibility, adding notes to your Revit Template to help users remember how to use what, linking parameters to host families and too many other tips to mention.


Carla Edwards presented the benefits of the BIM Workshops. Some of the tips from their events include: Steve Stafford's library analogy, definitions of survey point vs project base point, supernudge (hold down shift while nudging), reference planes have a direction, and using Bluebeam to compare documents (PDF the old and the new and Bluebeam highlights the differences). 

Vendors presented their wares. Notably there were two "collaborate in the cloud" companies. They offered great solutions for those working live across multiple offices. 

Knowledge Trax presented their system for evaluating the Revit knowledge of users. They have pre assessment testing, recommendations of training to fill knowledge gaps, and post training assessment. It looks very effective. Nick brought up that it is very good at flagging people that do not follow written directions. Purchasers of their services can use pre-baked questions and training or create their own. It is much more cost effective and consistent than having someone in house create an evaluation/assessment/training system.

Also of note, Solibri  played a short video and shared their marketing strategy. Solibri software is a model review software. There are two steps, decide what rules to use and check the model against those rules. The software uses embedded information the model to conduct the review. One example is a door and its required clearance based on accessible requirements in the International Building Code.  However, one can write one's own rules. Does the client want rooms named "office" to have specific dimensions? Solibri can check the model and report violations. Solibri is marketing this functionality toward jurisdictions that need to check plans. Building departments worldwide could accelerate plan checks. The review the violations part of the software is well developed. One can make a series of "slides" into an HTML document with live links to views of the model. The views of the model are automatically marked with visual references to the clearance available and the required clearance. Powerful.

Perkowitz+Ruth Architects provided four laptops with Revit 1.0 installed for a design challenge. Revit 1.0 was FAST on those laptops. 

I would be remiss if I did not mention DOOR PRIZES. Thousands of dollars changed hands (when you count the drinks, gift cards, electronics and software). Thanks to Newport Rib Company, US CAD, Kelar Pacific, Microdesk and the other vendors. 

While I did not stay past 9pm, the portion of the meeting I attended was intense fast paced and amazing. I plan to stay a member of this group and attend future meetings. 

Saturday, October 4, 2014

SCRUG at BIM workshop

On September 25, 2014, the SCRUG meeting was held after the first day of the BIM workshop held at the Anaheim/Garden Grove Wyndham Hotel. I know I've missed a couple of the last meetings; this meeting was definitely not one to miss. There was a panel discussion about Building Information Modeling, BIM. I apologize for not getting the names of all the panel participants. You may leave you name in the comments below and I will update the post. While this is a long post, it is not meant as a verbatim transcript of the event. It is one architect's perspective of what occurred. Please enjoy.

The discussion focused about coordinating during design between the different disciplines using BIM. For example, you have architectural, mechanical, structural, electrical, plumbing and civil. Our panel discussion included people representing most of those and we also had people in the audience to represent the contractors. The discussion started out with workflow. When is it best to bring the consultants into the process? Design is traditionally driven by floor plans. While the plans are in flux, it is problematic to decide on the size of structural members or the space to allot for electrical rooms.

One of the difficulties that we often have in the design professions, is that the designers don't  work in the same software as the people documenting the design. The question came up what do we do about SketchUp? Should SketchUp be treated just like trace paper or bum wad? Or is SketchUp treated as the gospel truth of design?

One of the challenges of the production side of design is taking that SketchUp model that undefined series of shapes and rationalizing them into something that is documented for the construction professions. One of the challenges along this line is that the design team often wants to stick with the SketchUp model and that means two different models: one by the design team and one by the production team.

Nick Kramer shared his experience in China that oftentimes things are done very differently from here in the United States. In some cases in China the construction actually begins before the owner has title to the land. It then becomes an arguing. To the government which basically owns all the land hey we've started building give us permission to finish. I think as a group, SCRUG feels that the SketchUp model is a sketch. It's sketchy; it is not to be taken literally.

A question to our group of about 24 people (design professionals, re-sellers and contractors) was what's the expectation when does the lead profession require their consultants to start modeling? There were a couple of different answers. Ideally, we would have the consultant start right away with the model, however, while the design is still in flux, it triggers rework on the part of the consultants with each new design. Essentially. the architect wants to cut a section and see if the design works. Are there conflicts? Will everything will fit in the space allotted? From my experience, I remember many projects adding on square footage to fit the electrical room or mechanical room. It is even happening on projects I manage now.

A lively part of the discussion centered around civil engineering and documentation. As an architect, getting the civil right is critical. The interface between the design parts - civil, electrical, plumbing, accessibility, structure and architecture is the difference between a successful project, on time and on budget and one riddled with delays and change orders. One of the civil engineers spoke to this issue on the panel. He said frankly that the civil tools presently are not at the same level as the Revit tools. That the civil tools, meaning specifically Autodesk Civil 3D, does not have accuracy to a shop drawing level. Often, architects want the point of connection at the same level or just to know what the level is so that we can verify that our plumbing drawings will be able to make the amount of fall that we need for the sewer connection.

The history of Civil 3D is that Autodesk bought it and developed that software. They transitioned all of their civil customers to Civil 3D from AutoCAD just a few months before they bought Revit and decided to spend a lot of resources on it. Autodesk could not in good conscience and with the support of their customers switch every civil license (about 75,000) from Civil 3D to Revit in such a short a time. Civil 3D has been developed on a more less a parallel track is Revit.

The beginning of the recession in 2007 and 2008 severely affected the civil profession. One civil engineer commented that the civil engineering profession shrink their offices, laid off employees and stopped buying new software and in some cases switched to hand drafting because they were in survival mode until nearly 2014. The fact of the matter is that most civil engineers do not work in three dimensions there a pipe networks are usually two-dimensional lines shown in plan and then they do a separate set of drawings to show the profiles and that each individual. That has to have an elevation that's done by hand and adjusted individually as needed. For the Civil Engineers that do work in three dimensions the exporting from Civil 3D to Revit is not a satisfying experience in some cases its just a sweep in AutoCAD in most cases it does not translate well. Civil engineers day don't like they don't work having continuous daily updates to a project team. Often times not just civil engineers but other professions as well will only export at milestones for coordination. That's works fine for smaller projects before large complicated projects it can be problematic.

Now some requests for proposals are asking for the civil engineering to be done three dimensionally for three-dimensional coordination.

The question came up on ways that we could maybe get a little bit more from civil; something that would be easy to coordinate in Revit and one suggestion was for each. Of connection for each critical point along the slope to have the civil drop in a 1 inch high 1 inch diameter cylinder at the right height. That cylinder when brought into Revit could then be scheduled and tagged. We want as a profession to make it easier for the people in the field to find their critical points. Where is the top of the pipe? What are the coordinates? Civil 3D includes a point of connection tool, however like many tools in many bits of software, very few people take full advantage. One civil engineering firm spoke up saying that they are looking at Revit work as a new revenue stream. They are taking Revit and using it to do as builts for clients. They take all of their potholing information instead of doing it 2D, as is tradition they are doing it three dimensionally using the Revit tools. They think of the model as being a 3d puzzle. And their model then becomes a tool for the long-term.

One point of information: Landscaping consultants often sub out their irrigation drawings.  Landscape Architects just focus on squares and circles to show the different types of plants and the over all areas; the actual plumbing is done by someone else.

Another point of information, in reality, design teams have to go to the lowest common denominator which in a lot of cases is AutoCAD. I have a consultant I'm working with and the version of AutoCAD they use is 10 years old. What winds up happening is the design team at the start of a project has to agree which version of software to use. On a long-term project most teams lock in their software right at the beginning. That may mean by the end of the project there using a version of software that is 6 or 7 years old. Some owners are actually rewarding companies that will not upgrade to the current software. That makes it difficult for those that stay current. For example the Irvine Company they just reward laggards they say well we'll be using an older version of software for the duration of the project.for projects where you want to upgrade in the middle, there is the danger that the upgrade translation portion of the software may break your model it may screw up the images or something else in the project. It was mentioned that one consultant may give you an additional service charge for upgrading in the middle of a project. That may cost between $500 and $5,000 in additional fees.

Autodesk is now offering a way to rent software. The rental of software has you locked into whatever the current version is and you can't use older versions.

The question a design team has to ask each consultant at the start is,  "are they equipped to do the project?" Eventually the prime in each project will need to start asking or in many cases telling the consultants, "if you want to work with us you need to be on subscription or you need to use this version of the software."

In speaking about the efficiency of using BIM on a project it may take about five to seven projects using the same team members have a sweet spot.  Those first couple of projects maybe you'll break even, maybe you lose money, but by the end of that process you will have a great team that will do great work. For companies or design teams with frequent turn over, they will be perpetually inefficient.

One of the real life situations about upgrading between versions of software or staying with older versions of software is a correction factor. One person said that in their projects there's about a five to seven percent correction factor. Companies have multiple versions of software installed and projects using different versions of software. They will often have to resort to back ups when projects are accidentally upgraded. They will use work arounds to copy work from one project to the next.

A note on the food: The pizza served was the best pizza I've had at a SCRUG meeting. The BIM Workshop mixer before the meeting had great food and plenty of it.

In the interest of timeliness, I am publishing this first draft "as is". I look forward to your comments and perspectives.


Friday, April 18, 2014

SCRUG 4/17/14

Qatar - 2022 world cup. Jay Holland gave a report on the largest BIM project currently in design or construction. KEO International Consultants is managing the design team, which includes AECOM London. The software used to generate the design ranges across the gamut. In the end the client, Government of Qatar, requires an Autodesk Revit deliverable. Jay's presentation included a Sketchup walk through, Rino model, and Solibri model. The design he showed is progress from their schematic phase. The final Schematic Design is due in July 2014.

A bit about Solibri: (like Navisworks you import models and files from other programs), you can examine clashes between models, it uses the IFC model format, you can examine model integrity, it is a rules based software, you can examine naming conventions or adherence to other standards.

Interesting fact about Qatar, the government provides city wide chilled water. Qatar has an estimated 200 years of Natural Gas reserves.

While the showing off of projects are a staple of many a SCRUG meeting, the real meat is showing off features in the software and teaching how to make it happen. Marcello Sgambelluri provided a work in progress version of his next AU presentation.

"Dynamo 101"

What is Dynamo? What can Dynamo do? How or why would I use Dynamo?
Marcello gave us the official Autodesk version and his own version. In the end, the vast majority of users do work on standard buildings and just want to do something that the GUI of Revit won't allow or makes difficult. Marcello is an expert on finding out what Revit can do and which tools to use to get the result you want in the shortest number of steps. 

Dynamo is a programming language with a Python back of house. The front end of Dynamo is visual - boxes with text and wires to connect the text. In typical programming you have to get the text exactly correct or it does not work; error checking and debugging are a fact of life. In Dynamo it is easy to see that there is nothing connected to the "input" or "output". In Dynamo you do not need to name variables. The "boxes" or "nodes" are modules of Python code that do something. Autodesk creates new boxes and releases them every day. Others are allowed to create custom boxes you can download and use them. You can create your own. 

Dynamo can:
  • Create moving pictures in your Revit model
  • Grab and change parameters
  • Pick an edge that Revit won't let you pick
  • Create complex geometry
  • Eliminate "work arounds"
  • Access ALL of Revit's parameters
  • Reorder things
  • Renumber things
  • Create sheets from an Excel spreadsheet
  • Create rebar inside a concrete column and schedule them
  • Attach a beam to the underside of a curve - and update it automatically
The reason to use Dynamo is to save time and increase accuracy. 
The most productive way to use Dynamo is dual screen - go back and forth between Revit & Dynamo.
Dynamo is the future of Revit.

Thank you to Jay, Marcello, US CAD, Microdesk and Keller Pacific. 

Thursday, March 27, 2014

SCRUG 3/2014

Autodesk formally launched its campaign to enlighten the masses about the benefits of Revit 2015 today. SCRUG was all about the new features. We were graced with the presence of Steve Stafford - Mr. Revit OP ED. He had on an Autodesk vest and presented the official Autodesk Powerpoint (cleared by Autodesk Legal Department) as if he was Scott Davis Autodesk Employee.

Many other blogs cover the feature list, so I will not repeat that here. There was not any thunderous applause for any single feature or the lot of them together. Many of the features added polish to existing parts of the program. One of my personal highlights was a demonstration of adding a shared parameter to a view title. It is not an earth shattering feature, but a nice to have feature. One of the features, opening up a dialog box when one tries to delete pinned objects, functioned a bit unexpectedly during the demonstration. You cannot delete a pinned object, but if you delete the pinned object's host there, Revit says nothing and both are erased.

Overheard... Cyberpower PC's gaming systems are a good fit for Revit. GSA is looking for a National BIM Director (Contact John Russo for more info). A local BIM conference passed out flyers. BIG BIM Theory is having a BBQ.

Thank you to the sponsors. US CAD, Keller Pacific and Microdesk.

Recent Architectural Projects

  • 2013-14 Facilities Support Center LEED submittals, NASA AFRC
  • 2013-14 Maguire Aviation Hanger, Van Nuys, BASCON
  • 2013-14 Fullerton Municipal Airport Terminal Remodel, City of Fullerton
  • 2014 DEA Fire Alarm, GSA Los Angeles
  • 2013-14 Fuel Farm, NASA DAOF