A lot of fiber operators end up running fixed wireless too.
The reasons vary. Some started as fixed wireless operators and added PON as fiber funding became available. Some added fixed wireless to fill coverage gaps in areas where PON was economically impossible to reach. Some acquired a fixed wireless operator and now have two technology stacks sitting under one roof. BEAD funding has accelerated all of these scenarios, and operators who thought they'd be running pure fiber operations are discovering that a multi-technology network is actually the norm.
The problem is that most OSS/BSS platforms weren't designed to handle both. Operators who try to run PON and fixed wireless on a single platform typically end up with compromise, workarounds, or two separate operations pretending to be one.
Here's what genuine multi-technology support actually requires, and what to look for when evaluating platforms.
Why PON and Fixed Wireless Are Operationally Different
The obvious differences are in the hardware. PON uses optical line terminals, optical network terminals, and fiber distribution. Fixed wireless uses base stations, sector antennas, and customer premise radios. The provisioning workflows for each are entirely different, and the equipment vendors in each category don't overlap much.
The less obvious differences are operational. Fixed wireless installs typically take less time than fiber installs but require line-of-sight verification and signal quality testing that fiber doesn't. Fixed wireless service quality is affected by weather, interference, and local RF conditions in ways that PON isn't. Fixed wireless customers churn differently, experience different service issues, and require different support workflows.
Every one of those differences has to be handled somewhere in your OSS/BSS stack. A platform that treats fixed wireless as a bolt-on to a fiber-first system typically handles the differences poorly.
What Multi-Technology Support Actually Requires
Five capabilities separate platforms that genuinely support both technologies from platforms that only support one well.
Unified address and coverage management across technology types.
Your serviceability database needs to know which addresses can be served by PON, which can be served by fixed wireless, and which have both options available. Some customers in a mixed-technology market will be candidates for either, and your sales and provisioning workflows need to route correctly based on what's actually available at a specific location. A single coverage system that handles both technology types eliminates the handoff errors that otherwise accumulate.
Technology-agnostic order capture.
Your customer portal, door-to-door sales app, and CSR order entry tools should all qualify an address and present the right service options regardless of underlying technology. Subscribers don't care whether they're getting fiber or fixed wireless. They care that the service works and the purchase experience is simple. The sales workflow should abstract the technology from the buyer.
Dual-path provisioning on one platform.
This is where most platforms break down. A platform that provisions PON equipment well often handles fixed wireless provisioning poorly, or vice versa. The underlying provisioning engines for the two technologies are genuinely different, and a platform that treats one as primary and the other as secondary will reflect that bias operationally. What you actually need is a provisioning layer that handles both as first-class workflows, with vendor-specific modules for each OEM in each technology category.
Shared field operations with technology-aware workflows.
Your field team often handles both PON and fixed wireless installs, sometimes on the same day. The platform should route jobs based on technician skills (PON certification, RF testing capability, line-of-sight assessment) and present the right mobile workflow for whichever install type the tech is performing. Same scheduling system, same dispatch view, same mobile app, but technology-aware job cards and completion checks.
Unified billing across technology types.
Subscribers on either technology should be billed through the same BSS stack, with the same payment methods, the same self-service portal, and the same customer service workflows. Running separate billing systems for PON and fixed wireless customers creates operational overhead you genuinely don't need. Plan changes, promotional pricing, and customer moves between technologies should all run through a single billing logic.
Where Most Platforms Fall Short
Three failure modes are common across the platforms operators typically evaluate.
Fiber-first platforms that bolted on fixed wireless.
These platforms handle PON well but treat fixed wireless as a secondary technology. Provisioning workflows for fixed wireless are often thinner, vendor support is narrower, and field workflows don't handle RF-specific requirements cleanly. You can run fixed wireless on these platforms, but you'll feel the compromise every day.
Wireless-first platforms that added fiber.
Same problem in reverse. These platforms handle wireless provisioning well but often treat PON as a secondary workflow. You'll feel the compromise on the fiber side instead.
Platforms that require separate instances for separate technologies.
Some vendors address the multi-technology problem by selling you two platforms and claiming integration between them. This is the worst outcome operationally. You're paying for two systems, managing two deployments, and still dealing with handoffs between them. The integration layer is almost always the point of failure.
The platforms worth evaluating are ones that were designed for multi-technology support from the start, with both PON and fixed wireless as first-class workflows on a single data model. These are rare, but they exist.
Questions to Ask About Multi-Technology Support
Adapting the broader framework from OSS/BSS vendor evaluation questions for fiber operators, here are the questions specific to multi-technology capability.
-
How does your platform handle both PON and fixed wireless provisioning? Can you show us both workflows end to end?
Ask for a live demo of each. Watch how the two differ. If the fixed wireless workflow feels like an afterthought, it is.
-
Which OEMs do you support in each technology category?
You want specificity. Named OEMs in both PON and fixed wireless, with a clear process for adding new ones in either category.
-
Can you show us a customer running both technologies on your platform at scale?
Reference customers who actually run both are the strongest signal. Ask specifically how they're using each, and what the operational experience has been.
-
How does your platform handle an address that can be served by both technologies?
The right answer involves unified address classification, clear service option presentation in sales channels, and routing logic that handles both technology paths cleanly. Vendors who struggle to answer this question haven't thought carefully about multi-technology operations.
-
How does billing handle customers who switch between technologies?
Some subscribers will migrate from fixed wireless to PON when fiber reaches their area. The billing system should handle this as a plan change, not as a new customer onboarding. If it's the latter, you'll lose history and create friction.
-
What happens to our operation if we add a new technology in the future, like next-generation fixed wireless or XGS-PON?
The platform should extend to new technologies without requiring replatforming. This is a proxy question for architectural quality.
The Acquisition Angle
Multi-technology capability matters most when you're acquiring. A PON operator acquiring a fixed wireless network (or vice versa) needs a platform that can absorb the acquired technology without running two separate operations indefinitely. Operators I've watched handle this well are running on platforms that abstracted technology type from the start. Operators who handled it poorly spent years trying to rationalize two stacks and typically ended up replatforming anyway.
If acquisition is any part of your growth strategy, multi-technology support isn't optional. It's a foundational platform requirement.
Closing
Multi-technology operations are increasingly the norm for fiber and broadband operators, not the exception. BEAD funding, acquisition-driven growth, and the realities of rural coverage all push operators toward running both PON and fixed wireless. The OSS/BSS platforms that fit this reality are the ones that treated it as a foundational requirement rather than a bolt-on capability.
Evaluate on the criteria that matter. Look for genuine multi-technology support, not marketing language. And pressure test the claims with reference customers who actually run both.
FAQ
Can the same OSS/BSS platform handle both PON and fixed wireless?
Yes, but genuine multi-technology platforms are rare. Most platforms handle one technology well and treat the other as secondary. The platforms worth evaluating are ones that support both PON and fixed wireless as first-class workflows on a single data model, with technology-specific provisioning for both and unified address, order, field, and billing management across technology types.
What's the biggest operational challenge with running PON and fixed wireless together?
The provisioning workflows for the two technologies are fundamentally different, and most platforms handle one better than the other. Operators who run both often end up with operational compromises, separate tools for different customer segments, or effectively two parallel operations. A platform designed for multi-technology support from the start eliminates these compromises.
How do I evaluate a vendor's claim to support both PON and fixed wireless?
Ask for live demos of both provisioning workflows end to end. Ask for reference customers running both technologies at scale. Ask specifically which OEMs are supported in each technology category. Vendors who genuinely handle both well can answer these questions concretely. Vendors who don't tend to lean on future roadmap items or deflect to integration with partner systems.
Should my billing system be unified across technology types?
Yes. Running separate billing systems for PON and fixed wireless customers creates operational overhead you genuinely don't need. Subscribers should be billed through one BSS stack with one self-service portal, one payment method set, and one customer service workflow regardless of which technology serves them.
What happens when a subscriber moves from fixed wireless to PON?
On a unified platform, this should be handled as a plan change or service upgrade, with customer history preserved and a seamless transition to the new technology. If the platform handles it as a new customer onboarding, you'll lose history and create unnecessary friction. This is a specific scenario worth testing during vendor evaluation.
