Revit - Orion Integration

Delivered by

Integration

Integration of Orion and Autodesk Revit Structure

For support and training on the full rangeof CSC products, please contact...

Support: [email protected]: [email protected]

:

CSC Offices Worldwide

UK Singapore United States

CSC (UK) Ltd.Yeadon HouseNew StreetPudsey, LeedsWest YorkshireLS28 8AQUK

Civil & Structural Computing [Asia] Pte Ltd3 Raffles Place#07‐01 Bharat BuildingSingapore 048617

CSC Inc500 North Michigan AvenueSuite 300ChicagoIL 60611USA

Tel: 0113 239 3000Fax: 0113 236 0546EMail: [email protected]

Tel:+65 6258 3700Fax:+65 6258 3721EMail: [email protected]

Toll Free: 877 710 2053Fax: 312 321 6489EMail: [email protected]

Malaysia Australia Hong Kong

CSC WORLD (Malaysia) Sdn BhdSuite B‐12‐5, Block B, Level 12North Point OfficesMid Valley City No.1, Medan Syed Putra Utara59200Kuala LumpurMalaysia

Civil & Structural Computing Pty LtdLevel 3349 Coronation DrivePO Box 1843MiltonQLD 4064Australia

CSC Level 21 & 46The CenterNo. 99 Queens Road Central Hong Kong

Tel:+60 (0)3 2287 5970Fax:+60 (0)3 2287 4950EMail: [email protected]

Tel: 1300 882 393Fax: 07 3378 5557EMail: [email protected]

Tel: +852 3478 3980Fax: +852 3478 3880EMail: [email protected]

2012 May 2 Delivered by


Disclaimer

Disclaimer CSC (UK) Ltd does not accept any liability whatsoever for loss or damage arising from any errors which might be contained in the documentation, text or operation of the programs supplied.

It shall be the responsibility of the customer (and not CSC)

• to check the documentation, text and operation of the programs supplied,

• to ensure that the person operating the programs or supervising their operation is suitably qualified and experienced,

• and to ensure that program operation is carried out in accordance with the user manuals,

at all times paying due regard to the specification and scope of the programs and to the CSC Software Licence Agreement.

ProprietaryRights

CSC (UK) Ltd, hereinafter referred to as the OWNER, retains all proprietary rights with respect to this program package, consisting of all handbooks, drills, programs recorded on CD and all related materials. This program package has been provided pursuant to an agreement containing restrictions on its use.

This publication is also protected by copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express written permission of the OWNER.

This confidentiality of the proprietary information and trade secrets of the OWNER shall be construed in accordance with and enforced under the laws of the United Kingdom.

Fastrak documentation: Fastrak software:

© CSC (UK) Ltd 2012 © CSC (UK) Ltd 2012

All rights reserved. All rights reserved.

Trademarks Fastrak™ is a trademark of CSC (UK) Ltd. Tedds® is a registered trademark of CSC (UK) Ltd. Orion™ is a trademark of CSC (UK) Ltd The CSC logo is a trademark of CSC (UK) Ltd.

Autodesk and Revit are registered trademarks or trademarks of Autodesk, Inc., in the USA and/or other countries.

Microsoft and Windows are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.

Acrobat® Reader Copyright © 1987‐2012 Adobe Systems Incorporated. All rights reserved. Adobe and Acrobat are trademarks of Adobe Systems Incorporated which may be registered in certain jurisdictions.

All other trademarks acknowledged.

2012May 4 Delivered by

Table of Contents

Table of Contents

Chapter 1 Overview of Integration. . . . . . . . . . . . . . 5

Chapter 2 Orion into Revit Structure . . . . . . . . . . . . . 6

2.1 Creation of the Orion Model . . . . . . . . . . . . 6

2.2 Deliverables . . . . . . . . . . . . . . . 7

2.3 Initial Export from Orion . . . . . . . . . . . . . 7

2.4 Initial Import into Revit Structure . . . . . . . . . . . 8

Chapter 3 Revit Structure into Orion . . . . . . . . . . . . . 13

3.1 Creation of the Revit Structure Model . . . . . . . . . . 13

3.2 Exporting a model from Revit to Orion . . . . . . . . . . 16

3.3 Initial Import into Orion . . . . . . . . . . . . . 20

3.4 Important Notes for Starting the Model in Revit Structure . . . . . . 21

3.4.1 Some key rules/things to note in the Revit model . . . . . . . . 21

Chapter 4 Synchronizing Models from Orion into Revit . . . . . . . . . 29

4.1 Synchronizing Orion to Revit Structure . . . . . . . . . . 29

4.1.1 Export from Orion . . . . . . . . . . . . . . 294.1.2 Synchronizing a model From Orion To Revit . . . . . . . . . 29

Appendix A API ‐ Application Program Interface . . . . . . . . . . . 34

A.1 API ‐ Application Program Interface . . . . . . . . . . . 34

Appendix B Information Transferred . . . . . . . . . . . . . 35

B.1 From Revit Structure to Orion . . . . . . . . . . . . 35

B.1.1 Information Transferred . . . . . . . . . . . . . 35B.1.2 Limitations . . . . . . . . . . . . . . . 35

B.2 From Orion to Revit Structure . . . . . . . . . . . . 36

B.2.1 Information Transferred . . . . . . . . . . . . . 36B.2.2 Limitations . . . . . . . . . . . . . . . 36

Appendix C Showing The Integration Status With A Filter . . . . . . . . . 37

1 : Overview of Integration

Chapter 1 Overview of Integration

When considering the integration of Orion and Revit Structure it is important to understand that the information transferred is essentially the physical information associated with the structure ‐ e.g. geometry, section sizes, grade and slab thicknesses etc.

Orion is a code‐based modelling tool to enable Structural Engineers to establish a code compliance design of the structure (for example EC2, BS8110). Revit Structure is principally a physical modelling tool for the production of drawings, material lists and BIM coordination. As Revit does not hold 'code' specific data it is important to understand that all the design/code data is held within Orion at all times.

In a typical design office, the Technicians are responsible for drawing production whilst the Engineers responsibilities include code compliant design. It is therefore common for the Engineer to be the predominant user of Orion and the Technician to be the predominant user of Revit. This of course varies from company to company where the role of the Technician and the Engineer merge, however the principles remain the same.


2 : Orion into Revit Structure

Chapter 2 Orion into Revit Structure

2.1 Creation of the Orion ModelThe Engineer has a number of options available to him when creating an Orion model.

1. Create model from Scratch.

• Orion includes typical modelling tools to create grids, columns, beams, walls, floors etc. Importantly each element is modelled as a physical object which can be positioned correctly in space.

• When synchronised with Revit Structure, the true spacial position is communicated along with items such as sections size and grade.

• For further information on creating Orion models please see the Orion user manual or visit www.cscworld.com.

2. Import 2D Drawings.

• It is common early in a project to have a number of 2D architectural drawings outlining the scheme. Orion has the facility to import 2D DXF drawings.

• The engineer can use these drawings as ghost layouts in the background to aid setting out or to import grids, columns and walls.

• If a common grid is used on the project, it is logical to import this grid into Orion to ensure the structure is set out in the correct position.

• When importing grids it is also advisable to check the geometry of the grid thoroughly.

3. Part Models.

• At the early stages of design it is possible to create part models to investigate a structural scheme.

• For example the engineer can model just a floor or a bay in Orion to investigate the best solution to satisfy code compliance and economics.

• Although only a part model, this can still be sent to Revit Structure. (Note, the physical position of the part model will be communicated to Revit Structure.)



2.2 DeliverablesEven at these early stages of a project Orion provides a significant number of the deliverables required.

For example:‐

• Comprehensive code compliant scheme design,

• Material take off,

• 2D engineering DXF drawings,

• 3D model visualisation,

• Foundation Loads.

2.3 Initial Export from OrionOnce a model has been created in Orion, you need to save the model with a recognisable name and then run the command File > Model/File Export > Export to Revit Structure. This process creates a .cxl file with a user defined file name in a chosen directory.



2.4 Initial Import into Revit StructureThis example covers the import of a correct model into Revit Structure using the CSC Integrator. The file that we are using contains no mapping problems and reference should be made to the relevant sections should you find that your own file does have any problems regarding mapping.

Firstly, activate the CSC Integrator program by clicking on the icon held on the Add‐Ins tab.

The following splash screen provides some information about the two base design products used with the CSC Integrator along with hyperlinks to the relevant website page. Click Next to move onto the next page.



The next dialog of the CSC Integrator allows various import and export options to be set for each of the two design programs.

In this example, we are importing a file created from Orion and we do not currently hold a Revit model to synchronize into. We therefore choose the option Import model from Orion ‐ First Time.

Click Next to continue after making your selection.

Having chosen the software and the correct import/export option, you will be prompted to select the file (and location) that you wish to import.



Select the correct information and then click Next to move onto the next dialog.

The Select Structural Objects to Import dialog allows you to control which items will be imported into Revit Structure. As a default, all items are flagged for inclusion in the import but if you have a requirement to omit certain items (say all Gridlines), then simply untick the item option.



The Section and Material Mapping dialog indicates the different section families detected in the importing file. If there are any numerical entries in the Not Recognized column then there is some mapping discrepancies and these should be investigated before continuing further. (See separate section on mapping objects).

Even if the mapping is correct and no problems exist (as per the example shown), the actual mapping can be checked by clicking to select the Review Mapping option for all Columns, Framing and Materials.

Click Finish to exit from the integrator dialog and start the processing of the file.

Having completed the use of the Integrator dialog, the importing CXL file will now start processing. This is a stage that is run automatically by the application and covers the actual building of the model, loading the correct families etc.



Once the processing of the 'CXL' file has been completed, a log file will be shown. The log file is simple a text file and a record of the objects imported, deleted or altered along with any warnings.

Please note that the log file is automatically saved in the same directory location used for the CXL file location (although this can be manually moved at a later date).

When exporting models from Orion for Revit integration please ensure that the part marks assigned to structural objects only contain alphanumeric characters. If non‐alphanumeric characters are used within the Orion part mark references then a software crash may be encountered on import into Revit.


3 : Revit Structure into Orion

Chapter 3 Revit Structure into Orion

3.1 Creation of the Revit Structure ModelWhen the design process is started in Revit, there are a number of considerations to be made.

From Revit Structure • A Revit Structure model can be exported to Orion in part or in full.

• To export a part model, first select the members you wish to export, prior to creating the export file.

• Only the main structural elements to be designed should be exported.

• The analytical wire model created within Revit Structure must be fully connected before exporting to Orion.

Structural Analysis Settings Within Revit• The option to enable a members analytical wire is held in the structural properties dialog of the individual member ('Enable Analytical Model' tickbox option).



• Other analytical properties can be checked and modified by accessing another page of the members properties.

• Within the Analytical properties of a given member is the option to amend the Analytical Alignment, giving the user various options to control the analysis wire location. Although it is possible to adjust the wire position differently at each end of the member, this will not be reflected in the resulting Fastrak or Orion model.

• We strongly recommend that structural columns should be modelled with the analysis wire positioned centrally about the column itself (centre of gravity position). However for columns which are offset from a given set of grid lines, then the wire can also be positioned on the grid intersection by altering the x‐Direction and y‐Direction Projection settings.



• Please note that the same settings applied onto the base projections should be also set on the top projections, and vice‐versa.

• For beam members where the analysis wire should be located on an edge of the member, we recommend that the 'Lateral Justification' setting ('Structural' page) is manipulated to suit either side1 or side2 as necessary.

When working with a Revit Architecture model• Orion will only communicate with Revit Structure.

• If a Revit Architecture model is available all structural components modelled in Revit Architecture must have analytical properties enabled (or be redrawn) before integration with Orion can take place.



3.2 Exporting a model from Revit to OrionThis example covers the export of a completed Revit model into CXL format using the CSC Integrator. The CXL file would then be imported into Orion as a Standard Import.

The file that we are using contains no mapping problems and reference should be made to the relevant sections should you find that your own file does have any problems regarding mapping.

To export the model to Orion, activate the CSC Integrator program by clicking on the icon held on the Add‐Ins tab.





In this example, we are exporting a model for use with Orion. The model will be imported so that an analysis model is set up from scratch. We therefore choose the option Export model to Orion ‐ First Time. Click Next to continue after making your selection.

The Select Structural Objects to Import dialog allows you to control which items will be imported into Fastrak/exported from Revit Structure. As a default, all items are flagged for inclusion in the import but if you have a requirement to omit certain items, then simply untick the include option for that item.



The Section and Material Mapping dialog indicates the different section families detected in the importing file. If there are any numerical entries in the Not Recognized column then there is some mapping discrepancies and these should be investigated before continuing further. (See separate section on mapping objects).

Even if the mapping is correct and no problems exist (as per the example shown), the actual mapping can be checked by clicking to select the 'Review Mapping' option for all Columns, Framing, Materials and Steel Decks.

Click Next to move onto the next page.

Having chosen the software and the correct import/export option, you will be prompted to select the file (and location) that you wish to export to.



Select the correct information and then click Finish to exit from the integrator dialog and start the processing of the file.

Once the processing of the CXL file has been completed, a log file will be shown. The log file is simple a text file and a record of the objects exported, deleted or altered along with any warnings.




3.3 Initial Import into OrionIn Orion, with no model open, using the command File >Model/File Import > Import from Revit Structure, locate and open the .cxl file created in Revit Structure.

The final part of the import process consolidates the members and axes after which a message box will be displayed, followed by a list of warnings / errors that have been detected by the import process.

There are a number of recommended actions that you should consider before proceeding with analysis and design.

• Add slabs to the model

While a draftsman is liable to think of a slab as a single extensive area, an engineer sees a slab as numerous discrete panels each of which requires separate design. In addition, in Orion loads are generally added along with the slab panels. By taking control of the panel creation and loading the engineer is taking control and responsibility for the design.

• Review and edit project parameters, default materials and other data that the draftsman would generally not be responsible for.

• Use the re‐label members command.

• Use the Building Model Validity Check.

• Duplicate levels are not supported by Revit. Where there are lots of duplicate floors it would save you time if you establish any duplicates.

• Columns can become discontinuous where different insertions are used on different storeys. Warnings will be given during analysis. This situation can be avoided by having sufficient grids in the initial Revit model so that few if any grids need to be created by Orion.

• Walls in Revit automatically join to other walls and are "cleaned‐up" graphically. However, when imported into Orion, there are no extensions and so the corners will look incomplete.



3.4 Important Notes for Starting the Model in Revit Structure

3.4.1 Some key rules/things to note in the Revit model

Autodesk provide an Application Programming Interface, (API), to enable CSC to query and modify the Revit model, but this means that the links are constrained by any limitations of that interface.

Good Practice — The best information that the API makes available when extracting model information is the underlying analysis data. When importing, Orion will use the Revit analysis model to build its own analysis model but difficulties / inconsistencies may arise, which can be reduced by good practice in constructing the Revit model.

• Add levels to the Revit model for each storey to be designed and use special names for the bottom of the first storey and optional to indicate the depth of foundations.

• Use "FOUNDATION", "FOOTING", or "FTG" to indicate the depth of foundations.

• Use "TOF", "BASE", "BASEMENT", "TOB", "GRO", "GROU", "GROUND", "ENTER", or "ENTRANCE" for the bottom of the first storey.

In the example below, the first storey will be from 0 to 3000mm with a foundation depth of zero, (because no suitable level is defined).



In the second example, the first storey will still be from 0 to 3000mm but the foundation depth will be set to 600mm.

• The model transfer procedure can be significantly improved by the addition of grid lines in Revit. As a minimum it is suggested that main grids along column and wall lines should be created.

• Where possible, use the standard Revit families for beams and columns.

• Where possible, allow Revit to automatically clean up the joins between beams, columns, walls and slabs.

• Model columns from level to level. Where slabs are required at slightly different heights in different wings of a building, it may simplify the model to use fewer levels in Revit and use vertical offsets to obtain the correct physical locations of the columns. However, if the physical length of the column is longer than the analytical length, then the design may be unconservative. It is also possible to create columns where the analysis wires overlap if the wrong settings are used in Revit.

Standard Column - Level to Level.



Vertically Offset Column - conservative lengths

Vertically Offset Column - unconservative length



• Model beams from reference point to reference point, not physical face to physical face and use the levels in the element properties. Each beam needs to be defined as the full depth of the rectangular section, not depth below the slab. Flange widths for design are determined automatically in Orion.

Vertically Offset Column - Overlapping Analysis Wires

Correct and Incorrect Beam Definition Points



Correct and Incorrect Beam Deph

Do not model beam flange



• Similarly model walls from reference point to reference point, not physical face to physical face and use the levels in the element properties. Also make sure Structural Usage property is set to "Shear" or "Structural combined".

Note : In some example Revit models, we have seen corrupt analysis wires for walls, especially where multiple openings have been applied or Revit's auto‐detection has failed.

Definition Points for walls



• Where beams and columns are offset horizontally from their centre‐lines, care must be taken with the Revit properties to ensure that the Analysis model is exported to Orion effectively.

• Move columns into position in plan views ‐Revit columns have no properties to achieve this anyway. Ensure that "Rigid Links" are checked for columns.

• Also move beams into position in plan views ‐ Revit beams do have properties for this, but ensure they are set to Center and turn‐off the Auto‐detection of the horizontal projection.

Similarly move walls into position in plan views and set the Location Line and Horizontal Projection properties to Center.

Any framing member located on the level which will be set as ground level within Orion will be altered on import.

The vertical justification for all beam members on the ground floor must be set within Orion to be “Bottom of Section”. This stipulation may cause beams to be amended on import.

The requirement for “Bottom of Section” justification will be communicated on returning the model to Revit and may result in framing members being modified during the merge process.



Users may find that analysis wire locations are amended after the transfer of the model from Revit into Orion. This amendment should not cause any problems during the analysis and design stages and may be ignored.

The updates to the analysis wire locations for all existing members will be ignored on return to Revit and the positions will be unaffected during the merge process.


4 : Synchronizing Models from Orion into Revit

Chapter 4 Synchronizing Models from Orion into Revit

After an initial import has taken place it is typical for both the Orion and Revit Structure models to be developed independently.

However as the project and design of the structural frame is refined, it is appropriate to synchronize the models together to communicate any changes in geometry, section size, and design parameters. This is easily achieved by repeating the import procedures.

4.1 Synchronizing Orion to Revit Structure

4.1.1 Export from Orion

To send the changes made in the Orion model to Revit Structure the export procedure is repeated ‐ File ‐‐> Model/File Export ‐‐> Export to Revit Structure. As always, before the export, it is advisable to save the model to a clearly named file so it can be returned to, should the need arise.

4.1.2 Synchronizing a model From Orion To Revit

This example covers the import of a second (updated) CXL file into Revit Structure using the CSC Integrator. The file that we are using contains no mapping problems and reference should be made to the relevant sections should you find that your own file does have any problems regarding mapping.

Firstly, with the current Revit model open in the background, activate the CSC Integrator program by clicking on the icon held on the Add‐Ins tab.





In this example, we are updating an existing model with a new CXL file created from Orion. We therefore choose the option Import model from Orion ‐ Update Existing. Click Next to continue after making your selection.



Having chosen the software and the correct import/export option, you will be prompted to select the file (and location) that you wish to import.

Select the correct information and then click Next to move onto the next dialog.



The Select Structural Objects to Import dialog allows you to control which items will be imported into Revit Structure. As a default, all items are flagged for inclusion in the import but if you have a requirement to omit certain items (say all Gridlines), then simply untick the item option.

The Section and Material Mapping dialog indicates the different section families detected in the importing file. If there are any numerical entries in the 'Not Recognized' column then there is some mapping discrepancies and these should be investigated before continuing further. (See separate section on mapping objects).

Even if the mapping is correct and no problems exist (as per the example shown), the actual mapping can be checked by clicking to select the Review Mapping option for all Columns, Framing, Materials and Steel Decks.

Click Finish to exit from the integrator dialog and start the processing of the file.



Once the processing of the CXL file has been completed, a log file will be shown. The log file is simple a text file and a record of the objects imported, deleted or altered along with any warnings.


Moves With Grid

When performing an update to an existing Revit Model please ensure that the Moves with Grid option is disabled for all columns.

Having the option enabled can result in column items being moved during the integration process due to existing Revit limitations.

An alternative to the above is to exclude grids during the update process.


4A : Synchronizing Models from Orion into RevitAPI ‐ Application Program Interface

Appendix A API ‐ Application Program Interface

A.1 API ‐ Application Program InterfaceThe transfer between Orion and Revit Structure is controlled by an API (Application Program Interface). The API is a separate program which sits inside the Orion‐Revit application and is provided by Autodesk for CSC's programmers to use.

The API is the governing factor between the two items of software and controls which object can be passed to and from the software packages. As a "Premier Structural Partner", CSC continues to work closely with Autodesk to grow the functionality of the API and to increase the integration functionality.


4B : Synchronizing Models from Orion into RevitInformation Transferred

Appendix B Information Transferred

B.1 From Revit Structure to Orion

B.1.1 Information Transferred

The following information is transferred from Revit Structure to Orion Building Design System:‐

• All grid lines in Revit Structure are imported

• A level in Revit Structure where data exists, is imported as a storey

• There is no suitable mapping between Boundary Conditions in Revit Structure and Supports in Orion, so by default supports are created at the bottom of every column.

• All selected Revit Structure beams, columns and walls are imported provided they are within the scope of geometric limitations that apply within Orion (i.e. only vertical columns and walls, only horizontal beams). Their orientation, section size and member releases will be maintained.

Please note that members flagged as "not for analysis" are not considered in the Export from Revit Structure.

Please also note that due to the current limitations of Revit Structure certain items, including curved beams and non‐vertical columns, may have to be modelled as "In‐place families". Unfortunately, these items may be flagged as non‐structural in which case the export process will not consider them, or some required data will be missing in which case they will be exported but with a warning.

B.1.2 Limitations

The following limitations exist in the current release:‐

• No loads

• No Slabs

• No Foundation objects

• No Rebar objects

• No openings in walls ‐ these must be manually modelled in Orion

• Only rectangular walls are handled ‐ bounding rectangles will be applied where necessary.

• No curved members or walls

• No pre‐cast concrete beams or columns

• If Revit Material is set to "By Category" there is a Revit API limitation meaning that we cannot determine the material. To avoid this issue, please ensure materials are set for Structural Column, Structural Framing, Wall and Floor categories (Object Styles dialog).


4B : Synchronizing Models from Orion into RevitInformation Transferred

B.2 From Orion to Revit Structure

B.2.1 Information Transferred

The following information is transferred from Orion to Revit Structure:‐

• All grid lines in Orion are exported ‐ Exported grids all appear in Revit with the default style (i.e. the settings for bubbles are ignored)

• All storeys are exported including a level for the Base and Foundations.

• All Columns are exported; all rotations are exported.

• All Beams are exported; all rotations and end releases are exported.

• All Slabs are exported

• All Shear Walls are exported

B.2.2 Limitations

The following limitations exist in the current release:‐

• Loads are not exported

• Due to current limitations in the Revit API, it is not possible to create the correct profile for some polyline columns or columns with skewed outlines. In such cases a rectangular section with the same bounding rectangle size is created. Revit model lines showing the profile are added to the base of the column for illustration purposes only.


4C : Synchronizing Models from Orion into RevitShowing The Integration Status With A Filter

Appendix C Showing The Integration Status With A Filter

This section will describe how to create a filter which can be applied onto a 3D Isometric view (but potentially onto any Revit view) to set color coding onto the structural items. The color coding applied should then match the same capabilities of the Fastrak Building Designer command Show/Alter State ‐‐> Integration Status.

The filter works on the settings applied onto members, panels and walls with the 'Orion_Integration_Status' parameter. Using the various settings of this parameter, we can set up the filter accordingly.

Firstly, create a new 3D view for the integration status settings by clicking on the View tab and using the command 3D View ‐‐> Default 3D View. This should create a new view titled '{3D}'. Please note that if this view name already exists within your project, please rename the existing view (see below) in order to be able to create a new 3D Isometric view.

Rename the view by right clicking over the name held in the project browser and choosing the option 'Rename'. Rename the view to be 'Fastrak Integration Status'.

Once the view has been created and renamed, access the Visibility/Graphics Overrides dialog by either clicking on the relevant Edit button within the view properties dialog or



by using the 'VG' or 'VV' shortcuts.

Within the Visibility/Graphics Overrides dialog, click on the Filter tab and then on the Add button to create a new filter.



When accessing the Add Filters dialog, click on Edit/New to create a new filter.

You should now be accessing the Filters dialog, click on New to create a new filter and enter the name as being 'Unchanged' with the filter option as being 'Define Criteria'. Click OK when this information has been entered.

Once the filter has been created, the categories and filter rules fields should have become active allowing certain objects and parameters to be filtered.



Within the categories window, tick the following entries:‐

• Floors

• Structural Columns

• Structural Framing

• Walls.

After the 'Unchanged' filter has been correctly created, highlight the filter name and then use the Duplicate option to create two copies. Please note that sometimes Revit does not initially duplicate the category and Filter Rules settings for duplicated filters. If you find this is the case, click to select the 'Unchanged' filter after creating one duplicate (this re‐selects the correct category and filter rules options) and use the same duplicate command again.

This time the data should be copied correctly and the first incorrect duplicate filter can be deleted.



After creating the two duplicates, you should have 3x filters. Rename one of the filter duplicates to be 'Updated' (use the relevant icon below the filter list) and change the data entry for the 'Filter Rules' from 'Unchanged' to be 'Updated'. Rename the second duplicated filter to be 'New'. Similarly alter the data entry for the 'Filter Rules' from 'Unchanged' to be 'New'.

Once the data for all three filters has been correctly created, click on the OK button to return to the Add Filters dialog. Within here, you can choose this filter to apply directly onto the drawing view. Select all three filter names to include them and click OK.



You should now have been returned to the main Visibility/Graphics Overrides dialog and should be able to see the three filters which have been created. Click to highlight the entry for 'Unchanged' and then choose to override the Patterns applied on the surface of an object.

When editing the pattern overrides, set the color to be RGB 176‐000‐000 and the pattern to be 'Solid Fill'. Click OK when done.



Perform the same override task on the 'Updated' and 'New' filters although please note that the colors used will alter. 'Updated' should use a color of RGB 000‐000‐255 whilst 'New' should use 000‐160‐000. When overrides for all three filters have been set, click OK to leave the dialog.

The color coding overrides should now be applied onto the model and will allow you as the user to easily tell which members are new, updated or unchanged in a similar fashion to the Show/Alter State command within Fastrak Building Designer.




Documents

Revit - Orion Integration