The 5 Operational Gaps Every Utility Faces After Their pLTE Network Goes Live
Published by Phillip Smith, Milewire LLC
Your private LTE network is live. The coverage maps look good, the vendor handed over the keys, and Ericsson or Nokia is managing the equipment under a multi-year managed services contract. From the outside it looks like the hard part is done.
It isn't.
What most utilities discover in the first 12 to 24 months after go-live is that deploying the network and operating it are two completely different problems. The vendor handles the first one. Nobody handles the second one -- because nobody at the utility was hired to.
After 25 years in RAN engineering and private LTE operations, I have seen the same five gaps appear at every utility that goes through this transition. None of them are the vendor's fault. None of them are covered by your managed services contract. And all of them are fixable.
Here they are.
Gap 1: Nobody On Your Side Can Read the Vendor's Reports
Every month Ericsson or Nokia sends you a network performance report. It is full of KPIs, availability percentages, RCA summaries, and SLA compliance tables. It looks thorough. It looks credible.
The problem is that nobody at your utility has the wireless background to know whether it is accurate.
Can your IT team tell the difference between a vendor RCA that genuinely explains a root cause and one that satisfies a contractual obligation without actually saying anything? Can they identify when an SLA clock was started late, paused without justification, or calculated against a metric that doesn't reflect the outage you actually experienced?
In most utilities the answer is no. Which means the vendor is effectively grading their own homework with no one checking the work.
This is not hypothetical. SLA disputes are common in managed wireless contracts. The utilities that catch them have someone with wireless expertise reviewing vendor outputs. The utilities that don't catch them keep paying full contract value for underperforming service.
What this gap costs you: SLA credits you never claimed, vendor accountability that exists only on paper, and a false sense of network health that masks real operational risk.
Gap 2: Your ITSM Platform Has No Wireless Operations Workflow
Most utilities run ServiceNow or a similar ITSM platform for IT incident management. When pLTE was deployed, nobody configured that platform for wireless network operations.
What that means in practice:
- There is no wireless-specific incident category so pLTE tickets get logged under generic IT buckets with no priority logic tied to wireless severity
- There is no SLA clock logic that matches your vendor WLA so you cannot track compliance independently
- There is no integration between the network management system -- ENM or NetAct -- and your ticketing platform so alarms and tickets live in completely separate systems with no correlation
- There is no automated workflow connecting a network event to a field dispatch so when a site goes down the path from alarm to truck roll is manual, slow, and inconsistent
The vendor has their own ticketing system. They manage their SLAs inside it. You have no visibility into that system and no independent record of how incidents are being handled on your behalf.
What this gap costs you: Slower response times, missed SLA violations, no audit trail for vendor disputes, and field crews finding out about network problems from operational failures rather than proactive alerts.
Gap 3: You Have No Independent Alarm Visibility
Your vendor's IOC is watching your network. Ericsson's or Nokia's team sees every alarm, every threshold breach, every performance degradation as it happens. You see a report at the end of the month.
That asymmetry is a problem.
When a major outage occurs -- a BBU failure, a transport cut, a multi-site degradation event -- you find out when your field crews call in or when operations notices the SCADA link is slow. By the time the situation reaches you the vendor has already been working it for hours, the SLA clock has been running, and you are completely reactive.
For utilities this is especially dangerous during high-demand operational windows. Storm response, planned maintenance events, grid switching operations -- these are exactly the moments when you most need network reliability and exactly the moments when you have the least visibility into what is actually happening.
Independent alarm visibility does not mean replacing the vendor's NOC. It means having your own eyes on the network so you are not dependent on vendor-produced summaries to understand your operational posture.
What this gap costs you: Reactive instead of proactive operations, field crew productivity lost to unreported network degradation, and zero leverage in vendor conversations because you have no independent data to support your position.
Gap 4: No RF or RAN Expertise to Challenge Technical Decisions
At some point your vendor will recommend a configuration change, a firmware upgrade, a coverage modification, or a capacity expansion. They will present it with confidence and technical justification. And your team will have no way to evaluate whether the recommendation is correct, necessary, or in your best interest.
This happens constantly in managed wireless relationships. Not because vendors are dishonest -- most are not -- but because their technical staff are optimizing for network performance as they define it, not operational outcomes as you define them. Those are not always the same thing.
A few examples of where this matters:
- A firmware upgrade that the vendor recommends on their schedule may conflict with your operational calendar. Without RF expertise on your side you have no basis to push back on the timing.
- A coverage complaint from a field crew may get dismissed as a device issue by the vendor. Without someone who can pull performance counters and evaluate the RF environment you cannot challenge that diagnosis.
- A capacity expansion proposal may be legitimate or it may be a revenue opportunity for the vendor. Without independent analysis you cannot tell the difference.
Having RF and RAN expertise available to you does not mean hiring a full-time wireless engineering team. It means having access to someone who can review technical recommendations, ask the right questions, and tell you when to push back.
What this gap costs you: Configuration decisions made without your input, coverage problems that persist longer than they should, and expansion costs you may not need.
Gap 5: Your Network Knowledge Lives Only With the Vendor
Ask yourself this question: if Ericsson or Nokia walked away from your managed services contract tomorrow, how long would it take your organization to operate the network independently or bring in a replacement vendor?
For most utilities the honest answer is months -- and even then, only with significant outside help.
Everything about how your network is configured, how it has been maintained, what problems have occurred, how they were resolved, and what operational procedures govern the day-to-day -- all of that knowledge lives inside the vendor's organization. Your team has almost none of it.
This is not an accident. It is a natural consequence of outsourcing network operations without retaining any of the operational knowledge on your side. The vendor is not withholding information maliciously. They are simply not obligated to build your internal capability as part of managing your network.
The result is a dependency that deepens over time. Every year that passes without building operational documentation, runbooks, escalation workflows, and institutional knowledge on the utility side makes the vendor harder to manage, harder to replace, and harder to hold accountable.
What this gap costs you: Complete vendor dependency, zero negotiating leverage at contract renewal, and an organization that cannot function without the vendor even to answer basic questions about its own network.
What To Do About It
None of these gaps require the utility to build a full internal wireless operations team. That is expensive, slow, and frankly unnecessary given the size of most utility pLTE deployments.
What they do require is a structured approach to building the operational capability the vendor assumes you already have -- independent visibility, documented workflows, technical advisory capacity, and institutional knowledge that stays with your organization regardless of who manages the equipment.
That is exactly the gap Milewire was built to fill.
If you are a utility that has deployed pLTE in the last one to three years and you are starting to feel any of these five gaps, the right first step is a structured operational readiness assessment. Thirty to sixty days. A defined scope. A prioritized roadmap that tells you exactly what to address and in what order.
Phillip Smith is the founder of Milewire LLC and a 25-year veteran of RAN and private LTE network operations. Milewire provides AI-powered wireless operations services for utilities, mining operations, ship ports, and industrial operators running vendor-managed pLTE networks.
Schedule a discovery call or reach out directly at info@milewire.io.