After discussing in class, watching the 2016 Autodesk University video with Bill Allen, and reading other groups’ views on this topic, I find myself believing that the future of the AEC industry will follow the described projection in roughly the next ten years.
To quickly recap, the video we viewed in class from Autodesk University exposed viewers to extremely efficient and useful tools that, as described, are in the works of becoming fully integrated in current construction practices. The software highlights new abilities that speed up a design process by rapid iteration development. From my understanding, iterative design is huge in architectural design, as there is a need to have choices on a final product. As a mechanical engineering student, I’m still learning more about this but it doestranslate well as mechanical engineering always has iterative design. That being said, I would agree that the same process described in architectural design and software manipulation could be easily bridged into common engineering processes. The biggest takeaway I had from the discussion is that a future of AI development will take away a lot of the “busy work” that comes with choosing a design and generating options. I believe that design intent and engineering principles can be streamlined into one singular process in the near future. I could be wrong, but the way Bill Allen presented the programs in the presentation made it appear as though this idea is not a dream and that it is quite literally happening right now. I am quite hopeful to see this technology come to fruition, and I hold that it will be possible within a decade.
While I stated that this transition will be possible in the next ten years, I do need to mention that this will not come with ease. With any change in an industry comes a slew of hindrances, limitations, and difficulties. Quite possibly the largest difficulty is overcoming the idea that not all software works the same. This was discussed quite a bit before in class in general discussion and was mentioned in the group last class. We talk about this idea of “interoperability” which, in theory, is fantastic. Quite frankly, though, the industry is limited right now as companies compete for business and software products are not compatible. A lack of compatibility hinders progress, and as much as I’d like to see it change, I’m not sure whether we will overcome the hurdle of business competition for the improvement of design and construction. Another aspect blocking the progress of this idea is the steep learning curve that exists between industries. Revit and BIM users are great at using those tools for design, but when you put, say, a mechanical engineer in front of these programs they’re sure to be at a loss for where to start. Solidworks and PTC Creo users also are great with those tools for 3D design and engineering calculations, but when put an architect in that environment those software products are extremely foreign. There will be a great need for education and assimilation of all people involved to streamline this technological development. With education and time comes great cost, and this development is surely going to be a costly one.
In conclusion, while I do hold that this idea presented in the video about the AEC industry will be feasible in ten years, I admit it will come with a lot of hard work. Associated costs, time needed for education, a need to overcome business competition to integrate interoperability, and a lack of interest from older generation workers will all create a great deal of friction. While the claim I make is quite a preposterous one, there is a certain inspiring feeling that comes from believing in a better future of development in the industry.
Comments on Others’ Posts
Nick Maloney, I could not agree more with all the points you mention in your post. The video in class really did present some outstanding tools that help with the iterative design process and their progression in the industry. I like your idea with how, ideally, the transition would go (that is, taking input parameters of interest that guide AI) and I believe my vision of this aligns perfectly with yours. I certainly do hope that this “methodology” (great word, by the way) is “close to implementation on an industry-wide scale” as you mentioned. It would be fascinating to observe this development from an outsider’s point of view (as I am studying mechanical engineering and this field is very new to me). I also could not agree more with the obstacles you address for the implementation within ten years. All are valid points and I’m curious to see how the industry addresses them. Great post!
Albert Hanan, after reading your post I think I’ve changed my mind on the matter. I agree with you that this is the future of the industry but it is a bit unrealistic and ludicrous to think that the industry will fit this change into a ten-year time frame. I also agree with your statement that the “technologies described in Allen’s talk aren’t that far off from existing now” because, as demonstrated in the video, the desired end-products are quite achievable right now via the simpler means provided by this software. Your point made that people like to stick to the “do it because that’s how we’ve always done it” notion is extremely valid. Our tendency is to stay in the safe zone with what we do and it indeed limits our ability to progress.
Hailey Ihlow, I like how you have experience with Revit so you are familiar with its popularity and its use. As a mechanical engineering student, I have no prior experience with the software so I look to students like you to give me some insight into its usefulness and relevance to the industry. I like your idea that more ambitious and competitive companies will be more likely to push to fit the ten-year timeframe. We’ll see where these companies go soon!
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.