> 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/deployment-resources/security-and-compliance/perimeter-fence-compliance.md).

# Perimeter fence compliance

Meet perimeter fence standards, design requirements, and commissioning obligations.

The compliance rules for a Gallagher energized security fence: the Code of Practice that governs certification, the per-market installation standards, the critical distances an installer must maintain, the warning-sign requirements, and the commissioning document set that must be completed at handover.

### Subpages

| Title                                       | Description                                                                           | Link                                                                                                                                             |
| ------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| International Code of Practice (INTCOP 7.1) | The minimum standard for Gallagher certification of an energized security fence.      | [Open page](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/international-code-of-practice-intcop-7-1.md) |
| Standards by Market                         | The fence-installation standard and IEC 60335-2-76 test certificates for each market. | [Open page](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/standards-by-market.md)                       |
| Critical Distances Reference                | Separation distances for barriers, energizers, power lines, and hostile toppings.     | [Open page](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/critical-distances-reference.md)              |
| Warning Sign Requirements                   | Warning-sign placement and maintenance requirements.                                  | [Open page](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/warning-sign-requirements.md)                 |
| Commissioning Checklist Summary             | The 3E2391 commissioning document set for handover and certification.                 | [Open page](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/commissioning-checklist-summary.md)           |


---

# 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/deployment-resources/security-and-compliance/perimeter-fence-compliance.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.