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.1 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 connect has the best UI compared to DOORS, Codebeamer, and PTC Integrity. It’s the clearest to use with the best usability. For example make traces between all requirements is as straightforward as clicking a button. The trace matrix view is highly configurable to get you to show anything you need. It has extensive filtering where every index in your requirement is indexed. Same with their export features, you can use default templates or create custom templates to export to PDF for all your regulatory needs like submitting documentation to FDA. This has helped us a ton without requiring much edits and letting us create up to date reviewed documents.
Speaking of review system, it’s well organized and you can set required approved and optional reviewers. Track your redlines in the tool and also view and resolve comments.
The one issue I’ve experienced is that with a large system the web app can take some time to load everything.
Teamcenter is perfect for working in large-scale projects related to manufacturing and engineering where collaboration and management of data are crucial. It is evident where the complexity of the products is high such as in automobile and aerospace industries. Some of its features may seem too elaborate for the small business with a less complex process and therefore too expensive. It is less useful in organizations that do not have complex PLM needs or have less IT capacity to implement the system.
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.
Data Management: your Parts divided into Item Types.
Data Management: You can easily add pseudo folders to segregate data inside. You don't have to look for anything now.
Change Management: Use the built-in or customize it. Now, you have workflows and can decide who is responsible for every task. It's done automatically.
Project Management - built-in MS Project, can manage tasks and still have a Gantt chart from it.
CAD integration - a lot of time saved when single source of true.
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.
I'm going to be a little blunt here. So the way how MPP and bombs are getting separated out, that is creating some issues when we want to implement end-to-end processes. The bomb team, the manufacturing or the sector manager kind of team, tries to give various features for the materials and bombs related to them, but all of those features are not available for BOP. For example, solution variant creation. When we have a variant based structure, I can create a solution variant for bombs, but I cannot create a solution variant for BOPs and this is, I would say something of a gap that Siemens should address and get it fixed. We have to do customization, but if the product is itself giving us then this is an elegant way to push it further. This is what I would say is the issue.
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
The requirements and baseline parts are easy to use. The review centre is very useable and understandable, once you understand/set up the moderation. (This last part could use some refinement.) Integration/connectability (the Connect part of Jama) is quite possible, but the useability could use some love as well.
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.
It has always been available, except for preventative maintenance which is announced beforehand. Nonetheless, we experienced one day shortage over a miscommunication about payment.
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.
Helpful and exhaustive and tailorable for our needs. Instructor was well versed and engaged. Material was a good reference and was up to date with tool. Overall, in person training was valuable for tool introduction. Trainer was an active user of the tool and worked closely with other clients. So, very knowledgeable.
Easy to reference and understand. Updated routinely to include new topics. Online training evolves to include more advanced topics and how to guides. Online training includes videos and reference guides that make it easy to perform more complex tasks. Online training is free and can be accessed from any computer.
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.
JCA is an extraordinary tool that is very simple to use and brings efficiency to the creation of requirements. It is particularly good at highlighting improvements to requirements which, when done properly and done up front in the engineering development process, will save significant time and prevent confusion downstream in the development process. It's difficult to quantify how much of a positive impact JCA would have on any individual project, but I would say it could easily save an organization more than its cost in terms of improving efficiencies and the traceability integrity throughout the entire portfolio of projects when applied correctly. This additional product from Jama is highly recommended.
Earlier, some of the companies acquired by my organization were using PTC Windchill, but the overall stability, user experience and depth of functionality which are provided by Teamcenter doesn't match with any other PLM software and thus, all the acquired companies which were earlier using PTC Windchill has now slowly started into moving towards Teamcenter.
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 is easily on the best scalable solution. The single source of product information allows us to collaborate more effectively on the product lifecycle. Also, being a cloud solution, it is pretty straightforward to scale as the maintenance required is quite low . In addition, the overall cost is also easily manageable for businesses like ours.
One experience that converted an engineer to using Jama Connect was an electronics engineer that was writing test plans. I showed them about how to write "unit" or very discrete tests and then showed them an automatic export to get the document. Thus the authoring of the document effort was taken away, they could focus on defining the test
Unfortunately I have very much struggled to embed systems engineering, requirements management and Jama Connect as part of the 'ways of working' outside the systems and electronics teams.
We chose Teamcenter because of its cost-effectiveness, and we can say that it has lived up to our expectations because we have been able to save in other more expensive tools to do what we can do in this one. The ROI has been over 40% because we have integrated it across multiple teams and it has allowed us to reduce the amount of errors in our processes and create a more centralized environment.
