Director of ERP Implementation and Business Enablement

Position Summary The Program Director owns ERP implementations across Orion’s operating companies from readiness assessment through configuration, testing, training, go-live, stabilization, and transition to support. This is a hands-on delivery and accountability role—not solely a project-management position. The Program Director is directly responsible for configuring the system according to Orion’s approved framework, controlling configuration changes, validating business processes and migrated data, preparing users, resolving delivery barriers, and operating Orion’s implementation governance model. The Program Director is accountable for implementation outcomes and business continuity, including accurate system performance and uninterrupted revenue, billing, cash collection, payroll, purchasing, project execution, WIP reporting, and financial close. When an issue arises, the Program Director identifies the root cause, establishes the resolution path, mobilizes the right resources, and drives the issue through validated closure. Key Responsibilities Program and Governance Leadership · Own the implementation strategy and execution plan, including milestones, deliverables, risks, decisions, dependencies, budget, resources, and measurable business outcomes. · Run Orion’s tollgate governance model and enforce entry and exit criteria. · Lead tollgate reviews, steering committees, and evidence-based go/no-go decisions; bring forward decisions requiring executive authority with a recommended course of action. · Maintain a current, decision-ready record of risks, issues, decisions, actions, approvals, owners, due dates, and implementation evidence. · Direct and align OpCo leaders, functional teams, technical resources, vendors, and contractors to deliver the approved implementation outcomes. · Identify risks and delivery barriers early, determine root cause, implement corrective action, and drive recovery plans until readiness and performance return to plan. · Own the quality of tollgate evidence and ensure approvals reflect demonstrated operational readiness—not administrative completion. System Configuration and Change Control · Configure the ERP according to Orion’s approved global framework and design standards. · Own the translation of business requirements into complete, accurate, and testable system configurations. · Distinguish between Orion standards, OpCo-specific inputs, and requests requiring deviation approval. · Maintain configuration workbooks, requirements, decisions, test evidence, and approvals. · Control all configuration changes from request and impact assessment through approval, implementation, testing, and validated closure. · Assess each change for operational, financial, integration, security, and control impacts. · Secure required approvals and verify readiness before introducing changes into test or production environments. · Maintain version control and a complete audit trail of approved, rejected, deferred, and implemented changes. · Identify, prioritize, and implement opportunities to standardize or automate configuration within the approved Orion framework. Testing and Data Validation · Develop test plans, scripts, expected results, completion criteria, and supporting documentation. · Personally test system configuration and critical business processes. · Lead functional, integration, end-to-end, security, user acceptance, regression, and cutover testing. · Validate complete transaction lifecycles across order-to-cash, procure-to-pay, payroll, project accounting, service, WIP, and financial close. · Confirm the system produces accurate calculations, accounting entries, approvals, and reports. · Own defect resolution: establish priority and accountability, drive root-cause correction, retest the solution, and secure business validation before closure. · Direct data owners and migration resources through complete validation of converted data, resolving reconciliation gaps before approval. · Reconcile migrated data to legacy systems, job-cost reports, WIP schedules, subledgers, trial balances, and the general ledger. · Validate customers, vendors, employees, projects, contracts, open receivables, payables, purchase orders, commitments, and other in-scope transactions. · Own readiness for formal business approval and do not advance to go-live until testing, data validation, and material defects meet approved acceptance criteria. Financial and Operational Continuity · Establish baseline financial and operational metrics before go-live. · Build continuity controls, thresholds, contingency plans, decision rights, and predefined response actions into each implementation. · Monitor revenue, billing, cash collection, purchasing, payroll, job costing, WIP, project margins, service activity, and financial close. · Compare post-go-live activity to historical performance, forecasts, and expected transaction volumes. · Investigate material variances, determine root cause across configuration, data, integrations, processes, training, adoption, or business conditions, and drive corrective action through verified resolution. · Immediately take ownership of risks to revenue, cash, payroll, customer service, or financial reporting; contain the impact, assign and drive corrective actions, engage the required decision-makers, and verify resolution. · Own the recommendation to go live and exit hypercare, supported by evidence that critical processes operate accurately, material issues are resolved, and the business can sustain performance without implementation-team dependency. Training, Adoption, and Business Performance · Deliver role-based training for key users, managers, and end users on the Orion standard design · Create process documentation, standard operating procedures, and user guides when needed. · Confirm users can perform critical transactions before go-live. · Lead hands-on supp