top of page

The full enterprise systems lifecycle, platform-agnostic: strategy and assessment, requirements-driven selection, implementation with full environment-lifecycle discipline, and recovery of programs that have stalled or failed. 29 JD Edwards EnterpriseOne implementations within 100+ enterprise systems engagements across Oracle, SAP, and Microsoft Dynamics. If your program has turned yellow or red, I diagnose the structural failure and lead the recovery through go-live.

The Problem

ERP programs fail in predictable ways: the integrator replicated your legacy mess in new software; the master data foundation was never designed; integrations were built transaction by transaction instead of as an architecture; training was an afterthought; the planning engine was configured but nobody architected how planning should work. The dashboard turns yellow, then red — and now you are paying for the program twice.

The Engagement

Honest diagnosis of what can be salvaged versus what must be rebuilt, then hands-on leadership through go-live. Scope spans the platforms an operating model actually runs on — ERP, CRM, CPQ, project planning and management, finance and accounting — and the connective tissue between them: integration architecture, data architecture and taxonomies, and legacy data extraction, cleansing, conversion, and migration programs iteratively perfected through go-live.

  • Strategy and selection: Enterprise systems assessment and roadmap; requirements engineering and RFI-based selection through the PARA™ framework’s weighted scoring — must-have coverage, coverage gap, and customization-to-score metrics — with scripted demos and quantified TCO

  • Implementation: Full environment-lifecycle discipline (Pristine → Dev → Test → QA → Approval → Production), master data designed before configuration, data migration scrutinized by someone who has personally done the work, parallel testing before cutover

  • Recovery: Four documented rescues delivered to go-live — a third failed JDE start, a program taken over mid-flight after the prime firm exited, a failed second attempt at a national distributor, and an existing platform two prior firms could not make work

  • Post-go-live optimization: Planning engines, integration rationalization, and the data governance that keeps the platform running as designed

Foundation: 29 JD Edwards EnterpriseOne implementations within 100+ enterprise systems engagements spanning Oracle, SAP, and Microsoft Dynamics.

Proof

  • National pipe distributor (250K SKUs, 18 DCs): Third consulting firm on the second JDE attempt; redesigned the master data taxonomy and architected a Factory Physics SIOP framework — ~99% of manual planning and purchasing execution eliminated

  • Federal military manufacturing contractor: Existing MS Dynamics GP platform rescued after two prior firms failed over 6+ months — Inventory and Purchasing live in under 2 months, federal suspension averted

  • Global 500 manufacturing division: JDE implementation within a full operating model redesign; cycle times from 8+ months to under 3; EBITDA from −20% to +10% after a 20-year history of losses

  • $1.5B agricultural cooperative (12 mills, 6 initiatives over ~3 years): Mill planning from over 3 hours to under 30 minutes; ~90% automation from near-100% manual; retail inventory accuracy from under 50% to ~100%

  • Agricultural chemical manufacturer: Month-end close from over 2 weeks to under 2 hours; railcar demurrage and partial-load returns cut by over 95%

  • PE-backed specialty healthcare MSO (~$200M, 50+ locations): 669+ weighted requirements, 3 enterprise platforms scored, CTO-endorsed NPV/IRR/TCO business case presented to executive leadership

Enterprise Systems Strategy, Implementation & Recovery

ERP, CRM, CPQ, project management, and finance platforms — strategy and selection through implementation and rescue, from someone who has done all three repeatedly.

bottom of page