IBM Engineering Lifecycle Management (ELM) is an end-to-end engineering solution used to manage system requirements to design, workflow, and test management, extending the functionality of ALM tools for better complex-systems development.
N/A
PTC Creo
Score 6.8 out of 10
N/A
PTC offers Creo, the company's line of computer-aided design (CAD) products that support the product lifecycle management (PLM) process with 2D and 3D design kits (Creo Elements and Creo Direct), an augmented reality module, Creo Illustrate for technical illustrations, Creo Sketch, Creo Schematics and Creo View for diagramming and sharing information, Creo simulate for running simulations, and other modules.
$2,480
Pricing
IBM Engineering Lifecycle Management
PTC Creo
Editions & Modules
No answers on this topic
Design Package
$2,480.00
Offerings
Pricing Offerings
IBM Engineering Lifecycle Management
PTC Creo
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM Engineering Lifecycle Management
PTC Creo
Features
IBM Engineering Lifecycle Management
PTC Creo
Computer-Aided Design Software
Comparison of Computer-Aided Design Software features of Product A and Product B
The software is robust enough to handle highly complex software development or other product development and can be used well beyond the range to do what a client needs. However, because of the inability to hold its users to proper best practices, things can get wildly out of hand and cascade over the years, creating unnecessary technical debt. The system has a lot of usable features, but they don't funnel users toward the correct processes and practices.
PTC Creo is great for assemblies that multiple users are collaborating on. Models can reference other models that someone in another department has released and when those models are changed, the referenced parts and assemblies are changed. These changes are very helpful when working on collaborative machine designs and comparing forging dies with the final parts.
I feel like it is too heavy sometimes and updating is not very straight forward. For example, if I want to change an incident ticket (IN) to a service request (SR) and add some comment for the change, I have to first change the IN to SR, then click refresh which takes a few seconds, then add a comment. If I forget the refresh step, my comment will be discarded without warning like my ticket is not in the latest status. This also happens when somebody else changes the ticket during my edit as I can not lock the ticket exclusively.
At the moment we are required by contract to continue to use the IBM DOORS software for our current client. Given that it can be expensive, if we were to use it after our current client's needs were met, we would have to secure other projects in order to justify the continued use of the software.
The UI is terrible and not intuitive. Users need training in order to complete tasks. Much like SAP, it's not the clearest tool. The tracing feature is especially complicated because you must write the scripts yourself. There is a learning curve. Also, even the setup, installation, and logging in each time takes a considerable amount of time.
It does a basic job and has the potential to complete some robust reporting tasks, however, it really is a clunky piece of software with a terrible user interface that makes using it routinely quite unpleasant. Many of our legacy and maintenance projects still use DOORS but our department and company use many alternatives and are looking for better tools.
I liked the training manuals I used to learn some, as I didn’t have CAD background in college or before this job. My coworkers were able to share with me what they learned in PTC training and I was able to get support online and through reading.
It was easier to do all the change management-related activities, even configurations were handled very effectively. New process definitions and initiatives made it easier for better project deliverables. Effective resource allocations and better reporting and defect management. The overall cost of the tool is great too and well within budget.
Learning curve of SOLIDWORKS is higher compared to Creo, however, stability and more design control is provided by Creo. Creo also have more robust and stable interfaces. For larger assemblies, Creo works better than SOLIDWORKS. New upgrades of Creo has given liberty to open different file data of different software without any file conversion. Creo costs comparable to SOLIDWORKS cost, with more capabilities.
It's part of CLM suite so it can be used to manage the whole lifecycle with tight integration with development module (Rational Team Concert) and quality module (Rational Quality Manager).
Comprehensive reports and dashboards provide better visibility.
Having PTC Creo as our primary tool positions us as forward thinking and creative in the eyes of our clients.
PTC Creo constantly evolves in the ability to increase our productivity; new capabilities and features are added, which reduce our level of effort for some tasks.