It Started With a Simple Question: "Can We Use Sierra Wireless for This?"
Back in October 2023, I was sitting in a planning meeting for a new fleet tracking project. Our client wanted rugged, reliable connectivity for a batch of 120 vehicles operating in remote areas with harsh conditions. The name on everyone's lips was Sierra Wireless.
"Sierra Wireless XR80 should handle it," the project lead said. "It's built for this."
I nodded. Should is a dangerous word in procurement.
At the time, I was a relatively new procurement analyst handling IoT hardware orders for about 18 months. I'd processed maybe 40-50 orders, some small, some in the thousands. But this was my first major deployment involving Sierra Wireless gear specifically. I was confident. Overconfident, as it turns out.
The Decision: XR80 vs. Something More... Specific
The client needed a gateway that could handle 5G and 4G fallback, with industrial-grade durability. The Sierra Wireless XR80 checked those boxes. It also had that rugged design we kept hearing about—IP64 rating, wide operating temperature range. Perfect, we thought.
But then the question of modules came up. The XR80 is a gateway, but it works with specific cellular modules. The client's existing infrastructure was built around Sierra Wireless MC7700 modules—a solid 4G LTE cat-3 module.
Here's where I made my first mistake: I assumed compatibility.
I went back and forth between the MC7700 and a newer 5G module for about a week. The MC7700 offered proven reliability and lower cost per unit. The 5G module offered future-proofing but came at a 40% premium. The client was cost-conscious—small fleet, initial deployment of 15 vehicles for a pilot. They went with the MC7700. I wrote up the order.
(Note to self: never assume compatibility when mixing gateways and modules from different product lines—even within the same brand. I really should have checked the official compatibility matrix.)
The Mistake That Cost $1,800
We ordered 15 Sierra Wireless XR80 gateways and 15 Sierra Wireless MC7700 modules. The order came to about $23,000. We were proud of the savings we'd negotiated.
When the hardware arrived, our installation team started the setup. Three days later, I got a call.
"The modules don't fit."
"What do you mean they don't fit?"
"The MC7700 uses a Mini PCIe form factor. The XR80 takes M.2 modules. They're physically incompatible."
I checked the spec sheets. Sure enough—XR80 requires M.2 Key B modules. MC7700 is Mini PCIe. The information was there all along, buried in the technical documentation. I hadn't checked.
The fix: we had to order 15 Sierra Wireless EM9191 modules (M.2, 5G-ready) at $120 each. The MC7700s we couldn't return—restocking fee plus the modules weren't compatible with any other active project. We sold them at a loss.
Total waste: $1,800 in excess cost, a 1-week delay in deployment, and a very uncomfortable conversation with the client about why their "proven" quote had increased.
I'm not a hardware engineer, so I can't speak to the nuances of PCIe vs. M.2 interface design. What I can tell you from a procurement perspective is: never trust a product name alone. Verify the physical specifications.
The Pivot: Why the XR80 + EM9191 Actually Worked Well
Once we got the right modules, the Sierra Wireless XR80 performed exactly as advertised. The EM9191 provided the 5G fallback we hadn't planned for (which turned out to be a bonus when the client expanded coverage requirements). The rugged design held up in the field—dust, vibration, temperature swings. No issues.
The client, despite the hiccup, was happy with the hardware. They eventually expanded the deployment to 75 vehicles based on the pilot success. That full order was $112,000—a significant account for us.
Part of me wishes we'd started with the EM9191 and avoided the whole mess. Another part acknowledges that the mistake forced us to build a proper spec verification checklist. We've caught 47 potential errors using that checklist in the past 18 months. Including one earlier this month where a vendor tried to substitute a different module without telling us.
What I Learned About Sierra Wireless (and Procurement)
Three takeaways from this experience:
- Specs are non-negotiable. Brand reputation and product family don't guarantee compatibility. Verify form factor, interface, power requirements, and firmware version for every component.
- Small orders deserve the same rigor as large ones. This was a 15-unit pilot. Had I treated it with the same seriousness as a 100-unit order, I would have caught the incompatibility. The vendors who took my small order seriously are the ones I went back to for the big expansions. That includes Sierra Wireless's distribution partners—they were patient with my panicked phone call.
- Document your mistakes. Without that checklist, I'd probably have made a similar error on another project. Now it's a permanent part of our workflow.
When I see someone comparing Sierra Wireless vs. Cisco or another vendor for a new project, I always ask: "Are you checking the compatibility of every component? Because I've learned that lesson for you."
No hard data on industry-wide rates of this mistake. But based on the number of forum posts I've seen about module incompatibility, my sense is it's more common than people admit.