Architecture Best Practices?

Hi all,

Looking for opinions on this more than anything else…
I have several BTS solutions in place that are starting to cross over into other solutions, in cases of one solution referencing another to use message schemas and other helper classes.  I'm wondering if there's an efficient way of managing this so I don't need to begin down more than one process if I have to make a change to the solution that is referenced by others?

So, is it better do say…create a dedicated BTS solution that houses all of my schemas in case more than one solution needs to access the same schema.  Also, if I have helper classes that may need to be shared among multiple solutions, should I combine them into another single class to avoid maintenance nightmares in the future?

Just wanting to get ideas from other developers on how to manage a potential mess.

Thanks!
-Rich