geesamand
Mechanical
- Jun 2, 2006
- 688
We have an older CAD program called ExpertCAD. It is supported on the latest builds of Windows, but you can tell it uses older Windows APIs. It performs oddly when run from a server or over long-latency connections in a way modern Windows programs do not.
IT really wants to move us to a terminal workstation system. This one program is the stumbling block - the interface performs poorly over the virtual and it's unlikely they will "fix" it since it requires recoding their entire interface. But IT has cost savings and security hazards that are better with the terminal workstation system. Plus ExpertCAD is really uncommon. (the other users still in existence are probably hipsters)
The other program to use is AutoCAD or AutoCAD LT. IME these programs have a huge assortment of complexity from their legacy - there are multiple ways to write text, multiple ways to make things appear or disappear, multiple ways to dimension and control dimension properties, etc. I'm concerned we'll never develop a useful mastery of them.
Of course there is the big hit when we train on the new CAD system and struggle back into productivity, and the endless tax caused by use converting old drawings into the new system when we want to make a new part based on the older part or revision.
Any tips for arguing a case to keep the old CAD system in place? Or tips for easing the transition and keeping AutoCAD from becoming the nasty animal it can sometimes be?
Thanks,
David
IT really wants to move us to a terminal workstation system. This one program is the stumbling block - the interface performs poorly over the virtual and it's unlikely they will "fix" it since it requires recoding their entire interface. But IT has cost savings and security hazards that are better with the terminal workstation system. Plus ExpertCAD is really uncommon. (the other users still in existence are probably hipsters)
The other program to use is AutoCAD or AutoCAD LT. IME these programs have a huge assortment of complexity from their legacy - there are multiple ways to write text, multiple ways to make things appear or disappear, multiple ways to dimension and control dimension properties, etc. I'm concerned we'll never develop a useful mastery of them.
Of course there is the big hit when we train on the new CAD system and struggle back into productivity, and the endless tax caused by use converting old drawings into the new system when we want to make a new part based on the older part or revision.
Any tips for arguing a case to keep the old CAD system in place? Or tips for easing the transition and keeping AutoCAD from becoming the nasty animal it can sometimes be?
Thanks,
David