As explained in the previous sections, because SNOMAN applications use SU Control, assembling SUs is much easier, but at the cost of having them all in the executable program ( SU control does not know, until execution time, which SUs will be called so it has to link to them all). This may well seem like taking a sledge hammer to crack a nut if all you want to do is perform some simple analysis on a data file! However it is clearly important that elements can be taken from SNOlib in any sensible combination without conflict and SNOMAN, as it uses them all, is an existence proof of this. So anything built that uses all the code should also be free of conflicts as well as being able to take advantage of support systems such as the interface to the database.