As mentioned elsewhere, BIM is heavily dependent on using components provided primarily by manufacturers. This means being able to convert RFA content into Mstn equivalents with as much fidelity and retained functionality as possible. Mstn's RFA Interpreter is a pioneering tool... but I think the results have been more 'zombie' than production-ready, lately. Overdue for an overhaul... using ODA BIMrv libraries?
Some of the problems:
No one is really going to want to use Mstn if every component has be to remade from scratch. OBD is infamous for having very bad OOTB datasets, based on decades old content, often US origin that has been 'metrified', based on old and multiple tools accumulated over the years. This has been overlooked for a long time as a lot of the corresponding functionality like Placement Points, Perforators, Named Presentations etc in Mstn just wasn't available. There is a huge pent up demand for updating all that old content to leverage the new MSCE Update16.1,2,3 etc functionality. OBD for example desparately needs to be able to include modern content in its OOTB datasets to be competitive. The converted BIMstore RFA content on ComponentCenter is no better. Hopefully, the localisation teams have been consulted by platform and the relevant conversion tools are being written.
The RFA Importer has been taken over by the platforms team. So are a lot of the key modeling tools iincluding Named Presentations (which is a reboot of OBD's old Compound Cells functionality), Perforators, Placement Points etc. Parametric Content Modeler was intended to replace OBD's Parametric Cell Studio. Most of the fundamental OBD tools now seem to be developed at platform level, which makes sense as most of the BIM functionality that is needed by OBD are equally applicable for other verticals.
This is the reason this thread was posted here and not in the OBD forum.