Batch pre-check
Inspect folder-name prefixes, unexpected nested folders and JPG/TIF counts before processing starts.
Eleway software · Local-first processing
CRATOR
OMR and document processing
A Windows-based processing console that brings batch checks, OMR recognition, barcode decoding, optional contact extraction, image compression and structured export into one monitored workflow.
Capabilities
One console for the work around OMR processing.
CRATOR addresses the operational steps surrounding recognition—not only the bubble-reading engine. It helps teams prepare incoming batches, run selected programs, monitor progress and open the finished outputs.
Marker and no-marker processing
Use marker-based alignment with crop-quality checks and retry through the configured no-marker template when required.
OMR and barcode recognition
Read configured response fields and barcode metadata from prepared image batches on the local Windows machine.
Exception-aware handling
Support conventional fills and selected thin-mark styles while separating failed or multi-marked sheets for review.
Optional contact extraction
Send only the configured contact-information crop to Gemini and keep successful OMR output when the connected module fails or stops.
Operational output
Create final CSV output, optional Microsoft Access output and compressed JPG copies when selected.
Operational flow
From prepared image batch to usable output.
CRATOR brings the supporting checks and processing stages into one monitored console.
Check the batch
Inspect folder naming, nested folders and JPG/TIF counts before processing begins.
Choose the work
Select OMR, contact extraction, JPG compression or the required combination.
Process and monitor
Run local recognition and barcode decoding while tracking each selected program separately.
Open the output
Receive final CSV output, optional Access output and compressed JPG copies where selected.
Deployment and data boundary
Local core. Optional connected extraction.
The distinction matters for deployment, privacy and procurement. Core OMR and file operations remain local; Gemini contact extraction is a separate connected module.
What stays local
Folder checks, image preparation, OMR recognition, barcode decoding, compression and CSV generation run on the user’s Windows computer.
What uses Gemini
When contact extraction is enabled, only the configured contact-information crop is encoded and sent to the Google Gemini API.
What the environment needs
CRATOR is Windows-oriented. Gemini requires internet and an API key. Microsoft Access output requires Access or the Access Database Engine; CSV remains the baseline output.
Practical applications
Where CRATOR can fit.
CRATOR is designed for organisations processing prepared OMR image batches and needing controlled, structured output.
01Examination and assessment operations
02Schools, universities and testing organisations
03Recruitment, certification and scholarship processing
04Document-processing teams using CSV or Access workflows
Next step
Start a conversation Want to assess CRATOR for your operation?
Tell us about the current workflow, source material and output you need.