Separate known-profile matches from unresolved observations

Define the reference population and acceptance criteria before interpreting a known or unknown label. An unresolved observation may reflect missing enrollment or poor visibility, so the next step should be verification or assistance.

Catalog workflow. Confirm detector availability, permitted use and event delivery for the proposed deployment. Website examples are illustrative.

Define known-profile classification

Example

Without IVISIONStandard CCTV feed

With IVISIONIllustrative event overlay

The Process

How It Works

Unknown is a matching state Route matching exceptions consistently.

Prepare the view

Approve the known-profile population.

Assess the observation

Validate matching and ambiguous-result handling.

Review the evidence

Review the classification with image quality and source context.

Choose a response

Use a credential or visitor process to resolve uncertainty.

Explore Your Options

Explore Related Capabilities

Dimension	Known-person and unknown-person classification	Stranger / Unknown Person Alert
Observation	A face observation with or without an accepted profile association.	An observation without a confirmed known profile.
Event criteria	A supported matcher applies validated acceptance criteria.	The available matcher returns no acceptable association.
Monitoring setup	Confirm profile population, threshold and ambiguous-match handling.	Confirm known population, threshold and duplicate policy.
What it cannot establish	Cannot establish legitimacy, threat or whether someone has visited previously.	Cannot prove danger or that someone has never visited.
Practical outcome	Make matching state explicit without judging the person.	Resolve unfamiliar arrivals through a defined reception process.