ContactBook the Grove

SAP EAM · SAP BAIP · Enterprise integration

Smart Solutions for Complex Challenges

We build SAP asset and work management for gas, electric and water utilities, and for asset-intensive industries beyond them — the architecture and consulting, the integrations, and three products of our own that keep your systems aligned and your teams informed.

Then we show it running — using your data, against a live, governed system, in ninety minutes.

Book the GroveSee the three products

The Grove is our demonstration environment — a fully configured SAP EAM system, with our products running in it.

The platformSAP S/4HANA asset and work management — master data, order structures, maintenance strategy and the reporting that stands on them.
The ecosystemEsri ArcGIS, Oracle Primavera P6 and the rest of it, connected to SAP through standard, upgrade-safe patterns.
How you startNinety minutes in The Grove, our fully configured SAP EAM demonstration environment. We drive; you bring the work that causes you trouble and watch it run end to end.

Partners and memberships

SAP partnerEsriLocusViewMirataSoftASUG member

Three products

Built on the rule, not around it

All three ship today. All three run inside The Grove, against a live, governed S/4HANA EAM system, so you can watch them work before any of this becomes a procurement question.

Product 01SigmaEAM balanced scorecardA governed KPI model built on the work order, so every measure resolves back to the SAP records that produced it — and drills all the way down to them.Open the product page Product 02GammaSAP – Primavera interfaceKeeps SAP S/4HANA and Oracle Primavera P6 in step in near real time, in both directions, so the schedule and the system stop drifting apart between status meetings.Open the product page Product 03ThetaSAP + Esri integrationKeeps functional locations and Esri ArcGIS features aligned, so the office and the crew are working from one map and one hierarchy.Open the product page

How we build

Extend the core. Do not modify it.

The field and the mapEsri ArcGIS · Oracle Primavera P6 · mobile execution
The extension layerSAP BAIP — Sigma, Gamma and Theta run here, on standard APIs
The coreSAP S/4HANA EAM, standard and unmodified
The networkAssets, functional locations, and the work order that moves across them

Clean core

Everything we ship sits above the line, on standard APIs. The core stays as SAP shipped it — no custom ABAP, nothing to unpick — which is what keeps an upgrade an upgrade rather than a second program.

Where standard will not reach at all we build Custom Solutions to the same rule. And we will tell you first whether standard already does it, which is more often than you might expect.

What we do

Four practices, one trunk

Utilities first, one platform, deeply. Every engagement extends the SAP foundation you already run rather than standing something new beside it.

Practice 01

Consulting and Advisory

Owner’s-agent advisory: readiness, architectural governance, quality assurance, and the difficult question asked early rather than late.

ReadinessAssuranceOwner’s agent
Practice 02

SAP EAM Consulting

Asset and work management designed around how crews actually execute — master data, order structures and maintenance strategy. Roughly 70% of the benefit of an S/4HANA program is realized here.

Master dataOrder structuresFailure codes
Practice 03

SAP BAIP Consulting

Business AI, integration and extension work grounded in governed SAP data, so the outputs are defensible to your regulator and to your own finance team.

Data contractsExtensionsGovernance
Practice 04

Enterprise Integration

Esri ArcGIS, Oracle Primavera P6 and the wider ecosystem connected to SAP through standard, upgrade-safe patterns. One set of numbers rather than a reconciliation.

Esri ArcGISPrimavera P6Standard APIs
Utilities first · one platform · four practices

Four layers, one structure

Everything out there is one of four things.

A utility is not one picture but four, stacked over the same ground. Each layer changes what the one below it means — and a single structure runs through all four, because by the top layer it is what the number is made of.

The networkEvery structure on the district, laid out the way the circuit actually runs.
The workEvery order open against those structures right now.
The scheduleWhat the plan says will happen on the feeder, and when.
The numberAnd the one measure all of it is supposed to resolve to.
P0331
Illustrative district. Not a customer network.

Where programs break

The reconciliation nobody is paid to do

The same structure, read out of four systems, attribute by attribute. Four of the nine agree. The other five are what a program quietly spends its budget on.

ASSET P0331 · FEEDER 12 · DISTRICT 044 OF 9 ATTRIBUTES AGREE
ATTRIBUTESAP S/4HANAESRI ARCGISPRIMAVERA P6FIELDAGREE
Functional locationUSNE-…-P0331P0331—P0331✓
Structure classClass 3Class 2—Class 3▲
Height45 ft45 ft—45 ft✓
CircuitFDR12FDR12FDR12FDR12✓
Planned dateWk 41—Wk 43Wk 41▲
Order typePM02——PM02✓
StatusReleased—In progressComplete▲
Failure causeOH-CAU-07——free text▲
Cost objectD04-OH—Project WBS—▲

Five disagreements, none of them a bug — every system is right inside its own rules. What is missing is the contract between them, and that is the thing we are usually called in to write.

The Grove

Watch one order travel, end to end

A fully configured SAP EAM system with Sigma, Gamma and Theta running inside it, against a live, governed S/4HANA EAM system. Bring an order type that causes you trouble and we will follow it through all four moments — planned, executed, mapped, measured.

Book the GroveSee the three products

Eight indicators

8 indicators it’s time to call AlphaOak

Tick the ones that sound like your week. Every one of these is something we have been called in to fix.

/ 8

Pick the ones that sound like your week.

One or two is a project. Worth a short conversation.

Three or more is a pattern. This is the call we usually get.

That many usually points at the operating model rather than the backlog.

Book the Grove

Where the work is going

Five rungs, and none of them skip

Maintenance strategy climbs in order, and every rung runs on the data the one below it produced. That is why the quickest route up is so often backwards — into the record. Most of the programs we join are working somewhere between the second rung and the third.

Rung 01 · Reactive

The order is written after the fact

Everything is emergent, so the record gets written from memory once the crew is back in. Run-to-failure is a legitimate strategy for the assets you have chosen it for — the difficulty is telling those apart from the ones that simply surprised you. The first move is an order type that separates the deliberate from the unplanned.

Order typesNotification qualitySAP EAM Consulting

Rung 02 · Preventive

Strategy moves into the maintenance plan

Task lists, maintenance items and scheduling parameters carry the strategy instead of a spreadsheet and a long-serving planner. This rung stands or falls on the functional location hierarchy: when it mirrors the cost center rather than the network, the plan cannot follow the asset.

Functional locationsTask listsMaintenance plansTheta

Rung 03 · Predictive

The asset tells you when

Measuring points and condition data take over from the calendar on the assets that justify the instrumentation. Most of the work is making readings arrive as records rather than as reports, and agreeing in advance what a reading is allowed to trigger.

Measuring pointsCharacteristicsTheta · Gamma

Rung 04 · Proactive

Failure history becomes a design input

Catalog profiles and failure codes that crews can complete in the time they actually have, so the reliability team stops rebuilding the picture every quarter and starts changing standards, specifications and strategy with it.

Failure codesCatalog profilesSigma

Rung 05 · Prescriptive

The intervention is proposed, and signed

Governed SAP data on SAP BAIP, where a proposed intervention arrives with the evidence attached and the approval stays with a named person. This rung is only worth building once the four below it are honest — which is why we rarely start here.

SAP BAIPGoverned data contractsSAP BAIP Consulting

From the practice

What we are publishing

Field notes, sessions and working demos, written by the people doing the work — which is the only reason any of it is worth reading.

FEATURED · FIELD NOTESThe Grid Has No Undo ButtonWritten for the person who has to sign the program off, not for the search engine.1 Sep 2026 · Read it
ADVISORYThe Fourth List: What Utility Transformation Teams Don’t Know They Don’t Know2 Sep 2026SAP BAIPAI Can Recommend. The Utility Must Answer.11 Aug 2026FIELD NOTESThe Little Things That Make Work Work2 Sep 2026

Who we are

A young firm with hundreds of programs behind it

AlphaOak is a senior-only advisory for gas, electric and water utilities. Between them, our team has delivered hundreds of SAP EAM implementations across three continents. We work as an owner’s agent — our only interest is whether the program works — and we will say so when something is not worth doing.

Our storyAll services

Next step

Start with the hardest part

A short conversation about where your SAP, GIS and schedule data stop agreeing — and what it would take to bring them into line.

Start a conversationBook the Grove