> 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-kiosk/visitor-management-kiosk-document-scanning-process.md).

# Visitor Management Kiosk Document Scanning Process

### Introduction

The Gallagher Visitor Management Kiosk supports an interface to a number of scanners allowing visitors to scan a form of ID, (e.g. Passport, Driver’s License, Business Card) during the "sign in" process at a self-service Kiosk. The aim is to reduce the amount of manual data entry required and improve Visitor processing time.

The scanners that the Visitor Management Kiosk interface with are:

* ScanShell 800NR Business Card Scanner,
* 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 Kiosk and the Visitor Management Client at the same time.

### Prerequisites

Unless you are using the ScanShell 800NR which is a business card scanner only, Visitor Management Kiosk 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 Data Maps

The scanning software must be configured to automatically populate the Visitor fields (within Visitor Management Kiosk) when a visitor scans a document at a Visitor Management Kiosk.

1. Create a set of Data Maps, one for each document type, (e.g. Passport, Driver's License, Business Card), in Command Centre Client.

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

#### Adding Data Maps to the Visitor Details screen

2. Add the Data Maps (configured in Step 1) to the Selected Data Maps grid on the Kiosk Screens tab of the Visitor Management Kiosk Division Configuration, in Configuration Client.

   See [Kiosk Screens tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/configuring-visitor-management-kiosk/configuring-visitor-management-for-the-kiosk/kiosk-screens-tab.md) for the procedure.

   **Note:** The order of the Data Maps listed in the Selected Data Maps grid will match the order of the personal identification type buttons shown on the ‘Visitor Details screen’ in Visitor Management Kiosk.

#### 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:

3. Ensure the Scanner is not connected to the PC.
4. Run the **OPOS\_CCOs\_1.14.001.msi** installer located in the `‘Utilities\Visitor Management Drivers’` folder of the Command Centre installation files.
5. Install the Card Scan Drivers ( **DPInst.exe** ) located in the `‘Utilities\Visitor Management Drivers\Card Scan Drivers\Drivers'` folder.
6. 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>ScanShell 800NR,</td><td>InstallerFor800NRScanner.bat</td></tr><tr><td>SnapShell,</td><td>InstallerForSnapShellScanner.bat</td></tr><tr><td>Acuant i-Dentify ID-150,</td><td>InstallerForID150Scanner.bat</td></tr></tbody></table>
7. Restart the PC.
8. Make sure all the drivers have installed correctly by checking the Windows **Programs and Features** list.
9. Plug the scanner into the PC.
10. Manually start the Visitor Management Client.
11. Go to the Visitor window and click the **Scan** button.

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

    A Calibrate Scanner screen displays.
13. 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 documents at a self-service Visitor Management Kiosk

14. A visitor clicks the **Visitor Sign In** button at a Visitor Management Kiosk, is presented with a ‘Scan Personal Document screen’, and scans a document (form of identification).

    Any fields that are mapped to Data Maps are populated with the scan data.

    See [Visitor Management Kiosk screens](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-screens.md) for examples of the screens and the screen flow.


---

# 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-kiosk/visitor-management-kiosk-document-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.
