We've built Sol for collaboration and re-use.

We have created the ability to build "templates". These are a block of inputs, outputs and formula's that are given a name, and typically represent an abstraction. We call these "templates". For instance, you may have a GPS template. All GPS's essentially provide the same information, so the abstract template has the same interface for other parts of Sol to use. But each GPS has a different internal protocol to communicate with the main computer. So inside the template, you can specify that this particular GPS uses specific commands over the serial port.

Abstractions are great to write generic software, where certain components are easily replaced by others. That makes it easy to switch one hardware sensor supplier by another, yet keep the overall software the same. 

Abstractions are also great to pass on to colleagues and business partners. There is no clearer documentation that a Sol application, which provides in requirements how to communicate with the hardware device to get the aircraft coordinates out.

We also try to help collaboration by fitting into the tools people use. Sol is a plain text format with simple markup. That means it is perfect to work with any configuration control system you have. It is also easy to publish on an internal intranet. Equally important, it is easy and safe to email a Sol application, given that it is just a plain text file.