> 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/command-centre-client/configuring-command-centre/configuring-licensable-features/data-map/understanding-data-maps.md).

# Understanding Data Maps

The ‘Visitor Management OCR Passport / Drivers License Interface’ allows the Gallagher Visitor Management Client to support an interface to the ScanShell 1000B Passport Scanner, 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 process for configuring the ‘Visitor Management OCR Passport / Drivers License Interface’ feature involves a number of procedures, including 'Creating Data Maps'. For further detail of the entire process, see "Visitor Management Passport/Drivers License Scanning Process" in the Configuration Client Help.

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.


---

# 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/command-centre-client/configuring-command-centre/configuring-licensable-features/data-map/understanding-data-maps.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.
