Aras PLM vs. GoCD

Aras PLM works for our company, yet I don't have experience with any other software system. The system does not refresh and update quickly. Often times users need to force a refresh or logout and logon to verify changes and updates. The Lock and Unlock feature needs getting used to.

Incentivized

Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.

Incentivized

• Aras PLM definitely controls documents and provides the approval levels needed to be compliant.
• Aras PLM makes organizing and structuring libraries logical and intuitive.
• The search tools in Aras PLM provides quick and efficient access to documents

Incentivized

• Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
• The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
• Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.

Incentivized

• Aras PLM uses terms and labels that can be confusing like Subsystem / Subsystem Version, Project Record Number (PRN). Companies need to understand these terms and develop business processes to set user standards.
• I personally use Aras PLM to manage information technology project documents. In my opinion, Aras PLM is more geared to product and engineering. I would like to see a general project management Aras PLM version with terms and labels that I am familiar with.
• The description field should be made required. Many of our engineers have created records and left that blank because it was not required. This would help with the context or background of each record.

Incentivized

• UI can be improved
• Location for settings can be re-arranged
• API for setting up pipeline

Incentivized

Our company is moving from repositories like IBM Notes, MS Sharepoint, and plain network file share directories to a more controlled system of recordd like Aras PLM.

Incentivized

Our company developed numerous IBM Lotus Notes databases to perform document control. Aras PLM is the better choice to IBM Notes databases and home grown databases.

Incentivized

GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.

Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.

Incentivized

• Aras PLM has kept our company compliant and on the right side of audits with the Food and Drug Administration (FDA).
• Aras PLM keeps our project document history readily available and works well without stage gate review and approval processes.

Incentivized

• ROI has been good since it's open source
• Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
• More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date

Incentivized