{"id":8103,"date":"2020-04-20T08:00:11","date_gmt":"2020-04-20T06:00:11","guid":{"rendered":"https:\/\/www.specpage.com\/?p=8103"},"modified":"2020-04-20T10:25:40","modified_gmt":"2020-04-20T08:25:40","slug":"remote-implementation-plm-software","status":"publish","type":"post","link":"https:\/\/www.specpage.com\/remote-implementation-plm-software\/","title":{"rendered":"How to Remotely Implement PLM Software"},"content":{"rendered":"
A remote implementation of product lifecycle management<\/a> (PLM) software might sound like a stretch, when in fact, SpecPage has been offering this for years.<\/p>\n While the majority of our customers have opted for remote implementations for quite some time, now all of our new projects are utilizing remote implementations due to the unprecedented work-from-home orders in place to halt the spread of the coronavirus. Even after the end of this crisis, we\u2019ll continue to implement PLM systems remotely.<\/p>\n In this post, we\u2019ll explore why we advocate for remote implementation and detail best practices for making it successful.<\/p>\n Before we move forward, here\u2019s a quick introduction to PLM software:<\/p>\n PLM software<\/a> helps manufacturers optimize, track, and manage all phases of new product development.<\/p>\n When you move from outdated solutions and manual processes like emails and spreadsheets to a cloud-hosted, secure PLM you experience the following benefits:<\/p>\n It can be difficult to imagine such a large change happening remotely. Food manufacturing is so complex. You need to make the software fit your actual workflows and stage gates, and then you need to get the right employees onboarded and using the software correctly and consistently.<\/p>\n Essentially, you need to move your master data management<\/a> for packaging and ingredients from a manual or outdated process to one that is optimized and securely managed in the cloud.<\/p>\n So how is it possible to do this remotely?<\/p>\n There are several reasons why:<\/p>\n If a PLM solution cannot offer remote implementation this usually comes down to two main reasons. They are probably not cloud-ready and can\u2019t offer secure remote access using encryption and multifactor authentication. They also likely do not have industry-specific functionality which reduces the need for long, complex in-person meetings with the goal of customizing the software.<\/p>\n When you choose a cloud-based PLM with features that match your industry\u2019s needs, then remote implementation should be not only possible but preferable in most cases.<\/p>\n Around the world, across all industries, enterprises have spent the past decade moving from on-premise to SaaS solutions, which are hosted in the cloud by the software provider and can be accessed remotely on any device.<\/p>\n Depending on the nature of the software and the industry, there are different levels of security. Some vendors encrypt all sensitive data. Some require two-factor authentication or multifactor authentication (or allow their customers to set requirements).<\/p>\n By providing secure, remote access you make it possible for employees to work remotely. The global coronavirus lockdowns have shown us that today\u2019s innovative workers need to be able to work remotely at the drop of the hat, with no notice.<\/p>\n We\u2019ve seen that, aside from the demand for remote work flexibility, there can be health and safety requirements. Governments can shut non-essential work down. Businesses need to be able to enable their employees to keep innovating.<\/p>\n For example, with a remote PLM in place, food manufacturers can continue to perfect formulas and track ingredient certifications from suppliers. Similarly, ingredients manufacturers can continue to pitch their products.<\/p>\n Fully remote implementation<\/a> (remote-access software with no on-premise hosting and no on-site vendor installation) has gained a lot of popularity with many types of B2B software. Not only does this typically lower the costs, but more importantly it helps you move faster. Why sit around in meetings and do factory tours if that\u2019s even necessary?<\/p>\n For a remote implementation of PLM software, these are the typical stages:<\/p>\n The first step is for the vendor to understand more about the manufacturer\u2019s needs. What type of products are created, what special regulations are in place, what countries the manufacturer sources ingredients from, and what countries products are shipped to. The vendor will also need to understand what master data management systems are already in place, and at what speed the company currently innovates new products.<\/p>\n After a general understanding of the manufacturer, the vendor will then need to gather information on the product development workflows used and the unique nature of the products being manufactured.<\/p>\n With a deeper understanding of the current manufacturing processes and the products under both development and active manufacturing, the vendor can then make any needed configurations to the software. This typically involves the customization of workflows to fit the manufacturer\u2019s exact process.<\/p>\n As mentioned elsewhere in this article, when the PLM is tailored toward the industry then this process goes much quicker than when using an industry-agnostic PLM.<\/p>\n Once the PLM is configured to the manufacturer\u2019s needs, then the vendor needs to help onboard the quality and innovation<\/a> executives and staff. These employees can vet the workflows and test them out before rolling out the solution to others.<\/p>\n When it\u2019s time to rollout the PLM, the heads of the project may decide to roll it out with one product that is currently under development. For a formula that\u2019s in its early stages, it can be easier to start using a new system for tracking supplier information and calculating product compliance than to start on a product that is nearing the final stages of development.<\/p>\n Next, the vendor will want to collect feedback from the employees who used the PLM during the initial implementation. Adjustments to the workflows can be made in order to keep the PLM system as close to real life manufacturing processes as possible.<\/p>\n With any readjustments complete, it\u2019s time to rollout the PLM to the entire manufacturing facility. The rollout might take place in stages by product type, process, or team. With vendor resources such as live virtual trainings, on-demand virtual trainings, and one-on-one support via phone, video call, and email, all staff can onboard to the new system smoothly.<\/p>\n The following best practices will help ensure a successful remote rollout of your new PLM system.<\/p>\n To get the most amount of value from a PLM system and reduce implementation effort, we recommend that companies work with a software vendor that specializes in their industry. This means that the workflow templates and stage gates are ready to go and require minimal customization. For example, SpecPage<\/a> has specialized its software products for food manufacturers for 20 years, meaning that much of the implementation hassle is already done, simply because the product is already tailored for the industry.<\/p>\n Consider who you should have on your implementation team. This might consist of:<\/p>\n It\u2019s important to involve the end users in implementation so you can setup the right workflows, test them, and reiterate on them. Of course, you don\u2019t need to include entire departments, just a few representatives of each user type.<\/p>\n Before rolling out the PLM to your entire staff, make sure they understand the reason for the digitization. Why are cloud-based processes better than manual ones? Help them to understand that speed to market increases revenue, which positively impacts the security of everyone\u2019s jobs.<\/p>\n Your PLM provider should have plenty of materials and experience to share with training. Nevertheless, some leg work will be required to put it into action. They may host some trainings or provide access to guidebooks and video tutorials. You will need to work with department heads and managers to make sure they understand when the implementation is occurring and what they need to do when.<\/p>\n An action plan would include the timeline for reviewing the training materials, starting to utilize the software, and finally, switching over to the software completely. As part of the training, employees should also be made aware of where they can turn for support.<\/p>\n To learn more about how to improve speed-to-market and save time on compliance documentation, visit SpecPage<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" A remote implementation of product lifecycle management (PLM) software might sound like a stretch, when in fact, SpecPage has been offering this for years.<\/p>\n","protected":false},"author":2,"featured_media":8104,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_FSMCFIC_featured_image_caption":"","_FSMCFIC_featured_image_nocaption":null,"_FSMCFIC_featured_image_hide":null},"categories":[2],"tags":[99,101,100],"yoast_head":"\nIntroduction to PLM software<\/h2>\n
\n
Why PLM software doesn\u2019t require onsite implementation<\/h2>\n
\n
Why don\u2019t all PLM providers allow remote implementation?<\/h2>\n
Why choose a PLM with remote access?<\/h2>\n
The remote PLM implementation process<\/h2>\n
Define requirements<\/h3>\n
Gather information for workflows and product structure<\/h3>\n
PLM configuration<\/h3>\n
Initial user training<\/h3>\n
Partial implementation<\/h3>\n
Workflow readjustments<\/h3>\n
Ramp up and additional user training<\/h3>\n
How to increase the implementation success and reduce rollout time<\/h2>\n
Work with a PLM provider that specializes in your industry<\/h3>\n
Organize an implementation team<\/h3>\n
\n
Communicate the reason for the PLM implementation to employees<\/h3>\n
Develop and execute a training plan<\/h3>\n