PDMGuru

Introduction I wanted to write a paper on what to do after an initial (hopefully successful) PLM project. Clearly you want to build on what was already done and hopefully you developed a vision of multiple phases when you pitched the original PLM suggestions to the senior management team. It is critical to have a good multi-phase plan to deploy the technology in your business. Planning If you already have a multi-phase plan you should review this and see if it still makes sense. It is a good time to revisit your vision and thoughts and refine them. I'll touch on this in the next section. As with all PLM project planning you should insure that you are delivering ROI and also solving real business problems, not just perceived ones. You should do all the due diligence you did in the initial project (and more) since you do not want to break what was already accomplished! Building on initial project Hopefully your initial deployment went well. It is likely that you

Introduction I wanted to write a short article on the integration between ERP and PLM systems. I feel this topic does not get enough discussion and there are some considerations you need to make on what to do and how to be successful. This topic should be read in parallel with an upcoming paper on bill of material management. Why integrate PLM and ERP So why should you integrate. In the next couple of sections I'll cover pros and cons, but before I do this some initial thoughts. Integrating ERP and PLM should not be taken lightly. It is the endpoint of the value proposition of a PLM implementation. It fully completes the circle of the product development; linking design and manufacturing. As such it holds many benefits including building what you design and designing what you build. To successfully accomplish this needs a strong arm and a lot of concessions from the two major players in the business. Everyone will need to give up something if the implementation is t

Overview I wanted to discuss some ideas on PLM Projects and Upgrades that I've seen over the years. I've been involved in upgrades as a developer, a consultant and even as an interested observer watching customers do their own projects/upgrades. In house or consultant? A number of factors will influence the decision of whether to use in-house resources or consultants (either vendor or independent/partner). The risk sharing of using a consultant and also the previous experience of the consultants can be very helpful. It's also helpful if your team does not have the necessary skills. For a customer who has lots of experience and proven success you would probably choose to do things yourself, unless it is a new area where you do not have experience. Cost versus risk always comes into play in these decisions too; a vendor led project can be costly, but (usually) the risks of a vendor led activity are less since if things are not straightforward they will have mor

Introduction I thought I'd like to put some ideas down to help people be successful in their PLM implementations. I've come up with some suggestions I've seen that have helped me in the past, also some of the unsuccessful implementations where using these approaches would have helped. Voice of the customer - insure buy in Making sure that there is adequate involvement in the process is key to any PLM implementation. There are going to be many changes to the fundamental way people do their jobs in an implementation and keeping everyone on board is key to being successful. Remember that all users of the system are effectively customers and you need their buy in for the ultimate success of the venture. All through implementation I've seen many implementations that start off including people from various departments for example during the definition of scope and requirements. But this is just the beginning. If this is the last contact with end users the project

Introduction I thought it would be interesting to look at why people and companies might consider changing PLM tool. You might not think it is usual but it can happen for a number of reasons. I'd like to make some comments and suggestions on how to do this. Why change Choice or necessity? Choice It might be that you realize that you made a mistake in choosing the current tool and/or it might not be fit for purpose. Clearly this is a big step and I would always suggest trying to avoid this. I'd recommend working with the current vendor to see if the situation can be remedied. It is very likely that your company has already made significant investments in the tool and training so to throw all this away should be avoided at all cost. I think most vendors would do all they could to help you in sorting out problems with the current system. It might be that there are irreconcilable issues between you and the vendor and their tool and you decide to move to another syst

Introduction I wanted to develop a white-paper with some comments about the small and medium sized business (SMB) view of PLM. The SMB space has some specific PLM offerings including ones from Siemens and PTC, but I wanted to discuss some topics I feel are pertinent to all SMB implementations . What is SMB? Defining an SMB is not easy; I would typify them by saying 1. They are usually privately owned companies 2. Often are suppliers to larger companies 3. Have small numbers of engineers who work on multiple projects and tend to be flexible in how they work 4. They probably manufacture things themselves Why implement PLM at SMBs? Understand problems to solve It is important to understand why you want to implement PLM at your business, there is a considerable investment in time and money to achieve this so insure you have a good problem statement. The most pressing issues for SMBs tend to be vaulting CAD data, managing change, bill of material management and consolidat

Introduction I decided to write this paper based on a couple of scary experiences I've had over my professional life. It seems very strange to me how many companies take an almost flippant approach to planning for disasters. Consider September 11 th or Hurricana Katrina or Superstorm Sandy. If such an event struck you data-center would your company be able to recover? Understanding the value of your engineering data All data in a company is important and it is critical to back it up and make sure you can recover from unplanned issues; but consider the loss of your engineering data. In many companies there is no company without this data! It still surprises me that senior people in companies don't realize that without the intellectual property (IP) of the engineering drawings, bill of materials, NC toolpaths, material specs, process sheets etc. the company could quickly go out of business. So that is why people invest in PLM systems etc. right? Of course, but s

Overview Over the past few months/years the main focus of discussions in the PLM industry seem to have centered on the “Cloud”. I thought I'd take a few minutes to provide my commentary/overview on this emerging technology with a few pros and cons to help people considering a move to the cloud. Most if not all PLM companies are now offering some kind of web/cloud/hosted offering – here is a non exhaustive list of the ones I found with some cursory googling. Siemens with AWS (Amazon Web Services) PTC Cloud services Autocad PLM360 Oracle Agile PLM in the cloud Arena Solutions Aras Cloud Oleg's BeyondPLM site also has an excellent (as usual!) write-up here... http://beyondplm.com/2014/09/19/what-cloud-plm-cannot-do-for-you/ What is it? I would define CloudPLM as accessing your PLM solution via a third party (host) where the host provides standard hosting options e.g. web server farms etc, but with the addition of applicati