A network asset map of every site, from the world view to the building.
When an estate spreads over dozens of sites, a list of 20 000 devices does not tell you where the trouble is. The ConnectMyAssets network asset map places every device at its site, groups them by area and colours the regions where critical vulnerabilities, devices down or open alerts pile up. It is a multi-site network monitoring map that runs entirely on your infrastructure, with no external map service.
Offline world map: no tiles, no Internet access needed
Locate a site once, every device under it follows
Heat layers for critical CVEs, devices down and alerts
Clusters adapt to the zoom level: a click shows the devices by type, criticality and group.
0external map service required
3heat layers: critical CVEs, devices down, alerts
1click from a site to its devices
USE CASES
Who uses a multi-site network monitoring map
The NOC wall
Put the map on a dashboard in TV mode and the operations room sees at a glance which regions have devices down or alerts piling up, refreshed automatically.
Regional managers
Each manager opens the map on their own perimeter: the header scope and their rights decide which sites and devices they see, nothing else is counted.
Incident triage
Ten unreachable devices in one city is a site problem, ten scattered across the country is not. The devices down layer shows the pattern before anyone opens a ticket.
Multi-site MSPs
Group customers and their sites in asset groups, locate each site once, and get a map per customer or across all of them, with each team limited to its own estate.
CAPABILITIES
Network asset map features: sites, clusters and heat layers
An operational map of your estate, not a topology diagram: where your devices are, how many, and where they need attention.
01
An offline world map
The basemap ships with ConnectMyAssets, built from public domain cartographic data: countries, regions, coasts, rivers and cities, drawn in the browser. No tile server, no Google Maps key, no request leaves your network, so the map works the same on an isolated network.
02
Locations that are inherited
Give coordinates to a country, a site, a building or a floor, and every asset group and device beneath it is placed there. A device can carry its own position, an access point on a campus for example. Each page says where a location comes from: own location, or inherited from Lyon.
03
Clusters by type and criticality
Whatever the zoom, the map shows clusters with their asset count. A click opens the breakdown by device type (switches, routers, firewalls, access points), by criticality and by group, with links to each site and device and an Open in the CMDB button on exactly that area.
04
Heat layers where it matters
Switch from clusters to a heat layer: critical vulnerabilities (vendor-excluded CVEs left out), devices down (hosts currently unreachable) or open Soron alerts. Each cell is shaded on a seven-step scale and a click zooms to the devices it marks.
05
The CMDB filters, on a map
Filter the map by vendor, model, type, status, criticality, lifecycle or firmware status, and search it like the inventory. Show only the firewalls behind on firmware, or only the critical switches: the map and the list always count the same devices.
06
Rights respected to the last device
The map follows the scope chosen in the header and the user's permissions, enforced in the database before anything is counted. A team granted one site never sees, nor counts, the devices of another. A heat layer appears only to those allowed to read vulnerabilities or alerts.
07
Locate hundreds of sites in one go
Type or paste coordinates, or click the pin on a small map. From the asset group list or the CMDB, select sites or devices and set their location in bulk. The counter of devices not located opens the list of those still to place.
08
A map in your dashboards
Add a map widget to any dashboard: the world map of a scope, or only the devices behind on firmware. Each circle opens the CMDB on the area it covers.
SEE IT IN ACTION
Critical vulnerabilities layer: where the exposed devices are.Alerts layer: the sites that need attention stand out at a glance.
HOW IT WORKS
How the network asset map works
Built for large estates: the browser never receives the full list of devices, ConnectMyAssets answers with clusters for the area on screen.
Location resolution
A device reads its own coordinates, else those of its asset group, else those of the nearest group above. A location descends, it never climbs: locating a site places its buildings and devices, never its country. The resolution is stored and kept up to date when groups move.
Server-side clustering
For the visible area and the zoom level, ConnectMyAssets cuts the world into a grid and returns one cluster per occupied cell, with its counts by type and criticality. The whole world or a single region displays quickly, however large the estate.
Same selection as the CMDB
Clusters and heat layers are computed from the same query as the inventory list: same rights, same scope, same filters. Open in the CMDB on a cluster lists exactly the devices it counts.
Audited changes
Every location set or cleared, on a group or a device, one by one or in bulk, is written to the audit trail with the value before and after.
A PRACTICAL WORKFLOW
From an inventory to a multi-site network map in four steps
01
Discover
Discovery and collection fill the CMDB with your devices, filed in asset groups by country, site or customer.
02
Locate
Give each site its coordinates, one at a time or in bulk. Buildings, floors and devices inherit them.
03
Read the map
Zoom from the world to a city, filter by type or vendor, switch on a heat layer to see where attention is needed.
04
Act
Open a cluster in the CMDB, follow the alerts or vulnerabilities behind it, and fix the right site first.
FAQ
Your questions, answered.
Prepare your project and define your scope.
Does the network map need Internet access or Google Maps?
No. The basemap is shipped with ConnectMyAssets and drawn in the browser from public domain data. No tile server, no API key, no external request: the map works the same way on an isolated network.
Is the site map the same as the network topology?
No. The topology shows how devices are connected to each other, rebuilt at every scan. The site map shows where your devices are geographically, how many there are per site and where problems concentrate. The two complement each other.
How do I place my sites on the map? Is there address geocoding?
There is no geocoding, because ConnectMyAssets may have no way out to an external service. You type or paste the coordinates of a site (for example 45.764, 4.8357) or click on a small map. Set them once on a site: every building, floor and device below inherits them. Bulk actions locate hundreds of sites at once.
What do the heat layers show?
Three indicators: devices with an open critical vulnerability (CVEs excluded by a vendor advisory are not counted), devices currently unreachable according to monitoring, and devices with an open Soron alert. Each cell of the grid is shaded by the number of devices concerned.
How many devices can the map display?
The map is built for the largest estates. Because ConnectMyAssets sends clusters rather than individual devices, the browser draws at most a few hundred circles whatever the size of the estate.
Can each team or customer see only its own sites?
Yes. The map applies the same role-based access control as the rest of the platform, in the database, before anything is counted. A team granted one region sees and counts only that region, which makes the map suitable for MSPs serving several customers.
Can I display the map on a NOC screen?
Yes. Add a map widget to a dashboard and open it in TV mode: full screen, no menus, automatic refresh every minute or more. Each circle still opens the matching devices in the CMDB.
