I just wanted to make a comment on supporting the new system that you and your team have worked so hard to supply for your company. When developing a new system, make sure that you have the support people separated from the developing people. The reason why this is needed is because, unless it is a show stopper, the developing people will be bombarded with new requests to improve the system and they would not have enough time to actually develop instead of fire fight. The company that I am with has their developers also do the support for our implementation. This causes problems for our developing time line and our support reaction time.
Many other companies who implement a system like this already has this separated which keeps them on track for implementation and support.
PLM "Why" Flash Video
Here is a flash that I found that really shows the PLM vision and goal.
Click here to view the flash video of why to use PLM. When I came across this, I thought it was the best way to show the benefits of why to have a completely integrated system.
Click here to view the flash video of why to use PLM. When I came across this, I thought it was the best way to show the benefits of why to have a completely integrated system.
How do we impact everyone?
Part of implementing a new system, you have to know how you are going to impact other people with the new system. If you are going to be working with a tool which is going to "Save" the company. You need to make sure that everyone who is going to be using it is fully trained within the tool. Besides getting the initial training, they also will need to get update training and best practices training. The reason why you need to train best practices to the users is to make them as efficient and comfortable with the new system as much as possible.
What happens when people are frustrated with a tool that they need to use to do their job?
They will adapt another system, tool, process to make it work for them. If you are a company that spend a lot of many cleaning up processes and making sure people were trained to use the system, you are not going to want the user community creating their own Frankenstein just so they can get their job done. Training, listening, training, listening, and communicating the new system and processes to the company is very important.
If you are a company that is implementing a new process and keeping or minimizing system tools. Then you need to do the exact same thing that I stated above. Training, communicating, and reviewing best practices are key to a successfully implementation of a completely integrated product life-cycle management tool.
What happens when people are frustrated with a tool that they need to use to do their job?
They will adapt another system, tool, process to make it work for them. If you are a company that spend a lot of many cleaning up processes and making sure people were trained to use the system, you are not going to want the user community creating their own Frankenstein just so they can get their job done. Training, listening, training, listening, and communicating the new system and processes to the company is very important.
If you are a company that is implementing a new process and keeping or minimizing system tools. Then you need to do the exact same thing that I stated above. Training, communicating, and reviewing best practices are key to a successfully implementation of a completely integrated product life-cycle management tool.
Subscribe to:
Posts (Atom)