> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/metal-framing/faq/family-libraries/service-holes/how-to-create-service-holes-in-horizontal-tracks.md).
# How to create service holes in horizontal tracks?
This guide explains how to prepare the service holes for CNC export before automating them using the **Detail Configurations** or **Smart Connections.** You'll need to set up the **Structural Framing** category **Service Hole** family **type settings.**
{% hint style="warning" %}
Make sure to use the **Metal Framing** families (**Settings** > **Load Families** > **Detail Families**)
{% endhint %}
{% hint style="success" %}
Note: **Imperial** service hole families already include pre-set types for CNC machine brands.
{% endhint %}
1. Navigate to the **Project Browser** > **Families** > **Structural Connections**
2. Find the **I\_SC Service Hole** (Imperial) or **M\_SC Service Hole** (Metric) family
3. Duplicate and rename any existing family type (not mandatory):
{% hint style="info" %}
When renaming a duplicated service hole family type, it's recommended to include your CNC brand name for clarity.
{% endhint %}
4. **Edit** the family **type**
5. Enter one of the values for the **CNC Type** parameter:
* **Arkitech** CNC machine:
```
Arkitech
```
* **Howick** CNC machine:
```
Howick
```
* **Knudson** CNC machine:
```
KnudsonKfsT1420
```
* **Metroll** CNC machine
```
Metroll
```
* **Pinnacle** CNC machine:
```
Pinnacle X5
```
* **Royal** CNC machine:
```
Ryoal
```
* **Scotsim** CNC machine:
```
ScotSim
```
\
6\. Enter the service hole punch command in the **CNC Command** parameter.
{% hint style="warning" %}
Your CNC machine has specific punch command names for service holes (e.g. SERVICE\_HOLE, 3, etc.). The value in the parameter must match it.
{% endhint %}
***
{% hint style="info" %}
If you can't find the answers you're looking for, please [contact our support team](https://emea.support.arkance.world/hc/en-gb/requests/new).
{% endhint %}
---
# 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://docs.besmart.software/3d-modeling-and-design/metal-framing/faq/family-libraries/service-holes/how-to-create-service-holes-in-horizontal-tracks.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.
