Business Process Leader (Erp)

Basic Qualifications:

• Bachelor's degree from an accredited institution.
• Minimum 7 years of experience working with ERP systems, including at least 5 years in a manufacturing environment.
• Minimum 3 years leading change-management initiatives, business-process transformation, or multi-site ERP adoption efforts.
• Demonstrated ability to coordinate cross-functional teams and influence stakeholders without direct authority.
• Strong understanding of manufacturing processes (production, supply chain, inventory, procurement, finance).
• Excellent facilitation, communication, analytical, and organizational skills.
• Ability to travel to domestic (and occasional international) manufacturing locations as required.
• Must be legally authorized to work in the United States; visa sponsorship is not available.
• Position requires access to export-controlled items; employment is conditioned on the ability to lawfully obtain such access.

Preferred Qualifications:

• Bachelor's or Master's degree in Engineering, Supply Chain, Business Administration, Operations, or related field.
• 10+ years of ERP experience in manufacturing; 5+ years leading process transformation or change initiatives.
• Experience with multi-site manufacturing ERP rollouts.
• Familiarity with SAP, Oracle, Microsoft Dynamics 365, Infor, Epicor, or similar platforms.
• PMP, Lean Six Sigma, Prosci, or Agile certification.
• Background in aerospace, industrial, or engineered products industries.

The ERP Implementation Lead is the business-side owner of process standardization, organizational change, and adoption for the enterprise-wide rollout of the pilot-validated ERP solution across multiple manufacturing locations. Working in close partnership with IT, this role ensures each site successfully transitions to the standardized business processes and realizes the intended operational and financial benefits. Post-deployment, the role owns the continuous-improvement agenda for the ERP platform from a business-process and value perspective.

Key Responsibilities:

Business Process Transformation & Standardization

• Lead the evaluation, standardization, and redesign of manufacturing and supporting business processes to align with ERP best practices.
• Ensure consistent processes are deployed across all sites while identifying and resolving legitimate site-specific operational needs.
• Balance business requirements against standard ERP functionality and minimize unnecessary customization.
• Drive data governance, master-data quality, and process discipline in partnership with site and functional leaders.
• Capture lessons learned from the pilot and each subsequent site to refine the enterprise process template, training materials, and deployment playbooks.

Organizational Change Management & Adoption

• Build strong partnerships with site leadership and functional leaders.
• Own communication, stakeholder engagement, readiness assessments, and change-management activities for each deployment.
• Coordinate user training and drive organizational acceptance of new processes and system capabilities.
• Support cutover and go-live from a business-readiness and adoption perspective (IT remains accountable for technical cutover and system readiness).

Continuous Improvement & Value Realization

• After each go-live, lead ongoing process optimization and system utilization improvements.
• Prioritize business-driven enhancement requests and continuous-improvement initiatives.
• Partner with business leaders to define future process capabilities and contribute the business perspective to the ERP roadmap.
• Establish and monitor key performance metrics that measure ERP effectiveness and process compliance.
• Maintain governance around process changes that impact the enterprise template.

Cross-Functional Coordination

• Serve as the primary business liaison to the IT-led deployment team, external implementation partners, and site leadership.
• Align business priorities, process decisions, and change activities with the IT-owned deployment schedule and technical plan.
• Escalate business-side risks, dependencies, and issues that could impact timeline or adoption.