Jump to content

CMM run per day.


---
 Share

Recommended Posts

Got an interesting question. I have set up 2 CMM's to run on AutoRun. I am trying to see if there is a way to gather how much a CMM has run. Is there an internal "counter" folder? Don't care about what part it ran, nor any Piweb data. Just simple....amount of runs per day, per week, etc.  If I can see the data, then I can sort. By date.       

Example. 1st shift ran cmm(s) 232 times. 

                2nd shift ran cmm(s) 150 times.

                3rd shift ran cmm(s) 80 times.   

Its a project requested by management . They basically want to see the amount of output per shift.  Yes, I do have a "results" folder, but i don't trust the output. Being that if the incremental part number is not changed it will simply copy over the past result. I can count the number of printouts per day on the printer but I'd have to literally be here all 4 shifts. The request is for 3 months of data.  I can easily estimate, but looking to see if there is actually a "counter" internally.  I'm sure there is, as i have seen the folder that defines number of hard hits/crashes. I'm just not sure it is accessible or recommended to casual operators.

THANKS

       

Link to comment
Share on other sites

Please sign in to view this quote.

Maybe you could check writes to C:\Users\Public\Documents\Zeiss\CALYPSO\workarea\basesystems with some script?

Link to comment
Share on other sites

Please sign in to view this quote.

Please sign in to view this username.

 Yes, I have done this in the past. First question - Do you have PCM? If you have PCM, it is very easy to write the needed information to a text file for manipulation outside of Calypso. Use "getRecordHead(insertVariableHere)" to log program name, operator, time, and measurementDuration. Then use Task Scheduler and a PowerShell script to create a daily report (HTML is best) to automatically be sent to everyone's inbox. You will be management's hero! (no pay increase of course 🤣)

Link to comment
Share on other sites

Beware of the Cobra Effect.  If you don't know what that is then look it up.  

When I solely tracked number of parts inspected, I found that 2nd shift operators would just run the quickest/easiest parts, thereby inflating their numbers, and leave 3rd shift to run the more difficult/longer run time parts.  

  • Like! 1
Link to comment
Share on other sites

Does Observer require a dashboard, third-party software?

I pull the ProgramDurationRecord.xml file into excel and chart it, it's a PITA.

Edited
Link to comment
Share on other sites

The Cobra Effect is a situation where an attempted solution to a problem actually makes the problem worse because of unintended incentives.

The term comes from a story during British colonial rule in India. Authorities were worried about venomous cobras, so they offered a reward for every dead snake. At first, it seemed effective—but people began breeding cobras just to kill them for the bounty. When the government discovered this and canceled the program, breeders released the now-worthless snakes, leading to even more cobras than before🤣

Link to comment
Share on other sites

 Share

×
×
  • Create New...