Aug 16, 2018 in Viewpoint
SaaS is the foundation of multi-tenancy buildings
In the future, we’ll see a rise in so-called “multi-tenant buildings”. Centralized and integrated office platforms are essential to structure the distribution of these buildings.
Just imagine four organizations in one building all implementing their own systems; booking a room would be a nightmare! To efficiently share resources, the systems to manage those resources need to act on the building-level, not on the level of an individual tenant. So, to make sure that the shared rooms aren’t double booked, you need a software multi-tenancy that suits the physical multi-tenancy of the building.
That’s where SaaS comes into play. In software terms, multi-tenancy is an architecture in which a single instance of a software application serves multiple customers. This architecture is quite common in SaaS services. For example, organizations that use a cloud solution for their email services (such as Office 365 or Gmail) do not have their “own” dedicated server farm running at the SaaS vendor. Instead, server resources are shared amongst tenants whilst a strict separation between the tenants is maintained on the functional and data level.
To make sure that the shared rooms aren’t double booked, you need a software multi-tenancy that suits the physical multi-tenancy of the building
A SaaS platform to support multi-tenancy
Although multitenancy in SaaS is an existing and common phenomenon, the rationale for choosing SaaS in multi-tenancy buildings is different. It’s not about increasing the efficiency of server resources, adding redundancy, or reducing operational costs of ICT administration. It’s all about manageability and sharing. Imagine four tenants in a building, all with their own ICT systems and facility management software. To allow for (for instance) room sharing, these four tenants would need to somehow interconnect their individual room booking systems. That’s six connections in total, maintained by four different ICT departments. In other words: a nightmare.
When instead a dedicated third-party platform for resource sharing is used, each of the tenants has their own integration with that platform, that they control and maintain. Adding and removing a tenant does not involve actions from the other tenants, as long as there is a clear set of common rules and standards that a tenant must adhere to in order to join the resource sharing community.
To summarize: when you want to provide services like room sharing at the building level, you will need your software solutions to act at the building level. Further, a clear set of standards is needed for the way that tenants technically communicate with that solution. With Mapiq we aim to cross the boundaries between organizations by offering such a SaaS platform that inherently supports multi-tenancy.
Exploring ideas at the intersection of bricks, bytes, and behavior. Subscribe to our monthly newsletter.
Viewpoint / Jan 23, 2020 / Bouwe de Planque
The story behind our workplace sensor
At Mapiq, we strongly believe that our smart office platform is only as good as the data it’s fed with. Good working sensors are a high priority for us. But many existing sensors are slow, or not functioning the way we want them too. So, we decided to make one of our own. A few months later, Mapi...Read more
Viewpoint / Jan 21, 2020 / Bastian de Graaf
How to build the perfect team for workplace change management
The office and the way we work is changing rapidly. Activity-based working has already entered work-life years ago and is here to stay. As a smart office platform, our focus lies on the employees in these modern offices. And as a member of the Customer Success team, I’m passionate about supportin...Read more