solver changeover cost

[IceBreakerSours]

About a year or so, I decided to switch the only tool I was ever familiar with for my analysis needs. I gauged its capabilities, solution accuracy, cost, licensing, support, etc. and it came on top in each category so I started presenting the argument to others that they might want to consider switching too because the benefits could not be ignored. Other vendors not giving a hoot about what we want or milking us has added fuel to the conversation. However, what I would like to have and do not have any hard data on is the switch-over cost. So, here is my question: How would you go about this exercise? What factors would you consider in measuring the cost of changing an FE code? I am already working on it but additional perspectives would be very helpful. I work for a 'large' enterprise, if that helps calibrate the answer.

*********************************************************
Are you new to this forum? If so, please read these FAQs:

http://www.eng-tips.com/faqs.cfm?fid=376

http://www.eng-tips.com/faqs.cfm?fid=1083

 

[JBlack68]

Assuming that the change-over was triggered by a capability not currently available, time saving , something else the main cost for the change over will be the training. I am not talking about talking of training offer by the supplier as a deal sweater. This is a given.

If all the stress guys have significant experience then all the basic is a given. it's just a "matter" of learning the new tool. It typically takes around 6-month day-in/day-out use to be proficient with the tool. Most (all) engineers will try to do the same thing with the new tool they use to do with the old one. It takes a "change of thinking" sometime. One must adapt to the way the new tool works. consequently there might be a change of process required. Therefore for about 6-months one needs to reduce the affectivity.

one may also wants to add extra checking

 

[goeasyon]

It could be difficult to totally replace an FEA package at a time, assuming a transitional period that two or multiple packages co-exist is probably more practical.

https://welsim.com

 

[JBlack68]

if both software co-exists one must assume that this is only for a defined period - maybe budget is such that have both is not a problem !
If there is a "switch off" day then one must be sure that all the previous FE files/models have been converted. Maybe a permanent licence has been purchased allowing the use of an old (frozen) version of the previous software