I am very reluctant to put an interim solution into place.
If we're going to keep this sort of information in the database, I think it makes much more sense to have a NOC object, and then pointers to it from other objects.
We don't gain much from an interim solution, other than the work involved in converting from the interim to the final situation. The effort involved in this would be better spent in doing it the right way from the start ... (IMHO, of course :)) We gain some time with the interim solution. I set up mailing lists out of the RIPE database for distributing trouble tickets, for example. Some people already start to complain, why they get the tickets two or threetimes, others don't understand why they don't get the tickets, even if they are the administrator of a network. People who understand starts to register mailing lists like ip-oper@<customer-site> for exactly the reason the *om: is supposed to stand for.
We have to judge a loss of meaning in the RIPE database pn records against introducing interim solutions. Needless to say that I support invention of a NOC object, but I don't see migration to a NOC object too complicated.
Dunc Andreas