For those of you who have not noticed I’m a bit of a system fanatic ;-p
Recently I was asked to write an article on Revit and Business systems for the brand new E-magazine in the USA called AUGIAECEDGE
Here is a shortcut to my recently published article: (Page 9 & 10)
Here is the link to the AUGIAECEDGE:
My name is Neil Greenstreet. It was nice to bump into you at the Revit User Group Sydney function and now be able to put a person to the name behind the blog.
As mentioned, your AUGIAEC Edge article really struck a chord with me. Amongst all that is written about BIM there seems to be relatively little on this topic. Although I have been practicing architecture and using CAD for a long time, I am relatively new to Revit. I have a longstanding interest in the systems approach to things and the way architects (and designers/problem solvers in general) deal with the huge volumes of information in the process of learning and practicing their profession.
Like you, I am fascinated by the different systems designers create to manage their work. It is hard not to be struck by the differences between one office and another – why are some well organised, and others lurching from one crisis to another? Why in one place does everything you need to do your work fall close at hand, and in another can never be found without a struggle.
The highly structured nature of BIM seems to have the potential to multiply the pain and frustration of any existing disorganisation – it needs a well organised supporting structure to really fly!
Crafting the right system seems to be an art. It needs very well thought out conceptual underpinnings, but should not be so rigid or over-elaborate that it is tedious to use. Like most things in design, it’s getting the balance right.
So this is how I am coming to this topic – finding a way to apply the principles I have learnt about organising information to the new (for me) BIM environment.
I would be very interested to read in more detail about the standards and protocols you have developed, if you are able to do this in the future.
Thank you for your great article and blog!
Thank you for your kind comments. My appologies for the delayed approval of your comment. I am glad to hear that you got something of value from my blog and article ;-)
To be honest – I think that your suggestion is a great idea, but not one that I am willing to expand on too much at present, especially in a blog format. (It’s far more fun for me to share ideas in a workshop forum, where everyone is participating equally, than typing on my own.) I enjoy the social aspect of sharing ideas and collaborating on real projects ;-p
None of the ideas or concepts about system design are really that complex or secret. However I agree with your comments, in my experience these business principles seem to be inconsistenly executed and more importantly poorly managed within the architecural industry, in general. (I cant speak for MEP or structural engineers.) I often joke that I think it’s because Architects and designers are far more focussed on the process of being creative and that perhaps, systems and procedures are seen by most as a bore, a hinderance to spontaneouity. (Being a former designer myself I figure I have earnt the right to laugh a little at myself and them too.) But the audience that will be using a designed system does need to be taken into account because it can result in industry specific hurdles that we often face when trying to bring about constructive business evolution.
I believe the most valuable process of building business, Revit or BIM systems is making the time (and getting mangement support) to do lots of exploring and testing of ideas/ solutions. Each company dynamic is different , the management style is not the same and the driving force for change may be dfferent. All this affects the speed, dedication and urgency of the the implementation strategy and the desired outcome. Some solutions are less effective in certain management dynamics than in others.
I think it’s imperative that system developers focus on ways to streamline business efficiency and effectiveness. However, it is as important that system designers remain open to ideas, feedback and be flexible with their own proposals and solutions (providing it does not jepordise the desired goal or outcome of coarse.) Our aim should be to try and build systems that solve many more problems than the inconvenience that any new systems can potentially create ;-p
I know I have not answered all your questions but I am happy to chat with you in person at the RTC (I’m assuming you’ll be there) as I am really short of time at present. Cheers