This is just a suggestion. In the SIMM valuation demo we send the entire jar file (18 MB) of the demo itself to the notary in order to enable contracts validation. Currently, we use 10 MB as a default maximum transaction size in network parameters. In fact, that 18 MB doesn't need to be sent as the only thing that the notary needs to validate the transaction is few contracts and possibly other classes.
This demo works in local deployment if we increase that 10 MB default maximum transaction value to 20 MB.
It would be good (and neat) though, if we could use i(n that example) an attachment that consists only necessary classes.