I have typed 'what is on my wifi' into a search bar more times than I want to admit. The first time, I assumed this was a security question. Maybe someone was leeching bandwidth. Maybe there was a rogue access point. The second time, I assumed IT would have a neat answer. They didn't.
The router said 47 clients. IT's spreadsheet said 12. My asset register said 23. The truth was somewhere around 40, depending on whether you counted the power meter that still held a DHCP lease but had been dead for six months.
From the outside, this looks like an IT problem. It's not. It's a cost problem with an IT symptom.
The Surface Problem: 'What Is on My Wi-Fi?' Is Not a Router Question
When you type 'what is on my wifi', what you really want to know is what you don't know. The router knows a MAC address and maybe a hostname. It doesn't tell you which engineer's project that device belongs to, when it was calibrated, or whether it is still needed. This is basically a trust issue. A network scan does not create the missing trust.
In a test and measurement environment, the unknown device is often not a hacker. It's a National Instruments cDAQ chassis that someone moved from Lab 2 to Lab 4 without telling anyone. Or a CompactRIO controller that was connected to a test stand and then disconnected but never removed from the network. Or a thermocouple input module that is sitting in a drawer but still appears in the last scan log. None of these are security incidents. They are inventory failures.
One of the few things I can price without calling a vendor is postage. USPS publishes stamp prices on usps.com/stamps, and they change on predictable dates. There is no equivalent for a lab network. A device can appear between the time a DHCP scan finishes and the time you walk across the building. The network has no price list, so the only useful inventory is the one you maintain yourself.
The Deeper Problem: Nobody Tags the Instrument
When I first started managing our annual budget—around $280,000 for instrumentation and support—I assumed the procurement system would have the final word. It didn't. Six years later, I know the system is only as good as the behaviour around it.
Here is the typical scenario. A lab manager buys a National Instruments cDAQ chassis on a purchasing card under $5,000. A National Instruments 9234 module comes out of a drawer, already owned but not in the asset register. The chassis connects to the lab Wi-Fi so a technician can watch a vibration measurement from the other side of the building. No asset tag. No network registration. No note to procurement. The work gets done. That is success to everyone on the floor. It only looks like a mistake to me.
To be fair, the engineers weren't trying to hide anything. The asset system was slow, and they had a test window. They solved the problem in front of them. The problem in front of them was not 'maintain the inventory'. It was 'get the measurement before the test stand is torn down'. So the cost of an unmanaged device stays invisible until someone asks the question that triggers the search: 'what is on my wifi?'
Last year, we found a PXI system under a bench that had been on the network for fourteen months. The engineer who installed it had left the company. The system was still collecting data that nobody was looking at. That is not a Wi-Fi issue. That is an inventory issue, and nobody in procurement wants to say that to a CFO.
The Real Cost of an Unknown Device
The surprise wasn't that we had unknown devices. The surprise was that each one had a cost that did not show up on the purchase order. Let me give you the four that show up in every audit.
Duplicate purchases. In 2023, I found $18,400 in equipment that had been ordered because the system said we did not own it. We had three National Instruments 9234 modules in the asset ledger and five on the shelf. The extra two were the 'missing' ones. Duplicate purchases don't happen because people are dishonest. They happen because nobody can see the floor from the procurement file.
Recurring costs. A National Instruments 9234 module is not a one-time purchase. It has a calibration cycle, a support contract, and a place in the total cost of ownership. If the device is invisible, the calibration date passes. When you finally find the device, you either use uncalibrated data or pay for rush calibration. We spent about $2,800 a month on calibration—no, $2,900, I'm mixing it up with the quarterly support bill. The point is, the recurring costs do not disappear when the device is forgotten.
Security questions. Per FTC business guidance, if a security tool claims to provide 'complete visibility' of your network, that claim has to be truthful and substantiated. But no tool can substantiate 'complete' if your asset data is wrong. When I asked one vendor how their scanner knew which device was which, they sent a white paper with no dates. That is a red flag. A scanner is only as good as the baseline you give it.
Engineering time. If a technician cannot trust the network inventory, they will spend an hour verifying each IP address before a test. Multiply that by twenty engineers, and the 'unknown device' has already cost more than a new network scanner. The list of forgotten devices is not infinite, but at 3 a.m., while you're staring at a DHCP table, it feels like infinity.
There is also the hidden setup fee. One vendor quoted $3,200 for network discovery software. The 'free setup' cost us $700 in extra labour because they didn't mention the cable identification work until the invoice arrived. That is the kind of line item that never makes the ROI calculation.
What I Did Instead of Buying More Hardware
If you ask the internet 'what is on my wifi', you will get advice that includes buying a network scanner, a new access point, or a software-defined radio. A National Instruments SDR is a great tool for RF applications, but it will not tell you that a forgotten CompactRIO controller still holds an IP address from 2021. Don't buy hardware to solve an inventory problem.
What helped us was a rule. Before any networked test asset gets installed, someone sends a one-line email to an asset folder. That's it. It isn't 'digital transformation' and it doesn't require AI. It took us three months to get everyone to use it. (Should mention: the old system had trained people to ignore it, so we had to rebuild trust by making the new file actually useful.)
We also started with the tools we already owned. NI MAX was able to list several National Instruments devices on the same subnet. It was not a full Wi-Fi audit, and it won't discover a stolen laptop, but it gave us a baseline that the engineers recognised. NI SystemLink can do more if you need a centralized repository, but we weren't ready for another platform.
An informed customer asks better questions and makes faster decisions. That applies to internal customers too.
Most of all, I stopped calling it an asset management project. I started calling it a way to protect test windows. The lab team cares about that more than they care about depreciation schedules. After comparing three options, we settled on a simple spreadsheet plus a review every quarter. Procurement policy now requires anyone buying networked test gear to send the asset email before the p-card is approved. That one sentence saved us from a confusing quarter and probably from another duplicate order.
National Instruments Corp. made a very flexible product line. That flexibility means someone has to decide how far asset responsibility goes. If you are searching 'what is on my wifi', you are already at that decision point. The answer isn't a new instrument.
Leave a Comment