Bring the order type that causes you trouble.
The Grove is a fully configured SAP EAM system with Sigma, Gamma and Theta running inside it, against a live, governed S/4HANA system. You name the scenario; one of our people drives. We follow one work order through it, end to end, while you watch.
Most demonstrations show you a screen.
This one shows you a record.
A screen can be made to look like anything. A record has to have come from somewhere, and it has to still be there when you drill into it an hour later.
The walkthrough
One order. Six stages. No hand-offs you cannot see.
A leaning distribution pole on feeder 12, from the moment a crew member raises it to the moment it turns into a number someone reports. Scroll to move through it.
Stage 01 · The notification
A crew member reports a leaning pole
It starts the way it starts on your network. Someone on the ground raises a notification, and the system has to know what kind of work this is before anybody plans it.
- Notification type
- M2 — Malfunction report
- Functional location
- USNE-DIST-04-FDR12-P0331
- Description
- Pole leaning, guy anchor pulled
- Priority
- 2 — High, 72h
- Reported by
- Line crew 14, from the field
- Catalog profile
- Overhead — structure
Stage 02 · The order
The order type decides everything downstream
One order type carrying inspection, corrective, capital and storm work is the single most common thing we are called in to unpick. Here they are separate, so the cost, the planner and the schedule all know which kind of work this is.
- Order type
- PM02 — Corrective, distribution
- Operations
- 0010 dispatch · 0020 de-energise · 0030 set pole · 0040 transfer
- Components
- 45ft class 3 pole, anchor kit
- Production resources
- Digger derrick, bucket
- Planner group
- D04
- Settlement
- Cost center D04-OH
Stage 03 · The schedule
The schedule and the system stop drifting
The order lands in the capacity plan and in Oracle Primavera P6 at the same time. Gamma keeps SAP PM and P6 in step in near real time, in both directions, so the two are never reconciled by hand on a Friday afternoon.
- Work center
- OH-CREW-D04
- Scheduled start
- Wk 41, Tue 06:30
- P6 activity
- A1240 — Set pole, FDR12
- Interface
- Gamma — SAP PM and Primavera P6
- Latency
- Near real time, both directions
Same window, both systems — and it stays that way without anyone exporting anything.
Stage 04 · The map
One asset, one map, one hierarchy
The functional location resolves to its Esri ArcGIS feature, so the crew in the field and the planner in the office are looking at the same structure rather than two records that happen to share a number. Theta keeps the two aligned as the network changes.
- Feature class
- Structure — ArcGIS Utility Network
- Tied to
- USNE-DIST-04-FDR12-P0331
- Attributes in step
- Class · height · install date · circuit
- Interface
- Theta — SAP and Esri ArcGIS
- Direction
- Both
Stage 05 · The confirmation
The cause is picked, not typed
The crew confirms against the operation they were actually sent to do, and the cause comes off a catalog profile rather than out of a free-text note. That one difference is what makes next quarter’s reliability number worth having.
- Confirmation
- Final, 10 of 10 operations
- Actual work
- 6.5 h, crew of three
- Damage
- OH-STR-02 — Leaning structure
- Cause
- OH-CAU-07 — Anchor failure
- Activity
- OH-ACT-11 — Structure replaced
- Measuring point
- Ground-line decay reading taken
Stage 06 · The number
And the number drills back to this order
Sigma’s measures are built on the work order, so the figure on the scorecard is not a re-keyed total. It resolves to the records that produced it — you can start at the KPI and finish at the confirmation we just watched.
- Measure
- Corrective structure replacements, D04
- Built from
- Confirmed PM02 orders
- Period
- Week 41
- Drill path
- KPI → order type → order → confirmation
- Governed by
- A data contract on SAP BAIP
Click the figure and you are in the order list.
Click an order and you are in this confirmation.
Nothing in between is re-keyed.
What is actually in there
Eight things already configured
Not a sandbox assembled for a demonstration. This is the architecture we would deploy for you, with our products running inside it.
Running inside it
What each product does while you are watching
Sigma
EAM balanced scorecard
Stage 06
You will see a measure on the scorecard and then, without leaving the room, the orders behind it and the confirmation behind those. Bring a number you cannot currently drill into and we will build the equivalent in front of you.
Gamma
SAP – Primavera interface
Stage 03
You will see an order change in SAP and the P6 activity follow it, and then the reverse. Bring the case where your schedule and your system last disagreed and we will run that one.
Theta
SAP + Esri integration
Stage 04
You will see a functional location and its ArcGIS feature carrying the same attributes, and what happens to both when the network changes. Bring a part of your hierarchy you are unsure about.
Who it is for
Six people get something different out of the same hour
The executive sponsor
Whether what you are being sold already exists in standard — and we will say so when it does.
The EAM lead
Order types, catalog profiles and the functional location hierarchy, argued over with people who have built them before.
The GIS lead
What SAP and Esri ArcGIS alignment looks like while it is running, rather than on an architecture slide.
The scheduler
SAP PM and Primavera P6 agreeing, in near real time, without a Friday reconciliation.
The reliability engineer
Failure history that does not have to be rebuilt in a spreadsheet every quarter.
The architect
The clean-core rule applied to a real case — where we would extend, and where we would not.
Booking one
Four formats. Pick who is in the room.
Straight to the reveal
One thing: the scorecard figure resolving all the way down to the confirmation. No configuration, no architecture, no build-up.
The order, end to end
The full six stages in one pass — notification to number — with the three products doing their part where they actually do it.
Role by role
The same order followed through each role in turn — planner, scheduler, GIS, crew, reliability — in the transactions each of them actually lives in.
Clean core, in detail
How it is built: SAP BAIP, the standard APIs each product uses, the data contracts, and exactly where we would and would not extend.
Tell us the scenario you care about and who is coming. We will set The Grove up for that, and we will be straight with you about what is live, what is configurable, and what is still on the roadmap.
Before you come
Bring three things
The session is worth far more with something real in it. None of this needs preparing — you already have all three.
01
An order type that causes you trouble
The one that carries four kinds of work, or the one nobody can settle cleanly. We will put it through all six stages.
02
A part of your hierarchy you are unsure about
A feeder, a substation, a treatment plant — wherever the functional locations and the map have stopped agreeing.
03
A number you cannot drill into
A reliability or compliance figure you report but cannot take apart. We will build the equivalent measure in front of you.
Straight about it
Three things the Grove is not
NOT THIS
It is not a slide deck
Every screen in the session is a live system responding to what is typed into it. If something does not work, you will watch it not work.
NOT THIS
It is not a sandbox you have to build
The configuration is already done and governed. Nothing in the session depends on your team standing an environment up first.
NOT THIS
It is not a commitment
No part of booking the Grove obliges you to buy anything, and if standard SAP already does what you are looking at, that is what we will tell you.
Next step
Come and try to break it
Bring the order type, the hierarchy and the number. Ninety minutes later you will know whether the thing you are considering is a product, a configuration decision, or already in standard.
Book the Grove
Put the order type, the hierarchy and the number in the box above. That is the part we build the session around. Or email info@alphaoak.com.
SAP, SAP BAIP, SAP S/4HANA and SAP Analytics Cloud are registered trademarks of SAP SE. Esri and ArcGIS are trademarks of Esri. Oracle and Primavera are trademarks of Oracle. AlphaOak is an SAP and Esri partner; The Grove is an AlphaOak environment and is not an SAP, Esri or Oracle product. The records shown are demonstration records.