Jama Connect® is a Requirements Management software and Requirements Traceability solution. Jama Software enables teams to manage product requirements and enable Live Traceability™ across the development process, in order to reduce cycle times and improve product quality.
N/A
Teamcenter
Score 8.2 out of 10
N/A
Teamcenter is a product lifecycle management system designed to help organizations integrate and standardize product development processes across functional silos.
Jama is an excellent tool for requirements management, development, and traceability throughout the development lifecycle. Jama aids in peer reviews of generated artifacts with time-boxed review cycles. Jama provides a robust ecosystem which is highly tailorable to the demands of the particular organization in which it is used
Teamcenter is growing very well in active workspace as a web-based client, but again, when I'm coming from the manufacturing point of view or a Build of Processes point of view, the software easy plan still needs to improve in a way. Of course, I think they're improving it also in a good way, but it's still not yet matured so from today onwards I can simply ask my users from product resistant to using the plan and push it further. I think there we have to improve more.
Focus in the content without loosing the track of the evolution of the items by maintaining the exchange of information between the users inside the Tool.
The possibilities to integrate this tool within our IT-landcape and with our other engineering tools is for us a leverage to success.
It is an easy-to-use tool and integrates many capabilities to manage CAD better than any other tool.
It is used by many companies with a great global presence and that has generated confidence for us when we decided to try it, the results have been satisfactory.
The user interface of this tool is not complex, it is easy to navigate and integrates a lot of functionalities that speed up our work significantly; as well as functionalities such as sectioning, displacing, moving, positioning, transforming, among others that have a lot to do with CAD management.
It works via the web through the browser, so it is not necessary to download any application that takes up space and more resources on the computer.
The 'filtering' capabilities in Jama are not as good as they could be. In particular, the ability to "nest" filters is quite limited. I have certain seen much better capabilities in other tools. ('Cradle' is an example of a tool with excellent "nested filters" capabilities.)
From an administrative point of view, the 'License' admin view is pretty disappointing. The particular thing that I'd like to be able to find out from it is the peak number of 'Float Creator' licenses in concurrent use on each day. If there's a way to get to that information, I haven't found it yet.
Jama is really easy to use and operate compared to other tools. This allows a process owner to get easier buy-in from the organization to see value early. My experience with this tool was very positive and we were able to see value early in its introduction
Because of our current customer needs, we will most likely maintain use of Siemens PLM products for some time. Aside from the initial software cost, we pay for yearly maintenance. Maintaining our yearly maintenance licensing with Siemens, we receive access to all of the latest software releases, as well as premier technical support
Jama is mostly designed for requirement gathering, but that can be possible using JIRA if we add only approval type of plugin for special requirement types. Jama's performance and features do not improve on a periodic basis i.e. with each release. Even bug fixes take a lot of time and they don't care about customer impact.
As previously mentioned, due to the intense amount of features and modules present in the software, the usability of the software suffers greatly. Many of the features are not used in our context, and many of the modules are not purchased, but the options are still present on the interface leading to a lot of clutter, much of which is never used. The interfaces suffer from a lack of design and tend to feel like a conglomerate of Windows 98 elements.
Jama is available most of the time if it is used within the application's boundary. Jama has very good availability if we use very high hardware servers. Sometimes we face issues if there are batch operations running.
With performance compared to JIRA, I do recommend Jama in this case. Jama provides very good performance, it loads immediately for any of the items and searches any item immediately. Performance is really good in all of the operations including creating stories, epics, item types or other support operations or report generation.
They typically answer within minutes of posting a ticket, and then you have a clear expectation of what the issue is, how to diagnose it, how long will it take to get resolved, and in which version a given problem is resolved, or if there is a patch for hosted services. They have a number of support people, and all of them are top-notch.
In the time that we have used Teamcenter we have received a good response from the support team, they have great customer service, we have solved the problems that have arisen very quickly, and they are attentive and answer us if we have any questions.
Jama 2015.5 implementation is very smooth and no need for much manual work. Jama 8 has many challenges and we can not install it as smoothly as Jama 2015.5. Initially, Jama didn't provide the Jama 8's installer files or zip files and they were just providing docker files to everyone (which was really strange). It is the worst that they don't provide all the files at a time. Why should they tell us where we should deploy, and why only a dockerfile? I am not very satisfied with Jama implementation.
The major sellingpoints of Jama were the review-system for internal and external reviewers and the inclusion of (Use Case) modelling tools, while keeping the core requirements-centric. Ability to synchronise with currently in use test-tooling and the low learning curve were additional selling points. Availablity of support in our local language was much appreciated as well.
Teamcenter is a more robust and faster application, with better search capability and easier customization. There is a reason you find companies using CATIA as their CAD software with Teamcenter as their PLM application! I don't know anyone who can name a company using NX with Enovia as their PLM!
There is no horizontal scalability available in Jama, we have only one choice to scale it vertically. But vertical scalable applications always have limitations to grow. In this case, Jama doesn't support horizontal scalability functions like multi-node architectures with a shared drive for the home directory.
Teamcenter exhibits commendable scalability, meriting an 8 out of 10. Its architecture accommodates our expanding material science firm seamlessly. With modular expansions and flexible configurations, it adapts well to increased data volumes and user growth. However, while robust, occasional complexities arise during extensive scaling, hindering a perfect score but substantiating a high ranking for its scalability.
