Revit Family Based Section Mapping

Use the mechanism that involves 1 to 1 section mapping between the Revit family and the Advance Steel table and between Revit profile type and Advance Steel section name for more accurate and consistent results.

Advance Steel 2016 Revit Extension uses a new mapping system. This new mechanism uses a 1 to 1 mapping between the Revit family and the Advance Steel table, as well as between the Revit profile Type and the Advance Steel SectionName.

Revit 2016 contains newly created families, according to the latest standards, for the following countries:

US Imperial (AISC 14.1)
US Metric (AISC 14.1)
Canada (CISC Shapes)
UK (British Standard)

The name inside the brackets represents the name of the folder where the new families are stored in each country folder. The families can be found in the Structural Framing and Structural Columns folders from each of the mentioned countries.

These families contain 2 newly created parameters:

Family Name Key
Section Name Key

The Family Name key parameter is mapped 1 to 1 to the Table Name from Advance Steel. This parameter is stored in the family.

There is also a new table inside AstorProfiles2016.mdb , called RevitASProfileConversion . This table stores the mapping between the Revit Family Name Key and Advance Steel Profile Table.

The Section Name key parameter is mapped 1 to 1 to the SectionName value of a profile in Advance Steel. This parameter is stored in the family.

The extension extracts (FamilyNameKey, RFAFilePath, RFAFileDate) from all Revit families from a given path and then builds a .xml file, which is used later at import.

The index file is created first time you start the extension.
When you add a new path, all families from the path are indexed. A progress bar appears to notify you.
When you remove a path, the index is updated.

Note: The new mapping mechanism imports profiles without using the Profile_Rotation table from the GTCMapping.mdb database.

The old mechanism that uses the 3 tables (GTC_Profile_Conversion, Profile_Exports_Conversion, Profile_Rotation) from GTCMapping2016.mdb is still present and is used as a secondary option, when the new mechanism is not able to map a profile.