Deprecated: Assigning the return value of new by reference is deprecated in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-settings.php on line 472

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-settings.php on line 487

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-settings.php on line 494

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-settings.php on line 530

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/classes.php on line 611

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/classes.php on line 728

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/cache.php on line 425

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/theme.php on line 623

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/class.wp-dependencies.php on line 15

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method Add_to_Any_Subscribe_Widget::init() should not be called statically in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/plugin.php on line 311

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/plugin.php on line 311
BIM | CAD VS. BIM

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/functions.php on line 55

Top 5 Things You Should Know Before Going BIM


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/plugin.php on line 163

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 498

This is a list of items that you should know before making the switch:

  1. Whoa! That file is large: The typical project file size can be 35+ MB, which can cause issues when emailing and sharing documents with others.
  2. Where’s my training?: BIM software is unlike traditional CAD programs and will require additional training for your entire CAD staff to be proficient with the software.
  3. Mutiny in the ranks: Your current employees that have been using 2D CAD software for years will most likely not be very receptive to changing the way they are designing and delivering projects.
  4. Upgrade?: There might be a need to increase your hardware setup and design processes.
  5. Test it out first: Before making the switch, you should explore the software with a test project and determine the pro’s and con’s.

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::spool_analytics() should not be called statically in /homepages/15/d261584954/htdocs/rdcadd/blog/wp-includes/plugin.php on line 311