Developers release 1.2.0 (beta release)

Today we released a beta version of 1.2.0. To get things clear right away: it has bugs. Please do not download this if you are an end-user. The main reason to release this new version is to inform developers of changes and, again, a new concept.

The new concept we would like to introduce is still a bit fuzzy. We are developing at it every day and it is changing every day. This is also the reason why we will keep updating the beta releases of 1.2.0 the coming weeks. The most important change you will notice is the ability to add ‘extended data schemas’ to projects and a new plugin type for queries (including the new BimQL plugin). More detailed info and documentation will follow soon.

When you are a developer, things will probably make sense when you dive into the code. When you are a user, a demo that we are preparing will say more than a thousand words. So please be patient for another little while.

After looking at the new release, please send your feedback through

BIMserver 1.1 beta: developers release

Today we released a beta version of 1.1. To get things clear right away: it has bugs. The main reason to release this new version is to inform developers of the changes and new concept. Since the 1.0 release not a lot of new features were added, but everything changed….  The most important, and radical, change was the introduction of the plugin-infrastructure. The previous release of BIMserver was one big chunk of code; in this new release all functional parts of the code are made modular. The whole import and export interface is put into plugins. The ignore files are now called ‘objectIDMs’ and also modular.

This release of makes it easier to integrate and communicate with BIMserver. Have a look at the communication schema and possibilities on

Some other big changes in 1.1beta are:

  • Visualisation is gone: we removed visualization from BIMserver. We think a server should be a server and not a visualization tool. We are teaming up with for visualization.
  • Slit between server and GUI: the graphical user interface of BIMserver sucks. We know… To encourage developers to create a new one, we split the JSP pages from the actual server. Therefor you can now download a server build (only the server) and a combined build (server + jsp GUI).
  • Bimserver now uses internal streaming rather than the creation of temporary files for parsing by the geometry kernel.  There is work in progress to integrate IfcOpenShell as a geometry kernel as well, but that might have to wait till 1.2.
  • Client Library:  Gives you access to plugins and the EMF core client side. As a result this developers  the same advanced possibilities on the client as they have server side.
  • New protocol buffer interface: In addition to SOAP and REST interface, we now support Protocol Buffers. This is a major step towards real-time (streaming) communication with clients.
  • Internal performance updates: we’ve improved a great deal of memory usage in this release.
  • Caching of downloads: Both revision and queries  are now cached on server after the first download. This means any additional download will have very fast retrieval . This speeds things up quite a bit in a multiuser environment where several people need to download a merged model or revision to their own machine.
  • Progress bar: lots have asked for it, now it’s there… a progress bar during upload and download.
  • Plugins: All serializers and deserializers (upload, download) are now plugins that can be activated or deactivated. This infrastructure makes it easy for developers to build on top of BIMserver. There are already several plugins being developed like a very promising COBie plugin.

You can find the release on this location: (which is our archive site). We call this a 1.1beta, but it will be placed in subfolders, ordered by date. Therefore we can update the release every couple of days, responding to your feedback.

Before (and during) your evaluation, please have a look at the know issues  and the documentation. The documentation on the wiki will grow, responding to your feedback.

Please place your feedback on