ComparaView is a web-based workflow application to manage a variety of activities related to maintaining a facial recognition system.
For instance the following activities may all be managed through the use of ComparaView:
Pre-enrolment Triage | |
Post-enrolment data cleansing | |
Finding identities of interest | |
Ad-hoc list processing | |
Deduplication | |
Data cleansing of new or 'wild' image sets |
ComparaView helps run identity resolution, deduplication and triage activities against a facial recognition system.
Cleansing a biometric system produces large amounts of data, typically requiring human processing. To effectively manage the human aspect of this process a workflow system is an ideal solution to keep control of all the 'moving parts'.
Features of ComparaView which assist with these processes include:
Role based user rights only permit people to do what you want | |
Restrict access to data control who sees what | |
Ensure consistency every case is handled in the same manner | |
All decisions are accountable know who did what | |
Post-event reporting to assist user aptitude and workload management |
Having said that, whilst ComparaView's origins were in cleansing facial recognition data, the reality is any time a workflow can be defined concerning a facial recognition system, ComparaView is potentially the answer.
The workflow is the basis by which all work in the system is managed. We've built ComparaView to have 'just enough' workflow so it doesn't contain feature bloat sometimes found in workflow systems where you end up paying for functionality you just don't require. The workflow is configurable post-deployment, allowing queues to be defined as additional business processes are discovered.
Driving the workflow are business rules contained in plugins. These plugins are dynamically loaded at system start-up, affording ComparaView the flexibility of further post-deployment configuration. This allows customisation to every business scenario without the need for re-deployment or upgrading the software...if there's a change in business rules the plugins only need be updated.
The user interface is delivered via a web-browser, meaning that once the server-side part of the system is configured deployment to new workstations is as simple as distributing a URL.