So if you were to import this into either of these packages its location would be 'correct' but the rotation would be off. Most other packages that read IFC's such as Navisworks and Solibri make use of the IFC's site coordinates and North rotation. Job done you might think, but sadly, not. If you generate the IFC at this point using this new coordinate system it will align perfectly in Revit.

Okay so what about Tekla? Well it makes finding the location of it's origin much easier - it highlights it with a nice clear origin marker In many cases, depending on what information was available when the model was set up, the location of the Revit Origin will be completely arbitrary. Typically on projects we will mark this with two grid lines labelled XX and YY for clarity. To locate the origin point, you need to turn on the Project Base Point (PBP), un-clip it, right click and select 'Move to Startup Location' - this point is the Revit Origin. Typically though the user is never really aware of it as everything is simply modeled relative to other elements which arguably makes life easy for the user. So the first thing is, what is and where is the 'Revit Origin'? This is the point the Revit uses to store all of it's geometric information, if you have used Dynamo and dealt with coordinates you will have seen the raw coordinates of this system. For IFC's however we get none of that and instead Revit defaults to using Origin to Origin. When linking an RVT or DWG file Revit provides options for the coordinate system you want to use to align the models, usually Center to Center, Origin to Origin, Shared Coordinates or Project Base Point to Project Base Point. The problem lies in how Revit links in the IFC's. On several projects recently we've encountered issues when linking IFC's generated from Tekla Structures into Revit where the two files simply do not align depsite the IFC showing the correct geographical location and linking in fine into other software such as Solibri and Navisworks.

Revit to tekla