
Adopting Out-Of-The-Box (OOTB) enterprise PLM solutions can help streamline processes and enhance efficiency. However, setting clear expectations for both business and IT teams is crucial for a successful implementation. What to expect when investing into a PLM solution? What do we mean by OOTB process or functional adoption? What is actually “in the box” when implementing PLM? Here is how to navigate this balancing act effectively.
While OOTB PLM solutions offer robust features, they may not cover every specific need within an organization. It is essential to conduct a thorough assessment to identify any functionality gaps and determine which missing features are critical to operations. Additionally, where possible, business teams should map their current processes in value streams structured to the capabilities of the OOTB solution, making necessary adjustments to ensure a good fit. It is also a matter of identifying business change implications at an early stage.
Understand the Limitations and Align with Processes
Minimizing customization is key, with an aim for zero customization being ideal, though how this is measured can vary from organization to organization. The focus should be on changing existing organizational processes while setting realistic expectations for controlled configuration and customization. The OOTB solution must be based on the good practices defined by the vendor and integrated into the platform. However, these practices may not be universally applicable; they could be tailored for specific customers or industries and may not align with every organization’s culture, size, operational maturity, or budget for change. There is a continuous need to measure the deviations or gaps between the latest OOTB capabilities and current or future requirements, as simply put, one size won’t fit all.
Past good practices might not directly translate into future good practices; plus, so-called good practices are contextual and not always directly applicable or transferable.
The robustness of people-process-data alignment is highly important for PLM implementation success. Most virtual and digital twin models are data-driven and intersect across multiple user stories and sub-processes. Therefore, modern PLM solutions should focus on data continuity and alignment rather than merely on the capabilities included in the box. By the time the target OOTB solution is deployed and stabilized, there may be one or more additional OOTB iterations to consider.
SaaS Adoption and Its Implications for OOTB Solutions
The rise of Software as a Service (SaaS) has significantly influenced OOTB PLM adoption. SaaS solutions promise rapid deployment and lower upfront costs, making them attractive for organizations looking to implement PLM systems without extensive infrastructure investments. However, SaaS can also introduces limitations in customization and integration. Many SaaS platforms offer predefined features and functionalities, which can restrict the ability to tailor the system to specific organizational needs. In addition, big vendors often lag with their SaaS offering since they mostly target large organizations with complex integrated business capabilities.
Moreover, organizations must consider the continuous evolution of SaaS offerings. As updates and new features are rolled out, there is often little control over how these changes will impact existing processes. Therefore, businesses need to balance the desire for customization with the benefits of sticking to OOTB solutions, carefully evaluating whether the trade-offs align with their strategic objectives.
Realistic Implementation Timelines and Training
Even with quick deployment promises, OOTB solutions require careful planning. Organizations must account for the integration and migration processes, understanding that merging the new system with existing platforms may extend the timeline. It is important to allocate sufficient time, personnel, and budget to support a successful rollout.
Broadly speaking, the PLM platform covers a wide scope which overlap with what one would expect to be covered by an ERP or CRM platform. Like most enterprise platform implementation, even simple technical upgrades might need to be considered as business change initiatives.
Business change and training are vital to maximizing the benefits of new integrated PLM system and processes. Developing tailored training programs that cater to different user roles will facilitate a smoother transition. Additionally, clearly communicating the benefits of the new system helps to alleviate resistance to change, ensuring that all stakeholders understand how the PLM solution can improve their processes.
Measure Success with KPIs and Ongoing Support
Establishing Key Performance Indicators (KPIs) is crucial for evaluating the impact of PLM solution. Focus on tracking key metrics such as improvements in time-to-market and collaboration efficiency. Regular assessments will allow you to continuously review system performance and identify gaps between the latest OOTB PLM capabilities and current or future requirements. Once again, it is important to remember that one size won’t fit all. The IT team will play an instrumental role in providing ongoing support. They should be prepared to address technical challenges by allocating resources to tackle integration issues and ensure that the system runs smoothly post-implementation.
By fostering collaboration between business and IT teams and setting realistic expectations, organizations can effectively navigate the complexities of OOTB PLM adoption. Hence, it is crucial to think “outside of the box” and act quickly when deciding what should be adopted OOTB and what could be configured or customized further to meet expected business needs and deployment timelines for benefit realization. The more time and effort spent on value delivery to the business, the less relevant the OOTB versus customization debate becomes, unlocking the full potential of end-to-end PLM solutions and transforming product development to enhance overall efficiency. This reinforces the need for a holistic approach to PLM adoption, recognizing its far-reaching implications across the organization.
Ps. While most of the above can apply to any enterprise digital solution and is not limited to PLM tools and processed, these principles and considerations perhaps more strongly apply to complex data and integrated workflows.
What are your thoughts?
Disclaimer: articles and thoughts published on v+d do not necessarily represent the views of the company, but solely the views or interpretations of the author(s); reviews, insights and mentions of publications, products, or services do neither constitute endorsement, nor recommendations for purchase or adoption.