English Română

Welcome to the Container Code Recognition (CCR) module! This page covers the Web Interface side of CCR — everything you manage from the browser under the Container Codes menu. For login, user administration, time tables, locations and cameras, backup and other shared settings, see the Introduction & Global Settings page.

Table of Contents

  1. Introduction
  2. Containers
  3. Containers Flow
  4. Live View
  5. Reports
  6. Actions
  7. Groups
  8. Settings

1. Introduction

Metrici Container Code Recognition (CCR) reads container identification codes (ISO 6346, e.g. CFSU 000560 [1]) from IP cameras and sends every detection to the Web Interface. From there you can browse events with their photos, generate reports and statistics, define automated actions per code, group codes for bulk management, and watch live camera feeds. All of this lives under the Container Codes menu in the left sidebar of the interface.

The detection itself is performed by the Metrici Control Panel engine on the server. This page documents only the Web Interface. For the engine settings (input stream, detection window, reporting, barriers, etc.) see the CCR Control Panel guide.

Before the CCR menu will show any data, two prerequisites must be met in Global Settings:

So a set up must be completed both in this Metrici Interface as well as in Metrici Control Panel, so please follow both guides for a full understanding.

The Container Codes menu groups the following sub-menus, each documented below: Containers, Containers flow, Live view, Reports, Actions (List and Groups), and Settings.

2. Containers

The Containers menu lists every detection recorded by the CCR engines. This is where you review what was seen, when, and where — see Fig.1 Containers.

Containers event list screenshot
Fig.1 Containers

The filter bar at the top lets you narrow down the list of events. The available filters are: Date & Time (from/to), Location, Camera, Direction, Group and Info (a free-text field that can store additional information for a code) — see Fig.1 Containers. Once you have selected the desired filter or filters, press OK to apply them. The result set can be exported in several formats (PDF, Excel or CSV) using the Export PDF, Export Excel and Export CSV buttons.

ColumnDescription
Code numberThe recognized container code, e.g. CFSU000560[1]. The number in brackets is the ISO 6346 check digit.
Date / TimeWhen the container was seen.
Location / CameraWhere it was seen and which camera detected it.
DirectionDirection of travel (coming or leaving), as configured in the engine's CCR tracking settings.
Time InsideDwell time, when applicable.
ActionWhether an action is set for that particular code.
InfoAny additional information attached to the code.

On the right side of the screen, a panel shows more detail for the selected code: the container photo captured at the moment of detection, and how many events that code has Today, This Week, and This Month. Two options are also available for the selected code — Add to actions list (see the Actions chapter) and Export PDF. Clicking the code or the photo enlarges the image from the moment of detection. At the bottom of the list, counters show the total number of codes and the number of unique codes in the current result.

3. Containers Flow

The Containers flow menu is a live alert view for the user watching the interface. It is similar to Live View, but instead of the full video stream it shows only the last detection, and it can play a beep sound/ alert each time a new detection is made — see Fig.2 Containers Flow.

Containers Flow screenshot
Fig.2 Containers Flow

At the top you choose the Location, the Camera, and the Alert Method. The alert method decides which detections appear in the flow:

Use the Audio Off / Play controls to toggle the alert sound. If you manage several locations and select only one, the flow shows detections from that location only. Clicking the detected code or the photo maximizes the picture from the moment of detection. The panel also indicates the previous detection for the same code.

4. Live View

Live view displays a live tile for each CCR camera you have defined — see Fig.3 Live View. Each tile shows the camera image together with the last code, the date and time, the Direction, and the Time Inside.

Live View screenshot
Fig.3 Live View

A tile can be made full screen by clicking the monitor icon in its top-right corner. Remove a tile with the × button; after viewing one camera full screen, return to all cameras with the restore (_) control.

Live View only works when it has been enabled for the camera in the engine's Live view settings. By default the Control Panel fills in a URL such as http://localhost/io/ccr/live_view.php. If the video is served from another address, replace localhost with the server's IP or hostname.

5. Reports

Metrici generates several reports automatically from the CCR events. Each report can be exported to an Excel (XLS) file, and the top bar lets you pick the date range, location, and camera to report on.

Containers each hour

Shows the number of recognized codes (detections) as well as unique codes for each hour of the day — see Fig.4 Containers each hour. The Type selector chooses between SUM and AVERAGE: the sum adds the detections of each hour across all filtered days, while the average calculates a per-hour average across those days.

Containers each hour report screenshot
Fig.4 Containers each hour

Containers each day

By default this report covers all the days of the current month; more days can be filtered from the top bar — see Fig.5 Containers each day.

Containers each day report screenshot
Fig.5 Containers each day

Containers each month

By default this report covers all the months of the current year; other months can be chosen for the report.

Containers each camera

Generates a report with all the detections seen by each camera in a location — see Fig.6 Containers each camera.

Containers each camera report screenshot
Fig.6 Containers each camera

Top Container Codes

Lists the codes that were detected most often, with columns for Total, Today, This Week, and This Month events — see Fig.7 Top Container Codes. From the top bar you can set the list length from 10 per page up to 100 per page. Each row has an ADD button to add that code directly to an action list.

Top Container Codes report screenshot
Fig.7 Top Container Codes

6. Actions

The Actions menu is where you define what the system should do when a container code is recognized — for example, opening a barrier, switching a traffic light, sending an e-mail, or displaying a pop-up. This menu has two submenus: List (individual codes) and Groups (groups of codes).

Action List

The action list displays every code entered in the database together with its settings — see Fig.8 Action List.

The columns are:

Action List screenshot
Fig.8 Action List

From the top bar you can use:

Adding a Code to the Action List

Click Add Code to open the form — see Fig.9 Add Code to Action List. Its fields are:

Add code to actions list form screenshot
Fig.9 Add Code to Action List
FieldDescription
CodeThe container code the rule applies to.
Info codeOptional free text stored with the code.
GroupIf the code belongs to a group you created, select it here. A code added to a group automatically inherits all of that group's settings.
Locations & CamerasChoose for which location(s) and camera(s) this code has an action rule. A code can have rights at one barrier only, not necessarily all of them.
Time TablesRestrict the actions to a schedule you created. The actions run only during that time table (for example, a barrier that opens only on a "Work Hours" table).
Expiration date / Never expireWhen the rule should stop applying, or tick Never expire to keep it permanent.
ActiveEnables the rule for this code.
Open BarrierOpen the barrier when this code is detected.
Trafic lightSwitch the traffic light when this code is detected.
Send Email / address / messageSend a notification e-mail; fill in the recipient address and the message.
Show Pop-up / messageShow a pop-up in the interface; fill in the message text.
Action URLThe address of the hardware device to command (barrier, traffic light, etc.) — usually the address of the LAN controller.
Cross ChecksNumber of extra conditions that must be met before the action runs. 0 (default) means a single condition. 1 means two conditions must be satisfied simultaneously — for example a container code and a license plate, linked in the database, before access is granted.
Wildcards. Throughout the interface — searches, action lists, and other data — the _ sign replaces a single letter or number, and the % sign replaces any number of letters or numbers. For example, a rule for CFSU% applies to any code starting with CFSU followed by at least one more character and as many possible.

7. Groups

Groups make managing many codes easier: the settings defined for a group are applied to every code assigned to it, so you don't have to configure each code by hand — see Fig.10 Groups. This menu lists all the groups you have created; clicking a group name shows the codes assigned to it along with the actions, locations, and cameras where those actions are active.

Groups list screenshot
Fig.10 Groups

To create a group, click Add Group and fill in the form — see Fig.11 Add Group. The fields are the same as for a single code, minus the code number: a Group Name, then Locations & Cameras, Time Tables, Expiration date / Never expire, Active, Open Barrier, Trafic light, Send Email (with address and message), Show Pop-up (with message), Action URL, and Cross Checks. Set these carefully, because they are copied to every code placed in the group.

Add group form screenshot
Fig.11 Add Group

Once a group exists, you can add codes to it one by one with Add Code — enter the code (and Info if you wish) and it inherits the group's settings. You can also import a list of codes in CSV format with Import Codes.

Empty group before import. When importing from a third-party system or a file that is always kept up to date, tick Empty group before import so codes are not duplicated on each import. If an import contains only new codes (not the old ones), leave this option unchecked. Group settings can also be exported to CSV at any time by clicking the group name and choosing export.

8. Settings

The Settings menu shows housekeeping information for the CCR module — see Fig.12 Settings:

CCR Settings screenshot
Fig.12 Settings
NameMeaning
Delete events after [days]How long events are kept before being removed automatically (default 90 days).
Events counterHow many events are currently stored in the database.
Disk spaceTotal, used, and free disk space on the server.

To change the retention period, click Edit Settings (upper right), set a new value for Delete events after [days], and click Save — see Fig.13 Edit Settings.

Edit CCR Settings screenshot
Fig.13 Edit Settings
The CCR detection engine can keep working without an internet connection, storing events in a local buffer, and will save them to the server and Web Interface once a connection is available.