...
Table of Contents | ||||
---|---|---|---|---|
|
Create / update spaces based on Rooms in the Architectural (linked) model
...
1.Linked Model: Add or update the model you are creating spaces from.
2. Verify that levels are named the same in both models.
Levels from linked model can be copied. Read more:
https://knowledge.autodesk.com/support/revit/troubleshooting/caas/CloudHelp/cloudhelp/2020/ENU/Revit-Collaborate/files/GUID-3B5AAC45-B5DC-48C0-8312-B90F06653F37-htm.html3. Set Attribute configuration for:
a. Room <--> Revit Room. Below is an example:
...
b. Room <-->Revit Space. Below is an example:
...
Read more Revit Attribute Configurations.
4. Select "Linked model Rooms - > Spaces" from the dRofus Add-On ribbon:
...
Window will appear
...
5. Tick the box to the model you would like to import Rooms from
Info |
---|
Room bounding: By default all linked models that are set as Room Bounding will be selected |
...
...
. Linked model that is not room bounding, |
...
will be set as Room Bounding when you copy them. | ||
Info | ||
---|---|---|
|
Click on "OK" to create the Spaces from the selected linked model(s), and then a message similar to the one below will then pop up6. Verify that the right Attribute configurations are used:
...
7. Verify that the correct data is being copied and used to comparing.
The attributes “Number”, “Room Name”, Base Offset” and “Limit Offset” will be copied by default
...
8. Select “Ok”
Message will appear, summarizing the total number of Spaces:
Created
Updated
That were not created/ updated
...
, due to the chosen key parameter within Rooms in the linked model being either not unique or empty
...
...
When creating / updating Spaces from an Architectural (linked) model, the values of the following attributes will always (by default) be copied from Rooms within the Architectural (linked) model in to Spaces within the Services (host) model:
It is also important to take note of the active Room as well as Space Configurations:
The active Room Configuration will use the mapping of the "Key Attribute used for comparing" in order to find Rooms within the Architectural (linked) model which correspond to Rooms within dRofus, after which the active Space Configuration will then be used to populate the necessary values within the Attribute / Parameter chosen as the "Key attribute used for comparing" to then establish and maintain a link between Spaces in the Services (host) model and Rooms in dRofus:
In addition, the above process will also use the active Space configuration to push and pull values as per the mapping of other Attributes / Parameters.
In the example above, the active Space configuration called "Revit Spaces" uses dRofus' "Room ID" as the Key Attribute (the value of which gets pushed in to the host model's corresponding Space parameter), and in addition has been mapped to bring in values of "Note" and "Room Function #" from dRofus Rooms in to "Comments" and "drofus_room_func_no" respectively in Revit Spaces as follows:
Hence these are also listed in the section "Attribute values to be copied from Rooms to Spaces" as follows:
And the values have been brought in to a new / updated Space within the host model as follows:
Also note that during the above command, the "Number" and "Name" parameters within the host model's Spaces will always get values copied across from these parameters within the linked model's Rooms (even though these may not be mapped to be brought in from dRofus Rooms within the active Room configuration):
...
Below you can see an example:
...
The attribute configuration has been used to write data to the created and updated Spaces:
...
Changes in Architect model.
Rooms in the Architect model can be added, deleted, moved, changed in shape and size etc. Once the updated Architectural (linked) model has been re-issued and re-loaded as a link to the Services (host) MEP model, the Services Consultant Engineer will again need to carry out the above process in order for the Revit Add-On to transfer all of the updates to the changed Spaces.
...
If
...
any
...
Rooms have been deleted in the Architect model, you will be asked if you'd like to "Delete Superfluous Spaces"
...
Level Names Mismatch
If the host and linked Level names do not match when creating / updating Spaces in the host model, you will get the following message:
You will need to ensure that the Level names are consistent between the models, next time you updating your spaces.
Creating / Updating Spaces Based on Spaces within Linked Models
It is You can also possible to create or update Spaces within a host model based on Spaces within a linked model. It is possible that on certain projects Revit is only being used by the Services Consultants. As an example, the Electrical Consultant is the lead consultant in a project and is responsibile for driving / maintaining Spaces, then once the Electrical Consultant issues their model to the other Services Consultants (such as Mechanical / Hydraulic / Fire etc.) then the Electrical model will be linked in to these other Services (host) models so that these other Services Consultants can then refer to the Space extents as defined by the Electrical (linked) model) to place their Family Instances / Systems accordingly. If the Spaces in the Electrical (linked) model have already been linked to Rooms in dRofus by the Electrical Consultant, then these other Services Consultants can conveniently create and / or update their Spaces within their Services (host) models based on the Spaces in the Electrical (linked) model. Furthermore, if there is information in regards to (planned) services Item occurrences for these Rooms in dRofus, and the Family Types in these other Services (host) models have already been linked to Items in dRofus by these other Services Consultants, the Services Consultants can then easily view as well as validate the Family Instances within their Revit Spaces against the (planned) occurrences of Items in the dRofus Rooms using either the "Items in room" or "Items in level/model (spaces)" window.
To create / update Spaces in the Services MEP (host) model (based on Spaces in another Services MEP (linked) model), select "Linked model spaces - > spaces":
...
Level Names Mismatch
If the host and linked Level names do not match when creating / updating Spaces in the host model, the following message will appear:
...
Ensure that the Level names are consistent between the models.