Plan It Autodesk

The Built Environment Lifecycle

What happens during each phase of a built environment project can have a major impact on other phases, but none more so than planning, in large part because it comes first. Planning is where it all starts. Planners create the vision. They must factor in a host of variables often without the time and/or detailed information that they would ideally like to have in order to produce a conceptual design that can stand the test of time.

The hot topic for planners today is the idea of sustainable design. This is the theme of the American Society of Landscape Architects' (ASLA) upcoming annual meeting which is being held in Minneapolis October 6 - 10. See http://www.asla.org/land/2006/0724/annualmeeting.html for more information.

Autodesk is focusing significant resources on developing integrated solutions that cover the entire lifecycle of a built environment project, which we believe supports the concept of sustainable design. In fact, we want to provide a leadership role in this movement.

Please let me know how you think this might best be accomplished.

Next time - Land Planning

Planners vs. Engineers

I admit it. I'm an engineer. Seems like I always have been, and I know it's too late now to change.

Now we all know about the differences between engineers and architects - books have been written on this subject, but what about the differences between the way engineers and planners see the built environment?

Once again, if we narrow the discussion to physical planners, as opposed to policy, I think there are a lot more similarities than differences between engineers and planners. In fact, in some cases if we use the broader Project Planner definition the two professions often overlap. Infrastructure projects are not started with design, they must be planned first and this is often done by the more experienced engineers.

Project planners are forced to think more abstractly, particularly in the early stages of planning a project. Many engineers are not comfortable in this kind of thought process. At the same time, when detailed analysis is required the planner types are not in their comfort zone.

The keys to productive co-existence, it seems to me , are recognition and respect. Knowing one's strength's and weaknesses, and respecting the needs of the other team members goes a long way toward producing high quality results. Working in a technology environment that supports the unique needs of both engineers and planners is also important.

What do you think?

Next time - The Built Environment Lifecycle

   

A Conceptual Project Planning Model

Are the automation needs of project planners being met by the tools available to them in today's marketplace? Not even close, according to all of the planners that I have discussed this with. The result - significantly lower productivity according to planners at some of the largest planning firms in the world.

What would a dedicated, focused project planning solution look like? I'll share with you one model for a conceptual project planning solution. The major modules would include: 1. Design/Drawing;  2. Data Capture; 3. Visualization; 4. Analysis; and 5. Reporting

The key to making this all work is data integration. The ultimate solution must be able to share information between modules, as well as with GIS and CAD so that information needs to be entered only once. This is what is missing today and why planners are forced to use 3 to 5 software products that are not integrated to achieve some level of productivity gain.

Can we do a better job? Absolutely. Please let me know what you think.

Next time - Planners vs. Engineers