Timeline: Product Data Issue

Apr 26, 2015

SC/GF move INI from J to K

Method used doesn't actually fix the problem, only masks it temporarily.

Apr 29, 2015

CG RAS code change

Load of product data on changeover, once per hour, and on bubble and test print.

Period: Apr 29, 2015 to Oct 28, 2015

CG RAS code timespan

Load of product data on changeover, once per hour, and on bubble and test print.

May 14, 2015

ZC x 44 possibly At-Risk 20:00-21:00

If the code was a problem at this point then these units may be at risk. Previous label ZB

Aug 19, 2015

ZC x 184 possibly At-Risk 14:08-14:47

Previous label 4V. Customer would see another companies logo on parts.

Period: Sep 19, 2015 to Oct 28, 2015

SC chosen timeline

SC was insisting the last EXE was good from 19-SEP.
His timeline began here, I refused the date.
2-3 more exe's were created after this point.
All information pointed at April/May.
Why did he say its been happening months, then decide the last exe was good?
How would he KNOW that exe was good?

Oct 12, 2015

20,000x more network access than necessary

Printing code hitting network 100x more frequently than needed when loading product data. Product data loaded every unit, multiplying issue by another factor of 200-2000x depending on build size.

Oct 15, 2015

Network Inefficiency Raised, Heated Debate Ensues

SC insistence that quality will have to check every label in spite the obvious solution to test our load procedures. I respond by stating I'll put it in a report and we'll get others involved in the discussion before we hand quality a huge workload.

Oct 24, 2015

RAS5 - 05x1 found with incorrect label

Saturday, SC on-call
Previous label 74

Oct 26, 2015

SC tells me about problem

Load of product data on changeover no longer present in application.

Oct 27, 2015

I refuse SC's change date of late September

I explain the code shows clearly that the mod happened in April. How can the operator claim its been happening 'months' yet SC wants to go back only 6 weeks?

Oct 28, 2015