The software changes into something it was not when it was first installed. They often overlook the reality that unlike 'hard' products, software is like a living organism which evolves and even morphs over time as updates are installed which include enhancements and new ways of doing things. It's not always an issue of what they don't see in their current software, it's that often management has NO idea what their current packages are capable of even doing and often when you hear about some 'new' capability in some other system, the tendency is to assume that these capabilities are ONLY available in the new system because they don't recall hearing about that when they first purchased their current software.
"Wildfires are dangerous, hard to control, and economically catastrophic."īen Loosli RE: NX vs. Good luck with the switch, if it happens. Another division was in the middle of a multi-million dollar expansion of UG and TeamCenter. We were the only division to make the change at that time. As a corporation, we had a balanced mix of UG and Pro/E seats, approaching 100 of each. It was a corporate decision that forced the change on us. The UG files had to be marked so the engineers knew that the master was in Wildfire now. How do charge that time when the design has been in production for 5 years or more and you are modeling it just to use in an assembly? Drawings had to be managed when we did a redesign in Wildfire and move the 'master' over, which we did on some parts. We only used Wildfire on new products, so that saved us some problems, but common items that we had modeled over 18 years of UG all had to be remodeled in Wildfire. Jobs had to be managed between the UG stuff and Wildfire stuff until everyone had been trained. Management was not happy with that loss and complained. Loss in productivity for another 6 months had to be factored into the work scheduling for jobs. Took us 6 months of training classes to get everyone through the courses.
We had 35 users, all of whom received 12 days minimum of training in Pro/E.
I worked for a company that switched from UG2V18 to Pro/E Wildfire1.
We are just getting ready to roll out Creo 2 M100, as earlier builds had problems in one area or another. What version are you looking at Creo 2 or the just released 3.0? My experience with PTC CAD is wait 6-8 months after initial release, about 6-8 build releases, before attempting to put it in production. It is Pro/E Wildifre with a new paint job on the outside. Creo is anything but 'new and shiny' on the inside.
0 kommentar(er)
