“SAP augmented reality” returns mostly manufacturing and supply chain results. For utilities the useful question is narrower: where does AR on SAP IS-U or S/4HANA Utilities actually help a field crew, and what does the implementation require? The answer centers on field service, meter work, and asset inspection, not general enterprise digitization.
Updated 9 August 2026: rewritten against the current product landscape. SAP has now published a deprecation notice for the Augmented Reality feature in SAP Mobile Services, with removal from the mobile services cockpit UI scheduled for Q4 2026, so the route table below marks what is still supported and what is not. The deeper treatment of that change is in what the Q4 2026 deprecation actually changes.
Key takeaways
- There is no single “SAP AR product”. There are four routes, and one of them now has a removal date: SAP states that “the Augmented Reality (AR) feature in SAP Mobile Services is deprecated and will be removed from the mobile services cockpit UI in Q4 2026”.
- The route that carries most real deployments is SAP Service and Asset Manager, whose AR views and visual work instructions target first-time-fix rate, extended where needed by a partner package.
- The durable integration contract is not any AR feature. It is the OData service layer over SAP IS-U or S/4HANA Utilities, which every route reads and writes through.
- For utilities the value concentrates in four field tasks: substation inspection, meter work, first-time fix, and switching. AR does not touch billing, customer records, or regulatory reporting, and no honest business case should claim it does.
- Asset data quality is a prerequisite, not an outcome. Where IS-U records are wrong, AR renders wrong data in three dimensions, faster.
Is SAP discontinuing augmented reality?
Two SAP mobile AR components are going away in 2026, and the integration approach behind utility field AR is not. SAP has deprecated the Augmented Reality feature in SAP Mobile Services, with removal from the mobile services cockpit UI scheduled for Q4 2026. Separately, it has deprecated the SAP Fiori for iOS AR components (the FioriAR package), marked deprecated in 2025 and scheduled for removal in 2026 because they rely on outdated third-party frameworks; that repository is now archived. Both are SAP-side building blocks, not the field-AR story as a whole.
What carries real utility deployments is untouched by either removal: SAP Service and Asset Manager with its built-in AR views, partner extensions layered on top of it, and direct OData integration to SAP IS-U or S/4HANA Utilities. A pilot built on those three routes keeps working after Q4 2026. The route with the removal date is the platform-side configuration surface, not the field application and not the data contract. The full picture of what the Q4 2026 deprecation changes is covered separately.
The four routes, and which are still supported
Most confusion about SAP augmented reality comes from treating it as one product. It is four different things with different owners, different costs, and now different lifecycles.
| Route | What it is | Who owns the integration | Status as of August 2026 |
|---|---|---|---|
| SAP Service and Asset Manager | The mobile field application, with built-in AR views and visual work instructions aimed at first-time fix | SAP, with your Basis and functional teams | Current, and the default starting point |
| Partner extension on top of SSAM | Packaged AR bought as an extension. TeamViewer Frontline provides xAssist remote-assistance calls and xInspect inspection workflows, triggered in context from the work order the technician is executing; ViewAR SERVICE AR is a comparable SAP-partner route | The vendor | Current, richest workflow coverage |
| Direct OData build | Your own AR client reading equipment, functional location, work order, and notification records straight from IS-U or S/4HANA Utilities | You | Current, and the route that ages best |
| AR feature in SAP Mobile Services | The platform-side AR configuration surface in the mobile services cockpit | SAP platform team | Deprecated. Removal from the cockpit UI in Q4 2026 |
Two practical notes. Captured field media does come back: notes and images taken during hands-free workflows are stored in the SAP backend and synced, so the documentation trail lands in S/4HANA rather than in a vendor silo. And the deprecation only touches the fourth row. If your pilot was built on the first three, nothing about it changes.
“On a utility rollout the AR headset is the easy part. The hard part is whether the asset record in IS-U is clean enough to overlay. Where the SAP data is good, augmented reality earns its place on substation inspection and meter work. Where it is not, AR just renders bad data in three dimensions.”
Nikhil Jathar, founder of AvanSaber and former SAP consultant
What SAP augmented reality means in a utility
Augmented reality in this context is a presentation and capture layer sitting over SAP data. The system of record stays SAP IS-U or S/4HANA Utilities. An AR application reads asset master data, work orders, and service notifications that already exist in SAP, then surfaces them to a worker standing in front of the equipment. The worker sees relevant data overlaid on the physical environment and can capture field input back into SAP without leaving the work site.
Three routes exist to build this layer on SAP for utilities:
SAP Asset Manager, SAP’s standard mobile field service application, includes built-in AR capabilities. It connects natively to IS-U and S/4HANA Utilities work orders and asset records and is the lowest-integration-effort path for a utility that already uses SAP Asset Manager for field service dispatch.
Third-party AR platforms, PTC Vuforia, Scope AR, and TeamViewer Frontline being the most deployed in utility environments, connect to SAP through OData services exposed by IS-U or S/4HANA Utilities. They add capabilities like remote expert video overlay and industrial AR annotation that the SAP-native option does not cover natively.
Hands-free hardware, specifically RealWear Navigator headsets, is a separate hardware layer that works with both the SAP-native and third-party software routes. It matters most for tasks where a technician needs both hands free: substation switching, meter installation in confined spaces, and lineman operations at height.
Four utility field uses that are operational
The utility-specific value of SAP AR concentrates in four areas. Each maps directly to data the utility already holds in IS-U or S/4HANA Utilities.
Asset and substation inspection. Overlay the asset record, last-inspection data, and the inspection checklist on the equipment in view, then capture results directly to the SAP work order. For substation equipment with complex inspection procedures and regulatory documentation requirements, the structured capture to the asset record is often the primary value, more concrete than the AR visualization itself.
Meter reading and meter work. Guide a technician to the correct meter, display the installation and configuration history from IS-U, and reduce mis-reads and mis-installs. For smart meter deployment programs and meter exchange work, AR-guided installation reduces repeat visits caused by installation errors on the first visit.
Field service and first-time fix. Surface the open work order, asset history, and next correct step so a crew completes more jobs on the first visit. Reducing unnecessary return trips is one of the largest controllable costs in utility field operations, and first-time-fix rate is where AR-assisted field service shows the clearest measurable impact.
Lineman safety and switching. Present switching steps and hazard data in the field crew’s line of sight for high-risk tasks, with each confirmation captured back to SAP. For complex switching sequences that require documented step-by-step execution, AR-guided switching reduces procedure errors and creates an automatic audit trail in the asset record.
Each of these ties to data a utility already holds in SAP IS-U or S/4HANA Utilities. That is what makes them operational rather than aspirational. For the detailed picture of how AR connects to ERP asset modules, work orders, and inspection data flows, AR and ERP for utility asset management covers the integration specifics.
Augmented reality for utility field service
Utility field service is where SAP AR earns its keep, and the framing that matters is utility-specific: field crews, meter technicians, and substation teams working assets that already live in SAP IS-U or S/4HANA Utilities. This is not generic field service management software. It is an AR presentation layer over the utility’s own asset and work-management data, delivered through SAP Service and Asset Manager and the OData services that expose IS-U to the field.
The dispatch and work-order backbone stays in SAP. A crew receives the assigned work order, and the AR layer surfaces the asset record, service history, and the next correct step against the equipment in front of them. For a meter technician that means the installation and configuration history from IS-U at the meter, not back at the truck. For a substation team it means the inspection checklist and isolation data tied to the specific functional location. The measure that moves is first-time fix: fewer return trips because the crew had the right asset data, captured to the work order, on the first visit.
Two constraints keep this honest for a utility. The value shows up on defined, repeatable tasks tied to clean IS-U records, not across the whole field operation at once. And connectivity is worst exactly where the assets are, so offline capture with deferred sync back to SAP is a requirement, not an extra. For the work-order and asset-management mechanics underneath this, AR and ERP for utility asset management has the detail.
Integration architecture
The integration pattern is consistent across SAP-native and third-party approaches. The AR application calls OData services exposed by SAP IS-U or S/4HANA Utilities to read:
- Asset master records: installation dates, nameplate data, maintenance history, equipment ratings
- Work orders with task lists, parts requirements, and step-by-step completion sequences
- Service notifications and structured inspection checklists
- Safety-relevant records including isolation procedures and switching step sequences
On job completion, the AR application writes captured data back through the same OData interfaces: inspection results, photo attachments, completion confirmations, and exception flags. The asset record and work order in IS-U reflect the field results without manual back-office data entry.
The integration scope should be bounded. A pilot that connects to one workflow object type, such as the inspection work order, is a manageable integration project. Expanding to cover the full breadth of IS-U objects in the first deployment adds complexity without proportional benefit and makes measuring success harder.
Treat the AR tool as a field client. It reads from and writes to SAP. It does not replace SAP as the system of record and should not be designed to operate independently of the IS-U data model.
A substation inspection in SAP AR, step by step
Here is what the integration does on one concrete task, described as capability rather than a specific deployment. The point is which SAP IS-U objects the AR layer reads and writes, so the scope of a pilot is clear before anyone buys hardware.
- The crew opens the assigned inspection work order in SAP Service and Asset Manager. The AR layer resolves the substation asset from its functional location and equipment records in IS-U.
- On the equipment in view, it overlays the asset master data (nameplate, ratings, installation date), the last inspection result, and the structured inspection checklist attached to the work order.
- The technician works the checklist hands-free. Each reading, photo, and exception is captured against the work order and the equipment record.
- Measurement readings write back as measurement documents on the equipment. Photos attach to the notification or work order. Completion and any exception flags post to SAP.
- The asset record and work order in IS-U reflect the field result with no back-office re-keying, which is the documentation trail a regulator expects.
Every object named here already exists in a utility’s IS-U or S/4HANA Utilities data model. That is what keeps the walkthrough grounded: the AR layer surfaces and captures records that are already there, and a pilot that connects only the inspection work order and its equipment is a bounded, measurable integration rather than an open-ended one.
Manufacturing AR versus utility field AR
The public SAP AR material, and most of what ranks for the term, is about the factory floor: assembly guidance, warehouse picking, and machine repair against product and production data. That is a real use, and it is not the utility use. A utility is not assembling a product on a line. It is inspecting a substation, exchanging a meter, and switching a feeder, against asset and work-management data in IS-U rather than production data.
The distinction matters for a buyer. Manufacturing AR value cases lean on throughput and assembly-error reduction. The utility case leans on first-time fix, inspection data quality in the asset record, and a defensible audit trail for safety-critical work. Reading a manufacturing AR business case and assuming it transfers is the fastest way to scope a utility pilot wrong.
What a first pilot should look like
Utilities that run successful first AR pilots consistently apply the same scoping rule: one workflow, one asset type, one crew, and a defined success metric.
Substation inspection is the most common starting point because it satisfies each condition. The inspection checklist maps to a defined asset record structure in IS-U. Hands-free operation in the substation environment has immediate practical value. The success metric, inspection completion time and data completeness in the asset record, is objective and measurable within weeks of deployment.
Define the success metric before deployment, not after. For first-time-fix rate improvement, set a baseline from the prior period’s work order data before the pilot begins. For inspection data quality, establish what a complete record looks like in IS-U before any AR capture begins. Pilots without a pre-defined metric rarely generate the evidence needed to justify a broader rollout.
Hardware choice is a pilot decision, not a pre-decision. Most pilots begin with rugged tablets using camera-based AR because they are practical outdoors, work with gloves, and survive utility field environments. Headsets add clear value in specific indoor scenarios, substation switchgear rooms, meter vaults, and underground distribution chambers, where hands-free operation is a genuine operational requirement rather than a convenience.
| Hardware | Where it fits in utility work | What to watch |
|---|---|---|
| Rugged tablet, camera AR | Default for outdoor field work: meter exchange, overhead inspection, general work orders | Glove operation and screen legibility in direct sun decide adoption more than AR quality does |
| Hands-free headset (RealWear Navigator class) | Switchgear rooms, meter vaults, underground chambers, any task needing both hands | Safety approval runs on its own calendar and sits outside the software project |
| Smart glasses with remote assist | Remote expert calls on rare equipment, where the value is the person on the other end | Connectivity, which is worst exactly where the equipment is most obscure |
The connectivity point deserves more weight than it usually gets in a business case. A workflow that assumes a live session fails in the substation basement. Offline capture with deferred sync is a requirement, not a nice-to-have, and it should be tested at the worst site in the territory rather than the one nearest the office.
What it costs, honestly
Nobody publishes real numbers for this, and any vendor total cost of ownership slide should be treated as marketing rather than evidence. What can be said without inventing figures is where the money actually goes, and it is not where first-time buyers expect.
The AR software licence is rarely the largest line. The larger ones are the integration work to expose and map the right OData services, the asset-data remediation the pilot exposes, the device fleet and its safety approval, and the training and process redesign that has to survive crew turnover. A programme that budgets for licences and headsets and not for the other four is the standard way this fails quietly.
The corollary is that the first pilot should be scoped to make those costs visible early, which is another argument for one workflow, one asset type, one crew.
Where SAP AR does not pay
Being specific about the failure cases is more useful than another list of benefits.
- Where the asset data is known to be poor. AR surfaces the record faster; it does not correct it. Fix the record first or the pilot measures your data problem instead of your AR question.
- Where a tablet showing the same record performs identically. If nothing about the task requires hands free or spatial context, AR is an expensive way to display a work order.
- Training scenarios a good video covers. The AR training case is real in a few high-consequence procedures and oversold everywhere else.
- Anything in billing to cash. Billing, customer records, and regulatory reporting run in IS-U FI-CA and the billing engine, and have no meaningful AR use case at all.
- Programmes without a measured task. If nobody can name the metric before deployment, the rollout has no way to prove itself and will be cut in the next budget round regardless of how well it works.
Where to draw the line
Generic enterprise AR and VR for ERP, broader innovation strategy, and non-utility applications sit with AvanSaber. UtilitiesLabs keeps the focus on utility field work tied to SAP IS-U and S/4HANA Utilities data, because that is where the use cases are concrete and the data already exists.
AR does not improve billing accuracy, customer record management, or regulatory reporting. Those functions run in IS-U FI-CA or the billing engine and have no meaningful AR use case. A utility should not expect AR to touch the billing-to-cash process.
Data quality is a prerequisite, not an outcome. If asset records in IS-U are incomplete or incorrect, the AR layer surfaces incorrect information to the field. A data quality assessment of the relevant asset class should precede the pilot, not follow it.
The verdict
SAP augmented reality earns its place in utilities on specific, repeatable field tasks: substation inspection, meter work, first-time-fix support, and safety-critical switching. The technology works when it is narrowly scoped, tied directly to IS-U or S/4HANA Utilities asset data, and measured against a defined outcome.
Pilot on one workflow. Keep SAP IS-U or S/4HANA Utilities as the system of record. Scale only where the field data shows measurable improvement in first-time-fix rate, inspection data completeness, or switching error reduction. For the full SAP IS-U module map and how field service and asset management fit into the broader SAP utilities architecture, start with the SAP IS-U platform overview.