Comentario
05-18-2018
06:12 AM
05-18-2018
06:12 AM
Martin
It leaves Six things undesirable:
-Past job we uploaded our Revit model to the General Contractor for clash detection. Forcing us to use "flex duct" as an electrical device sometimes plays havoc on the coordinators clash files because they will inadvertently use system filters to separate and export Trade designated coordination models into Navis for clash detection. Since Flex duct is not an electrical system, it ended up in the Mechanical contractors NAVIS clash file. This was a Lesson learned. The solution was to use a "work around".
-Primary and secondary panels with a transformer in-between them we have to use a conduit elbow for GTP then filter out off for coordination upload, we use the flex duct as the flex connection because in actually can fit more like the field install. If this was an electrical system GTP would probably update their program to "connect" these on the autonomous one-line.
-Creating a BOM for Flex/Liquid Tight we have to add an extra step to the schedule so its description is correct.
-Have to customize fittings with conduit and flex duct connectors on each end.
-For BOM reasons-cannot get an accurate Run length to calculate wire lengths. The flex or liquid tight does not get captured in the total length of the run. We have to manually add length, (this is AKA a "workaround").
-GTP does not automatically recognize Flex Duct at final equipment connection, have to use a manual "work around" (use conduit that will be filtered off on Coordination model export) as opposed to the program autonomously adding the P.O.C. intelligence.
The electrical "Flex" family needs all the descriptions from the NEC (National Electrical Code-North American).
Here are a few examples:
-Flexible metallic Conduit (MC) i.e. aluminum or steel
-Liquid tight Flexible Metallic Conduit (LFMC) i.e. Steel, Aluminum
-Liquid tight Flexible Nonmetallic Conduit (LNFC) i.e. PVC
The Cable and Wire Family needs all the descriptions from the NEC (National Electrical Code-North American).
Cable and wire would have absolutely created value for my department on our last job for BOM purposes. Using conduit as cables in tray was very cumbersome, modifying conduit would inadvertently delete or move sections of tray furthermore the bending radius of wire is smaller than what Revit would allow for the conduit.
-Cable i.e. Triplex, TC or other types, Sometimes cabling can have a 3.5" O.D on these.
-Wire i.e. THHN 500 mcm Cu.
Please try to push this product improvement especially when this has been posted for over 3 years.
It leaves Six things undesirable:
-Past job we uploaded our Revit model to the General Contractor for clash detection. Forcing us to use "flex duct" as an electrical device sometimes plays havoc on the coordinators clash files because they will inadvertently use system filters to separate and export Trade designated coordination models into Navis for clash detection. Since Flex duct is not an electrical system, it ended up in the Mechanical contractors NAVIS clash file. This was a Lesson learned. The solution was to use a "work around".
-Primary and secondary panels with a transformer in-between them we have to use a conduit elbow for GTP then filter out off for coordination upload, we use the flex duct as the flex connection because in actually can fit more like the field install. If this was an electrical system GTP would probably update their program to "connect" these on the autonomous one-line.
-Creating a BOM for Flex/Liquid Tight we have to add an extra step to the schedule so its description is correct.
-Have to customize fittings with conduit and flex duct connectors on each end.
-For BOM reasons-cannot get an accurate Run length to calculate wire lengths. The flex or liquid tight does not get captured in the total length of the run. We have to manually add length, (this is AKA a "workaround").
-GTP does not automatically recognize Flex Duct at final equipment connection, have to use a manual "work around" (use conduit that will be filtered off on Coordination model export) as opposed to the program autonomously adding the P.O.C. intelligence.
The electrical "Flex" family needs all the descriptions from the NEC (National Electrical Code-North American).
Here are a few examples:
-Flexible metallic Conduit (MC) i.e. aluminum or steel
-Liquid tight Flexible Metallic Conduit (LFMC) i.e. Steel, Aluminum
-Liquid tight Flexible Nonmetallic Conduit (LNFC) i.e. PVC
The Cable and Wire Family needs all the descriptions from the NEC (National Electrical Code-North American).
Cable and wire would have absolutely created value for my department on our last job for BOM purposes. Using conduit as cables in tray was very cumbersome, modifying conduit would inadvertently delete or move sections of tray furthermore the bending radius of wire is smaller than what Revit would allow for the conduit.
-Cable i.e. Triplex, TC or other types, Sometimes cabling can have a 3.5" O.D on these.
-Wire i.e. THHN 500 mcm Cu.
Please try to push this product improvement especially when this has been posted for over 3 years.