In addition to the honor of being named the standout leader in requirements management software (for both Mid-Market and Enterprise), we are proud to showcase that we were awarded the Users Most Likely to Recommend badge as well as several additional medals for Spring 2023, including:
Users Most Likely to Recommend: Earned the highest rating among other solutions in this category.
Users Love Us: For products that have collected 20 reviews with an average rating of 4.0 stars.
Fastest Implementation: For products that had the shortest go-live time in its category.
Easiest Setup: The product that earned the highest Ease of Setup rating in its category.
Easiest to Use: The product in the Usability Index earned the highest Ease of Admin rating in its category.
Easiest Admin: For products that earn the highest Ease of Admin rating in their category.
Momentum Leader: Products in the Leader tier in the Momentum Grid® rank in the top 25% of their category’s products by their users.
Enterprise Leader: For products rated highly by G2 users and have substantial Satisfaction and Market Presence scores.
Download the full report to see why customers love using Jama Connect for product, systems, and software development.
Learn More About the Spring 2023 G2 Grid for the top Requirements Management Software productsHERE!
We live vicariously through the successes of our customers. The “Users Love Us” category, in particular, is a testament to our commitment to our customers.
At Jama Software®, we’re proud to be recognized as the leader in requirements management software. We’re grateful to our customers for their invaluable feedback on their experiences using Jama Connect for requirements management. We remain committed to providing them with the expert knowledge, attention, and resources they need to help them achieve their goals.
“Powerful tool that makes traceability easy. I’ve found Jama Connect to be a great platform for managing my project requirements. It has a simple user interface but also allows for a lot of customization for my own company’s needs. I work in the medical device industry and find this software essential for tracking our internal requirements as well as external regulatory requirements.”
-From review collected and hosted on G2.com, Andrew P, Lead Product Engineer – Systems and Usability – Small Business
We strive to provide our customers with the best level of service possible, and we look forward to supporting them with our expertise.
“I’ve been satisfied with Jama for years. Everything just works. The administrative tools are flexible and allow configuration to match our team’s workflow. It has highly configurable reports to allow us to export data for use in our document control system..”
-From review collected and hosted on G2.com, Allan P., Principal Test Engineer – Enterprise
From all of us at Jama Software to all of you, thank you!
G2 scores products and sellers based on reviews, gathered from their user community, as well as data aggregated from online sources and social networks. Together, these scores are mapped on their proprietary G2 Grid®, which can be used to compare products, streamline the buying process, and quickly identify the best products based on the experiences of your peers.
https://www.jamasoftware.com/media/2023/04/2023-05-02_g2-leader-spring-2023_1024x512-1.jpg5121024Jama Software/media/jama-logo-primary.svgJama Software2023-05-02 03:00:572024-01-18 00:24:19G2 Again Names Jama Connect® the Standout Leader in Requirements Management Software in their Spring 2023 Grid® Report
What is a Trial Master File in the Medical Device Industry?
A Trial Master File, also known as a TMF, is a collection of records and documentation about the creation, evaluation, and regulatory approval of a medical device. It shows the quality control procedures used in the device’s design, production, and testing to make sure it meets all applicable regulations. Regulators look at the TMF during inspections and audits to see if the device is in compliance.
How is a Clinical Trial Master File (TMF) similar to a Trial Master File?
A Clinical Trial Master File (TMF) is similar to a Trial Master File in that they are both collections of documents and records related to a specific project. However, while a Trial Master File pertains to the development, testing, and regulatory approval of a medical device, a Clinical Trial Master File pertains to the clinical trials conducted to evaluate the safety and efficacy of a medical device, pharmaceutical product, or treatment.
Both types of TMFs provide evidence of the processes and procedures used during the development and testing phases, and both are subject to review by regulatory agencies during inspections and audits.
What is an Electronic Trial Master File?
An Electronic Trial Master File (eTMF) is an electronic version of TMF that stores documents and records generated during the clinical trial process. eTMFs can replace paper-based TMFs and provide a more efficient and effective way to manage the vast amount of information generated during a clinical trial. Using an eTMF is becoming more common in the clinical trial industry due to its many benefits over paper-based TMFs, including improved efficiency, increased security and accessibility, and enhanced regulatory compliance.
To achieve compliance, organizations need defined processes for development and production and detailed traceability, from the high-level user needs through to test management. Documentation is a large part of proving compliance, and Jama Connect® makes it easy to compile the necessary documentation, like eTMFs. By automating the process, teams can focus on what’s important and avoid potential errors.
What types of regulations are TMFs or eTMFs expected to meet?
Both Clinical Trial Master File (TMF) and Electronic Trial Master File (eTMF) must adhere to various regulatory requirements depending on the jurisdiction in which the clinical trial is conducted. Some of the common regulations that a TMF or eTMF must comply with include:
International Conference on Harmonisation of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH) guidelines: This is a set of global guidelines for the development, registration, and post-approval of pharmaceuticals.
Good Clinical Practice (GCP) guidelines: This is an international ethical and scientific quality standard for designing, conducting, recording, and reporting clinical trials that involve the participation of human subjects.
The Food and Drug Administration (FDA) 21 CFR Part 11: This is a regulation that establishes the criteria under which electronic records and electronic signatures are considered trustworthy, reliable, and equivalent to paper records.
Health Insurance Portability and Accountability Act (HIPAA): This is a US federal law that requires the protection and confidential handling of personal health information (PHI) stored in electronic form.
European Union Clinical Trials Regulation (EU CTR): This is a regulation that governs the conduct of clinical trials in the European Union and aims to harmonize the regulatory requirements across EU Member States.
How can a TMF help an organization with successful product development and management?
It is important for the trial sponsor, sponsor’s representative or the CRO to ensure that the TMF or eTMF meets all relevant regulatory requirements to ensure the integrity and quality of the clinical trial data.
A Clinical Trial Master File (TMF) can help an organization with successful product management by providing a centralized repository of all the relevant documentation and information related to the development and testing of a product. The TMF helps to ensure that all necessary documentation is captured and easily accessible, which can help to:
Overall, a well-managed TMF can play a critical role in the successful development, testing, and management of a product, by providing a comprehensive and centralized record of all relevant information and documentation.
Note: This article was drafted with the aid of AI. Additional content, edits for accuracy, and industry expertise by Decoteau Wilkerson, McKenzie Jonsson, and Vincent Balgos.
https://www.jamasoftware.com/media/2023/04/NEW-2022-11-17-trial-master-file-1.png5121024Vincent Balgos/media/jama-logo-primary.svgVincent Balgos2023-04-27 03:00:052024-01-18 00:25:08What is a Trial Master File in the Medical Device Industry?
In this blog, we recap the “An Overview of the EU Medical Device Regulation (MDR) and In-Vitro Diagnostics Regulation (IVDR)” webinar.
Looking to stay ahead of ever-evolving regulations governing medical devices?
In this webinar, we discuss the continual rollout of the EU Medical Device Regulation (MDR) and In-Vitro Device Regulation (IVDR) and the impact they’re having on the medical device industry.
Vincent Balgos, Director of Medical Device Solutions at Jama Software and Saby Agai, Sr. Consultant at Jama Software, provide a high-level overview of the new regulations, along with general industry observations and future considerations for organizations with medical products marketed in the EU market area, including:
New classifications, grandfathering clause, and risk management requirements
The number of notified bodies, backlog, and remediation efforts for placed products
Future considerations regarding the compliance compatibility of IVDR & FDA and traceability
Finally, learn how the Medical Device Framework in Jama Connect® can help streamline your compliance efforts and ensure your products meet all the necessary regulatory requirements.
Below is an abbreviated transcript and a recording of our webinar.
Why it Makes Sense to Store Cybersecurity Risk Management Items Inside a Requirements Management System
Saby Agai: So, in the first part of the webinar we will talk about the EU medical device regulations. There is a small agenda to that. Basically, we would like to show the key changes and challenges that the MDR means compared to the MDD. We would also like to talk a little bit about what we see as the challenges for the process transformation of the medical device developers and also a bit of discussions with the race on the timeline for the MDR. The second section is on the MDR for the MedDev engineering. So basically, how the engineering teams can do anything with the MDR. We’ll talk about harmonized standardization. How does that fit in the concept of the MDR? And some of the medical device best practices that we would recommend. So the medical device regulations now has quite a bit of history because the MDR is valued also for existing [inaudible 00:04:15] devices and also for all the new devices.
The medical device regulations entered into force historically in May 2017, and there was a bit of extension period in 2020 that the certificates issued under the MDD before the MDR remained valid up to four additional years. So it was a bit of a time extension for manufacturers to migrate the legacy devices to the MDR. Recently 2023, the EU commission had the new rule based on 607 was the number of it on the time extension for the medical device regulations. So there are two-time extension now in force for December 2027 and 2028 for all devices. As part of this modification, the commission removed the sale of period from the original context of the Medicaid device regulation.
Three key area that we would mention that we see as key challenges with the MDR is first is the technical documentation. So because of the legacy medical devices has to be reclassified in a context of the new MDR, those manufacturers highly likely will face it extended set of documentation for market clearances in the EU. It’s particularly true for software as a medical device because, basically the class one level has removed by legislation for all software as a medical device. The other thing on the technical documentation is that the MDR is far more prescriptive about the requirement content of the technical documentation, and it’s particularly true and there are more detailed requirements needed for the quality management system. So the manufacturer will have to ensure that they not only have full access and control for the documentation of the device, but also they should keep the eye on the market and the vigilance market, post-market vigilance area, as well as publication or new common specifications.
Agai: So there is a bit of higher focus on the post-market activities in the context of the MDR. And the technical documentation basically has two key parts in Annex II, annex III it’s detailed. Annex II there is a list of requirements for the technical documentation itself for the device design, and also, in Annex III, we see details or requirements for technical documentation post-market surveillance. So nothing particularly new, only an extended set of expectation and requirements for all these contents. Little note something on the technical documentation. So historically, the technical documentation has a tradition to be seen as a burden on the med tech developers and additional administrative work. And quite often, at the end of the development cycle, there is a massive effort made to make what is documentation available for regulators and also for market clearance. It definitely could require very intense administrative work from the engineering sometimes stress involved and also, the content creation has not much help or not much support for the regional engineering activities, which is the development.
So these content created purely to support the market access activities and it should not necessarily should be a case, though. So, for example, we in Jama has a medical solution. It’s a example proven a tool actually can support both med tech developers to enhance the development efficiency as they develop a new device as well as to support these technical documentation needs at the same time. So it’s a opportunity also for organizations to get most out of using a tool when they thinking about to ease the burden of the medical device regulation technical documentation part.
Agai: Thirdly but not lastly, there was a new, particularly in EU requirements for the unique device identifier. So basically, 2021 was a deadline to register an MDR UD MDR devices with the UDI in the [inaudible 00:09:02] framework, and for the IVDR, it’s 2022. Looking into purely on the numbers, we could say that the content of the MDR compared to the MDD is actually four time heavier. So the extent and the legal tax basically is four time more. There are five plus on axis that we can see, and there is a special attention on safety and patient safety particularly because 293 times mentioned the safety word in MDR where in the MDD was the 24. All these numbers also telling that the regulators in EU want to have higher scrutiny compared to the MDD, and they also have more details on that level of expectation that they would like to see from manufacturer. And there is a definite focus on patient safety that we can see.
Two more things to mention is that quite often, in the context of the MDR, the legacy devices should be reclassified into a higher level class. So it means that the quality management process support is more intense, and more support expected. More activities and works are expected from the manufacturer to keep the same device basically on the market. It also could mean that companies should take a step for high-level maturity as an organization and it’s true also for the design and device development activities. So one of the challenge with that is that if we talk about the same device with higher regulatory scrutiny, how do we retain and enhance profitability? Because the administrative burden is definitely something that goes towards the cost part of the profitability. So the design and development goes under higher level of process expectation in that sense, and it goes higher level of design documentation needs as well. So one of the advantages using the tool in general medical device environment that the medical solution can ease actually this work and enable a bit quicker, and the developers can leverage a little bit more help on these challenges.
https://www.jamasoftware.com/media/2023/04/BLOG-RECAP-Medical-Device-Webinar-Social-Image.png5121024Vincent Balgos/media/jama-logo-primary.svgVincent Balgos2023-04-20 03:00:122024-01-18 00:27:52[Webinar Recap] An Overview of the EU Medical Device Regulation (MDR) and In-Vitro Device Regulation (IVDR)
Jama Connect® Features in Five: Using Jama Connect with a Quality Management System (QMS) for Medical Device & Life Sciences
Learn how you can supercharge your systems development process! In this blog series, we’re pulling back the curtains to give you a look at a few of Jama Connect®’s powerful features… in under five minutes.
In this Features in Five video, Steven Pink, Senior Solutions Architect at Jama Software®, will provide insight into how Jama Connect is commonly used in the context of a medical device Quality Management System (QMS.)
In this video, we will:
Provide insight on how Jama Connect is commonly used in the context of a medical device quality management system
Demonstrate key features that provide value to those responsible for quality and regulatory matters
Offer clear guidance on how Jama Connect – a requirements management solution – supplements a separate quality management system within a cohesive ecosystem of complimentary applications
VIDEO TRANSCRIPT:
Steven Pink: Welcome to this segment of Features in Five. I’m Steven Pink, a senior solutions architect at Jama Software and today I’ll be giving an overview to help provide some insight into how Jama Connect is commonly used in the context of a medical device quality management system.
We’ll demonstrate some of the key features that provide value to those responsible for quality and regulatory matters and clear guidance on how Jama Connect, a requirements management solution supplements a separate quality management system within a cohesive ecosystem of complimentary applications.
We often work with medical device or life science companies that have some form of quality management system whether that be paper-based or an eQMS and they’re working to introduce a requirements management solution like Jama Connect for the first time.
For individuals with a quality and regulatory background that have not yet worked in an environment using a formal requirements management solution, this can seem like a foreign and potentially disruptive change to a well-defined process.
Pink: So before we provide some insight to help address that common concern, we want to provide some context as to why an organization would want to introduce Jama Connect in the first place. Prior to using a formal requirements management solution, engineering and R&D are often left managing requirements related data during development in documents, spreadsheets and tools like Jira, Confluence, or SharePoint that are not designed to support complex requirements management.
In this type of scenario, engineering often finds it difficult to manage and maintain complex traceability as they work. So they often leave it to be completed at the end of a phase or milestone as opposed to maintained in real time. This often leads to gaps or errors being identified late in development which is significantly more costly to address the later they’re identified. In addition to having difficulty maintaining traceability, engineering often struggles to manage change to requirements and understand the full impact of each change.
They’ll find it hard to keep data in sync between requirements stored in documents or spreadsheets and other tools like Jira or Azure DevOps where data resides in silos. They’ll often waste a lot of time or effort compiling documentation for their design history file at the end of a given phase before these artifacts can be signed off and stored as an auditable record in a document control system. As products increase in complexity and regulatory guidelines continue to increase in rigor, these challenges grow exponentially for engineering.
To help address these challenges, Jama Connect provides engineering and product teams with a working environment to manage requirements, risks, tests and the traceability between these items in real time. We call this managing live traceability.
Pink: From a quality and regulatory perspective, Jama Connect’s relationship rule diagram provides a governing structure to ensure that requirement traceability is maintained following proper design controls and quality procedures. This structure makes it simple to manage change, perform impact analysis, and ensure traceability coverage throughout development.
The first thing we see when working on a project in Jama Connect is the dashboard with traceability rules. This makes it easy to understand the expectations for traceability and identify exceptions through dashboard widgets, such as gaps in test coverage or finding unmitigated risks.
With data living and Jama Connect, managing documentation and traceability becomes easier. Once documentation has been authored, it can be sent for a formalized review. Cross-functional teams can utilize the review center to conduct iterative reviews and significantly increase the quality and efficiency of the feedback being given.
Once all items for a given release have been reviewed and approved, these items can automatically transition into an accepted and blocked state, ensuring that changes are not made to approved items unintentionally. When the time comes to generate auditable documentation, Jama Connect allows teams to automatically or manually capture baselines and export these baseline documents out of the system to be signed off in a separate document control system as an auditable record. This process reduces the time spent manually reworking documents as part of the QMS process. And these document export templates can easily be customized to match existing internal quality standards and ensure consistency in the way requirements and other details are documented.
In the end, Jama Connect can help engineering team more easily manage their work and simplify the process of maintaining traceability. As a byproduct of their efforts, quality, and regulatory teams are provided with higher-quality auditable documents without making changes to their existing quality management systems.
https://www.jamasoftware.com/media/2023/04/FIF-QMS-4.jpg10801920Steven Pink/media/jama-logo-primary.svgSteven Pink2023-04-14 03:00:232024-01-18 00:30:54Jama Connect® Features in Five: Using Jama Connect with a Quality Management System (QMS) for Medical Device & Life Sciences
In this blog, we preview whitepaper, “The Top Challenges in Industrial Manufacturing and Consumer Electronic Development” — Click HERE to read the entire thing.
The Top Challenges in Industrial Manufacturing and Consumer Electronic Development
From supply chain disruptions to digitization – learn more about what development teams are up against and get expert suggestions for how to overcome them
PART I: The Top Challenges in Industrial Manufacturing and Consumer Electronic Development
Industrial manufacturing has always been a cornerstone of economic growth and development worldwide. Over the last few years (or more), the
industrial manufacturing sector has undergone significant transformation; from the introduction of automation and robotics to advanced analytics.
Today, industrial manufacturers are facing a host of new challenges that are forcing teams to rethink their strategies and adapt to changing market influences and demands.
The need to increase operational efficiency while also cutting expenses is one of the most pressing issues facing industrial manufacturing — a challenge not unique to this industry alone. Manufacturers are under a lot of pressure to optimize their processes, cut lead times, and boost product quality due to intense competition and rising customer expectations. Teams must also figure out how to lower production costs and waste while adhering to strict industry regulations. To be boost innovation and optimize operations, teams need to have not only an in-depth knowledge of the production process, but also access to cutting-edge technologies like the internet of things (IoT), artificial intelligence (AI), product development platforms, and machine learning (ML).
In this whitepaper, we’ll explore some of the challenges industrial manufacturing teams are up against and offer expert insights and strategies on how to work through them.
CHALLENGE #1: Supply Chain Disruptions
The industrial manufacturing sector may continue to endure supply chain disruptions as a result of the ongoing COVID-19 epidemic — primarily due to a lack of workers, raw materials, and component parts. Outside of the pandemic, supply chain interruptions are also being caused by trade conflicts and tariffs.
Supply chain disruptions continue to be a complex challenge for industrial manufacturers, and engineers play a critical role in identifying and mitigating these risks. By developing robust supply chain management strategies and leveraging innovative and modern technologies, engineers can help to reduce the impact of disruptions and ensure a more efficient and reliable manufacturing process.
As demand for environmentally friendly and sustainable products rises, firms must adopt more sustainable procedures in their business operations. This can entail cutting back on carbon emissions, switching to renewable energy, and reducing waste and pollution.
Consumers in the manufacturing sector have become more and more demanding of environmental sustainability. As the world’s population shifts to be more environmentally concerned, customers are increasingly seeking out goods that were produced using sustainable methods, such as using renewable energy sources, lowering carbon emissions, and limiting waste and pollution.
While environmental sustainability is of vital import for society (and meeting modern ethics standards), it may also be very advantageous to a business’s bottom line. Manufacturers who place a high priority on sustainability can significantly lessen their energy and resource consumption, improve the reputation of their brands, and boost their market share and consumer loyalty.
Today’s forward-thinking industrial product, systems, and software developers are embracing a variety of environmentally friendly practices and modern technologies to both optimize production and satisfy this growing demand for environmental sustainability.
CHALLENGE #3: Automation and Digitalization
The industrial sector is changing as a result of the growing use of automation and digital technology, but these changes also bring issues. Manufacturers must upskill their staff, invest in new technology, and manage the risks related to cyber-attacks and data security.
In order to maximize productivity, cut costs, improve product quality, and adapt to changing customer demands, businesses across all sectors, including industrial manufacturing, are automating and digitizing more of their processes. By enabling the automation of production processes and the use of data analytics to enhance operations, automation and digitalization technologies are revolutionizing the
manufacturing sector.
Here’s how manufacturers are leveraging new technology:
Robotic automation: It is possible to boost productivity, reduce labor expenses, and improve product quality by using robots and other automated technologies to complete tasks that were previously completed by hand.
Digital twin technology: Manufacturing processes are simulated and improved using digital models of physical systems in the real world. By spotting and fixing issues before they arise, manufacturers can increase the quality of their goods while lowering costs.
Predictive maintenance: In order to predict when repairs are required and prevent unscheduled downtime, predictive maintenance uses data analytics and machine learning algorithms. This increases equipment dependability and lowers maintenance costs.
Internet of Things (IoT): The IoT involves the use of sensors and other devices to collect data on processes and equipment. The data can then be used to optimize processes, reduce downtime, and improve product quality.
Automation and digitalization technologies are being adopted in industrial manufacturing for a number of reasons, including efforts to lower costs, increase efficiency, and meet shifting client demands. By lowering the need for human labor and enhancing quality control, this move toward automation can also increase safety.
There is a talent deficit in the industrial manufacturing sector, notably in fields like engineering, computer science, and data analytics. Manufacturers must invest in training and development initiatives to recruit and keep people in order to meet this challenge.
The labor shortage in industrial manufacturing has been an ongoing challenge for many years, and the COVID-19 pandemic only exacerbated it. Several factors play into the labor shortage, including an aging workforce, a lack of skilled workers, and shifting attitudes towards traditional work among younger generations.
To overcome the labor shortage, teams are implementing a range of strategies, including:
Investing in automation and robotics: Automation and robotics reduce the need for manual labor. By investing in automation technology, organizations can reduce their reliance on human labor costs and increase productivity.
Offering training and upskilling programs for employee attraction and retention: Many organizations are offering programs to their current employees to help them acquire new skills and advance their careers. The cost of replacing an employee is shockingly expensive. In fact, studies show that every time an organization replaces a salaried employee, it costs six to nine months’ salary on average. By investing in their employees, manufacturers can increase employee retention and reduce the need to hire new workers.
Implementing flexible working arrangements: Organizations across all industries are moving towards more flexible working arrangements, such as remote work and flexible scheduling, to attract and retain workers who are looking for a better work-life balance.
Collaborating with educational institutions: Many industrial manufacturing organizations are partnering with educational institutions to create training programs and apprenticeships that prepare students for careers in manufacturing.
Offering competitive incentive and benefits packages: Offering competitive compensation and benefits packages to attract and retain workers might include; higher salaries, flexible working environment, competitive health benefits, retirement plans, and other incentives.
This has been a preview of The Top Challenges in Industrial Manufacturing and Consumer Electronic Development whitepaper. Click HERE to read the entire thing!
https://www.jamasoftware.com/media/2023/04/2023-04-11-ice-paper-1.jpg5121024Steven Meadows/media/jama-logo-primary.svgSteven Meadows2023-04-11 03:00:092024-10-03 09:51:40The Top Challenges in Industrial Manufacturing and Consumer Electronic Development
In this blog, we recap the “Why it Makes Sense to Store Cybersecurity Risk Management Items Inside a Requirements Management System” webinar.
In this webinar, “Why it Makes Sense to Store Cybersecurity Risk Management Items Inside a Requirements Management System”, learn about the implementation of the Threat and Risk Analysis (TARA), the centerpiece of the new Automotive Cybersecurity standard ISO 21434.
Many companies currently use spreadsheets to develop TARAs, which can be challenging when managing large sets of requirements across distributed teams and car line variants. In this webinar, we’ll examine why a requirement management system (RMS) is well-suited to manage the TARA work product and can make a significant impact on managing this data across teams, supporting compliance audits, and assessments.
Attendees will gain insights into TARA’s complexities and how the right tooling solution can make a difference in managing this data across teams, supporting compliance audits and assessments.
Key Takeaways:
The Threat and Risk Analysis or TARA is the centerpiece of the ISO 21434 Automotive Cybersecurity standard
Overview of TARA
ISO 21434 compliance requirements when implementing TARAs
Why an RMS is well-suited to manage TARAs
Below is an abbreviated transcript and a recording of our webinar.
Why it Makes Sense to Store Cybersecurity Risk Management Items Inside a Requirements Management System
Kevin Dibble: Thanks, Juliet. Okay. I’m going to just go through the agenda and then get right into 21434. I’ll start with a high-level introduction and then get into the focus of our topic today, which is the threat and risk analysis, which is a centerpiece of 21434, also known as the TARA. And then make an argument for the management of a TARA using an RMS or a requirement management tool. And then Steve will take over and talk about what that would look like in Jama software and summarize with some key points of managing TARAs in Jama versus some traditional methods. And then we’ll have time for some questions.
So with that, again, this is going to be a very high-level overview of 21434. I have a feeling that some of you have worked in cybersecurity for some time, others are just brand new to the term. And so, I want to touch on this as a basis for the rest of the discussion.
And so, first, what is 21434? It is the automotive industry standard for developing cyber secure systems. After several years of review, it was approved in August of 2021 as the method for developing cyber secure systems. In terms of the standard itself, it’s structured and uses a lot of the same terminology as the functional safety standard called ISO 26262. So if you’re familiar with functional safety, then this standard will make a lot of sense the way that it’s organized. Some of the terms such as an item definition, a concept phase, a cybersecurity goal, even TARA parallels functional safety terms like functional safety concept, functional safety goals, or the HARA, Hazard and Risk Analysis. And so, that’s just a reference point as you’re learning about this new standard. Now as far as its scope, it covers or it applies to passenger vehicles and cargo vehicles.
So just a little bit different than ISO 262 there, passengers would include buses, commercial or non-commercial. I think even tripods and some of those other types of motorcycle hybrid type of devices are in or vehicles are in scope as well. It applies to series production and it uses a lifecycle that starts at the request for a quotation for an item. And I’ll define that in a little bit and goes all the way through to the end of cybersecurity support. So like functional safety, we’re not talking about supporting the risks and the hazards associated in this case with threats from attackers leading up to SOP, but it extends far past that. In fact, in 21434, instead of using the term SOP or start of production, which is a critical milestone in any automotive product development program, they call that milestone the release to post-development.
Dibble: And I want to camp on that for just a second because it raises a really important point and it’s very relevant to what we’re going to talk about regarding the TARA. Release to post-development. So the automotive industry is under a lot of change and OEMs want to be or are becoming mobility providers and services will be sold after the car is released. And some of those services weren’t even imagined at the time the car was sold. That’s so different than where the automotive industry was even five years ago. And this standard recognizes that and embraces it along with another important concept, which is that the world of cybersecurity and the landscape for threats and the technologies and the tools that are used to attack vehicles is constantly changing. And so, at the release to production, what is assumed to be protected in terms of say a set of cryptographic keys or a communication bus might be more vulnerable in five years than it was when the car was released because of new techniques, new methods, new tricks, new hacks, and other things that have been discovered.
And so, that’s an important concept because it feeds to our idea that we’re going to get into about the TARA as a living document, as a living asset that begins all the way at the concept phase at the beginning of the high-level architectures of the item or the system in the car. And extends all the way until the end of life for cybersecurity support, which is 10, 15 years down the road. Now, the 21434 has both requirements for developing cyber secure systems, is kind of what I’m showing you on the right, but it also has process requirements. And to that end, there is an audit of the process and an assessment of the results of your project according to 21434. That assessment piece is important for our discussion because when we think about the TARA and the pieces of it or the items of the TARA, then we have to think in terms of what are the evidences we need to leave behind and produce in order to pass an assessment, very important consideration.
Dibble: And so, we have audits for the processes and then assessments for the end result. So that’s very brief overview of 21434. I want to make sure I leave you with the… If you remember anything about 21434 besides the TARA, you’ll hopefully remember this, is to manage unreasonable risk of damage to road users due to a malicious attack to a vehicle or a vehicle data, confidentiality, integrity and availability. Let me unpack that for just a second. Unreasonable risk, this is when you get into a car, when you operate a vehicle, you assume some risk. But that risk doesn’t include driving down the highway at 70 miles an hour, turning right and the car going left or the headlights going off while you’re on the highway at night. It applies to road users. That’s the people that use the road, the driver, the passengers, and the people surrounding it.
All of that is our scope for how we’re going to define threats according to 262 and then mitigate them against malicious attack due to… That’s the cyber aspect of this. And then what’s being attacked and what are we protecting? We’re protecting vehicle systems, functions, data, et cetera. We call them assets according to their properties, confidentiality, integrity and availability. There could be more properties, that’s the CIA that we’re protecting. Why is cyber such a hot topic? Well, I would say there’s several reasons, but here’s two of the big ones. On the left of my slide, the advent of the connected car coupled with the automated driving functions. I’m not going to read through all the stats here, but the connected car is here. It’s 2 billion in terms of the market in 2021 to grow to $5.3 billion in 2026. And the connected car is accessible via the internet, accessible via Bluetooth and other network interfaces, which all result in attack services. It also has a lot more software.
https://www.jamasoftware.com/media/2023/03/Cybersecurity-Risk-RM-.png5121024Steve Rush/media/jama-logo-primary.svgSteve Rush2023-03-30 03:00:042024-04-05 13:27:22[Webinar Recap] Why it Makes Sense to Store Cybersecurity Risk Management Items Inside a Requirements Management System
In this blog, we recap our press release, “Jama Software® Announces Insurance Framework to Simplify Insurance Product Development ” – To read the entire thing, click HERE
Jama Software® Announces Insurance Framework to Simplify Insurance Product Development
Streamline and Accelerate Insurance Product Development with Jama Connect®
Jama Software®, the industry-leading requirements management and traceability solution provider, has released an insurance framework and dataset that streamlines and simplifies product development for the insurance industry.
With increased challenges and a changing landscape, insurance carriers are facing competitive pressures related to growth and profitability. Carriers can now use Jama Connect® to make product development more efficient and deliver high quality products on time and on budget.
“Insurance carriers are facing increased pressure to bring new and competitive products to market, across multiple jurisdictions and lines of business. At Jama Software, we’ve developed a customizable framework to allow our insurance customers to create a scalable and standardized approach to managing their up-front product requirements through downstream systems development. This framework allows carriers to innovate, bring products to market quicker, and ultimately better serve their customers.”
Steven Meadows, Solutions Lead for Insurance Industry, Jama Software
“With the increased complexity associated with developing insurance products, the traditional method of insurance product development is no longer viable.” stated Tom Tseki, Chief Revenue Officer at Jama Software. “The challenges associated with business analysts leveraging spreadsheets to try to ensure everyone is working off a live single source of truth is nearly impossible. Business analysts are constantly chasing development teams to get progress and status updates while trying to manage changes and inform all the upstream and downstream activities/teams of the changes before too much work is completed. This disjointed and out-of-sync approach means a lack of real-time visibility and control which results in significant rework, increased costs, and product delays.” Tseki continued.
“A real solution for managing insurance product requirements and specifications across multiple states, products, and departments has long been overdue. Jama Connect is that solution, bringing business units and IT together on a common requirements platform. It’s intuitive enough for non-technical users, configurable around existing processes and toolsets, and sophisticated enough to support everything from requirements reuse, comparisons, collaboration, change control, integrated test management, and more. As product portfolios get more complex, it’s important to manage requirements so they don’t manage you. The Jama Connect insurance framework places your organization in the driver’s seat – increasing product quality and standardization, speed to market, and scalability. It’s a game changer.”
With effective requirements management and Live Traceability™ in Jama Connect, insurance carriers can easily manage new product requirements from ideation through to implementation, enhancement, and revisions — enabling them to meet regulatory requirements, maximize development efficiency, and accelerate speed to market.
If you want to learn more about how Jama Connect can help accelerate insurance product development, please download the datasheet below, or click here to speak with one of our experts and book a free trial.
If you want to learn more about how Jama Connect can help accelerate insurance product development,
please refer to our datasheet: Download the Datasheet
About Jama Software
Jama Software is focused on maximizing innovation success for complex development. Numerous firsts for humanity in fields such as fuel cells, electrification, space, autonomous vehicles, surgical robotics, and more all rely on Jama Connect® to minimize the risk of product failure, delays, cost overruns, compliance gaps, defects, and rework. Jama Connect uniquely creates Live Traceability™ through siloed development, test, and risk activities to provide end-to-end compliance, risk mitigation, and process improvement. Our rapidly growing customer base of more than 12.5 million users across 30 countries spans the automotive, insurance, financial services, medical devices, semiconductor, aerospace & defense and industrial manufacturing industries. For more information about how Jama Connect can help Insurance industries, please visit: Jama Software Solutions: Financial Services and Insurance
https://www.jamasoftware.com/media/2023/03/2023-03-15-insurance-release-1.jpg5121024Steven Meadows/media/jama-logo-primary.svgSteven Meadows2023-03-15 06:30:512024-01-18 00:47:30Jama Software® Announces Insurance Framework to Simplify Insurance Product Development
In this blog, we recap the “Launch Your Aerospace & Defense Product Development Processes with Jama Connect®” webinar.
In this webinar, we discuss exciting new features in our updated Jama Connect® for Aerospace & Defense framework. These updates include refreshed solutions for cybersecurity, the DoD Range Safety Requirements Library, and other libraries of standards.
Also, Cary Bryczek, Solutions Director for Aerospace & Defense at Jama Software®, shares best practices in the Jama Connect platform and demonstrates significant new features that can help you further enhance your aerospace and defense product development processes, including:
ARP 4761A – Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment
DO-326A – Airworthiness Security Process Specification
US CFR Parts 21-57 Pre-imported Libraries and Usage
Defense MBSE and Digital Engineering Guidance
NASA and Air Force Range Safety Requirements
European Cooperate with Space Standards (ECSS) Pre-Imported Libraries
Below is an abbreviated transcript and a recording of our webinar.
Launch Your Aerospace & Defense Product Development Processes with Jama Connect®
Cary Bryczek: Let’s get started. So the Airborne Systems Solution. So when we say solution, it’s really a complete set of frameworks, example projects and the procedural documentation that goes along with that. It’s really intended to accelerate your implementation of Jama Connect, especially those that are developing Airborne Systems and the Airborne Systems components that are going to live on these aircraft. When you utilize these frameworks, you can either have zero set up time, so we’re developed the solution to align with the standards and you can also tailor it. So your consultant who does team with you could help you tailor it to meet your very specific business needs as well. So it’s really designed for any organization, whether you’re a startup in the Airborne Systems world or whether you’re a longtime developer of aircraft.
The Airborne Systems Solution is really designed to help you ease the path to regulatory compliance, to help the engineers produce the evidence and collect that evidence in coordination with the regulatory requirements and the industry standards that are used that are requiring the acceptable means of compliance. Today’s. In today’s world, there is a lot of new engineers that are being employed in Airborne Systems development. And really this particular template is helpful to them because it really gets them to understand “How am supposed to do development?” We all know that Airborne Systems development has the most onerous and rigorous standards of any industry. And teaching our new engineers is very time-consuming. So having this template with all of the guidance built into it and the procedure guide really helps our new engineers to get started.
So there’s three components to the Airborne Systems Solution that what we call the data set, a procedure guide, and the success program. The data set essentially is what you get when you install Jama and it has the templates, it has a ready to use configuration that matches those regulations. It has all of the item types, all of the reports, all of the best practices built right in. And then the procedure guides and the documentation of the reports essentially show you how the Airborne Systems template is meeting the industry standards. So how does it meet ARP4754, how do you use the solution to meet DO-178. That’s sort of a thing.
Bryczek: And then we also pair our solution with specific consulting. So our consultants already are very familiar with the regulations with working with our customers that have been delivering and developing Airborne Systems already, as well as systems engineering best practices. Some of our customers have interesting supply chain needs. And so they might want to use an additional tool that we package called data exchange. That’s just an add-on to the solution.
So when we look at the framework itself, there are a lot of industry standards that we support. These industry standards are the acceptable means of compliance that the FAA and EASA recognize in order to meet type certifications. So we have those processes that come right out of those standards built right in to the framework. So that framework consists of specially configured item types, pick lists and views of that information. Our relationship rules are aligned to the types of trace matrices these particular standards are calling for. We have workflows and guidance for how you conduct reviews of information as well. We have the libraries of standards, so if you need to comply with the different CFR parts, we actually have those pre imported. This is something new that we’ve added and we’ll talk about that a little bit more. The framework includes these document export templates as well as risk templates and analysis templates and more.
Now this is a company with a procedure guide. So along with not only just the template itself in Jama, we give you the procedure guide. You can take this guide and tailor it to meet your specific needs as well. This procedures guide is updated. So as a subscriber to the Airborne Systems Solution, any updates we make or new releases like what we have right now is included with your subscription. It just makes it easy for everyone to kind of understand “How do I use Jama if I need to meet these industry standards?”
Bryczek: Also with this particular release is the configuration and update guide. So this is new this time around. This particular guide gives a very detailed description of the entire dataset. It includes all of the types that we’ve defined, all of the pick lists that are defined, all of the relationship rules, all of the workflows. So if you need to update from your existing Airborne Systems Solution and take in aspects of the new release, it makes it really easy for you guys to update as well. This might be something as well… So if you tailor from your existing Jama solution and you want to keep track of that, something like this might be a really great way for you to document your own implementation of Jama itself.
So exciting. This is one of the new things. So we have for cybersecurity, DO-326A is an acceptable means of compliance for doing security analyses. There are a significant number of new item types that have been added to the solution that comprise our cybersecurity solution as well as how do you really do the airworthiness security analysis. Essentially there are seven steps to do this particular type of analysis. This really starts with developing your PSecAC. And for those of you who are maybe new to Airborne Systems development or are not familiar with DO-326 or cybersecurity, it is a process that’s sort of done in tandem with both the system development and safety. But this is different in that this is analyzing the intentional unauthorized electronic interaction. So it’s really designed to find ways that hackers or bad actors might be accessing parts of the Airborne Systems that you don’t want them to.
https://www.jamasoftware.com/media/2023/03/BLOG-RECAP-Launch-Your-AD-Product-Development-Processes-with-Jama-1-1.png5121024Cary Bryczek/media/jama-logo-primary.svgCary Bryczek2023-03-09 03:00:092024-01-18 00:50:15[Webinar Recap] Launch Your Aerospace & Defense Product Development Processes with Jama Connect®
Jama Connect® Features in Five: Finding Information
Learn how you can supercharge your systems development process! In this blog series, we’re pulling back the curtains to give you a look at a few of Jama Connect®’s powerful features… in under five minutes.
In this Features in Five video, Carleda Wade, Senior Consultantat Jama Software®, walks viewers through various ways of filtering and finding information within Jama Connect.
In this session, viewers will learn:
How to find information within Jama Connect®
Use search boxes throughout the application
Use facet filters to narrow search results
Interact with predefined filters
Create and manage new filters
Follow along with this short video below to learn more – and find the full video transcript below!
VIDEO TRANSCRIPT:
Carleda Wade: In this session, we will learn how to find information within Jama Connect, use search boxes throughout the application, use facet filters to narrow search results, interact with predefined filters, and create and manage new filters. So now let’s jump into our Jama instance.
Now we’re going to show you a couple different ways that you can search throughout the software. So here on our homepage we have this search bar. So let’s say I’d like to look for scheduling, since we just did manual scheduling in the previous session.
If I click on submit, you’ll see all these results. These results will show anytime the word scheduling shows up in any of the various projects. As you can see, this is a lot of results. So maybe we want to apply a filter so that we can narrow our list. So here I can click on filter items, and maybe potentially search for a keyword.
But I can also narrow this by looking at a certain project. So we’ve been working in our Jama 101, and then maybe I want to just look at system requirements, and let’s say stakeholder requirements. So here you’ll see are just the items that meet those two requirements. Another way to do this is by an advanced search. If I do an advanced search, first I can create a new filter. So let’s say I want to look for scheduling in my Jama 101 project, and I want to look at system requirements with the keyword of scheduling. When I do this, you can see here that I can preview, and that there will be three results. So if I click on there, it will give me a preview. And I can choose to save my filter. So now, essentially I’ve created a brand new filter.
Next, if I click here from my project explorer on filters, you’ll be able to see all of the various filters that are available. If I click on bookmarks, you’ll see this is the one that I just created, scheduling. And this little icon here indicates that it’s been bookmarked, or it’s become one of my favorites. If I go through the all, you can see other filters that have already been created within the system.
Wade: So let’s take a look at what happens when you right click. So when you right click on a filter. There are a few different options. So I could choose to remove this from my bookmarks if I so to desire. I could also choose to duplicate this. So let’s say for instance, this particular filter houses a lot of good information, and I want to be able to modify that information without changing the original filter. Maybe I would first duplicate this filter, then add onto it. I could also choose to edit the filter and view the criteria. If so desired, I could delete it. Another way to do this is by an advanced search. If I do an advanced search, first I can create a new filter. So let’s say I want to look for scheduling in my Jama 101 project, and I want to look at system requirements with the keyword of scheduling.
When I do this, you can see here that I can preview, and that there will be three results. So if I click on there, it will give me a preview. And I can choose to save my filter. So now, essentially I’ve created a brand new filter. Next, if I click here from my project explorer on filters, you’ll be able to see all of the various filters that are available. If I click on bookmarks, you’ll see this is the one that I just created, scheduling. And this little icon here indicates that it’s been bookmarked, or it’s become one of my favorites. If I go through the all, you can see other filters that have already been created within the system.
So let’s take a look at what happens when you right click. So when you right click on a filter. There are a few different options. So I could choose to remove this from my bookmarks if I so to desire. I could also choose to duplicate this. So let’s say for instance, this particular filter houses a lot of good information, and I want to be able to modify that information without changing the original filter. Maybe I would first duplicate this filter, then add onto it. I could also choose to edit the filter and view the criteria. If so desired, I could delete it.
Wade: Another really interesting thing to see is if I choose to apply the filter to the explorer. When I do that, you’ll see that only the items that meet the filter requirements show up, instead of the full exploratory like it did before. So that’s pretty interesting.
Going back in, the last option is send for review. So let’s say for instance, for this stakeholder requirements in draft status. If I wanted to go ahead and move these requirements from draft, I could choose right here from the filtered screen to send this for a review. And it would just open up in the review center. Another really interesting thing to see is if I choose to apply the filter to the explorer. When I do that, you’ll see that only the items that meet the filter requirements show up, instead of the full exploratory like it did before. So that’s pretty interesting.
Going back in, the last option is send for review. So let’s say for instance, for this stakeholder requirements in draft status. If I wanted to go ahead and move these requirements from draft, I could choose right here from the filtered screen to send this for a review. And it would just open up in the review center. Another way to be able to search is if we go to our activity stream. So here you can see there’s a little search bar for our activity stream. So let’s say I also typed in scheduling here. Or let’s say I wanted to see what Sarah has done within my stream. Here you can see all of the activities that Sarah has done within my instance here.
Another way to search for information is, let’s go back into our manual scheduling and go to our activities. Here you’ll see we have yet another search function, if we’d like. And then also, we could apply filters here if we so desire. Also, whenever using filters such as either here or any of the locations, we can also use built in operators. So let’s say we wanted to look for intelligent and scheduling in our project. You’ll see here that it comes up.
https://www.jamasoftware.com/media/2023/02/FIF-Finding-Information-5in5-intro.jpg10801920Carleda Wade/media/jama-logo-primary.svgCarleda Wade2023-03-03 03:00:562024-01-18 00:52:40Jama Connect® Features in Five: Finding Information
Jama Connect® vs. IBM®DOORS®: Total Cost of Ownership: A User Experience Roundtable Chat
Increasing industry challenges and complexities are pushing innovative organizations to consider modernizing the tool(s) they use for requirements management (RM). In this blog series, Jama Connect® vs. IBM® DOORS®: A User Experience Roundtable Chat, we’ll present several information-packed video blogs covering the challenges that teams face in their project management process.
In the 10th and final episode of our Roundtable Chat series, Preston Mitchell – Sr Director, Global Business Consulting at Jama Software® – and Susan Manupelli – Senior Solutions Architect at Jama Software® – discuss the total cost of ownership in product management.
To watch other episodes in this series, click HERE.
Watch the full video and find the video transcript below to learn more!
VIDEO TRANSCRIPT:
Preston Mitchell: All right. Welcome everybody, to episode 10 in our vlog series. Today, we’re going to be talking about total cost of ownership. I’m Preston Mitchell, the senior director of solutions at Jama Software, and I’m joined by my colleague, Susan Manupelli. Susan, do you want to introduce yourself?
Susan Manupelli: Sure. My name’s Susan Manupelli. I’m a senior solutions architect here at Jama Software, but I came from IBM, where I was a test architect for the last 20 years on some of their requirements management tools, so primarily Rational DOORS Next Generation and RequisitePro actually, before that.
Preston Mitchell: Excellent. Like Susan, I was a former IBM-er as well, so a user of many of those tools. Today, as you can see, we want to talk about kind of three main categories of total cost of ownership, IT infrastructure, so these are things like the actual physical hardware, the FTE administration costs, so like upgrades, maintenance, and then also the opportunity costs of when you do not adopt best-in-breed tools and processes. Why don’t we first start it off with the IT infrastructure costs? You know, Susan, in your experience with other RN tools, what have you found to be the challenges in this area?
Susan Manupelli: Sure. I’ll talk first about DOORS Next Generation. You know, DNG’s part of the ELM suite of products, that’s based on the Jazz architecture. It’s a very complex architecture. There’s a large number of servers you need, or VMs, to be able to stand up the solution. There’s an app server or some version of WebSphere. There’s a DB server for every application. So at a minimum with DNG, in addition to the app and DB server, you also would need a JTS server, an additional reporting server, [inaudible 00:02:08] or Data Warehouse. And if you have configuration management enabled, then there’s two additional servers that come with that, so for the global configuration manager and the LDX server. So-
Preston Mitchell: Interesting.
Susan Manupelli: And then of course, if you use any of the other applications of the ELM suite, there’s a server and database for those.
Preston Mitchell: Yeah, that’s quite a contrast to Jama, where we just require one application server and then a database server, which could be shared, actually, with other applications. Of course, that’s as far as self-host customers. Cloud customers really have no IT infrastructure costs at all, and I think that’s one of the biggest benefits of adopting a tool like Jama Connect. Okay, great. Next, I’d love to talk about the human or FTE maintenance costs that go along with tools. Susan, what’s your experience with other requirements management tools around the FTE costs?
Susan Manupelli: Sure. I’ll start off with DOORS Classic, which is an older client-server technology, and what I mean by that is that every user had to have software installed on their computer that was compatible with the server, so it was what we referred to as a thick client. An upgrade or maintenance of that would mean pushing out updates to however many users you have in your organization, potentially could be hundreds. So there was a lot of logistics involved with trying to get that upgrade done.
Preston Mitchell: Got it, and yeah, I imagine that’s downtime for the users, and a lot different than just a web-based tool that I sign in with my browser. The other thing that I know in working with customers that have migrated from DOORS Classic is DXL scripts and customization. Maybe you could talk a little bit about the hidden costs with those things.
Susan Manupelli: Yeah. Basically, any kind of customization that you want to do in DOORS Classic, you had to have somebody that could write a DXL script for it, that’s kind of a specialized skill, so there were costs with maintaining those, and particularly if they were used by across the organization.
Preston Mitchell: Is that any better with DOORS Next Generation?
Susan Manupelli:With DOORS Next Generation, there’s no DXL scripting or anything like that, but the thing that’s challenging with DOORS Next Generation is the upgrades and maintenance. Upgrades were often very complex and time-consuming. There was pretty high risk of failure, and then of course you have the time involved in roll back and trying it again. There’s also the ongoing maintenance of the middleware, would require a highly technical admin with some specialized skills in maybe database optimization, so Oracle or Db2. Also, keeping the system running optimally requires a full-time, highly skilled administrator for the ELM suite.
Preston Mitchell: Really? Full-time just for the backend? Wow.
Preston Mitchell: Yeah, that’s definitely different than kind of what our self-hosted customers experience. I mean, we try to make the self-hosted upgrades very easy and straightforward. It’s a button click in the admin console. And then obviously, for the majority of our customers who use our cloud solution, there’s really no upgrade or maintenance that they have to do at all. We push the upgrades for them. We handle that for them in an automated process, that’s validated and verified. So yeah, definitely different. Well, let’s transition to talk about adoption costs, and I want to bring my screen share up again, because you and I have spoken about really the opportunity costs of not using best-in-breed tools or processes, and it kind of really comes down to measurement. We really believe using Jama Connect, we can reduce the negative product outcomes, because we can help you measure your process performance. As management guru, Peter Drucker, said, “If you can’t measure it, you can’t improvement.” So Susan, maybe you could touch on what I find are the three primary ways that we can help our customers measure their performance.
Susan Manupelli: Sure. First of all, we can measure the quality of the requirements. This means properly define… making sure the requirements are properly defined, that they’re complete and consistent. And we actually have a new product, Jama Connect Advisor, that helps in this area. As far as the digital engineering, we can measure the level of collaboration that’s happening in the tool, the number of reviews, and the output from those reviews. And then also for live traceability. Traceability is one of the key reasons why people use a requirements management tool, and Jama does it better than any other tool that I’ve used. And in addition, we can measure how well you’re actually capturing that traceability.
Preston Mitchell: Yeah. And speaking to that, especially on the live traceability, we have for our cloud customers, this great benchmark, where we anonymize all the data, and you can actually see how you stack up against your peers in the industry with regards to the traceability completeness of your projects. So some really great return on investment by utilizing our cloud offering and being able to see the actual performance compared to your peers in the industry. Ultimately, I think everyone realizes the later you are in a product development lifecycle, it’s much more expensive to actually fix any errors that are found. So our whole goal at Jama Connect is really to lower the total cost of ownership, but really actually make your product development less costly by finding and fixing those errors way earlier in the cycle, in the requirements definition phase. Well Susan, thanks again for the quick chat, and sharing your perspective on cost of ownership. Appreciate it.
Susan Manupelli: Great. Thanks, Preston.
Preston Mitchell: Bye, everybody.
Is your data working for you? A consistent and scalable data model is instrumental for achieving Live Traceability™ and making data readily available across the development lifecycle.
Thank you for watching our 10th and final episode in this series, Jama Connect vs. IBM DOORS: Total Cost of Ownership. To watch other episodes in this series, click HERE.
https://www.jamasoftware.com/media/2023/02/Doors-VLOG-Episode-10-intro-1.jpg10801920Preston Mitchell/media/jama-logo-primary.svgPreston Mitchell2023-03-01 03:00:242024-01-18 00:54:05Jama Connect® vs. IBM® DOORS®: Total Cost of Ownership: A User Experience Roundtable Chat
![[Webinar Recap] An Overview of the EU Medical Device Regulation (MDR) and In-Vitro Device Regulation (IVDR)](https://www.jamasoftware.com/media/2023/04/BLOG-RECAP-Medical-Device-Webinar-Social-Image.png "[Webinar Recap] An Overview of the EU Medical Device Regulation (MDR) and In-Vitro Device Regulation (IVDR)")
![[Webinar Recap] Why it Makes Sense to Store Cybersecurity Risk Management Items Inside a Requirements Management System](https://www.jamasoftware.com/media/2023/03/Cybersecurity-Risk-RM-.png "[Webinar Recap] Why it Makes Sense to Store Cybersecurity Risk Management Items Inside a Requirements Management System")
![[Webinar Recap] Launch Your Aerospace & Defense Product Development Processes with Jama Connect®](https://www.jamasoftware.com/media/2023/03/BLOG-RECAP-Launch-Your-AD-Product-Development-Processes-with-Jama-1-1.png "[Webinar Recap] Launch Your Aerospace & Defense Product Development Processes with Jama Connect®")
