This is happening: https://www.linkedin.com/feed/update/urn:li:activity:6909623002003365888/

It continues a trend started in 2012. Automated fusion of technical drawings presented at their true orientation inside digital models has been developed in some apps and platforms over the last 10 years. But those solutions remain mostly siloed in those apps, gaps remain, and important improvements are yet to come.

Here’s an idea to make it easier to fill those gaps, break silos, and improve the effect and usability of the fusion of technical drawing and modeling.

A very simple CAD/IO workflow if TGN is used earlier in the workflow. What I mean is, where TGN features are implemented in modeling platforms, then workflow for the user is like this:

Put a TGN rig into your model like this:

1. use the CAD I/O function of the TGN rig. This function is a simple script that creates a new DWG file, places a cube in the DWG that matches the TGN cube in xyz, creates and activates a UCS in the DWG that sets the drawing plane to the main plane of the TGN cube, and links/xrefs/overlays the new DWG to the model. Any CAD graphics you draw then on that DWG plane will show up at the right place in the model without having to do any manual positioning. Of course apps that implement these functions would be best if they include code to add at least some model-derived graphics into the DWG at and around the drawing plane https://www.opendesign.com/blog/2019/august/part-1-2-generating-cut-geometry-planar-clipping-boundaries
2. This can be very flexible because these DWG files can be passed around to different users, disciplines, and editor apps and still be easily checkable against the model.
3. This could also be a nice assist for those workflows where old drawings already exist. You can use this method in a modified way to help get old DWGs ready for display in TGN rigs.
4. This also fits with the most basic “law of TGN”: TGN RIGS ARE MADE FOR SHARING ACROSS MANY MODELING APPS. Maybe you create a TGN rig in your model web viewer in your browser. Then you share the TGN rig so it is viewable (and editable) in TEKLA, and then you share it for expression and use in Revit, and again for use in 360, and so on.
5. Of course TGN rigs should be managed in a TGN communication hub, like BCF is https://catenda.com/case-study/nge-batiment-the-use-of-the-bcf-format-bim/ 

And it definitely makes sense to be thinking about the merger of BCF and TGN…

Developer specification for TGN and more videos are here https://tangerinefocus.com/