Last spring, my VP of Operations dropped a folder on my desk. "We need to fix field communications by the end of the year," he said. And walked out. That was that.
I'm the office administrator for a utility field-services company, about 400 employees across three locations. I manage purchasing—roughly $850,000 a year across eight major vendors. Most of it is orderly: PPE, tools, office supplies, vehicle parts. I can order a pallet of work gloves with my eyes closed.
This project was a different beast entirely.
The Problem Nobody Wanted to Own
Our field crews had been complaining about dropped connections for months. They relied on a messy combination of personal hotspots, consumer phones, and sheer patience. When a technician was out at a remote site, diagnostic reports often didn't get submitted until they drove back into coverage. A few safety logs came in hours late. Nothing catastrophic at the time, but nobody wanted to be the one explaining to a regulator why documentation was missing.
Here's what I learned early: this wasn't a wifi problem. It was a cellular connectivity problem. We needed equipment designed to stay connected in vehicles, in harsh conditions, with no one around to power-cycle a router when it froze.
"Add the Best Blood Pressure Monitor You Can Find"
That was a crew lead's suggestion during our first week of research, delivered deadpan. He wasn't entirely joking. Looking for a connectivity solution without an internal technical team to lean on felt like shoveling sand against the tide.
I'm not a network engineer. I can't speak to spectrum bands or antenna isolation specs. What I can tell you from a procurement perspective is how to evaluate vendors when you don't speak technical language—because that's where the real traps are.
The first round of vendor calls went badly. One reseller pushed a box of Nokia 2660 Flip phones, insisting they were rugged enough for every field crew. Another tried to sell us wifi extenders, which would've been useless in trucks miles away from the nearest building. A third sent a quote without asking about our coverage areas, fleet size, or even how many vehicles needed this. I almost bought from that third vendor, just because they responded fast.
Almost.
What Changed My Approach
I started asking better questions. What I mean is, I stopped letting vendors tell me what to buy and started demanding they explain the basics without the acronym salad.
That's when one reseller asked a question that reset the entire project: "Are you looking for an embedded module, a gateway, or both?"
I didn't know the difference. So he explained it clearly. A cellular module is the radio component that goes inside a device to give it cellular connectivity—the engine. A gateway is the standalone box that manages connectivity for multiple devices—the vehicle. For us, we needed both: gateways in the trucks to handle onboard laptops and diagnostic tools, and embedded modules inside our custom inspection equipment.
That's how Sierra Wireless entered the conversation. I knew the name, but I couldn't have named a single product at the time. A contact in fleet operations at another utility company mentioned they'd standardized on Sierra Wireless gateways in their service trucks. That gave me somewhere to start—though their fleet is more than double our size, so I treated their recommendation as a lead, not gospel. I also confirmed during that research that Sierra Wireless is now part of Semtech—the acquisition closed in 2023—which eased my concern about long-term software updates.
The Obstacle: Cheap Solutions That Wouldn't Stay Cheap
The finance team saw the price difference between the Sierra Wireless quote and the consumer alternatives, and they pushed back hard. The Nokia 2660 Flip idea came up again—a whole pallet of them for less than two enterprise gateway units. My finance counterpart, who I genuinely respect, asked why we couldn't just hand everyone a phone and be done with it.
I had to explain something I'd only just learned myself. Consumer devices are built for a controlled life. They're not designed to handle constant vibration, temperature swings from freezing mornings to blazing afternoons, or running 12 hours a day in a work truck. The 2660 Flip is a perfectly good phone for many uses. A work truck is not one of them.
The upside of the cheap path was obvious: roughly $6,000 in upfront savings. The risk was that field failures would force us to redo the entire project within a year. I kept asking myself whether $6,000 was worth potentially repeating every procurement headache and losing the crews' trust. The expected value said no.
I documented that reasoning with rough math, not gut feel. That made the hard conversation easier. Finance respects numbers, even shaky ones.
The Boring Details That Actually Matter
Once we committed, the specifics mattered more than I expected. The module we standardized on was the Sierra Wireless AirPrime MC7455. If I remember correctly, it's a Category 6 LTE module supporting multiple frequency bands—which is important because our crews cross state lines. Even more important to a buyer: it's been widely deployed for years, so replacement stock is easy to find. I didn't want a priority safety project stalled because we'd chosen a module that was hard to source. That's the kind of risk that doesn't appear on a spec sheet.
For the trucks, we chose the AirLink gateway line. The configuration that fit our setup was one of the 3210 variants—whether that's the base SKU or the one bundled with the mounting kit, I'd have to check the purchase order. Don't quote me on the exact model number. What I do remember is why we picked it: multiple Ethernet ports, ignition-sensing power, and a wide operating temperature range. It boots when the truck starts and shuts down cleanly when the ignition cuts. You don't fully appreciate that feature until you realize no one's going to be crawling under a desk to reset it.
Installation coordination was a whole other adventure. Three locations. Twelve pilot vehicles to start, then a full rollout to 85 trucks. It sounds simple until you're juggling two installation vendors, an internal IT team of four people, and a field operations manager with zero patience for "operational transition phases."
The Pilot That Almost Exploded
We launched the pilot in September. By week two, six of the twelve installed gateways were reporting that the web management interface kept timing out. I panicked. The money was already committed. If the hardware was faulty, I'd be the one who spent five figures on boxes that didn't work.
Turns out it wasn't the hardware. The gateways were trying to reach the cloud management service, and a firewall rule—set up by our IT team for an unrelated project—was silently dropping the connection. The installation vendor and our internal IT had never communicated. And honestly, that's on me. I'd been so focused on vendor management that I forgot stakeholder management. Put another way: I tried to deploy a technical solution without ever making the humans who'd keep it running share a room.
Once the two teams talked, the problem disappeared within a day. I still remember our IT lead's reply: "That was fun. Let's align earlier next time." Fair.
What I'd Tell Another Buyer
If you're an administrator or office manager getting pulled into a connectivity procurement you don't feel qualified for, here's what I'd pass along:
1. The jargon is a barrier, but it isn't the point. You're still doing the same job you always do: evaluating total cost, supplier reliability, and long-term fit. The acronyms change. The logic doesn't.
2. Industrial hardware costs more because it does more. At least, that's been my experience. The difference between a consumer hotspot and an enterprise gateway isn't branding. It's temperature ratings, vibration tolerance, and continuous operation specs. The stuff you can't see in a product photo.
3. Ask about replacement availability before you buy. The MC7455 is widely deployed, so if one fails, I can source a replacement quickly. That question should be part of every evaluation, not an afterthought.
4. Bring your internal IT into the conversation early. They can make your rollout sleek or sink it, and it's not their fault if you never told them what you were planning.
The Bottom Line
We completed the full rollout in November, six weeks ahead of the year-end deadline. Crews stopped complaining about dropped forms. Safety logs started appearing on time. Even the operations manager sent a nice email, which I've kept for posterity.
The bigger lesson was about buying things you don't fully understand yet: find suppliers willing to educate you. The reseller who explained modules versus gateways, and who once told us we didn't need a more expensive model we'd asked about—that's who won the contract. Not the cheapest quote. The honest one.
An informed buyer makes better decisions. A supplier that invests in your understanding earns your trust. I'd rather spend ten minutes learning the difference between a module and a gateway than deal with a mismatched purchase that eats a quarter of the budget fixing it later.
And for the record: I never ordered those blood pressure monitors. Strangely, I didn't need them.