jwebby - Thursday, December 9, 2010 10:34 PM:
Hi I am just evaluating this software. I work for an aerospace engineering company and we are about to purchase a plm system. I like open source software so I have come to aras. I need would need to integrate solidworks. After talking with a sales person from aras I was told I could purchase the connector from xplm for 4500 for 5 users annually. I was also told I could make the api myself with the training class they provide. I dont really have time for that, Im wondering if there is anyone who knows of an open source solidworks connector of anyone who developed their own who would be willing to sell the software for a more reasonable price??
Brian - Wednesday, December 15, 2010 6:51 AM:
Just out of interest how much are you about to spend on buying another PLM system?
I'd be willing to bet that if it is anywhere near as good and flexible as Innovator it will make the 4500 x 5 per year look like chicken feed.
Writing your own Integration to Solidworks is possible but it would be a big undertaking and cost you a lot more than 4500 x 5 to do properly.
Cheers,
Brian.
jwebby - Thursday, December 16, 2010 11:03 PM:
Thanks Brian
we are looking at a system called keytech. the price was around 70k for implementation and training with an annual maitenance cost of about 10k this is for a very small number of licenses. I think it was 8 engineering and 4 admin. the licenses are floating so that is a little better. One of my engineers went through a plm implementation, and knows the work its going to take to get it up and running CORRECTLY. He and I have setup a sandbox aras database and have been testing out the software, we talked with a couple guys from xplm and they showed us a demo of what their soldiworks integration can do. I think if we decide to go with aras instead of keytech we will be purchasing the solidworks connector. I've been warned that in order to do a succesful plm implementation there are a lot of things that need to planned for and that all departments need to be involved. I'm wondering if anyone has any advise on the best way to implement aras/plm? Maybe a good book on plm implementaion.
Jason
Brian - Friday, December 17, 2010 8:04 AM:
Hi Jason,
Like so many things there are many ways to go about a PLM implementation.
There are no doubt books out there and almost any well thought out methodical approach will get you a long way.
The most important thing, in my opinion, is knowing where you want to get to with PLM. It can be a lot of things to a lot of people and covers such a large area that it is easy to get overwhelmed by the options. Don't expect to do it all at once. Start with the things you know best and have the most control over. Then expand by looking for low hanging fruit opportunities to demonstrate positive results. Tighten your control and your processes then "annex" a new area and expand into there, bringing business imporovements with the new tools.
Understand that PLM is not just about the Engineers and engineering data and it is certainly more than just a software application. In the end PLM is about Process AND Data. With the right PLM system you can improve virtually every Business Process in the company over time. Figure out who will use the data you are going to capture. This will help you to understand the number of licences you need (if you are not using Innovator) and also the scope and impact you are expecting out of your system.
Do you have robust change management processes already in place? Do they "cover enough ground" as far as involving all of the stakeholders?
Do you have in house manufacturing that you need to package information for or are you using a contract manufacturer who might require more (or less) data packaged in a different manner?
Understand your chosen tool. What can it do? What can it be made to do? Will you outgrow it with modest growth over a couple of years? How will it integrate into CAD and ERP systems? Do you even want it to? Training with the tool, possibly even before you start using it, can help you to make the right decisions on how PLM should be implemented and what areas to tackle first. Are you looking only at CAD, Part and Document type data or are you looking to integrate Project Management, Part definition and approval, Vendor Approval and performance tracking. Does Finance/Marketing have an interest in the tool and the data from an early Design to cost position in order that better design decisions can be made along the way.
Do you have the resources to develop the system into the future or do you plan to establish a strategic partnership with your PLM implementer?
Understand your own processes before you start. Certainly understand the processes you are going to start with (since you are unlikely to try to eat the elephant in one bite). What do you do now. Where are the ptifalls? What do you hope to gain out of implementing PLM? This will help you to educate the users who WILL be put off by having to do new things and work with new tools for reasons that don't always directly affect them in positive ways. Since PLM is usually about more than just one department/area there are some things that you will ask users to do that they will say "but that takes me more time" (even in the best PLM systems you will have some of these instances) "and I don't see why I should do it." Understanding why you are doing it will help with user buy in.
I always aim for processes which capture useful/valuable/critical information as a by product of "doing the job the right way". Say in a CAD design environment when an Engineer first thinks "I'm going to design an xyz widget" they should be getting a part number from the PLM system and checking the first interation of the documents (CAD) and technical/specification/requirements documents into the system. When they want to get the part or assembly reviewed all of the information about that product should already be in the system ready for all of the reviewers to access electronically. The parts and documents are released (Actually the Documents are released which causes the Parts to be released since the Documents describe the Parts and as such "Documents Lead and Parts Follow") for purpose. Initially the purpose for which they are released is Prototyping. Now you can assess the prototype against the documents that define it.
Now I'm rambling. Send me an email direct to [email protected] if you think you would like to continue this discussion.
I'm a PLM Implementation Consultant at Matrix (Aras Partner http://www.aras.com/partners/partner-directory.aspx?region=Australia / NZ&vertical=All&type=All)
Cheers,
Brian.
