> 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/international-code-of-practice-intcop-7-1.md). # International Code of Practice (INTCOP 7.1) [Perimeter Fence Compliance](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance.md) › INTCOP 7.1 *Effective 24 February 2020. Supersedes all previous versions.* Every installation certified by Gallagher must comply with INTCOP 7.1. The Code of Practice outlines the **minimum acceptable standard** for Gallagher certification of an energized security fence. It is applied via an **on-site system inspection and documentation review** by Gallagher together with the Channel Partner, covering safety **and** application of product and workmanship practices, but **not** compliance to any other regulation, code, standard, construction, or specification of the installation. > 📄 **Source document:** [3E0654 - Gallagher International Code of Practice, Perimeter Systems (PDF)](https://media.gallagher.com/asset/14b3d74b-85c1-458e-acf8-3106e00a22e7/3E0654-International-Code-of-Practice-Perimeter.pdf). The governing per-market fence-installation standards (AS/NZS 3016, BS1722-17, SANS10222-3, GB/T 7946, EN60335-2-76, IEC60335-2-76) are listed in [Standards by Market](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/standards-by-market.md). **Compliance of the installation to any such standard is the responsibility of the Channel Partner.** ## Certification * Required annually for Gallagher certification to remain valid * Inspection by an authorised Gallagher staff member * Grades A (excellent) through E (major safety failure) * Grade D or E means remedial work required before the certificate is issued Signed: Greg Barclay, Chief Operating Officer, Gallagher NZ HQ. ## Prohibited Configurations * Energised barbed wire or razor wire * Mantrap construction (a person can become trapped between fence and structure) * Multiple energisers on the same fence wire (single energiser per circuit only) * Installation in a combustible or hazardous atmosphere (definition of hazardous areas is the responsibility of the site H\&S authority) ## Connecting Leads (Lead-Out Cables) * Leads run inside buildings **shall** be insulated from earthed structural parts using insulated HV cable * Leads **shall not** share conduit with mains supply, communication, or data cables * Leads and fence wires **shall not** cross above overhead power or communication lines * All mains-operated ancillary equipment connected to the fence circuit must provide isolation between the fence circuit and the supply mains equivalent to the energiser ## Personnel Access and Gates * Gate conductors should not be energised unless authorised persons have been informed of the fence function * Gates shall be capable of being secured and opened without the operator receiving a pulse * Where a gate is used for personnel access, a method to de-energise conductors should be included to prevent inadvertent contact ## Maintenance and Certification * Every installation **shall** have a formal maintenance program offered to the System User * The maintenance program should be documented and consider environmental factors, contamination, battery replacement, vegetation, and emergency repair provisions * Certification is performed by an authorised Gallagher staff member only, using the Commissioning Document Set (3E2391) * The certificate is issued in the user's name with site address and date * **Annual re-certification** is required to maintain certification > **If there is a conflict**, the requirements in INTCOP are supplementary to country-of-installation standards and should be considered **Manufacturer's Minimum Installation Criteria**. *** 🔗 **Related** * [Standards by Market](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/standards-by-market.md) · [Critical Distances Reference](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/critical-distances-reference.md) · [Warning Sign Requirements](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/warning-sign-requirements.md) · [Commissioning Checklist Summary](/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/commissioning-checklist-summary.md) *Source: INTCOP (3E0654), SECHUB-CR-INTCOP* --- # 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/international-code-of-practice-intcop-7-1.md?ask=&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.