Jump to content

  • Quick Navigation
Photo

Root Cause - sharing information globally

Share this

  • You cannot start a new topic
  • Please log in to reply
7 replies to this topic

mics0618

    Grade - Active

  • IFSQN Associate
  • 5 posts
  • 0 thanks
0
Neutral

  • United States
    United States

Posted 10 October 2014 - 05:23 PM

I'm looking for advice on sharing information if you are part of a global company.  If you don't have access to a globally shared software for root cause, CAPA, etc. what kind of system, process, or tools do you use to share information?  How can you ensure a problem at one site doesn't happen at another site?

 

Thanks.



agasr

    Grade - AIFSQN

  • IFSQN Associate
  • 37 posts
  • 9 thanks
2
Neutral

  • United States
    United States

Posted 10 October 2014 - 08:52 PM

Hi -

 

In lieu of a common database that would house all CAPAs, Some of the best practices/approaches I have seen around this are

 

Agree on the inputs (Food Safety, Quality, Internal Audit, External Audit, Customer Complaints, etc. agree on the severity of those inputs for which a detailed CAPA would be communicated amongst the different groups). A summary of all the issues (inputs for CAPA) can be shared in any form like simple set of numbers or as graphs for comparison & improvement sake, on a regular basis. But as details, only the agreed significant ones will be communicated as separate document to serve learning, awareness needs to prevent similar issues. A tip on deciding the input that is worth communicating globally would be, anything that would impact Food Safety, Regulatory, Customer expectations & Compliances. When such a system or similar system is implemented, eventually the calibration process happens for it to more meaningful and helpful & it runs on its own from there on.

 

I have seen companies sharing such documents in word format with pictures or as Pdfs to start with via emails. Later they would move to a shared folder or database where such things will be housed for future references companywide or across multiple sites.

 

I hope this helps.

 

Regards,



Charles.C

    Grade - FIFSQN

  • IFSQN Moderator
  • 20,542 posts
  • 5662 thanks
1,544
Excellent

  • Earth
    Earth
  • Gender:Male
  • Interests:SF
    TV
    Movies

Posted 10 October 2014 - 11:35 PM

I'm looking for advice on sharing information if you are part of a global company.  If you don't have access to a globally shared software for root cause, CAPA, etc. what kind of system, process, or tools do you use to share information?  How can you ensure a problem at one site doesn't happen at another site?

 

Thanks.

Dear mics,

 

What level of security are you expecting ?

 

Better than email ?

 

Rgds / Charles.C

 

PS - for non-Americans(?), I believe CAPA = Corrective and Preventive Actions


Kind Regards,

 

Charles.C


mics0618

    Grade - Active

  • IFSQN Associate
  • 5 posts
  • 0 thanks
0
Neutral

  • United States
    United States

Posted 13 October 2014 - 07:05 PM

Email is fine from a security standpoint.

 

Are there any example root cause/CAPA reports someone can share?  I'm looking for a report template that summarizes an invesitigation at one site that can be shared with several other sites so they can look for preventive actions.

 

Thanks.



fgjuadi

    Grade - PIFSQN

  • Banned
  • 898 posts
  • 203 thanks
28
Excellent

  • United States
    United States
  • Gender:Male

Posted 13 October 2014 - 07:30 PM

Oh, we used to get these when I worked at a huge company with 40 different factories all doing the same thing.  We called them "Quality Bulletin" - there would be a big picture of the disaster (one time a lab fire where the alcohol stored caught flame, another where the preform blower thingy (technical term) was malfunctioning and creating slight smaller bottles) , the literally bullet points written by the offending plant on what happened.   Then, on our monthly call, we'd go through each one of them that had cropped up, and talk about the solution. 

 

I always thought it was more of a shame thing than a "this is helpful to you" thing  :dunno:  - if you're only a handful of plants, and you think people will actually read or use it instead of throwing it away,  you can use a shared drive with a folder Labeled "Plant X CAPA log"


.--. .- -. - ... / --- .--. - .. --- -. .- .-..

ericcaces

    Grade - Active

  • IFSQN Active
  • 7 posts
  • 1 thanks
0
Neutral

  • Chile
    Chile

Posted 16 October 2014 - 08:12 PM

Example

Attached Files



Thanked by 1 Member:

bacon

    Grade - MIFSQN

  • IFSQN Member
  • 173 posts
  • 77 thanks
18
Good

  • United States
    United States
  • Gender:Male
  • Interests:NOAA HACCP & Better Process Control School Certified, GFSI Schemes (BRC/SQF) Certified, Woolworths Quality Assurance (WQA), USDC, FDA, U.S. Army and client audit preparation; Seafood Processing, Supplier Approval

Posted 17 October 2014 - 04:46 AM

Here is one, a wee bit simple but can absorb the amount of possibilities.

I have used it with different companies, BRC and SQF.

-Baron

Attached Files


____________________________________________________
><((((º> Salmon of Doubt & NOAA HACCP lover of Bacon

Thanked by 1 Member:

Charles.C

    Grade - FIFSQN

  • IFSQN Moderator
  • 20,542 posts
  • 5662 thanks
1,544
Excellent

  • Earth
    Earth
  • Gender:Male
  • Interests:SF
    TV
    Movies

Posted 17 October 2014 - 10:11 AM

Dear mics,

 

i deduce that the Best Practice answer to the OP is to use a Corrective Action Form, including a section on Root Cause(s), presumably transmitted by email.

 

One limitation IMEX is that many CAs may well be interesting to other sites but not directly relevant unless the "situations" are comparable. Likely exceptions might be relating to prerequisites, eg missing screws upon reassembly of a machine (probably not exactly a "revolutionary" News item of  course :smile: )

 

Rgds / Charles.C

 

.


Kind Regards,

 

Charles.C




Share this


Also tagged with one or more of these keywords: root cause, global, information sharing, management

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users