hexagon logo

Falsifying PDF Reports

I just found an instance to where someone copied a passing report, pasted it and changed the file name to a failing part number. Does anyone have anything program wise to prevent this?

Details:

Operator scans a barcode the inputs a report comment with the serial number. Then I use assignments to take that input and use it to print a pdf with the serial number as the filename. If a part pass the inspection, it goes to a passing folder and it goes to a failing folder if there is 1 or more out of tolerance dimensions. So I have some redundancy with the serial number being present in the report comment and as the filename. Our production software checks to see if the serial number is in the passing folder in order to move it on to the next step. So if it fails, it cannot move forward and it has to be scrapped or reworked. Pretty simple.

Machinist had 2 parts pass the CMM and the 3rd failed last Friday. I have a CNC programmer troubleshooting the CNC machine to make adjustments and he wanted to re inspect the bad part. Problem was we couldn't find it in the scrap bin and didn't know where it was. So he wanted to see the good reports and as we looked at the filenames (serial numbers) we saw the failing serial number in the passing folder. We opened the report and the report comment had a different serial number in the field. It appears the machinist opened the passing folder, copied a passing report, pasted it, and changed the file name to match the failing part. This would allow him to move the part through. So I have 2 identical reports with the exact same time and deviations but with the same report comment serial number and different filename. Luckily we caught this before it left the building.

Now I have IT working on removing filename edit access so now we can't edit filenames but you can still copy a failing report from the failing folder and paste in in the passing folder. They are still working on that part.

Anyway, does anyone have any advice or preventative measures so this doesn't happen again utilizing pcdmis?
Parents
  • Reprimand the individual! You shouldn't have to build integrity into software, a bad person will always find a way.

    With that said... I denote an NG at the end of a failing report. Set it up to READ access only and if they manage to move a 'bad' report into the good directory shame on them for placing a big fat NG report in there (HAHA!) I initially created this to be able to easily spot bad reports in a single directory though I switched to a dual pass/fail hierarchy many years ago and kept the NG eg. PART#_OP_SN_1_NG.RTF << fail, PART#_OP_SN_1.RTF << pass
Reply
  • Reprimand the individual! You shouldn't have to build integrity into software, a bad person will always find a way.

    With that said... I denote an NG at the end of a failing report. Set it up to READ access only and if they manage to move a 'bad' report into the good directory shame on them for placing a big fat NG report in there (HAHA!) I initially created this to be able to easily spot bad reports in a single directory though I switched to a dual pass/fail hierarchy many years ago and kept the NG eg. PART#_OP_SN_1_NG.RTF << fail, PART#_OP_SN_1.RTF << pass
Children
No Data