Investigate a case

An IREX  instance might be as big as several hundred or even thousands of cameras (and other sensors) in size. Taken together, those sensors produce an enormous array of events, stored in the archive together with snapshots and videos in full. Typically, of those events only a few are relevant to the post-incident analysis task the user is currently busy with.

So, the problem arises of finding those relevant events in the archive among irrelevant ones and comprehensively presenting them on the screen. The solution comes as Searchveillance™ - the patented technology to find people, vehicles, and scenes in the Archive. Searchveillance™ saves man-days of labor-intensive video analysis during law enforcement operations and investigations.

Using Searchveillance™ in any way requires a Case ID to be provided.

Click Events on the main menu - the event screen opens, which looks like:

• This, if over 24 hours have passed since the last event search had been run.



• This,  if less.

Click Back to Previous Results to return to the results of the latest previous event search.

Asynchronous event search 

IREX implements the asynchronous processing scheme of search (filtration) queries for events to lower the workload on the server in big clusters. This means that such queries from multiple clients are accumulated on the server into an ordered queue, to be then executed strictly in chronological order. Execution of a query may take quite a while.

Basic principles and limitations

• Event search (filtration) queries from multiple clients are accumulated on the server into an ordered queue to be then executed strictly in chronological order. 
• Every single client may have only one query waiting to be responded to at a time; the next query can only be sent after the previous one has been responded or canceled.
• A query not responded yet can be canceled.
• While a query is waiting for a response, all the system functionalities stay active, except for those for making more queries. If the user is currently on a different web page of the website or app, query execution notification will be shown.
• Last query results stay on the screen for 1 hour.
• A user can be logged in on multiple devices or in multiple windows, but still only one query can be sent at a time from all devices (windows) taken together; the same query results will show on all devices (in all windows).

Asynchronous query routine step-by-step

1. Go to the Events screen.

The screen is empty on the first visit within the past 24 hours; otherwise, the last query results show.

By default, Date and Time = Today is active and it will stay such until it is explicitly switched off.

2. Switch on other query filters (e.g. Appearance - Gender = Male).
3. Press Apply on the filter pane.

Pressing the Apply does not send the query.

4. Press Search on top of the screen.

As soon as this is done:

The query goes to the server to be currently the last in the queue.
Filters and text boxes on the page get disabled.
The notification shows in which the Cancel search button gets enabled.

5. Use the functionalities on the other pages of the application according to need; while on another page (except for those in the User Menu) the indicator is shown.

6. As soon as the query is executed, the indicator gets green; if it is a failure - red.
7. After the query is executed successfully, 24 event cards will be shown; click Show more to show next 24 ones. However, the total limit is 24x15 events.
8. Click Reset on top of the window to clear the filters or simply add/remove new search criteria to go to the next search. Anyway, a message shows as a reminder to press Search again.

Searchveillance™ event filters

Searchveillance™ powers a rich set of filters offered on the Events screen to filter events meeting user-defined criteria.

Search subject filter

On the dropdown on the left-hand side, select what to look for:

• All — any kind of events
• People — face recognition events 
• Vehicles — license plate recognition events
• Additional events  — all events other than the two above, e.g. a bag left unattended, a traffic jam, an intrusion into a restricted area, etc.

Find events on a camera

A search like this answers the question “What events did the camera “XXXXXX” see”? The search returns a consolidated array of events generated by the video analytics module activated on XXXXXX camera.

The “XXXXXX” stands for the camera name/IP/ID or tag, or it can be selected on the camera list.

Only the cameras that the current user's User Groups have access to can be used.
Learn more about access to cameras.

By camera name/ID/IP

Type its name, id or IP-address as shown and click Apply; then click Search.

By camera tag

Select a camera tag on the list under the Tags; then click Apply and then click Search.

Select camera on the list

To query for events on a camera selected from the list of existing cameras, select it under the Cameras as described here, then click Apply and then click Search. 

Filter events by date and time

To find all events that occurred anywhere within IREX instance range within a predefined time period in the past, select the time limits under the Date and Time, then click Apply and then click Search.  

Find events in a building/on a plan

A search like this returns all events seen in “City Plaza”. “3rd floor Head Office”, etc., provided those objects were created in a dedicated user layer.

Select a building or plan under the Cameras as described here, then click Apply and then click Search.   

Only the venues that the current user's User Groups have access to can be used.
Learn more about access to venues.

Find events by location

A search like this returns all events that took place at a street or square, in a county. state, etc.

Learn more about location hierarchy in IREX.

Select a relevant location (e.g. “Broward County”) under the Locations, then click Apply and then click Search.    

Only a location assigned to one of the current user's user groups can be selected.
Learn more about access to locations.

Find events by priority

When managing video analytics, Admin assigns priorities to the configured events (e.g. like this or like that), one of:

To leave displayed only the events of a predefined priority (-es), checkmark them under the Priorities. Then click Apply and then click Search.     

Search criteria combination rules

• Search criteria under different filters are logically multiplied (“AND” operator).

For instance, if Date and Time = "Yesterday” while Location = "Broward County”, the events will be returned that occurred there AND then, and only those.

• Multiple options under the same filter are logically summarized (“OR” operator).

E.g. If both “Critical” and “High” are checkmarked under Priorities, the events will be returned that have any of these priorities.