If you view a lot of IFC files in Tekla BIMsight, you may find that the cache or storage folder fills up quite quickly. If this is in its default location of \%localappdata%\Tekla\Tekla BIMsight\ then you could use up valuable space on your SSD.

We can easily move this folder using symbolic links. In the script below, we:

  • check the default directory exists, and if so rename it
  • make a symbolic link to a new target directory, in this case I have used E:\TeklaBimSight
  • make the new directory if necessary
  • copy existing contents to the new directory

To use the script:

  1. Close Tekla BIMsight
  2. Copy text from the script into Notepad and save as CMD. Modify the target directory to your preference
  3. Save the script with CMD extension
  4. Right click and Run As Administrator
  5. Open BIMsight and confirm all is working ok
  6. Optional: delete the bimsight.old directory to cleanup
if exist "%localappdata%\Tekla\Tekla BIMsight" rename "%localappdata%\Tekla\Tekla BIMsight" bimsight.old
mklink /d "%localappdata%\Tekla\Tekla BIMsight" E:\TeklaBimSight
if not exist E:\TeklaBimSight MD E:\TeklaBimSight
robocopy /mir %localappdata%\Teklabimsight.old E:\TeklaBimSight\

BIMSIGHT.png

Tekla has issued an XML file containing preset IFC settings for export to Revit, specifically for Coordination. In some cases, this may already be available on your system, but in other regions you may have to install it manually.

Here’s how:

  1. Download the zipped XML at this link.
  2. Unzip the XML into this folder on all PC’s running Tekla Structures:
    C:\TeklaStructures\*version*\Environments\australasia\system
    Note: you may need to adjust the above path to suit your Region
  3. Once this file is included in the folder mentioned above it will be available in all projects. When the user goes to File – ExportIFC they will have a pre-saved setting named “RevitCoordination”. The user simply Loads that setting and exports the parts needed.

  4. This “RevitCoordination” setting also is setup to export additional property sets for Design Workflow data that is entered into the member properties (ie. Beam, Column etc.) in Tekla Structures.


More information at:
CUSTOMER QUESTIONS: What’s the best settings to use when sending Structural BIM to Revit Architecture?
and
Tekla Revit BIM workflow example | Tekla User Assistance

A document was recently released that essentially describes differences in the way that Tekla and RST respond to changes in a linked architectural model. This document doesn’t really take into account the other benefits of working in a completely Revit environment – not having to convert to and from IFC, tagging through links, scheduling, bidirectionality, and so on (I don’t feel a need to keep listing reasons 🙂

Download the comparison PDF (keep in mind this was prepared by/for Tekla)

via
LinkedIn

Tekla have released a viewer app for iOS that can read IFC files. You will probably use Dropbox to get any large IFC files onto your phone or tablet, but you can also open from email or web.

Download at:
https://itunes.apple.com/gb/app/tekla-field3d/id868034113?mt=8

Free version features
• View 3D models in multiple formats: .ifc, .3ds, .obj
• Very large models load in mere seconds, tested to more than 2 GB
• Zoom, pan and rotate 3D models
• Object Outlines and dynamic Shadows to better visualize model geometry and depth
• Open files from email, file-share or web
• Sample files included and more can be downloaded
• Orthogonal view of 3D models – as an alternative to Perspective view
• Imperial units display option for Property values (feet &inches)

Of course, you could also append the IFC to Navisworks, then Glue it, and use the BIM 360 Glue app to do something very similar 🙂

I was approached by Reza Hosseini, who is currently completing his Phd, to have an interview about virtual construction. 

It is embedded here:

Some of the topics covered:

  • virtual teams
  • technological challenges of trying to work ‘live’ on a cloud model
  • effects of virtuality in teams
  • cultural background and project experience and the effect on teams
  • the size of teams (number of disciplines / stakeholders)
  • accountability for action items (for example, clashes)
  • Revit interoperability (including with Tekla), and using IFC
  • new roles for contractors to do model conversions (as Virtual Built is doing)
  • change management, and the instigators of change
  • is the Client or Head Contractor requesting BIM?
  • using Aconex
  • conflict creation
  • IP issues and contract rights for BIM team members
  • team identity and affiliation
  • level of importance of social interaction
  • skills shortage of BIM users
  • researching BIM, determining unique topics of discussion
  • building trust relationships
  • level of importance of face-to-face contact
  • frequency of communication
  • scaleability of BIM to small projects

I hope the background noise and sounds of cutlery aren’t too distracting 🙂

Ryan Schultz is working on Revit–>IFC–>Revit translations, and he has created a open source page as a focus for test and sample files.  Here is the link:
https://github.com/theoryshaw/IFC_Roundtrip

Interestingly, Ryan is looking into IFC translations with ArchiCAD, Vectorworks, Microstation, Tekla and others.  The mixed environment of BIM software on collaborative projects is proving a challenge to many teams.  Ok, we can’t all work with Revit (maybe one day), but for now we have to find a way to share our models with high geometry fidelity and without losing the actual intelligence of BIM data.

I’m sure Ryan would be keen to hear from you, perhaps via Twitter or the github page.

Let’s work together to learn how to work together…

via
https://twitter.com/theoryshaw/status/450604566132686848