Hi,
Can somebody over there tell me in detail what are the responsibilities of a PDMS Administrator and what will going to happen if he is not there in a company or if a company is not having any PDMS Admin.
[QUOTE=veenuraj]Hi,
Can somebody over there tell me in detail what are the responsibilities of a PDMS Administrator and what will going to happen if he is not there in a company or if a company is not having any PDMS Admin.
BR
veenuraj
That is a good question.
I think the PDMS admin's responsiblity is:
1. set up projects
2. maintain software versions, look for upgrade on projects if new features warrant an upgrade.
3. help daily project needs, such as Cats/spec issues, iso debugging, draft setup, database maintainence.
4. interface with company IT to ensure Global runs properly
5. look for work process improvements and write / help spec out PML automation.
6. Anything your boss wants done.
If there is no PDMS admin, well, if the project is setup properly, it can run on autopilot for a while until something happens and it crashes. And then the design manager will wonder why the MTO is wrong and why the draft drawings are corrupted. And then they scramble to find someone to clean up the mess, pay for a lot money for it.
That is my experience here in US. However there are a few companies that tries to keep their "core competence" team and give them a "cushy" job being "PDMS Czars".
The rate for PDMS designer is at high $50s in Houston, admins - I do not have data, but it heard numbers north of $60s.
So if you do not make that much in US now, it is time to make a visit with your boss and explain the "supply and demand" theory.
I just spoke to my boss yesterday about my responsibilities and they are what de_ding said plus
- being familiar with and understanding design codes and standards for all disciplines(ANSI, API, AISC, ASTM)
- being willing to work with all peoples and disciplines (people skeells)
- being willing to crank out draft drawings on a project if the need arises (which it does!)
- keeping the company up with the latest software and hardware requirements, and looking at tools beyond just AVEVA products (Navisworks, WalkInside)
- creating training classes and schedules to bring the rest of the team up to speed, whether it be new users to PDMS, or a quick short class on the newer applications in PDMS 11.6.sp2 & sp3
- maintain the pdms master catalog, and be sure that the elements in that catalog are checked and backchecked by very particular checkers, to ENSURE that the company catalog is correct.
- to represent to company in a professional manner when discussing PDMS procedures with other companies and clients
- to create presentations and speak at company meetings on the benefits and drawbacks of using PDMS, and to speak about the accomplishments and disasters encountered while using this software
- to know that there is no task below me, being PDMS Admin does not mean that people work for me, but that I work for people, the PDMS administrator should be a SERVANT to the design team. and that is what I strive to be. I have worked for administrators that refused to do thier own cats and specs, that wouldn't touch draft if thier life depended on it, that couldn't tell you if a 2X1.1/2 PBE SWAGE was male or female (true story) and couldn't place that component in the model. Sure, they could add users to a project, yeah they could write a collection macro, but they didn't know what to do with that collection when they got it. I am a USER first and an ADMIN second. Like DE_DING said, projects should run on autopilot, and while they are on autopilot the admin guy should be useful at something besides waiting to set up the next job. It was made very clear to me by my boss that not only is it ok if I get involved in projects at the engineering and design levels, he fully EXPECTS me to be involved at these levels. You can be a better admin person if you see yourself as a benevolent server to your team, not as some untouchable jerk that sits in thier office all day mulling over pml code and trying to think of the next totally useless tool to implement.
[QUOTE=PDMSGURU]
- to know that there is no task below me, being PDMS Admin does not mean that people work for me, but that I work for people, the PDMS administrator should be a SERVANT to the design team. and that is what I strive to be. I have worked for administrators that refused to do thier own cats and specs, that wouldn't touch draft if thier life depended on it, that couldn't tell you if a 2X1.1/2 PBE SWAGE was male or female (true story) and couldn't place that component in the model. Sure, they could add users to a project, yeah they could write a collection macro, but they didn't know what to do with that collection when they got it. I am a USER first and an ADMIN second. Like DE_DING said, projects should run on autopilot, and while they are on autopilot the admin guy should be useful at something besides waiting to set up the next job. It was made very clear to me by my boss that not only is it ok if I get involved in projects at the engineering and design levels, he fully EXPECTS me to be involved at these levels. You can be a better admin person if you see yourself as a benevolent server to your team, not as some untouchable jerk that sits in thier office all day mulling over pml code and trying to think of the next totally useless tool to implement.
this forum is the best!!!
It is so true that some PDMS admin think they are the king. Just as Guru said we are in service department, we help designers and engineers. They are the "billable" people that gets the project done and things built. Without them I do not care how fancy the macro is and how automated the drawing productions are, it is all useless.
Also being the PDMS admin nowadays means you will need to also know some networking basics, move and segament the network, if your LAN is luggish etc. Back up your own data instead of depending on IT's incremental backup...
I have also seen some admin guards whatever knowledge they have to themselves and lock up the system to any improvement ideas. I got myself into trouble so many times fighting this battle.
To me there should be collaberation and not competition. Just like this forum exist so we can share our knowledge and work process so that everyone who uses PDMS on real projects gets to see benefits of the automation and value provided by using this tool.
I like Guru's signiture - if I can not do it, then it can not be done. Guru must be a piper. I would go a little beyond that - if this forum can not help you solve it, then it can not be done.[/U]
if this forum can not help you solve it, then it can not be done.[/U]
