The pipeline
- 01MaskFictitious number. Flap torn off.
- 02ScanOverhead or high-speed. Books may be opened.
- 03CloudPrivate server. Copy, pages, quality.
- 04AgencyEvery copy reviewed page by page.
- 05PacketsApproved books assigned to examiners.
- 06RevalUnmarked original. Marks stored separately.
Direct answer
In a university OSM deployment, the exam cell (or equivalent) controls who may mark, which packets they receive, and whether evaluation is finishing on time. Examiners mark on screen; the university watches a realtime pipeline: scanned → agency-approved → assigned in packets → submitted — plus revaluation queues on the unmarked original.
How it works
Identity is already masked (fictitious number, flap torn) before images reach examiners. Examiners are empanelled and given credentials. Copies that pass automated identification (copy id, page count, quality) and agency page-by-page review become assignable packets. Progress is visible by course or paper as it happens. Follow-up (email, messaging, or an agency call desk) exists because some examiners will lag — software does not remove academic calendars.
Key considerations
- Confidentiality: examiners should see assigned copies, not the entire exam dump.
- Scheme configuration must be frozen before a rush of assignments.
- Result handoff should be a defined export or integration, not a spreadsheet afterthought.
Avid’s approach
Avid OSM includes a university panel for this control loop. Documented production use began in 2020 at Dr. Bhimrao Ambedkar Law University, Jaipur. Marks can later sit in Avid University ERP COE workflows when both systems are in place.