Wednesday, January 30, 2008
Second thing, is some construction scheduling/sequencing and how it works with Innovaya (I'll do the NavisWorks tutorial at a later date).
For the most part if you are using Primavera products or Microsoft Project you are in the clear in regards to Innovaya. If you have some other proprietary scheduling software you might be in a pinch if it can't at least export to one of these programs. Hopefully I'll get the demo video up tomorrow so you all can take a gander at the interface and how the platform works.
Friday, January 25, 2008
Thanks again for coming out and what great emails!
Tuesday, January 22, 2008
Revit Architecture can report cut and fill volumes on a site to aid in determining the costs of landscape modification during site development.
Revit Architecture reports the values by making a comparison between a surface from one phase and, from a later phase, another surface whose boundary lies within the earlier surface. For example, Revit Architecture can comparea toposurface created in Phase 1 and a toposurface created in Phase 2 that lies within the boundary of the surface from Phase 1.
When you select the later surface and click Properties, you see the following instance properties:
-> The Cut value is the volume removed (where the lower surface is lower than the earlier surface)
-> The Fill value is the volume added (where the later surface is higher than the earlier surface)
-> Net Cut/Fill value comes from subtracting the cut value from the fill value.
Monday, January 21, 2008
Should be pretty good. Longer blog tomorrow on how to manage keynotes linked to spec numbers and/or how to identify and estimate from Revit using Innovaya on a TI project we got going on. Depends on how much coffee I have...
Monday, January 7, 2008
This is a quick demo of section perspectives and how they help visually spell things out to an owner. We put this video together to explain the space we could recapture by moving a basement wall back 5' for potential meeting space. I gotta say this worked pretty well!
I've been asked a couple of times why we do it differently, why we choose to do single / same model coordination. The reasons are simple, but ultimately BIM in and of itself is really only part of the greater pie.
With technology advancing (finally) in the AEC industries, I don't think we are about to see a slow down in the amount of information and coordination that affects the teams decisions and coordination. Ultimately, I think that by setting up the flow and management of information correctly now we won't have to reinvent the flow of processes the next time.
Secondly, I know the opportunity for improved communication and growth is a real need. The opportunity in using a singular BIM forces the issue of communication and coordination. Just as your "forced" to model walls to exact dimensions, BIM pushes the team to collaborate and define, just where are those construction joints? how is this panel going to be constructed? what is the necessary aesthetic for a space? what is the owners program and can we design those spaces first?
What we've started to see, is yes it's the "harder way" to construct a BIM. And that's the point. The point is to make sure that everyone involved has access to input and share the same information regardless of the others undertanding of what that teammate might need.
When we start to see overlap and questions pop up of "Well how are we going to get the ductwork through that? etc..." is when we know we are in some way creating savings.