The Aras Innovator software is used for product lifecycle management (PLM), advanced product quality planning (APQP), lean product development, and new product introduction (NPI). Aras switched to an open source model in 2007, where clients obtain the software for free, and Aras Corp provides technical support, software updates, and other consulting as a subscription service.
N/A
GitLab
Score 8.7 out of 10
N/A
GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps teams across the complete DevSecOps lifecycle, from developing, securing, and deploying software. Differentiators, as described by Gitlab:
Simplicity: With GitLab, DevSecOps can…
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.
It is well-suited for any project that needs VCS. It's an excellent choice for teams that might be remote or have to collaborate across teams. Plenty of features allow for async working. With its dashboards and reporting features, it is also suitable for nontechnical PMs or stakeholders. It allows for very bespoke customization and can most often do much more than you need it to.
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.
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.
I really feel the platform has matured quite faster than others, and it is always at the top of its game compared to the different vendors like GitHub, Azure pipelines, CircleCI, Travis, Jenkins. Since it provides, agents, CI/CD, repository hosting, Secrets management, user management, and Single Sign on; among other features
I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!
I've never had experienced outages from GItlab itself, but regarding the code I have deployed to Gitlab, the history helps a lot to trace the cause of the issue or performing a rollback to go back to a working version
GItlab reponsiveness is amazing, has never left me IDLE. I've never had issues even with complex projects. I have not experienced any issues when integrating it with agents for example or SSO
At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft
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.
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution. GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same. No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.