OSP-103.29 Communications Center - User Manual

7/31/2019 OSP-103.29 Communications Center - User Manual

1/39

ALL RIGHTS RESERVED. USE, DU PLICATION, OR DISCLOSURE IS PROH IBITED

Project: OSHP

Sub Project: Operation Center

Component:

User Manual Operation Center

Code: HK4SOHP27600 Rev.: 1.0 Date: 23-May-2004

Organisation Authorisation Signature Date

Checked TRI G. Garibotto 23-May-04

Checked PSS C. Coelho 23-May-04

Approved GSP N. Gennari 23-May-04


2/39

GSP Division OSHP User Manual Operation Center

Code : HK4SOHP27600 Rev. : 1.0 Date : 23-May-2004 Pag. 2/39 ALL RIGHTS RESERVED, REPRODUCTION AND DISTRIBUTION PROHIBITED

Word Processor: WinWord 2000

REVISIONS

Rev. Date Author/s Signature Description

Rev. 1.0 14-06-2004 A. Maccagno First Emission


3/39



CONTENTS

1 - OVERVIEW ....................................................................................................................6

1.1 Document scope..................................................................................................................................6 1.2 Definitions and Abbreviations...............................................................................................................6

2 GENERAL DESCRIPTION ............................................................................................7

2.1 Overall configuration......................... ......................... ......................... ......................... ........................ 7 2.2 Human-Computer interface (HCI).........................................................................................................8

3 CONNECTION TO THE SYSTEM .................................................................................8

3.1 Functional Description..........................................................................................................................8 3.2 Operational status................................................................................................................................8

3.3 Detailed Description.............................................................................................................................9 3.4 - Examples ...................... ......................... ......................... ......................... ......................... ................... 9 3.5 Possible Errors ......................... ......................... ......................... ........................ ......................... ...... 10

4 - ALARM VIEW...............................................................................................................10

4.1 Functional Description........................................................................................................................10 4.2 - Warnings and Precautions...................... ........................ ......................... ......................... .................. 11 4.3 - Detailed Description.............................. ......................... ......................... ......................... ................... 11 4.4 - Examples ...................... ......................... ......................... ......................... ......................... ................. 13 4.5 - Possible Errors ....................... ........................ ......................... ......................... ......................... ......... 13

5 ALARM QUERY ..........................................................................................................14

5.1 - Query ........................ ......................... ......................... ......................... ......................... ..................... 14 5.1.1 - Functional Description......................................... ......................... ......................... ................... 14 5.1.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 14 5.1.3 - Detailed Description............ ......................... ......................... ......................... ......................... . 14 5.1.4 - Examples.......................... ......................... ......................... ........................ ......................... .... 16 5.1.5 - Possible Errors ....................... ......................... ......................... ......................... ...................... 17

5.2 Alarm Image Search ......................... ......................... ......................... ......................... ...................... 18 5.2.1 - Functional Description......................................... ......................... ......................... ................... 18 5.2.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 18 5.2.3 - Detailed Description............ ......................... ......................... ......................... ......................... . 18 5.2.4 - Examples.......................... ......................... ......................... ........................ ......................... .... 19 5.2.5 - Possible Errors ....................... ......................... ......................... ......................... ...................... 19

5.3 Correct Alarm........................................ ........................ ......................... ......................... ................... 19 5.3.1 - Functional Description......................................... ......................... ......................... ................... 19 5.3.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 19 5.3.3 - Detailed Description............ ......................... ......................... ......................... ......................... . 19 5.3.4 - Examples.......................... ......................... ......................... ........................ ......................... .... 20 5.3.5 - Possible Errors ....................... ......................... ......................... ......................... ...................... 21

6 - STATISTICAL ANALYSIS ...........................................................................................21

6.1 - Overview ...................... ......................... ......................... ......................... ......................... .................. 21 6.2 - Functional Description ..................... ......................... ......................... ......................... ........................ 21 6.3 - Warnings and Precautions...................... ........................ ......................... ......................... .................. 21 6.4 - Detailed Description.............................. ......................... ......................... ......................... ................... 21 6.5 - Examples ...................... ......................... ......................... ......................... ......................... ................. 23 6.6 - Possible Errors ....................... ........................ ......................... ......................... ......................... ......... 23

7 - HOT LIST MANAGEMENT ..........................................................................................23


4/39



7.1 - External Hot List Automatic Update...................... ......................... ......................... ......................... .... 23 7.1.1 - Functional Description ..................... ......................... ......................... ......................... ............. 23 7.1.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 23

7.2 - Plate Search in Temporary Hot List and External Hot List ........................ ......................... .................. 24 7.2.1 - Functional Description ..................... ......................... ......................... ......................... ............. 24 7.2.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 24 7.2.3 - Detailed Description..................... ......................... ......................... ......................... ................. 24 7.2.4 - Examples................................... ......................... ........................ ......................... .................... 25 7.2.5 - Possible Errors ........................ ......................... ......................... ......................... ..................... 26

7.3 Plate Entry in Temporary Hot List.................. ......................... ......................... ......................... .......... 26 7.3.1 - Functional Description ..................... ......................... ......................... ......................... ............. 26 7.3.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 26 7.3.3 - Detailed Description..................... ......................... ......................... ......................... ................. 26 7.3.4 - Examples................................... ......................... ........................ ......................... .................... 28 7.3.5 - Possible Errors ........................ ......................... ......................... ......................... ..................... 28

7.4 Plate Removal from Temporary Hot List ..................... ......................... ......................... ...................... 29 7.4.1 - Functional Description ..................... ......................... ......................... ......................... ............. 29 7.4.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 29

7.4.3 - Detailed Description..................... ......................... ......................... ......................... ................. 29

7.4.4 - Examples................................... ......................... ........................ ......................... .................... 30 7.4.5 - Possible Errors ........................ ......................... ......................... ......................... ..................... 30

8 - USER MANAGEMENT ................................................................................................ 30

8.1 Overview ....................... ......................... ......................... ......................... ......................... ................ 30 8.2 Users List ...................... ......................... ......................... ......................... ......................... ................ 31

8.2.1 - Functional Description ..................... ......................... ......................... ......................... ............. 31 8.2.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 31 8.2.3 - Detailed Description..................... ......................... ......................... ......................... ................. 31 8.2.4 - Examples................................... ......................... ........................ ......................... .................... 32 8.2.5 - Possible Errors ........................ ......................... ......................... ......................... ..................... 32

8.3 New User Insertion ......................... ......................... ......................... ......................... ........................ 32 8.3.1 - Functional Description ..................... ......................... ......................... ......................... ............. 32 8.3.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 33 8.3.3 - Detailed Description..................... ......................... ......................... ......................... ................. 33 8.3.4 - Examples................................... ......................... ........................ ......................... .................... 34 8.3.5 - Possible Errors ........................ ......................... ......................... ......................... ..................... 34

8.4 User Removal........ ......................... ......................... ........................ ......................... ......................... 34 8.4.1 - Functional Description ..................... ......................... ......................... ......................... ............. 34 8.4.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 34 8.4.3 - Detailed Description..................... ......................... ......................... ......................... ................. 34 8.4.4 - Examples................................... ......................... ........................ ......................... .................... 35 8.4.5 - Possible Errors ........................ ......................... ......................... ......................... ..................... 35

8.5 Change User Password ..................... ......................... ......................... ......................... ..................... 35 8.5.1 - Functional Description ..................... ......................... ......................... ......................... ............. 35 8.5.2 - Warnings and Precautions ...................... ......................... ......................... ......................... ...... 35 8.5.3 - Detailed Description..................... ......................... ......................... ......................... ................. 36 8.5.4 - Examples................................... ......................... ........................ ......................... .................... 37 8.5.5 - Possible Errors ........................ ......................... ......................... ......................... ..................... 37

9 OPERATION LOGGING ............................................................................................. 37

9.1 - Functional Description ...................... ......................... ......................... ......................... ....................... 37 9.2 - Warnings and Precautions...... ........................ ......................... ......................... ......................... ......... 37 9.3 - Detailed Description................................ ......................... ......................... ......................... ................. 37 9.4 - Examples ....................... ......................... ......................... ......................... ......................... ................ 38 9.5 - Possible Errors ....................... ......................... ......................... ......................... ......................... ........ 39

10 - ON LINE HELP.......................................................................................................... 39

10.1 - Functional Description ........................ ......................... ......................... ......................... ................... 39


5/39



10.2 - Warnings and Precautions ......................... ......................... ......................... ......................... ............ 39

ILLUSTRATIONS

Fig. 2.1 Overall configuration of Pilot Project System ....................... ......................... ......................... ........7 Fig. 3.1 HCI Connection Page....................................................................................................................9 Fig. 3.2 Site Home Page..........................................................................................................................10 Fig. 4.1 Alarm Management Area.............................................................................................................11 Fig. 4.2 Alarm Details Page for Acceptance ...................... ......................... ......................... ..................... 12 Fig. 4.3 Alarm Acceptance Message..... ......................... ......................... ......................... ........................ 12 Fig. 4.4 Alarm Discard Message ......................... ......................... ......................... ......................... ..........13 Fig. 4.5 Alarm already accepted...............................................................................................................13 Fig. 4.6 - Image Enhancement Commands ........................ ......................... ......................... ....................... 14 Fig. 5.1 Main Menu..................................................................................................................................14 Fig. 5.2 Alarm Query Page.......................................................................................................................15 Fig. 5.3 Gates and Cars Selection Page...................................................................................................16 Fig. 5.4 Alarm Query Results Page ........................ ......................... ........................ ......................... ........16 Fig. 5.5 Alarm Image Page ......................... ......................... ......................... ......................... .................. 18 Fig. 5.6 Plate Correction Page ...................... ......................... ......................... ......................... ................ 20 Fig. 5.7 Transit Correction Operation Result Page....................................................................................20 Fig. 5.8 Transit Discard Operation Result Page........................................................................................21 Fig. 6.1 Gate and Car Statistics ...................... ......................... ......................... ......................... .............. 22 Fig. 6.2 Complete Gate Chart ....................... ......................... ......................... ......................... ................ 23 Fig. 7.1 Last External Hot List Update......................................................................................................23 Fig. 7.2 Hot List Plate Search Menu Page................................................................................................24 Fig. 7.3 Hot Plate List Page ......................... ......................... ......................... ......................... ................. 25 Fig. 7.4 Hot List Drop-down Menu..........................................................................................................26 Fig. 7.5 Plate Insertion in Temporary Hot List Page..................................................................................27 Fig. 7.6 Plate Insertion in Temporary Hot List Page with Confirmation Request ...................... .................. 28 Fig. 7.7 Plate Insertion in Temporary Hot List Page with Confirmation of Success......................... ...........28 Fig. 7.8 Plate Removal from Temporary Hot List Page ......................... ......................... ......................... ..29 Fig. 7.9 Operation Confirmation Dialog Box..............................................................................................30 Fig. 7.10 Plate Removal Command Failure Page ....................... ......................... ......................... ............ 30 Fig. 8.1 Users Drop-down Menu ........................ ......................... ......................... ......................... .........32 Fig. 8.2 - USERS MANAGEMENT Page with Granted Users List ...................... ......................... ................. 32 Fig. 8.3 - USERS MANAGEMENT - Insert New User Page ......................... ......................... ....................... 33 Fig. 8.4 Operation Confirmation Window..................................................................................................34 Fig. 8.5 - USER MANAGEMENT - User Removal Page ....................... ......................... ......................... .....35 Fig. 8.6 Operation Confirmation Dialog Box..............................................................................................35 Fig. 8.7 - USER MANAGEMENT - Change Password Page (Maintenance-Upgrade or Sys Admin users) ...36 Fig. 8.8 - USER MANAGEMENT - Change Password Page (User or Supervisor Profiles) ........................ ...36 Fig. 8.9 Operations Confirmation Dialog Box............................................................................................37 Fig. 9.1 Example of OWA Logging File Content........................................................................................38 Fig. 10.1 Help On Line Page....................................................................................................................39

TABLES

Tab. 1.1 List of Abbreviations and Meanings..............................................................................................6 Tab. 8.1 Permitted Operations according to User Type ........................ ......................... ......................... ..31


6/39



1 - OVERVIEW

1.1 Document scopeThis handbook is for both general users and system administrators.

It describes:

- functions available;

- operations to perform system functions;

- messages to guide the user when interacting with the system.

1.2 Definitions and AbbreviationsTab. 1.1 lists the abbreviations used in the text and their meanings:

Tab. 1.1 List of Abbreviations and Meanings

ABBR. MEANINGIIS Internet Information S ervices

LAN Local Area NetworkPC P ersonal Computer

ANPR A utomantic Number P late Reader DDS Data D ownload S tationEHL E xternal Hot ListTHL Temporary Hot List

HLPN H ot License P late Number ODM Operations Center Data Manager OWA O perations Center Web Application

PS_DB P eripheral S tation Data BasePOST P olice Office S tation

HCI Human Computer Interface


7/39



2 GENERAL DESCRIPTION

2.1 Overall configuration

The Overall configuration of the pilot project system is illustrated in Fig. 2.1. The system comprises theheadquarters (POST), two gates and two patrol cars. Each gate has three ANPR readers to monitor 3 lanes.Patrol cars are equipped with a mobile version of the ANPR plate reader.

Fig. 2.1 Overall configuration of Pilot Project System

The following components are installed at Headquarters 10 (Berea):

- a personal computer ( Client PC ) that allows the users to access the HCI of the system;

- a personal computer ( Post Station ) loaded with the IIS, OWA and ODM applications;

- a personal computer ( Car Peripheral Station ) loaded with the DDS application;

- a LAN Wireless Access Point for connection with patrol cars;

- an 8 port 10/100Mb/s HUB/SWITCH for PC network interconnection;

The following components are installed in each Gate Peripheral Station:

- a personal computer ( Gate Peripheral Station ) loaded with the DDS application;

- three ANPR readers with LAN interface;

- an 8 port 10/100Mb/s HUB/SWITCH for ANPR reader network interconnection;


8/39



The following components are installed in each patrol car:

- two ANPR readers with wireless network interface;

The system stores alarm data only and no sensitive information on detected transits in compliance with Pri-vacy Law restrictions.

2.2 Human-Computer interface (HCI)The Human-Computer Interface (HCI) is a web-based client/server application: the Post Station runs a webserver (IIS) for remote connections and a graphical interface through which the operator can access the sys-tem.The minimum hardware configuration for the client PC to be able to use the HCI is as follows:

- PIII 1 GHz processor;- 128Mb RAM;- Video Card Definition 1024x768;- 100Mb/s LAN Card;- Internet Explorer v. 6.0;

- Windows 2000 or XP Operating System;The HCI application is hosted on the web server. Client PCs can use Internet Explorer both to access theapplication and monitor, control and manage the system.

These operations are described in detail in the following sections.

Access to system functions is restricted. Different user profiles specify permitted operations for classes of users.

User classes are:

- Maintenance-Upgrade ;

- System Administration ;

- Supervisor ;

- User .

The following sections list all HCI operations available to System Administration user profiles. Details onthe characteristics of other profiles are given in Sec. 8.

3 CONNECTION TO THE SYSTEM

3.1 Functional Description At the start of a work session, users must enter their name and password in the " User Authentication " form(see Fig. 3.1): if both match the information contained in the system database the HCI system can be ac-cessed.

3.2 Operational statusFor access to be granted, the application has to be running. This means that the Post Station IIS servicemust also be running. The system default settings activate these services.

The system distinguishes between upper and lower case letters. Spaces are considered as characters.


9/39



Pay special attention to using function keys like " Caps Lock ".

3.3 Detailed DescriptionUsers must:

- Enter their user ID in the " LOGIN " box;

- Enter the access code associated with the user ID in the " PASSWORD " box. All characters entered aredisplayed as for reasons of confidentiality;

- Press " Enter " on the keyboard or click the " ENTER " button on the screen to confirm the ID and Pass-word.

3.4 - Examples

In the example below:

Fig. 3.1 HCI Connection Page

The user ID is MyLogin and the associated password comprises eight characters displayed as a sequenceof eight .

If the user ID and password match the values stored in the system, a home page like the one shown in Fig.3.2. is displayed:


10/39


Code : HK4SOHP27600 Rev. : 1.0 Date : 23-May-2004 Pag. 10 /39 ALL RIGHTS RESERVED, REPRODUCTION AND DISTRIBUTION PROHIBITED

AlarmManagement

Footer

Menu

MainFrame

Fig. 3.2 Site Home Page

As illustrated in Fig. 3.2, the home page contains four frames:

- Alarm Management , on the left side of the home page;

- Menu , the blue bar at the top of the home page;

- Main Frame , in the centre of the home page.

- Footer , at the bottom of the home page.

3.5 Possible ErrorsIf the user ID and password do not match the values stored in the system, the following message is dis-played to signal an access error:

Wrong User or Wrong Password or User not allowed

At this point the operation may be repeated by re-entering the information described in par. 3.3.

4- ALARM VIEW

4.1 Functional DescriptionThis function displays alarms as soon as a suspect license plate is intercepted by a gate.

As soon as the plate recognition system detects a vehicle on the hot list of suspect plates, an alarm bell icon


11/39



appears on the operators monitor along with an acoustic alarm to signal the event.

The operator must then take charge of the alarm using the alarm view function.

4.2 - Warnings and PrecautionsNone.

4.3 - Detailed Description Almost all site pages, except those relating to command results, contain an alarm indication field (see Fig.3.2 and Fig. 4.1).

Fig. 4.1 Alarm Management Area

The " Pending Alarms " section shows the alarm bell icons associated with alarms which have not yet beentaken in charge of by the operator. The " Latest Alarms " section shows the icons (one for each alarm) asso-ciated with the last five alarms taken in charge.For sake of simplicity, a maximum of 5 pending alarm icons are displayed with the total indicated as a num-ber. The presence of one or more pending alarms is also signalled by an acoustic alarm.2/2 indicates that 2 latest alarm icons are displayed out of a total of 2 pending alarms.The total number of pending alarms is automatically decreased each time an alarm is taken in charge andaccepted (or discarded).By clicking on the icons the operator can obtain detailed information on the corresponding alarm and decidewhether to accept it (resolving any possible ambiguities present, relating to state for example) or discard it.

Fig. 4.2 shows the alarm view details page:


12/39



Fig. 4.2 Alarm Details Page for Acceptance

The page includes:

- "Date " of the interception;

- "Plate (State) " of the intercepted vehicle;

- "Gate " ID of the gate that detected the transit;

Plus:

- an image of the transit;

- the form for accepting (selecting the correct plate-state pair from the Hot List) or discarding the alarm.

By pressing ACCEPT and confirming the operation, the alarm is accepted and entered in the database withinformation on the date and time it was taken in charge by the operator. The system displays the messageshown in Fig. 4.3.

Fig. 4.3 Alarm Acceptance Message

It is also possible to discard an alarm by pressing DISCARD . After confirming the operation, the system


13/39



displays the message shown in Fig. 4.4

Fig. 4.4 Alarm Discard Message

4.4 - ExamplesSee previous paragraph.

4.5 - Possible ErrorsIf several clients are connected to the OWA there may be an icon in the pending alarms list that refers to analarm which has already been taken in charge by a user logged on to another client. However, as the list isupdated every 10 seconds this is highly unlikely.In this case the page would appear as in Fig. 4.5, which has no accept/discard form and displays the opera-tor who acknowledged the alarm with the date and time.

Fig. 4.5 Alarm already accepted

The screen shown in Fig. 4.5 is identical to the screen that appears after clicking on one of the icons repre-senting the latest alarms taken in charge ( Latest Alarms ).


14/39



Alarm view images may sometimes be quite dark because the infrared filter is mounted on the plate reader.If this is the case, the commands at the top of the frame can be used to increase brightness, contrast andzoom.

ZOOM

SATURATI ON

BRI GHTNESS EDGE ENHANCE

CONTRAST

RESET

Fig. 4.6 - Image Enhancement Commands

5 ALARM QUERY

5.1 - Query

5.1.1 - Functional DescriptionThe query function allows users to select a set of alarms stored in the database on the local or a remotePOST and display them in chronological order.

The set is defined according to user provided time and logic criteria.

The storage period for alarms in the database is a system setting (31 days by default). After this period thesystem automatically deletes the alarm information and relative images.

5.1.2 - Warnings and PrecautionsWhen making consecutive queries, check the data entered in the form because the default settings are auto-matically restored.

5.1.3 - Detailed DescriptionTo perform an Alarm Query , left click the mouse on the Query option in the Main Menu (see Fig. 5.1).

Fig. 5.1 Main Menu

The following page is displayed (Fig. 5.2).


15/39



Fig. 5.2 Alarm Query Page

Set the desired query criteria.

These include:

- "Month ", "Day ", "Year ", "Hour " and " Minute " of the start of the query interval;

- " Month ", " Day ", " Year ", " Hour " and " Minute " of the end of the query interval;

- "Plate ": the complete or partial license plate alarm to query. To specify a partial license plate use the wildcharacter %, which performs a similar function to the character in MS-DOS commands. For example,entering the characters AB365TS in the plate field searches for alarms of the specific plate AB365TS .Entering the characters AB% searches for alarms of all plates starting with AB. Entering the charac-ters %5TS searches for alarms of all plates ending with 5TS . Entering %36% searches for alarms of all plates containing the characters 36 ;NOTE: to prevent ambiguity between the letter O and the number 0, the system only uses thenumber 0. Any O letters entered in the Plate field are automatically replaced with the num-

ber 0.

- "Gates ": Restricts the query to alarms signalled by gates. The search can be restricted to a single gate byselecting the corresponding ID from the drop-down list;

- "Cars ": Restricts the query to alarms signalled by patrol cars. The search can be further restricted to asingle patrol car by selecting its ID from the drop-down list;


16/39



Fig. 5.3 Gates and Cars Selection Page

- "POST ": name of Post where transit is stored.

The fields in the Alarm Query form are automatically set to the following default values:

- the current date and time with a time window of one hour between query Start and End Date / Time;

- "Gates " mode selected;

- "Plate " = "ALL" (the same as not specifying anything in the plate field and querying all detected platetransits);

- "Gates " = "ALL" (see plate field: query for all gates);

- POST the name of the local Post.

5.1.4 - ExamplesFig. 5.4 gives an example of the Alarm Query results page:

Save Query Dat a

Backup Data

Print

Fig. 5.4 Alarm Query Results Page


17/39



Transits found are given in table form on one or more pages containing the following information:

- "Date ";

- "Gate / Car ";

- "Plate (State) ";

- "Description ";

- "Image ": Link to the transit image. Left click on the mouse to view all transit details, including the image;

The query criteria are given above the table, specifying:

- "Start Date Hour: ";

- "End Date Hour: ";

- "Plate: ";- "Gate / Car: ".

The following supplementary operations are also possible:

- Result order: transits can be sorted in ascending or descending order by left clicking on the " Date ", "Gate/ Car " and " Plate (State) " links;

- Browsing the table: the query results pages can be browsed by left clicking the " Prev " and " Next " links atthe bottom of the table;

- Save Table: left clicking on the " Save Query Data " icon saves the query result to file as text. The file can

be downloaded to a client PC;- Query Backup: left clicking on the " Backup Data " icon creates a zipped file containing an index, in HTML

format, and all the images associated with the alarms. The file can be downloaded to a Client PC;

- Print table: left clicking on the " Print " icon prints the query results;

- Back to Search Window: left clicking on the " Back to Search window " icon returns you to the corre-sponding page and the search criteria are restored to the default values.

5.1.5 - Possible ErrorsNo errors are possible other than entering search criteria which do not correspond to any transit stored in the

database at the selected POST.

If no transits meet the search criteria, the HCI informs the operator with the message:

No Transit Found

Left clicking on " BACK " at the end of the previous message displays the Search Window .

The storage period is a system parameter, set by default to 31 days. Queries on previous periods will pro-duce no results since the information is automatically deleted at the set time.


18/39



5.2 Alarm Image Search

5.2.1 - Functional DescriptionThe images associated with alarms found can also be displayed. These images allow operators to identifythe license plate and usually the type of vehicle as well, depending on image quality.

5.2.2 - Warnings and PrecautionsThe plate recognition system processes images captured by a gate or patrol car during missions. Imagequality is directly dependent on environmental conditions during capture.

5.2.3 - Detailed DescriptionWith reference to Fig. 5.4, the image of the desired transit can be viewed by left clicking on the " Image " linkin the far right column of the table, which displays the page shown in Fig. 5.5.

Fig. 5.5 Alarm Image Page

Transit details are given at the top:

- "Date ": date and time of alarm;

- "Plate (State) ": license plate and nationality of vehicle;

- "Gate / Car ": gate or patrol car involved;


19/39



- "Take in Charge Date' ": date the alarm was taken in charge;

- "Description' ": description of the plate.

Further down the page:

- Alarm Image, if available;

- the " Plate Correction " link is only displayed if an image of the transit is available, allowing the plate andthe nationality of the vehicle identified to be corrected.

The control buttons above the image can be used to adjust zoom and contrast level.

5.2.4 - ExamplesFig. 5.5 gives an example of transit image display.

5.2.5 - Possible ErrorsIf, for any reason, (no connection between POST and DDS, images unavailable on DDS because not yetdownloaded from patrol car, etc.) image transfer is not possible, the following message is displayed in placeof the image:

Image not Available

While the detailed information described above continues to be displayed, there is no " Plate Correction " linkas clearly the operator is unable to make any visual comparison between the plate recognition result and theplate image.

5.3 Correct Alarm

5.3.1 - Functional Description

The license plate and nationality of the transit displayed can be corrected by choosing between the alterna-tives (plate-state pairs) presented by the system. All alarms from gates must be accepted by the operator before entry into the database. Alarms detected by cars during patrols are accepted by the officer onboard.

5.3.2- Warnings and PrecautionsThe plate recognition system processes images captured by a gate or patrol car during missions. Imagequality is directly dependent on environmental conditions during capture.

Adjusting the zoom and contrast levels may improve plate legibility.

5.3.3 - Detailed Description

With reference to Fig. 5.5, left clicking on " Plate Correction " displays the page shown in Fig. 5.6:


20/39



Fig. 5.6 Plate Correction Page

Any Hot List alternatives to the detected plate are displayed in the drop-down list. The correct alternative canbe selected (State recognition ambiguity) or the alarm can be discarded.

5.3.4 - ExamplesFig. 5.7 shows an example of the result of a plate correction carried out as described above:

Fig. 5.7 Transit Correction Operation Result Page

Fig. 5.8 shows an example of the result of a plate discard operation performed by clicking the DISCARD


21/39



button.

Fig. 5.8 Transit Discard Operation Result Page

The link displayed closes the plate correction/discard page.

5.3.5 - Possible ErrorsNone.

6- STATISTICAL ANALYSIS

6.1 - OverviewThe system performs statistical analysis of the number of transits and alarms detected by each gate or car.

6.2- Functional Description All data is stored automatically with date and time information. Statistics can be displayed in table or bar chart formats.


6.4 - Detailed DescriptionSelect Stats from the menu to access the statistical analysis function. Fig. 6.1 shows the main page, whichgives a summary report of transits detected by cars and gates.


22/39



Fig. 6.1 Gate and Car Statistics

The statistics are presented in tabular, numerical form, sorted on the acquisition date.The meanings of the fields are as follows:

- "Date " acquisition date;

- "Transits " number of transits detected;

- "Alarms " number of alarms detected;

- "Gate/Car " ID of gate or car the data refers to.

Clicking on the number fields displays a bar chart of hourly data:

- "Date " chart of transits and alarms during the day;

- "Transits " chart of transits only during the day;

- "Alarms " chart of alarms only during the day;

Fig. 6.2 gives an example of a complete graph.


23/39



Fig. 6.2 Complete Gate Chart

6.5- ExamplesSee previous paragraph.

6.6- Possible ErrorsData from patrol cars is only available after the transits and alarms have been downloaded at the end of amission. The fact that some days are empty and the bar chart distribution is not uniform over the 24 hour pe-riod is quite normal.

7 - HOT LIST MANAGEMENTThe Hot List managed by the system is divided into two categories: External and Temporary.

Any Hot License Plate entered by the operators through the HCI, are inserted in the Temporary Hot List. Listof Hot License Plate imported using suitably formatted files from outside sources are associated with the Ex-ternal Hot List.

7.1- External Hot List Automatic Update

7.1.1 - Functional DescriptionThe system automatically updates the External Hot List. For this to happen, a suitably formatted file must beplaced in a specific directory on the Post Station. The ODM application reads the file and sends the updatesto the competent DDS. These updates are downloaded to the patrol cars at the beginning of patrol mission.Operators can find out when the last External Hot List update was performed by reading the information inthe HCI footer, as shown in Fig. 7.1.

Fig. 7.1 Last External Hot List Update

Hot List updates are presumed to be periodic (every 24 hours).

7.1.2- Warnings and Precautions

The update operation is fully automatic and requires no operator intervention.


24/39



7.2- Plate Search in Temporary Hot List and External Hot List


This function enables users to select a set of plates in the Temporary Hot List or the External Hot List andview it in chronological order sorted on the Entry Date field.

The set is defined according to user provided time and logic criteria.

Access to External Hot List data is restricted to System Administration users.

7.2.2 - Warnings and PrecautionsWhen making consecutive queries, check the data entered in the form as the default settings are automati-cally restored.


Clicking on " Query " (see Fig. 7.4) under " Hot List " in the Main Menu opens the page shown in Fig. 7.2:

Fig. 7.2 Hot List Plate Search Menu Page

Enter the required search criteria.

Available parameters are:

- "Month ", "Day ", "Year ", "Hour " and " Minute " of the start of the search interval;

- "Month ", "Day ", "Year ", "Hour " and " Minute " of the end of the search interval;

The time interval refers to the plate Entry Date in the Hot List.


25/39



- "Plate ": complete or partial plate to search in the Hot List. To specify a partial license plate use the wildcharacter %, which performs a similar function to the character in MS-DOS commands. For example,entering the characters AB365TS in the plate field searches for records of the specific plate AB365TS .Entering the characters AB% searches for records of all plates starting with AB. Entering the charac-ters %5TS searches for records of all plates ending with 5TS . Entering %36% searches for recordsof all plates containing the characters 36;NOTE: to prevent ambiguity between the letter O and the number 0, the system only uses thenumber 0. Any O letters entered in the Plate field are automatically replaced with the num-ber 0.

- "Hot List ": to search the plates entered in the temporary or external list.

7.2.4 - ExamplesLeft clicking on the " SEARCH " button displays the page shown in Fig. 7.3:

Fig. 7.3 Hot Plate List Page

Search results are presented in table form on one or more pages containing the following information:

- "Plate ";

- "State ";

- "Entry Date ";

- "Deleting Date ";

- "Hot List " indicates whether the plate is on the temporary or external list;

- "Description ".


26/39



- "REMOVE ": direct link to the page used to remove the plate from the temporary list.

For details on these data types, see Par. 7.3.

To browse through the pages, simply click on the " Prev " or " Next " links under the table.

7.2.5 - Possible ErrorsThe only possible error is entering search criteria that do not correspond to any plate in the Hot List.

If no plates meet the set search criteria, the HCI informs the operator with the message:

No Query Result

Operators can return to the previous page by left clicking on the link New Search at the end of the previousmessage.

7.3 Plate Entry in Temporary Hot List

7.3.1 - Functional Description A plate can be entered in the Temporary Hot List to receive alerts when the vehicle license plate is recog-nised by the ANPR car detector system installed in gates or onboard patrol cars. While the gate readers areupdated immediately (data network transfer time is negligible), patrol car readers are only updated at the be-ginning of patrol mission.

7.3.2 - Warnings and Precautions A plate can be entered in the Temporary Hot List by sending an entry request to the local POST.

7.3.3 - Detailed DescriptionLeft clicking on " Hot List " in the Main Menu presents the options shown below in Fig. 7.4:

Fig. 7.4 Hot List Drop-down Menu

Clicking on " Insert " displays the Plate Insertion in Temporary Hot List page shown in Fig. 7.5:


27/39



Fig. 7.5 Plate Insertion in Temporary Hot List PageEntry fields:

- "Entry Date ": date of entry in Temporary Hot List, automatically set to the current date. Cannot be editedby the operator;

- "Deleting Date ": date of removal from Temporary Hot List, automatically set to the configuration defaultperiod;

- "Plate ": vehicle license plate;

- "State ": vehicle nationality;

- "Description ": text describing the entry (eg. reason why).

NOTE: to prevent ambiguity between the letter O and the number 0, the system only uses thenumber 0. Any O letters entered in the Plate field are automatically replaced with the num-ber 0.

Clicking the " INSERT " button requests command execution. A confirmation dialog box is displayed to allowthe operator to go back and check the data entered before finally issuing the command (see Fig. 7.6).


28/39



Fig. 7.6 Plate Insertion in Temporary Hot List Page with Confirmation Request

7.3.4 - ExamplesClicking on " INSERT " and then confirming displays the page shown in Fig. 7.7:

Fig. 7.7 Plate Insertion in Temporary Hot List Page with Confirmation of Success

This message reports the following information:

- "Plate Insertion ": the alphanumerical characters of the plate inserted;

- "from POST ": the HCI POST from which the insertion was performed;- a Message informing the operator of the outcome of the command.

7.3.5 - Possible ErrorsIf the plate is already present in the Temporary Hot List or External Hot List, the insertion command fails andthe operator is informed of the error by the message:

AA971BB - OH: This Plate isalready in the Hot List

Operators can return to the previous page by pressing " Back ".


29/39



7.4 Plate Removal from Temporary Hot List

7.4.1 - Functional Description A plate can be removed from the Temporary Hot List to stop alarms being signalled if they are recognised bythe ANPR system installed in gates and onboard patrol cars. While the gate readers are updated immedi-

ately (data network transfer time is negligible), patrol car readers are only updated at the beginning of patrolmission.

7.4.2 - Warnings and PrecautionsIt is only possible to remove plates from the Temporary Hot List if they are not on the External Hot List.

7.4.3 - Detailed DescriptionClicking on " Remove " under " Hot List " in the Main Menu (see Fig. 7.4) displays the page shown in Fig. 7.8:

Fig. 7.8 Plate Removal from Temporary Hot List Page

Entry fields:

- "Plate ": license plate of the vehicle to remove from the list;

- "State ": nationality of the vehicle to remove from the list.

Clicking on the " REMOVE " button requests command execution. A confirmation dialog box is displayed to al-low the operator to go back and check the data entered before finally issuing the command (see Fig. 7.9).


30/39



Fig. 7.9 Operation Confirmation Dialog Box

7.4.4 - ExamplesClicking on " REMOVE " and confirming displays a page like the one in Fig. 7.10:

Fig. 7.10 Plate Removal Command Failure Page

In this case, for example, the plate couldnt be found in the Temporary Hot List and an error message hasbeen displayed to inform the operator that the command has failed.

7.4.5 - Possible ErrorsIf the specified plate is not in the Temporary Hot List or it is present in the External Hot List, the operationfails and the HCI informs the operator of the error with one of the following messages:

This Plate cannot be removed (External Hot List)

or:

Can't find this Plate in List

Operators can return to the previous page by pressing " Back ".

8- USER MANAGEMENT

8.1 Overview As mentioned in the introduction to section 2.2, indiscriminate access to these functions is not available to allusers, with different user profiles assigned to operators connecting to the system.

User types are:

- Maintenance-Upgrade ;

- System Administration ;


31/39



- Supervisor ;

- User .

Tab. 8.1 below lists permitted operations for each user type:

Tab. 8.1 Permitted Operations according to User Type

Login Role Description Privilegesoperator User Supervisor Search Database for Alarms

Show Granted UsersChange User Passw ordPerformance Statistics

alarm Alarm Management User Search Database for AlarmsSearch for License Plate Number in the Temporary Hot ListInsert/Remove Plate in the Temporary Hot ListChange User Passw ord

Accept, Store or Discard A larmsPerformance Statistics

s ys tem Sy stem A dminis tration Sy stem Manager Insert/Remove Us ersShow Granted UsersChange User Passw ordSearch Database for AlarmsSearch for License Plate Number in the External Hot ListSearch for License Plate Number in the Temporary Hot ListInsert/Remove Plate in the Temporary Hot ListUpload External Hot List Upgrade/Replace

maintenanc e Maintenanc e Maintenanc e Operator Searc h Databas e f or AlarmsSearch for License Plate Number in the Temporary Hot ListSearch for License Plate Number in the External Hot ListInsert/Remove Plate in the Temporary Hot ListShow Granted UsersInsert/Remove UsersChange User Passw ord

Accept, Store or Discard A larmsUpload External Hot List Upgrade/ReplaceSys tem ConfigurationSystem MonitoringPerformace Statistics

8.2 Users List

8.2.1 - Functional DescriptionThis function displays a list of users present in the ODM User Database used by the OWA.

8.2.2 - Warnings and PrecautionsNone.

8.2.3 - Detailed DescriptionLeft clicking on " Users " in the Main Menu displays the drop-down menu options displayed below in Fig. 8.1:


32/39



Fig. 8.1 Users Drop-down Menu

Clicking on the " Users List " item displays a list of granted users (see Fig. 8.2):

Fig. 8.2 - USERS MANAGEMENT Page with Granted Users List

8.2.4 - ExamplesSee previous paragraph.


8.3 New User Insertion


This function allows a new user to be entered in the systems user database.


33/39




8.3.3 - Detailed DescriptionLeft clicking on " Users " in the Main Menu displays the drop-down menu illustrated in Fig. 8.1. Now clickingon the " New User " item displays the page shown in Fig. 8.3:

Fig. 8.3 - USERS MANAGEMENT - Insert New User Page

A form is displayed for the operator to enter the new users data, including:

- "Login ": name of new user;

- "Password ": password associated with the new user;

- "Confirm Password ": password confirmation;

- "Role ": type of user profile associated with the new user;

- "Description ": note describing the new user.

Clicking on the " OK" button requests command execution. A confirmation dialog box is displayed to allow theoperator to go back and check the data entered before finally issuing the command (see Fig. 8.4):


34/39



Fig. 8.4 Operation Confirmation Window

At the end of the operation a result message is displayed.


8.3.5 - Possible ErrorsThe following errors are possible:

- "Password " and " Confirm Password " different;

- "Login " not specified;

- "Login " the same as that of an existing user.

In all these cases access is not allowed and the operator is informed of this with a specific message andgiven the possibility of returning to the login screen by pressing " BACK ".

8.4 User Removal

8.4.1 - Functional DescriptionThis function allows a user to be removed from the system Database.



Left clicking on " Users " in the Main Menu displays the options in the drop-down menu illustrated in Fig. 8.1.Now clicking on the " Remove User " item displays the page shown in Fig. 8.5:


35/39



Fig. 8.5 - USER MANAGEMENT - User Removal Page A drop-down list of user logins in the Database is displayed for the operator to select the user login to re-move.

Clicking on the " OK" button requests command execution. A confirmation dialog box is displayed to allow theoperator to go back and check the data entered before finally issuing the command (see Fig. 8.6).

Fig. 8.6 Operation Confirmation Dialog Box




8.5 Change User Password

8.5.1 - Functional DescriptionThis function allows a user password in the system database to be changed.

8.5.2 - Warnings and PrecautionsModification mode depends on the user profile of the operator connected to the OWA.


36/39


37/39



Both contain a form for entering the following information:

- "Login ": login name of user to change password;

- "New Password ": new password to enter;

- "Confirm New Password ": new password to enter, confirmation.

The screen in Fig. 8.7 also contains a list of the users stored in the database, whereas the one in Fig. 8.8has a Password field in which to enter the old user password.

Clicking on the " OK" button requests command execution. A confirmation dialog box is displayed to allow theoperator to go back and check the data entered before finally issuing the command (see Fig. 8.9):

Fig. 8.9 Operations Confirmation Dialog Box



8.5.5 - Possible ErrorsThe following errors are possible:

- "New Password " and " Confirm New Password " are different;

- "Password " incorrect (Fig. 8.8 only).

In all these cases the operation produces no result. The operator is informed by a specific message andgiven the possibility of going back by pressing " BACK ".

9 OPERATION LOGGING

9.1 - Functional DescriptionThe HCI incorporates a logging function to record the main operations carried out by the operator.


9.3 - Detailed Description A file is created in the OWA log folder at each system login.


38/39



Operations are stored in files with names in the following format:

< MM>< SS >_< SessionId >_ UserActions .txt

Where: < AAAA> 4 characters identifying year of creation 2 characters identifying the month of creation 2 characters identifying the day of creation 2 characters identifying the hour of creation 2 characters identifying the minute of creation 2 characters identifying the second of creation numerical characters identifying the session of creation

Logged operations include:

- User / HCI connection data;

- Alarm database queries;

- Hot List queries;

- Alarm Accept/Discard;

- Temporary Hot List Insert/Remove;

- Data Backup / Export.

9.4 - ExamplesFig. 9.1 gives an example of the start of an HCI logging file.

06-07-2004 15:27:26 - system (System Administration) - 172.19.0.31 - Mozilla/4.0 (compatible; MSIE6.0; Windows NT 5.0; .NET CLR 1.1.4322) - Connection to WEB APPLICATION06-07-2004 15:27:44 - Query 5/4/2004 15:00 - 6/7/2004 16:00 - alarms - gate - ALL -06-07-2004 15:27:52 - Export Query Data06-07-2004 15:28:04 - Backup Query Data06-07-2004 15:29:46 - Query Hot List - 5/7/2004 0:00 6/7/2004 23:59 Temporary ALL06-07-2004 15:29:05 - Query Hot List - 6/1/2004 0:00 6/7/2004 23:59 External ALL06-07-2004 15:42:01 Alarm Accept BT863ZA (0H) EvId 0000101200406040842128AB406-07-2004 16:23:27 Hot List Insert Plate AA000BB (0H) 06/09/2004 Test Plate Insert06-07-2004 16:35:27 Hot List Delete Plate AA000BB (0H)

Fig. 9.1 Example of OWA Logging File Content

As can be seen the lines indicate the following operations:

- connection to HCI;

- alarm database queries;

- data export commands;

- data backup commands;

- Temporary Hot List queries;

- External Hot List queries;

- alarm accept;

- plate insertion in Temporary Hot List;


39/39


- plate removal from Temporary Hot List;

9.5- Possible Errors

None.

10- ON LINE HELP

10.1 - Functional DescriptionThe HCI incorporates an online help function for operators. Clicking on Help in the main menu (see Fig.5.1) displays a page containing basic system instructions. Fig. 10.1 shows the Help page.

Fig. 10.1 Help On Line Page

Clicking View User Manual opens a copy of this manual in Acrobat PDF format.10.2 - Warnings and PrecautionsNone.

Documents

OSP-103.29 Communications Center - User Manual