I didn't have problems with its scalability. We have managed to go from about 100 devices to almost 4,000 or 5,000 devices, which is a pretty good number. What makes it cool is that you don't have to build everything in one environment. You can develop different tabs, and you can add device maps, for example, by a geographical area. You can break these maps by functionality. You can create maps for your IT group and your enterprise customers. You can also create maps for customers to whom you offer managed services with UPS, firewalls, and Wi-Fi. 

We have 20 or 30 users of this solution. Some users have just web access. Our support team has read-only access to HelpSystems InterMapper, which is the web-only access that is required to see a device in the red state. People can look at it quickly to get an idea about the uptime and some indication about the power issues.

It is used quite well in our organization. By having access to HelpSystems InterMapper, our support team doesn't have to really escalate too many tickets. We have a team for building new sites and keeping their eyes on our current sites. We have an engineering organization that is responsible for core maps and assisting the operators and support teams with different maps.

If you put some energy into it, you can create a lot of reference points in HelpSystems InterMapper. You can put information in the cloud and use it for the circuit ID in HelpSystems InterMapper. You can have an escalation with a circuit ID at the click of a button. You don't have to go and start looking up different records.

With carrier maps, you can create all of your nodes. Earlier, you had to go and search through the back of a system. Now you just click on it, and it takes seconds for an operator to see the flashing device in the carrier list, like the Verizon carrier map. You can click on the flashing red device and get the circuit ID for the flashing red device. Similarly, you can click on a carrier icon, and get the carrier escalation. 

Regarding scalability, it does well. If you're trying to do flows, it's limited because of the hardware requirements in the background, but if you're using it for up/down-type monitoring, it scales up very well.

We have not encountered any issues with scalability, and we are a global organization. To be fair though, the overall number of monitored devices is shrinking. On the plus side, the Intermapper RemoteAccess client has zero issues connecting to multiple servers.

It's a scalable solution.