PLM Strategy, Governance & Roadmap
- Business Ownership: Own PLM as a cross-functional business program, ensuring it supports company priorities across Engineering, Manufacturing, Supply Chain, Quality, and Field Service.
- Roadmap Development: Define and maintain the PLM roadmap, aligning system capabilities and process improvements to business needs, scale requirements, and product lifecycle priorities.
- Leadership Alignment: Drive alignment across functional leaders on priorities, decisions, process standards, and investment needs related to PLM and connected engineering systems ( Colab, SolidWorks, Altium 365 ).
- Governance: Establish decision-making forums, ownership models, and governance processes for PLM enhancements, master data standards, change workflows, and business process adoption.
Cross-Functional Process & Execution Leadership - Process Design: Partner with stakeholders to design and improve end-to-end lifecycle processes spanning eBOM, mBOM, Service BOM, engineering change management, configuration management, and traceability.
- Program Prioritization: Translate business needs into sequenced workstreams, balancing short-term operational issues with longer-term platform and process maturity goals.
- Change Management: Lead organizational adoption of new PLM workflows, standards, and ways of working; ensure the right teams are engaged early and that changes are durable.
- Gap Identification: Assess process, system, and resource gaps that limit PLM effectiveness, and recommend staffing, workflow, or tooling changes needed to close them.
PLM Systems & Business Value Delivery - Value Realization: Define success metrics and ensure PLM investments are improving data quality, process efficiency, traceability, change execution, and cross-functional visibility.
- System Partnership: Work closely with the PLM technical lead to translate business priorities into system requirements, feature releases, enhancements, and integration needs.
- Connected Systems Alignment: Help drive alignment across PLM, ERP, WMS, MES, and Salesforce FSM or other downstream systems that depend on accurate product and configuration data.
- Requirements Definition: Write clear business requirements, user stories, and operating needs for developers, administrators, and implementation partners.
Stakeholder Enablement & Operating Rhythm - Adoption & Training: Support stakeholder readiness, communication, and training for PLM process updates, new capabilities, and role expectations.
- Issue Resolution: Surface and resolve cross-functional blockers that impact data quality, execution speed, system usage, or business outcomes.
- Operating Cadence: Run a clear operating rhythm for roadmap reviews, prioritization, business requirement intake, release readiness, and post-launch adoption follow-through.