When fetching either historical data or streaming real-time events, for each CCON a sensor is within range of, an individual 'networkStatus' event is generated and available through the API. The event JSON contains, among other things, the CCON name, signal strength, and timestamp information. Using this, by implementing a simple buffering scheme, the related networkStatus events for all the CCONs communicating with the sensor can be grouped. Then, if one or several CCONs are mapped to a given location, it can be assumed that the sensor, and therefore asset, is also at that location. Figure 4 shows the signal strength matrix of a single sensor in time, where each row represents the signal strength of one CCON. It can clearly be seen that CCON 1, 2, and 3 are all in the same location due to their overlapping signals.