> 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/products/cc-software/configure/workforce-management-solutions/alcolizer-integration.md).

# Alcolizer Integration

Connect Alcolizer breath-testing units to Command Centre for alcohol-screening results and access control.

The Alcolizer integration connects Command Centre to the **Alcolizer WM4 and Centurion** breath-testing units. When an access card is presented at a nominated reader, the Alcolizer unit starts a **Blood Alcohol Content (BAC)** test. The Pass/Fail result is sent to Command Centre and recorded as an event against the cardholder. Part numbers are **C12673** and **C12674**.

### What it does

On receiving a result, Command Centre can:

* Generate an **alarm on a failed result**, immediately alerting the operator.
* **Automatically deny site access** for the cardholder on a failed result.
* Send a **notification to the cardholder's Supervisor**.
* **Enable or activate the cardholder's Competency** on a passed result.

You can use it alongside the licensed **Random Selection** feature where testing every cardholder every day is not mandatory.

### Reporting

The **Activity Report** can report on: Cardholder failed; Cardholder passed; Cardholder Alcolizer Action Error; Failed to get Alcolizer Response; Failed to Modify Cardholder after Alcolizer Action; Failed to obtain COM port.

### Use case

A mine site must legally ensure workers are not under the influence. Integrating the existing Alcolizer breath-test unit with Command Centre supports compliance: automatic access denial on failure, immediate supervisor notification, and database-stored results for audit.

### Versions

Supported in **v8.20–v9.40** (every version).

Documentation:

{% file src="/files/MWfwoVHt8D5UK8OKtFv0" %}
Alcolizer Integration Feature Overview v6
{% endfile %}


---

# 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/products/cc-software/configure/workforce-management-solutions/alcolizer-integration.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.