CAPA – Corrective Action Preventative Action
FRACAS – Failure Reporting And Corrective Action
FMEA – Failure Mode effects Analysis

Unlike FMEA, some (probably many) people have never heard of FRACAS. When I was explaining FRACAS to some people, someone said “oh that’s CAPA, we do that now.” Although CAPA and FRACAS share features, there are key differences.

Timing – FRACAS deals with products before release for sale, and CAPA with products after release for sale. FRACAS however, can also be continued after products are released.

Responsibility – In medical device companies, FRACAS is usually conducted by R&D and CAPA by service and manufacturing. Whereas, this may not sound like a big difference, it is. For example, service is more concerned with keeping customers happy than with corrective action.

Data source – In CAPA, there are two data sources, (customer) complaints and (manufacturing) nonconformities. This sets up the possibility for two CAPAs, which may not talk to each other; namely, a CAPA in manufacturing to deal with nonconformities and a CAPA by service to deal with customer complaints. In a FRACAS that is conducted before release for sale, the data source is “events”. An event is an observed action that has the potential to cause harm, increased cost, a return, a complaint, and so on. Note that not all events will lead to complaints. For example, a clinician may disregard an erroneous result and not complain about it.

Metrics – While anything is possible, the reliability growth management metrics associated with FRACAS are almost never used with CAPA.

Regulations – FDA requires medical device companies to have procedures in place to address nonconformities and complaints. This is traditionally handled by CAPA. There is no requirement for FRACAS.

To sum up, is CAPA the same as FRACAS? No, not by a long shot.

One Response to CAPA versus FRACAS

  1. Chris Swallow says:

    This is an interesting article but I would question whether or not the alignment indicated is correct; FRACAS is most commonly considered as a tool for Field Failure reporting, whilst CAPA has great connectivity into design.

    In my experience, most companies that I have worked with use FRACAS to deal with the Corrective Action loop of a Fielded-Failure item, whilst CAPA is the extended effort of that Corrective Action from the Field team back into Design and then, most crucially, the Preventive Action developed to assure the Failure does not occur again.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: