> 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/operate/asic-registry-and-reporting.md).

# ASIC registry and reporting

Register aviation security cards and report on their status and history.

ASIC Registry and Reporting was developed to satisfy the record-keeping requirements of the **Aviation Transport Security (ATS) Regulations 2005**, for issuing **Aviation Security Identification Cards (ASICs)** and **Visitor Identification Cards (VICs)**.

### Components

* **ASIC Registration** lets an operator register and issue an ASIC per the ATS Regulations, via the Gallagher Configuration Client or the Command Centre Client. It introduces the **ASIC Cardholder Cards tile** in the Command Centre Client.
* **ASIC Reporting** reports on ASIC card status and history. **From v7.20**, it is included in the Command Centre Client reporting framework.
* **ASIC Enterprise Data Interface** is available **from v7.20**. It lets an operator import a new ASIC Cardholder or modify an existing one via Command Centre's **EDI** feature (data importable from a `.CSV` file).

**Versions supported:** v8.60 to v9.20.

***

🔗 **Related**

* [Enterprise Data Interface (EDI)](/knowledge-hub/products/cc-software/configure/interface-options/enterprise-data-interface-edi.md). The import feature the ASIC EDI uses.


---

# 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/operate/asic-registry-and-reporting.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.