The process is leading

Roof inspection

“As easy as pie. If not, we haven't done our job properly.”


Decisions about maintenance activities that are to be planned are often based on priorities. Problems with roof inspections often relate to the variation in the results. The causes include the fact that different inspectors make different assessments of defects and their consequences. For example, how is your own roof inspected and that of someone else? Moreover, the instructions are not always clear or the knowledge and skills of the inspector are insufficient. A solution is condition measurement in accordance a standard, which ensures commonality and makes it possible to visualize both the desired quality and the actual quality. The condition measurement is a uniform inspection method with predetermined maintenance levels. A Multi-Year Maintenance Plan (MYMP) can be linked to this, in which the costs of maintenance are related to return aspects.

Fits perfectly
We build your ambition.
State of the art
Incorporation of state-of-the-art technology.
Fast in operation
Basic version within a few weeks.
Grows along
Scales along with your future ambitions.
Roof-control2.png

Assumptions

Before Wikibase Solutions started developing a roof application for condition measurement, a number of assumptions were made about the roofing industry that were later not entirely correct. Eric/Jan van Kakerken:


“For example, we thought that digitalization would be high on the agenda of the average roofing company. That turned out to be a misconception. It hardly matters at a number of companies. Looking at their processes and their checklists, nothing has changed in years. Some still work as they did fifteen years ago. That is a choice that every company makes itself. There are many roofing companies that still work out everything manually. They swear by paper as an information carrier and means of communication. They have little interest in automation and digitalization. The condition measurement in accordance with a standard is still passing them by. Their customers go along with this. Fine, that's a choice. They put the client first and you can never be against that. It is a different story if the client suddenly wants inspections to take place in accordance with a standard. In order to continue to do business in a customer-oriented manner, they are more or less forced to examine their own work process and adjust them if possible. The tool we have developed for roof maintenance reports can be a useful aid. This roof application saves time, increases efficiency and ensures clear communication. The application is offered in the form of a webapp. This consists of a basic version that is the same for everyone, which can be expanded with company-specific features as desired. The latter can be used to shape the individuality of the company. This is important to us. The work flow and process are leading, or the unique inspection method that each company uses. This is how companies can distinguish themselves. The unique selling points, after all, no company works the same. There are currently eleven different versions circulating in the roofing industry and four basic versions that have not changed.”

Added value

The added value of this webapp is its speed and the fact that it ensures a uniform way of working. Van Kakerken:


“An inspector who inspects a roof uses his 'device' (hardware device on which software runs - for example a tablet or smartphone) and enters the data in accordance with the condition measurement program. Photos ('´before' and 'after') can be placed directly into the system. As soon as the inspector leaves the roof the report is complete. If forwarded immediately, the status of the roof is available on site at the same time. The report has been generated and can be sent directly to the client if necessary. Some companies provide a quote for repairs and send the report separately. Others do not do this and use the report as a starting point. Customers can access the database 24 hours a day to view the status of their roofs, provided they have been given permission to do so.”

Working with the software of the roof application does not cause any problems. Van Kakerken: “The system navigates itself. Although it is possible, we have never had to organize training for it. As easy as pie. If not, we haven't done our job properly. Data stored by another system can, to the extent that it can be exported, be imported into the new tool. No problem. This allows you to record the history of the inspections and therefore the documentation. From quick scan to complete reference work. Updates are free and download automatically. As soon as we develop something, it can be followed by the client. He can see every day what phase the development is in. If necessary, adjustments can be made in the meantime. At the end of the ride everything functions flawlessly. The roof application speeds up and simplifies the work flow. Roofing companies can serve their customers more quickly and, regardless of the inspector, are always able to comply with the condition measurement in accordance with the chosen standard.”

Wikibase stack.png

The Wikibase stack

The Wikibase stack builds on MediaWiki.

With Open CSP MediaWiki is turned into an enterprise level Content Services Platform.

Wikibase CSP is Open CSP with additional features that fit in our ecosystem.

Our current products:

The customer solution that fits like a glove.

Want to know more?

Lua error: bad argument #1 to 'mw.text.jsonDecode' (string expected, got nil).