A module is used to transfer schema and code to other stores. It bundles some topic types and services, its parts. The store where a module is defined is called its origin. When a module is released, the version increases by 1 and a library, a zip file, is created and archived at the orgin. After downloading the library, it can be uploaded in another store, the target, and then imported. Topic types and services will function just like having been created manually.

The primary motivation for modules is the reduction of repetetive modelling and programming. A module can range from a single topic type, over a set of related topic types and services, to a complete store. It is possible to include instances of topic types in a module (master data).

It is recommended that a module works out of the box without any further ado. Nevertheless a module might contain mapping errors, which should be corrected after import. A mapping error is any topic mention in a source code file that does not map (refer) to a topic since it was not a piece in the module. It is easy to find these by accessing the content tab of the module in the target store.