Translator and Conversion options for HLM instances of PLNs

[Josh Verran]

I'm familiar with the process of working with IFC files, by where you place as a hotlink.

You then have options for the translators to map things like layers, properties, classifications etc.

I've just placed a HLM of a PLN, however realizing that there's no option to pick a translator (which makes sense - it's not an IFC). But surely there's a way to map (and save preferences) for when you're working with PLNs (or PLAs for that matter).

Any suggestions?

One idea I had which I haven't tried is to export as IFC from the original file, however, I suspect I will lose the native AC elements (eg Walls become whatever geometry is set in the translator).

[Lingwisyer]

As in you are wanting to place someone elses model into your template, and are wanting to "translate" their template into yours? If you are collaborating with someone else using AC, would it not be better to all be using the same template?

[Josh Verran]

Yeah, there's a couple of scenarios.
One where we need to utilize a model that someone else has created in their system/template.
Unfortunately, it's not always reasonable to expect another company to use our template.
Also, our template is reasonably evolved, we would benefit from utilizing our pre-set views, layouts, schedules, properties (expressions) etc.

There's also the issue of IP.

Another scenario is within our office, we have instances where a model was created in our own system, but years have passed, and templates etc have evolved.

If we can convert/translate the previously mentioned parameters, we can utilize old models, in new templates.

This can all be done manually, but being able to automate has it's benefits.