A building is an enormous source of data and the built environment encloses a lot of integrations and programming interfaces, APIs. Those little digitized sockets provide data delivery for a complex process and service environment but can also enable emergence of new innovations. API is a gatekeeper to the source of information where besides the API, data can also be a product.
A good API is tested properly, documented and productized. However, even being an extraordinary API is not enough. Because API is a product transmitting other products, it should have an owner, a budget and a product strategy as well as a documented service and process environment. So, when tendering systems and solutions for any but in this case built environment, one must make sure that at least the following questions are answered. The answers may be anything, but the point is to take a stand on the matter and identify risks.
As a buyer, beware of the pitfall, because even if the API is for sale, it may not exist yet. This can especially come across in the construction and real estate industry that is digitizing quickly based on demand. On the other hand, as a seller beware of situations where your customer acquires a system whose API has not yet been properly tested. This creates extra work for your organization. The existence of the API, the possibilities and features it offers should be understood at the latest in the contract phase of the procurement, so as not to be surprised - whether you are in the role of a seller or a buyer.
Discover our latest news & best practises.
We won't spam you - we'll send you relevant content maximum 1-2 times a month.