Demo: Scanning Handwritten Tickets
Here are the steps involved when scanning in a batch of handwritten tickets from a client:
Step 1: Prepare Tickets
To ensure a quality scan of all the tickets in the batch we do the following before scanning the tickets into the system:
- Remove and discard all tickets marked "VOID"
- Verify that all tickets are facing the same direction
- Remove all staples and repair rips and wrinkles in the ticket
Fig. 1 shows an original handwritten ticket sent to us from a client.
(Fig 1. Original Ticket)
Step 2: Scan Tickets
All tickets are scanned in using a sheet-fed scanner for fast and accurate scanning.
Fig. 2 is an image of the scanning software scanning in a batch of tickets.
(Fig 2. Scan Server)
Step 3: Recognition
The Recognition Server process attempts to convert the hand written portions of the ticket
into text that can be stored in a file on the computer.
Each ticket will receive an average confidence rating, if the rating is lower than a certain
percentage the ticket will be put into quality control so it can be rescanned and processed.
This ensures that each ticket is scanned in properly and less mistakes are made.
Fig. 3 Shows the recognition software processing a batch of tickets.
(Fig 3. Recognition Server)
Step 4: Validation
The Validation Server allows the operator to verify that each ticket's data
was properly reconginzed in step 3. If the data is incorrect the operator can
fix the mistake and move on the the next ticket. These changes will be recorded to
the text file for future processing.
Fig 4. Shows the validation process on a batch of tickets.
(Fig 4. Validation Server)
Step 5: Release
The final stage in the process is to release the tickets
into long term storage. The Release Module
releases the image files to permanent storage and the data
values to a flat text file.
(Fig 5. Release Server)
Step 6: Copy To Client's Machine
The tickets and images are then moved to our FTP site to await
pickup from the client's machine. A nightly process
runs on the Client's machine that logs into our FTP site,
copies the data and images, and loads them into the databases
for storage. After this process is complete the tickets can be
used like any other ticket on the system.
(Fig 6. Front view of ticket)
(Fig 7. Back view of ticket)
(Fig 8. Reports)
|