How much time would an administrator spend on pdm implementation and
migration during a work day/week?
I took the class. That was a week.
Migration took 3 attempts. 2 were user errored.
3rd took a weekend with success. I would say if you have a good process, understanding of workflow, and on how to do it another week including that weekend.
Estimated, two weeks if you know you know you know..
Talk to your VAR as there is a tool out there for importing folder structure that will add an unestimatable amount of time if you don't - IMO.
back in 2011 it took us about 6 months.
it will depend greatly on your scope - how involved your workflow(s) are (and how much testing you feel is required), how big is your dataset (#number and types of files - and just the current revs, or do you need to import history as well), and how "clean" your data is.
That's a good question and I'm guessing you mean the everyday duties of an Admin?
I'm wanting to know as well.
We follow the priciple of 5 hours per user but that can all change due to the complexity of the implementation.
A better option is to rather use a Scope Of Work and start with 10 hours for a simple install and set up and For each line item to be customized, for example, workflow, variables and template add 2h per item.
Our migration from Windchill and an external PDF location to PDM took 6 months. We had approximately 100k Creo files with multiple versions, and 60k PDF versioned files. The 6 months doesn't include the vault configuration time. Total implementation time took 15 months.
I dedicated my entire schedule to the implementation and migration, and am still 100% dedicated 4 months post migration.
Another variable that will make a huge amount of difference is, how many users are you working with along with how many files are you migrating. 3 users and a couple years of files will be vastly different than 50 users and 20 years of files.
Then comes the "how clean are your files and how clean do you intend to keep them?" Do you have 20 different parts with the same name hiding in your archives? Are you going to set the vault to restrict to one instance of each name? (you should regardless the amount of time it takes to clean things up).
The last place I worked at implemented PDM and it took about 6 months of heavy, but not full time, work. Then it was 4-5 hours a week with 16 users.
The direct answer to the question ask would be 8/40.
A better answer to the question is not really possible outside of a generalized guessimate, because not enough information was provided. I see that you are implementing SWPDM and that you have data to migrate.
What I don't know is:
I have completed migrations from Workgroup PDM to SWPDM in anywhere from a couple weeks to over a year working on them 4 to 8 hours a day. Other types of immplementations have been in that range as well. It all depends on the specifics of the project.
As Paul indicated PDM Data Migrations can be pretty complicated and time consuming. There are several factors that will determine time needed.
There are a lot more factors but those have a big impact on time required. We have also completed migration that are fairly quick (just a couple days) to ones that take weeks & even months to complete.
SOLIDWORKS & PDM Admin/Implementation Specialist
Our migration was suppose to be 2 weeks when I was the admin.
Since corporate took over and took it over from me, it has now been 1-3/4 years.
I gave up trying to convince corporate to hurry up.
I have read the answers and I agree with a lot of what has been said. The situation I have is I was only a part time Admin for 7-1/2 years. I just put out fires then. Before I came there were 4 administrators in less than 3 years. Now I am cleaning up what the last 4 administrators did. I have changed the workflows available. I have changed the revision scheme. We have separated one of our divisions and I had to redo their revision scheme to numeric revisions.
On a regular basis I work 4 hours a day or more on cleaning up the files and drawing structure. We have approximately 50 modifiers, 15 contributors and over 100 viewers, so there is always a few things to do. Orientation is the most important item you can have for a new employee.
In addition to how many files, It also depends on the scope of your implementation, how much data you have, where you get it from, how you prepare it, and have your VAR do for you.
In my case, we had the VAR migrate the files and the data into PDM, but I prepared and cleaned up all the data that came from different legacy systems (drawing history, ECRs, etc.). We migrated all of our legacy system data to virtual documents. CAD files were migrated into PDM, to "Migration" sub-folders, then I left it to the Design Engineers to move them to the proper CAD data folders and finish the migration cleanup as they needed the files. I wasn't about to waste my time cleaning up their messes. The migration cleanup involves removing duplicate or similarly named models for the same part. If I recall correctly, it took my VAR about 1 week to migrate everything in. We did that during a holiday week at the end of the year. The migration is on-going as needed, but I don't spend any time on it.
Implementation took a long time (about 1.5 yrs) testing vault configurations before we migrated and went live, but we had about 80 years of data and files to migrate I wanted to make sure we got it 95% right the first time. I didn't want to get stuck with a mediocre system that I could not change for whatever reason.
Now that we've stabilized, I spend almost no time on maintenance. There are occasional issues, but they are the exception rather than the rule. Almost every time there's a problem, I find it is user error, and they can fix it themselves.
Retrieving data ...