top of page

Everything any user needs to manage their assets

It all starts with the user.

He/she is the one who makes sure that all this is useful, meaningful, and that there are budgets to make the use case last. And there are so many direct and indirect users of this IoT data; the employee, the employer, the manager, the visitor, .. and tons of other systems that would also like to work with the conclusions generated from it.

application01.png

The WMW library approach

Ontwerp zonder titel-224.png

We believe this end user has the right to post requests. They will face a situation, a challenge in this business they've been in for a long time. Their problem has grown organically and they needs to see certain things to solve it, optimise it, better it.

​

At WMW we have a very strong user centric philosophy. It is at the heart of our technological and business model. Where modularity is great for scaling purposes, it is a killer for adaptability. So, we handle a library approach, a mother-set of micromodules, snippets if you like.

​

This library is smart and intersects with many other library items, on a semi automated way. It allows us to build fast, but also build custom made. You may call it productisation of customisation. As we already have + 150 products constructed with it.

Consume and adapt

Whereas the data layer is accepting and preparing all data, the application layer is allowing for the consumption of the data.

Our library is packed with features that are often used in interfaces but also allow us to draw new ones, just like we would on a blank canvas.

​

Some standard features are mapping systems, list views, filter mechanisms, navigation items and a lot of analytics tools. But that would make us the same as any other platform. The secret sauce is in how we can create new items, based on experience briefings.

​

As an example, we created a full access control system in 3 weeks, a social distancing tool in 4,5 days, a traffic monitoring setup in 2,5 weeks. None of these were standard and briefed by experts in their market. Each of their customers needed the results of the data presented in different ways with many different stakeholders all with their own agenda.

3apps.png
application02.png

Existing catalogue

This all does not mean you can not start your IoT journey easily. We have +150 applications ready, off the shelf, and hundreds of devices that are already supported. They range from street lighting applications, to parking management, to tracking apps for various purposes. In agriculture we have apps for crop growth, field management and cattle tracking. In logistics we develop warehouse management apps, area conditions and geofence automation.
There are apps dedicated for the mining industry, oil & gas, smart City, ... and the list continues.

​

And the great thing about it is that you can start combining them and make dedicated suites. Water management for example, lets you bring together metering, valve position, pipe pressure, calorie measurement, leak detection, tank filling, water quality, manhole monitoring, ...

Asset management

A core part of every application is the ability to create, view and manage the asset. As an important note, we are not just device management showing you readings of the device. It's not about the tracker, it's about the animal wearing it. It's also not about the smoke detector, it's about the room housing this detector.

​

Asset management will go a few extra miles, like we do when creating apps for it. You'll have detailed views, list views, filter systems, alarm overviews and profile setups. Data flows in both directions and as an example, you'll be able to set a dimming profile on 1 lamppost or a group of streetlights in a part of a city.

Downlink-profile.png

Analytics

ROI comes from optimising things. You'll have to know what

is going on before you can optimise it. There are a few

stages to it:

  • You will want to know what's happening on single assets

  • You will want to see the results on groups of assets

  • You will want to set KPI's to them on overview dashboards

  • You need to have configuration systems to set thresholds

  • You need a flexible ruling system to set the outliers for generating alarms

  • and there is much more that you need ...

​

All of these need to be presented graphically. The platform is packed with powerful graphing engines and alert overview sections.

​

Additionally, automation mechanisms are in place to act upon all of these results. Create a task for someone to perform something, send a downlink to another device to do something, send out notifications and reports to the right stakeholders.

 

Dashboard02c.png
analytics.png
parking12-dashboard_v3.png
bottom of page