Point base system for errors.

[Mark]

Hi all,

We (2 departments) have been tasked with designing a point base system for
QC errors. We will be using mySql for database with access as the GUI front
end. I’m not even sure how to start something like this using the condition
below.

Is there some examples of this logic anywhere? Also, would it be better to
do the calculations on the SQL side or in the access GUI?


ï¬ One free training error per process
ï¬ Verbal corrective action at 6 points
ï¬ Written corrective action at 10 points
ï¬ Final corrective action at 16 points
ï¬ Termination at >20 points and after Final corrective action step reached.
ï¬ 2 points will be deducted after every 30 calendar days from last error
without making any errors
ï¬ Minimum points for an associate is 0
ï¬ All errors will count until the associate reaches a level. Once the level
is met, then a corrective action must be completed before the next errors
committed by the associate continue to count to the next level.
ï¬ Corrective actions are to be completed by the next shift worked by that
associate.

 

[claus-peter erdmann]

Hi all,

We (2 departments) have been tasked with designing a point base system for
QC errors. We will be using mySql for database with access as the GUI
front
end. I’m not even sure how to start something like this using the
condition
below.

Is there some examples of this logic anywhere? Also, would it be better
to
do the calculations on the SQL side or in the access GUI?


ï¬ One free training error per process
ï¬ Verbal corrective action at 6 points
ï¬ Written corrective action at 10 points
ï¬ Final corrective action at 16 points
ï¬ Termination at >20 points and after Final corrective action step
reached.
ï¬ 2 points will be deducted after every 30 calendar days from last error
without making any errors
ï¬ Minimum points for an associate is 0
ï¬ All errors will count until the associate reaches a level. Once the
level
is met, then a corrective action must be completed before the next errors
committed by the associate continue to count to the next level.
ï¬ Corrective actions are to be completed by the next shift worked by that
associate.

 

[KARL DEWEY]

How are you collecting the information?

- after every 30 calendar days
- until the associate reaches a level.
- Termination at >20 points
- after Final corrective action step reached.
- Once the level is met
- by the next shift worked
This is a lot of data elements to collect or link from other
tables/databases - Level, Shift.

Some of these sound very subjective (speaking as a lapsed certified QA).

 

[Mark]

How are you collecting the information?

- after every 30 calendar days
- until the associate reaches a level.
- Termination at >20 points
- after Final corrective action step reached.
- Once the level is met
- by the next shift worked
This is a lot of data elements to collect or link from other
tables/databases - Level, Shift.

Some of these sound very subjective (speaking as a lapsed certified QA).

Per incident. When QC finds an error they would log it in. Then once
logged it would cycle through the algorithm and update a table with the
correct point status.

 

[KARL DEWEY]

it would cycle through the algorithm and update a table with the correct
point status.
Table to collect data but not to retain proccessed information.

What is your proposed structure? Maybe something like this --
tblQCAudits --
AuditID - primary key
AuditDate - DateTime
AuditorID - foreign key
AuditeeID - foreign key
ProcProd -

tblAuditFinding --
AudFindID - primary key
AuditID - foreign key
Severity - (Maj, Min, Obsvr, None)
ReqMnt -
Ref - Law, Contract, Process document Specification, etc
Finding -
Corrective -
Root -
Follow-up -
CloseDate -