A discovery brief from Enmovil

The clock started. The spine doesn't exist yet.

BCI Burke closes this quarter. Peak season is already here.

BCI Burke closes this quarter. Right now, during the highest-revenue weeks, there is still no unified analytics spine across the two ERPs. Two order books, two plant networks, one peak season. The gap exists today, not after close.

(Sources: BCI Burke acquisition signed Feb 13, 2026, close expected Q2 2026. Platinum Equity acquired PlayPower Oct 31, 2025.)

Two ERPs · one Day-1

What we've read.

Two legacy systems about to meet. The analytics layer above them is the open question.

PlayPower ERP Huntersville NC 6 brands · 7 plants · PE Oct '25 BCI Burke ERP Fond du Lac WI close expected Q2 2026 ? analytics spine One view · one inventory unified across brands, plants, and dealer channel
System A PlayPower legacy ERP. 6 brands, 7 plants, live.
System B BCI Burke ERP. Arrives Q2 2026 at close.
The spine Analytics layer above legacy, lands before ERP consolidation finishes.
The goal Unified inventory, forecast accuracy, and dealer-order tracking across both entities from Day-1.
Two entities, one spine

The gap.

Between Day-1 of the BCI Burke merger and "one view across every brand, every plant, every dealer."

Hypothesis: the failure mode isn't ERP consolidation. That takes 18 months. It's the 6-month window after Day-1 when two ERPs run in parallel through peak season, and the blind spot between them turns into missed dealer orders, inventory misallocation, and dispatch errors. The spine needs to be live before the ERP decision is final.
EDP (SC Analytics)

% of combined SKUs with unified inventory, forecast accuracy, and dealer-order tracking in one analytics view. Measured weekly, per brand, per plant.

Numerator: SKUs live in the unified spine. Denominator: SKUs shipped across both entities that week.

0% on Day-1 to 80%+ by FY26 end: the integration story writes itself. Stall, and peak-season orders fly blind across two systems.

Oct '25
Platinum Equity acquires PlayPower.
Feb '26
PlayPower signs BCI Burke acquisition.
Q2 '26
BCI Burke close expected. Day-1 clock starts.
6 → 7+
Brands in the combined portfolio.

A hypothesis, not a characterization. We'd love to test it against your measured state.

Three clocks running now

Why now.

Integration clock, peak-season clock, dealer-channel clock. All live.

01

Integration blind spot

Two ERPs, two order books, two plant networks. No unified analytics layer above them. The gap between what each side sees lands on Day-1 as operational risk.

Platinum Equity acquired PlayPower · Oct 31 2025.

02

Integration clock

BCI Burke closes this quarter. Day-1 isn't a planning date. It's a live event.

Signed Feb 13 2026 · close expected Q2 2026.

03

Revenue clock

Spring and summer are the highest-revenue weeks in playground and recreation. Disruption landing now isn't a Q3 problem. It's a right-now problem.

Industry seasonality · municipal and school procurement cycles.

Three clocks, same quarter. If one is on your team's radar, it's worth a conversation.

Where fit could live

The leverage.

A hypothesis. ERP consolidation takes 18 months. The spine above it is where we'd test fit.

Outside-in read

Plan landed. Whether the spine stands up in parallel with, not after, ERP work: untested.

What "scaled" would look like

  • One inventory view across both entities from Q2 Day-1.
  • Forecast accuracy at brand × plant × region in weeks.
  • Dealer cycle time unchanged through the transition.

The replication surface

Huntersville NC + Fond du Lac WI → dealer channel.

Two brands as the pilot pair. Template for the full portfolio.

PlayPower + BCI Burke
HQs · NC and WI · 7+ brands
Municipal parks
Public-sector long tail
Schools
Seasonal bid cycles
Early childhood
Growth segment
Residential
Builder + consumer
Works on one pair → templates the remaining 5+ brands.
One platform, every decision layer

What Enmovil is.

The intelligence layer that sits above SAP, not in place of it.

PREDICT

Available for expansion

  • Forecast & Demand Intelligence
  • Inventory Planning & Optimisation
  • Scenario Modelling · S&OP
  • Warehouse & Node Operations

PLAN

Available for expansion

  • Dispatch & Route Optimisation
  • 3D Load Building
  • Network & Capacity Planning
  • Carrier Allocation

EXECUTE

Best-fit wedge for this conversation

  • Control Tower & Resilience · Unified Analytics Spine
  • Multimodal Orchestration
  • Smart RFQ / Bidding
  • ePOD & Freight Settlement
CADDIE AI: the cross-suite intelligence layer across Predict, Plan, and Execute. Conversational. Agentic. Sits above SAP S/4HANA and the legacy ERPs. Reclaims analyst hours that integration work consumes.
25+ Fortune 100 customers · 150+ team · 10+ years · ISO 27001 · SOC 2 Type II · SAP-ready · AI-native
Proof-by-geometry

How we've helped a peer.

Tier-1 global auto OEM. Multi-plant, multi-mode, dealer outbound. Manual vanning sheet eliminated. Contract extended 5 years.

Before

Excel vanning / loading sheets

  • Manual dispatch across plants, modes, dealer orders.
  • Fragmented visibility across rail, road, ocean, air.
  • Dealer sequencing by phone and spreadsheet.

After

One orchestration layer

  • Multimodal orchestration across every mode, one view.
  • Dealer sequencing automated end to end.
  • 4 to 5 years live. Contract extended 5 more.

~$2.15M

Annual dispatch savings.

4 modes

Rail, road, ocean, air on one layer.

5 yrs

Contract extension post initial deployment.

Eliminated

Manual vanning sheet.

Different category. Geometry translates. Percentages validated together.
The stack view

CADDIE AI above SAP, not in place of it.

The intelligence layer SC analytics and ops leads actually query.

CADDIE AI · conversational · agentic · cross-suite
Predict
Plan
Execute
PlayPower ERP · BCI Burke ERP · (future) unified S/4HANA · dealer portals
Plant · Dealer · Channel · Operations signals, real-time
No rip and replace. Both legacy ERPs stay until the formal consolidation project completes. CADDIE AI queries across the pillars in your language: "show me every open dealer order this week across both entities that's at risk on the combined plant capacity, and the corrective dispatch."
For a longer conversation

Questions we'd love to explore together.

What we'd want to understand in a longer conversation.

The spine gap

  • On Day-1, what does a dealer order on the BCI Burke side look like to someone in Huntersville: visible instantly, visible after a manual pull, or invisible?
  • Is there a single report today showing inventory across every PlayPower brand and plant in one view, or does it still need stitching by hand each week?

The integration state

  • When the team reviews integration progress, which operational metric turns red to green first, and who owns the data behind it?
  • The two entities almost certainly run different ERP instances, different analytics tooling, different KPI definitions. Which mismatch worries the team most on Day-1?

Season pressure

  • Spring and summer are your peak weeks. If a workflow change caused a two-week delay in visibility, what's the revenue exposure, and has anyone modeled it?
  • Is there a freeze window on systems changes during peak season, or is that not how integration is being managed?

The window

  • If an analytics layer were live above both ERPs before the consolidation decision, what conversation inside the business gets materially easier first?
  • Who is the right person for a 60 to 90 minute working session: you, or someone you want to shape scope with first?
Who's building this

Enmovil · the technology thought partner for autonomous supply chains.

AI-native platform for demand, inventory, dispatch, execution, settlement, sustainability. Sits above your existing stack.

Under orchestration
~100K
Trucks per day across the customer base
Daily ETA accuracy
99%
Road, rail, ocean, air
Forecast accuracy
97%
Demand sensing on deployed customers
Logistics cost savings
8 to 15%
Measured across deployments
Integration
3 to 4wks
On existing SAP, Oracle, TMS, WMS. No migration.
Deployed at
Dispatch Planning
Multimodal Logistics
Multimodal Orchestration
Dispatch Planning
Fleet Management
Logistics Orchestration
Logistics Resilience
Inventory Management
Freight Settlement
Dispatch Planning
Transport Management
Export Planning
Runs under GDPR and SOC 2. Data ingestion via API, EDI, or bulk upload. Enterprise SSO. Deploys over existing SAP ECC 6.0 and above.
The tension

Clock started Feb 13. Peak season is live. Spine doesn't exist. That's the 60 to 90 minutes we'd spend with you.

The ask: a 60 to 90 minute working session.

01

Test the hypothesis

Walk us through your actual Day-1 state. We'll point at where we think the spine gap is largest: inventory, forecast accuracy, or dealer order visibility. You tell us where we're wrong. Hypothesis sharpens or dies in the room.

02

Stack read above both ERPs

A shared read of where the analytics layer lands on top of the legacy systems before the consolidation decision. Which gaps close immediately, which at close: dealer visibility, cross-entity inventory, dispatch accuracy. No rip and replace.

03

One-page fit hypothesis

A co-drafted page naming the brand pair where evidence is clearest, the metric that turns green first, the scope you'd take back to IT and ops. You own it. We write it together.

Three questions before the session

On Day-1, where is the largest visibility gap?

Which Day-1 risk keeps the team up at night?

Who needs to be in the room?

Predict.Plan.Execute.
Not a pitch. A working session.globalsales@enmovil.inenmovil.ai

CONFIDENTIAL · Enmovil × PlayPower Integration discovery. Prepared for the American Supply Chain Summit 2026, Dallas. Third-party trademarks belong to their respective owners. Not affiliated with or endorsed by PlayPower, BCI Burke, or Platinum Equity.