Every consultant offering you an SAP MES transition will hand you a 5-phase roadmap. Assess. Pilot. Expand. Cutover. Optimize. The phases are not where projects go wrong. The wrong target architecture in Phase 1 is where they go wrong. Pick the wrong destination and you spend $2-5M and 18 months getting somewhere your CIO is going to regret in 2032. The honest reality: SAP DM on BTP is cloud-only and adds a permanent subscription. For discrete plants with deep custom MES logic, CNC-heavy operations, OEE history that must be preserved, or operator UIs the team already trusts, there is a third target most consultants don't pitch. Same 5-phase roadmap, different destination. AI-first MES platform running on NVIDIA on-prem hardware. MES workflows protected. OEE history preserved. Work order routing kept. Operator screens look the same on day one. Pilot in 6 to 12 weeks. Book a free demo of SAP MES transition roadmap software.
The On-Prem Server Stack — Your MES Backbone Without the Cloud
Discrete MES data is high-value. Production orders, routings, work-in-progress, OEE history, operator credentials, genealogy records — the kind of data your IT security, audit, and IP teams want kept inside your perimeter. Three pieces of NVIDIA hardware sit in your control room, never connect to the public internet, and run your full MES stack. Book a free demo of on-prem MES migration software.
SHOP FLOOR · BRIDGE
NVIDIA Jetson AGX Orin The Shop Floor Bridge
JobTalks to CNC, PLC, SCADA, scanners, torque tools
SpeedSub-second updates from every station
WhereMounts on the production floor, near machines
FormSmall ruggedized box, fits in switchgear cabinet
What it does: Replaces SAP PCo and SAP ME machine integration. Reads from any PLC brand via OPC-UA, MODBUS, MQTT. Local buffering ensures no data loss during network maintenance. Same integration tags MII used — minimal rewiring.
CONTROL ROOM · MES CORE
RTX PRO 6000 Blackwell The MES Core
JobRuns work orders, routings, OEE, traceability
SpeedSub-second operator screen response
WhereSits in your control room behind your firewall
FormTower computer, fits under a desk
What it does: Runs your full MES — production orders, routings, work instructions, OEE calculations, traceability, quality holds. AI layer adds predictive scheduling and anomaly detection MII never had. Pushes status to S/4HANA via the same APIs.
ENTERPRISE · OEE ARCHIVE
NVIDIA DGX Station GB300 Ultra · OEE Archive Brain
JobPreserves OEE history · fleet-wide pattern matching
SpeedCross-plant analytics in hours
WhereSits at corporate HQ in a server rack
FormRack-mounted, 24/7 enterprise grade
What it does: Loads all your historical MES + OEE data from SAP ME into time-series storage. AI layer analyzes downtime patterns across plants. Audit trail preserved for compliance lookups — no data loss during migration.
100%
Stays inside your building · never goes online
$0/mo
No subscription · buy once, own forever
Offline
Works fully air-gapped if your team requires it
Yours
Source code included · modify it freely
The 5-Phase Roadmap — Every Phase, Every Exit Criterion, Mapped
This is the same 5-phase structure SAP consultants use, applied to the AI-first on-prem destination. Each phase has a defined deliverable and an exit criterion you don't cross until it's met. Phase 2 is where the NVIDIA hardware lands on-site. Sign up free for SAP MES transition roadmap software.
P1
ASSESS
4 WEEKS
INVENTORY + FIT-GAP
Inventory every MES transaction, custom workflow, integration touchpoint, and operator screen. Interview supervisors. Tag every artifact: keep · transform · retire · replace. Output is a board-ready plan.
EXIT
Phased migration plan signed off · scope locked · budget approved
P2
PILOT
6-12 WEEKS
HARDWARE BOM LANDS
NVIDIA hardware on-site — Jetson Shop Floor Bridge + RTX MES Core + DGX OEE Archive. 3-5 machines pilot. MES workflows mirrored. OEE history loaded. Operators trained on screens that look the same.
EXIT
Pilot line stable · KPIs match MII · operators signed off
P3
EXPAND
2-6 MONTHS
WAVE ROLLOUT
Roll out platform line-by-line, area-by-area. Run new platform parallel with MES. Validate every output line by line. Operators continue using familiar screens. No production interruption.
EXIT
All lines online · parallel run validated · zero production loss
P4
CUTOVER
1-2 WEEKS
SWITCHOVER + HYPERCARE
Cut over by site, in waves. New platform becomes authoritative. SAP ME placed in read-only mode. Run hypercare for one stable quarter before considering full decommission.
EXIT
Stable quarter · ME read-only · audit docs refreshed
P5
OPTIMIZE
ONGOING
AI LAYER · TURN ON
Activate the AI-first layer your old MES could never offer — predictive scheduling, anomaly detection, fleet-wide OEE pattern matching, auto work order generation. Continuous improvement begins.
EXIT
No exit · this phase continues for the life of the plant
Three Real Discrete-Plant Scenarios — Same Roadmap, Different Plant
Three real migration scenarios from real discrete manufacturers — each walked through in plain language. Same 5-phase roadmap, same hardware, different challenges. Book a free demo of SAP MES roadmap software.
SCENARIO 01
"Our operators have used the same MES screens for 12 years. Retraining the floor on SAP DM's new POD designer feels like an enormous risk. Is there a faster path?"
THE PROBLEM
Aerospace components plant. 180 operators. Trained on SAP ME screens for over a decade. SAP DM's POD designer rebuilds operator UIs in a different paradigm — the SAP integrator estimates 4 months of full-floor retraining plus a productivity dip in the first quarter post-go-live. The COO sees a high adoption risk and is asking the IT director to explore alternatives.
HOW THE HARDWARE SOLVES IT
Phase 1 (Assess) → Phase 2 (Pilot)
Inventory every MES screen + workflow. Replicate exact look-and-feel on new platform — same fields, same buttons, same flow logic. Operators see screens that match what they've used for 12 years.
The MES Core (RTX)
Runs the operator UIs natively on-prem. Source code included means UI templates are fully customizable. Operator workflow stays identical — only the backend technology changes.
Phase 3 (Expand)
Wave rollout. Each operator gets 30 minutes of orientation (not 4 months of retraining). Productivity holds through cutover. Floor confidence high.
THE RESULT
180 operators trained in 30 min each (not 4 months). Zero productivity dip. Adoption risk neutralized. COO approved fleet rollout.
SCENARIO 02
"We have 8 years of OEE history feeding our continuous improvement program. SAP DM cloud migration loses the time-series detail. Is that history protected?"
THE PROBLEM
Automotive Tier-1 supplier with 8 years of detailed OEE history — every downtime event, every quality hold, every changeover timing. CI program uses this as the baseline for every improvement initiative. SAP DM migration typically truncates time-series detail to summarized roll-ups. Plant continuous improvement leader is fighting to protect the granular history.
HOW THE HARDWARE SOLVES IT
The OEE Archive (DGX)
Loads all 8 years of granular OEE history into on-prem time-series storage. Full timestamp resolution preserved. Original event types, downtime reason codes, quality flags all kept intact.
The MES Core (RTX) + AI Layer
Continuous improvement dashboards continue running against the same OEE history. AI layer adds pattern matching the old MES couldn't do — surfaces recurring downtime causes the CI team had been chasing manually.
CI Program Continuity
CI program runs uninterrupted across the cutover. Baseline comparisons remain valid. AI surfaces 3 chronic loss categories the team hadn't isolated before.
THE RESULT
8 years of OEE history preserved at full resolution. OEE up 4% in first quarter post-cutover. CI program accelerated.
SCENARIO 03
"Our work order routing logic has 600+ rules built over 10 years. SAP DM's POD Designer can't import them. Do we rebuild all 600 rules from scratch?"
THE PROBLEM
Industrial valves manufacturer. 10 years of work order routing logic — 600+ rules covering product variants, customer requirements, machine capability matrices, quality stage gates, rework routing. No documentation beyond the rules themselves. SAP integrator wants 18 months and $3.2M to rebuild every rule in SAP DM's POD Designer. Plant CIO is searching for a faster path.
HOW THE HARDWARE SOLVES IT
Phase 1 (Assess) · Source Code Included
Inventory all 600 rules. Categorize: 410 ported as-is, 130 modernized (cleanup of tech debt), 60 retired (redundant or obsolete). Audit trail captures the decision for each one.
The MES Core (RTX)
Routing rules port as code modules — not rebuilt in proprietary low-code designers. Your team owns the result forever. AI layer adds dynamic rule selection based on real-time machine availability.
Phase 4 (Cutover)
All 600 rules executing correctly day one. Parallel run with SAP ME for one quarter validates output line-by-line. No business disruption.
THE RESULT
600 rules migrated in 7 months · 60 retired as redundant. $2.8M+ saved vs SAP DM rebuild quote. Routing logic owned forever.
$4-8M
Typical combined savings at a discrete plant vs the SAP DM cloud rebuild path — operator UI continuity, OEE history preservation, work order rules ported as code. Plus ongoing $0/mo perpetual license and data sovereignty.
Phase 1 Assessment · 4-Week Inventory · Board-Ready Plan
Get Your 5-Phase MES Transition Roadmap. Phase 1 Starts the Day You Book.
Book a 30-minute call. We walk through your current MES footprint, custom logic, OEE history, and operator screens. You leave with a phased roadmap specific to your plant — Phase 2 pilot can land hardware in 6 to 12 weeks. Buy it once, own it forever — no monthly fees, source code included.
What You Get — Everything In One Box, Yours Forever
A pre-configured AI-first MES platform arrives at your control room. Shop floor bridge, MES core, OEE archive, source code, migration templates, parallel-run validation tools — all pre-loaded. Connect to your existing PLCs and S/4HANA. Plug in, validate, cut over module by module. Sign up free for discrete manufacturing MES software.
Buy Once, Own Forever
No monthly fees. No per-user charges. No annual price increases. One price up front.
Your Data Stays Home
CNC programs, OEE history, work order rules, traceability records — all stays inside your firewall.
Source Code Included
Port routing rules and custom MES logic as code, not rebuilt in proprietary designers. Not locked in.
Ready Out of the Box
MES + OEE + ISA-95 + S/4HANA connectors — all pre-loaded. Phase 2 pilot in 6-12 weeks.
Frequently Asked Questions
What's the smallest first step we can take this quarter?
A 4-week Phase 1 Assessment. Our team inventories your MES transactions, maps every integration touchpoint, classifies custom logic into keep/transform/retire/replace buckets, defines a future-state vision, and produces a phased migration plan with effort estimates. Output is a board-ready plan plus a shortlist of quick-win use cases for Phase 2 pilot. Most plants find this is the most useful 4 weeks of the entire migration.
What happens to our master data and historical MES data?
Master data (materials, BOMs, routings, operations) flows from S/4HANA or ECC into the new platform via standard SAP integration. Historical MES data — work orders, OEE events, downtime reasons, genealogy records — is loaded into time-series storage on the DGX with full timestamp resolution preserved. Compliance lookups continue to work against the same data. Nothing gets summarized or truncated. The data migration plan is a formal Phase 1 deliverable.
Can we run the new platform parallel with SAP ME during cutover?
Yes — and parallel run is part of every standard rollout. Phase 3 runs the new platform alongside SAP ME for typically 4-8 weeks per site. Every output is validated line-by-line against SAP ME before cutover. Phase 4 cutover happens only when KPIs match, operators are signed off, performance is proven, and the cutover playbook has been rehearsed. SAP ME goes to read-only mode for one stable quarter before any decommissioning decision.
How fast can we get to Phase 2 pilot hardware on-site?
Typical timeline: Phase 1 Assessment is 4 weeks. Hardware procurement and pre-configuration is another 4-6 weeks running in parallel with the back end of Phase 1. Phase 2 pilot installation and validation is 6-12 weeks once hardware is on-site. So from contract signature to a live pilot line running in your plant is usually 14 to 22 weeks total — versus the 12 to 24 months SAP DM partners typically quote for a full ME-to-DM migration.
Will the AI layer disrupt our existing MES workflows?
No. The AI layer is additive, not disruptive. Through Phases 2 and 3, the platform replicates your existing MES workflows exactly — same operator screens, same work order rules, same OEE definitions. The AI capabilities (predictive scheduling, anomaly detection, fleet OEE pattern matching, auto work order generation) only activate in Phase 5 Optimize, after the basic MES is stable. Each AI feature can be toggled on per line, per shift, per use case. Operators always have an "off" switch.
5 Phases · Hardware in Phase 2 · Buy Once, Own Forever
Get Your Transition Roadmap. Don't Wait for the 2030 Clock.
Book a 30-minute call. Walk through your MES footprint. Get a phased roadmap and a hardware BOM. Pilot in 6 to 12 weeks. Buy it once, own it forever — no monthly fees, source code included.
