Today I had a conversation with the Chief Information Officer at one of the largest architectural firms in the US. He said that the most pressing issue he faces--and by implication, the industry--is the need to understand process and change management in architecture in the light of moving to building information modeling.
After our conversation, I started looking through the AECnews archives on the subject, and came up with several relevant articles. I sent an email to him with the links, then realized that others would be interested in these articles as a set, as well.
Most of these articles were written before AECnews became a free, web-based publication. So, even if you've been reading online since we made the big change earlier this year, you wouldn't have seen most of these articles.
The articles (and URL's) are:
"Work in Process," by Jerry Laiserin:
http://aecnews.com/articles/793.aspx
"AEC IT Magnetism and the Rise of the New Master Builder," by Randall Newton, http://aecnews.com/articles/788.aspx
"Enabling Innovation Through Project Lifecycle Management," by John MacKrell, http://aecnews.com/articles/786.aspx
"Teamwork Initiative Issues Recommendations for AEC,"
http://aecnews.com/articles/727.aspx
"Lessons from London, part 3: Manage Expectations to Properly Exploit Technology," by Randall Newton: http://aecnews.com/articles/725.aspx
"Understanding and Minimizing Transaction Costs in AEC," by Randall Newton: http://aecnews.com/articles/714.aspx
"Lessons from London, Part 2: Implement Building Information Modeling in Phases," by Randall Newton, http://aecnews.com/articles/706.aspx
"Lessons from London, part 1: Design is a Modeling Process; Offer Value, Not Cost," by Randall Newton: http://aecnews.com/articles/695.aspx