Overall, I would rate the solution a seven out of ten. I would recommend it. 

My specific advice is for people in the automotive, aerospace, defense, or healthcare industries, where auditing is crucial. For example, in healthcare, where the FDA is involved, their audits are very strict, and they require a tool like IBM ELM that provides end-to-end traceability of changes. This traceability allows you to track what changes were made, why they were made, and how they impacted the requirements. 

This is essential for industries where functional safety or certifications are critical. I would recommend this product for these use cases.

If you are working on a small project or managing a small internal team, I would not recommend using IBM ELM. It would be too much overhead for such projects.

I think there are probably better and more nimble solutions available on the market. If a company is starting from scratch, it doesn't really need such a heavy solution. If you're in the automobile, healthcare, aerospace industries and the like, where you have a lot of legacy data, and your requirements are crucial and you might be audited, then you do need to have a system which offers safe certification and a few other things. It should support agile templates and a few other things. 

I rate this solution a seven out of 10. 

Consider the Atlassian tool set and an open source control system.

From my experience, Jira is a better solution than Workflow because it's more flexible. 

I rate this solution four out of 10. 

Overall, it is a good solution. It is flexible and adaptable.

Consider reviews before investing a fortune on it.

You should use this product only after the issues mentioned above are resolved.

• Check the planning, and see if RTC fulfills all of your needs.
• Check if your other tools can connect to RTC.
• RTC does not come with many interfaces. However, OSLC and an internal API are what you can program for your interfaces for your tools.
• It may be necessary to migrate your existing data from another SCM tool, or for the standard process flow afterwards. It is nice to have some automated helpers which create and update work items for the user.

We are using the on-premises deployment model.

I would advise others considering using the solution to have expertise in the solution from the beginning. Have someone who understands the tool and can help you utilize its features and you'll get an ROI right from the start.

I would rate the solution eight out of ten.

Look for guidelines and YouTube videos before starting to use RTC (too complex for new users).

Be careful when selecting suitable project templates, as there's no way of changing it later.

It is very complex tool and require a lot of expertise to manage. Anyone opting for IBM RTC should first get a through training

I recommend this product. But it is very important that you define your software development process very well before starting to use this tool. Otherwise, you will be automating a problem.