The tool's web-based UI needs improvement. Some functionalities don't work yet, and querying items is slow. Also, it's not in the cloud yet. I don't know if they'll do it in the future because they already have core agreements with customers. If they offer these functionalities, customers will likely buy their product.
Inspector General at a manufacturing company with 11-50 employees
Real User
Top 20
2023-09-05T09:47:48Z
Sep 5, 2023
The product requires a learning curve. For complex businesses, the internal templates could have more flexibility and compatibility. Our maintenance team finds it challenging to customize some functions. It could be user-friendly.
Architect at a computer software company with 5,001-10,000 employees
MSP
Top 5
2023-06-19T04:55:00Z
Jun 19, 2023
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.
Software Development Engineer at a transportation company with 5,001-10,000 employees
Real User
2020-04-20T07:27:00Z
Apr 20, 2020
It's not easy to plan on this solution and it's not user-friendly. The interface should be more like a web interface. It's not easy to use. For example, if I need to attach pictures then relate items together, it doesn't work well. It doesn't look nice and it doesn't show you how it will look.
Manager at a manufacturing company with 10,001+ employees
Real User
2020-03-16T06:56:10Z
Mar 16, 2020
We are unhappy because everything that we needed required customization and this is not a plug-and-play type of solution at all. It is like for every small thing, you need a dedicated team around to do the customization. Even very simple needs that are generic in the industry are not available out of the box. Overall, it needs to be more plug-and-play. The integrations that PTC has built are not fully integrable. The version that we are using is not web-based, but client-based. I have received feedback from our team who is doing the most recent PoC and they are not happy with the web-based interface. Apparently, it does not have all of the features that the client-based one has. Our client-based version is not helping us because each machine needs to have the application separately installed, which is a big problem for us. The user interface is difficult to navigate.
Technical Leader at a manufacturing company with 10,001+ employees
Real User
2020-02-11T06:18:00Z
Feb 11, 2020
The most significant improvement I would like to see would relate to speed. I work in India and our server here is quite slow sometimes, so I would like to see performance improvement. I would like to see an improvement there in the next release, but I'd also like to see a lot more reports. Nowadays people lean towards JIRA where they are able to see a lot of reports. In PTC there are more ways to create them but more chance of things going wrong. People would like to see something similar to what is available in JIRA.
Technial Lead at a transportation company with 1-10 employees
Real User
2019-12-31T09:39:00Z
Dec 31, 2019
The development environment is only on JavaScripts but other languages are not. For example, .NET platforms. It's not so customizable. Compared to other tools, defining user stories is a slightly more cumbersome process as an ALM engineer.
Software Developer at a transportation company with 10,001+ employees
Real User
2019-09-15T16:43:00Z
Sep 15, 2019
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.
The PTC Integrity Software Suite provides a comprehensive set of Application Lifecycle Management (ALM) and Systems Engineering capabilities that enable cross-discipline collaboration, improve time-to-market, streamline compliance, and reduce product risk. Simplify the complexity involved in developing today's complex engineered and smart, connected products.
The tool's web-based UI needs improvement. Some functionalities don't work yet, and querying items is slow. Also, it's not in the cloud yet. I don't know if they'll do it in the future because they already have core agreements with customers. If they offer these functionalities, customers will likely buy their product.
The product requires a learning curve. For complex businesses, the internal templates could have more flexibility and compatibility. Our maintenance team finds it challenging to customize some functions. It could be user-friendly.
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.
It's not easy to plan on this solution and it's not user-friendly. The interface should be more like a web interface. It's not easy to use. For example, if I need to attach pictures then relate items together, it doesn't work well. It doesn't look nice and it doesn't show you how it will look.
We are unhappy because everything that we needed required customization and this is not a plug-and-play type of solution at all. It is like for every small thing, you need a dedicated team around to do the customization. Even very simple needs that are generic in the industry are not available out of the box. Overall, it needs to be more plug-and-play. The integrations that PTC has built are not fully integrable. The version that we are using is not web-based, but client-based. I have received feedback from our team who is doing the most recent PoC and they are not happy with the web-based interface. Apparently, it does not have all of the features that the client-based one has. Our client-based version is not helping us because each machine needs to have the application separately installed, which is a big problem for us. The user interface is difficult to navigate.
I would like to see better integration from the architectural side. It is difficult to use when it comes to linking models.
The most significant improvement I would like to see would relate to speed. I work in India and our server here is quite slow sometimes, so I would like to see performance improvement. I would like to see an improvement there in the next release, but I'd also like to see a lot more reports. Nowadays people lean towards JIRA where they are able to see a lot of reports. In PTC there are more ways to create them but more chance of things going wrong. People would like to see something similar to what is available in JIRA.
The development environment is only on JavaScripts but other languages are not. For example, .NET platforms. It's not so customizable. Compared to other tools, defining user stories is a slightly more cumbersome process as an ALM engineer.
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.