PTC Windchill RV&S Reviews & Insights

There is a group of engineers that work on the interface to validation preparation and validation. They are in need of tools that connect their systems and software. They need to organize and manage their requirements, models, codes, and tests. PTC Windchill RV&S supports and allows to manage complete trackability of activities on the whole software life cycle. The software allows for improved strategy finding and optimization in end-to-end scenarios. There is room for cross-discipline collaboration. The client-server architecture is comfortable and allows for several well-introduced strategies and rigorous control. PTC advertizes PTC Windchill RV&S 12.3 as a flagship for PLM. We agree that the software package is complete for our needs and we are very satisfied with the in our company well-introduced methodologies. We are addicted to the transparency and thorough-going processes implemented. We find it guiding and prefer to follow the included best practices. The software allows us not only to organize all our validation activities it favors the control and initiation. We start better, are better in performing tasks in sole responsibility and collectively. We have comfortably adapted and customized the best practices. PTC Windchill is well accepted in the outcomes at our customers.

We enjoy doing requirement mappings. The enhancement in transferring them between models is great. It is for innovation all the time a challenge to conduct them. We have two major scenarios for that task set. One is to integrate already well-validated models into greater sets. The other is defining totally new ones. We developed new strategies and refined the existing ones. We rate the synching requirement configurations as comfortable. The processes of synching the items back to the models. The major advantage is to optionally synchronize all-important and intended traceability relationships from Modeler so that both can be given the correct right the right group of uses while others only see the structures. We too prefer the handling of deletion and creation. It is a real advantage how the mapping and relation are implemented. The implemented integration to third-party tools for requirements definition and management is a plus. We like the profiling features and the high compliance to industrial standards as well as the module variability modeling.Windchill RV&S makes us perform better and let us take over control. It enhances our return-of-investment efficiencies to the top. The only drawbacks are the high skill levels needed and the necessary relation in businesses to make the profits. Another topic is the resources that are needed.

Our organization has deployed Windchill RV&S. It is used by backend Engineers in our company for change management, source code management, version controlling. It aids in the proper management of the code.

The product is ideal for big development firms with several software solutions being produced at various periods. It is most likely unsuitable and overkill for smaller enterprises.

PTC Integrity was used by one of my client, and it is being used for past 8 yrs. PTC previously known as MKS Integrity, is used as a version control, source code management, change management and defect tracking tool. This tool is used throughout the IT Organization globally. I've been using this tool since 4-5 years, and comparing it with other tools in the market, I did initially have some problems using the functionality, but once I got used to it, I liked it a lot. The version controlling of the source code is very nicely organized, and helps in managing the code optimally. In one specific instance, we did see the tool help identifying an issue in code which was checked-in about 2 years prior. There are other features in PTC Integrity, but my main purpose was for version control of source code, and change management, used for labeling the code and promoting.

PTC Integrity is an excellent source code management and version control tool, and I would suggest anyone to use it for that purpose. We can even define our workflows using individual forms for implementing Change Management, Defect Management and Access management requests. If properly used, this tool is great for managing our code for very long periods, considering my 4-5 years of usage.
Though the UI could be better, and integration with some application servers could be better implemented, this tool is a good tool.

PTC integrity is used by couple of division at my company. It is a single access point for requirement management and traceability.

PTC Integrity is well suited for requirement management.

PTC Integrity is being used by the Engineering Department for DO-178 and DO-254 projects.

I would say that PTC Integrity is very well suited to structured environments where traceability is critical.

It streamlined the software development life cycle.

Ican't think of any limitations but it was the best tool I have used so far.

PTC Integrity is being used by the company that I am contracted to. As a systems engineer I help users globally to become proficient with the tool, as well has how to correctly use the tool in a systems environment capacity. Meaning we use the tool to develop requirements for the product and then verify and validate the requirements/product. It has taken the ISD (Integrated Systems Development) team two years but the software has now been adopted by the company globally. The problems that PTC Integrity helps address is the one of having project teams scattered all over the world working on the same project. PTC Integrity helps these groups to communicate and work together better and more efficiently.

What are you using now?
What are you spending currently for this type of software solution?
How could a tool of this nature be used by your company to save money lost due to poor or inefficient design?

Integrity is being used by specific groups within our organization. Primarily it is used by analysts for requirements tracking and by QA for testing. It addresses the need to have complete organization and documentation as required by the FDA, for certain groups.

Are all areas of the SDLC willing to use the same tool? If everyone is not going to use the tool, the group may not get all of the intended functionality out of Integrity.

MKS Integrity is used by one of our retail clients to store the deliverables and the ETL Codes. It is used throughout all the departments by all the teams like development, QA, UAT, Production. The biggest problem it addresses is it stores all the deliverables(whether it is document, model or Code) at a single location and assures the same codes are being deployed across the environments.

I recommend the product because of the following reasons.
- Version Control Management
- Deployment is easy through the tool
- Single Repository for all the Documents, codes, deliverable.
- Easy to manage the Projects, Folders with in Projects.
- Ability to support multi users, multi projects, availability thru Citrix,
- Ability to create the new version of the same deliverable when edited which assures availability of the history of the deliverable.

PTC (MKS) Integrity is used as our Configuration/Change Management tool by our program. The problems it is addressing are: having data in one location for access by all team members; helping in the management of workflow processes involving change processes, construction, logistics, software version tracking, document version tracking.

1. Know the requirements for each team that will access the tool.
2. Have the tool representative talk to how each requirement can be addressed.
3. What other third part tools can PTC "talk to" (data transfer requirements)?
4. How can we transfer info (data, documents) to third party vendors or partners?