PTC Windchill RV&S Reviews

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.

With 20 different teams of 8 developers each working on different paced projects with one single code base, our company decided MKS Integrity would be a great solution to purchase. MKS Integrity was chosen after reviewing products by IBM, Atlassian and a few other open source products. The great thing about MKS Integrity is that it is more of a toolbox of components rather than a tool. You can take components and make them work exactly the way you want your solution to work. For example, we started off by using this strictly for an SVN replacement. We only needed a couple of projects with many sandboxes. Then we used the toolkit to migrate away from another project management tool and track all change requests through customized screens in MKS. The change requests had strict workflows, allowing better management and control over changes. Then the company designed a QA process and issue tracking within MKS. Then came the help desk software replacement with further build out of Integrity. Over time, we replaced almost all of the one off applications/solutions used by Dev, QA, HelpDesk, Business Development & Project Management into one single solution MKS.

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.

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.

It is used by the engineering department primarily for software development.

MKS is used for:

• Storing documents
• Requirement Management
• Feasibility Analysis
• Test Management
• Release Mangement

We Used MKS Integrity at Intersections Inc (my previous workplace) basically for change control and version management for application code.

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

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

It streamlined the software development life cycle.

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.

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.

MKS Integrity is used across the whole organization and allows our product development team to track all aspects of day to day development work .

We use it to support our software development process. It is used in software development department. We keep records of all activities, task, code outputs, code review, requirements and documents. Most of the time we do not use it directly since we have a custom internally developed tool that automates a lot of actions.