Wednesday, June 27, 2012

Small Groups, Large Groups, Red Crowd, Blue Crowd… AU Conference Presentation and Teaching Tips


Now that I know I’m headed back to Las Vegas for Autodesk University this year, it’s time to pass off some ideas about how to have a successful class. Whether you’re a first timer or an old dawg, you’ve got to understand that presenting at a conference isn’t the same as a regular training class, or presenting to your buddies in the office. So let’s start with a few things that help your classes get high marks.

1.       Know Your Audience

If you’re a beginner, intermediate or advanced instructor, this is the most common mistake. Don’t teach symbiotic quantum physics to first year AutoCAD users…and it may sound silly, but keep it simple. You’re not there to impress them with your prowess or command of the English language. You’re there to communicate ideas, instill excitement and passion, and motivate the learner.

The AU crowd, for example is a little different. They’re a highly technical bunch, but they also are in Vegas…yes, Vegas has them now. And in most cases, they have a fairly good understanding of how the tools they’re using work, but are looking for the gems and tips they can’t find in the books or help file. When they signed up for classes, they were looking at your description and skill levels. So whatever you’re teaching, you need to stay in that general playground.

The key is to make sure your topic is something that is valuable to them. Cruise the discussion groups, talk to coworkers and check out the blogs to see what people are looking for. Since you’ve already submitted your class, make sure you tune it as needed so the information is relevant. Even if it’s advanced class, you’ll always get a few lost souls that probably didn’t mean to sign up for your class, but could really benefit from the topic.
                                                                                                                                                       
Know the Audience, Part 2

If you’re presenting for a first time, it can be daunting. I was so nervous in my first AU class, I kept tripping over the screen stand legs, which unfortunately stuck out about 3 feet in front of the screen (appropriately the class was about interference conditions in AutoCAD MEP). Get out and literally get to know your audience. If all you do is stand in front of the podium, your first contact occurs when you begin to speak. I like to walk around the room, introduce myself, talk to the users, even meet some outside the door (I’ve also been known to take tickets and charge admission…oops, probably shouldn't have said that). Ever notice how it’s easier to talk to friends than a large crowd?

This requires that you make sure you get into your presentation earlier, so have everything setup and ready to go well before the presentation. Make sure the software is open to files you’re using, your presentation is loaded. If you’re speaking at an event where there’s dinner or lunch being served, don’t sit by yourself – or even with friends. Sit at a table with people you don’t know and at least introduce yourself. You’ll find it’s easier to connect with people before the presentation than during.

2.       Preparation - Practice, Practice, Practice, Practice, etc.

There’s a big difference between knowing something and owning something. As much as I present, even the same things, it’s still a good idea to go through the presentation – night before, etc. I used a short script prompter, which contains the key points and sections. I leave it on the table where my laptop is, if I’m driving, since this helps me stay on course.  But no script keeps you from flubbing if you haven’t gone through everything. I had updated my computer before AU, but didn’t run through the steps in the exercise – my path to the lookup tables for pipe fittings in Revit was wrong…boom – but we turned it into a teaching moment, and showed the class why it broke. That’s rare, but sometimes you have to make quick adjustments. Try standing in front of the mirror – watch your facial expressions, hand movement, body posture – but nothing exudes confidence like owning the material. And never, ever, ever rewrite material the night before. Make sure you deliver exactly what you say you’re going to deliver – set the right expectation for the class.

3.       Relevant Topics – Stay on them.

As much as you may want to teach lisp programming that sets layers to an Architecture crowd at AU, that may not be what the crowd is really interested in. Find something that’s current and fresh – don’t dwell on how you did things in the past, unless you’re using it to define context. For example, a great expression is “I used to do this way, but then I learned a better way”.  And always credit the person who taught you – it shows humility, and respect.

4.       Presentation is everything!

At Bobby Flay’s Mesa Grill, in the Bellagio hotel, it’s all about presentation – getting the fries to be fluffed up a specific way so they look enticing.  A former co-worker of mine, David Garrigus, was a big inspiration – the ball and chain demo on ACAD 2000 was one of the best. You may have a style, but you can’t rest on it. You can keep the style, but change it up – do something different at every event. I may have fishing videos before the class, but every year I bring different props.

One of the things that drives me nuts is a presenter who hides behind a podium or desk, and doesn’t stop and step out. Engaging the audience is mission critical at an event like AU. You want them to share how you feel about what you’re teaching, but say it a little gently.

We even did the dating game once – but I won’t ever do it again. Judge the response – if it works, tweak it. If it doesn’t, run away from it. Don’t be afraid to ask people what they think – but also don’t be depressed if your presentation gets trashed by one or two people. There’s always a critic that thinks they can do better, or wants a specific presentation. Most important – be yourself.

5.       What to do when Things Break Down – and They Will!



Beware – if some disagrees with you, and they will, never trash them or their idea. Say something like, “I hadn’t thought of that, but it sounds interesting.” Many times, and unfortunately, there will be someone in the group that wants to bring you down a notch. Don’t ever play into it – better yet, try to deal with it after the class, and stay on track, so you can finish what you need to cover.



If something crashes, don’t dwell on it – even in a lab, you can still step out, and talk about what you’re trying to accomplish. One of the things I do is keep presentation or lab files saved at critical points, so a user can pick up and keep moving if they get behind, or worse, if something breaks.



And I’m a little superstitious – I always bring two laptops with me, just in case. But Autodesk is great about providing powerful desktop systems that you can use. One of the reasons I get to AU on Sundays is so I can spend time in my labs on Monday, and make sure all of the datasets are current and correct. I don’t recommend trying to customize the AutoCAD or other software on these computers, as not everyone who teaches will share your ideas about how menus suck and keyboard shortcuts are the only way to go. That’s when the dual laptop method works best. All it takes is a little static – and you’re talking about your kids for the next 75 minutes… and getting a crappy score.



To wrap it up, understand that AU is not a traditional training event, so you can’t approach it with the chalk and talk method. Be creative – engage the audience – know your subject – but most of all, have a great time and enjoy the privilege. Not everyone is crazy…excuse me, qualified enough to teach at AU, so make the most of it!

Later - David B.

AU 2012 - Time to get loaded up!

You'd think I would have learned by now, don't offer to do too much...but if it wasn't so much fun...

For AU 2012, held at Mandalay Bay in Las Vegas this year, November 27-29, 2012 (au.autodesk.com), I've got six classes:


Class ID: MP1414
Class Title: Revit MEP 2013 - On Steroids!
Class Type: Lecture


Class ID: MP1461
Class Title: You did WHAT? Revit MEP and AutoCAD PID? Amazing!
Class Type: Lecture

Class ID: MP1465-L
Class Title: Fast Content for AutoCAD MEP 2013
Class Type: Hands-on Lab

Class ID: MP1470
Class Title: Supercharge your AutoCAD MEP 2013!
Class Type: Lecture

Class ID: MP1477-L
Class Title: FASTER Families for Revit MEP!
Class Type: Hands-on Lab

Class ID: MP1478-L
Class Title: Perfecting the System for the Revit MEP Project
Class Type: Hands-on Lab


Usually the labs fill up first, so make sure you sign up early. I'm also volunteering to be a mentor to newbies and first timers, so I'll be in Vegas on Sunday, November 25 around midday.

Registration starts in early August, so if you haven't created an AU account, get online and do it today - it's going to be a blast this year!

Later - David B.

Wednesday, June 20, 2012

Piping, Worksets and Large Projects in Revit

Came across a little tidbit about changing connected systems (in this case, piping) on a good sized project. It appears that if you have worksets defined by building or structure, and you have connected geometry that is in more than one workset, you need to make sure that you're the owner of all worksets the connected pipe or duct belongs to.

In our case, we've set up an overall site model, that contains worksets based on building and discipline. We had a group of pipe we needed to shift down about a foot. When the tech went to move the pipe, he got an ownership warning (along with the editing request). In this case, the pipe that was being stretched was connected to a pipe in another workset the tech didn't have enabled, so the command fails. enabling the workset eliminated the dialog and allowed the move, even though the pipe being edited wasn't in the disabled workset.

We've discussed doing workset by systems, but this seems to be a little more trouble...so let me know how you're dealing with it - is it better to have a system that's connect across a longer distance in one workset, or do it all by building? (By they way, we also have the yard piping in its own workset, too.)

Ain't this BIM stuff fun...later - dab

Wednesday, May 30, 2012

Are you getting SPIKES in BIM?

I'm noticing an interesting phenomenon. As we make our move to the BIM environment, we've learned that everything moves forward in stages. Obviously, different people learn at different rates. We have users that have easily adapted, and are constantly pushing the envelope. For users that are new to BIM, we keep coming across the "hesitant" user.

You can easily identify these folks. At the pool, they start by only getting in up to their ankles...and quickly get out because the water temp isn't exactly warm enough (others simply pee in the pool in vain attempt to warm it up). I always wind up behind this person in line at Starbucks in any airport...standing there, staring at the screen, wondering if the expresso will keep them awake on the flight, or if the protein in the smoothie will make them constipated for days.

Anyway, back to the projects. We've had some weird issues show up. And by the way - this isn't happening just for us, but across the spectrum of design firms, so my examples are global. For example, we have several structures to renovate and build from scratch, but the project manager only chooses to use BIM on the new facilities. Not that there's anything wrong with that, except that we're connecting equipment between the facilities - so it would have been really nice, and incredibly more efficient in the design process if everything new was created as BIM objects.

I've also heard about other projects, where the client wants AutoCAD, wants 2D, isn't interested in 3D...but the question is asked about using laser scanning and point clouds to generate an as-built, for presentation purposes, then runnin' back home to Mama and delivering plain AutoCAD.

It seems that every once in a while, an old school team leader hears about BIM - and SPIKE! Just like that, we get a flash of awareness that lasts as long as a lighting bug in a bird house. The idea is pushed, let's try BIM...but let's just do it here...and not too much. It's kind of like watching the beer commercial where the drinker only wants 1/5 of a glass...and if they don't like it, do they have to pay for it?

Have you ever experienced getting SPIKED? Man, this drives me nuts...and hence the soapbox. If we haven't said this once, we'll say it again. Building Information Modeling is a design process. It's something that you make a decision to follow at the start of a project. It's a business model, not a toy you buy once and throw in the box. And it's really annoying, because only a limited amount of effort is being applied to understanding this.

Here's how I think the fear manifests itself. The PM, Department Head, lead engineer, project architect...we've all had projects at some point that have blown up on us. Especially in older users, it instills a fear of anything that moves you out of your comfort zone. And it's scary, because none of us want to fail. The current business climate has made it worse, as everyone knows it's lot harder to get on with new firms nowadays. But it boils down to a simple thing - you don't just pick a small part of a project (a SPIKE) and "kick the tires".

If you're first instinct is that BIM only works on new projects, we're blowing that away every day. One advantage to having a new BIM user model an existing facility is that the design is already worked out - so this is great practice. There's also a preconceived notion that you have to model everything. I don't recommend doing any more than you need to, to get the design intent across - and in most cases, you can get away with LOD 100 - unless the client is paying you to do more.

I like to hear people say "We're doing BIM on this job" and then they whisper "only up to 60% - then it's back to AutoCAD". Why in the world would you develop a model, that in CD's would save you 50% or more of your contract document production time, and then decide to go back to a drafting board mentality? So we SPIKE to create the model - then panic when the deadline approaches, and go back to our comfort zone.

I've got an electrical designer I love in our office - he's so old school, he still has a pocket protector. But he gave me the quote of the day..."it's become very apparent to me that Revit isn't AutoCAD..." I was stunned...but he's trying, I have to give him credit. Then we gave him a tech that is really fast on Revit, and life is now better.

It boils down to this - if you are a team leader, understand that BIM is like poker - you only win (and win BIG) when you go "all in". If you only decide to do parts of a project, then you open yourself to whole new range of issues - compatibility between applications, loss of data, lack of coordination, document consistency (lineweights, fonts, etc.). Inconsistent application - SPIKES - is not a viable method to use on a project. The spike invariably impacts one major component - the COST of the design.

By the way, my interpretation of SPIKES - Some Projects I Know Explode Spectacularly...that's what happens when you take a half serious approach to BIM...

Have a great day - keep 'em between the lines - David B.

Wednesday, May 23, 2012

Great Article on BIM Implementation by Josh Oakley

By goodness, when I find an article that lays it all out, I like to pass it on - Josh Oakley of ANGL Consulting wrote a great article on why BIM implementations fail - and what you can do about it. Check it out - it's a great read:


Nicely done! David B.

Tuesday, May 8, 2012

Changes to the Autodesk Subscription/Upgrade plans

Greg Arkin has posted a pretty detailed article about upcoming plans to change the Autodesk pricing/subscription model. This wasn't really surprising to me, as Autodesk is gradually moving to similar software vendor models (re: can you say online sales, severely whacked down channel).

The fact is, they've been more than generous to users that have held on to their old AutoCAD's (I had to work with a guy who was still on a DOS System using ACAD 9 a few years back), but the reality of it is, the companies that were either pirating software, or not making the investments in technology with good planning, are the ones who are going to be screwed.

And for those that have been clinging to their precious LISP routines and thinking they're just as productive in a 2D electronic drafting world as we are in the BIM/3D Modeling world with the Suites, you're sadly mistaken - and the cost penalty is going to be high...

So if you're still sitting on your AutoCAD 2000, you've got nobody to blame but yourself. Work with us, and we'll help you leverage the modeling we're doing, re-designing and updating your office, plant, school...whatever...to help you get into the 21st Century the new design paradigm. Get on subscription, and keep your tools current!

News Flash - Autodesk to remove upgrade pricing next March - Older customers screwed! Subscription customers laugh

Monday, May 7, 2012

FIM...Part Two...

Back to the jetski fishing rig project...OK, so the rig is about finished. One thing I didn't point out before is that I published the model of the cooler/rod holder to Design Review, and used that in the garage to put this together:


So I'm already doing my part to save the planet...anyway, we wound up making a few changes, but this worked out really well. The rig was placed up on feet, so the Yamaha plume would clear the unit without blowing it off the back end:

The rig holds an Igloo 25 quart cooler, and two Berkley adjustable rod holders. The side mounts allow us to rotate this out for trolling if we want to, although I don't know if they'd hold up to a big king mack or tarpon...but we'll find out. The unit will be anchored down to the tow eyes and the rope ring on the back of the seat. The frame was glued and screwed with stainless steel, so corrosion shouldn't be much of an issue.

Next up - electronics...


We settled on the Humminbird 385 DI combo, due to the small size, waterproof, sonar, GPS and downscan imaging - with the transducer mounted in-hull, so it wouldn't be quite as tacky (like we're not already). We added a gel-based 12 volt battery in a small box in the forward storage compartment, with the openings sealed through the wall to protect the electronics.


Mounting was completed by bolting in a RAM Mounted (Humminbird Specific) in the cup holder - since we never use this, due to the fact the water bottle kept flying out at speed...but this baby ain't going anywhere. Easy removal - just unplug, and loosen the mount, and you can tuck it away for travel. Wiring was coil wrapped to protect from movement during a run, and also to keep the leads from sliding down below the steering.

So, does this qualify for creative? Not sure, but a patent and copyright are on the way...

Next up - the real test in Key West, Florida - watch for pics soon!

Later - David B.