ARP4761A Safety Assessment Structure

Traceability gaps in a safety case lead to costly rework when certification teams discover that their Functional Hazard Assessment (FHA), Preliminary System Safety Assessment (PSSA), and System Safety Assessment (SSA) no longer align. When SAE’s S-18 committee released ARP4761A in December 2023, the document grew substantially. That growth reflects the addition of aircraft-level assessment processes that practitioners had been performing informally for years, new analytical methods such as Model-Based Safety Analysis (MBSA), and a structural reorganization with more appendices than in the original version.

For certification teams building safety evidence packages for Designated Engineering Representatives (DERs) or Federal Aviation Administration (FAA) Stage of Involvement (SOI) audits, the revision changes how safety artifacts are organized, where Development Assurance Level (DAL) assignments are documented, and which analytical methods carry formal recognition. 

This article covers what changed in the 2023 revision, how the core assessment processes fit together, and where teams most often lose traceability across their safety artifacts.

What Is ARP4761A and What Changed in the 2023 Revision?

ARP4761A is an SAE Aerospace Recommended Practice for the safety assessment process on civil aircraft, systems, and equipment. The 2023 release was also designated ED-135 by the European Organisation for Civil Aviation Equipment (EUROCAE) and supersedes the original ARP4761 published in 1996.

Aircraft-level processes are now formal parts of the standard. The original standard’s single FHA is now split into an Aircraft Functional Hazard Assessment (AFHA) and a System Functional Hazard Assessment (SFHA). 

Two aircraft-level processes, the Preliminary Aircraft Safety Assessment (PASA) and the Aircraft Safety Assessment (ASA), fill a gap left undefined by the original standard. ARP4761A also introduces Model-Based Safety Analysis (MBSA) and Cascading Effects Analysis (CEA) as formal analytical methods and adds a dedicated appendix for Functional DAL (FDAL) and Item DAL (IDAL) assignment. The standard’s preface notes that the AFHA, once an emerging practice, is now a standard element of the safety assessment process. The title change reflects a broader scope. “Airborne” was replaced with “Aircraft,” which positions the document more broadly across aircraft-level and system-level work.

How ARP4761A Fits With ARP4754B in the Safety Lifecycle

ARP4761A and ARP4754B were released together in December 2023 and are intended to work as companion standards. Within the ARP4754B aircraft and system development framework, DO-178C and DO-254 connect system-level safety and development requirements to item-level software and hardware development obligations.

The Relationship Between System Development and Safety Assessment

ARP4754B covers the system development lifecycle, including requirements validation, architecture definition, and verification. ARP4761A covers how teams assess the safety of their development. The interaction between them is bidirectional and iterative. ARP4754B feeds architectural definitions into ARP4761A’s safety analyses. ARP4761A feeds DAL assignments and safety requirements back into ARP4754B’s development activities. Neither standard operates in isolation, and a change in one domain’s artifacts typically triggers reassessment in the other.

Where ARP4761A Sits in the DO-178C and DO-254 Certification Path

ARP4761A safety assessment outputs determine the rigor required for airborne software development under DO-178C and airborne electronic hardware under DO-254. The FHA classifies failure conditions by severity. The PSSA allocates IDALs to specific software and hardware items based on architectural decisions. Those IDALs then dictate the number and type of objectives a DO-178C or DO-254 program must satisfy. The safety assessment chain from FHA through PSSA generates those obligations.

The Core Safety Assessment Processes in ARP4761A

ARP4761A provides guidance for the System Safety Assessment process, which is commonly applied within the broader V-model development framework defined by ARP4754B. FHA and PSSA operate top-down on the left side to evaluate preliminary designs. The SSA operates bottom-up on the right side, verifying implemented designs. Common Cause Analysis (CCA) runs iteratively across both sides throughout the lifecycle.

Functional Hazard Assessment (FHA)

The FHA identifies aircraft and system functions, evaluates their failure conditions, and classifies each condition by severity. Classifications range from Catastrophic through Hazardous, Major, and Minor, down to No Safety Effect. ARP4761A formalizes the split into AFHA at the aircraft level and SFHA at the system level, in which each system’s allocated functions are re-examined under single- and combined-failure conditions.

Preliminary System Safety Assessment (PSSA)

The PSSA tests proposed system designs against identified hazards and shapes architecture decisions. It determines how failures can cause the functional hazards identified by the FHA. It evaluates proposed architectures, supports allocation of safety objectives and development assurance levels such as FDALs and IDALs, and generates derived safety requirements. The PSSA is continuous and iterative, with high-level requirements generating lower-level ones. ARP4761A’s revision emphasizes that the PSSA is not a verification exercise performed after the fact.

System Safety Assessment (SSA)

The SSA checks whether the implemented design meets requirements established by the FHA and PSSA. It incorporates quantitative Fault Tree Analysis (FTA), Failure Modes and Effects Summary (FMES) data, and finalized CCA results to demonstrate that catastrophic failure probabilities remain below their thresholds. The SSA sits on the right side of the V-model and works bottom-up, in contrast to the top-down FHA and PSSA.

Common Cause Analysis (CCA)

CCA evaluates susceptibility to events that could simultaneously affect multiple items, defeating redundancy and independence. It comprises three sub-analyses. Zonal Safety Analysis (ZSA) examines physical compartments for hazards affecting co-located components. 

Particular Risk Analysis (PRA) evaluates external hazards such as fire, lightning, or rotor burst that can affect redundant systems across zones. Common Mode Analysis (CMA) examines whether redundant components share failure modes through design errors, manufacturing, maintenance, or software. CCA outputs trace directly to implementation.

The Analytical Methods That Support Each Process

ARP4761A integrates qualitative and quantitative methods, enabling teams to connect judgment-based assessments with formal analysis. Its analytical methods are organized across Section 4 and dedicated appendices. Quantitative analysis tools are intended to complement, not replace, qualitative methods based on engineering and operational judgment.

Fault Tree Analysis (FTA)

FTA is the primary quantitative method for architecture evaluation and compliance demonstration. It is a deductive, top-down method in which FHA top-level events generate the root nodes of fault trees. 

During PSSA, FTA supports architectural evaluation and failure-probability budgeting. During SSA, cutset analysis demonstrates that no single failure causes a hazardous or catastrophic condition. FTA remains one of the most commonly used methods for demonstrating quantitative compliance.

Failure Modes and Effects Analysis (FMEA)

FMEA evaluates the effect of each possible component failure from the bottom up. It is an inductive method that traces the effect of each component failure on the system and the aircraft. Component-level FMEA data is summarized into an FMES, which feeds quantitative FTA during SSA. FMEA alone is insufficient for hazard identification because it captures only dominant failure modes. It must be combined with top-down methods to provide a complete safety picture.

Dependence Diagrams (DDs) and Markov Analysis (MA)

Dependence Diagrams (DDs) and Markov Analysis (MA) address cases where fault-tree representations are insufficient. DDs represent success logic rather than failure logic and are treated as equivalents to FTA for PSSA and SSA purposes. 

MA models state transitions in systems where failure order, repair interactions, or phased missions matter. MA is more computationally intensive and is typically reserved for cases where FTA or DD representations are insufficient. ARP4761A groups FTA, DD, MA, and MBSA together in Section 4.1 as a family of quantitative methods.

How Development Assurance Levels Shape Assessment Rigor

DAL assignments set the rigor of downstream development and verification work. FHA severity classification maps directly to the FDAL, which determines the minimum rigor for all downstream development. Catastrophic conditions require the highest level of assurance, followed by Hazardous, Major, Minor, and No Safety Effect.

During the PSSA, architectural decisions allow the allocation of IDALs to specific items. Where formal independence between components can be demonstrated and verified through CCA, individual items may receive lower IDALs than the function’s FDAL. Without that demonstration, IDALs default to match the FDAL. ARP4761A’s new appendix formalizes the FDAL and IDAL assignment process within the safety assessment standard itself. That procedure previously resided only in ARP4754A.

Higher-assurance software and hardware items carry substantially more development and verification obligations than lower-assurance items. That difference in verification effort, staffing, and schedule often shapes architectural decisions during PSSA.

Where Safety Assessment Teams Lose Traceability

Traceability usually breaks down at the handoffs between safety artifacts, requirements, and design changes. The ARP4761A safety assessment process is formally iterative, but the toolchains teams use to produce safety artifacts often are not.

Disconnected Hazard Data Across Tools and Documents

Disconnected tools make it easy for hazard data and requirements links to drift out of sync. FHA tables, FTA models, and FMEA spreadsheets typically live in separate tools with no automated synchronization. 

A failure condition probability threshold from the FHA flows through the PSSA into a system safety requirement, then into software requirements in a separate Application Lifecycle Management (ALM) tool. When the hazard register is a Word document and the requirements baseline is in a different system, the link between the failure condition and the implementing requirement is maintained manually. That link breaks when either artifact is updated independently.

Keeping Safety Artifacts Current Through Design Change

Design changes can invalidate safety analyses faster than teams update them. A system architecture modification, such as removing a redundant path to reduce weight, invalidates the FTA most recently updated at the Preliminary Design Review (PDR). 

If the SSA submitted for certification still references the pre-change architecture, the DER will identify the inconsistency. The program then faces an unplanned FTA revision and SSA update before the certification data package is accepted. Without automated change impact analysis, there is no way to flag dependent documents for review when an artifact changes.

Building Certification-Ready Safety Assessments

Certification-ready safety assessments depend on keeping every related artifact aligned as the program evolves. The 2023 revision’s addition of aircraft-level processes, MBSA and CEA, and a dedicated FDAL/IDAL appendix increases the volume and complexity of artifacts that must remain synchronized throughout a certification program. 

Programs that wait until the certification data package is due to discover traceability gaps between their FHA, PSSA, and SSA artifacts face the most expensive kind of rework, unplanned analysis revision under schedule pressure. The same discipline applies to other safety-critical avionics programs, where a single late-stage architecture change can ripple through every dependent analysis.

How Jama Connect® Supports ARP4761A Safety Assessment Structure

Jama Connect® is a web-based requirements management and traceability platform for complex, regulated product development, and it addresses the specific challenge of keeping AFHA, SFHA, PSSA, SSA, and CCA artifacts aligned as designs, requirements, and verification evidence change. That alignment problem grows as more safety artifacts, downstream development items, and verification results must remain connected across every revision.

Jama Connect includes pre-built structures aligned to ARP4754B, ARP4761A, DO-178C, and DO-254 that link aircraft functions, safety requirements, downstream development items, and verification evidence in a single traceable chain. Its Live Traceability™ capability surfaces coverage gaps and suspect links before SSA or DER review, enabling upstream assessment of changes across dependent artifacts before they become inconsistencies in the certification package.

Keep Your ARP4761A Safety Case Certification-Ready 

The 2023 revision rewards programs that treat the safety case as a living network of connected artifacts rather than a set of documents reconciled at milestone reviews. As aircraft-level processes and new analytical methods add more artifacts to keep synchronized, the cost of discovering misalignment late in certification climbs faster than it did under the original standard.

Jama Connect supports this workflow by maintaining traceable links among functions, hazards, requirements, and verification evidence as designs evolve, keeping the safety case review-ready rather than requiring reconstruction before a DER audit. Start a free 30-day trial of Jama Connect.

Frequently Asked Questions About ARP4761

What is the difference between ARP4761 and ARP4761A?

ARP4761A is the December 2023 revision of the original 1996 ARP4761. It formalizes aircraft-level safety assessment processes, recognizes MBSA and Cascading Effects Analysis as formal methods, and adds guidance for FDAL/IDAL assignment. The revision is designed for use alongside ARP4754B rather than the original ARP4754.

Is ARP4761A mandatory for aerospace certification?

ARP4761A is not a regulation. It is an SAE Aerospace Recommended Practice that the FAA and the European Union Aviation Safety Agency (EASA)  may recognize as an accepted means of demonstrating compliance within the broader certification framework. Teams can propose alternative safety assessment methods, but they must be agreed with the relevant certification authority, making it important to keep the resulting safety evidence organized and review-ready.

How does ARP4761A relate to FAA and EASA requirements?

FAA and EASA airworthiness regulations establish the regulatory basis for aircraft safety assessment, while ARP4761A provides guidance on how applicants may perform that work. Some agency materials reference ARP4761A by name, while older guidance still cites the earlier version, creating a documentation alignment challenge for certification teams managing both.

Which analytical methods does ARP4761A recognize?

ARP4761A recognizes Fault Tree Analysis, Dependence Diagrams, Markov Analysis, and Model-Based Safety Analysis as quantitative methods, alongside FMEA and Common Cause Analysis for inductive and dependence-related assessment. Quantitative tools are intended to complement qualitative engineering judgment rather than replace it, and most programs combine top-down and bottom-up methods to cover both hazard identification and probability budgeting.

The post ARP4761A Introduction for Engineers and Managers appeared first on Jama Software.

This blog overviews our recent Datasheet. To download the entire asset, visit “Increase Efficiency and Reduce Risk through Structured Collaboration and Traceability with Jama Connect for Requests for Proposals (RFPs).”

Increase Efficiency and Reduce Risk through Structured Collaboration and Traceability with Jama Connect for Requests for Proposals (RFPs)

KEY BENEFITS

• Faster Time to Submit: Produce high-quality, detailed responses faster by replacing manual data entry in disparate documents with a solution providing workflows and automation for importing, organizing, and responding to RFP requirements.
• Higher Response Consistency: Maintain end-to-end traceability between RFP requirements and your current and planned engineering capabilities by ensuring that every item is verified and validated to generate reports that are accurate and professional.
• Reduce Subject Matter Expert Disruption: Replace siloed email feedback on RFP related documentation with a structured, collaborative environment that makes it easy for internal subject matter experts and external stakeholders to comment, review, and approve responses.
• Lower Bid Risk: Identify gaps and potential risks during the bid phase through dashboards that provide real-time view of RFP progress, showing requirement status, risks, ownership, and gaps in one place to quickly identify bottlenecks, overdue items, and high-risk areas.

Managing Requests for Proposals (RFPs) is often a chaotic process that if not handled well, can result in lost bids, margin erosion, and delivery risk. It requires subject matter experts to step away from their primary work to produce high-quality detailed responses quickly to meet tight deadlines. The typical manual approach involves Proposal, Capture, Product, Engineering, and Compliance managers and other staff juggling spreadsheets and lengthy PDF documents in email threads, struggling to maintain version control and track status of individual items. Without content libraries or automation, responding to similar questions that exist across different proposals leads to inefficient, repetitive, and frustrating work. Any resulting mistakes in responses jeopardize the success of the bid and create a disconnect between what is promised in the proposal and what is eventually delivered.

Jama Connect for RFPs is a structured requirements and traceability solution purpose-built to manage proposal complexity and risk. By bringing the RFP lifecycle directly into the Jama Connect platform, organizations can import product or project requirements from RFP documents, trace them to existing capabilities, and manage responses with greater speed and accuracy. This solution ensures that every proposal is backed by data, compliance is verified early, and the quality of responses reflects the true capabilities of your organization.

RELATED: Buyer’s Guide: How to Select the Right Requirements Management and Traceability Solution

What’s Included in Jama Connect for RFPs

Jama Connect for RFPs replaces ad-hoc proposal chaos with a purpose-built, traceable system of record. The solution delivers a preconfigured framework for managing RFP complexity, anchored by a dedicated Traceability Information Model™ that enforces clear, auditable relationships between RFP requirements, responses, gaps, and clarifications. The result is disciplined, traceable proposals where commitments are verified, risks are visible, and delivery expectations are set correctly from day one.

Sample RFP Project Dashboard

Companies choose Jama Connect for RFPs to increase efficiency, accuracy, and consistency and reduce risk when responding to RFPs. To learn more, visit jamasoftware.com

TO DOWNLOAD THIS DATASHEET, VISIT:
Increase Efficiency and Reduce Risk through Structured Collaboration and Traceability with Jama Connect for Requests for Proposals (RFPs)

The post Increase Efficiency and Reduce Risk through Structured Collaboration and Traceability with Jama Connect® for Requests for Proposals appeared first on Jama Software.

What Is Research Use Only (RUO)? Definition and FDA Rules

The research use only (RUO) designation gives diagnostics teams a valuable window during early development. It lets a product support assay development and biomarker discovery before the full set of in vitro diagnostic (IVD) obligations kick in. That window is exactly where teams generate the performance data that later carries a submission.

The catch is how narrow the exemption actually is, and how much compliance work still runs in the background. This guide covers what the RUO exemption under 21 CFR 809.10 allows, how the US and EU treat it, and what it takes to move an RUO product into a cleared IVD without losing traceability.

What Is Research Use Only (RUO)?

Research use only (RUO) is a narrow FDA exemption that lets an in vitro diagnostic product sit outside most IVD obligations while it is genuinely still in research. 21 CFR 809.10, the FDA rule that governs IVD labeling, sets three conditions that all have to hold at the same time. The product must be in the laboratory research phase, cannot be represented as an effective IVD, and must carry prominent labeling that reads “For Research Use Only. Not for use in diagnostic procedures.” Miss any one and the exemption falls away.

The designation covers instruments, reagents, software, and test systems used for early assay work, method development, and biomarker discovery. Minimum labeling still applies, so the carton needs the RUO statement, net quantity, manufacturer identity, and a lot number that ties back to manufacturing history. Premarket review, quality system requirements, and post-market surveillance all sit outside the RUO envelope.

How the RUO Regulatory Framework Works in the US and EU

FDA and EU regulators both judge RUO status by intended use, and the carton is only one piece of evidence. Both frameworks reconstruct intent from the full set of manufacturer communications and commercial conduct.

How the FDA Evaluates Objective Intent

FDA applies an objective-intent standard when deciding whether an RUO claim holds. Investigators weigh labeling, advertising, website copy, technical support content, sales records, and customer lists together. During an inspection, they pull website archives, purchase orders, shipping records, and support tickets, then compare the commercial pattern to the research-phase claim on the carton.

An RUO statement by itself protects nothing once the record points to clinical use. Sales concentrated in clinical analysis companies, marketing copy that names diagnostic applications, and support staff walking customers through clinical workflows all count as evidence of intent. If the evidence contradicts the label, FDA can treat the product as misbranded under section 502 of the FD&C Act and adulterated under section 501.

How EU IVDR 2017/746 Treats RUO Products

EU IVDR 2017/746, the EU regulation on in vitro diagnostic medical devices, applies to products intended for a medical purpose. Article 1(3)(a) takes products genuinely intended for research, product development, or performance evaluation out of scope, provided they are not placed on the market as IVDs. A product that stays inside that scope exclusion does not need CE marking under IVDR.

Medical Device Coordination Group (MDCG) guidance tightens the same idea. An RUO product cannot be promoted, supported, or sold in a way that implies diagnostic use. Drifting into clinical promotion pulls the product back inside IVDR and turns it into an IVD without CE marking, which creates the same exposure as a mislabeled product in the US.

What the Exemption Does Not Cover

The RUO relief covers premarket review, 21 CFR Part 820 quality system obligations, and post-market surveillance. It stops at the point where distribution contradicts the label or the product moves into clinical diagnosis. In the EU, an RUO product outside IVDR scope can still fall under product safety, chemical, and biosafety rules, so the scope exclusion is not a blanket pass on regulation.

How RUO Products Differ From Cleared IVDs

The gap between an RUO product and a cleared IVD is wider than it looks from a labeling perspective. The table below shows where the two sit across the dimensions that matter most during transition planning.

Technical support is where the line tends to blur. Generic instrument maintenance and software patches stay inside the research frame. Helping a customer validate a clinical workflow or walking staff through clinical result calls looks to FDA like diagnostic intent.

Where RUO Products Fit in Diagnostic Development

RUO products earn their place in four settings where a clinical claim would be premature and the work is still about characterizing performance.

• Early assay development: Teams tune instrument settings, reagent combinations, and software parameters before locking a design input. The RUO label fits because there is nothing yet to validate against, and pretending otherwise would create a misbranding problem.
• Biomarker discovery and translational research: Exploratory work generates hypotheses and results that never feed patient decisions. RUO reagents fit that scope and keep the work outside premarket review until a specific indication emerges.
• LDT component supply: Reference laboratories use RUO components inside laboratory-developed tests they validate themselves under Clinical Laboratory
• Improvement Amendments (CLIA) oversight. The laboratory carries regulatory responsibility for the finished test, so the RUO label correctly reflects the component maker’s scope.
• Analytical method development: Method development teams pick antibody pairs, characterize interference, and probe matrix effects before formal analytical validation begins. RUO tools carry the right claim here because the performance specifications are still being written.

Using RUO deliberately in these four settings gives diagnostics teams clean, defendable data for the point when the same product carries a clinical claim. A well-structured medical device requirements practice during this phase makes the eventual submission easier.

What Triggers FDA Enforcement

FDA acts on RUO products when intent points to clinical use in spite of the label. Two recent warning letters show the evidence pattern investigators build.

The Agena warning letter in March 2024 covered the iPLEX HS Colon Panel. FDA found sales into CLIA-certified labs doing patient testing and dual distribution confirmed in the company’s own records, and concluded that the RUO disclaimer was inconsistent with the commercial pattern.

The DRG warning letter in March 2025 covered the Salivary Cortisol ELISA RUO and related devices. FDA cited website copy describing clinical applications like diagnosis of systemic conditions and therapeutic drug monitoring, along with shipments to clinical analysis companies. In both cases the RUO statement sat where it was supposed to, and the rest of the record carried the product across the line. Consequences can include seizure, injunction, civil money penalties, and pressure to pursue a 510(k) or PMA before further distribution.

How to Transition an RUO Product Into an IVD

A product needs to move out of RUO status when its intended use shifts into clinical diagnosis, or when the way it sells starts to imply that shift. A last-minute relabeling push usually stalls while reviewers ask for records that were never captured under design controls. The work runs best as a structured program with three connected moves.

Start Design Controls Before Investigational Work

Open design controls under ISO 13485:2016 right after feasibility and before any investigational studies begin. Starting the Design History File early captures inputs, outputs, verification, validation, and reviews in real time, with authors and dates attached. Back-filling a DHF close to submission is the pattern auditors spot fastest, and a record reconstructed from memory always reads differently from one built as the work happened.

Time the QMSR Transition Correctly

The FDA Quality Management System Regulation (QMSR) took effect on February 2, 2026, and incorporates ISO 13485:2016 by reference. Build to QMSR from the start of transition so you avoid a second round of documentation work later and stay compatible with EU markets at the same time. Teams already  certified to ISO 13485:2016 still need to address FDA-specific additions like Unique Device Identification and Medical Device Reporting.

Pick the Submission Pathway That Fits the Device

Classification decides the path. Most Class II IVDs go through 510(k) on the strength of a cleared predicate, novel Class II devices without one use De Novo, and Class III IVDs require PMA with full analytical and clinical validation data. Analytical studies built to recognized Clinical and Laboratory Standards Institute (CLSI) documents give reviewers a design they already know how to evaluate.

With the program in place, the harder question is whether the underlying records can actually support the submission.

Why Traceability Breaks Down During Transition

Research-phase documentation usually lives in spreadsheets, lab notebooks, and file shares, with design decisions scattered across authors and versions. That setup holds until a regulated submission asks for a single, current, reviewable chain from user need through verification and validation evidence. An auditor who pulls a random design input expects to walk straight to the linked verification output, and any gap becomes a finding.

A requirements traceability matrix links design inputs to design outputs, verification, and validation in one view, and risk outputs from ISO 14971 hazard analysis feed the same chain through inputs and change management. Teams managing this in disconnected files carry a compounding maintenance burden, since every design change forces manual updates across many documents, and a single missed link can surface as an audit finding months later.

How Jama Connect Supports RUO-to-IVD Transition

Most breakdowns during RUO-to-IVD transition trace back to records that held up for research-phase work but cannot stand up to a design review. When design inputs, risk items, verification records, and change history live in separate systems, the chain a reviewer expects gets stitched together manually, and design transfer slows because production specs cannot be cleanly tied back to the validated design.

Jama Connect^® is a requirements management platform for regulated product development, with pre-built frameworks for ISO 13485, FDA QMSR, EU IVDR, ISO 14971, and IEC 62304. Those frameworks keep design, risk, and verification records connected as an RUO program matures into a cleared IVD. When a requirement changes, suspect links alert the downstream owners who need to review verification evidence and risk management outputs.

Treating RUO as a Structured Phase of a Regulated Program

RUO pays off most for teams that treat it as a structured phase of a longer program. The research-phase work generates the data that will carry a submission, and the quality of that record depends on whether requirements, risk, and verification were connected from the start. Recent enforcement makes a record reconstructed under audit pressure much more expensive than it used to be.

A single system for requirements, risk, testing, and regulatory records gives diagnostics teams a way to see an RUO program as it matures. Jama Connect supports that workflow with its medical device and IVD frameworks, keeping traceability intact as a product moves toward a cleared IVD. Start a free trial of Jama Connect today to see how it keeps the record current.

Frequently Asked Questions About Research Use Only

Can an RUO product be sold to clinical laboratories?

Selling to clinical labs is not automatically a problem. It becomes one when the surrounding conduct points to clinical use, through promotional material, clinical support, or a customer book concentrated in clinical analysis companies. The Agena and DRG warning letters turned on exactly that combination of evidence.

When does an RUO product need to transition to an IVD?

Once commercial behavior, marketing copy, or support practice implies clinical use, the product is on the wrong side of the RUO line whether or not the carton has been updated. Building design controls, risk records, and traceability during the RUO phase makes the conversion to a regulated program much less painful than rebuilding the record later.

How does the QMSR affect RUO-to-IVD transition plans?

QMSR replaces most of 21 CFR Part 820 and incorporates ISO 13485:2016 by reference, with an effective date of February 2, 2026. A transition plan built to

QMSR from the start carries both FDA and ISO 13485 expectations at once. Teams already certified to ISO 13485:2016 mostly need to address FDA-specific adds like Unique Device Identification and Medical Device Reporting.

What is the difference between RUO status in the US and EU?

Both frameworks judge intended use through the full body of a manufacturer’s communications, so label text is never the only input. FDA applies an objective-intent standard across labeling, advertising, support content, and customer records, while EU IVDR 2017/746 uses an Article 1(3)(a) scope exclusion for products genuinely intended for research. Promoting for clinical use creates enforcement exposure in both jurisdictions even when the carton still reads RUO.

The post What Is Research Use Only (RUO)? Definition and FDA Rules appeared first on Jama Software.

Teams that catch defects early spend less on rework, move faster through audits, and protect the margins that fund their next program. A big part of how they get there is managing cost of poor quality (COPQ), which can consume five to 35 percent of revenue in manufacturing companies and often goes untracked until an audit or recall forces it into the open.

This guide covers what COPQ is, how to calculate it, where the biggest costs accumulate, and how to shift spending from failure correction to prevention.

What Is the Cost of Poor Quality (COPQ)?

Cost of poor quality (COPQ) is the total cost a team pays when something goes wrong, from internal scrap and rework to external recalls and warranty claims. In quality engineering, it covers everything that would disappear if there were no deficiencies, no errors, and no failures.

Most quality programs treat COPQ as a subset of total cost of quality (COQ). Here is how the breakdown works:

• Cost of good quality (COGQ): Prevention costs + appraisal costs.
• Cost of poor quality (COPQ): Internal failure costs + external failure costs.
• Total cost of quality (COQ): COGQ + COPQ.

That breakdown is useful because it separates what you spend on purpose (prevention and appraisal) from what you lose when things go wrong (internal and external failures).
COPQ typically falls [between five to 35 percent of sales revenue in manufacturing companies. In companies without well-developed quality programs, failure costs have historically consumed 60 to 70 percent of total quality costs, while prevention received just five to 10 percent.

The Four Categories of Quality Costs

So if failure costs are consuming that much revenue, where exactly is it going? The Prevention-Appraisal-Failure (PAF model) divides quality costs into four categories. Two represent investments (prevention and appraisal) and two represent losses (internal and external failures).

Prevention Costs

Prevention includes requirements engineering, design failure mode and effects analysis (FMEA), risk management per ISO 14971, supplier qualification, and quality planning. Every dollar spent here tends to save multiples downstream because it stops defects from entering the system in the first place.

Appraisal Costs

Appraisal is what teams spend to detect defects that already exist. Incoming inspection, integration testing, independent verification and validation (IV&V), calibration, and third-party certification audits all fit here.

Internal Failure Costs

This is where a defect is found before release, but the team still pays for it. Scrap, rework, failed test reruns, nonconforming product disposition, and Material Review Board processing all belong here.

External Failure Costs

External failure costs hit when a defect reaches the field, the customer, or the regulator. In 2025, NHTSA issued 997 recalls affecting more than 29 million vehicles, and large-scale program failures in aerospace and automotive have accumulated costs in the tens of billions when quality gaps went undetected through multiple development phases.

In regulated products, the stakes are even higher. FDA Class I recalls can cost millions in direct expenses before accounting for reputational damage and regulatory scrutiny.

How to Calculate COPQ

Calculating COPQ is straightforward once you know where to look. The tricky part is capturing the costs that don’t show up in your budget as line items.

The COPQ Formula

COPQ = Internal Failure Costs + External Failure Costs

The broader COQ formula adds prevention and appraisal:

COQ = (Prevention + Appraisal) + (Internal Failure + External Failure)

A common executive KPI is COPQ as a percentage of revenue: (Internal Failure Costs + External Failure Costs) ÷ Sales Revenue × 100.

For example, say a medical device team ships 10,000 units in a quarter. Internal failures, including scrap and rework on rejected assemblies, cost $150,000. External failures, covering warranty claims and one field corrective action, cost $800,000. Total COPQ is $950,000. Against $5M in quarterly revenue, that is 19% of sales going to failure costs, well within the range where most of the quality budget is being consumed by reaction rather than prevention.

Visible vs. Hidden Quality Costs

The costs you can see (scrap, warranty claims, rework labor) are only part of the picture. Hidden costs like engineering time lost to firefighting, delayed launches, and lost customer trust often run 4-5x higher. A $50,000 warranty charge can easily become $250,000 once you factor in the root cause investigation, the three-week launch delay, and the customer trust lost on the next renewal cycle.

Common Metrics and Benchmarks

The most useful metrics are the ones that show where failure costs are piling up. For internal failures, track scrap rate, first pass yield, rework hours, and defects per unit. For external failures, track warranty cost per unit, customer return rate, and recall costs. The COQ ratio also helps you see whether your quality program is weighted toward prevention or toward failure response.

Root Causes of COPQ

In complex, regulated product development, COPQ usually does not start on the shop floor or in the field. It starts earlier, when unclear requirements, weak verification, and broken traceability let defects travel downstream.

Incomplete or Ambiguous Requirements

Roughly half of all software defects originate in the requirements phase, and the majority of rework costs trace back to requirement errors, whether missing, wrong, or unnecessary. Regulatory bodies like the FAA stress the need for clear, complete requirements in software and computing system development. If the requirement is wrong, incomplete, or vague, every downstream artifact inherits that weakness.

Insufficient Testing and Verification

Defect correction costs rise sharply the later they are found, and the increase is far from linear. Correcting a defect during design costs roughly 3-8x more than catching it during requirements, 7-16x more during build, and 29x to over 1,000x more during operations, depending on the system and industry. By the time a defect shows up in verification, you end up fixing every artifact built on top of that original requirement.

Poor Traceability Across the Development Lifecycle

Complete traceability directly decreases defect rates: teams working with traceability performed 21% faster and produced 60% more correct solutions than those without it.
When a requirement changes and test cases are not updated to match, risk inputs go stale and coverage gaps go unseen. This is especially common when the traceability chain is spread across disconnected tools, where COPQ accumulates quietly across handoffs until rework, schedule delays, or audit findings force it into the open.

How COPQ Shows Up in Different Industries

Every industry feels COPQ differently, but the pattern is worth understanding before you try to fix it.

Manufacturing and Production

Manufacturing teams see COPQ most visibly in warranty claims, scrap, and rework labor. Scrap rates and first-pass yield are typically the first metrics to watch because they give the clearest signal of where quality controls are falling short.

Medical Devices and Regulated Products

For medical device teams, the traceability needed to show that verification is complete often becomes the largest compliance cost driver, and gaps in that chain usually surface during audits or submissions instead of during development. A single FDA Class I recall can cost millions in direct expenses before accounting for the reputational damage and regulatory scrutiny that follows.

Software and Complex Systems Development

Software teams feel COPQ through defect fixes, delayed releases, outage recovery, and the operational disruption that follows. Teams that track what percentage of sprint capacity goes to bug fixes often find that poor requirements quality is consuming 30-50% of their engineering time.

How to Reduce COPQ

Most COPQ starts upstream, so the most effective reductions come from moving effort upstream too. Here are three approaches that consistently work:

Build Quality Into Your QMS From the Start

In regulated environments, some appraisal activities are mandatory under FDA, FAA, or NHTSA oversight, but you can reduce discretionary inspection and manual recovery by improving what happens earlier in development. Organizations that embedded quality into their process saw significant improvements in both operational costs and revenue. A key part of that is Corrective and Preventive Action (CAPA): when each failure investigation feeds a systemic fix back into your prevention process, COPQ drops over time instead of recurring.

Use COPQ-Weighted Pareto Analysis to Prioritize Fixes

Two processes can have the same defect count but very different financial exposure. A Pareto analysis weighted by dollar impact is more useful than ranking by frequency alone, because a rare traceability gap that delays a submission can cost more than a frequent but low-impact defect. Going after the top three cost drivers first usually produces the fastest return.

Track COPQ Monthly and Tie It to Process Changes

Quality engineer Joseph Juran outlined a three-part approach that still holds up today: plan quality into your processes, control performance so it doesn’t degrade, and systematically reduce chronic waste. The most effective teams we’ve seen apply this by measuring COPQ monthly against prior-year costs and tying each improvement to a specific process change, so it’s clear what’s working and what needs more attention.

How Jama Connect Helps Reduce COPQ

When a requirement changes mid-program, every downstream artifact needs to reflect that change. Jama Connect flags suspect relationships when an upstream item changes, so engineers can assess the impact before gaps compound into rework. Across 40,000+ projects, teams with higher traceability scores catch defects faster and cover more verification ground, with top-quartile performers outperforming bottom-quartile counterparts by roughly 2x to 2.5x. After adopting Jama Connect, Arteris IP saw reuse increase by 100%, rework drop by 50%, review cycle time decrease by 30%, and audit prep time fall by 75%.

Jama Connect Advisor™ evaluates each requirement against INCOSE rules and EARS patterns, flagging vague terms and passive voice before they spread downstream. If roughly half of all defects trace back to requirements, catching ambiguity at authoring time is one of the most direct ways to cut COPQ at the source.

How to Turn COPQ Into a Competitive Advantage

COPQ is rarely just a scrap or warranty number. The teams that actually reduce it invest earlier, surface changes sooner, and make it easier to see what is missing before it becomes rework, delay, or recall.

For engineering and quality leaders trying to make that shift, traceability and requirements quality need to be part of daily engineering work. If your team is losing time and budget to rework driven by requirements gaps, start a free 30-day trial to see how upstream visibility reduces downstream cost.

Frequently Asked Questions About COPQ

What is the difference between cost of quality and cost of poor quality?

COQ is the total picture: what you spend to prevent and catch defects (prevention + appraisal) plus what you lose when defects get through (internal + external failures). COPQ is the loss side only. Tracking both helps you see whether your quality budget is weighted toward catching problems or preventing them.

How do you measure COPQ?

Start by tagging every quality-related cost to one of the four PAF categories. For internal failures, track scrap rate, rework hours, and first-pass yield. For external failures, track warranty cost per unit, customer returns, and recall expenses. Express COPQ as a percentage of revenue and review it monthly so you can spot trends and tie improvements to specific process changes.

What is a good COPQ benchmark for my industry?

There is no single target that works across all industries, but 5-35% of revenue is the commonly cited range for manufacturing companies. Teams with mature quality programs spend more on prevention and less on failure, which brings the overall COPQ percentage down over time. Tracking COPQ as a percentage of revenue month over month gives you a trend line to measure improvement against.

How is COPQ different in hardware versus software programs?

In hardware programs, COPQ shows up most visibly in scrap, rework labor, and warranty claims because physical materials and manufacturing time have already been committed. In software programs, the costs are less visible but equally real: defect remediation, delayed releases, outage recovery, and the engineering hours lost to debugging issues that originated in requirements. Both share the same root cause pattern where upstream problems create downstream costs.

The post What Is the Cost of Poor Quality (COPQ)? How to Calculate and Reduce COPQ appeared first on Jama Software.

This blog overviews our recent Datasheet, “Streamline Complex Product Quality Compliance, and Time-to-completion, with Jama Connect for Semiconductors” – To download the entire asset, click HERE.

Streamline Complex Product Quality, Compliance, and Time-to-completion with Jama Connect for Semiconductors

Semiconductor companies face increasing challenges in developing their next-generation products and product families. Product customization and resulting variants make it difficult for development teams to establish and maintain traceability throughout their engineering workflows, especially when design changes occur frequently. This often results in missed ship dates, cost overruns, dissatisfied customers, and, worse still, quality escapes.

Jama Connect for Semiconductors is a custom-built, powerful, and easy-to-use solution that helps automate requirements, testing, and traceability engineering processes that are often done manually in Excel and Word. With Jama Connect for Semiconductors, you will streamline requirements definition and management, bolster review and approval processes, and integrate tests so you can develop the right products with speed, quality, and data integrity – all while maintaining necessary standards compliance.

RELATED: Buyer’s Guide: How to Select the Right Requirements Management and Traceability Solution

KEY BENEFITS

• Accelerated Adoption: Templates, data models, and item types in Jama Connect are preconfigured for common Semiconductor use cases, delivered on day one.
• Single Source of Truth: A shared data repository enables Silicon Planners, Platform and Component Architects, Engineers, Testers, and others to collaborate effectively across the product life cycle, helping teams respond to change and mitigate risks.
• Visibility Leads to Accountability: Reports and indicators provide real-time status updates on program progress toward milestones.
• Reusability: Coordinate custom silicon definition through advanced reuse and sync capabilities to increase work efficiency and consistency.
• Contextual Guidance: A Procedure Guide tailored for Semiconductor provides simple process descriptions from the initial Stakeholder MRD to System-level PRDs, through validation and verification.

Jama Connect for Semiconductors is a solution designed and optimized for semiconductor companies. It includes an out-of-the-box Traceability Information Model aligned with systems engineering and semiconductor design best practices, end-to-end traceability from the high-level MRD through post-silicon validation, and a procedure guide with detailed steps for requirement capture, traceability, collaboration, verification reviews, and configuration management baselines.

Jama Connect for Semiconductors: Providing Real-Time Status of Project Requirements

Jama Connect for Semiconductors helps you stay ahead of the competition by strengthening your ability to manage requirements for developing the right products quickly, with high quality, data integrity, and compliance with necessary standards.

To learn more, visit us at jamasoftware.com/solutions/semiconductor

DOWNLOAD THIS ASSET: Streamline Complex Product Quality, Compliance, and Time-to-completion with Jama Connect for Semiconductors

The post Streamline Complex Product Quality, Compliance, and Time-to-completion with Jama Connect® for Semiconductors appeared first on Jama Software.

In this blog, we cover our recent datasheet, “Deliver Innovative Products Faster with Jama Connect for Consumer Electronics Development” – To download this asset, click HERE.

Deliver Innovative Products Faster with Jama Connect for Consumer Electronics Development

Consumer electronics markets are highly competitive, with pressure on companies to deliver new and improved products fast. Falling short of consumer and supply chain expectations relating to product features, performance, or quality can hurt company reputations with buyers and resellers in the marketplace. Failure to satisfy applicable safety and environmental regulations can lead to
product recalls and payments to consumers and government agencies.

To be successful, companies must be able to develop new or improved products quickly by efficiently managing customer, market, and regulatory requirements across product lines with multiple configurations to meet the needs of buyers and regulators around the world.

Jama Connect for Consumer Electronics Development helps companies reduce time to market in delivering innovative, quality, affordable products to avoid recalls and reengineering, and stay ahead of the competition, and meet customer expectations. It supports compliance with IEC 62368 consumer electronics and IEC 60730 home appliance global safety standards.

RELATED: AI-Assisted Engineering: Shaping the Future of Requirements Management

KEY BENEFITS

• Guided, Measurable Product Development: Jama Connect’s intelligent engineering management enables significant reduction in re-engineering and product recalls by guiding the user through the end-to-end product development, automatically detecting gaps and risks across the entire engineering data, and automatically measuring the system and process completion.
• AI Engineering Automation: Jama Connect Advisor’s™ AI will automate manual, day-to-day engineering tasks so that engineering can focus on innovation and problem-solving.
• Digital Co-development Across the Supply Chain: With Jama Connect’s native co-development and engineering collaboration features, internal development and quality teams and external subcontractors and contract manufacturers can jointly define and develop products in the same source of truth in real time.
• Apply Intelligence to Product Line Engineering: Efficiently manage requirements and tests shared by related products in libraries selectable based on the relevant configuration.
• Streamline Safety and Cybersecurity Risk Analysis, Testing, and Compliance Reporting: Simplify adherence to applicable safety and cybersecurity regulations with pre-built requirements, automated test case generation for traceability, and templates for exporting compliance reports.

RELATED: FORT Robotics Selects Jama Connect to Replace Google Sheets for Product Development

Jama Connect for Consumer Electronics Development Out-of-the-Box

Jama Software’s solution includes the following for developing integrated multidisciplinary consumer electronics products, subsystems, and software platforms:

• Product, subsystem, and software development items
• Product line engineering
• Safety, risk, and cybersecurity regulation items
• Co-development and digital thread process recommendations
• Report templates

Organizations at the forefront of consumer electronics innovation recognize Jama Connect as the tool that provides a competitive advantage in the market by enabling the acceleration of development and bringing innovative products to market faster.

To learn more about managing your consumer electronics and home appliance requirements, tests, and risks more intelligently and efficiently with Jama Connect, visit jamasoftware.com

TO DOWNLOAD THIS DATASHEET, VISIT: Deliver Innovative Products Faster with Jama Connect for Consumer Electronics Development

The post Deliver Innovative Products Faster with Jama Connect® for Consumer Electronics Development appeared first on Jama Software.

Streamline Industrial Machinery Development with Jama Connect!

In this Features in Five session, Patrick Garman, Solution Lead for Industrial Automation and Machinery at Jama Software, demonstrates how Jama Connect’s Industrial Machinery Data Model empowers teams to accelerate development and maximize project success in the industrial machinery space.

Key highlights include:

• Purpose-built support for complex machinery, from robotic assembly cells to heavy equipment.
• Centralized systems engineering with integrated safety, cybersecurity, risk management, and testing.
• Tools for improving requirements quality, identifying gaps early, and ensuring seamless traceability.

Introduction to Industrial Machinery Data Model

Hi, everyone. I’m Patrick Garman, Solution Lead for Industrial Automation and Machinery at Jama Software. Today, I’ll introduce our industrial machinery data model and why it’s so powerful for teams building sophisticated machinery. Industrial machinery includes systems like robotic assembly cells, packaging equipment, elevators, and heavy machinery. Any automated system with software, safety, or network components.

Integration of Standards and Systems Engineering

These products must comply with a wide range of standards, and our data model integrates systems engineering, safety, cybersecurity, risk management, and testing into one structure in Jama Connect.

This gives your teams a head start so you can launch products faster without reinventing processes. With predefined structures, traceability models, and workflows, Jama Connect reduces rework and recalls by exposing gaps early. Centralized traceability helps teams respond to change confidently, measure progress, and identify risks before they become problems. At the core is our traceability information model, which enforces good engineering practices, prevents invalid links, and highlights gaps automatically. Let’s see how this works and looks in the tool.

RELATED: Accelerating Innovation: Integrating Jama Connect and Jira^® for Enhanced Requirements Management in the Semiconductor Industry

Navigating the Project Explorer Tree

First, here’s the project explorer tree. You’ll notice that it’s organized by product architecture as well as domain. This makes it easy for project members to quickly locate relevant data. And, of course, XAML is more than just a repository for requirements. We’re actively managing those requirements based on stakeholder review and feedback.

Utilizing Live Trace Explorer™ for Traceability

Next, let’s look at Live Trace Explorer. This gives a real-time view of traceability coverage across our project. We can immediately see what’s complete, what’s missing coverage, and so on.

Identifying Gaps in Coverage

This is really one of the biggest value drivers, knowing your gaps early before they turn into late-stage redesign. So let’s drill into one of these gaps right now. So I can see that I have just shy of seventeen percent coverage at the system level.

Using Trace View™ to Add Coverage

I can click that metric in the Live Trace Explorer diagram to open Trace View and find exactly where I need to add coverage. In Trace View, you can see that Jama Connect is prompting me to add coverage where required links are missing.

Creating and Managing Test Cases

And you can take action directly from this view to add that coverage, or we can open a specific requirement for a more detailed view. Here we have a system requirement with missing test coverage. I can author test cases directly in Jama Connect using the add related feature, or I can use Jama Connect Advisor™’s test case intelligence tool to generate suggested test cases, complete with test steps based on the context I provide. But of course, traceability doesn’t end with test coverage.

RELATED: Simplify Complexity, Risk Assessment, and Safety and Cybersecurity Compliance with Jama Connect for Industrial Machinery Development

Integration with Development Tools

Jama Connect integrates directly with Jira to track development tasks. Jama Connect also has turnkey integrations for the most commonly used digital engineering and productivity tools. For example, I’m able to link my subsystem requirements to model elements in Simulink, again, with one click, links to the source artifacts. Pulling data from your digital thread into Jama Connect is not about duplicating work. Each team works in the tool fit for their purpose, and that work is reflected in Jama Connect for traceability and in context reporting. For teams managing product lines or customer-specific customizations, we can create catalog or library projects for reusable requirements.

Reusability and Component Management

With reuse, we can easily pull a reusable component and its related requirements into any project, and we can also use sync comparison to see which products a part or component is being leveraged in and how it may vary from what we have in our library. And that concludes our tour of the Industrial Machinery data model in Jama Connect. If you’d like a deeper dive or to learn more about Jama Connect Advisor and our live integration capabilities, please let us know.

To view more Jama Connect Features in Five topics, visit:
Jama Connect Features in Five Video Series

The post Jama Connect® Features in Five: Industrial Machinery Development Solution appeared first on Jama Software.

Next Generation Nuclear: Reactor Innovations Shaping 2025

The nuclear energy industry is about to undergo a significant change. A new generation of reactor technologies is emerging to offer safer, more economical, and efficient solutions as the world’s power demands rise. These cutting-edge concepts will transform our understanding of nuclear power, going beyond conventional models to provide clean and adaptable energy.

The main advancements in nuclear reactor technology that are anticipated to gain traction will be examined in this post. We will examine innovative designs such as Fast Reactors, High-Temperature Gas Reactors, and Molten Salt Reactors and talk about how they could transform energy production for a sustainable future.

The Evolution of Reactor Design

For decades, traditional nuclear power plants have been reliable sources of carbon-free electricity. However, the industry has moved to developing advanced reactors that improve upon these foundational designs. These next-generation technologies focus on passive safety systems, modular construction, and enhanced efficiency. This evolution allows them to not only generate electricity but also provide industrial heat, support renewable energy grids, and even address nuclear waste.

In addition to the advancements in modular construction and passive safety systems, the development of microreactors is gaining momentum. For instance, NANO Nuclear Energy’s KRONOS Micro Modular Reactor (MMR) represents a significant leap in reactor design. This high-temperature gas-cooled microreactor is designed to deliver 15 MWe (45 MWt) and can operate autonomously during grid outages. Its use of TRISO fuel and passive helium cooling ensures safety and resilience, making it a promising solution for energy resilience in urban and military settings.

We expect to see significant progress in regulatory approvals and pilot projects for these cutting-edge designs. This progress will bring us closer to commercial demonstrations that could reshape the global energy mix.

RELATED: Accelerate Nuclear Design Assessments and Reduce Certifications and Engineering Costs with Jama Connect^® for Nuclear Reactor Design & I&C Development

Innovations to Watch: MSRs, HTGRs, and Fast Reactors

Several advanced reactor types are leading the charge. Each offers unique benefits that make them suitable for different applications, from powering data centers to decarbonizing heavy industry.

Molten Salt Reactors (MSRs)

Molten Salt Reactors represent a significant departure from conventional water-cooled reactors. Instead of solid fuel rods, MSRs use nuclear fuel dissolved in a molten fluoride or chloride salt. This liquid fuel also acts as the primary coolant, operating at low pressure and high temperatures.

This design has inherent safety advantages. If the reactor overheats, a freeze plug melts, and the liquid fuel automatically drains into a secure containment tank where the reaction stops. While commercial applications are anticipated by the mid-2030s, important developmental milestones are expected in the coming year.

High-Temperature Gas Reactors (HTGRs)

High-Temperature Gas Reactors use gas, such as helium, as a coolant and operate at very high temperatures. The high temperature allows them to generate electricity with great efficiency and also makes them ideal for providing industrial process heat for applications like hydrogen production and chemical manufacturing.

The KRONOS MMR, developed by NANO Nuclear Energy, exemplifies the potential of HTGRs. This microreactor is not only designed for multi-decade use but also incorporates features like autonomous operation and resistance to cyber and physical threats. Its modular nature allows for scalability, making it suitable for diverse applications, including military installations and industrial use.

Fast Reactors

“Fast” neutrons are used in fast reactors to maintain the nuclear chain reaction. Compared to conventional reactors, this enables them to extract a notably greater amount of energy from uranium. This technology’s capacity to “breed” its own fuel and consume nuclear waste from other reactors, converting long-lived waste into a useful energy source, is one of its main advantages.

RELATED: Buyer’s Guide: How to Select the Right Requirements Management and Traceability Solution

Impact on the Future of Energy

These advanced reactor technologies promise to have a profound impact on the global energy landscape. Their key benefits extend beyond simple electricity generation.

Enhanced Safety and Cost-Effectiveness

New reactor designs incorporate passive safety systems, which safely shut down the reactor using gravity and convection without the need for external power or human intervention. This greatly improves the safety profile of nuclear energy.

These designs frequently incorporate modular construction. By producing smaller, standardized parts in a factory and drastically reducing construction schedules and costs, nuclear power can become a more affordable option, assembling them on-site.

The KRONOS MMR’s ability to operate independently of the main grid and its reliance on passive safety mechanisms highlight the strides being made in reactor safety. These features ensure that critical operations can continue uninterrupted, even in the face of external disruptions.

Integration with Renewable Energy

The operational flexibility of advanced reactors, like TerraPower’s Natrium, makes them ideal partners for renewable energy. They can ramp their power output up or down to balance the variable nature of wind and solar power, providing the grid with a consistent and reliable backbone of clean energy. This ability to integrate seamlessly with renewables is critical for building a stable, zero-carbon energy system.

Decarbonizing Industry

The high temperatures produced by reactors like HTGRs and MSRs can be used to provide process heat for heavy industries such as steel, cement, and chemical production. These sectors are historically difficult to decarbonize. By replacing fossil fuels with clean nuclear heat, advanced reactors can play a key role in helping these industries achieve climate goals.

Challenges and the Road Ahead

Advanced reactors have enormous potential, but there are obstacles in the way of their widespread deployment. Significant challenges that need to be addressed include managing early development costs, gaining public acceptance, and navigating complex regulatory environments.

But things are gathering steam as as investment in these technologies rises. For a number of innovative designs, we expect regulatory approvals to advance, opening the door for additional pilot projects and commercial demonstrations. These projects will provide essential real-world data on performance, safety, and economic viability.

As countries around the world expand their nuclear programs, the ongoing refinement of these technologies will continue. With a keen focus on digital engineering and operational efficiency, advanced reactors are poised to become a cornerstone of a clean, secure, and sustainable energy future.

Summary and Conclusion

The potential of nuclear energy is being transformed by advancements in nuclear reactor technology. The industry is moving toward safer, more adaptable, and more efficient power generation with designs like Molten Salt Reactors, High-Temperature Gas Reactors, and Fast Reactors setting the standard. Despite obstacles, these advancements will move us closer to a time when modern nuclear power and renewable energy sources coexist to meet the world’s energy demands without significant risk to the climate.

The post Next Generation Nuclear: Reactor Innovations Shaping 2025 appeared first on Jama Software.

In this blog, we preview a section of our recent Whitepaper – To read it in its entirety, visit “Empowering Complex Development with Responsible AI”

Empowering Complex Development with Responsible AI

Streamlining Efficiency and Compliance with Scalable Solutions

Product and system development is entering a new era, driven by AI innovation. Highly regulated industries like aerospace, automotive, medical devices, and financial services are facing unprecedented challenges such as escalating regulatory scrutiny in some cases, rising product complexity, and the relentless demand to accelerate time-to-market. Navigating these challenges requires a balance of innovation, compliance, and efficiency.

Artificial intelligence is beginning to demonstrate its potential in requirements management by automating manual processes, enhancing decision-making, and streamlining compliance. However, harnessing AI’s full potential requires a commitment to responsible AI practices, ensuring transparency, fairness, and security.

This whitepaper explores how AI is shaping the future of product development, offering insights into its applications, best practices for governance, and the role of Jama Software and AWS in delivering scalable, secure, and responsible AI solutions.

RELATED: Write Better Requirements with Jama Connect Advisor™

Today’s Systems Have Become More Complex

Systems of Systems (SoS)

• A System of Systems (SoS) is a collection of independent systems, integrated into a larger system that delivers unique capabilities
• It is difficult to produce accurate predictive models of all emergent behaviors, so global SoS performance is difficult to design
• Testing and verifying upgrades to a SoS is difficult and expensive (sometimes prohibitively) due to scale, complexity, and constant evolution

AI Applications in Complex Product Development

1. Challenges in Product Development

Complex product development demands businesses to manage an increasing number of variables, such as system interconnectivity, regulatory requirements, and shorter development
cycles. This intensifies the need for precise requirements management tools.

Modern systems, such as self-driving cars, embody system of systems architectures, integrating hardware, software, AI functionality, and cybersecurity. While this creates immense innovation opportunities, the complexity of these systems presents significant challenges:

• Predicting behaviors accurately
• Designing test frameworks for integration
• Scaling verification and validation processes efficiently

These challenges are amplified as the systems grow in complexity and sophistication. Accurately predicting behaviors becomes increasingly critical as interconnected components interact
in unpredictable ways, potentially leading to performance issues, safety concerns, or unintended outcomes. Addressing this requires advanced modeling and simulation techniques capable
of capturing the intricate relationships across subsystems.

Designing effective test frameworks for integration presents its own hurdles. Comprehensive testing must account for the diverse interfaces, software dependencies, and hardware configurations found in modern systems. Without a robust plan, teams risk delays, inefficiencies, and gaps in system validation that can lead to compliance failures or product recalls.

Scaling verification and validation processes to match the demands of high-complexity systems also requires significant innovation. Traditional, manual methods are often unable to keep pace,
resulting in slowed time-to-market and increased resource consumption. Automated solutions offer a scalable pathway, providing traceability, consistency, and efficiency needed to manage
these complex operations effectively.

Ultimately, organizations must balance innovation with rigorous oversight to address these challenges while ensuring safety, reliability, and compliance. Adopting tools designed for enhanced requirements management, streamlined traceability, and automated testing is paramount for achieving these goals in an evolving technological landscape.

RELATED: Buyer’s Guide: How to Select the Right Requirements Management and Traceability Solution

2. AI Solutions to the Challenges

AI-driven solutions are addressing these challenges in profound ways:

Automating Requirements Validation

• AI uses natural language processing (NLP) to verify that project requirements are complete, precise, and testable
• By identifying ambiguous requirements early, businesses reduce the risk of failures
• Automated test case generation cuts time and ensures that all requirements are tested

AI-driven solutions are fundamentally transforming the way businesses address traditional challenges in requirements management and validation. Through the use of natural language processing (NLP), AI automates the validation of project requirements by ensuring they are complete, precise, and testable. This advanced capability allows ambiguities or inconsistencies within requirements to be identified early in the development process. By addressing potential issues proactively, businesses can significantly reduce the risks associated with failures, enhancing overall project efficiency and success.

Ensuring Regulatory Compliance

• AI tools can help map requirements to stringent regulatory standards in sectors such as aerospace, defense, automotive, and medical devices
• Automated monitoring ensures continuous compliance throughout the product lifecycle, minimizing risks

Ensuring regulatory compliance is critical for organizations operating in highly regulated industries such as aerospace, defense, and medical devices. AI tools can play a pivotal role in this process by mapping requirements to stringent regulatory standards, ensuring that all necessary conditions are met without manual oversight. These tools offer automated monitoring, which enables continuous compliance throughout the product lifecycle. By reducing the likelihood of human error and streamlining the regulatory process, businesses can minimize risks and maintain adherence to evolving standards, ultimately supporting the success and longevity of their projects.

Accelerating Development Cycles

• Predictive analytics can enable immediate impact assessments of change requests, minimizing rework and speeding up delivery timelines

Predictive analytics play a crucial role in accelerating development cycles by enabling immediate impact assessments of change requests. This capability minimizes rework, allowing teams to address potential issues swiftly and efficiently. By streamlining workflows and reducing delays, organizations can significantly speed up delivery timelines, ensuring that projects are completed on schedule while maintaining high-quality standards.

Enhancing Collaboration

• Distributed teams benefit from AI-powered traceability that links requirements, tests, and design components in real time

Efficient collaboration is critical for success, especially for distributed teams. Jama Connect enhances collaboration by providing AI-powered traceability that seamlessly links requirements, tests, and design components in real time. By fostering better communication and streamlining the sharing of critical project information, Jama Connect empowers teams to work more cohesively, reducing misunderstandings and improving overall productivity.

TO READ THIS ENTIRE WHITEPAPER, VISIT: Empowering Complex Development with Responsible AI

The post Empowering Complex Development with Responsible AI appeared first on Jama Software.

Mergers and Acquisitions in MedTech: Positioning Your Company for Success

The MedTech Mergers and Acquisitions (M&A) scene is more active than ever. As global healthcare needs grow and regulatory landscapes shift, strategic acquisitions are becoming a key route to innovation, growth, and market expansion. For emerging MedTech companies, understanding this environment and positioning themselves smartly within it can shape their future.

Recent activity shows that opportunity is abundant for companies that are prepared. Strategic buyers are on the lookout for innovative technologies, strong product pipelines, and solid regulatory foundations. But having a breakthrough product is not enough. Success in M&A hinges on preparation, documentation, and systems that can stand up to intense due diligence.

The Current M&A Landscape: A Shifting Landscape

The MedTech M&A scene has evolved dramatically over the past year, marked by fewer deals but significantly larger transactions. While deal volume dropped by over 40%, the average deal size surged to $636 million, driven by strategic acquisitions like Stryker’s $4.9B purchase of Inari Medical and Thermo Fisher’s $4.1B buyout of Solventum’s filtration business.

Strategic Focus: Bigger Bets, Sharper Targets

Major players like Johnson & Johnson and Medtronic continue to lead the charge, but their strategies are shifting. J&J, for example, has spent over $30B on acquisitions since 2022, including Shockwave Medical ($13.1B) and Abiomed ($16.6B). These deals weren’t just about scale as they targeted technologies that redefine standards of care, particularly in cardiovascular intervention.

Medtronic, meanwhile, is leaning into tuck-in acquisitions to transform slower-growth units into innovation hubs. With 11+ deals in the past five years, the company is focused on strategic adjacencies and long-term portfolio optimization.

Trends Driving the Market

• Portfolio Shifts: Companies are divesting non-core assets and doubling down on high-growth areas like robotics, diabetes, and structural heart technologies.
• Private Equity’s Role: PE firms are increasingly active, both as buyers and partners in divestitures, helping streamline portfolios and unlock value.
• Cultural Fit Matters: Executives emphasize that successful deals go beyond financials. Shared values and aligned visions for patient impact are now critical to integration success.

What Strategic Buyers Seek: The Acquisition Criteria That Matter

To attract the right buyer, emerging MedTech companies need to align with what strategic acquirers value most. Here is what consistently matters:

Technology Differentiation & Market Position

Buyers want technologies that offer real clinical advantages such as better outcomes, simpler procedures, or cost savings. Proprietary tech backed by strong patents is especially attractive.

The best targets complement the buyer’s existing portfolio and address unmet clinical needs. Think AI diagnostics that plug into existing imaging platforms or minimally invasive tools that expand surgical options.

Regulatory Clarity

A clear regulatory strategy is a major plus. Companies that have engaged with the FDA, gathered solid clinical data, and understand approval pathways stand out.

Detailed documentation like pre-submission notes, trial protocols, and quality systems reduces risk and speeds up integration. It also boosts valuation.

Commercial Potential

Buyers assess market size, competition, and go-to-market strategy. Companies with clinical relationships, distribution channels, or early traction are more appealing.

Technologies that target large markets with clear reimbursement paths, and show signs of physician adoption, are especially valuable.

Financial Performance and Scalability

Even early-stage companies need to show a viable business model. Efficient use of capital, clear milestones, and scalable operations build credibility.

Detailed financials like cost breakdowns, revenue forecasts, and funding needs help buyers model ROI and integration scenarios.

RELATED: Buyer’s Guide: Selecting a Requirements Management and Traceability Solution for Medical Device & Life Sciences

Getting Acquisition-Ready: Preparing for Due Diligence

Due diligence represents the most critical phase of any acquisition process. Companies that invest in comprehensive documentation and systematic organization significantly improve their chances of successful transactions and favorable valuations.

Product Documentation

Keep everything up to date: design requirements, risk files, and testing protocols. Use document control systems to manage versions and changes.

Requirements management is key. Acquirers want to see how products were developed, validated, and maintained. Full traceability from concept to release builds trust.

Risk & Quality Systems

Risk documentation such as hazard analyses, mitigation controls, and post-market surveillance plans is essential. Quality systems should be fully implemented and certified (ISO 13485 is a big plus).

Design controls should be complete and easy to navigate: planning, inputs/outputs, reviews, V&V protocols, and change logs. A well-organized design and development file makes due diligence smoother and less risky.

Testing and Validation Evidence

Strong testing documentation is essential to prove your product’s safety and performance. This includes everything from software testing protocols and biocompatibility studies to electrical safety tests and clinical evaluations.

To stand out, companies should maintain:

• Detailed test plans
• Clear procedures
• Organized results

This shows a systematic approach to validating product performance. When testing documentation is thorough and easy to navigate, acquirers can quickly assess technical risks and regulatory readiness.

Validation should not stop at product launch. Ongoing monitoring, post-market studies, and performance tracking signal a commitment to continuous improvement — something buyers value highly.

RELATED: Industry-leading Practices Modernize Legacy Public Health Software System, a Deloitte Customer Story

Intellectual Property and Regulatory Assets

Your IP and regulatory documentation are more than just paperwork — they are strategic assets. Patent portfolios, FDA submissions, and clinical data all play a key role in valuation and deal structure.

To prepare:

• Keep patent files current
• Document freedom-to-operate analyses
• Develop a clear IP strategy

On the regulatory side, maintain organized records of:

• FDA correspondence
• Clinical trial data
• Post-market surveillance reports

Well-managed documentation shows a strong compliance history and gives acquirers confidence in your ability to navigate future regulatory hurdles.

How Jama Connect^® Supports M&A Readiness

Requirements management and traceability are critical for M&A success and that’s where Jama Connect shines.

The platform helps companies maintain acquisition-ready documentation throughout the product lifecycle by:

• Connecting requirements to design decisions, tests, and regulatory submissions — giving acquirers full visibility into development processes.
• Organizing documents with version control — making it easy for due diligence teams to trace product history and compliance.
• Generating detailed reports — showcasing the maturity of your quality management system and development discipline.
• Supporting collaboration across teams and locations — ensuring documentation integrity even in distributed environments.

With Jama Connect, medical device and life sciences companies can confidently present their development story and proof of compliance, a major advantage during acquisition discussions.

RELATED: Jama Connect for Medical Device & Life Sciences Development Datasheet

Building Long-Term Value Through Strategic Preparation

The MedTech M&A landscape is evolving fast. As healthcare needs grow and technologies advance, new opportunities are emerging for companies that are ready.

Success isn’t just about having a great product. It’s about:

• Operational excellence
• Regulatory sophistication
• Systematic development processes

Investing early in documentation, requirements management, and quality systems pays off. These capabilities lead to faster development, lower regulatory risk, and better product quality.

If you’re looking to strengthen your M&A readiness, start by evaluating your documentation systems. Book a demo with Jama Software to see how structured requirements management can streamline your development and boost acquisition appeal.

Note: This article was drafted with the aid of AI. Additional content, edits for accuracy, and industry expertise by Tom Rish and Decoteau Wilkerson.

The post Mergers and Acquisitions in MedTech: Positioning Your Company for Success appeared first on Jama Software.