Sending schedule data from Revit to Flux

07/04/17 — Individual Exploration

Using the sample project in Revit I was able to create schedules for various components including;

• Rooms
• Floors
• Doors
• Windows

Although the sample is a multi-storey residential complex, the same principles can be applied to the scheduling of a pavilion. In the pavilion we should be providing the following schedules:

• Spaces — to define the function of each space inside the pavilion

Data to be collected: Space number, Function, Area, Unbounded Height

• Entries/Exits — to locate flow of people

Data to be collected: Space number, Function (Interior or Exterior), Height, Width

• Openings — to highlight light sources

Data to be collected: Space number, Area, Perimeter

• Grid — members

Data to be collected: Total quantity, Type/Number, Length, Width, Location, Material, Cost

• Fabric — the cover

Data to be collected: Location, Space coverage (percent)

• Joints — for the grid and to attach fabric

Data to be collected: Function (grid or fabric), Type, Number, Location, Material, Cost

Scheduling and data transfer

Revit to Flux — using Flux plugin on Revit, I simply sent over Revit data through to Flux.

Flux scheduler — chose the schedule I wanted to view, for example; space schedule as shown below. By clicking on a room / space on the left OR directly onto a line of information on the right, you can quickly view all of the information and data about that area OR view which geometry is associated with that information. This can can become quite useful in the pavilion project if spaces were associated with members / nodes. So we will be able to quickly associate a node or member with its Function, Type, Number, Location, Material and Cost for example.

Displayed on the left of the image, I am choosing data to be viewed in table format on the right

Visualising spaces and their unique data and information displayed on the right

Other schedules— we can easily view other information simply by creating or selecting from existing schedules already created.

Overall I think scheduling through Flux will improve efficiency within the pavilion project as it is simple to set up and will be easy to navigate during project construction.

I wanted to test out some live data changes and view how instant they were between the platforms.

With a click of a button, I found that you had to manually press update in Revit’s Flux app. But the changes were instant. I think this could be applied to the pavilion project as we can then transfer this data gathered in Flux and then again through Flux send it to Excel and use it for construction purposes. It will ensure that all information is continuously updated without the need to cross check, maximising workflow.