Wednesday, 27 October 2010
Sketchup is dead! (Long live Sketchup!)
We have had a ton of requests for a Sketchup test this year. And I should make this clear, we have manfully resisted this for quite some time, feeling that a Sketchup test was somehow an exercise in overkill. Many times I have asked the question, 'Why on earth would you want a Sketchup test?!'.
Nevertheless, it still keeps coming up in feedback forums, so it has been added to our list of short term devs.
However...
...I don't know if something is in the water, but over the past few months, I have been in meetings with heads of design and technology (mostly in Architectural firms, to be fair) where Sketchup is no longer the poster-child of design software. Oh no, in fact, quite the opposite! 'We're trying to kill Sketchup', was the anguished cry from one leading design firm in New York. And back in Blighty, the same trend is emerging; 'Sketchup has become my biggest pain in the ****!', bemoans another technology leader.
But what has prompted such a collective venting of creative spleens, I hear you cry? Well, it seems that, whilst Sketchup is great for knocking out quick visualizations, too many people are trying to use it for much more than that.
In some ways, Sketchup is becoming a victim of its own simplicity. Because Architects are nowhere near as scared of learning Sketchup as they are of, say, Revit or MicroStation, they're now trying to use it for all sorts of inappropriate outputs. Let's make this clear - Sketchup is not Revit. You can't create a BIM model in Sketchup - so stop trying!
And it doesn't stop there. Not only is misguided use of the drafting tool causing the collective blood-pressure of BIM managers everywhere to reach Vesuvian levels, it is also now being cited in a couple of legal cases where, I kid you not, firms of Architects are being sued by clients for mishandled project information leading to mistakes during a build. Turns out that shadow diagrams quickly crunched out in Sketchup have been used as hard data during a build, which, in turn, has led to some pretty upset clients!
Suddenly, the ramifications of using technical software inappropriately on projects isn't funny at all. It can cost AEC firms thousands of dollars in lost income - not to mention the management time that goes into yet another round of unnecessary litigation. And those design firms who poo-poo the importance of technical software as a highly sought after skill? You have been warned. No longer can you get away with the familiar refrain, 'We only employ good designers. Software skills don't matter - we can always get them up to speed in Revit later'. (For the record, my blood freezes whenever I hear those 5 words - get... them... up... to... speed).
Oh, and don't blame Sketchup for this mess. It's not the one at fault here! The clue is in the name, stupid! ;)
R
Monday, 27 September 2010
Herbert Hoover's Engineer
The great liability of the engineer compared to men of other professions is that his works are out in the open where all can see them. His acts, step by step, are in hard substance. He cannot, like the architect, cover his failures with trees and vines. He cannot like the politician screen his shortcomings by blaming his opponents and hope the people will forget. The engineer simply cannot deny he did it. If his works do not work he is damned.
On the other hand, unlike the doctor, his is not a life among the weak. Unlike the soldier, destruction is not his purpose. Unlike the lawyer, quarrels are not his daily bread. To the engineer falls the job of clothing the bare bones of science with life, comfort and hope. No doubt as years go by the people forget which engineer did it, even if they ever knew. Or some politician put his name on it. Or they credit it to some promoter who used other people’s money…
But the engineer himself looks back at the unending stream of goodness which flows from his success with satisfaction that few professions may know. And the verdict of his fellow professionals is all the accolade he wants."
R
Thursday, 19 August 2010
540,000 hours
Thursday, 5 August 2010
Daisy-chain

This month, we are introducing a change to the way assessments are authored, based on the idea of linking separate modules in a 'daisy-chain', to create a longer test.
In essence, the KS system breaks down like this;
- A test is one or more modules linked together.
- A module is comprised of typically 4-6 questions, covering the same topic, i.e. Families in Revit or UCS in AutoCAD, etc.
- A question tests an individual's understanding of a particular software feature or command.
Questions and modules have training tag keywords (meta tags) associated with them, which makes training needs analysis, post-assessment, much more relevant.
Questions can be "task" based or "knowledge" based.
A task based question has files associated with it. The user has to do something to the file, in order to work out the answer, as follows;
- Task (interrogate) - the user has to open the file and find the answer, but they don't have to modify or change the file in any way.
- Task (modify) - the user has to open and modify the file, to work out the correct answer.
- Knowledge - this type of question does not require a file to be associated with it.
Test administrators can present a single module as a test, provided they create a new test from the module first.
A 'daisy-chain' happens when an administrator links a series of modules together, to create a longer test.
This concept allows us to create a wide range of test material, in bite-sized blocks, which map closely to corresponding training and learning material.
Daisy-chains go live next month.
R
MCMC 2010
The organisers have pulled out the stops, with an agenda packed full of high-quality speakers, over the course of the two days.
See this link for full details:
http://www.tmcmcmc.org/meetings/2010/Onsite_Agenda_2010.pdf .
Tuesday night's entertainment includes dinner and a repeat trip to Power Play, for another high energy Whirlyball contest. (For the un-initiated, Whirlyball is a mix of lacrosse, basketball - and bumber cars - not for the faint hearted!).
Tickets are just $95 per day, including lunch and snacks throughout the day.
The theme for this conference is Versatility. Covering multiple tracks, including, MicroStation, Civils, Plotting, CAD Management, Collaboration, Building, Structural Analysis and US Army Corps projects.
Wednesday, 9 June 2010
What happened in Chicago...
Here is mine: http://ka-connect.com/talks.php?vdx=48.
The funny thing about my presentation was that I had the very last slot on day 2. It's fair to say that of my Pecha Kucha session - 20 slides, 20 seconds per slide - about 75% of what I had to speak about, had already been covered at some point during the previous 35 talks! So much of what you see here is delivered on the fly. :)
There were some terrific presenters during the course of the 2 days. Here are some of my favourites:
Laurie Dreyer, head of HR at US design firm Anshen + Allen (34 mins long, but frankly unmissable viewing!): http://ka-connect.com/talks.php?vdx=40.
John Moebes, Director of Construction at Crate+Barrel, with a fascinating insight into what owners expect from their design, engineering and construction partners:
http://ka-connect.com/talks.php?vdx=2.
Michael Kilkelly, Associate at Gehry Partners, gives us a look behind the scenes of one of the world's leading design firms: http://ka-connect.com/talks.php?vdx=57.
KA-Connect 2011 takes place in San Francisco, in April 2011.
R
Friday, 4 June 2010
EYC CAD Managers Forum - summer 2010
See link for full details: http://www.eatyourcad.com/resource.php?resource_id=1676
The meeting takes place on June 30, at Buro Happold's Newman Street offices, from 10am to 4.30pm.
There are two main topics on the agenda; I'll be talking about the effects of the recession (isn't it over yet??) and what lessons we may have learned. The afternoon session looks at BIM contracts, technology and deliverables.
All in all, it promises to be an excellent forum. Tickets are just £50, to cover EYC's costs, so be sure to book your slot - and I look forward to seeing you in London.
R