Git vs. PTC Windchill RV&S

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Git
Score 10.0 out of 10
N/A
N/AN/A
PTC Windchill RV&S
Score 8.3 out of 10
N/A
PTC Windchill RV&S (formerly Integrity Lifecycle Manager of the Integrity suite) is an MBSE (model-based systems engineering) suite. The former Integrity suite contains an Asset Library which supports systems-of-systems approach to design (i.e. linking models into higher-level models that subsume them), a Process Director which is designed to articulate, manage and improve the design process, and a Modeler for visualizing and controlling the product design process. The Integrity suite is…N/A
Pricing
GitPTC Windchill RV&S
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
GitPTC Windchill RV&S
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
GitPTC Windchill RV&S
Considered Both Products
Git

No answer on this topic

PTC Windchill RV&S
Chose PTC Windchill RV&S
Source Tree and Stash with Git.

MKS integrity does well in some areas such as merging changes into the main trunk and managing change sets. We actually selected Git after using MKS integrity for over 7 years.
Top Pros
Top Cons
Best Alternatives
GitPTC Windchill RV&S
Small Businesses
GitHub
GitHub
Score 9.1 out of 10
GitLab
GitLab
Score 8.9 out of 10
Medium-sized Companies
GitHub
GitHub
Score 9.1 out of 10
GitLab
GitLab
Score 8.9 out of 10
Enterprises
Perforce Helix Core
Perforce Helix Core
Score 6.4 out of 10
GitLab
GitLab
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
GitPTC Windchill RV&S
Likelihood to Recommend
10.0
(36 ratings)
9.0
(16 ratings)
Likelihood to Renew
10.0
(1 ratings)
8.7
(10 ratings)
Usability
9.0
(1 ratings)
8.0
(2 ratings)
Availability
-
(0 ratings)
9.0
(1 ratings)
Support Rating
8.5
(11 ratings)
9.8
(2 ratings)
Implementation Rating
9.0
(1 ratings)
9.0
(1 ratings)
User Testimonials
GitPTC Windchill RV&S
Likelihood to Recommend
Open Source
GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
Read full review
PTC
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.
Read full review
Pros
Open Source
  • Ability to create branches off current releases to modify code that can be tested in a separate environment.
  • Each developer had their own local copy of branches so it minimizes mistakes being made.
  • Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
  • Conflicts are displayed nicely so that developers can resolve with ease.
Read full review
PTC
  • Helps to advance carefully through complicated and delicate process hives.
  • Improve thereby our time-to-market knowledge transfers along our portfolio.
  • Enhances the performances of single step in processes as well as the processes.
  • Allows for unprecedented overview in broads and in depths.
Read full review
Cons
Open Source
  • There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
  • Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
  • Many different GUIs, many people (including myself) opt to just use the command-line.
Read full review
PTC
  • It can be overwhelming with the number of tabs, functions and ways to achieve the same result. The average user may struggle with learning the tool.
  • The text editing in Integrity is weak and does not provide many options. Because of this, many user decide to use MS word instead, to document requirements.
Read full review
Likelihood to Renew
Open Source
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
Read full review
PTC
I do not make decisions on what tool my company uses. I am just the user of the tool and such decisions are not handled by me. If I were to make such decisions, I would definitely renew MKS, considering the amount of data we have stored in MKS and the current number of users who are familiar with the system
Read full review
Usability
Open Source
Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.
Read full review
PTC
PTC Integrity comparatively could be considered a nice Source code management, Version controlling tool and could be compared with tools like StarTeam. If the integration to move/migrate code could be integrated into this tool, it would become an extremely powerful tool.
Read full review
Support Rating
Open Source
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
Read full review
PTC
PTC Integrity administration can be somewhat daunting. They have been able to help with every question that I have submitted. Their support website is very easy to understand and submit questions and their phone support is wonderful
Read full review
Implementation Rating
Open Source
It's easy to set up and get going.
Read full review
PTC
I wasn't involved in implementation.
Read full review
Alternatives Considered
Open Source
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different.
The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
Read full review
PTC
I think the reason that PTC Integrity was initially chosen is that it was the best product available in the mix at the time. This coupled with the PTC deal on multiple products was a no brainer based on the size and scope of potential users.
Read full review
Return on Investment
Open Source
  • Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
  • Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
  • Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
Read full review
PTC
  • MKS Integrity has proved to be particularly useful in the software development process by increasing employee effieciency
  • MKS integrity has also made software development a very efficient process and makes feature releases and bug fixing a lot easier
  • In addition to the above, our organization has been able to support manufacturing easily by reverting to a previous software version in case of an emergency.
  • It has also led to faster time to market for new products.
Read full review
ScreenShots