Atlassian Jira is a project management tool, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
$81.85
per month 10 users
Enovia
Score 6.7 out of 10
N/A
Dassault Systèmes S.A. is a French company and a world leader in the production of 3D design software, 3D digital mock-up and product lifecycle management (PLM) solutions.
The Jira software works well for managing scrum boards and allocating resources to a task. When your Epics and Issues are set up properly, it can give you a good idea of where your team stands and the trajectory of your project. It is not the ideal solution if you need to provide documentation and support to people outside of your product teams or organization. It would benefit from having a public documentation or repository feature.
Very well suited for direct integration with CAD packages (Solidworks/ Auto desk Inventor or AutoCAD) and version control of CAD Model/Assemblies and Drawing files) and creating parts and document objects directly into Enovia and controlling their lifecycle from CAD Interface. Similarly, Enovia's Engineering central is already equipped with Industry standard ECR/ECO process which needs little customization for implementing Engineering Change management process. The hardest part in Enovia is controlling the disposition of released material for the downstream process in other ERP systems. For example, if a released material has gone for production or purchasing in ERP system/MRP system then dispositioning that material with Major revision (which may need manufacturing to stop the production due to faulty design) have no direct control to stop the downstream activities. Most cases its manual process to communicate with ERP team to for taking action. Similarly, revision of Documents (material Spec for example) linked to thousands of parts required special process (some time needs to schedule in the weekend).
When a part/assembly has been released in Enovia and gone for production or downstream processing, Enovia doesn't have much control, hence, Enovia should come up with an easy controlling mechanism for various disposition of parts and seamless communication with an ERP or downstream process.
If a document is linked to thousands of materials then revising this document takes long time gets floated to the BOMs where the previous document versions are used. So, Enovia should have an efficient way to replace the floating process or another efficient mechanism for document revision processing.
This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.
In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.
JIRA Software is a pretty complex tool. We have a project manager for JIRA who onboarded us, created our board, and taught us the basics. I think it would have been pretty overwhelming to learn without her. JIRA offers so much functionality that I'm not aware of -- I constantly need to Google or ask others about existing features. Also, although they are all under the Atlassian umbrella, I find it difficult to switch between JIRA Software and Confluence.
Our JIRA support is handled internally by members of our Product Support team. It is not supported by a 3rd party. Our internal support will always sent out notifications for downtime which is usually done on the weekend unless it is required to fix a bug/issue that is affecting the entire company. Downtime is typically 3-4 hours and then once the maintenance is complete, another broadcast email is sent out informing the user community that the system is now available for use.
One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.
Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.
Jira Software has more integrations and has more features than many of its competitors. While some of its competitors do have better UI/UX than Jira Software, they have improved this greatly over time. Atlassian also acquired Trello years ago, so that adds better user interfaces to the system. They do also offer a pretty in-depth library of how to customize the platform that others don't.
Easy learning curve for the users- Very user-friendly Interface for Engineering central make the users happy and easy to learn the BOM creation and Engineering change management process.
Time-saving - Seamless Creation and revision process of objects saves a huge amount of time compared to other systems.
Easy to copy existing business data and modify them as required.
