PTC Integrity Reviews

I use the tool to create tasks or change requests and documentation. Earlier, I used it for configuration management, requirement analysis and writing of test cases. Currently, I'm only using it for creating tasks or change requests.

I personally like PTC Integrity because it provides everything within the software. You can store and access your data and perform various tasks. Compared to other products, I find it user-friendly, which can sometimes feel complex. I think PTC Integrity is user-friendly, making it nice to use. The tool is easier to learn. 

The tool has a dashboard that details our projects and products, including the number of tasks, change requests, and their statuses (incomplete or complete). Having all this data within the solution makes collaborating easy for our project team. Unlike using multiple tools, having everything we need in one software platform is convenient.

I rate the tool's user experience and interface a nine point five out of ten. 

We use the tool for Application Lifecycle Management. It's an ALM tool to manage the product from inception to providing support and maintenance.

I have found that previously, the OEM sector was managing everything, possibly manually. However, with the introduction of the product, it has become much easier for customers to handle their products. Previously, customers were using different software to manage their products. However, PTC Integrity offers a solution for requirements management, test management, and even development to support live ticket management. So instead of using multiple software tools, we can use it for all these purposes.

Instead of spending money on different companies for various software, using one product like PTC Integrity saves money and offers all the needed functionality in one place.

I would rate the product's user interface and experience an eight out of ten. 

The solution is flexible in terms of customization. You can bend and reformat it in many ways. You can also customize the APIs and public functions. 

The web version does not have all the functionalities of the non-web version. Administration and adding/removing fields, etc. cannot be done on the web version. People want solutions that are compatible with Android. I also want to have a version by which I can bulk edit all the fields. 

I mainly used PTC to make a JIRA-like tool so that people can work with Agile.

I think it has more features as presented by PTC. However, we mainly used this solution for item management, change requests, item tracking, etc. The second thing we used it for was version control.

We have been using it because it gives certain abilities in the automotive industry, such as auditing or keeping track of information. It's still being used in many more companies, not just in mine. But I think that we can also replace it with other tools. Its performance is not very good, because many features are not relevant in today's world. I believe it's going to be fading away from use.

To be honest, the third controller system is kind of old. There are lots of transactional changes that have not been implemented in PTC. If you have a larger project, for example, whenever you give bits and need to change 10,000 files you can just commit them. But here the work style is a little more file-based, so you'll have to take care of almost all the files individually. It's not a single commit like you do here, but rather you have to allocate time for each component or file that you want to check-in or commit. That's a very big issue.

It's moderately user-friendly. There are some functions that are missing, for example, copying the path of a file in the versioning system. That one has been implemented by adding a button that we programmed it in our company to do so. That's just an example. There are more features that should have been there for a better user experience. So our hesitation has been at this point in user experience.

It is also very hard to connect this solution with other tools or integrate it with other tools.

All the features are valuable, including:

• NPI
• Requirement management
• Test management
• Project management
• Defect management
• Source and configuration management
• Review and audit management
• Agile

• This tools improve teams productivity, a lot of flexibility for automation.
• One admin can manage multiple servers with the same configuration.
• If a team is doing off line testing, then 2,500 test results can be updated in two and a half minutes, meaning a saving of 40 man-hours when compared to users updating results manually.

I am a solution manager and I manage a portfolio of applications in the company. We have been conducting a PTC Integrity pilot.

We use it for documentation and requirements management. We do not use it for test management, yet. It is for requirements collection and then creating and maintaining specification documents.

The most valuable feature is traceability starting from the requirements until the end of a project. This works provided it has been properly managed.

Our primary use case is for all kinds of data management right through to test case management. We have offices in both Germany and India with about 600 licenses in total.

The most valuable feature relates to traceability, we have complete traceability as per process requirements.