Jeffrey W Ouellette

Christiaan, I am not talking down the geometry. But I think you are overstating the details, the bells and whistles, of specific features of specific workflows, in specific applications, and ignoring the more relevant big picture. I take issue with your persistent negativity toward VW as a BIM tool. I have tried to show in my BIM in Practice project files that there are valid tools and workflows, today, in VW, to create digital geometric analogies. VW does do "virtual building" well. But it does it differently than any of our competitors, and that is OK. Why should we all work the same way? I reject such insistence that VW, or specific features, need to be a clone of a competitor just because YOU feel the competition's workflow is preferable. Every BIM tool utilizes different technology, at its core, to implement different features and workflows that are tightly integrated. I have a great deal of respect for the technology that our competition does offer, but first and foremost, I think there is always an option to do it differently, in some cases better, than they do, and do it in a way that is consistent with VW technology and workflows. If you don't feel that VW is a viable BIM tool, it is your opinion. I think it is an erroneous opinion and I think you just need to learn how to use VW better, smarter, to get the most "BIM" out of it. Otherwise, you know you have other options. I don't deny that VW has room to improve and grow, but there are so many perspectives and factors involved in accomplishing this, at a global market scale, that having an entire community being taken hostage by one stubborn, vociferous user's opinions is not reasonable.

No application IS BIM. Many types of applications can be used as BIM tools, tools that are focused on particular interactions with the data model. I said 'data model', NOT 'model data', on purpose. Building Information Modeling IS Information Modeling, as in creating a database. In the case of AEC, the database is focused on the semantics of creating an analogy to, or a description of, a "building". Too often, we tend to focus more on the literal digital geometric analogy, than on the information itself. Any application that can tie into the database that describes the building, whether is is geometry-based, or not, can be used as a method/mechanism to view, report, or add viable information to the description of the building model. Not every application "builds" the model. Some "BIM applications" take the database, or a snapshot of it, and perform some kind of analysis, report, or presentation on it. Using VW and Excel, a user could create COBIE-compliant worksheets that allow a contractor or owner to qualify and quantify the MEP assets in a proposed design. They don't NEED direct access to the digital geometry model, just a report extracted from it. What makes it a BIM is the use of an open data standard, IFC, and a standardized reporting format, COBIE, along with software utilities in either applications, or standalone, to extract and transform the desired data into a desired format for use. In the US, the National Institute of Building Sciences and the buildingSMART alliance, in the form of the National BIM Standard, alongside the AIA's Integrated Project Delivery (IPD) and contract E202, have very thoroughly described what BIM IS. Other entities in the world, working together with buildingSMART International, are in sync with these efforts and descriptions. The data model is one part. The business processes/practices are another part. The standards to guide both of these are the third part. Together, BIM is defined. Pull out any of the three pieces and you don't have BIM anymore, just fancy CAD, or a smoother, but platform-restricted, project delivery. When standards are used, then a team of users in the process of designing, constructing, and managing a building, can take the data generated and, over time, use it, enrich it. This means that an Architect could use Vectorworks to create the building design, a Structural engineer could use Revit Structure to create the structural design, an MEP engineer could use Bentley Building Systems to design mechanical and electrical systems, the contractor could use Vico's suite of products to do 4D and 5D analysis and tracking, and the owner could use TMA Systems CMMS to track assets and schedule maintenance for equipment. Believe it or not, but it IS possible to go down this road TODAY. You can export an IFC model from Vectorworks 2009 and it can be imported, with a relatively high degree of fidelity into ArchiCAD 12 (OK but not the best), Revit Architecture 2010 (OK, but with different problems), AutoCAD Architecture 2010 (better than Revit or ArchiCAD), or Bentley Architecture V8i (very good). The user can browse and overlay the Vectorworks IFC model with other IFC models from these programs using Solibri Model Checker or Autodesk Navisworks 2010. So quit arguing about which application is BIM or isn't. The question is WHO of YOU are using BIM, or not? The tools are there. The processes and practices have been codified. The standards are in place to govern. The only thing missing are the users willing to dive in to put them together and do the work. The quick (but not easy) way out is to blame a platform and say BIM is only possible if you use one platform for the whole process. But that is a cop-out. Work together, work smart, and the tools shouldn't matter anymore. VW isn't BIM, but it is a BIM tool. Revit isn't BIM, but it is a BIM tool. ArchiCAD isn't BIM, but it is a BIM tool. The question is... Do you know how to use the tools?

Ooops! My bad! It turns out, when you use the "IF" to include more than one record (in this case a Door AND/OR Window), the two-way interactivity directly inside a cell is disabled. If it was a simple data filed header [e.g. =('Door'.'Manuf'], then the cell editing would work. You can still right-click on the Row Header and 'Select Item' will navigate to the object to edit, though. This led to an interesting discussion with one of our engineers and some ideas for how to improve functionality in the future....

Geez, guys, give me a chance to respond first before jumping ship... KBW, I've set up a worksheet in the file you posted. Using the IF function in a database worksheet can open up many doors (no pun intended). I would suggest that if you are going to list doors and windows together, they should all have a unique number, so there are no duplicate IDs. Otherwise, take Pat's suggestion and create 2 database rows in the same worksheet. Once you have the worksheet in place, remember that you can edit the values in the database worksheet to change them in the object. This bi-directional functionality is a very powerful feature in managing door & window data as your design progresses over time.

Post the file and I'll take a look. Also, look at the following post in the General Forum to get a better idea about how to use database worksheets. http://techboard.vectorworks.net/ubbthreads/ubbthreads.php?ubb=showflat&Number=111911#Post111911

Actually, you don't NEED a custom record format. It can be helpful, but you can create a database worksheet and set the criteria to look for both doors and windows. You can set the worksheet to display the common fields and sort by ID. I always suggest, that for custom database worksheets, users start with the "Create Report..." command. Choose one of the objects (door or window), the specify which fields you want to see. Accept the report and place it in the file. Next open the worksheet up and select the database row, right-click, then select "Edit Criteria...". From here you can edit what the database worksheet is looking for, without also worrying about the fields to display. First choose "Type" "is" "Door", then "More Choices", Add "Type" "is" "Window". Then you can choose to add more criteria like a particular layer or layers. Remember that criteria can be additive, as well as exclusionary. Try this as a first step and let's see if we can get you farther.

If they are properly aligned (the outer vertical surfaces exactly co-planar), there shouldn't be a line between the walls at the joint. I believe this was fixed for v12.5, but I know that versions 2008 and 2009 remove the lines for coplanar walls automatically. If you're not going to upgrade to the 2009 version, you should, at least download the updater for 12.5.3; http://www.nemetschek.net/downloads/fundamentals/version12/12.5.3.php You're best performance bet, though, is to upgrade to 2009.

It has NOT been fixed in 2009. Ideally, when a user starts to create their own custom finishes or door hardware, the application should write a new file to the User folder automatically, and point to that location. Right now, users should implement the steps I indicated above. It is a permissions issue, but not one that is user-fixable. The current files reside in the application folder. Users are not, should not, be allowed to write to the application folder. That is what the user folder and it's structure is for; to customize the application per user needs/desires. It is a system that work very well, when it is working. Some tools have slipped under the radar in adhering to this new system.

Peter, This is a known bug. But there is a solution until it is fixed (keeping fingers crossed it is in the next version): 1. Copy one of the "Prefs_" folders from the current plug-ins location (:Vectorworks:Plug-ins:VW_Arch:Data:) to a new location, either in your "User folder", or some other desired project or an office standards location. Rename it, if desired, "Prefs_". 2. Open command in Architect Menu "Tools > Options > VA Set Project Prefs... 3. Select "Add..." from pop-up dialog 4. Select "Browse..." from new "Add Preference Set" pop-up dialog 5. Navigate to the location of the new folder. 6. Select OK and Navigate back through the dialogs by confirming choices. 7. Now, any work done to the Door Hardware or Room Finishes should be saved, for that project, between sessions. You can copy this folder and rename it for other projects, too. I suggest that if you have a common set of finishes and door hardware for every project that you save it in a "library" folder. If the hardware and finishes are unique to every project, then you could create this in the project's folder. Just make sure VW is pointing to the correct location in each case. I'll do some more prodding on my end to see it gets fixed....

Jonathan (et al), Vectorworks? IFC support hasn?t been around for very long and is a work in process. That said, I can give you an outline of what is possible today. First, I am assuming that since you see the ?Export IFC Project...? command. This is available only to Architect or Designer installations. Also what version of VW are you using? VW 2009 SP3 currently supports the best results for IFC export. Secondly, there are a number of translations of VW elements/objects done automatically Space -> IfcSpace Wall -> IfcWallStandardCase Round Wall -> IfcWallStandardCase Floor -> IfcSlab Roof Face -> IfcSlab_Roof Roof -> IfcRoof Column -> IfcColumn Framing Member -> IfcMember OR IfcBeam Door -> IfcDoor Window -> IfcWindow Stair -> IfcStair Ramp -> IfcRamp Pilaster -> IfcColumn Handrail -> IfcRailing Countertop -> IfcFurnishingElement Cabinets -> IfcFurnishingElement HVAC Ducts & Accessories (with ?Show 3D Detail? option ON) -> IfcDistributionFlowElement Incandescent Fixture (with ?Show 3D Detail? option ON) -> IfcDistributionFlowElement Receptacle (with ?Show 3D Detail? option ON) -> IfcDistributionFlowElement Switch (with ?Show 3D Detail? option ON) -> IfcDistributionFlowElement Thirdly, beyond this list of automatic translations, the user is able to attach IFC data to any object by using the ?IFC Data...? command. Select the object, then select the ?IFC data...? command. You will be shown a very extensive list of ALL available IFC entities. However, many of these entities aren?t even supported by a Model View Definition, yet. We advise users who are familiar with IFC, to limit their choices to the ?root? entities, like IfcSlab (not IfcSlabType, this is set from within the interface). Next, select the option ?Use standard properties for this symbol.? This will expose all Psets available to this object type. Then, make sure the ?IFC Type? is checked in the ?Property Sets for this Object:? list below. Now, select/highlight the IFC Type in the list. This will populate the lower list window with a number of enumeration fields and property settings. Scroll to the bottom of the list and look for ?PreDefinedType?. When available, this will give the user the option to specify a ?sub-type? or ?enumeration?. If available, it will off a pulldown menu in the data field below the list. Select any one of the options. At this point, you can add other Psets in the upper list window, based on the sub-type of object it is and fill in some of the information. Some fields are greyed-out because they are filled in automatically by the translation. Finally, select OK and exit the dialog You will notice that the object doesn?t appear to have changed it?s identity in the Object Info Palette, because it hasn?t. It is still a ?native? VW object, just with the IFC data ?hanging? off it. You can select the object and return to this command and dialog at any time to change it?s IFC data. This is also useful for overriding the automatic translation of an object when you want it to be some other IFC entity. For example, I may want to use the VW ?Floor? command to make ceiling planes for rooms. For IFC translation, I just have to be sure I properly override the default associations with my own: Draw a rectangle/polygon Select the ?Floor? command. Give it a thickness and Z-value Move the slab to a ?ceiling? height Select the ?IFC Data? command In the case of a ceiling, choose ?IfcCovering? In the IFC Data dialog, choose ?Use standard properties...?, then select ?IfcCovering? In the lower list window, scroll to the bottom and select ?PredefinedType? From the newly exposed ?Enum value for selected property? data field below that, select ?CEILING? from the pulldown. Return to the upper list window and check ?Pset_CoveringCeiling? and ?Pset_CoveringCommon?. Done Finally, you shouldn?t see objects behave any differently after IFC data have been attached. If an object is ?moving? then it is either a bug that needs to be reported and verified (although I?ve never seen such behavior), or it is a problem with your installation or file. Regardless, please contact either your distributor or Tech Support. Please let me know if I can be of any more help.

Yes. VW supports images files such as pdf, jpg, png, and tiff. Just create a file/snapshot of the map you want, then import it into VW.

Bob, When is the workshop? I would encourage you to demonstrate VW BIM capabilities, especially using the BIM in Practice demonstration projects. The two current projects cover a lot of ground regarding modeling, database reporting, and drawing creation. I'll be adding another project very soon. It will be more focused on using VW tools to virtually construct a small project, to a great deal of detail and then using database worksheets to schedule the heck out of it, interactively. Less emphasis on actually drawing, as this can be gleaned from the Alexandria Lofts project, or even your own. There will also be an IFC component to the project. IFC is another important aspect of BIM. It is the lingua franca of interoperability, an open standard data format vs. a closed, proprietary standard platform. I think more members of the AECOO community need to understand the pitfalls of moving down the "DWG path", again. Users/owners should own their building data, free and clear, not subject to the whims of any particular vendor. I see IFC as a part of the "Holy Grail" for the future of exchanging, storing/archiving, and re-using AEC data, along with PDFs. Please feel free to contact me offline regarding this demonstration. I think it is important for your peers to understand that BIM doesn't equal Revit. Revit is a BIM tool, but NOT the only one, and may not be the best one for every person/firm or workflow. BIM is BIM, and any technology is only in service to it, a part of it.

Hans-Olav, There are two methods for the user to "attach" an IFC identity to both built-in and custom objects. They are available only in the Architect (or Designer) package. 1. "Create IFC Entity..." command a) Select the target object b) Select the "Create IFC Entity..." command c) You will get a dialog that will prompt you to pick the IFC Entity you wish to attach. At this time, this list includes ALL IFC Entities. You will have to have some working knowledge of IFC to wade through the list and select the particular and appropriate entity. d) Next, you will see an "IFC Data" dialog. This will give you a place to input the data related to the appropriate IFC Psets for a corresponding IFC Entity. Make sure to select the option "Use standard properties for this symbol." e) In many cases, you will need to select the "PredefinedType" at minimum, in order for the IFC data to be assigned to the object and for it to export correctly. f) At this point, the object will appear in the Object Info Palette as an "IFC Entity" and list its data. This is now a VW IFC container object. g) To edit the geometry of the object, just use "Enter Group". 2. "IFC Data..." command Steps a) through e) are the same, however, instead of a VW IFC container object being created, the object maintains its VW identity and has the IFC Entity and data attached to it "in the background". This is useful for either custom geometry (either in symbols or not) or overriding the default translator mapping of VW objects to corresponding IFC entities. At this time, VW 2009 provides the best performance and results in IFC export. Many, but not all, VW plug-in objects currently export automatically to IFC (e.g. walls, floors, doors, windows, roof faces, framing members, railings, stairs, columns, and spaces). Up to now, we have focused on supporting the objects for which there has been formal MVD definition and requirements. Also, the commands described above give the VW user a unique ability to create any geometry and make it an IFC compatible object. We will continue to improve both options for our users. Unfortunately, IFC import is still not as good as our export. Much, but not all, of this has to do with handling the IFC data from other applications that may NOT produce "standardized" IFC files. My hope is that as significant progress is being made by buildingSMART International in better, standardized testing procedures, tools, and results, that ALL vendors will produce higher quality data exchanges. This will take time, though. NNA actively participates in IFC-centric workshops/events/programs to improve our development and knowledge. To date, we have worked with the U.S. GSA on there Spatial Program Validation initiative, Onuma, Inc. on the Onuma Planning System BIMStorms, and the Open Geospatial Consortium, inc. on the AECOO Testbed. I am always looking for more users interested in using IFC in a BIM methodology, to communicate more closely with our efforts and provide feedback on how we can improve. Please feel free to contact me directly.

manfredi, Send me a Private Message with your email address and I will send you a link with 2D and 3D files, both v2008 and v2009 format. One file will be the Space Program, containing Space PIOs for the different programmatic elements. Another file will be the Site, in 3D, and another the Site in 2D.

Right now, failure at import of the IfcSite object is a known issue. I'm looking for a workaround. The "extruded squares" should be Space PIOs (please note that the Name and Number appear swapped - another known issue). The purpose is to give entrants an idea of area sizes for each programmatic element. They are not arranged in any particular sequence/order/spatial config. The DWG file is not as comprehensive or as clean as I had hoped. In fact, it seems to be fairly poorly encoded. Usually, a site dwg will contain 3D polylines for contours, buildgin and roads. I'm not sure what the heck is going on with the contours in the supplied file. It may be best to use it strictly as a reference and build a VW DTM over the top.

By word of our Norwegian distributor, it appears that there is supposed to be an update of the digital files (ifc and dwg). I will keep you posted. In the mean time, let me see if I can get you a 2008 version of what we were able to import, to get you started. FYI: The site did not come through the IFC translation (v2009), but did in the DWG import. The space objects did come through in the IFC translation (v2009).

Also, for best results both import and export of IFC, you are going to need v2009. Significant work has been done in this translator since v2009 was first launched. Can you also tell me what other IFC-capable tools you are using (e.g. Solibri, MagiCAD, DDS, IfcStoreyViewer)?

Aww, Ozzie beat me to it!

With database row 1 highlighted, move your cursor up to the little itty-bitty "SUM" button located above the Column 'A' label and click-drag-and-drop it on the A1 cell. This will give you a summary of each common field entry. If you grab the little ascending button (the one on the right) and drag-and-drop on the same cell, it will sort alphabetically. Let me know if it works or you need more help.

I think this can be accomplished by using the Space objects and a custom database worksheet by using IF statements to "see" the value of a finish in the Space object as it is formatted there, but then display it as needed in this schedule. I must admit, that this is the first time I've ever seen a Room Finish Schedule like this. It may be "old school" but I have no idea what school it came from... Let me clear a couple things off my plate and see if I can help you out next week. Is that early enough?

Manfredi, Is this related to the Statsbygg sponsored National Museum of Art, Architecture and Design at Vestbanen Competition?

Submit a bug, not a wish.

Vincent, Why not create multiple Sheet Layers? Each Sheet Layer can have its own 'paper size' and orientation and own unique Drawing Border/title block.

I think what he means, Christiaan, is making the Mode Bar float next to the cursor(currently is is 'adhered' near the top of the drawing window), like the Floating Data Bar.

Vincent, You can have as many DLVPs you want on any design layer. You can Copy/Paste any DLVP to the same layer or another design layer, it automatically renames itself. DLVPs are objects, just like symbols or any other PIO. You can Lock them in place, change/override all their visibility attributes. You can attach Record Formats to them, just like symbols. I used DLVPs extensively in the Ellicott Heights BIM in Practice project. Every level of the main building was modeled in a separate file. The parking garages were each modeled as separate files. The site was another file. Then, in a centralized model file, I created DLVPs on each design layer to 'compose' the building on the site. Then, I used DLVPs to insert the residential unit plans on the residential floors. Essentially, each unit plan (four of them) was 'imported' once, but copied, mirrored, rotated and, uniquely named (using a nomenclature system to track the unit type and number and address). The naming allows me to schedule the units, quantifying them in various ways.