Dassault Systèmes S.A. is a French company and a world leader in the production of 3D design software, 3D digital mock-up and product lifecycle management (PLM) solutions.
$15
per month
IBM Engineering Lifecycle Management
Score 6.9 out of 10
N/A
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.
Very well suited for direct integration with CAD packages (Solidworks/ Auto desk Inventor or AutoCAD) and version control of CAD Model/Assemblies and Drawing files) and creating parts and document objects directly into Enovia and controlling their lifecycle from CAD Interface. Similarly, Enovia's Engineering central is already equipped with Industry standard ECR/ECO process which needs little customization for implementing Engineering Change management process. The hardest part in Enovia is controlling the disposition of released material for the downstream process in other ERP systems. For example, if a released material has gone for production or purchasing in ERP system/MRP system then dispositioning that material with Major revision (which may need manufacturing to stop the production due to faulty design) have no direct control to stop the downstream activities. Most cases its manual process to communicate with ERP team to for taking action. Similarly, revision of Documents (material Spec for example) linked to thousands of parts required special process (some time needs to schedule in the weekend).
IBM Engineering Requirements Management DOORS former IBM Rational DOORS profits very much from the mighty market position it had till today. It had been the most favored requirement engineering tools suite with the highest investments in the infrastructure concerning hardware, software, and knowledge sources. It was embedded in knowledge sources of test stands, hardware labs, and knowledge database servers. It allowed for some of the highest profit changes and made the fame with it. But the paradigms of requirements engineering change. If not were superseded by completely different approaches for the target solution worlds. The foremost position in the selling tables is unstable if changes are not solved or coped with by the strategist at IBM and their customers. Since the highly successful alternative suits are already at the market, and some are from IBM already the lifecycle for IBM Engineering Requirements Management DOORS is at the later highs. But the suite is still at the very top and very popular. There are still many problems unsolved and many wishes at the customers to make the use more comfortable and efficient at the overall level. If the time of setting up the software package is passed the adoption get more extended and complicated. There is a lot of work at the stage around and the expertise will be required for a long time from now.
Easy to use with well defined template and user defined fields. New team can setup a project area easily by copying an existing template and adding customized fields for their special needs.
It can be used during almost the whole project cycle and give us a better view and control on the projects.
When a part/assembly has been released in Enovia and gone for production or downstream processing, Enovia doesn't have much control, hence, Enovia should come up with an easy controlling mechanism for various disposition of parts and seamless communication with an ERP or downstream process.
If a document is linked to thousands of materials then revising this document takes long time gets floated to the BOMs where the previous document versions are used. So, Enovia should have an efficient way to replace the floating process or another efficient mechanism for document revision processing.
Wireframes are quite basic. If you need intuitive and interactive wireframes to elaborate the requirements. you probably need to define outside the tool and then upload as image.
ER (define data dictionaries) modeling is not there.
Use case modeling is quite basic. You can visualize the use case and actors relation but the tool does not enforce the rules.
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.
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.
Easy learning curve for the users- Very user-friendly Interface for Engineering central make the users happy and easy to learn the BOM creation and Engineering change management process.
Time-saving - Seamless Creation and revision process of objects saves a huge amount of time compared to other systems.
Easy to copy existing business data and modify them as required.
