Thursday, July 29, 2010
Welcome,  Register  | 
CIP WORKFLOW AND ROUTING

CIPs from any source can be classified as corrective or preventive action according to the severity of the problem deemed by the CIP coordinator. The long path assures that the CIP root cause analysis & investigation is reviewed and approved prior to taking the action. Verification and validation of the action are also necessary for the CIP to be considered closed.

CIP WORKFLOW SCREEN SHOTS
CIP Coordinator decides if the opportunity for improvement reported is a Corrective Action, Preventive Action or a simply Correction.  By relieving the requestor from that task, you are letting them report any opportunity or problem they encounter.    CIP Coordination - Assign Routing
Once CIP Coordinator decides if the problem is a corrective action, preventive action or correction, then he/she chooses the path.  Long Path and Short Path are available when the problem is deemed corrective action or preventive action.  CIP Coordination Path
CIPs deemed Corrective Action and assigned a Long Path, will go thru a seven step process: Request, Coordination, Investigation, Investigation Verification, Action, Action Verification and Validation.  CIP Corrective Action Long Path
CIPs deemed Corrective Action and assigned a Short Path, will go thru a five step process, thus saving you a lot time and resources: Request, Coordination, Investigation, Action Verification and Validation.  
CIPs deemed Preventive Action and assigned a Long Path, will go thru a six step process, thus saving you a lot time and resources: Request, Coordination, Investigation, Investigation Verification and Action Verification.  
A detail history tab, will show you exactly what happened to the CIP, when it was requested, when it moved through the different stages and any comments available.  
   
Mireaux Management Solutions
info@mireauxms.com
 
Home   |   Products & Services   |   Resources   |   Company Profile   |   ISO Vanguard Blog   |   Contact Us
Copyright 2009 by Mireaux Inc.   |  Privacy Statement  |  Terms Of Use