Modular Architecture
[SOURCE: Frode Hegland]


Features can be added as small additional plug in projects rather than having to be built from scratch, allowing organizations and even individuals to power to shape their information environment.

This is due to the explicit segmentation of the environment and open APIs. Features can be slotted in along the input path, view generation, manipulation, background timed processes, output path or in any combination.

Depending on the magnitude of the feature and its impact on other parts of the environment, it will be seamlessly slotted in to the major free versions or it will have to be added to the customers own server, where the feature only becomes a part of a catalog of optional installations for others in the future.

Anybody can now add features. With traditional OpenSource projects only by being a programmer or by having the budget and technical know-how could you add to the OpenSource project. With the OHS project however, there is an independent, non-exclusive option of using a centrally coordinated programing mediator, at very low cost.
           EXAMPLE: This means that making a simple but specialist addition of something like a custom calendar with special features trivial. Even a non-technical individual can have it done at low cost, provided he or she can communicate clearly how the feature is to behave and it doesn't interfere with other basic features of the system.