Hi,
In order to be acceptable in court, speed cameras need to be checked daily, requiring a police car with an accurate speedometer to drive past the camera, every morning, at a specified speed.
When speed cameras were first introduced, there was a story about a young lad standing in front of a camera, whirling a bean can on a bit of string round his head.
In a similar sort of vein, in the early days of DVLC, it was suggested that ADP problems would be best sorted by not trying fix them. Just let them run, and the "ignorant" girls on the keyboards would work out a solution. Many a true word ....
602
PS, When I had a DVLA data input team (70 militant ladies) I devised a system that enabled me to guickly identify "patterns" .... two ladies who regularly went to the "Ladies" at the same time, or regularly pulled a Sicky on the third Tuesday of every month, etc.
I didn't implement it, their lives were too controlled as it was (big softy, me) ... although if they finished a batch, and there was no work waiting, they were allowed to sit at their machines, and do their catalogs, etc. But instant recovery as soon as the next batch of work arrived. If my memory is correct, they were expected to maintain 13,000 keystrokes per hour, and allowed a set number of mistakes. (2 per 1000? One lady was a trouble maker .... 36,000 keystrokes per hour and zero mistakes. She spent so much time walking to get her next job, that she didn't spend enough recorded time actually keying. Solution ... she was allowed to pick up three jobs at a time, cut down on the walking.
36,000 keystrokes per hour? I'll let you calculate how many characters she keyed per second ... virtually non-stop, all day, with no mistakes. Mistakes were identified by a second operator keying the batch again, and the CPU compared the two inputs, stopped the keyboard until the discrepancy was corrected, either way. OK, it could be corrected incorrectly. Sorry!
Remember this, next time you scribble your details on an application form.
602