> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/machinery/floorpocket-v2/assembly/column-extension.md).
# Column Extension
### Lift the extension up and place on top of base column.
### Make the splices, leave bolts loose
Pro-Tip: Using a drift pin is helpfup for aligning the hole and making the bolted connection.
#### Splice Hardware
Hevi- Rail Hardware:
* Torque Specification: 41 ft/lbs
* Qty: 4 - 3/8" x 2" Socket Head Cap Screws
* Qty: 4 - 3/8" Lock Nuts
Splice Hardware:
* Torque Specification: 57 ft/lbs
* Qty: 4 - Splice Plates
1. Qty: 32 - 1/2" x 1.5" Hex Bolt
2. Qty: 32 - 1/2" Flat Washers
3. Qty: 32 - 1/2" Lock Washers
4. Qty: 32 - 1/2" Hex Nut
### Align the hevi-rail.
* Make sure the seems on the hevi-rail line up
* Tighten bolts
### Level the base platform
Adjust the leveling feet to make sure the hevi-rail is sitting plumb
---
# 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.creativeconners.com/docs/machinery/floorpocket-v2/assembly/column-extension.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.
