QuestionsQuestions (LTO MEMORANDUM CIRCULAR NO. VPT-2010-1375)
Its purpose is to provide guidelines for the quarterly validation of Optical Mark Reader (OMR) software and hardware used in the Automated Driver’s License Examination System (ADLES), to ensure credibility, integrity, proper utilization, and compliance with the Office’s Quality Management System standards.
The OMR software and hardware are part of the Driver’s License System Core Application Module, specifically the Automated Driver’s License Examination System (ADLES).
The ITPEMC Technical Team and the ITPEMC-DLS Team are tasked to conduct the validation test.
Validation must be done onsite every quarter of the year, with at least two (2) sites per quarter, or more as the need arises.
The test sites will be identified by the teams mentioned in the circular (ITPEMC Technical Team and ITPEMC-DLS Team).
The circular instructs that the OMR should be tested using the listed transaction types, selected on a random basis, to verify that the OMR performs reliably across different exam/license scenarios.
2 New Non Pro; 2 New Pro; 2 Non Pro Dormant; 2 Pro Dormant; 2 Non Pro to Pro; 2 ARC; 2 New Conductor’s License.
The answer sheet must be shaded and checked in accordance with the Automated Exam Guidelines.
Validation is declared passed if all results obtained from the script and manual checking tally with the results given by the OMR software.
The testing is declared failed. An investigation relative to the problem encountered must be done by STRADCOM, and corrective action must be approved by the ITPEMC.
A resolution shall be prepared by the team that conducted the validation test, based on the results of the test made.
The OMR is plugged in and kept running continuously for 24 hours.
Feed answer sheets into the OMR, count how many can be scanned per minute, compute an average based on five (5) one-minute intervals.
Scan 150 answer sheets, manually check each sheet, and compare the manual scores with the tabulated results from automatic scanning. Compute the percentage of error, then compare it to the hardware specifications for margin of error.
It establishes an internal governance step: failures must trigger investigation by STRADCOM and subsequent corrective action cannot be implemented without ITPEMC’s approval, ensuring control and accountability.
Both are covered. The circular is explicitly titled as guidelines for quarterly validation of OMR software & hardware, and it includes both script/manual tallying (software/performance accuracy) and hardware procedures like stress test and efficiency tests.