Given that the software-as-a-service model relies largely on subscriptions and that most construction projects often have a longer expected life than projects in many other industries, what is it in SaaS that construction majors feel is not available in perpetual licensing?
SaaS collaboration software for project delivery has proved attractive to many construction businesses for its rapid mobilisation and "Pay As You Go" approach. Project teams could quickly get a system in place (no hardware to acquire, configure, etc) and pay for it as long as they needed it, then switch it off (ideally having created archives, etc) once the project was commissioned and handed over to the client.
As we begin to adopt more whole-life approaches, the need for data management shifts from a sole focus on delivery to maintaining data from delivery right through to demolition. Clearly, this will be an issue for the asset owner/operator, and much will depend on their ability and willingness to manage a growing amount of data throughout the asset's operational life (no longer just data collated during delivery, but also data accumulated from operations - energy use, repair, maintenance, in-use performance, etc). If they sell the asset, then this "owner manual" could also be a key part of the transaction.
Will they want to store, manage and maintain this data, or will they prefer to outsource this responsibility to an external "data-as-a-service" provider? Such a provider might also be subject to a service level agreement to ensure security, backup, uptime, speed of access, continued future access to its data (ie: ensuring its formats remain compatible with current software tools), etc.