Ok, this is a bit counter-intuitive but: If you want to export parameters from Revit to an IFC file, note that the parameters should not be grouped under the category “IFC parameter”, but under a different (eg, .. ID data, text) category.
This is because the IFC parameter group is for inbuilt / standard IFC parameters.
I think this was previously called DataSlider. To get it, just close Revit and Vasari and open your Case Add-in Manager (it may want to update itself). Then tick the Migrate Parameter to Parameter box and Install/Update checked.
From their website: CASE APPS Migrate Parameter Have you ever needed to schedule an item of data that Revit would not let you? This is a common hurdle for many and now there’s a free tool that you can use to get around this. Common uses include migrating Wall Base Constraint Element Names (Levels) into a schedulable parameter. I’m sure you guys will find lots of uses for this one.
You can export from the Family or Project environment. If you already have a SP with the same name in your current SP file, you will need to switch to a blank SP file, export the parameter, and then possibly you can “hack” it into your current file by text editing the SP files (maybe).
Revit doesn’t let you tag Wall Volume by default, so Avisotskiy puts RDBLink to good use – he uses Microsoft Access to update a Shared Parameter with the wall Volume data, and then simply uses a tag to grab the manually updated and manually created Volume data.
This is not a ‘live’ link, but it shouldn’t take too long to round trip the project to update the Volume information prior to document transmission or printing.
From his blog: Revit does not allow to directly make a mark in the volume of the object. …
4. Unload in Access, using the Query Designer update the “_Obem”, taking data from the parameter “Volume”.
Martijn de Riet has pointed out something very useful when you are trying to use a Calculated Value to pull together a bunch of similar-but-different parameters. If you come across an error, don’t forget about the ‘Add to all elements in the selected categories’ check box in the Parameter Properties dialog.
The Problem: When you create the first (window) schedule you’ll notice a whole bunch of width parameters, all referencing the total width of different windows (fig 1) After creating the schedule you figure: let’s create a “scheduled width” parameter which adds up all those separate width parameters. This way you can clean up your schedule (fig 2). Only to find that it won’t calculate. In this case, the family “ontwerpraam doesn’t have the parameter “breedte_vo” so in the schedule it returns no value. Therefor, the total cannot be calculated (fig 3).
The Solution: Open the schedule properties, go to the Fields Tab, select the parameter causing problems and click Edit. In the Parameter Properties, check the checkbox “Add to all elements in the selected category”, select the category “windows” and choose whether it should be an Instance or Type Parameter (fig 4). The parameter is now accessible in the schedules, even with the families it’s not actually in. You can now fill in a value and the Scheduled Width parameter will calculate properly (fig 5). It will even show up in the family’s properties (fig 6).
Essentially, in any schedule you can actually add Project Information parameters. This includes Sheet Schedules, Component Schedules and Material Takeoffs, but not Note Blocks. All you need to do is tick the ‘Include Elements in Linked Files’ box to expose the ‘Project Information’ option in the dropdown list. And when you add custom Project Information parameters, make sure you tick ‘Instance’ in the Parameter Properties box (otherwise you won’t see Project Information as a possible category for your new parameter).
My brain is starting to tick over as to possible uses of this in filtering and calculation… You could use it to set a provisional unit cost for flooring, use the parameter in a number of different cost schedules, and then 6 months down the track if the cost changes – you only have to change it once, in Project Information!
You could filter all of your schedules with a Yes/No Project Information parameter, lets say for ‘optional building elements’, and when the Client decides they don’t want them – just untick the box in Project Information and all the schedules hide all of these optional elements. That is cool!