> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/visitor-management-passport-drivers-license-scanning-process.md).

# Visitor Management Passport/Drivers License Scanning Process

### Introduction

The ‘Visitor Management OCR Passport / Drivers License Interface’ allows the Gallagher Visitor Management Client to support an interface to a number of scanners, such that Visitor fields in the Visitor Management Client can be automatically populated when a form of ID is scanned, (e.g. Passport or Driver’s License). The aim is to reduce the amount of manual data entry required by an Operator and improve Visitor processing time.

The scanners that Visitor Management interface with are:

* SnapShell P5 Scanner, and
* Acuant i-Dentify ID-150 Card Scanner.

**Notes:**

* The SnapShell P5 Scanner supports Microsoft Windows 8 and 10 (32 & 64 bits).
* SnapShell P5 Scanners cannot be used for the Visitor Management Client and the Visitor Management Kiosk at the same time.

### Prerequisites

* If you already have version vEL.7.30.2014 with this feature installed, you must first uninstall the ScanShell SDK before Gallagher Command Centre can be upgraded, as follows:
  1. Exit Command Centre and stop the Command Centre Services.
  2. Uninstall the ScanShell SDK, (i.e. **CSSN SDK Version 10.05.20.05** ), using the Windows **Programs and Features** utility.
* Visitor Management Scanning requires the following Interface (**Accuant OCR Scanner Interface - C12716**) and Licence file entry (`Visitor Management ID Scanning=1`) to enable the capture of:
  * Passports, Drivers Licenses and National Identity Cards, and
  * information from visitors at the Visitor Management workstation, when integrated with Command Centre.

### Procedure

To configure and use this feature, perform the following procedures in the order specified.

#### Creating a Personal Data Field

1. Create a Personal Data Field (e.g. Date of Birth) that will be used by the Passport Scanner, in Configuration Client or Command Centre Client.

   See [Creating a new Personal Data Field](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/personal-data-fields/creating-a-new-personal-data-field.md) for the procedure if using Configuration Client.

   **Note:** If using Command Centre Client, see "Creating a new Personal Data Field" in the Command Centre Client Help File for the procedure.

#### Adding the Personal Data Field to Visitor Types

2. Add the Personal Data Field (configured in Step 1) to the appropriate Access Groups (Visitor Types), in Configuration Client or Command Centre Client.

   See Step 27 of [Setting up Access Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/setting-up-access-groups.md) for the procedure if using Configuration Client.

   **Note:** If using Command Centre Client, see Step 10 of "Creating a new Access Group" in the Command Centre Client Help file for the procedure.

#### Adding the Personal Data Field to the Visitor screen

3. Add the Personal Data Field (configured in Step 1) to the Selected Fields grid on the **Visitor Fields** tab of the Visitor Management Division Configuration, in Configuration Client.

   See [Visitor Fields tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/command-centre-site-configuration/configuring-visitor-management-setup/visitor-fields-tab.md) for the procedure.

   **Note:** The order of the Personal Data Fields listed in the Selected Fields grid will match the order of the Personal Data Fields shown on the Visitor screen in the Visitor Management client. If required, check the **Required when adding to a visit** or **Required when marking On Site** checkboxes.

#### Creating Data Maps

The scanning software must be configured to automatically populate the Visitor fields (within Visitor Management) when a Passport or Driver’s License is scanned.

4. Create Data Maps in Command Centre Client.

   See "Creating a Data Map" for the procedure in the Command Centre Client Help.

#### Installing the Scanner

Installing a document scanner installs the necessary SDK and drivers for the specific scanner. Log on as an Administrator, and install for each client as follows:

5. Ensure the Scanner is not connected to the PC.
6. Run the **OPOS\_CCOs\_1.14.001.msi** installer located in the `‘Utilities\Visitor Management Drivers’` folder of the Command Centre installation files.
7. Install the Card Scan Drivers ( **DPInst.exe** ) located in the `‘Utilities\Visitor Management Drivers\Card Scan Drivers\Drivers'` folder.
8. From the `‘Utilities\Visitor Management Drivers\ScannerDrivers’` folder, run the relevant silent install patch file for the type of scanner you are installing.

   **Note:** The patch files install all the drivers for the scanner from the **SDK\_setup\_is.exe** file automatically.

   <table><thead><tr><th width="198">Scanner type</th><th>Install patch file...</th></tr></thead><tbody><tr><td>SnapShell,</td><td>InstallerForSnapShellScanner.bat</td></tr><tr><td>Acuant i-Dentify ID-150,</td><td>InstallerForID150Scanner.bat</td></tr></tbody></table>
9. Restart the PC.
10. Make sure all the drivers have installed correctly by checking the Windows **Programs and Features** list.
11. Plug the scanner into the PC.
12. Manually start the Visitor Management Client.
13. Go to the Visitor window and click the **Scan** button.

    **Note:** You require the "Edit Visits" operator privilege to scan.
14. Place the calibration sheet provided with the scanner into the scanner.

    A Calibrate Scanner screen displays.
15. Click the **Calibrate** button.

    Calibration starts.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-32712889a55207b77f3d6575c64430f887984c3b%2Fscannercalibrationscreen.png?alt=media)

    When the progress bar reaches 100% calibration is complete, and a pop-up message *"Calibration done successfully"* displays.

    **Note:** The scanner needs to be calibrated before being used for the first time, and may need recalibrating if unplugged.

#### Scanning a Passport or Driver's License for a Visitor

16. Scan a visitor’s passport or driver’s license in the Visitor Management application.

    See [Scanning passports or driver licenses for visitors](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/using-visitor-management/pre-registration-and-receptionist-functions/the-find-visit-screen/scanning-passports-or-driver-licenses-for-visitors.md) for the procedure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/visitor-management-passport-drivers-license-scanning-process.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
