Just commenting that this has come up on AYON Community Discord here and here (this is you).
However, this issue has come up before on the Alliance of USD forums:
Which I feel is a very good place to ask about these kind of things - and the topics show that it’s very much a case where no real solution seems to exist?
Anyway, definitely bump those posts there if it’s important to you - because it’d reach a much wider USD audience.
In that second topic link there is mention however of a new feature in Maya USD:
For the record we did update Maya to support units and axis in Maya USD 0.31.
For Blender the import has e.g. “Apply Unit Scale Conversion” checkbox which I suppose would apply the scaling towards the Blender units. Funnily enough export doesn’t seem to have something equivalent (although it does have “Units” section which may indicate that it’d also recale to the chosen units?)
For Houdini - not sure how it comes into play, but with it’s procedural nature I’ve commonly seen just a transform or whatever in there just for the sake of taking it into houdini sims, etc.
Tagging @robert, @ralphymeijer and @jm22dogs since in the past they’ve all shown interest in this topic (e.g. in discord)
And to close off with a bit of Aaron Luk’s point:
As much as possible for now, I’d recommend that animation and game studios that have full control over their content and pipelines to use consistent stage metrics and export them explicitly, e.g., always write USD in meters with Y-up (or pick the metrics that work best for you). I see OV Metrics Assembler more as a necessity for industrial digital twins where content is coming in from many different sources and no one stakeholder has control over the stage metrics as a whole.
At least, if we do that and apply export/import conversion into the format and back at least for that unit then at least you’re doing something consistent - even if it still means the conversion is happening somewhere?