Jeffrey W Ouellette

Also, depending on the size of the project, it may not even make sense splitting it up by level. Instead, you could set up a complete central file of the building "shell" and then reference in interior configurations, independent of the exterior walls and structure. From the interior files, you would then reference in the respective portions of the shell file. I find that using the BIM tools in Vw makes it easier for one person to do a lot of related work (e.g. exterior wall/form design) and that artificially chopping up the model into many pieces (like stories/levels) may actually create more work, not less.

Troy, Yes, I usually end up forgoing the linked layer capability of the Custom Stair tool. Instead, the "new" Stair tool (as opposed to the "old" Stair tool, which is now the Custom Stair tool) has an option for 2D or hybrid. When I want specific 2D graphics to show the stair above/below, I'll insert a 2D stair underneath the 3D/hybrid one and adjust both graphics. I admit it is not ideal, but the new Stair tool doesn't have the layer linking functionality, yet.

Christiaan, What exactly is "freeform" about this method? I've demonstrated using native Vectorworks BIM tools (Wall *round wall works, too!*, Mullion, Window/Door, Framing Member) and applied the symbol methodology in the correct way, using multiple instances of a single configuration definition. If I choose to export this via IFC, I can leave the objects as they are or I can Group the Wall and all its inserted elements and attached the IfcCurtainWall data to it. I can edit this system using the same tools I use to edit any Wall and symbol geometry. I can structure the wall to be segmented on a floor-by-floor, or an entire facade basis; dealer's choice. Each choice has advantages or disadvantages, depending on the needed output and method of sharing the data. I can schedule the elements of the system, quantifying the amount of glazing (WallNetArea), the number of mullions (both horizontal AND vertical, the number of spandrel panels of each type/config/size AND all the windows and doors (individually or by type). AND I can slice and dice this information for feedback on a floor-by-floor basis, if I so choose. I can name the individual components and tag them, if needed for component/assembly drawings. I can control my graphic standards for each of the parts to satisfy any needs. I have the flexibility to deal with alternate conditions where a vertical or horizontal bay has a different configuration for aesthetic effect. I can even take the details of the system further by creating custom symbols with more detailed intricate profiles of any component part, if needed. This method is consistent with Vw tools and methods. I would argue that a single curtain wall object would be more complex and too cumbersome to deal with, especially for more complex configurations. There would be such a high number of parameters needed that it would make the tool as difficult to use as the current Window Wall tool, just on the other end of the spectrum. More and more, I am finding that "magic" all-in-one BIM objects are not all that they're cracked up to be. In some cases they work, but what options does a user have when they don't? With the tools and system I have at my fingertips in Vectorworks, I don't have to worry about an objects limitations in order to design, document and share BIMs. The more rigid a system is, the less that can actually be done with it.

Or you could use the Wall tool, set the Wall Style to be the glazing, then use the Mullion tool for the vertical mullions and the Framing Member tool to do the horizontal mullions. That way you can insert Doors and Windows (e.g. "vents") and even custom symbols for spandrel panels. Refer to the images in a Flicker set: Flickr - VW 2010 BIM Methods - Curtain Walls

Troy, I've usually got other layers for other "supplemental" information. Typically, I use a "Mod-Guidelines" layer to put the structural/building grid (class='Structural-Grid') and maybe other important alignment guidelines that don't fall on the grid (class='Non-plot'). In addition, if I have a site model, I may have a "Mod-Site" layer. This will either contain the actually DTM or just a reference from another file (or even a Design Layer Viewport from another layer in the file).

Troy, What I hoped to get across in the Ellicott Heights white paper was that the Vw organization of a project can vary, dependent on the size and complexity of a project. You have to design the process and all the parts - size of team, responsibility of team members, data structure (level-based or function-based), file/folder structure, referencing system, etc. - before you even start creating model data. As I create more research models, resulting in more BIM in Practice material to be released in the future, I am constantly learning and thus tweaking ideas and recommendations for doing BIM in Vw. So take my following advice as a reflection of what I know today and have learned from the past. IFC is a means/file format/schema describing BIM data. In Vw, the IFC expression of building elements such as Columns, Walls, and Floors, runs parallel to the Vw internal data structures. The IFC data is mapped directly to objects, not by Vw Classes. At export, we automatically map the Vw data to IFC data formats. In Vw Architect 2010 SP3, this includes automatic IFC mapping for the following Vw entities: Base Cabinet, Bath-Shower, Ceiling Grid, Clothes Rod, Column, Comm Device, Compartment Sink, Counter Top, Desk, Door, Drilled Footing, Simple Elevator, Escalator, Fireplace, Floor (as IFC slab), Framing Member, Grab Bars, Guardrail (Curved & Straight), Handrail (Curved & Straight), HVAC Damper, HVAC Diffuser, HVAC Elbow Duct, HVAC Flex Duct, HVAC Outlet, HVAC Splitter, HVAC, Straight Duct, HVAC Transition, HVAC Vertical Duct, HVAC Vertical Elbow, Incandescent Fixture, Mullion, Parking Spaces, Pilaster, Pillar, Ramp, Receptacle, Roadway (all types), Roof, Roof Face, Seating Layout, Shelving Unit, Space, Stair (and Custom Stair), Switch, Table, Tables and Chairs, Utility Cabinet, Wall Cabinet, Round Wall, Wall (and Wall Projection/Recess), Window, Window Wall (Straight & Curved), Workstation Counter, Workstation Overhead, Workstation Panel, Workstation Pedestal In addition, symbols in the following content libraries are also automatically assign basic IFC data: Architect Sampler.vwx, Equip-Office Equipment.vwx, Equip-Residential Appliances AGA Ranges.vwx, Equip-Residential Appliances SubZero USA.vwx, Equip-Residential Appliances Wolf USA.vwx, Equip-Residential Appliances-Audio Video.vwx, Equip-Residential Appliances-Imp.vwx, Equip-Residential Appliances-Metric.vwx, Equip-Restaurant Equipment-Imp.vwx, Fixtures-Imp.vwx, Furniture-Furnishings and Scenic Elements.vwx, Furniture-HMI-Modern Classics.vwx, Furniture-Knoll.vwx, Furniture-Misc-Imperial.vwx, Furniture-Misc-Metric.vwx, Furniture-Office.vwx, Furniture-Residential.vwx, Furniture-Systems HMI-Typicals.vwx, Furniture-Systems-Imp.vwx, Furniture-Systems-Metric.vwx, Openings-Windows Velux Skylights.vwx, Electrical-Lighting Fixtures Int & Ext.vwx, Electrical-Lighting-Imp.vwx, Electrical-Panels-Imp.vwx, Electrical-Panels-Metric.vwx, Electrical-Power Devices-Metric.vwx, HVAC-Equipment-Imp.vwx, Sanitary-Fixtures.vwx, Sanitary-Kohler Baths.vwx, Sanitary-Kohler Bidets.vwx, Sanitary-Kohler Faucets.vwx, Sanitary-Kohler Lavatory Sinks.vwx, Sanitary-Kohler Showers.vwx, Sanitary-Kohler Sinks.vwx, Sanitary-Kohler Toilets.vwx, Sanitary-Kohler Whirlpools.vwx Please note that in many cases the IFC data that is attached to an object is NOT completely comprehensive of all IFC Entity and Property Set (Pset) data associated with a BIM object. A user is able to edit/override/add IFC data to any object using the "IFC Data..." command in the AEC menu. As far as the overall Design Layer structure of the BIM, I am now leaning more toward "Less is More". I would have just three (or four) layers for each story/level; Mod-Floor-#, for architectural floor planning elements,(optionally a Mod-Ceiling-#, for architectural ceiling plane elements,) Mod-Structure-#, for structural elements including floors, columns and load-bearing walls, and Mod-MEP-#, for MEP/HVAC systems and elements. Through this structure, you can maintain the internal flexibility of setting up drawings in Vw while simplifying export in the IFC Export dialog. Also, it simplifies the IFC import of data from structural and MEP engineers, giving you a placeholder layer, independent of the architectural design/elements.

In addition, you could turn that poly into a Space object with Gross and Full-Floor parameters.

Troy, You could also try using the Framing Member(FM) tool. This can be pitched, as desired to almost vertical and the top and bottom ends can be properly resolved. To export as columns via IFC, just select the FM/Column and open the "IFC Data..." command under the AEC menu. When the dialog opens, reassign the FM from IfcMember to IfcColumn.

It may be, but why does it matter? IFC2x3 is going to be used for application certification for at least then next year. A new certification process is currently being implemented and ALL applications are starting from zero. I have confidence that we'll be one of the very first, if not the first, to pass and be certified, this time around (this should happen end of 2010/early 2011). IFC2x4 implementation will probably then occur some time mid to late next year (2011) among many applications. Some may start earlier, some later. But certification for use/app competency of 2x4 probably won't happen until late 2011/mid 2012. Mass adoption of 2x4 won't occur until most downstream, as well as upstream (BIM-authoring) apps have implemented it and been certified.

Roger, In the OIP, you must enter the text of the Class that you want the Texture Bed to be assigned to. Then, set the desired Texture in the Class. The Texture Bed will then Texture, as long as all Attributes are set "By Class".

Snow Leopard. I'll get some more info from you off-line (private message) so our engineers can see what the problem may be.

Vincent, I can't say I share your crashing experience with Vw2010 on the new MacBook Pro. Have you filed bugs?

Thanks, Bob. Got it. Looks like it is a legitimate IFC file. I am able to open it in Solibri Model Checker (our internal preference) with no reported errors. I'll send you the screen shots offline. This bring up a good point for all Vw IFC users. Look for and download an IFC viewer to verify the IFC file after it has been created. If the viewer can open and browse the file, then any other purported IFC capable program should be able to import it. IF not, then there is a bug on the other end that needs to be resolved. Solibri Model Viewer (PC and MAC) - FZKViewer (PC) - DDS-CAD Viewer (PC) - The viewers are also invaluable to let you inspect what hasn't exported from Vw. If something didn't get exported it is because it doesn't have IFC Data attached to it, via the "IFC Data..." command. Most, if not all, PIOs shoudl export automatically, without user interaction, but custom geometry and symbols need to have IFC Data attached by the user.

Bob, Could you please submit the VWX and IFC files that crashed for you in Revit? What versions of Vw and Revit were involved? We're currently working on guidelines/prescriptions for Vw BIMs that are interoperable with Revit and Scia and Bentley, but any user input/experience, at this point, would be very useful.

You're going to have a lot of problems using IFC to communicate between Vw2008 and Revit (which version, it matters). The quality of the the 2008 IFC export is not very good compared to 2010. Vw2009 SP4 was a BIG step up and 2010 was another big one, as well. You can try using DWG/DXF, as the AutoCAD users have to, but these results will also be mixed as Revit's pre-2010 DWG/DXF support isn't perfect either. Right now the best known/tested performance using IFC to communicate with Autodesk products is between Vw2010 and AutoCAD Architecture/MEP/Structural Detailing 2010 and/or Navisworks 2010. Revit 2010 is in third place, but definitely better than their 2009 or earlier versions, which are almost completely unreliable. Sorry, that's the current state of things. Much quality development on IFC has lagged as our competitors have slowly taken up the pace to improve their support, also.

Et al, Have these issues, and the files in which they are occurring, been submitted for review and investigation via Bug Submit? This board is NOT an official technical support or bug reporting resource. That is why we have links to those resources at the upper right. If you want a resolution to the problem, then you have to give the engineering staff the evidence of the problem so it can be analyzed and fixed. I, personally, have NOT seen this issue in the work I have been doing with Vw2010 since the last couple betas before release.

As a feature improvement, Vw 2010 allows multiple keynote legends to exist, in any location, even on the same layer, and Callouts as Keynotes to "subscribe" to any Keynote Legend in the current file, specified by the user.

Paul, Check out the Ellicott Heights PDFs at the web page that Christiaan linked to above. The White paper gives an explanation of why and how the file structure was set up, using referencing to create a BIM and come together in a single file for building elevations and sections. After you've taken a look at these materials, I'd be more than happy to discuss this with you further.

It is working in the latest version of VW2010 (SP2).

Ben, I was expressing my own PERSONAL OPINION. Learn how to chill out. I don't "hate" Windows as much as you seem to "hate" Apple. I just have my own personal preferences. Sheeesh... Take a pill..

I, for one, agree with the Kool Aide. Get two systems for the price of 1 1/2. Buy the iMac and buy a Windows 7 license. Best of the best(MacOS Intel) with the bonus of the rest(Windoze ...sorry Ben).

Thanks for the info.

Petri, At this point, I want to get to the bottom of this because your efforts are valuable, but the feedback through official channels (the Community Board is NOT included) has been non-existent. How are you reporting the bugs? Are you giving them to Ultirender? Are you emailing them to other NNA staff? Or are you submitting directly through the Bug Submit page on the main website? I have not seen any IFC bugs attributed to you, or Ultirender, in our BugTrack system since July 2008 (B068038:IFC GUIDs are not persistent, storeys are added on import). Without these BugTrack entries, our engineering staff cannot locate and fix issues. If there is a communication problem, I want to locate it and fix it so your efforts and needs are properly addressed and met. This benefits all of us. Please contact me in a PM to further discuss and resolve this issue.

Petri, I meant what I said and these points don't contradict. There are users working on this, but nothing has been finished or made available for submission, yet. Issues have been located and addressed. But more needs to be done and more users need to get involved. We need to play the odds to improve our chances of getting this done by expanding the number of opportunities for project models (of any size, type, or market). You could say there is a horse race, but the race means nothing until a horse (preferably two) actually crosses the finish (or Finnish) line.