Community Tip - Need to share some code when posting a question or reply? Make sure to use the "Insert code sample" menu option. Learn more! X
Dax,
Do you have a good understanding of your user community? Have the WC users be broken down into different groups, depending on their roles and access they have to the functionality in WC PDMLink and ProjectLink? If you have already done this great, if not suggest to perform this analysis.
Also, have your current business and engineering processes already been reviewed and changed to use any of the new WC functionality in WC 9.1? If yes, great, if no, suggest your organization look into this before creating training material.
Once you have these grouping and have processes defined, you will be able to identify the training material requirements for each of these groups. The most effective training material for users is training material using business data and scenarios the WC users use to perform their work in PDMLink and ProjectLink. Here we are speaking about custom training material, which takes time and budget to create, but we have found this to be the most effective means to train users how to perform their work in Windchill.
In conjunction with this custom training material, suggest you use OOTB training to supplement this training to teach users how to search for their data in PDMLink and ProjectLink, and how to interact with WC functionality, such as discussions, assignments, and user preferences. You do not want to re-create the “Wheel”, so I would not recommend you create any custom training material to teach OOTB WC functionality.
My current organization used this methodology to create custom training material for DELL, BOEING and other customers.
I have done a lot of the same things Mike mentions in his post, but have not done anything with a Wiki.
So what Wiki software do you reccommend?
What should I do to get started using Wiki's?
-marc
I agree with all that the PTC/U training is too generic. People don't want to know "how to check in a document", they want to know how to use the system to to their jobs. That's where the use cases and examples come in. When we did our initial 7.0 deployment, we used PTC/U for the Pro/E functionality training only, and developed custom training on the concepts of PLM (i.e. what is a lifecycle), the change process and use cases. The custom training was provided in an instructor led environment. It was a lot of work, and we found that many of the users just didn't get it and required retraining a few times. One of the biggest complaints with that training was that they wanted "hands on" training so they could actually try it in the system, not just sit and watch a powerpoint. Hands-on training is time-consuming to manage however... you have to have a training environment available, and you need to have data available for people to test with. Then you need to refresh that data or the environment between training sessions so that the next group can run through the same activities the previous group did.
We recorded some of the sessions so that they would be available to new users who were hired into the company later on. That worked ok.
For our upgrade from 7.0 to 9.1, we conducted "delta" training for the existing users. We have a corporate training group, but they just helped us to coordinate and plan, they didn't actually deliver the training. We identified SMEs for various subject areas, and they developed the training materials and then delivered the classes. The "delta" focused on the differences between how you did something in 7.0 and how you now do it in 9.1... no need to retrain on the basics. That appeared to work well. Now we are looking at deploying more sites with brand new users, and will have to undertake the whole process of a full training program again. PTC had proposed to customize some of their PTC/U classes to be specific to our processes. This sounds good, but the management here is of the opinion that they will still involve SME time since they need to learn our processes, and this is not cheap to do.
As for the wiki, I think it is a great idea in concept, but I question how effective it will be in practice. We created a sharepoint site dedicated to Windchill support and training where we made available the recorded training sessions, cheat sheets on particular functionality, a FAQ list, and areas where users could ask questions, discuss functionality or . While users go there occasionally for a cheat sheet, we find that this site is rarely used, and not a single user has contributed any content. I suppose it may be a function of the culture of your organization, but that approach here has been relatively unsuccessful.
Regards,
Robert M. Priest, PE, PMP
Engineering Manager
STERIS Corporation
I have to agree iwth you Robert about user involvement. In my experience, at a couple of different companies, most users don't have the time or inclination to add to the content. Perhaps they feel that it is "not their job".
After looking at several different Wiki's, I think that I am going to leave the best practice guides and training material in Windchill in a specific library set up for the materials. I don't think a wiki gives me any additional capability that I will take advantage of over Windchill.
Plus that way we are "eating our own dogfood" so to speak. *woof*
-marc