powering productive workplaces
Front page
ExplainerService & Connectivity1h · 12:01 BST · 13 min read

Field Service Under Storm Pressure: Can IFS Resolve Keep Up?

IFS Nexus Black launched Resolve for Utilities at DISTRIBUTECH in February 2026, extending its field service stack with AI aimed at storm restoration. What is missing is a named utility deployment showing a measured before and after restoration time.

IFS Resolve for Utilities
IFS Resolve for Utilities

IFS Resolve for Utilities extends IFS Field Service Management with AI-assisted crew callout, mutual-aid coordination, and field guidance, giving energy and water providers a service-management layer that connects outage, asset, workforce, inventory, and contractor data to field execution, for now, though, public proof that Resolve itself cuts restoration time is still missing.

Reuters counted more than 373,000 US homes and businesses without power on July 6, 2026, with Pennsylvania above 70,000 outages and FirstEnergy and DTE Energy taking some of the biggest hits. That’s when field-service software stops being a feature contest. Dispatch, crew availability, parts, safety, and restoration time are what matter.

Utilities already have systems that detect faults, model networks, and track outages. The hard part comes next: planners have to combine those signals with qualifications, switching authority, asset history, stock, contractors, mutual-aid crews, and changing field conditions. That makes IFS's real proposition broader than a storm-response screen. It's a service-management layer connecting operational information to execution.

Currently, IFS has genuine utility pedigree in mobile workforce management and scheduling, including SoCalGas and Elvia, while Resolve adds utility-specific emergency-response capabilities. The architecture makes sense. Buyers still need to prove that the connections hold up when data is stale, mobile coverage disappears, crews change, and the restoration plan has to be rebuilt mid-event.

TL;DR: Is IFS Resolve for Utilities Ready for a Real Storm?

  • IFS Nexus Black launched Resolve for Utilities at DISTRIBUTECH International on February 3, 2026. It extends IFS Field Service Management for energy and water providers with AI-assisted crew callout, mutual-aid coordination, and field guidance.
  • Resolve sits on IFS's wider scheduling, mobile workforce, contractor, asset, and service-management stack. IFS also has utility customers using that underlying machinery, including SoCalGas and Elvia, so the sector story doesn't start with Resolve.
  • IFS hasn't published a named utility deployment showing a measured before-and-after restoration-time result for Resolve itself. Its utility evidence supports the platform underneath the new layer more strongly than the newest outage claim.
  • S&P Global reported on March 31, 2026 that system integration, data quality, and data access were the most common technical problems in energy and utility AI projects. Thirty-four percent of initiatives started in the prior year had been terminated.

What Is IFS Resolve for Utilities?

IFS Resolve for Utilities is a utility-specific extension of IFS Field Service Management. IFS Nexus Black launched it at DISTRIBUTECH International on February 3, 2026 for energy and water providers, with intelligent crew callout, mutual-aid coordination, and mobile field guidance layered onto IFS's wider scheduling, contractor, asset, and service-execution capabilities.

IFS Resolve isn't replacing the utility's outage management system, SCADA, GIS, or core asset records. Its value comes from using information from those environments to decide who should go, what they need, what work takes priority, and how completion gets recorded.

SoCalGas already chose IFS Mobile Workforce Management and Planning & Scheduling Optimization to replace a 30-year-old system, while IFS says Elvia supports 1,200+ daily users and thousands of field workers on IFS Cloud. Those examples don't prove Resolve's restoration claim, but they do show the underlying field-service stack has utility operating history.

IFS is more careful than some of the launch language seems, too. In the February 3, 2026 announcement, Brian Burdette, Emergency Management Supervisor at SoCalGas, said the platform could reduce restoration times. 'Could' is the right word. IFS still hasn't published a completed Resolve outage deployment with measured restoration results.

Key Takeaways

  • Resolve adds utility-specific muscle to IFS Field Service Management. Buyers shouldn’t expect it to replace OMS, SCADA, GIS, or core asset systems.
  • SoCalGas and Elvia strengthen the utility pedigree of the underlying IFS stack, while Resolve-specific restoration evidence remains prospective.

Why Do Utilities Need Specialized Field Service Management Software?

Utilities need field service software that understands qualifications, switching authority, asset condition, network priority, parts, location, and safety constraints together. A crew can be three miles from a failed substation and still be the wrong crew. The assignment has to be operationally valid before anyone worries about route efficiency.

Utilities already have a labor problem, so bad scheduling gets expensive fast. Reuters said on May 18, 2026, 2026 that the US needs roughly 507,000 more workers across transmission, grid infrastructure, and energy construction by 2030. A scarce line worker shouldn’t be driving across town for a job with the wrong materials or getting reassigned after the truck is moving.

IFS Planning & Scheduling Optimization is built to juggle skills, location, demand, constraints, and available resources as conditions change. The catch is obvious: if the outage, asset, workforce, inventory, or identity data is old, the “optimized” answer can still be lousy.

Utility Problem What the Platform Needs to Know
Damaged substation Skills, clearance, asset history, switching rules
New outage cluster Customer impact, urgency, crew travel time
Contractor deployment Identity, qualifications, permissions
Remote site Offline instructions and later synchronization
Missing component Depot stock and alternative parts

Mobile workforce management can’t just tell somebody where to go next. It should catch a lousy assignment before the truck moves and keep the right job context handy when the original plan falls apart.

Key Takeaways

  • Utility scheduling is a safety and qualification problem as much as an efficiency problem. The nearest crew isn't automatically the right crew.
  • With Reuters projecting a major grid-workforce shortfall through 2030, wasted specialist hours become a service-management problem utilities can measure directly.

Which 2026 IFS Field Service Updates Matter Most to Utilities?

The 2026 IFS changes that matter most to utilities are Resolve, IFS Loops Agent Studio, IFS Cloud 26R1 service execution, asset-based AI pricing, and the AVEVA partnership. Together they push IFS beyond dispatch toward connected planning, field execution, asset decisions, and governed AI. Buyers should judge how the pieces work together.

S&P Global reported on March 31, 2026 that 64% of energy and utility organizations invest more than 10% of IT budgets in AI, while only 43% of recent projects were expected to return value within 12 months. Thirty-four percent of initiatives started in the prior year had been terminated, with system integration, data quality, and data access the most common technical challenges.

2026 Update Why a Utility Buyer Should Care
IFS Loops Agent Studio Governed planning, dispatch, and knowledge recommendations
IFS Cloud 26R1 Mobile Work Order is offline-capable; the browser Service Execution Portal is online-only
Asset-based AI pricing Some Industrial AI is priced by managed assets; confirm contract scope
AVEVA partnership Links operational asset data to maintenance and enterprise execution
Original Software partnership Code-free regression testing can help de-risk IFS Cloud changes and upgrades

Architecture and ownership are more important here than release volume. Buyers should ask whether Resolve, Loops, mobile work, contractor tools, and partner data share a support path and coherent data model. Otherwise the coordination headache simply moves from dispatch into IT.

Key Takeaways

  • S&P Global’s 34% termination rate makes connectivity and bad data part of the product result, not some implementation footnote.
  • Ask which 2026 capabilities are included, which are separately licensed, and who owns the end-to-end workflow when a partner connection fails.

Learn more about service management and connectivity in this guide.

How Does IFS Connect Utility Asset and Outage Data to Field Work?

IFS connects utility data to field execution by combining operational signals with asset history, network priority, workforce capacity, parts, and work plans. The interesting part of IFS isn’t the alarm. Utilities already have plenty of alarms. The value is in connecting that signal to asset history, network priority, available people, parts, and the work that’s already underway.

IFS’s May 19, 2026 partnership with AVEVA makes that idea easier to see. AVEVA brings real-time operational data; IFS is supposed to turn it into maintenance, scheduling, and execution decisions. A transformer can be running hot, but that reading won’t tell you who’s qualified to respond or whether the spare is sitting in the wrong depot.

IFS says this setup can shrink detection-to-response from days or weeks to hours. There’s no named utility result proving that yet, so the claim stays in pencil. Resolve also depends heavily on what’s feeding it. OMS, ADMS, SCADA, GIS, AMI, EAM, ERP, weather, inventory, identity, and contractor data need to line up well enough that the resulting dispatch isn’t nonsense.

Key Takeaways

  • AVEVA strengthens the mechanism behind IFS's connectivity story, but the 'days or weeks to hours' claim remains projected until a named utility publishes a measured result.
  • For utility buyers, connector ownership, refresh speed, writeback, and conflict handling deserve the same scrutiny as the scheduling algorithm.

How Does IFS Coordinate Utility Crews, Contractors, and Mutual Aid?

IFS coordinates mixed utility workforces through availability, skills-based scheduling, contractor management, mobile work, and automated callout. Resolve adds cross-region and mutual-aid coordination, while IFS Cloud provides the execution layer underneath.

APPA said in May 2026 that its network coordinated 220-plus utilities across 32 states during Hurricanes Francine, Helene, and Milton. It also found gaps in emergency planning. That’s an important limit on the software story. Better allocation helps, but it won’t sort out a vague agreement or an argument over who has final authority.

IFS Cloud 26R1 needs precision here. The browser-based Service Execution Portal is online-only. IFS Mobile Work Order works online and offline, including for contractor technicians, with some features limited while disconnected. That’s worth remembering when storms take mobile coverage with them.

IFS Loops adds Digital Workers for planning, dispatch, and knowledge tasks. Utilities still need human approval, visible reasoning, and proper credential checks when outside crews are involved. IFS’s asset-based AI pricing could work well during a surge, but the contract needs to say exactly how contractors, mutual-aid crews, agents, and emergency spikes get counted.

Key Takeaways

  • APPA's 2026 review shows that mutual-aid failures can start with operating agreements and authority, outside the software itself.
  • The Service Execution Portal is online-only; IFS Mobile Work Order is the offline-capable route buyers should test for storm field execution.

What Utility Evidence Supports IFS Field Service Management?

IFS isn’t coming into utilities cold. SoCalGas picked its Mobile Workforce Management and Planning & Scheduling Optimization tools to replace a 30-year-old system. Elvia reportedly has more than 1,200 daily users plus thousands of field workers on IFS, and Tekniska verken chose IFS Cloud in December 2025 to tie together ERP, EAM, FSM, and asset-investment planning.

Utility / Evidence IFS-Reported Position What it Tells Us
SoCalGas Selected IFS MWM and PSO to replace a 30-year-old system Major US utility proof for scheduling and mobile workforce
Elvia IFS reports 1,200+ daily users and thousands in the field Utility-scale field service and asset-management history
Tekniska verken Selected IFS Cloud in Dec. 2025 to connect ERP, EAM, FSM, and AIP Direct evidence for the connected-platform proposition
Konica Minolta 20-25% productivity gain; 4.36x ROI in 18 months Strong scheduling proof, but cross-sector
Resolve for Utilities No named restoration result published yet The remaining gap is Resolve-specific

The examples prove sector fit more convincingly than cross-sector cases alone.

Konica Minolta adds useful scheduling evidence, with reported productivity gains of 20% to 25% and a 4.36x ROI in 18 months. ISG’s February 2026 Buyers Guides also ranked IFS among the top three Overall Leaders in several field-service categories. That gives the underlying service platform some useful credibility. It doesn’t tell us whether Resolve can shave hours off a major outage.

Key Takeaways

  • SoCalGas, Elvia, and Tekniska verken give IFS a real utility deployment story for workforce, field service, assets, and connected operations.
  • Resolve's missing proof is narrower than 'IFS lacks utility evidence.' The unanswered question is whether the new Resolve layer measurably improves restoration outcomes.

How Does IFS Compare With Other Utility Field Service Platforms?

IFS is appealing when a utility wants field work tied to assets, maintenance, scheduling, contractors, inventory, and enterprise data. Oracle has deeper utility-network software, Veoci focuses more narrowly on storm administration, Salesforce suits customer-led field work, and ServiceNow fits enterprise workflow. The best choice depends on the gap being fixed.

Platform Best Fit Where Buyers Should Push
IFS Resolve for Utilities Asset-heavy utilities connecting assets and field execution Count licenses, connectors, partner tools, and support owners
Oracle Utilities Utilities centered on Oracle OMS and network operations Check whether IFS reduces fragmentation or adds another layer
Salesforce Field Service Customer-led field work Test asset depth, emergency scheduling, and network links
ServiceNow FSM Enterprise workflow-led service Identify which utility and asset functions still need specialists
Veoci Storm response and mutual-aid administration Check support for routine asset maintenance after the emergency

Oracle is the comparison IFS can’t really dodge. Oracle says its Outage Management System supports more than 60 million meters in production and coordinates restoration across field, mutual-aid, and asset teams. IFS has to make breadth part of the argument. It can connect service work, assets, people, and planning across operations that are usually spread all over the place. That’s useful for a large asset-heavy utility. If the problem is simply storm callouts or reimbursement, though, it may be more platform than anyone asked for.

Key Takeaways

  • Oracle's 60-million-meter OMS footprint remains a real incumbent advantage where network operations already sit in Oracle.
  • IFS differentiates on the connection between asset management and service execution. Buyers should decide whether that breadth solves the actual gap.

What Should Utilities Test Before Choosing IFS Resolve?

Utilities should test IFS Resolve with a deliberately difficult outage scenario. Include conflicting asset signals, a crew cancellation, missing parts, outside workers, lost connectivity, and a dispatcher override. The platform should show how it rebuilds the plan, preserves safety rules, and records why the new decision was made.

Start with severe weather and ask IFS to pre-position crews, contractors, vehicles, and materials. Add a transformer alarm and a fresh outage cluster, then remove the assigned crew, move the required part, introduce mutual-aid workers on unfamiliar devices, and cut mobile service. Make the dispatcher reject the AI recommendation and ask the platform to explain the safer alternative. That exposes whether data connections and human controls work when the script breaks.

Track signal-to-work-order time, dispatch time, planner interventions, callout acceptance, AI overrides, parts availability, mutual-aid onboarding, offline sync failures, first-time completion, mean time to restore, safety exceptions, integration latency, and audit completeness. That’s how you find out whether the demo actually works when things get ugly.

The commercial test matters too. Get written answers on Resolve availability, Loops dependencies, connector ownership, offline execution, asset-based pricing, contractor treatment, surge usage, and overnight support. A utility shouldn't discover during a regional storm that three vendors own three parts of one restoration workflow.

Key Takeaways

  • Give the demo a bad day. Kill a connection, change a crew, lose some data, then score how well the system digs itself out.
  • Put feature availability, pricing scope, connector ownership, offline behavior, and escalation responsibility in writing before the first real storm tests them for you.

What’s the Verdict on IFS Resolve for Utilities?

IFS has built a credible utility proposition around a problem that goes well beyond dispatch. Resolve adds storm response and mutual-aid capabilities to a field-service stack already used by utilities, while the wider IFS architecture connects workforce scheduling with assets, contractors, mobile execution, and enterprise data. For asset-intensive providers trying to cut operational handoffs, that combination deserves serious attention.

The remaining gap is specific and important. IFS still hasn’t published a named utility deployment showing that Resolve reduced restoration time during a major outage. That doesn’t undermine the wider platform evidence, but it does mean buyers should separate architectural promise from demonstrated restoration outcomes. IFS belongs on the shortlist, particularly where fragmented service and asset workflows are the bigger problem.

rate this story
helps rank stories across uc today
The discussion0 takes · attributed & checked

Does this reflect your experience?

opening the room…
Read nextordered by techtelligence · every pick explained
same beat · Service & Connectivity

Can Better Integration Save Customer Trust? Xurrent Is Betting on It

11 Aug 2026
same beat · Service & ConnectivityThe Future of UC Onboarding Is Self-Service10 Aug 2026same beat · Service & ConnectivityTata Communications Global Network: Is Network Fabric Ready for AI Service Management?7 Aug 2026