Enterprise systems create value when the transaction model matches the way the operation actually needs to work.
My ERP, MES, and WMS work has been primarily functional and operational: defining requirements, redesigning workflows, governing master data, connecting systems to shop-floor and warehouse execution, managing implementation risk, and making the resulting system usable across functions.
I approach these programs from the operating model outward. The software matters, but so do BOMs, routings, permissions, data ownership, exception handling, training, traceability, and the decisions people make before and after a transaction reaches the system.
The projects span enterprise transformation, manufacturing execution, product data, warehouse workflows, and implementation recovery.
8 projects represented here
Executive-led transformation of a multi-site medical-product manufacturing operation through an internally governed custom ERP, MES and WMS environment built around the company’s actual processes.
Manufacturing-engineering leadership in a defense environment combining complex production support, customer-facing program recovery work, and a controlled transition from a legacy production system toward Visual Manufacturing ERP/MES.
Functional architecture and operating leadership for a governed product-data backbone connecting product masters, BOMs, routings, engineering history, manufacturing data, and legacy-system migration across regulated operations.
ERP and MES modernization consulting connecting business processes to functional designs, data structures, wireframes, development priorities, and ERP, warehouse, finance, product-data, and mobile workflows.
Customer-facing B2B commerce leadership connecting product catalog, account and address rules, checkout, shipping and payment choices, mobile UX, administrative workflows, release governance, and production ERP order integration.
Across these projects, system success depended less on software selection than on functional architecture: clear business rules, governed data, usable workflows, integration, and ownership after go-live.
3 additional examples connected to ERP, MES & WMS.
Executive infrastructure and continuity leadership spanning servers, networks, wireless and operating devices, backup and recovery controls, incident documentation, administrator knowledge transfer, and communications-service continuity.
A candid ERP implementation-failure and recovery case spanning repeated go-live problems, reimplementation assessment, and lessons carried into later systems strategy.
Cross-functional operating leadership for an international sales and export system connecting customer onboarding, commercial terms, payment controls, production coordination, export documentation, freight, customs, invoicing, exceptions, and role-based training.
manufacturing technology buyers, employers, and transformation teams