Introduction to the Revit 2010 Platform Seminar

**** UPDATE ****

WOO WHOO!! Are you as excited upcoming 2010 Platform Seminar with Scott Davis as Mira is? If so, we look forward to seeing you and please RSVP with Stephanie Murrell at cad@seilerinst.com so we can get an accurate count for lunch.

If you you are interested in attending this event, please RSVP with Stephanie at:

RSVP asap please to:
Contact: Stephanie Murrell
Phone: 816-518-1220 or
Call Toll free: 888-263-8918
Email: cad@seilerinst.com

If you have questions or comments, please contact Mirabela Ticu at 816-527-2438

You can also register as a member of the user group on our KCRevit Google Groups page.

---------------

Hey, you interested in learning about the changes to the Revit 2010 Platform? Want to know about all the new Features? What to complain about a new Feature? Want to see Phil Read wear a tie? Then you will want to attend the next meeting of the Kansas City Revit User Group. Scott Davis of Autodesk will be presenting an Introduction to the Revit 2010 Platform on April 17th from 11:30 to 1:30pm at HNTB (715 Kirk Dr, Kansas City, MO 64105).

Topics to be covered are new features for the Revit 2010 product line. Including Architecture, MEP and Structure. Inside these disciplines he will focus on the major development themes which were; User Interface, Modeling & Analysis, Performance & Operability and Conceptual Design.

We want to thank Stephanie at Seiler Instrument for sponsoring this event and providing lunch to all attendees. If your not familiar with Seiler Instruments, they are an Authorized Autodesk Reseller serving the Midwest. Stephanie will be in attendance so please make sure that you stop by and introduce yourself.

Keep watching the site and we will have more details to come.

For those that have not seen Phil in a tie, here is a pic.

























Chances are though, you won't see Phil wearing a tie though. With the upcoming release of the Revit 2010 products, he is wearing his Revit Implementation suit. See below.

HNTB and Solibri

Press Release


HNTB Architecture Inc. extends BIM capabilities by executing a firm-wide implementation of Solibri Model Checker v5.

Las Vegas, NV, December 3, 2008 - HNTB Architecture Inc. has selected the Solibri Model Checker v5 technology as part of its corporate initiative to advance the practice of BIM. “We are committed to BIM and are always exploring ways to improve the consistency and quality of our processes. Using the Solibri Model Checker will allow us to establish an internal BIM quality assurance program, where we can dramatically extend our model analysis capabilities, throughout the organization”, said Phil Read, VP and Director of Technology at HNTB Architecture.

Jonathan Widney, CEO of Solibri LLC (the US HQ of Solibri) stated, “HNTB Architecture is regarded as a leader in BIM and Solibri is a company that is totally dedicated to improving the quality of BIM analysis. This will allow us to work together to advance the BIM process and practices. We will continue to provide market leading BIM solutions, incorporating the needs and enhancement requests of valued customers like HNTB.”

For Solibri

Solibri, Inc. was established in 1999 to develop and market solutions that improve the quality of Building Information Modeling and make the entire design process more productive. Solibri is well recognized as the pioneer in providing out of the box software that automates the BIM Model Checking, Design Review, Analysis, and Code Checking process. Solibri’s customers include building owners and users, construction companies, architects and engineering firms.
For more information about Solibri, please visit www.solibri.com.

For HNTB Architecture Inc.
HNTB Architecture Inc. serves aviation, private, education, federal and local government clients across the nation. The employee-owned firm's design professionals provide comprehensive architecture services ranging from planning to design to construction services.
For more information about HNTB Architecture Inc., visit www.hntbarchitecture.com.

In case you haven't started reading it, Phil Read formerly of Autodesk Consulting has joined HNTB Architecture and started started a Arch | Tech blog. His latest post is on the weakness of the current Revit Warnings system.

In case you haven't started reading it, Phil Read formerly of Autodesk Consulting has joined HNTB Architecture and started started a Arch | Tech blog. His latest post is on the weakness of the current Revit Warnings system.

I used to be one of those users that didn't concentrate too much on warnings, until I started working with Daniel Hurtubise. It took Daniel all of a half hour to show me the importance of addressing warnings immediately. Yes, I know that is not always possible, but it is a good practice. (If you are a non-believer, send Daniel an email and I am sure he will provide you with a demo).

Since then I have been working with Phil and Autodesk Consulting (and yes they still have some assume talent there) on addressing warnings. While we have been documenting many warnings to provide the user with greater insight on how to correct them, the ability to access and track warnings has been lacking.

When Phil joined HNTB, one of the topics I was hoping would be addressed is the issue of accessing and tracking warnings and during the recent AIA Large Firm Roundtable BIM Implementors meeting, Phil let one of the Revit Architecture product managers aware of his thoughts about how the warning system could be improved ad what would happen if this didn't get done. So, I thought I would include the text from his blog.

One final note, Autodesk is monitoring his blog, so if you have a comment to make about the warning system, by all means comment.

Dear Anthony,

The cultural challenge with Warnings in Revit is the present lack of accountability. Users are smart enough to know there's something amiss in the file. But they have no idea where to point (or give) the finger. Or fingers.

Warnings also provide some indication as to the learning and experience level of members on a team. Warnings indicate when users have decided to work in a way that is expedient rather than deliberate. Reviewing Warnings allow people to learn from their own mistakes. Or better yet - they allow people to learn from another team member's mistake. ;)

Unfortunately, many users and teams tend to put off reviewing / resolving Warnings as there's no sense of ownership. This makes project management really difficult. By the time you need to review warnings - it's often too late. And who should fix what?

So I'd propose the following stuff with regard to Warnings:

1. Warnings should be maintained in a regular Revit Schedule. Stop hiding them in a dialog at the bottom of a Tools Menu.

2. Project Managers would like to know the Workset Username responsible for generating the Warning. This would allow Warnings to be scheduled per user name - which would impose a sense of accountability in the Revit database.

3. Original date / time stamp helps the team track the frequency of Warnings against project development.

4. Like any other Schedule in Revit , the ability to jump from line item / to context of project location.

5. Some indication of severity (for ranking purposes). All warnings are not created equal.

6. Counts / Totals / Types of Warnings. Now the project manager knows who (typically) on a team is responsible for the bulk of Warnings so they can remedy the situation, and prevent its recurrence.

Overall, this added functionality compels team members to preemptively fix what they have broken. Project Managers can quickly get a sense project dynamics. And the rest of the team isn't penalized with one or two team member's lack of discipline.